Mule ESB WebsphereMQ connection with JMS connector works in Mule Design, but not standalone server

Question

I am new to Mule and followed this blog to create a "websphere-mq connector" through the jms connector. I am using the community edition.

In order to connect to the websphere mq server, I must run the application under a specific Windows username. Running the mule application in Mule Design under the specific username, I am able to connect and receive messages. However, I am unable to connect to the websphere mq server through the standalone application running on a windows server. I changed the user on the service that is running mule to the specific user but am unable to get authorization to the websphere mq server.

Any additional insight would be much appreciated.

Answer 1

I would suggest reviewing the "Getting going without turning off security" article for an introduction to MQ security. This might help get the MQ system correctly configured.

Answer 2

The stand alone application runs the Tanuki Software wrapper as the user assigned to the environment variable %USERNAME% in windows. Even though I updated the user in the Mule service to run as the approved user, the wrapper will take the environment variable.

To solve the problem, I updated the wrapper.conf file to include the following:

set.USERNAME=<approvedUsername>

the environment variable %USERNAME% is now set to the approved username, in which mule will allow the JMS connector to the authenticate with the correct username.