Resolution:
How to configure the Siebel adapter (/JDB Client) to connect multiple Siebel Server configured with Native load balance with Siebel 8.1.1?

Environment and Pre-requisites:
Siebel 8.1.1

•    Enterprise Server
•    Gateway Naming Server
•    Siebel Server
•    Database Server
•    Web server (The Siebel Web Server Extension (SWSE) is a plug-in for third-party Web servers which should be preinstalled as well(e.g. Windows IIS web server))

Description:
=========
Siebel Native load balancing has been available In Siebel since release 7.7 . At least two Siebel servers are required for load balancing purposes and each should have its respective gateway naming server. They can be located on different machines.

1). Siebel Server Side Configuration:
  
1.1). If  the SWSE logical profile (i.e., eapps.cfg and eapps_sia.cfg file) has not been created, first create them with the Siebel configuration wizard which is located in the bin folder of the gateway naming server installation directory (E:\sba81\gtwysrvr\BIN\ ssincfgw.exe).

For more details refer to:
  http://download.oracle.com/docs/cd/E14004_01/books/SiebInstWIN/SiebInstCOM_InstSWSE8.html#wp1986441

and

http://download.oracle.com/docs/cd/E14004_01/books/SiebInstUNIX/SiebInstCOM_InstSWSE9.html


By default, the directory of the SWSE logical profile is:

&ltGATEWAY_NAMING_SERVER_HOME>\ADMIN\Webserver.e.g. E:\sba81\gtwysrvr\ADMIN\Webserver

1.2). Generate the lbconfig.txt file and apply the SWSE logical profile with native load balancing.

a). On a Siebel Server, start the Server Manager at the enterprise level (do not use the /s option) e.g.,

E:\sba81\siebsrvr\BIN&gtsrvrmgr /g sia81 /e SBA_81 /u SADMIN /p SADMIN

(Refer to srvrmgr –help for more details).

Enter the command: generate lbconfig . The file is then created in the admin subdirectory of the Siebel Server installation directory.

b). Review the generated lbconfig.txt file to verify that virtual server definitions do not include any Siebel Servers that will not participate in load balancing.

Refer to the attached lbconfig.txt as reference, also refer to:
http://download.oracle.com/docs/cd/E14004_01/books/SystAdm/SystAdm_lbconfigfile.html for more details about the structure of lbconfig.txt


c). Manually edit the lbconfig.txt file to remove or comment out any AOMs that were disabled.
    
d). Configure the SWSE logical profile to be used with the web servers that will participate in Siebel native load balancing.

e). Copy the lbconfig.txt file into the SWSE logical profile folder.

f). Configure the installed SWSE by applying the SWSE logical profile.
    
g). Bring up the Siebel Configuration wizard under the installation directory of SWSE (e.g. E:\sba81\SWEApp\BIN\ ssincfgw.exe). Choose native load balancing and apply the SWSE logical profile by pointing to the SWSE logical profile folder which stores the lbconfig.txt, eapps.cfg and eapps_sia.cfg files.

h). Restart the Web server.
    
2). Siebel Client(Adapter) Side Configuration:
  
2.1). In Siebel.properties, add following property:

siebel.conmgr.virtualhosts=VirtualServer=1:192.168.69.35:2321,2:192.168.69.42:2321;

Please note that we should use comma to separate different Siebel servers.

where VirtualServer matches the VirtualServer parameter in the session manager rules in the file lbconfig.txt .

Note that there is a difference as the two Siebel server addresses are separated by a semi colon “;” in the session manager rules in lbconfig.txt. For example, in lbconfig,

VirtualServer=1:192.168.69.35:2321;2:192.168.69.42:2321;

2.2). Place the siebel.properties under the directory of the Siebel adapter lib or the Siebel adapter hotfix lib e.g. D:\tibco\adapter\adsbl\5.3\hotfix\lib .

2.3). Go to the designer under the design time connection tab, set the Host to the virtual host which you have defined in siebel.properties. e.g. Host: VirtualServer.

2.4). Start the adapter, JDB distributes the connection evenly among the load-ballanced Siebel servers.

Note,  Siebel Native load balancing  works in a round robin fashion, i.e., each JDB connection is being evenly distributed on each load balanced Siebel server. If the adapter connection pool size is 20 and the adapter is connecting towards the two Siebel severs being load balanced, the JDB will create 10 connections on each Siebel sever. The result can be seen in the Siebel call center by looking at the number of running tasks on each object manager (e.g., SCCObjMgr) in the respective load balanced Siebel sever.

How to configure the Siebel adapter (/JDB Client) to connect to multiple Siebel Serves configured with Native load balance with Siebel 8.1.1?