Bookshelf Home | Contents | Index | Search | PDF

Siebel Server Installation Guide for UNIX > Implementing Load-Balancing with Central Dispatch > Configuring the Central Dispatch Site >

Using Dispatch Manager to Configure Your Site

---

To finish configuring your Central Dispatch site, complete the following procedure.

To configure a Central Dispatch site

Verify that the Enterprise VIP is not assigned to any machine or another Siebel configuration by using the ping command.
From a Siebel Server on which Central Dispatch was installed, open a shell.
Navigate to /resonate/bin and enter:

./dispatch-manager

In the Dispatch Manager Welcome dialog box, leave the Connect to Node field blank if this is the initial configuration of Central Dispatch.

Otherwise, enter the static IP address or the host name of the primary node, then enter the Resonate manager password to log in to Central Dispatch.

In the Site View dialog box, click Site Setup.
On the System Nodes tab:
Add the static IP address of each machine that will support a Siebel Server, Central Dispatch Primary Scheduler, or Central Dispatch Backup Scheduler. (A place for these IP addresses has been reserved in Deployment Planning Worksheets.)

NOTE:  Hostnames can be used, but they must map one-to-one to the static IP address that Resonate uses. It is recommended that you enter the IP address instead of the host to avoid any conflicts.

Verify that the check boxes for Server Enable and Server Auto-reenable are checked for all services except the dedicated schedulers.
After entering the first primary IP address, click Add.
After entering information for the next node, click Add and Apply Changes.

NOTE:  Type the static IP address, not the name of the machine to which it is assigned in the Node Name field. The use of host names can cause inconsistencies in routing, depending on the operation of your DNS servers.

On the VIPs tab, add the IP address to the site:
In the VIP field, type the virtual IP address.
In the Primary Scheduler list box, select the static IP address of the server that will serve as the primary Scheduler node.
In the Backup Scheduler list box, select the static IP address of a second machine to serve as the Backup Scheduler node.
To add the IP, click Add.
On the Licensing tab, type the license key in the New Key field and select Set New Key.

The license key is stored in the license.txt file in the Resonate subdirectory of the AIX|Solaris|HP-UX Server Ancillary Programs (CD 2 of 2) CD-ROM.

On the Policies tab:
Select Resource-based in the Scheduling Policy drop-down list.

You must select resource-based scheduling to take advantage of Central Dispatch's load-balancing features with Siebel eBusiness Applications.

For the load-balancing policy, it is recommended that you select CPU Load and Connections (Enhanced).
On the Operation tab:
Click the advanced options button.
Set Agent Heartbeat Interval to 1 second.
Set Heartbeat Until down to 100. Setting this parameter to one hundred means that it will take 100 seconds for a scheduler or Siebel Server to failover. This value can be adjusted based on your requirements for failover time, but keep in mind that a small value (<10) may result in false failover of Siebel Servers.
Click Start Site.
Type the password for the Resonate Administrative Mode account.
Verify that the Central Dispatch site has started by using either of the following methods:
Click the Operations tab. System Started should be visible in the bottom message area.
Click the Site View tab. Your system nodes appear green if the site has been started, and red if Central Dispatch has not started successfully.

Scheduler nodes should appear green unless you did not check the Server Enable and Server Auto-reenable check boxes on the System Nodes tab. If you failed to check these boxes, the scheduler nodes appear blue.

If the other nodes are red, verify that you entered a valid IP address for those nodes. If the IP address was correct, verify that your Siebel Gateway Name Server or Siebel Server was not started. They cannot be in operation when you install and configure Central Dispatch.

Check the messages tab. If there are messages with a status of Error, investigate the cause.

Bookshelf Home | Contents | Index | Search | PDF