System Management Peripheral Instance
Overview
A Peripheral Instance contains components directly related to the Queue Manager of the Core Instance. When a Core Instance switches from backup to primary, the components of the Peripheral Instance connect to the new primary Core Instance automatically. Peripheral instances are displayed in alphabetical order in the System Management user interface.
Location
Peripheral instances may either display below the core instances in the System Management user interface, or to the right:
- A peripheral instance displays below the core instances if it does not find an active core instance to which to connect.
- As soon as an active core instance is detected, the peripheral instance starts up, connects to that core instance and displays to its right.
Name
Display the name of the peripheral instance and the server on which it is installed.
Components
Components are displayed for both core and peripheral instances. The icon displayed for each component identifies whether it is active, starting, stopped, or unknown.
| Status | Description |
|---|---|
| Active | Component is active |
| Starting | Component is initializing. |
| Stopped | Component is not active or not connected |
| Unknown |
Component status is unknown because its "heartbeat" was not detected. The component may actually be active (or not), but cannot be recognized due to a network issue or other problem. Refer to the System Management Troubleshooting topic in the System Management Maintenance Guide for more information. If a component has a stopped status and then its heartbeat is lost, the stopped icon will remain on the component. |
Non-controllable components are shaded gray and listed first (in alphabetical order). Controllable components are unshaded and listed second (in alphabetical order). Examples of components for a peripheral instance are:
- Launchpad
- GlobalCall IVR
- Message Bus
- QWatch Client
- Web Monitor
- Platform ToolKit
- VXML Interaction Server
- Outbound Contact Client
Web Monitor
The Web Monitor periodically polls the Platform ToolKit (and optionally VXML Interaction Server, any other web apps and web services) in order to report its status in System Management along with the other system components. The Web Monitors installed on the Management instances display in their corresponding Management Instance container. A Web Monitor installed outside of a Management instance displays in its own container as a peripheral instance.
The Platform ToolKit is automatically configured for monitoring when Callback is installed/upgraded. To change the configuration, or to add VXML Interaction Server monitoring, refer to the System Management Notification Server Configuration topic in the System Management Maintenance Guide.
