Displaying the runtime properties of a messaging engine
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: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 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.