Using Connections with Siebel Server Load Balancing
Load balancing is a new feature introduced in Siebel Server 7.7. With this feature, depending on the number of concurrent client sessions, multiple Siebel servers can share the system work load. To make this load balancing possible, Siebel introduced the concept of a virtual server, which is a logical grouping of several Siebel servers.
The information about the underlying physical Siebel servers is abstracted from the Siebel clients. When the client requests a connection to a virtual server, the Siebel Adapter provides it. The Siebel Java Data Bean, through which a Siebel Java Connection connects to the Siebel server, needs to know the mapping between the virtual server and the underlying Siebel servers so that it can connect to the least loaded Siebel server and start the session. This mapping is provided through a configuration file required by the Siebel Java Data Bean, called siebel.properties, which must reside in the Integration Server_directory \packages\WmSiebelAdapter\resources directory. In this file you specify the virtual server and then provide the list of servers used in the workload for a particular Siebel application.
Then, when configuring an adapter connection for a Siebel Java Connection, you provide the virtual server name in place of the gateway server and leave the Siebel Server field empty.
For example, say there are two Siebel servers, one running on the host orpheus:2321 and the second on the host eurydice:2321. Both servers are logically grouped with the virtual server callcenter_srv. When the Siebel client requests a connection to the Siebel system named callcenter_srv, the Siebel Adapter reads the siebel.properties file to look for a virtual server entry named callcenter_srv, finds the list of physical servers represented by callcenter_srv, and connects to either orpheus:2321 or eurydice:2321.
To use Siebel Server load balancing with the adapter
1. Create the siebel.properties file:
a. Using a text editor, create a file named siebel.properties in the Integration Server_directory \packages\WmSiebelAdapter\resources directory.
b. Edit the file and add the following property:
siebel.conmgr.virtualhosts=virtualserver=1:server1:port,2:server2:port,.. .N:serverN:port;
where:
virtualserver is the name of the Siebel virtual server
server1,
server2,...
serverN are the names of the Siebel load balancing servers that are available to the adapter connection
port is the port number of the associated Siebel load balancing server
For example, to use the servers named orpheus and eurydice (both on port 2321) that are grouped with the virtual server named callcenter_srv, to handle the processing for the call center, use the following property:
siebel.conmgr.virtualhosts=callcenter_srv=1:orpheus:2321,2:eurydice:2321;
You can also specify multiple Siebel virtual servers as needed for your configuration. For example, in addition to the call center server shown above, you also want to use the servers named corvette, firebird, and gto that are grouped with the virtual server named sales_srv to handle the processing for sales requests. In this case, your property would look like this:
siebel.conmgr.virtualhosts=callcenter_srv=1:orpheus:2321,2:eurydice:2321;
sales_srv=1:corvette:2321,2:firebird:2321,3:gto:2321;
c. Save and close the file.
2. Restart the Integration Server.
Note:
Restarting the Integration Server causes the siebel.properties file to be added to the classpath, allowing the Siebel Java Data Bean to locate the file when you enable the adapter connection.
3. When configuring the adapter connections, ensure the following connection parameters are set as follows:
Select the Connection Type as
Siebel Java Connection.
Set the
Gateway Server parameter to be the Siebel virtual server name.
Leave the
Siebel Server parameter blank.