IBM Support

Collecting Data: WebSphere Discovery

Troubleshooting


Problem

If you encounter problems discovering WebSphere servers, the following information will be useful in assisting TADDM support in diagnosing your problem.

Symptom

WebSphere server won't discover without errors.

Resolving The Problem

In order to diagnose why TADDM is having difficulties discovering WebSphere, you should gather and send the following information to support.

1) The following information describing the problem and the environment

  • The error message
  • The time of the error
  • A screenshot showing the problem
  • The IP of the target WebSphere server
  • The SOAP port (if you know it)
  • Whether any anchor servers are configured in the environment and whether the discovery goes through them.
  • The TADDM version
  • The WebSphere Server version

2) Logs

In order to gather the appropriate logs, please ensure that TADDM logging is in DEBUG and that split sensor logging is enabled. You can confirm or change these settings in dist/etc/collation.properties:


com.collation.log.level=DEBUG
com.collation.discover.engine.SplitSensorLog=true
If the SplitSensorLog setting is changed you will need to restart TADDM.
If either setting is changed, please reproduce before gathering logs.

Then please gather up the following logs.
$COLLATION_HOME/dist/log/*
$COLLATION_HOME/dist/log/services/*
$COLLATION_HOME/dist/log/sensors/*/*

If an anchor server is involved, please also gather the logs files in the coll7.2/log directory in the anchor service account's home directory on the anchor server.

On UNIX systems we recommend using "tar -cvfz" to product a tar + zipped collection of logs. A zip file is sufficient for Windows. Please name the file with the full PMR number (i.e. 21014,082,000.tar.gz) and either upload them via the support website, email them to [email protected] (make sure the full pmr # is in the subject line) or ftp to ftp.ecurep.ibm.com /toibm/tivoli.

3) Tests
a) Most WAS discovery problem stem from difficulty in connecting to the WebSphere server from TADDM or the anchor. There is a script to test this connection outside of a discovery called testwasconnection. In 7.1.2 you will find this in $COLLATION_HOME/dist/support/bin. In 7.2 it's in $COLLATION_HOME/dist/bin. If you will run this script and provide the results it can help us determine if the problem is with the configuration, the network, or the ssl security keys.

Usage Info -
host version
host version port connectorType
host version port connectorType user password trust-store trust-passphrase
key-store key-passphrase
Valid versions include, 5.x, 6.0, and 6.1
trust-store and key-store must use full path

Examples -
./testwasconnection.sh yourhost.com 5.x
./testwasconnection.sh yourhost.com 6.0 8880 SOAP
./testwasconnection.sh yourhost.com 6.1 8880 SOAP wasadmin foobar
/opt/WebSphere/AppServer/profiles/default/etc/DummyClientTrustFile.jks WebAS
/opt/WebSphere/AppServer/profiles/default/etc/DummyClientKeyFile.jks WebAS

The script can be copied to an anchor and used there, but will not automatically navigate anchors in it's testing.

If the testwasconnection script works, but your discovery does not, you may want to review your access list credentials before opening a PMR.

b) If the above test leads you to suspect the network, the following simple command line test from the TADDM server or anchor can assist us in determining the presence of a firewall or a non-listening process on the target:
telnet IP_of_yourhost SOAP_port
i.e. telnet 122.133.24.16 8880
A hang in the response indicates that a firewall is blocking the port.

c) If you suspect that SSL certificates are *not* in use in your environment, the easiest way to verify this is to connect to the WebSphere Administrator Console. If the URL in the web browser when you connect to the console starts with "https" then you *are* using SSL certificates and you *should* ensure that you have certificates/keyfiles/trustfiles in the access list.

d) To verify that SOAP is enabled on the WebSphere server and determine what port SOAP is using, review the serverindex.xml file from the WebSphere server. It will have a stanza describing the SOAP port the WebSphere server is configured to use.

[{"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.2;7.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

TADDM

Document Information

Modified date:
17 June 2018

UID

swg21425996