SiteScope - Websphere configuration issue

  • KM03262571
  • 03-Oct-2018
  • 04-Jan-2019


SiteScope - Websphere configuration issue


After configuring WebSphere 8.5 on SiteScope 11.30 an error message appears.


1. Stop The SiteScope server.
2. Create a new “was” folder, to place the jar files from a WebSphere server on windows and the .jks files
(make sure to remove the previous .jar files from WebSphere on SunOS server )
the was folder the should contain:
DummyClientTrustFile.jks(You will need to use the ones that cames with your WAS server)
DummyClientKey File.jks(You will need to use the ones that cames with your WAS server)
the folder \java\lib\ext should contain:
3. Start the service.
4. Create the monitor and retrieve the counters.
In addition there are some considerations that need mention, one of them is that you can only configure SiteScope to monitor 1 specific version of WAS. For example if you are trying to configure a WAS 9.0, it will cause problems since the current *.jar and certs belongs to another version of WAS.
Regarding the below information:
“I have one more websphere server. I am facing an issue with that configuration. I am getting a message which states “ wrong certificates for DummyClientKeyFile.jks and DummyClientTrustFile.jks .
I checked with my Websphere Team. They are saying whatever .jks files that exists on that Websphere server are valid and there is nothing much they can do about it.”
You'll need to consider that the current DummyClientKeyFile.jks and DummyClientTrustFile.jks that you are using, belongs to an specific WAS instance, and you'll need to request obtain the DummyClientKeyFile.jks and DummyClientTrustFile.jks for the specific server with the inconvenient.
After that , is require to merge the certificates into a single KeyStore.
For example:
WAS 8.5 server A:
DummyClientKeyFile.jks and DummyClientTrustFile.jks
WAS 8.5 server B:
DummyClientKeyFile.jks and DummyClientTrustFile.jks
Copy the certs from each KeyStore and create a new files with the name: DummyClientKeyFile.jks and DummyClientTrustFile.jks
After that insert the certs into the corresponding KeyStore.
DummyClientKeyFile.jks A
DummyClientKeyFile.jks  B
DummyClientKeyFile.jks  C (A+B DummyClientKeyFile certificates)
DummyClientTrustFile.jks  A
DummyClientTrustFile.jks  B
DummyClientTrustFile .jks C (A+B DummyClientTrustFile certificates)
A great tool that you can try to use to handle the certificates is the following: