The role of permissions

Permissions define effective user rights and can be seen as the glue between users and the connections that they manage. In MainView Middleware Administrator (MVMA), permissions are assigned to principals (users and groups) to facilitate their interaction with managed objects. Permissions are an inherent part of the MVMA security mechanism.

The Product Administrator sets permissions for users and groups for specific projects. Those permissions then pertain to all project connections, and specifically control how a user can interact with these connections and related objects. The permissions set within MVMA include specific individual rights.

These can be grouped into:

• Permissions that are designed to help users work with manageable middleware objects such as queues and channels. This applies to Inquire, Operator and Administrator permissions.
• Read, Write and Delete permissions that let users work specifically with messages.

The following list describes the available permissions:

• Inquire: Lets users see all accessible project objects and view their properties, as well as export objects; Inquire does not let a user change properties or browse messages.
• Read: Allows user to browse messages within the message manager.
• Write: Lets user modify and create messages in the message manager.
• Delete: Allows user to delete messages in the message manager.
• Operator: Enables full administrative permission on existing middleware objects, but without the ability to create new objects or delete existing objects.
• Administration: Lets the user create new objects and import, administer, and delete existing ones.