MQSeries.net :: View topic - Connecting to the java agent with websphere security enabled

ptazbaz

Hello,

I have an urgent problem using the workflow api's when Websphere security is enabled. I have three physical servers in my environment.

My application code is running on server 1 and is hosted in Websphere 3.5. From server 1, I connect to the workflow java agent running on server 2 via jndi. The java agent running on server 2 is hosted in a Websphere 3.5 container and is setup to point to my workflow 3.3.2.3 instance running on server 3. Because of company policy, I was not allowed to install workflow on server 1, so the only way I can connect to the agent on server 2 is to use the fmcojapi.jar and fmcohcli.jar files along with two -d command line settings:

-Djava.naming.factory.initial=com.ibm.ejs.ns.jndi.CNInitialContextFactory
-Djava.naming.provider.url=iiop://server2_url:2222

With websphere security disabled, it works great. From server 1, I can connect to the workflow agent on server 2 and be able to make any api call I choose. With websphere security enabled on server 1, I cannot even start my application instance. From the looks of it, it appears that websphere security will not allow me to override these two -d parameters. But, without these two parameters, I get a null pointer exception when I try to connect to the java agent on server 2. If anyone has found a way to get around this, please let me know. Unfortunately, I have to use websphere security when this application rolls into production. Any input is much appreciated.

Regards,

Paul