Managing Serviceguard Extension for SAP Version B.05.10, December 2012

do not need to change batch jobs, which are tied to the locality, after a switchover, even if the
hostname which is also stored in the above tables differs.
Installation Step: IS1180
Within the SAP Computing Center Management System (CCMS) you can define operation modes
for SAP instances .
An operation mode defines a resource configuration for the instances in your SAP system. It can
be used to determine which instances are started and stopped, and how the individual services
are allocated for each instance in the configuration.
An instance definition for a particular operation mode consist of the number and types of work
processes as well as start and instance profiles (starting with version 3.0, the CCMS allows profile
maintenance from within the SAP system).
When defining an instance for an operation mode, enter the hostname and the system number of
the application server. By using <relocci> to fill in the hostname field, the instance is working
under control of the CCMS after a failover without any change.
If an instance is running on the standby node in normal operation (and is stopped when switching
over), the control console shows this instance to be down (for example, you will get a red node
on a graphical display) after the switchover.
Installation Step: IS1190
A 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. In scenarios using external web communication, one or more SAP Web Dispatcher
often accompanies the ICMs. The SAP Web Dispatcher can be laid out redundantly with hardware
load balancing. SAP also allows SGeSAP packaging for a single Web Dispatcher.
To find out if ICM is configured as part of an Application Server, 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. Therefor a
parameter
icm/host_name_full=<relocatible_ip>
needs to be set within the Instance Profile of the Application Server.
Double-check the settings with report RSBB_URL_PREFIX_GET or review the parameters within
the SMMS transaction.
Installation Step: IS1200
If you cluster a Central Instance or an ABAP System Central Service Instance, configure the frontend
PCs to attach to <relocci>.
Most of the time, this can be achieved by distributing a new saplogon.ini file to the windows
directory.
SAP Application Server Configuration 115