HTTP load balancing NW 2004

[Former Member]

We recently upgraded our hardware and OS. Hardware is 64 bit and OS is Win 2003 with MSSQL 2005. Since then our HTTP load balancing has not worked. BEX and RFC load balancing okay. We are using EP 6 for SSO to BW. In portal config we are using port 8100 for the message server. Nothing has changed there. We did cluster our backend when we upgraded. I do not know if we left something off (parameters) or something is missing. We are using the message server as load balancing. Does the App servers need something to let the message server know they are out there ?

[Former Member]

Here is what I see in the log. For some reason it does not like the paramteter. This parameter is in the default profile. I beleive this needs to be moved to the CI profile only. IS this correct ?

[Thr 6404] Thu Mar 08 09:39:12 2007

[Thr 6404] set HTTP state to CLOSED

[Thr 6404] MsHttpPortRemoveIdx: removed ms/server_port_0=PROT = HTTP, PORT = 8100 (1)

[Thr 6404] *** HTTP port 8100 state CLOSED ***

[Thr 6404] *** HTTP port 8100 state LISTEN ***

[Thr 6404] set HTTP state to LISTEN

[Thr 6404] Thu Mar 08 09:43:15 2007

[Thr 6404] *** ERROR => MsSetServerPort: illegal protocol: HTTxP [msxxhttp.c 2916]

[Former Member]

That has all ben done. The one thing I find differeent is the profile parameter ms/server_port_0 is not in the kernel (sapparam). I believe this is the parameter we always used. The URL that is generated has the wrong port. I read note 805344 but need to know where that information is derived from. From what I have read, it should be using a profile parameter. I pulled a document for BW load balancing and set things up as it directed, using ms/HTTP_Port = and still does not work. This all semmed to work fine until we upgraded our hardware to X64 and clustered the DB and CI. Of course, due to the 64 bit, this was installed with a different installation master and different kernel files.

[Former Member]

ms/HTTP_Port is obsolete.

ms/server_port_0 is the new syntax.

Under work/dev_ms you can see if http is started (and maybe what goes wrong if it does not start)

-AD

[Former Member]

You need to activate a couple of services in SICF:

/sap/public/icf_info

/sap/public/icf_info/logon_groups

/sap/public/icf_info/urlprefix

Check note 751873

-AD

[Former Member]

no you don't need.

[Former Member]

Do we need the JAVA add on installed on our app servers ?

[Former Member]

Hi Garry,

No, you do not need Java installed in your backend system. I think I misunderstood your configuration.

You mention that BEX and RFC load balancing work OK, so the new application servers are in contact with the message server. Where are you configuring the portal -> message server connection? See <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/ea/d4df3df2ad685ae10000000a11405a/frameset.htm">Editing SAP System Properties</a>.

Best Regards,

Matt

[Former Member]

In the link it says to look at the Message Server parameter in the system landscape. I have gone to the system landscape and that parameter is not there.

[Former Member]

We are not using the WEB dispatcher. We are only using the message server to load balance the requests.

[Former Member]

Hi Garry,

You need either the Web Dispatcher or other load balancer to distribute the requests. See the help <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/05/d5ca3d695f2051e10000000a114084/frameset.htm">Load Balancing Between Many Java Instances</a>.

Best Regards,

Matt

[Former Member]

Hi Garry,

Are you using logon groups for the application servers? http://help.sap.com/saphelp_nw2004s/helpdata/en/a9/775a421b5ec153e10000000a1550b0/frameset.htm

Best Regards,

Matt