Goals To combine servers from at least two different machines into an enterprise Time 30 – 40 minutes
Instructions:
Practice Note: The following practices are intended to be performed on at least two machines. Team up with at least one partner to combine your machines into a single enterprise. Over the next few practices, you will first add a second Siebel Server to your enterprise, but it will not be running an Application Object Manager (AOM), hence it requires no additional configuration. You will then enable Siebel Sales on that server, which is a different AOM from the one (Siebel Call Center) on your original server. This requires editing eapps.cfg. You will finally enable Siebel Call Center on both servers. This requires enabling load balancing.
Note: It is possible to perform these practices on a single, powerful machine, with at least 3 GB of RAM. However, when configuring OUSrvr2 you will need to change the Siebel Connection Broker Port to 2322, and use that throughout the configuration. The practice is written for groups with multiple machines.
In this first practice, you will configure at least one additional Siebel Server in your enterprise, and enable the Workflow component group on all of the servers. By invoking multiple batch jobs in the enterprise, you can see how default load balancing and distribution occurs within the enterprise when Application Object Managers (AOMs) are not involved.
Note that because you are working in a team on multiple machines, some of these steps may be performed in parallel. To indicate which machine you should be working on, the steps in this practice are labeled: Siebel Gateway Name Server (GNS) steps are steps to be performed on the Siebel Gateway Name Server machine. Siebel Server (SS) steps are steps to be performed on each Siebel Server machine. Steps on different machines may be performed in parallel unless otherwise
indicated.
Oracle Internal & Or acle Academy Use Only
visible after logging in to Siebel Call Center multiple times in practice 11-3). If you encounter issues, restore the service to run as a local system service.
1. Select one machine to support the Siebel Gateway Name Server for the enterprise. Since you have already installed a complete enterprise on this machine, any additional machines will only require Siebel Servers.
Component Machine Name IP Address
Siebel Gateway Name Server Siebel Server 1
Siebel Server 2 Siebel Server 3 Siebel Server 4
2. SIEBEL GATEWAY NAME SERVER (GNS): Verify that OUSrvr is the only server left in your enterprise. Otherwise, load balancing may not work correctly when you add the additional server.
a. If necessary, start the Siebel Server [OUEnt_OUSrvr] Windows service.
b. Once the service has started completely, start the Siebel Call Center Web client:
i. Select Start > Programs > Internet Explorer ii. Enter Address: http://localhost/callcenter_enu.
iii. Enter:
User ID SADMIN
Password SADMIN
iv. Click the arrow.
c. Navigate to Administration - Server Configuration > Servers and confirm that OUSrvr is the only server left in the Enterprise. If it is not, refer to the next major step (for the Siebel Server machine) for instructions on how to remove a Siebel Server.
d. Log out of Siebel Call Center.
3. SIEBEL SERVER MACHINE(S) (SS): Remove the existing Siebel Servers. Recommended practice is to have only one server using a given server directory (for example,
D:\OUses\siebsrvr), hence you should remove OUSrvr before creating your new server. You must also avoid port conflicts (for example, port 2321, the Siebel Connection Broker port).
Finally, you cannot have two identically-named Siebel Servers in the same enterprise. The easiest way to avoid these conflicts is to remove all of the servers from this machine before proceeding.
a. If necessary, start the Siebel Gateway Name Server service.
b. Stop the Siebel Server [OUEnt_OUSrvr] service.
c. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration to invoke the Siebel Server Configuration Tool.
d. Select Configure Product in Live Mode and click Next.
e. Select Remove Existing Configuration and click Next.
Oracle Internal & Or acle Academy Use Only
Lesson 11: Configuring Multiple Servers within an Enterprise
f. Enter these parameters to remove the extra Siebel Server, clicking Next to proceed:
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.
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.
Use the Siebel Server machine name, as you are removing the existing server connected to the local 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 OUSrvr 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.
g. If necessary, repeat these steps to remove the Siebel Server named <machine name> as well.
h. As a verification step, bring up the Services window and select Action > Refresh. There should be no Siebel Server services on your Siebel Server machine.
4. SIEBEL SERVER MACHINE(S) (SS): Edit tnsnames.ora to point to the correct database.
Note that your current ODBC connection points to your local database; you need to modify that
Oracle Internal & Or acle Academy Use Only
tnsping siebeldb
and confirm that it returns OK.
Course Note: All of the text strings used in this course are contained in text files, allowing you to copy and paste the strings instead of having to type them manually.
The strings used for this practice are contained in
D:\labs\8.1_Install\Solutions\MultiServer\multiserverStrings.txt.
iv. Close the command prompt.
5. SIEBEL SERVER MACHINE(S) (SS):: Configure a Siebel Server to communicate with the GNS machine:
a. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration to invoke the Siebel Server Configuration Tool.
b. Select Configure Product in Live Mode and click Next.
c. Select Create New Configuration and click Next.
d. Click Next.
e. Enter the parameters below to create a new Siebel Server. Note that you are naming this server OUSrvr2, as the name must be distinct from the existing Siebel Servers in the
enterprise. Be careful to use the OTHER machine’s name, rather than your machine’s, for the GNS host name.
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 <GNS 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 OUSrvr2 A string of up to 12 characters including letters, numbers, and underscores that uniquely identify the Siebel Server.
Siebel Server
Description Siebel Server OUSrvr2 A description displayed in several of the administrative views.
Enable Component
Groups Sales 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.
Oracle Internal & Or acle Academy Use Only
Lesson 11: Configuring Multiple Servers within an Enterprise
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_OUSrvr2] Windows service.
h. Minimize the Services window.
6. ANY MACHINE; can be performed in parallel on multiple machines: Confirm that both Siebel Servers are visible in the enterprise, and that load balancing is automatically performed between the two servers.
a. In Internet Explorer, enter an address of http://<GNS Machine Name>/callcenter_enu.
b. Enter:
User ID SADMIN
Password SADMIN
c. Click the arrow.
d. Perform a synchronization to ensure that both servers’ components are available.
i. Navigate to Administration - Server Configuration > Enterprises > Synchronize.
ii. Click the Synchronize button in the middle of the view. The process should take 1-2 minutes.
e. Navigate to Administration - Server Management > Servers and confirm that both OUSrvr and OUSrvr2 are listed.
f. Click the Component Groups view tab.
Oracle Internal & Or acle Academy Use Only
g. For each Siebel Server, confirm that the Server State is Running and that the System Management component group is online for that server.
h. Click the Jobs view link. You will be running several Siebel Administrator Notification Component jobs to confirm that the jobs are distributed between the two Servers, both of which are running.
i. Create a new Siebel Administrator Notification Component job:
i. Click New.
ii. Click the Select button in the Component/Job field.
iii. Query for a short name starting with AdminNotify, select it, and click OK.
iv. Scroll down to the Job Parameters applet and click New.
v. Click the Select button in the Name field.
vi. Select the Notification Handler job parameter and click OK.
vii. Enter AdminEmailAlert as the value for this parameter.
viii. Step off the record to save it.
ix. Note that the record status is “Creating”.
j. Create four additional Siebel Administrator Notification Component jobs to create five total jobs. By default, the first four jobs will be sent to the first server, then the next four will be sent to the second server, and so forth. This configurable parameter assumes that it is more efficient for a single server to run multiple instances of the same job than it is to perform total round-robin distribution, where one job at a time is sent to each server:
i. Select the Siebel Administrator Notification Component job you just created.
ii. Select Menu > Copy Record from the applet-level menu.
iii. Repeat this step to create three more jobs, for five jobs in total.
k. Perform the following steps as quickly as possible:
i. Scroll up and click Submit Job.
ii. Select the next job with a status of “Creating” and click Submit job.
iii. Repeat until all 5 jobs have been submitted.
l. Click Query and then click Go to refresh the jobs list.
m. Examine the Execution Server column of the jobs. You should notice that the jobs got distributed betweeen the two servers without any additional configuration on your part.
Oracle Internal & Or acle Academy Use Only
Lesson 11: Configuring Multiple Servers within an Enterprise
7. Remain logged in to Siebel Call Center. In the next practice you will configure the Siebel Servers to support two different Application Object Managers.