Goals To enable SWSE load balancing for your enterprise Time 25 – 30 minutes
Instructions:
In this practice, you will enable the Siebel Call Center AOM on both server machines, and then modify the SWSE configuration to support distributing the load between the two servers. The built-in load balancbuilt-ing is quite simple: The first session request goes to the first server, the second goes to the second, and so forth.
1. Enable the Siebel Call Center component group on the Siebel Server machine:
a. On any machine, in Siebel Call Center, navigate to Administration - Server Configuration >
Enterprises > Component Groups.
b. Query for the Siebel Call Center component group.
c. Enable the Siebel Call Center component group on OUSrvr2.
d. Restart the Siebel Server [OUEnt_OUSrvr2] service on the Siebel Server machine. Wait for the service to fully start before proceeding.
2. Generate the load balancing configuration file, lbconfig.txt. This file will contain load balancing information that will be used by the SWSE to distribute session requests among the Siebel Servers.
a. On the GNS machine, open a command prompt and navigate to the D:\OUses\siebsrvr\bin directory. Note that you can perform this step on any machine, but performing it on the machine hosting the Gateway Name Server allows you avoid having to copy the file between two machines.
i. Select Start > Run.
ii. Enter cmd and press OK.
iii. Enter the command
cd D:\OUses\siebsrvr\bin
b. Start the command-line server manger by entering the command:
srvrmgr.exe -g <GNS machine name> -e OUEnt -u SADMIN -p SADMIN
This connects to the Gateway Name Server and Enterprise as SADMIN/SADMIN, but does not connect to any server in particular.
Oracle Internal & Or acle Academy Use Only
Lesson 11: Configuring Multiple Servers within an Enterprise
c. At the srvrmgr> prompt, enter the command
generate lbconfig
This reads the configuration information from each Siebel Server and creates a file named lbconfig.txt in the ADMIN subdirectory of the Siebel Server directory.
d. Enter exit to exit the server manager.
e. Use Notepad to open D:\OUses\siebsrvr\admin\lbconfig.txt and examine the contents.
Confirm that both the Gateway Name Server and Siebel Server machine names are listed under VirtualServer. Recall that the first Siebel Server is co-located with the Gateway Name Server.
f. Close lbconfig.txt, not saving any changes.
3. Copy lbconfig.txt to the existing SWSE logical profile. None of the logical profile settings depend on load balancing:
a. On the Gateway Name Server machine, copy lbconfig.txt from D:\OUses\siebsrvr\admin to D:\OUses\gtwysrvr\admin\Webserver.
4. Reapply the SWSE logical profile:
a. On the Gateway Name Server machine, select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Web Server Extension Configuration.
b. Select Configure Product in Live Mode and click Next.
c. Select Apply an SWSE Logical Profile and click Next.
d. Select Siebel Native Load Balancing and click Next.
e. Browse for the logical profile at D:\OUses\gtwysrvr\admin\Webserver and click Open.
f. Click Next. Confirm the next few dialog boxes.
g. The profile should apply successfully.
h. Cancel out of the configuration tool.
5. Edit eapps.cfg to ensure it is using lbconfig.txt:
a. Use Notepad to open D:\OUWebServer\SWEApp\bin\eapps.cfg.
b. Under the [ConnMgmt] section, edit the VirtualHostsFile parameter to set it to
D:\OUWebServer\SWEApp\admin\lbconfig.txt. This should involve changing the .cfg
suffix to .txt.
Oracle Internal & Or acle Academy Use Only
d. Query for a component of SCCObjMgr_enu. Confirm that multiple sessions of Call Center are running on different machines, evenly distributed between the two machines. This shows that Siebel native load balancing is working.
Note: It may be necessary to re-expose the Siebel Server column to see how the sessions are distributed.
8. Verify that you can still log on to an AOM that is enabled on only one server:
a. In an instance of Internet Explorer, enter an address of http://<GNS machine name>/sales_enu and log in as SADMIN/SADMIN.
b. The fact that you were able to log in even though the Siebel Sales component group is enabled on only one of the Siebel Servers shows that load balancing properly handles different AOMs enabled on different Siebel Servers.
9. Log out of all applications and close all instances of Internet Explorer.
Restore your configurations for the next practice:
10. SIEBEL GATEWAY NAME SERVER (GNS): Re-apply the SWSE logical profile to eliminate load balancing:
a. On the Gateway Name Server machine, select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Web Server Extension Configuration.
b. Select Configure Product in Live Mode and click Next.
c. Select Apply an SWSE Logical Profile and click Next.
d. Select Single Siebel Server and click Next.
e. Enter your machine name and click Next.
f. Accept the default port number and click Next.
g. Browse for the logical profile at D:\OUses\gtwysrvr\admin\Webserver and click Open.
h. Complete the configuration.
i. The profile should apply successfully.
j. Cancel out of the configuration tool.
k. Confirm that you can log in to Siebel Call Center as SADMIN/SADMIN. Recall that the URL is http://localhost/callcenter_enu.
11. SIEBEL SERVER: Remove OUSrvr2:
a. Stop the Siebel Server [OUEnt_OUSrvr2] service. Wait until it is fully stopped before proceeding.
b. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration to invoke the Siebel Server Configuration Tool.
c. Select Configure Product in Live Mode and click Next.
d. Select Remove Existing Configuration and click Next.
e. Enter these parameters to remove the extra Siebel Server:
Parameter Value Purpose
Gateway Name Server Authentication User Account Name
SADMIN Used to log in to the gateway name server to collect Siebel Server information, and later to remove the server information from the gateway name server.
Oracle Internal & Or acle Academy Use Only
Lesson 11: Configuring Multiple Servers within an Enterprise
Gateway Name Server Authentication User Account Password - and confirm
SADMIN Used to log in to the gateway name server.
Gateway Name Server
Host Name <GNS machine name> Used to connect to the gateway name server.
Gateway Name Server
TCP/IP Port 2320 Port on which the gateway name server is listening for connections.
Siebel Enterprise Name OUEnt Enterprise containing the server to be removed.
Siebel Server Name OUSrvr2 The Siebel Server to remove.
Remove Siebel Server
Configuration Selected Remove the configuration from the gateway name server.
Remove Siebel Server
Windows Service Selected Remove the Windows service that implements the Siebel Server.
Remove Siebel Server
ODBC Data Source Not selected Do not remove the ODBC Data Source until you have removed all Siebel Servers from this machine, or you will not be able to re-run the Server Configuration Tool because the
connection to the Siebel Gateway Name Server will be lost.
Remove Selected
Siebel Server Selected Confirm that you wish to remove the Siebel Server.
12. SIEBEL SERVER: Edit tnsnames.ora to point to your local database:
a. Using Windows Explorer, navigate to D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN.
b. Right-click tnsnames.ora and select Send To > Notepad.
c. In the SIEBELDB section, change the HOST to <your machine name>.
d. Save and close tnsnames.ora.
e. Test the connection.
i. Select Start > Run.
ii. Enter cmd and click OK.
iii. Enter the command
tnsping siebeldb
Oracle Internal & Or acle Academy Use Only
e. Enter the parameters below to create a new Siebel Server.
Parameter Value Purpose
Gateway Name Server Authentication User Account Name
SADMIN Used to log in to the gateway name server to obtain configuration parameters.
Gateway Name Server Authentication User Account Password - and confirm
SADMIN Used to log in to the gateway name server.
Gateway Name Server
Host Name <machine name> Used to connect to the gateway name server.
Recall that this is the other person’s machine.
Gateway Name Server
TCP/IP Port 2320 Port on which the gateway name server listens for connections.
Siebel Enterprise Name OUEnt Used to connect to the Siebel Enterprise.
Siebel Server Name OUSrvr A string of up to 12 characters including letters, numbers, and underscores that uniquely identify the Siebel Server.
Siebel Server
Description Siebel Server OUSrvr A description displayed in several of the administrative views.
Enable Component
Groups Call Center Which component groups should be enabled on the Siebel Server when it first starts.
Siebel Connection
Broker Port 2321 Port on which the Siebel Server listens for connections.
Network TCP/IP Port for Synchronization
Manager
40400 Port used by Siebel Remote for synchronization.
Additional Tasks None Configure SSL, LDAP, or Exchange synchronization.
Register External Oracle
DB ODBC Driver Checked Used by the Siebel Connector for Oracle Applications to connect to back office Oracle databases.
Clustering Configuration Not clustered Cluster Siebel Servers to provide redundancy in case of server failure.
Start Siebel Server
service automatically? Unchecked For most deployments, the Siebel Server should start up when the system boots. To preserve system resources, do not do this on the classroom machine.
Start Siebel Server service at the end of profile execution?
Unchecked Whether or not to start the Siebel Server service as soon as the profile execution completes.
f. Return to the Services window and select Action > Refresh.
g. Start the Siebel Server [OUEnt_OUSrvr] Windows service.
h. Once the service has completely started, log in to Siebel Call Center as SADMIN/SADMIN to confirm your configuration. Recall that the URL is http://localhost/callcenter_enu.
Oracle Internal & Or acle Academy Use Only
Lesson 12: Multilingual Installations