Deployment > Deploying Servers > Appendixes > Connectivity Troubleshooting
Connectivity Troubleshooting
This section describes common problems that you may encounter when connecting to Mercury Business Availability Center, and the solutions to these problems. For additional troubleshooting information, refer to the Mercury Business Availability Center knowledge base on the Mercury Customer Support Web site (http://support.mercury.com).
General connectivity problems related to ports
Verify that all ports required by Mercury Business Availability Center servers are not in use by other applications on the same machine. To do so, open a Command Prompt window, and run netstat (or use any utility that enables you to view port information). Search for the required ports.
For details on the ports required by Mercury Business Availability Center, and on how to modify them, see Port Management.
Tip: To troubleshoot port usage problems, use a utility that lists all ports in use and the application that is using them. An example of such a utility is Active Ports, a freeware program that maps ports to the owning application and shows which process has opened which port. Active Ports is available at www.ntutility.com.
Mercury Business Availability Center connectivity is down, but the Tomcat servlet engine and JBoss application server appear to be working
Connectivity problems include the inability to log in to Mercury Business Availability Center, and the inability of Business Process Monitor to connect to the Core Server.
Possible Cause:
This can happen if the TopazInfra.ini file is empty or corrupt.
To verify that this is the problem:
- In the browser, type http://<Centers Server>:8080/web-console to connect to the JBoss Management Console.
- Under System > JMX MBeans > Topaz, select Topaz:service=Connection Pool Information.
- Click the showConfigurationSummary Invoke button toward the bottom of the page. If the Operation Result page is blank, the TopazInfra.ini file is empty or corrupt.
Solution:
To solve this problem, rerun the set management database utility and either reconnect to your existing management database or define a new management database. If you did not discover a problem with the TopazInfra.ini file, contact Mercury Customer Support.
Inability to log in to Mercury Business Availability Center, and JBoss server fails to initialize
Running the Verify tool returns errors that indicate failure to connect to the TMC, DataEngine, and ChartEngine due to a JNDI error.
Verify that the database server on which the management database is located is up and running.
Browser unable to reach Mercury Business Availability Center or the .jsp source code appears in the browser window
For example, you get a message indicating that the page does not exist.
Solution 1:
Ensure that the Tomcat servlet engine is running and that port 8009 is not in use by another application. Perform the activities below on the Mercury Business Availability Center server machine (or Centers Server if installed separately).
To verify Tomcat servlet engine functionality:
- Verify whether JBoss is running by opening the \\<Mercury Business Availability Center root directory>\MercuryAM\log\jboss_boot.log file and looking for the following line: long-date [main] (ServerImpl.java:395) INFO - JBoss (MX MicroKernel) [3.2.2 (build: CVSTag=JBoss_3_2_2 date=date)] Started in
start-time.
where:
long-date - represents the date in ms; for example: 2004-09-05 12:03:28,359
date - represents the date in hours; for example: 200310182216
start-date - represents JBoss startup duration; for example: 3m:34s:781ms- Verify whether the Mercury Business Availability Center service is installed and running.
- If port 8009 is in use by another application:
Solution 2:
Ensure that the Jakarta filter path is correct. The path might be incorrect, for example, if you uninstall Mercury Business Availability Center servers and then reinstall to a different directory. In this case, the Jakarta filter path is not updated, causing redirection problems.
To update the Jakarta filter path:
- Open the IIS Internet Services Manager.
- Right-click the machine name in the tree and select Properties.
- With WWW Service displayed in the Master Properties list, click Edit.
- Select the ISAPI Filters tab.
- Select jakartaFilter and click Edit.
- In the Filter Properties box, update the path to point to the drive and directory of the current Mercury Business Availability Center installation.
- Apply your changes, and quit the Internet Services Manager.
- Restart the IIS service.
Mercury Business Availability Center is sitting behind a proxy and neither the server name nor the IP address is recognized by the proxy
The problem occurs for both Microsoft IIS and Apache Web servers.
Possible Cause:
The Web server redirects the browser page to a URL that replaces the server name or the IP address entered by the user.
Solution:
Add the Mercury Business Availability Center server name to the NT or Windows 2000 hosts file on the proxy server machine. This file is located in WINNT\system32\drivers\etc.
Business Process Monitor is unable to connect via the Internet to the Core Server installed on an Apache Web server
Possible Cause:
The Business Process Monitor machine is unable to resolve the Core Server name correctly.
Solution:
If this is the cause, you can solve this problem in one of the following ways:
| Copyright 2006 Mercury Interactive Corporation |