Skip to Content
author's profile photo
Former Member

Message Server to ICM(s) redirection issue

Hello,

System setup:

Backend network address: server_i0.domain.com.au

Backend ip address: 10.10.1.10

Frontend network address: server_e0.domain.com.au

Frontend ip address: 172.16.195.10

ABAP HTTP Message Server port: 8125

ICM port: 8025

The backend network is obviously a highspeed network that our SAP servers use to communicate to each other.

The frontend network is our LAN/WAN environment that our end users use to access our SAP systems.

From the browser (IE 6.0) if I enter the following URL:

http://server_e0.domain.com.au:8125 I should be automatically redirected to http://server_e0.domain.com.au:8025

This is not happening. It works if I define the server_i0.domain.com.au address in my hosts file on my pc referencing the LAN/WAN IP address of 172.16.195.25 and then use the URL of http://server_i0.domain.com.au:8125 (auto redirected to port 8025)

What do I need to do on the backend WAS to allow server_e0.domain.com.au:8125 to redirect to port 8025??

Regards

Shaun

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Oct 04, 2005 at 03:59 AM

    Hi,

    do I get it right, that you want to use the message server as load balancer for your ABAP system?

    This can be done in transaction SICF, in the corresponding service you would like to use.

    Anyway this is not the recommended way to load balance since for example bookmarking doesn't work. I would recommend to install a load balancer (if you want on the same box) for example the SAP Web Dispatcher.

    Regards,

    Jochen

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Jochen,

      No, we don't plan to use the message server to load balance to our ICMs. We will be using the SAPWebDispatcher, however we have an issue as I described above where the message server SHOULD route us to the ICM port. It is not doing this on our frontend network, only on our backend network.

      Hope this helps.

      Cheers

      Shaun