Last updated on DECEMBER 20, 2016
Applies to:Oracle Documaker - Version 11.4 and later
Information in this document applies to any platform.
As part of migrating our java component to new servers (publishing /documaker remains unchanged, wipedit plugin remains unchanged), we are having issues with our new MQ configuration on the java side (it is fine on the publishing end).
In our current set-up, our MQ is on the same lpar as websphere; using bindings mode.
(a) The java code puts a message on the request queue; local to the publishing server (set-up as a remote/alias queue on the WebSphere MQ node).
(b) After publishing processed the message is sent, it puts a message back on the response queue, local to the WebSphere LPAR.
All works well.
In our new world, MQ is centralized on what we are calling a MQ Cluster. As a result, MQ is no longer installed on the WebSphere lpar, the java code uses a client channel to connect to the MQ Cluster.
(a) The java code puts a message on the request queue; local to the publishing server (set-up as a remote/alias queue on the MQ Cluster).
(b) After publishing processed the message is sent, it puts a message back on the response queue, local to the MQ Cluster.
To meet our security standards, we need to pass a different username/password to the mq cluster. What is currently being passed is the user running WebSphere.
In our DocuMaker implementation, we are using documaker mq classes; and are not seeing a way to add these credentials. We have tried to add them to the getProperties method.
Can you provide us a way to pass these credentials? Is there a way to get a handle on the MQConnection Factory object?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms