Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Server Installation Guide for Microsoft Windows > Implementing Load-Balancing with Central Dispatch >
Troubleshooting Load-Balancing with Central Dispatch
This troubleshooting section addresses some of the common Siebel-specific issues with Central Dispatch. For general information on troubleshooting Central Dispatch, see the Resonate Web site at http://www.resonate.com.
If you encounter problems installing or configuring Central Dispatch that you cannot resolve using these instructions, contact Siebel Technical Support. Do not contact Resonate Technical Support.
Use the task flow in Figure 6 when troubleshooting Central Dispatch with Siebel eBusiness Applications.
Task 1: Confirm Problem is Central Dispatch Related
To confirm whether the problem is a Central Dispatch issue, try connecting directly to the Siebel Server without using Central Dispatch. To do this, modify the following connect string:
siebel[.
protocol
][.encryption
][.
compression
]
://VIP:siebel_port
/
Enterprise
/
Component
Replace it with the following:
siebel[.
protocol
][.
encryption
][.
compression
]://Gateway
:siebel_port/Enterprise/Component/Siebel_Server
To test the connection
- Shut down all Web servers.
- Shut down all but one Siebel Server.
- Change the connect string above in one of the virtual directories in the eapps.cfg file.
- Restart one Web server using the modified file.
- Try connecting to the Siebel Server.
If you can connect using the new connect string but cannot connect using the load-balanced connect string, then the problem is related to Central Dispatch.
Task 2: Check Central Dispatch Availability
Use the Dispatch Manager Site View tab to view the status of each server. If any server is red, investigate the cause. If all servers appear as green, select the Messages lower tab for messages labeled critical and investigate the cause.
You can also run the
netstat -anP tcp
command to list all active TCP sockets. There should be some sockets using the VIP as the Local Address.Task 3: Verify Configuration
Before proceeding with troubleshooting, verify the following:
- Verify that the EnterpriseVIP is set correctly on the Name Server by running List
EntParameter EnterpriseVIP
command through the Siebel Server Manager.- If necessary, reset the
ResonatePassword
through Siebel Server Manager by running theEntParameter ResonatePassword;
for example,EntParameter ResonatePassword= "newpassword".)
- Verify that the connect strings are set correctly on the Web server. In the
eapps.cfg
file on each Web server, your "load balance component" connect strings should have the VIP (or corresponding hostname) and Vport (2320 by default), and only specify Enterprise name and component name. For example:
siebel.tcp.none.zlib://VIP:2320/Enterprise_name/OM_component_name
- Perform the installation verification tasks listed in the Resonate Central Dispatch and Resonate Commander Installation Guide, available on the Siebel eBusiness Third-Party Bookshelf.
Task 4: Check Scheduling Rule Registration
Use Dispatch Manager to verify that the expected rules exist and that there are no extra or duplicate rules. If you do not find all of the expected rules, examine the log files for the applicable Siebel components for errors running CDAction.
Task 5: Check Network Connectivity
Check client-to-scheduler, scheduler-to-server, and server-to-client connectivity.
TIP: If you use the command
IPCONFIG /ALL t
o display the Windows IP configuration, make sure that Resonate Agent is at the top of the list.Task 6: Check IP Routing Enabled Setting
Check the
IP Routing Enabled
setting in theIPCONFIG /ALL
display. If theIP Routing Enabled
is set toNo
, Resonate will not work. For details on how to set theIP Routing Enabled
, refer to your Windows documentation.NOTE: For more information on performing these tasks, see TechNote 316, posted on SupportWeb.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Server Installation Guide for Microsoft Windows Published: 25 June 2003 |