BEA Logo BEA MessageQ Release 5.0

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy


   MessageQ Doc Home   |   Introduction to Message Queuing   |   Previous Topic   |   Next Topic   |   Contents   

Managing the BEA MessageQ Environment


After you develop your BEA MessageQ programs and deploy your distributed application into the production environment, you need to monitor and tune your system's performance and occasionally troubleshoot BEA MessageQ problems.

To successfully manage your distributed BEA MessageQ applications, you need to:

Understanding the BEA MessageQ Environment

To efficiently manage and troubleshoot a distributed BEA MessageQ application, it is important to be able to visualize the components of the BEA MessageQ environment. Figure 4-1 shows how Application A running in Group 1 can be configured to exchange messages with Application B running in Group 2 on the same message queuing bus though the systems do not run the same operating system. Communication between the two groups is enabled using the network communications link between both systems and a BEA MessageQ cross-group link.

Figure 4-1 The BEA MessageQ Environment

This typical configuration of the BEA MessageQ environment consists of:

Anatomy of a Message Queuing Group

Message queuing groups are designed to provide centralized resources for a group of queues running on a host system. As shown in Figure 4-2, each message queuing group may run a number of BEA MessageQ servers to service the needs of the temporary and permanent queues to which applications are attached.

Figure 4-2 BEA MessageQ Servers

Depending upon the services enabled in the group initialization file, a message queuing group may run the following processes:

Starting and Stopping Groups, Queues, Links and the CLS

As options of both its character-cell and GUI-based Monitor utility, BEA MessageQ enables users to interactively:

Monitoring System Performance

The BEA MessageQ Monitor utility helps developers observe the BEA MessageQ environment on local and remote nodes. Developers and system managers can use the summary and detailed display of information by the Monitor utility to tune the BEA MessageQ system configuration.

To monitor or control your BEA MessageQ groups or buses, you can invoke either the Motif-based Monitor Utility or the character-cell Monitor utility. Either interface can be used to perform the following sets of functions:

Error Logging and Recovery

BEA MessageQ has an error logging mechanism to display and capture informational, warning, and error messages that can occur during processing. The messages display a description of the condition to help developers gather more information about failure conditions within a message queuing group.

On UNIX and Windows NT systems the BEA MessageQ an error log file is created when the group is started using the appropriate switch on the dmqstartup command line. Error logs can be created for each message queuing group. On OpenVMS systems, an error log can be created at group startup or the System Manager utility can be used to redirect output to several error log files.

Listing 4-1 shows the kind of information logged for each BEA MessageQ event on a UNIX or a Windows NT system: