Portal access problem through Web Dispatcher

[janos_czettler]

Hi Experts,

We have a newly installed Web Dispatcher (7.41, installed with SWPM). I'm using the one WD with more system scenario with modification rules. So there are two systems:

- one ABAP stack with sid D07

- one portal with sid PD2

There are two aliases for reach these systems through the WD.

- for D07: wdtest_d07.mydomain.com

- for PD2: wdtest_pd2.mydomain.com

the WD is on hle0125.mydomain.com

The WD is listening no port 8888.

The content of modifcation handlers is the following:

Compatibility Rules

-------------------

icm/HTTP/forward_ccert_as_header = TRUE

wdisp/add_clientprotocol_header = TRUE

HTTP Rewrite Rules

------------------

if "%{HTTP_HOST}" regimatch "wdtest_d07"

  SetHeader "x-sap-webdisp-target-sid" "D07" [break]

if "%{HTTP_HOST}" regimatch "wdtest_pd2"

  SetHeader "x-sap-webdisp-target-sid" "PD2" [break]

When I call this: http://wdtest_d07.mydomain.com:8888/sap/bc/ping or other services for the ABAP sytem through the WD is works perfect.

When I call this: http://wdtest_pd2.mydomain.com:8888 the startPage (SAP NetWeaver Application Server Java) is coming up.

Then I select any link with is needs authentacion (eg. SAP NetWeaver Administrator for nwa)

I try to login (eg. J2EE_ADMIN), i got the following:

I don't know why. The portal PD2 works fine without WD.

Here is the instance profile for the WD:

SAPSYSTEMNAME = WDD

SAPGLOBALHOST = hle0125

SAPSYSTEM = 10

INSTANCE_NAME = W10

DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64

DIR_EXECUTABLE = $(DIR_CT_RUN)

DIR_PROFILE = $(DIR_INSTALL)\profile

_PF = $(DIR_PROFILE)\WDD_W10_hle0125

SETENV_00 = PATH=$(DIR_EXECUTABLE);%PATH%

#-----------------------------------------------------------------------

# Accesssability of Message Server

#-----------------------------------------------------------------------

rdisp/mshost = saps12.hostlogic.hu

ms/http_port = 8120

#-----------------------------------------------------------------------

# Configuration for medium scenario

#-----------------------------------------------------------------------

icm/max_conn = 500

icm/max_sockets = 1024

icm/req_queue_len = 500

icm/min_threads = 10

icm/max_threads = 50

mpi/total_size_MB = 80

#-----------------------------------------------------------------------

# SAP Web Dispatcher Ports

#-----------------------------------------------------------------------

icm/server_port_0 = PROT=HTTP,HOST=hle0125,PORT=81$$

icm/server_port_1 = PROT=HTTP,HOST=localhost,PORT=81$$

icm/HTTP/admin_0 = PREFIX=/sap/admin,DOCROOT=$(DIR_DATA)$(DIR_SEP)icmandir,AUTHFILE=$(icm/authfile),PORT=81$$

#-----------------------------------------------------------------------

# Start webdispatcher

#-----------------------------------------------------------------------

_WD = $(DIR_EXECUTABLE)\sapwebdisp$(FT_EXE)

Start_Program_00 = local $(_WD) pf=$(_PF)

SETENV_01 = SECUDIR=$(DIR_INSTANCE)/sec

icm/server_port_2 = PROT=HTTP, PORT=8888

wdisp/system_0 = SID=D07, MSHOST=sapd07.mydomain.com, MSPORT=8110

wdisp/system_2 = SID=PD2, MSHOST=sappd2.mydomain.com, MSPORT=8105

icm/HTTP/mod_0 = PREFIX=/, FILE=E:\usr\sap\WDD\SYS\global\mod_rules.txt

Is there any idea of somebody why does not the portal access work?

Thank you!

Regards,

Janos

[janos_czettler · Accepted solution]

the problem solved in two steps

1. patching the wd up to level 49, the chrome and firefox works now, but the explrer does not

2. the exploret does not support the character '_' in the hostname, but only '.' or '-'

now all browsers works with wd!

[janos_czettler]

Hi!

Some other additional info... as I wrote tomorroww, the portal access through WD works with Chorme but not with IE.

I turned on the http trace on the ED and I get the following:

for Chrome (the portal access works):

10.108.235.67 - - [01/Aug/2014:15:55:45 +0200] "POST

/webdynpro/resources/sap.com/tc~lm~itsam~ui~mainframe~wd/j_security_check HTTP/1.1" 302 742

for IE (does not work):

10.108.235.67 - - [01/Aug/2014:15:21:55 +0200] "POST /webdynpro/resources/sap.com/tc~lm~itsam~ui~mainframe~wd/j_security_check HTTP/1.1" 404 682

As I know the HTTP respond 302 means redirection, and the 404 is a not found. But why the 404 with IE?

[Former Member]

Anything in defaultTrace? Somehow I doubt it is a problem with Web Dispatcher, it's just coincidence. Have you installed the latest patch level for WD? What is the version and SP level of your AS JAVA? Have you changed Login Modules or Auth Schemes? Are you using some sort of SSO?

[janos_czettler]

an additional info. I checked it whit Chrome, and the portal access works through the wd, but there is the error:

if I click on the related link I get this:

This is that error, what IE shows immediately when trying to access the portal (eg. nwa).

But without using WD (direct access to portal), both of IE and Chrome works, but in this case I can see the missing resource above. However the IE can handle that, and does not show any error.

I was totally confused