Getting started as a Product Administrator

As a Product Administrator, you plan and implement the installation of MainView Middleware Administrator (MVMA), including license requirements.

The Product Administrator also configures and administers projects. A project exists in MVMA as a container for different components, from users and groups to the middleware connections that users manage. The project is a flexible work space that lets you assign permissions (rights) to users and groups to work with those middleware connections that are IBM WebSphere MQ queue managers and TIBCO EMS servers.

For a full review of the Product Administrator's main tasks, see Key administrative tasks.

Product Administrators work in the Administration Console. While only Product Administrators can access the Administration Console, you can assign yourself user privileges and work as a user, managing specific connections within IBM WebSphere MQ and TIBCO EMS.



Key administrative tasks 

The Product Administrator has a number of main tasks to administer to ensure that MVMA functions correctly. This section describes those main tasks. 

Site planning

Site planning and preparation are essential aspects of the Administrator's task. Site planning includes assessing current enterprise infrastructure: hardware, network architecture, users, and managed middleware connections (IBM WebSphere MQ queue managers and TIBCO EMS servers). Each MVMA license comes with a product key that supports a specific number of IBM WebSphere MQ queue managers or TIBCO EMS servers. Exceeding this number requires acquisition of an additional license.

Users/Groups administration

Administering product users and groups is an important function in MVMA. A 'group' is a way to organize a collection of users related in purpose and function. Managing users and groups includes configuring them and associating them with the projects that link users to connections.

Project administration

This constitutes the core of administrative activities. Critical project planning and execution elements include:

Planning the Project

Note relevant users and groups that have logical connection to a new project. Communicate with potential and actual project members once the project is created. Define and associate middleware assets with the project.

Configuring the Project

Assign product users and groups; select IBM WebSphere MQ or TIBCO EMS assets to associate with the project. Set permissions on a user or group basis for the project. Configure event rules to apply to project entities (WebSphere MQ only). Project maintenance includes:

  • Adding, modifying and deleting users
  • Adding, modifying and deleting groups
  • Adding and deleting connections
  • Adding and associating filters to connections
  • Configuring project-associated event rules
  • Deleting existing projects

Configuring IBM WebSphere MQ events on a per project basis 

The Administrator sets event rules for project connections using rule types functionality. Multiple rule types exist, any of which can be configured for any project. 

Rule Type Definitions 

Multiple rule types can be configured, setting up the possibility of multiple concurrent events. Rule configurations trigger events when defined thresholds are crossed x times (as defined in the rule). Note you can also configure notification triggers for events. These are optional actions such as script execution and email notification on an active event incident.

Configuring filters for various application objects

Setting filters regulates user access to connections within IBM WebSphere MQ queue managers and TIBCO EMS servers.

Controlling general application settings

Settings include administrative controls for event monitoring and notification of users.

Pre-requisite knowledge for Product Administrators

General knowledge of the middleware administration environments helps with your administrative work:

  • Familiarity with the enterprise, its users, and installed applications.
  • Awareness of organizational security policies.
  • Ability to interact with the enterprise security team to implement the right security model for your installation.
  • Knowledge of the enterprise's internal projects, key personnel and projects. This helps to create realistic and useful MVMA projects.
Was this page helpful? Yes No Submitting... Thank you