cancel
Showing results for 
Search instead for 
Did you mean: 

NW7.40 standalone SAP Web Dispatcher & CISO Load balancer

Former Member
0 Kudos

I am trying to use a URL which points to our VIP.  I can use the URL in Internet Explorer 10 from my desktop and call /sap/bc/ping successfully.

I know the port the VIP is off loading and have wdisp/system_0 = SID=, MSHOST=(my_url), MSSPORT=xxxx, and SRCSRV=*:xxxx configured in my profile.

I can telnet to both the url and IP address with the  designated secure message server port from my source Microsoft Server 2008 SR2 x64.  I can start the Web Dispatcher locally but not successful in making an RFC call through the VIP and into the backend.

Results of sapwebdisp pf=(my_profile) -checkconfig:

Server info will be retrieved from host: abc.myurl.com:xxxx with protocol: https
Checking connection to message server of system (my SID)...
ERROR: Unexpected HTTP OK code 404 received -
please check that abc.myurl.com:xxx is really the HTTPS port of the Message Server

Check ended with 1 errors, 0 warnings

I have tried both secure ports which are active on the backend ABAP instance with identical results.  And as stated previously I can resolve the URL https://abc.myurl.com/sap/bc/ping from my desktop successfully.

Trace Level 3 log shows: [SAP Note 552286 is of course NOT Helpful!]

Thr 2288]   Subject Alt Names: dNSName=def.ux.myurl.com, dNSName=ghi.ux.myurl.com, dNSName=abc.myurl.com

[Thr 2288]   MatchTargetName("abc.myurl.com", dNSName="abc.myurl.com") == EXACT match

[Thr 2288] <<- SapSSLSessionStart(sssl_hdl=0000000008106800)==SAP_O_K

[Thr 2288]  in/out: status = "resumed SSL session"

[Thr 2288]   Subject DN = "CN=abc.myurl.com, SN=400003312, BC=Private Organization, O=myurl., OID.1.3.6.1.4.1.311.60.2.1.2=Texas, OID.1.3.6.1.4.1.311.60.2.1.3=US, L=Houston, SP=Texas, C=US"

[Thr 2288]   Issuer  DN = "CN=Entrust Certification Authority - L1E, OU="(c) 2009 Entrust, Inc.", OU=www.entrust.net/rpa is incorporated by reference, O="Entrust, Inc.", C=US"

[Thr 2288] ->> SapSSLWrite(sssl_hdl=0000000008106800, buf=00000000153AF500, len=50, timeout=60000, &writelen=00000000153AF420)

[Thr 2288] <<- SapSSLWrite(sssl_hdl=0000000008106800)==SAP_O_K

[Thr 2288]  in/out: ... = "buf= 00000000153AF500, written= 50 of 50 (all)"

[Thr 2288] ->> SapSSLRead(sssl_hdl=0000000008106800, buf=0000000014144CC0, buf_max=65535, timeout=60000, &readlen=00000000153AF410)

[Thr 2288] <<- SapSSLRead(sssl_hdl=0000000008106800)==SAP_O_K

[Thr 2288]  in/out: ... = "buf= 0000000014144CC0, max=65535, received=2502"

[Thr 2288] IcrIHandleHTTPClientRequest received response: len = 2502

[Thr 2288] ICT: IctIHttpOpenMessage: 0000000014154CD0 typ=2

[Thr 2288] ICR: HTTP response error code = 404

[Thr 2288] ICT: IctHttpCloseMessage( 0000000014154CD0 ) -> u=0 rc=0

[Thr 2288] ->> SapSSLSessionDone(&sssl_hdl=0000000007F8C668)

[Thr 2288] <<- SapSSLSessionDone()==SAP_O_K

[Thr 2288]      in: sssl_hdl   = 0000000008106800

[Thr 2288]  in/out: ... ni_hdl = 59

[Thr 2288] NiICloseHandle: shutdown and close hdl 59/sock 32820

[Thr 2288] IcmConnClientRqFree: Connection 0/8 closed

[Thr 2288] IcmConnFreeContext: context 0 released

[Thr 2288] IcmServDecrRefCount: webdisp1:65477 - new serv_ref_count: 0

[Thr 2288] IcrIHandleHTTPClientRequest dest='abc.myurl.com:xxx' URL='/msgserver/text/logon?version=1.2' -> -1

[Thr 2288] *** ERROR => Could not connect to SAP Message Server at abc.myurl.com. URL=/msgserver/text/logon?version=1.2 [icrxx.c      4315]

[Thr 2288] *** ERROR => rc=-1, HTTP response code: 404 [icrxx.c      4316]

[Thr 2288] *** ERROR => see also SAP note 552286 [icrxx.c      4317]

Accepted Solutions (0)

Answers (1)

Answers (1)

bxiv
Active Contributor
0 Kudos

MSHOST should not be 'my_url' it should be the dns name or virtual name, servername or SAP*** (* = SID)

As for the SRCSRV port are you using the port defined in your icm/server_port_XX?

wdisp/system_0 = SID=, MSHOST=(my_url), MSSPORT=xxxx, and SRCSRV=*:xxxx

I'm also not sure where the Cisco ACE comes into play, are you trying to get the web dispatcher to work first and then bringing in the ACE or is it already behind the ACE and its handing traffic off to the web dispatcher?

Former Member
0 Kudos

Hello Billy,

I am aware of the parameter values.  I have removed actual entries for security purposes.  I am using a fully qualified DNS name.

SRCSRV is pointing to backend ms/server_port_0.

I already have a separate Web Dispatcher bypassing the CISCO ACE.  For another project we need this next web dispatcher in front of the CISCO ACE and its handing traffic of to the Central Instance.

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

SRCSRV= <source-services> : Specifies the possible host/port combinations in a list separated by semicolons: <sourceservices>=
<host1>: <port1>[; <host2>: <port2>;…], whereby for host name and port the wild card character * can be
used to specify every possible host name and port.

Each port specified here is configured in the Web dispatcher as the HTTP port (parameter icm/server_port_<xx>).

Example
SRCSRV=*:8073 means: All requests arriving through the Web Dispatcher port 8073 should be forwarded to this system.
SRCSRV=*:8083;*:8073 means: All requests arriving through the Web Dispatcher ports 8073 and 8083 should be forwarded
to this system.

bxiv
Active Contributor
0 Kudos

Understood about using examples for the configuration lines.

I also agree with the srcsrv=*8073 and the other example.

What is your current icm/server_port_## for abc.myurl.com?

Former Member
0 Kudos

Hello Billy,

Are we referring to the Web Dispatcher or backend in regards to the question on icm/server_port_##.

I believe you mean the Web Dispatcher and I am testing with port 65477.

Cheers,

Dan Mead

bxiv
Active Contributor
0 Kudos

I was referring to the web dispatcher, and now my question is for your wdisp configuration line, does it use SRCSRV=*:65477.


[Thr 2288] ICR: HTTP response error code = 404

[Thr 2288] IcrIHandleHTTPClientRequest dest='abc.myurl.com:xxx' URL='/msgserver/text/logon?version=1.2' -> -1

With your trace I am led to believe that the HTTP 404 is due to URL test that is done to verify the system is operational.  Do you have unique ## numbers for every wdisp?

Also do you have the same system listed multiple times in the configuration?  Not sure if you are running into the multiple matching systems configuration which is false by default.

Former Member
0 Kudos

Question 1:

wdisp/system_0 SRCSRV was not using that port.

Question 2:

Yes, for now I have set up wdisp/system_0 and wdisp/system_1 but plan on more.

Question 3:

Not sure what you mean by having system listed multiple times?

  Besides wdisp config I have rdisp/mshost=abc.myurl.com;def.myurl.com

Cheers,

Dan Mead