Websphere Domain Configuration Troubleshooting

Community post

Shared by the Applicare community. It has not been re-checked against Applicare 10.0, so confirm the steps in your environment or contact Support.

The first configuration parameter to check is the Applicare agent root context, which must be /applicare_agent.

Then, check the custom server properties, boot classpath which should be something similar to C:\Applicare\applicare-aspects.jar.

To ensure you are using the correct information for domain configuration, you may first read the AboutThisProfile.txt file under <WAS_INSTALL_DIR>/profiles/<profile_name>/logs/.

If the default information has been changed, you can check the SOAP port on the administration console under Servers>Websphere Application Servers>servername>Ports.

Next, check your Websphere SystemOut.log. Look for this error:

The system cannot create a SOAP connector to connect to host
at port with SOAP connector security enabled.

This error means that either the trust/key store path or password is still wrong.

  • In WAS 6.1, the default password is the cell name.
  • In WAS 7, the default trust/key store password is WebAS.
  • A sample path for the trust store in Windows systems is the following:
C:\Program Files\IBM\WebSphere\AppServer1\profiles\AppSrv01\
config\cells\defaultNode02Cell\nodes\defaultNode02\trust.p12

If your trust/key store is more then 100 characters, you have to update your Applicare to v6.6.7 or later version. This a minor bug on earlier versions.

Restart the Websphere server and try to add it on Applicare.

If you followed the troubleshooting instructions and you still can't get it running, please contact the Arcturus support team for assistance.

Join the discussion

Comments, voting and following are kept by Zendesk and need a Help Center account. This button opens the original discussion there.

Opens Zendesk · needs internet and sign-in

Still stuck? Contact support