Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Service integration > Administer messaging engines
Display the runtime properties of a messaging engine
Display the runtime properties of a messaging engine by .
To be able to retrieve the status of messaging engines, 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.
With WAS v8 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh.
To display the runtime properties of a messaging engine, use the administrative console to complete the following steps.
Procedure
- In the navigation pane, click Service integration -> Buses .
- 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.
Messaging engines
Use HPEL to troubleshoot applications
Start a messaging engine
Stop a messaging engine
Messaging engine troubleshooting tips