Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Application Configuration
Chapter 2 89
IS1080 Installation Step:
SAP Internet Communication Manager (ICM) may run as part of any
application server. It is started as a separate multi-threaded process and
can be restarted independently from the application server. E.g. usage of
BW web reporting, Business Server Pages (BSP) rely on ICM to work
properly. To find out if ICM is configured as part of the Central Instance,
check for the following SAP profile parameter:
rdisp/start_icman=TRUE
ICM gets switched over with the Instance package. In order to make it
work, ICM has to be registered with the message server using a virtual
IP address.
This mechanism is different from SAPLOCALHOST and
SAPLOCALHOSTFULL since ICM allows HTTP Server Aliasing via
icm/server_port_<nn> settings.
During startup, icman reads its configuration and propagates it to the
SAP Message Server or the SAP Web Dispatcher Server. These servers
then act as the physical point of access for HTTP requests. They classify
requests and send HTTP redirects to the client in order to connect them
to the required ICM Instance. This only works properly if the bound ICM
instances propagate virtual IP addresses. Therefore a parameter:
icm/host_name_full=<relocci> needs to be set within the instance
profile of the Central Instance.
Doublecheck the settings with report RSBB_URL_PREFIX_GET or
review the parameters within the SMMS transaction.
IS1090 Installation Step:
Configure the frontend PCs and their webbrowsers to attach to <relocci>.
For SAPGUI this can be achieved by distributing a reconfigured
saplogon.ini file to the Windows directories of the frontend PCs.