Managing Ensemble Productions - InterSystems Documentation
Managing Ensemble Productions - InterSystems Documentation
Managing Ensemble Productions - InterSystems Documentation
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Management Tasks<br />
Monitor...<br />
Message queues<br />
Messages on a specific queue<br />
Messages in a Suspended state<br />
System jobs, in detail<br />
Sequence of Portal Commands<br />
Queues<br />
Queues, Contents<br />
Maintenance, Suspended Messages<br />
Jobs<br />
This book describe how to monitor an <strong>Ensemble</strong> production using the <strong>Ensemble</strong> Management Portal. Other types of monitoring<br />
are available, and other books describe them. For example:<br />
• To read about a command-line interface that you can use to retrieve basic status information from a running production<br />
via a Telnet connection or command-line script, see the section “TCP Status Service” in the “TCP Text Line Inbound<br />
Adapter” chapter of Using TCP Adapters with <strong>Ensemble</strong>.<br />
• Windows Management Instrumentation (WMI) is a feature of the Windows operating system that provides a standardized<br />
way of collecting management information. It allows users and programmers to access management information from<br />
the operating system and other applications in a variety of ways, including scripts, programming languages, and management<br />
tools and applications. WMI is the Microsoft implementation of the Web-Based Enterprise Management<br />
(WBEM) standard from the Distributed Management Task Force (DMTF).<br />
The <strong>InterSystems</strong> implementation of WMI signals an <strong>Ensemble</strong>_LogEvent each time an <strong>Ensemble</strong> business host posts<br />
an alert to the <strong>Ensemble</strong> Event Log. To set up WMI monitoring for <strong>InterSystems</strong> products, see “Monitoring Caché<br />
Using WMI” in the Caché Monitoring Guide.<br />
2.5 Purging Items<br />
The “purge” task includes other tasks that you might want to perform, such as archive, clean, delete, destroy, maintain,<br />
or remove. If you do not see the task you want in this section, try the section “Monitoring Items.”<br />
Purge...<br />
Any runtime data: event log, rule log, I/O log, messages, business<br />
process instances<br />
Event log entries only<br />
Business process instance data<br />
Older messages, while saving them to a separate archive for long<br />
term storage<br />
Production configuration data<br />
Sequence of Portal Commands<br />
Maintenance, Purge Management Data<br />
Event Log, Purge<br />
Business Processes, Instances, Purge<br />
Maintenance, Archive Manager<br />
<strong>Productions</strong>, Configure, Production<br />
2.6 Starting and Stopping Items<br />
The “start” task includes other tasks that you might want to perform, such as access, boot, execute, launch, login, reboot,<br />
run, send, or startup. The “stopping” task includes other tasks that you might want to perform, such as close, exit, halt,<br />
log out, or shut down. If you do not see the task you want in this section, try the Monitoring Items section.<br />
18 <strong>Managing</strong> <strong>Ensemble</strong> <strong>Productions</strong>