Running Application Sharing Server in a
Clustered Environment 
Use
This topic describes the configuration steps you need to perform to run the Application Sharing Server in a clustered environment.
If you are running the Application Sharing Server on a single server instance with multiple server nodes, you need to fulfill certain steps mentioned in this procedure. You are notified when a step is not necessary.
You may skip this section if you have not installed the Application Sharing Server, disabled it, or installed the server on a dedicated machine outside the clustered environment (and the machine does not comprise multiple server nodes).
Prerequisites
● The Application Sharing Server is installed on a portal machine in a clustered environment.
●
You are using a software-based load balancer.
Currently, only the SAP Web Dispatcher (see 
SAP Web
Dispatcher) has been tested and qualified. If you are using a load
balancer solution from a different vendor, it must be software-based, and
support session stickiness and traffic load balancing through the use of a URL
prefix.
If you are running a single server instance only with multiple server nodes, this prerequisite is not relevant.
● On the SAP Web Dispatcher, you have defined a unique logon group and assigned to it the server machines in the cluster that participate in balancing the load of application sharing sessions.
Even if you intend to use all instances in the cluster, the Application Sharing Server still requires that you define a logon group name.
For
information on how to set up a logon group for SAP Web Dispatcher in a
Workload Distribution scenario, see Configuring the SAP
Web Dispatcher.
If you are running a single server instance only with multiple server nodes, this prerequisite is not relevant.
● The Application Sharing Server must be enabled on all server nodes on each server instance (see Enabling / Disabling the Application Sharing Server (RTC)). This is only relevant to the server instances that are assigned to the logon group, which handle Application Sharing Server requests.
Procedure
...
...
1. In the portal, navigate to the Application Sharing configuration settings, as described in Setting Application Sharing Server Parameters (RTC).
2. Configure the following configuration objects. To edit an existing configuration object, select its checkbox, and then click Edit.
If the following configuration objects do not exist, you need to create them. The name of each configuration object must be defined exactly as shown in the table below; names are case-sensitive. To create a configuration object, click New.
Configuration object (Parameter) |
Description (Value |
ClusterLogonGroupName |
If you are using a SAP Web Dispatcher, enter the same logon name (or zone) which you defined on the SAP Web Dispatcher. The logon name specifies which machines in the cluster participate in distributing load for all application sharing sessions.
If you are not using a SAP Web Dispatcher, change the default value (undefined) to any value; for example: irj. Failure to do so will prevent the Application Sharing Server from functioning properly. If your environment consists of a single server instance only with multiple server nodes, enter any unique portal-based logon group. |
ClusterGroupSeparator |
Enter the same zone
separator string or symbol that has been set on the SAP Web Dispatcher (see The separator indicates which segment in the request URL refers to the logon group name (the logon group name is the string that follows the separator). By default, the separator is a tilde symbol (~).
If you are running a single server instance only with multiple server nodes, you need to enter the same zone separator as set on the J2EE Engine. |
If you are using SAP Web Dispatcher and RTC application sharing sessions are not functioning, you may need to increase the value of the processing timeout parameter (PROCTIMEOUT) for icm/server_port_<xx> in the SAP Web Dispatcher profile file.
For more
information, see icm/server_port_<xx>
> Processing timeout Option
PROCTIMEOUT.