we are trying to connect a cloud-based system vie JMS to webmethods. According to the “webMethods Broker Messaging Programmer’s Guide”, we need to define a property “com.webmethods.jms.naming.truststore” to point to a truststore on disk.
Now, we don’t have access to the filesystem, thus we do not have this option. The service is maintaining its own keystore and it provides a UI where we could upload certificates to.
And we could get a reference to an according “java.security.KeyStore” object in code…
… but, the webmethods client seems to accept only filesystem-paths in that property. And the connection fails, if that property is not set. The client fails with “[BRM.10.5072] JMS: SSL truststore “bkServerTrustStore.jks”: not found”. “bkServerTrustStore.jks” seems to be a default.
So actually we are looking for a way to either
a) pass to the JNDI context the Keystore object we derive in the code or
b) have the webmethods client use the JDKs truststore.
c) something I haven’t thought of?
I have been told, that the server is some 9.2 version and it seems that the client is an 8.something version.
You might have guessed, that we are working on a migration of a pretty old codebase. And if the answer is, that we need to upgrade the client that could be an option (though I a looking at the documentation of version 9.6).
This is my first time I am working with webmethods and JMS… so bare with me if I am not using the correct terminology (or get things completely wrong )