Use WebSphere MQ Remotely

 

If you are connecting to a Windows machine using either Terminal Services or a Remote Desktop Connection and you have problems creating, starting or deleting a queue manager this might be because of the introduction of a new user right, "Create global objects".

The "Create global objects" user right limits the users authorized to create objects in the global namespace. In order for an application to create a global object, it must either be running in the global namespace, or the user under which the application is running must have the "Create global objects" user right applied to it.

When you connect remotely to a Windows machine using either Terminal Services or Remote Desktop Connection, applications run in their own local namespace. If you attempt to create or delete a queue manager using WebSphere MQ Explorer or the crtmqm or dltmqm command, or to start a queue manager using the strmqm command, it will result in an authorization failure. This will create a WebSphere MQ FDC with Probe ID XY132002.

Starting a queue manager using the WebSphere MQ Explorer, or using the amqmdain qmgr start command will work correctly because these commands do not directly start the queue manager. Instead the commands send the request to start the queue manager to a separate process running in the global namespace.

If we need to perform any of these operations on a queue manager when connected remotely to a Windows machine, have the "Create global objects" user right. For information on how to assign a user this right, see your operating system documentation.

Administrators have the "Create global objects" user right by default, so if you are an administrator you will be able to create and start queue managers when connected remotely without altering your user rights.

 

Parent topic:

Configuring a WebSphere MQ Server