Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see MainView Middleware Monitor 9.2.

Working with the Event Journal

This section describes the Event Journal feature, and includes:

While it is possible to create events based on transient topics (see Using-the-trigger-toolbar), events generated based on transient topics are not added to the Event Journal. Transient topics are used for publishing the attributes of highly dynamic objects such as MQ channel instances, MQ subscriptions,  MQ event messages, and BTM transaction data. They are also used for MQ Listeners and MQ Service Definitions. Thus, while it is possible to define an event on the status of one MQ SVRCONN Channel Instance being stopped or the writing of an MQ Authorization Event, there will be no record of these events in the Event Journal. 

When in doubt, examine the explorer (left hand) pane of the Operations tab. If monitored objects of a type do not appear in that tree, then they are transient. 

For example, you might see a “WebSphere MQ Queue Managers” type folder in the tree and your queue managers beneath that. Similarly, beneath a specific queue you may see a “WebSphere MQ Local Queues” folder beneath that. Neither of these types are transient. However, you will not see a type folder for “WebSphere MQ Listeners” because they are a transient type.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*