SAP Sourcing and WebDispatcher

[Former Member]

Hi all,

We have installed Sourcing 9.0 under Solaris, and all working correctly from the standard URLs, for system, enterprise, and buyer.

Now, I've tried to use a sap Web Dispatcher, and when I start a check config, I got the followng:

Checking SAP Web Dispatcher Configuration

=========================================

maximum number of sockets supported on this host: 32768

Server info will be retrieved from host: fcosd100.yourict.net:8137 with protocol: http

Checking connection to message server...OK

Retrieving server info from message server...OK

Message Server instance list

+---------------------+---------------------+---------+----------+

|    instance name    |    hostname         |HTTP port|HTTPS port|

+---------------------+---------------------+---------+----------+

|       J2EE365667720 |fcosd100.yourict.net |   53600 |          |

+---------------------+---------------------+---------+----------+

Checking ABAP servers with URL "/sap/public/icman/ping":

No server group "!DIAG" defined

Checking J2EE servers with URL "/index.html":

Checking J2EE server http://fcosd100.yourict.net:53600...not active - IGNORED

Web Dispatcher configuration for J2EE only system: No server group !DIAG defined

On double stack systems, configure Web Dispatcher to access Message Server of SAP Web AS ABAP

Check ended with 0 errors, 0 warnings

But when I try to start from URL, there's no connection to server, here's the profile :

SAPSYSTEMNAME = WSD

SAPSYSTEM = 45

INSTANCE_NAME = W45

DIR_CT_RUN = $(DIR_EXE_ROOT)/run

DIR_EXECUTABLE = $(DIR_CT_RUN)

SAPLOCALHOST = fcowsd45

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

# Accesssability of Message Server

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

rdisp/mshost = fcosd100

ms/http_port = 8137

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

# Configuration for medium scenario

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

icm/max_conn = 16384

icm/max_sockets = 16384

icm/req_queue_len = 6000

icm/min_threads = 100

icm/max_threads = 250

mpi/max_pipes = 20500

mpi/total_size_MB = 500

mpi/buffer_size = 32768

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

# SAP Web Dispatcher Ports

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

icm/server_port_0 = PROT=HTTPS,PORT=443,TIMEOUT=3600,EXTBIND=1,HOST=fcowsd45

icm/HTTP/redirect_0 = PREFIX=/, TO=/sourcing/fssystem/portal/login

Can you please propose a check to do ?

Thanks.

[Former Member]

If your backend system is a Java-only system, then you can disregard the message because the "!DIAG" group exists only for ABAP or dual-stack systems.