WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Users and Citrix

Review the categories of user that might want to use with Citrix, and how to configure for concurrent multi-users.

Categories of user

The following categories of user exist:
Application developers
These users do not need to run mqsi commands, but must be placed in an access control list (ACL) before they can use a broker. Put these users only in the user list for publishing WebSphere Message Broker Toolkit.
Administrators
If you use Citrix to publish the WebSphere Message Broker Toolkit and the WebSphere Message Broker command console, put all administrators in the users lists for both applications. For information about the permissions that administrators need, see Security requirements for administrative tasks.

You can create Windows groups that correspond to the application developer and administrator categories, put the groups in the appropriate user lists, then allocate users to the relevant Windows group. Alternatively, you can give appropriate permissions directly to the user.

Make all users members of the Remote Desktop Users group, so that they can use Terminal Server.

Attention: Users who have access to the WebSphere Message Broker command console through Citrix can use the console to run other commands that are unrelated to the broker.

For information about the rights of groups such as mqm, mqbrkrs, and Administrators, see Security requirements for Windows systems.

Concurrent multi-users

Allowing multiple concurrent users to access WebSphere Message Broker by Citrix on a Windows server requires the same planning as allowing multiple concurrent users to access the WebSphere Message Broker on a Linux or UNIX server. For example:
  • All application developers should have their own execution group, so that they can deploy message flows and start and stop execution groups without conflicting with each other during development and testing. However, an exection group might be administered by more than one administrator. In these cases, administrators should coordinate their activities so that they do not conflict with each other. For example, when one administrator is starting an execution group, no one else should be trying to stop it.
  • All users should have their own workspace. The Windows system administrator should give each user the appropriate read and write permissions for the directory that corresponds to their workspace.
  • The WebSphere Message Broker Toolkit user can create the default configuration from the Samples; the product samples are deployed to the default configuration. Because you can create only one default configuration, only one user should use it at one time.

You can view information about samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit or the online information center. You can run samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:08


Concept topicConcept topic | Version 8.0.0.7 | ah60375_