Using Webdispatcher for Non-SAP (i.e Lotus iNotes)

[Former Member]

Hi Experts,

We have a Web Dispatcher system setup which allow our SAP production environment to be accessed through the internet.

I have read in the documents that SAP Web dispatcher can be used to access non-SAP systems.

Does this mean we can access any other https server which is not part of

our SAP Landscape e.g Lotus iNotes, using SAP Webdispatcher as a reverse proxy?

We currently are using Apache as reverse proxy to access our Lotus iNotes.

Can we, technically, use the SAP Web dispatcher to access it instead?

Our current setup profile is attached to this msg for your reference.

When we try it based on the profile below we are not able to !!?

Appreciate any advise ... Thx

Rgds,

Sheikh Saggaf

WebDisp_Profile.txt.zip

[Former Member]

Dear Sheikh

SAP Web-Dispatcher can be used in front of non-SAP systems also. For configuration, you need to set parameter SAP Web-Dispatcher profile parameter "wdisp/system_<xx>" with "EXTSRV" option. Currently, in the attached profile file, this parameter is commented.

For details on various configuration set-up of parameter "wdisp/system_<xx>", please refer sap help link:

http://help.sap.com/saphelp_nw73/helpdata/en/1b/b0fd8a12344c4ca89b7a1c5d1d7310/content.htm

I hope this helps you!

Tapan

[former_member237791]

Dear Tapan

Thank you for your Answer.

We have tried what is suggested the SAP Help but it seems that we still have issues in trying to connect to outside servers. What we want to do is use the SAP Webdispatcher to Access our production SAP - which it is successfully doing using port 8443 and a redirect. We want to use port 8444 to direct us to another server(Lotus Inotes) in our case. Referenced below is the profile we are using. Can anyone assist us how to get connected to our non-SAP system.

unique instance number

SAPSYSTEM = 88

# add default directory settings

DIR_EXECUTABLE = .

DIR_INSTANCE = .

# Accessibility of Message Servers

rdisp/mshost = 10.2.16.25

ms/http_port = 8188

# SAP Web Dispatcher Parameter

wdisp/system_2 = SID=EXT, EXTSRV=https://10.2.16.87:443, SRCSRV=10.2.3.26:8444

wdisp/auto_refresh = 25

wdisp/max_servers = 100

wdisp/shm_attach_mode = 6

wdisp/ssl_encrypt          = 0

wdisp/add_client_protocol_header = true

ssl/server_pse          = /usr/sap/webdisp/sec/SAPSSLSN.pse

ssl/ssl_lib                    = /usr/sap/webdisp/secudir/linux-x86_64-glibc2.3/libsapcrypto.so

#wdisp/server_info_location = /usr/sap/webdisp/info.icr

# configuration for default scenario (medium size)

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

#maximum number of concurrent connections to one server

wdisp/HTTP/max_pooled_con = 500

wdisp/HTTPS/max_pooled_con = 500

# SAP Web Dispatcher Ports

icm/server_port_0 = PROT=HTTPS,PORT=8443,TIMEOUT=180, PROCTIMEOUT=3600

icm/server_port_1 = PROT=HTTP,PORT=0

icm/server_port_2 = PROT=HTTPS,PORT=8444,TIMEOUT=180, PROCTIMEOUT=3600

icm/HTTPS/verify_client = 0

#icm/server_port_2 = PROT=HTTPS,PORT=8444,TIMEOUT=180, PROCTIMEOUT=3600

# SAP Web Dispatcher Web Administration

icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt

icm/HTTP/redirect_0 = PREFIX=/, TO=/sap/bc/gui/sap/its/webgui/!