Display the runtime properties of a messaging engine by
using the administrative console.
Before you begin
To be able to retrieve the status of messaging engines,
you must be logged into the administrative console with at least monitor
authority. If you do not have this authority, the messaging engine
status is displayed as "Unavailable", even if the messaging engine
has started. Also, if you are not logged in with the authority needed
to retrieve the status of messaging engines, a SECJ0305I error message
is logged in the server
SystemOut.log file.
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.
About this task
To display the runtime properties of a messaging engine,
use the administrative console to complete the following steps.
Procedure
- In the navigation pane, click .
- In the content pane, click the name of the bus to which
your messaging engine belongs.
- In the content pane, under Topology,
click Messaging engines. A
list of messaging engines is displayed.
- Click the messaging engine name.
- Click the Runtime tab. The status of the messaging engine, that is, whether it
is currently started or stopped is displayed.