kb78: WebSphere registration errors

We have seen the following errors when registering the WebSphere application in Longitude:

• If the server is not running or the AdminClientSoapPort is wrong, you will see the following error message:

  Unable to reach a WebSphere Server on computer XXX.
  Ensure that the port number and device name are correct and that the server is running. If security is enabled on the server, also verify that the user name and password are correct.
  com.ibm.websphere.management.exception.ConnectorException: ADMC0053E: Could not create SOAP Connector to connect to host computer at port XXXX with SOAP Connector security enabled.

• If the Username or Password is incorrect, you will see the following error message:

  Unable to reach a WebSphere Server on computer XXX.
  Ensure that the port number and device name are correct and that the server is running. If security is enabled on the server, also verify that the user name and password are correct.
  javax.management.JMRuntimeException: ADMN0022E: Access denied for the getStatsObject operation on Perf MBean due to insufficient or empty credentials.

• If the Performance Monitoring Service is not running on the server, you will see the following error message:

  A general error occurred: Unable to monitor a WebSphere Server on computer COMPUTER.
  Ensure that the Performance Monitoring Service for your server is configured properly.

  To resolve this error, follow instruction #6 under Making WebSphere Monitorable.

• If the Performance Monitoring Service is running on the server, but the initial specification level is wrong, you will see the following error message:

  Missing stat
  A general error occurred: Missing stat
  No remedy is available.
  To resolve this error, follow instruction # 7 under Making WebSphere Monitorable.