SAP webdispatcher maintenance mode

[chris_mckay2]

Hi there,

We have setup a new webdispatcher which will redirect requests to our enterprise portal. The webdispatcher was built using sapinst and the profile is being maintained through the MMC not by the sapwebdisp.pfl file. The redirect seems to be working properly, but when we put the webdispatcher into maintenance mode the redirect still goes directly to the portal, and does not display the maintenance mode page. Would there be a specific parameter in the MMC that I have missed to configure? Anyone else have this issue??

Any information would be greatly appreciated.

Kind regards,

Chris

[isaias_freitas · Accepted solution]

Hello Chris,

What do you mean by "redirect"?

Did you configure the Web Dispatcher to send a "redirect response" to the end user, so the end user reaches the Portal system directly?

Attaching the Web Dispatcher profile to this thread might be helpful as well.

Kind regards,

Isaías

[chris_mckay2 · Accepted solution]

Hi Isaias,

Shown below is the profile. I am just trying to get the standard maintenance mode working. I built a few webdispatchers a few years ago and setup the profile by running the sapwebdisp.exe -bootstrap method. This time we just built the webdispatcher using sapinst and edited the parameters through the MMC. It will reach the portal, but when I place it in maintenance mode you can still access the portal normally, which I don't expect. Perhaps the webdispatcher isn't communicating to the portal properly??

Anyways thanks again for the response, and below is the profile:

#generated by user: Fri Oct 02 11:43:55 2015

SAPSYSTEMNAME=NXX

SAPGLOBALHOST=NXXXXX

SAPSYSTEM=00

INSTANCE_NAME=XXX

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

DIR_EXECUTABLE=$(DIR_CT_RUN)

DIR_PROFILE=$(DIR_INSTALL)\profile

_PF=$(DIR_PROFILE)\NXX_XXX_XXXXXX

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

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

# Accesssability of Message Server

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

rdisp/mshost=nXXXXXXX.XXXXX.XX

ms/http_port=8101

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

# 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,PORT=8100,TIMEOUT=90,PROCTIMEOUT=600

icm/server_port_1=

icm/server_port_2=

icm/server_port_3=

icm/server_port_4=

icm/HTTP/admin_0=PREFIX=/sap/admin,DOCROOT=D:\usr\sap\XXX\XXX\data\icmandir/admin,PORT=8100,AUTHFILE=D:\usr\sap\XXX\SYS\global\security\data\icmauth.txt

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

# Start webdispatcher

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

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

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

SETENV_01=SECUDIR=$(DIR_INSTANCE)/sec

is/HTTP/show_detailed_errors=FALSE

icm/HTTP/redirect_0=PREFIX=/,TO=/irj/portal,HOST=nsportal.ycdsb.ca,PORT=50000,FROM=/*

icm/HTTPS/verify_client=0

[isaias_freitas · Accepted solution]

Hello,

icm/HTTP/redirect_0=PREFIX=/,
      TO=/irj/portal,HOST=nsportal.ycdsb.ca,PORT=50000,FROM=/*

This parameter is effectively making the end users bypass the Web dispatcher and access the Portal system directly.

Please change it to the below, and it should work fine then .

icm/HTTP/redirect_0 = PREFIX=/, TO=/irj/portal

Regards,

Isaías

[chris_mckay2 · Accepted solution]

Hello again Isaias,

Thank-you very much for the information, that worked perfectly.

Greatly appreciated.

Kind regards,

Chris

[isaias_freitas · Accepted solution]

You're welcome!

[chris_mckay2 · Accepted solution]

Hi Isaias,

Although a little off topic, would you know the proper procedure to have a custom page shown when entering maintenance mode? ie: file name, location??

Regards,

Chris

[isaias_freitas · Accepted solution]

Hello Chris,

It is better to ask different questions in separate threads.

This way, other SCN users can find the information they are looking for more clearly.

Anyway, see the following SAP Help pages:

Maintenance Mode - SAP Web Dispatcher - SAP Library

Setting Up Your Own Error Pages - SAP Web Dispatcher - SAP Library

Regards,

Isaías

[chris_mckay2 · Accepted solution]

Thank you again for your assistance.

[Former Member]

icm/HTTP/file_access_0 i changed the PREFIX to /irj/images/ instead of /images/

working fine now...thanks guys!

regards Marco

[Former Member]

FYI

hmmz deleted wdisp/system_0 from my profile and added rdisp/mshost and ms/http_port to my profile. Both containing my backend (portal). This works but now my customized errorpage is shown without jpegs.

[isaias_freitas]

Hello,

You should not use "rdisp/mshost" and "ms/http_port".

These are deprecated parameters and were replaced by the "wdisp/system_X" parameter.

The Web Dispatcher will act similar to a proxy server.

When you access https://<webdispatcherhost>:<port>/irj/portal the Web Dispatcher will choose which Portal instance will handle the request and forward the request to that instance.

The Portal will reply to the Web Dispatcher, which will forward the response to the end user.

Regards,

Isaías

[Former Member]

Hi Isaias,

Can't get it working with the new parameter, with the deprecated it does work.

example (made during install):

wdisp/system_0 = SID=<SID_BACKEND>, MSHOST=<HOSTNAME_BACKEND>, MSPORT=8101, SSL_ENCRYPT=2, SRCURL= /

Doesn't work.

What does work is:

rdisp/mshost = <HOSTNAME_BACKEND>

ms/http_port = 8101

What am I doing wrong?

Kind regards Marco

[isaias_freitas]

The wdisp/system_0 parameter looks fine to me...

Anyway, glad to hear it is working now!

[Former Member]

Hi Isaias,

I understand that ;-). I expect people to add the webdispatcher URL in their browser. The webdispatcher redirect to the portal. When I delete parameter HOST from icm/HTTP/redirect_0 the behaviour will be https://<webdispatcherhost>:<port>/irj/portal and that url does not exist.

please explain 😉

Regards Marco

[Former Member]

Hi Chris,

Did you install the webdispatcher on the portal system or on a dedicated server?

We have the same problem.

I also added the portal hostname to the redirect. Without the hostname it adds /irj/portal to the webdispatcher host.

Kind regards Marco

[isaias_freitas]

Hello Marco,

Without the hostname it adds /irj/portal to the webdispatcher host.

This is the expected behavior, so the end users perform the access through the Web Dispatcher, not directly to the Portal / other backend system.

Kind regards,

Isaías

[chris_mckay2]

Hi Marco,

The webdispatcher is installed on a dedicated server.

Regards,

Chris