IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Managing Server is started successfully but the connection has problem
The following content provides some solutions when Managing Server is started successfully but the connection has problem.
Managing Server is started successfully but Kernel is shown to be unreachable
The problem: After installing ITCAM for Application Diagnostics 7.1 or upgrading from ITCAM for WAS 6.1 and running am-start.sh, Managing Server is started successfully, but the Enterprise view shows no data. When viewing the diagnostic page, a message shows kernel can't be contacted. There is also a "No such file or directory" message during running am-start.sh.
The cause: This problem is caused by Winzip or zip utility of Windows. When extracting Managing Server installation image using Winzip or zip utility of Windows, the CR/LF(^M) was added automatically to all text files in Managing Server image.
The solution: For Managing Server installation on Windows, use WinRAR or utility 7-Zip to extract Managing Server image. Do not use Winzip.
Managing Server is installed successfully but the database cannot be connected
The problem: The installation of ITCAM for WebSphere Managing Server runs successfully, but the database cannot be connected.
Diagnosing the problem: You must still test the database connection even if the installation appears to succeed. The installation program creates a data source. The following procedure tests if the installation was successful.
In the case of an Oracle database, you have to perform the following steps in addition:
- In the WAS administrative console, expand the tree Security > JAAS Configuration > J2C Authentication Data.
- Click the WSAM J2C Authentication data entry.
- Click Apply.
To test the database connection:
- In the WAS administrative console, expand the tree Resources > JDBC Providers.
- Select the name of the JDBC provider.
- At the bottom of the page, select Data Sources.
- Place a checkmark in the box next to the correct data source.
- Click Test Connection to verify that ITCAM for WebSphere can connect successfully to the Octigate database.
The solution: If the database is connected successfully, a message will display at the top of the screen.
If the test fails, try verifying the following actions:
- Try to connect to the Octigate database manually using the DB2/Oracle command-line processor.
- Verify the user name, password, and database name. If using Oracle, make sure the URL has the following format:
jdbc:oracle:thin:@db_host:port:SIDFor example:
jdbc:oracle:thin:@perfdb-sun-so1.ibm.com:1521:octigate- Verify that the user which is used to start the WAS console has a DB2 or Oracle profile as part of its profile.
If the Managing Server uses an Oracle database and you see SQL syntax errors, check the ve.properties file to make sure that com.cyanea.octigate.database.ORACLE_8I is set to Y, and then restart the Application Monitor. For example:
com.cyanea.octigate.database.ORACLE_8I=Y
Parent topic:
Installation and configuration