Cerner's Olympus Whitepaper - Cerner Corporation

Cerner’s Olympus Whitepaper
Version 3.1.0
February 2011
Cerner Corporation 2800 Rockcreek Parkway, Kansas City, MO 64117 866.221.8877 www.cerner.com

Table of Contents
Introduction ........................................................................................................................................................... 3
Benefits ................................................................................................................................................................... 3
Architecture ........................................................................................................................................................... 5
Licensing ................................................................................................................................................................. 6
Implementation ...................................................................................................................................................... 6
Minimum Hardware Requirements .................................................................................................................................... 6
Functionality .......................................................................................................................................................... 8
Olympus Command & Control ........................................................................................................................................... 8
Core Millennium Services .......................................................................................................................................... 8
Millennium Interface Services ................................................................................................................................. 10
Operating System Services ...................................................................................................................................... 10
Olympus Security ..................................................................................................................................................... 11
Olympus Alerting .............................................................................................................................................................. 12
Auditing Alerting ..................................................................................................................................................... 12
Backend Server Alerting .......................................................................................................................................... 12
Code Cache Alerting ................................................................................................................................................ 12
Interface Alerting .................................................................................................................................................... 12
MQ Series Alerting .................................................................................................................................................. 13
Operating System Alerting ...................................................................................................................................... 13
Operations Alerting ................................................................................................................................................. 13
RRD Alerting ............................................................................................................................................................ 14
RTMS Alerting .......................................................................................................................................................... 14
Olympus Recovery Action Scripts ..................................................................................................................................... 14
Olympus Dashboard ......................................................................................................................................................... 14
Olympus Smart Modules .................................................................................................................................................. 15
Olympus Smart Module Alerting ...................................................................................................................................... 16
724Access Smart Module Alerting .......................................................................................................................... 16
Chart Server Smart Module Alerting ....................................................................................................................... 16
CPDI Smart Module Alerting ................................................................................................................................... 16
High Availability Smart Module Alerting ................................................................................................................. 17
Multum Smart Module Alerting .............................................................................................................................. 17
Oracle Smart Module Alerting ................................................................................................................................. 17
WebSphere Smart Module Alerting ........................................................................................................................ 18
2

Introduction
Management and monitoring of a Cerner Millennium ® environment can be challenging. It requires a combination of tools, scripts and 3 rd party
solutions. Recognizing the need for a single console, management architecture, Cerner developed the Olympus solution. The purpose of this
document is to provide technical information about the Olympus solution, including: architecture, functionality and a solution roadmap.
Cerner’s Olympus solution provides a single console to manage a Cerner Millennium environment, allowing the management of systems across all
architectural platforms from one location. Olympus unifies the many tool sets previously required to administer Cerner Millennium, thereby
improving manageability and access to critical sub-systems within Cerner Millennium.
Olympus was designed with three main objectives:
■ Command and Control: Provides the ability to effectively manage Cerner Millennium from a single console. Examples of Command and
Control include managing application servers, modifying the Millennium Registry, managing print queues, and managing chart requests. A full
functionality list is detailed later in this document. Olympus Command and Control streamlines Cerner Millennium maintenance by providing
troubleshooting and issue resolution toolsets for multiple platforms in a unified console.
■ Monitoring: The Olympus Thresholding & Alerting Engine provides the ability to monitor environments and generate events (e-mails and
pages) when thresholds are crossed. Olympus can set thresholds against any captured data point. The Thresholding & Alerting Engine
facilitates proactive monitoring of a Cerner Millennium environment.
■ Performance Analysis: Using the historical data captured by Olympus in combination with RTMS data, Olympus allows users to analyze system
and application performance.
Benefits
The Olympus solution unifies more than 40 toolsets previously required to manage Cerner Millennium, thereby greatly reducing the time and effort
required to manage an environment. For example, cycling all instances of a server across a domain can take several command-line entries, but
with Olympus this can be accomplished in a few mouse clicks. Additional benefits include:
■ A single console for all Cerner Millennium architectural platforms (AIX, VMS, HP-UX, Linux, Windows)
■ Streamlining of the time and effort required to manage Cerner Millennium
■ Reduction of the number of backend user accounts previously required to manage Cerner Millennium
■ Increased security with custom roles to fit your environment and grant permissions on user basis
■ Auditable actions of changes made to a system, when they were made, and by whom.
Architecture
Overview
The Olympus architecture was designed to separate systems management from Cerner Millennium. Olympus operates independently from Cerner
Millennium, allowing users to manage Millennium even when components of Millennium are not available. Below are the technologies and
components that comprise the Olympus architecture.
JMX
The foundation of the Olympus architecture is built on the industry standard JMX (Java Management Extensions). JMX technology manages
resources by Java objects called MBeans (management beans). The MBeans are registered to the MBean Server (JMX Server). The JMX Server
acts as management agent and can run on java-enabled platforms. For additional information on JMX, visit
http://java.sun.com/j2se/1.5.0/docs/guide/jmx.
Olympus Console
The Olympus console is the user interface built on Java Eclipse technology. The console provides a centralized interface for Cerner Millennium
management. The Olympus console comes out of the box with four default views that allow users to maneuver through the console in the way
that’s most convenient for the task at hand. The default views are:
■ Server View: Displays by node name
■ Profile View: Displays by profile/function (i.e. Citrix, backend, etc.)
■ Service View: Displays by the service they offer
■ Domain View: Displays by Cerner Millennium domain
In addition to the default view users can create custom views to meet their specific needs. These custom views can then be saved as
perspectives to be displayed again at any time. The Olympus console allows users to “drag and drop” windows and arrange them in a manner
that is most convenient to the user (all user settings and preferences are saved upon exiting the application).
The console is a rich client and can be deployed in three ways: local installed application, via network share or Citrix published application.
3

Sentinel
Sentinel is installed on each system that is managed by Olympus. Sentinel is the process responsible for starting and managing the JMX server.
The Sentinel configuration contains the information required by the JMX server to start and stay running. That information includes:
■ LDAP URL: LDAP server that contains all Olympus configuration and security data
■ Profile: The profile defines which services the server has to offer
■ JVM parameters: These parameters include the directory to Java command and memory allocation
■ Credentials: Credentials are required to authenticate the JMX server
MBeans
MBeans (management beans) are Java objects that provide data and perform actions (command and control) to change the state of underlying
sub-systems. MBeans are installed on systems that are managed by Olympus and provide the key architecture enabler to allow for centralized
management (in conjunction with the Olympus console). For the remainder of this document, MBeans are referred to as “Services.” A complete
list of Services and functionality is included in this document.
LDAP
LDAP (Lightweight Directory Access Protocol) is a network protocol used to access and modify directory services. The LDAP server stores the
Olympus security and configuration data, which is housed in dedicated LDAP instance. Supported LDAP servers are Microsoft Active Directory
Application Mode (ADAM) and Oracle Internet Directory (OID). This LDAP instance is a standalone instance and does not require any modifications
to your corporate active directory.
Guardian
Guardian consists of two components: a service responsible for collecting data from managed systems; and a database. The Guardian service
may be thought of as an “Unattended Olympus User:” it collects data by invoking the same MBeans that an interactive user employs through the
Olympus console. The Guardian service is also responsible for the Alerting and Thresholding Engine. The data points collected by the service are
stored in the Guardian database for historical reference. Currently, both Oracle and MySQL are supported databases. The Guardian service
manages the database by summarizing and purging data at scheduled intervals. Multiple Guardian services and databases may be deployed to
support a large-scale Olympus environment.
Security
Olympus security supports LDAP authentication (Oracle Internet Directory or Microsoft Active Directory), eliminating the need for additional user
IDs and passwords for console login. Administrators in the Olympus security model have the ability to create custom roles to fit their specific needs
for individual users or groups of users. For example, a specific role could be created for an interface team. This role might have access to the
Open Engine (OEN) servers and transactions, but not to the MQ queues, the Millennium registry, or Operations Jobs. Roles may be further
customized to allow or disallow actions in each area. User Security is based on the following items:
■ User ID
■ Role
■ System/Domain Role (Production vs. Non-production)
■ Enterprise (logical grouping of nodes and domains)
4

Olympus Architectural Diagram
5

Licensing
There are two Olympus components that require licensing:
■ Olympus Thresholding & Alerting: The Thresholding & Alerting Engine enables users to proactively monitor the Cerner Millennium application
by generating e-mails and pages when parameters cross an established threshold.
■ Olympus Smart Modules for: Olympus Smart Modules enable clients to monitor and manage the technologies that support Cerner Millennium,
such as Oracle, WebSphere, High Availability (HA), PACs, and more.
The Olympus Thresholding & Alerting Engine is offered as an Enterprise license. Olympus Smart Module s are offered either as an Enterprise
license, or "Ala Carte" pricing. An Enterprise Olympus Smart Module License entitles a client to any available Olympus Smart Modules, as well as
any new subsequent releases. Olympus Smart Module Ala Carte licenses are purchased on a per-Smart Module basis, and offer licensing
flexibility for those clients who are only interested in specific Smart Modules. No matter the choice -- Enterprise or Ala Carte -- Olympus
Thresholding & Alerting and Smart Module Licensing give clients the ability to deploy to unlimited servers, with no reoccurring Licensing costs.
See your Technology Sales Executive for details on pricing.
Note: Olympus Command & Control functionality does not require licensing and is included in annual Cerner Millennium Maintenance.
Implementation
Olympus Thresholding & Alerting implementation is two weeks of engagement services which includes implementation, configuration, event
notification tuning, and knowledge transfer. Olympus Smart Module implementation is one additional week of services for implementation,
configuration, and knowledge transfer. See your Technology Sales Executive for pricing and scope.
Minimum Hardware Requirements
■ LDAP, Guardian, and Guardian Database Server(s)
The LDAP Server is the server on which the ADAM instance will be installed. A Guardian Server is a server on which the Guardian (data
collector) Service runs. A Guardian Database Server is a server on which the Guardian Database runs. Servers may be Virtual Machines if all
other requirements are met.
Olympus Installation Requirements vary on the size of each Millennium implementation. For ease of identification, this section has been
divided between Small, Medium, and Large clients.
Olympus Command & Control Only
6

Olympus Alerting/Enterprise – Up to 300 Servers
Olympus Alerting/Enterprise – Over 300 Servers
■ Managed System: A system/server (Back-end, Citrix, RRD, etc) managed by Olympus
- Disk Space:
- 1 GB of Free Disk Space on AIX, HP-UX, Linux, VMS servers
- 200 MB of Free Disk Space on Windows systems
- Minimum JRE (Java Runtime Environment) Version*
a. AIX – 1.4.2 SR6
b. VMS – 1.4.2-5
c. Windows 1.4.2_13
*Note: Required JRE Version may be installed at time of implementation. It does not require complete system Java upgrade and will not affect other programs utilizing
Java.
7

Functionality
This section details Olympus features and functionalities and is divided into: Olympus Command & Control Functionality; Olympus Alerting; and
Olympus Smart Modules
OLYMPUS COMMAND & CONTROL
Core Cerner Millennium Services
Service Description Actions
Backend Servers
Clinical Reporting
DeviceViewer*
Enterprise
Authentication*
Manage Cerner Millennium Application Servers
(functionality equivalent to SCPView and SPSMON)
Manage Cerner Millennium Chart Requests
(functionality equivalent to Chart Request
Maintenance)
DeviceViewer Functionality with additional
enhanced features
*Requires Millennium 2007.13 or higher for full
functionality
New service for user maintenance and reporting
*Requires Millennium 2007.18 or higher
- Start, Stop, Cycle (single or across domain) Server Instances
- View and Modify Server Definitions
- OS detail for Server Instances (CPU, Memory)
- View all Cerner Millennium Services (including shared services)
- Server Activity view [Requires minimum Millennium 2005.02.43]
- View server deficits and overages
- View server-service and service-server relationships
- Prompting for modification of protected servers
- Export Server Definitions to, and import from, SCP files
- Compare Server Definitions between two nodes, two SCP files, or
a node and a SCP file
- Server Groups can be defined for backend servers, allowing
monitoring and managing of a subset of servers. Users may be
given access to manage only specific server groups.
- Server Notes can be created and edited for all servers in
Olympus. Notes are visible in many Server management views
- View Chart Request Statistics, Details, and Statuses
- View by All Servers or Specific Chart Request Servers
- Re-submit Chart Requests
- Search Chart Requests with robust filters
- View and manage the following devices in the Millennium
database: Printers, Print Queues, Nodes, Faxes, Ports, Scanners
- View and manage output destinations in Millennium database
- View and control back end queues
- View Device Cross References in the Millennium database.
- Define New Printers via Import Tool, including LRS definitions
- Within a specified timeframe, view the following authentication
information:
- Authenticated users
- Failed authentications
- Locked users
- User Activity
- Ability to lock/unlock user from further Millennium activity
- Ability to lock out all users for downtime maintenance
Global Section View CMB Global Section - View Global Section Tables
Health Maintenance
Management
Logicals
View Health Expert Jobs
Manage Operating System Logicals (Environment
Variables)
- View Health Expert Jobs
- Modify Health Expert Job Size and Intervals
- View Logicals by Environment
- Add/Delete/Update Logicals
- Compare Logicals between nodes and domains
- Copy Logicals between nodes and domains
- Permanently save Logicals to the Cerner Registry
8

Core Cerner Millennium Services (continued)
Service Description Actions
Message Log
Millennium
Management
Operations
Order Format Validation
Manage Millennium Message Logs (functionality
equivalent to System Message View, Message View
and Message View Win)
View and Compare Code Sets
Event Code and Event Set Management
Domain Maintenance
Manage Operation Jobs and Servers (functionality
equivalent to OpsView Monitor)
Performs static analysis on a given order entry
format to help identify potential build issues that
may affect the order entry system.
- View, Browse, and Search Logs
- Export Logs to CSV
- Search Multiple Message Logs on Multiple Servers (both
Millennium Application and Citrix) in Single Search
- View Code Set differences between that which is loaded into
cache and defined in the Cerner database
- Repair Code Sets by synching cache with the database
- Load and Unload Event Codes and Event Sets
- Start/Stop and Set Millennium Components
- Manage Control Group Servers
- View by Status, Control Group, or Scheduled Tasks
- View Job Step Details
- Start/Stop/Initialize Tasks
- Binding/Skip/Reset Job groups
- Server Notes can be created and edited for all servers in
Olympus. Notes are visible in many Server management views
- Validation for all formats and action formats, with specifics for
General Laboratory and Pharmacy formats.
- View color-coded validation results that range from Success,
Informative Warning, and Error
PowerNote Maintenance Perform PowerNote maintenance tasks - Delete the PowerNote Cache
- Export/Import notes created in PowerNote
- Upload PowerNote files
- Import paragraphs
Queuing
Registry
Manage Cerner Millennium MQ (functionality
equivalent to QCPView)
Manage Cerner Millennium Registry (functionality
equivalent to LRegView)
- Start and Stop Queue Managers
- View and Modify Queue Properties
- Manage and Create Queue Channels
- View, Re-queue, and Purge Queued Transactions
- Manage Registry
- Add/Delete/Copy Keys and Properties
- Manage Registry Locks and Sessions
RTMS View and Analyze RTMS Data in “Real Time” - View Raw Data
- View User Response Time Graphs
- Advanced Filtering for Data Analysis
- New framework for RTMS collection and checkpoint
measurement
- View collected RTMS Timers from Guardian database
- View both RTMS v3 and v4 timers in a consolidated window
RRD
View RRD Statistics (functionality equivalent to
separate database query scripts)
- View All Stations or Specific Stations
- View Transmission Status
- Change fax status
- View, enable, and disable RRD ports
- View RRD Session Logs
- View RRD Modem Pools and Ports
- View quick Error Code reference information
9

Core Cerner Millennium Services (continued)
Service Description Actions
Volume Reports
View Cerner Millennium Application Statistics
(Functionality Equivalent to Database Monitoring
Tools)
- FirstNet, Orders, PathNet, Patient Management, Personnel,
RadNet, Scheduling Reports
Millennium Interface Services
Service Description Actions
ESI
ESO
OEN (Open Engine)
View ESI Statistics (functionality equivalent to
separate database query scripts)
View ESO Statistics (functionality equivalent to
separate database query scripts)
Manage FSI and MDI Interfaces (functionality
equivalent to OpenView Controller and separate
HL7 viewer)
-View ESI Volumes Statistics (Message and System)
- Query for ESI transactions in a specific time range
- Filter by only failed ESI transactions
- View contributor system, error text, and other pertinent data
for each transaction
- View all HL7 messages associated with a failed ESI transaction
- View ESO Volumes
- View real-time graph of TR1, Notify, and OCC ESO Queue
depths
- Start/Stop Interfaces
- View Interfaces Statistics
- View Queued Transactions
- View In-bound/Out-bound HL7 messages
- Search HL7 messages for text strings
- Server Notes can be created and edited for all servers in
Olympus. These Notes are visible in many Server management
views
- Replay messages for any outbound COM server from the Open
Engine CQM (Common Queuing Model) tables
Operating System Services
Service Description Actions
Dr. Watson
Manage Dr Watson and Crash Collector for Citrix
Servers
- Configure Dr. Watson and Crash Collector
- FTPs Crash Files to Cerner
- View Dr. Watson Crash Summary Logs
File System View File Systems and Disk Performance For all platforms (AIX, HP-UX, Linux, Open VMS, Windows):
- View File System Utilization
- View I/O Statistics
- File Browser
- View Disk performance
- Perform File Transfer to and from a Managed Server
- Text File Viewer
10

Operating System Services (continued)
Service Description Actions
Operating System View Operating System Statistics and Properties For all platforms (AIX, HP-UX, Linux, Open VMS, Windows):
- View Server CPU, Memory, and Network Statistics
- View Individual Process CPU/Memory Statistics
- View Running Processes
- View Process Detail
- View System Properties (OS Version, Machine Name, Time Zone,
CPU Count, Total Memory)
- Display process name in process view (not just executable
name)
- Terminate running processes
- View top CPU-consuming processes
- View process Page Faults
Printers Manage Backend Print Queues and Print Jobs - View All Print Queues
- View Queue Detail
- Start/Stop Queue
- Hold/Release/Delete Print Jobs
- Search for Print Queues and easily see their statuses and queue
depths
- Ping a printer to determine its availability
Windows Event Log View Event Logs (Application, Event, System) - View and Search Windows Events Logs
Windows Registry View Windows Registry - View, Search, and Modify Windows Registry
Windows Services Manage Windows Services - View Windows Services
- Start/Stop/Restart Windows Services
- View Service Details
Olympus Security and Administration
Service Description Actions
Auditing
Deployment Service
Creates an Audit Log of Actions Performed in
Olympus
Allows for centralized deployment and upgrades of
Olympus environments
- View what changes have been made to the system, when the
changes were made, and by whom in a centralized location with
searchable filters
- Deploy bundles of updates with which Servers can automatically
upgrade themselves.
Enhanced Security Control and configure security access to Olympus - Add and configure new users, roles, and levels of access to each
service
- Search users
- Configure Auditing categories
Olympus
Administration
Configure and manage Olympus infrastructure
- Deploy new Sentinel installations and upgrades to backend
nodes from the console
- Modify and deploy Sentinel configuration (sentinel.config)
- Retrieve Domains and Database info
- Cycle Sentinel servers from the console
- Cycle JMX servers from the console
11

OLYMPUS ALERTING
*Requires Thresholding & Alerting Licensing or Enterprise Licensing
Auditing Alerting
Parameter
Description
Audit Event
Monitors Olympus Auditing Events and notifies when a specific event is detected
Backend Server and Service Alerting
Parameter
Description
Server Connections
Server Definition Change
Server Exceptions
Server State
Server Working State
Service Message Count
Service Message Count
The number of Connections to each Server Instance
Indicates that a modification to a server definition or one of its properties has occurred
Indicates that the number of Server Instances running for a particular Server does not equal its
defined count (covers both Deficit and Overage conditions)
Indicates that a Server Instance has been in an abnormal state (starting or stopping) for longer
than a specified period of time
Indicates that a Server Instance is in a Working State for longer than a specified period of time
Indicates the number of Messages a Service (Connected or Shared) is currently processing
Indicates the total number of Messages that a Service (Connected or Shared) has processed
Code Cache Alerting
Parameter
Code Cache Difference
Description
Monitors the Millennium Code Cache and alerts when it is out of synch with the database
Interface Alerting
Parameter
ESI Fail Count
ESI Log Entry
ESI Max Time
ESI Retry Count
ESO Message Count
ESO Notify Queue Depth
ESO OCC Queue Depth
ESO TR1 Queue Depth
Open Engine In Cycle Time
Open Engine Interface State
Open Engine Orphaned Trigger
Open Engine Out Cycle Time
Open Engine Out Cycle Lag
Open Engine Transaction Count
Description
Number of ESI transaction failures for a message type
Monitors ESI Log Entries for errors
Maximum ESI transaction completion time for a message type
Number of ESI transaction retries for a message type
Number of ESO transactions sent for a message type
Monitors the depth of the ESO Notify Queue
Monitors the depth of the ESO OCC Queue
Monitors the depth of the ESO TR1 Queue
Last time a transaction was queued in for each OEN interface
Indicates the State of each OEN Interface
Indicates that an orphaned trigger exists
Last time a transaction was processed for each OEN interface
Indicates that an OEN Interface may be stalled
Number of queued transactions for each OEN Interface
12

OLYMPUS ALERTING (CONTINUED)
*Requires Thresholding & Alerting Licensing or Enterprise Licensing
MQ Series Alerting
Parameter
Description
MQ Local Queue Depth
MQ Local Queue Depth Percentage
MQ Local Queue Growth
MQ Local Queue Input/Output
Mismatch
MQ Queue Manager Status
MQ Queue Manager Change
MQ Local Queue Oldest Message Time
MQ Local Queue Put and Get Enabled
Queued depth of each MQ Local Queue
Queued depth of each MQ Local Queue as a Percentage of its maximum queue depth
Difference of each Local MQ Queue’s queued depth between the last polling cycle and the
current polling cycle. Indicates whether the Local MQ Queue is growing or shrinking.
Monitors Local Queues and alerts if there are publishers but no subscribers
Status of each MQ Queue Manager
Monitors when the status of an MQ Queue Manager changes
Age of the oldest queued message in each MQ Local Queue (minutes)
Indicates whether each MQ Local Queue may have messages put to and taken from (queued
and de-queued).
Operating System Alerting
Parameter
CPU Run Queue
CPU Utilization
File Contents
Logical Disk Bytes Available
Logical Disk Space Percentage Used
Physical Memory Percentage Used
Print Queue Status
Process Count
Description
CPU Run Queue count on a server
CPU Utilization (%) of all CPU’s on a server
Monitors the contents of a text file for a specified string
Available space (in Bytes) for each logical disk on a server
Percentage of used space for each logical disk on a server
Percentage of Physical Memory Used on each server
Status of each Print Queue on each server
Number of running instances of a specified process (Process Presence)
Process CPU Utilization Processes that have exceeded a specified amount of used CPU (%)
Process Physical Memory
Processes that have exceeded a specified amount of used Physical Memory (in Bytes)
Virtual Memory Used Measures the amount of Virtual Memory Used on each server (%)
Windows Service State
Indicates the State of a particular Windows Service
Operations Alerting
Parameter
Operations Control Group Status
Ops Job Status
Ops Task Change
Ops Template Change
Stalled Ops Jobs
Description
Status of each Operations Control Group
Monitors when Operations Jobs are not in a normal state
Monitors for changes in Operations Tasks
Monitors for changes in Operations Job Templates
Monitors when Operations Jobs are running longer than expected
13

OLYMPUS ALERTING
*Requires Thresholding & Alerting Licensing or Enterprise Licensing
RRD Alerting
Parameter
Description
RRD Port Status
Status of each RRD Port
RTMS Alerting
Parameter
Description
RTMS Timer
Monitors the duration of an RTMS timer
OLYMPUS RECOVERY ACTION SCRIPTS
*Requires Thresholding & Alerting Licensing or Enterprise Licensing
Olympus Recovery Script Actions allow scripts to be automatically called when a specified Olympus Alerting event occurs
Script
Cycle Server
Enable RRD Port
Requeue Messages
Description
Automatically Cycles Backend Servers intelligently. Supports Server Exceptions, Server Connections, Server
Working State, and Server Definition Change Alerts
Automatically Enables an RRD Port when it becomes disabled
Automatically requeues messages in a given queue
OLYMPUS DASHBOARD
*Requires Thresholding & Alerting Licensing or Enterprise Licensing
Offers an at-­‐a-­‐glace view of environment health at the Enterprise, Domain, and Node level
Widget
Description
Active Events
CPU
Memory
Queue Depths
Server Exceptions
Shared Services
Working Servers
Displays the Active Olympus Alerts
Displays the percentage of CPU Utilization for one or more nodes
Displays the physical and virtual memory used at the Node level. Displays the percentage of
virtual memory used for each Node at the Domain level.
Displays the current depth of the top ten local MQ queues with the highest depth. Data is
displayed in a bar graph.
Displays the server entries in a deficit or overage state
Displays the message count for the top ten shared services with the highest message count.
Data is displayed in a bar graph.
Displays the servers currently in a working state.
14

OLYMPUS SMART MODULES
*Requires Smart Module Licensing or Enterprise Licensing
Service Description Actions
724Access
CPDI
Chart Server
High Availability
View and Manage a 724Access
environment
View and Manage Cerner ProVision
Document Imaging Services
View and Manage Legacy (WinWord)
Chart Servers
View High Availability Configuration on
AIX systems
- Displays 724Access topology of Source and Mid-Tier Nodes
- Provides ability to Stop, Start, and Monitor the Manager, Capture,
Pump, and Replicat Processes
- View data flow of Capture, Pump, and Replicat Processes
- View and transfer 724Access and GoldenGate log files
- Displays CPDI topology of Services, Domains, and Nodes
- Provides the ability to Stop, Start, and Monitor the Document
Imaging, Batch Capture, and Content Management Services.
- Displays the Directory Detail of Service Directories
- Displays Detailed Service information, including Queues and
processing throughput
- Displays a detailed view of the Auto Import Folders, including the
watched, processed, and error folders.
- Manage configuration and operations of Chart Servers (WinWordbased).
- Remotely manages Starting, Stopping and configuration changes.
- Suppresses blocking pop-up windows.
- Allows management of multiple chart servers on a domain at once.
- Provides information and statistics on recent request, out files and
actual windows suppressed.
- Displays HA cluster topology of Database and Application nodes
- Checks HA configuration against Cerner recommended HA standards
- Allows comparison of nodes in an HA cluster to identify where their
configurations may differ
- Supports HA ATG.2 and HA.ATG.4 scripts
Oracle View Oracle Database Statistics - View DB Instance Health
- View Long Running Transactions
- View Top SQL Statements (by number of disk reads)
- View Tablespace Disk Utilization
- View Archive Destination and Percent Utilized
- View Table Locks and Waiting Transactions
- View Oracle Alert Logs
- View Archive Log Cut Rate
- View Latch Hit Ratios
- View Oracle Tablespace Usage Projections
- View DBA Resumable Events
- View and Manage Oracle Sessions
Multum View health of Multum environment - View Multum server status and response times
- Monitor node-level Multum status attributes as well as Multum SDK
Servers
WebSphere
View IBM WebSphere environment
health
- View cell topology: Cells, Clusters, Nodes, Application Servers,
Applications
- View statuses and attributes of elements in cell topology
- Start, Stop, and Cycle Application Servers
- Supports WAS environments with Application Security
15

OLYMPUS SMART MODULE ALERTING
724Access Smart Module Alerting
*Requires Thresholding & Alerting Licensing and 724Access Smart Module Licensing or Enterprise Licensing
Parameter
Active Sessions
Manager Status
Capture Checkpoint Time
Capture Lag Time
Capture Status
Pump Checkpoint Time
Pump Lag Time
Pump Status
Replicat Checkpoint Time
Replicat Lag Time
Replicat Status
Description
Monitors the elapsed time of Oracle sessions
Monitors Manager Process Status on Source and Mid-Tier nodes
Monitors Capture Process Checkpoint Time
Monitors Capture Process Lag Time
Monitors Capture Process Status
Monitors Pump Process Checkpoint Time
Monitors Pump Process Lag Time
Monitors Pump Process Status
Monitors Replicat Process Checkpoint Time
Monitors Replicat Process Lag Time
Monitors Replicat Process Status
Chart Server Smart Module Alerting
*Requires Thresholding & Alerting Licensing and Chart Server Smart Module Licensing or Enterprise Licensing
Parameter
Chart Server Log Level
Chart Server Printing Enabled
Chart Server Screen Updating
Chart Server State
Description
Monitors Chart Server Log Level Setting
Monitors Chart Server Log Level Setting
Monitors Chart Server Screen Updating Setting
Monitors for a Chart Server not in a RUNNING state
CPDI Smart Module Alerting
*Requires Thresholding & Alerting Licensing and CPDI Smart Module Licensing or Enterprise Licensing
Parameter
Age of Last Processed CPDI Item
Age of Oldest Item
Age of Oldest CPDI Property
Age of Last Processed Batch Capture
Item
Age of Newest Batch Capture Auto
Import Folder Item
Count of Batch Capture Auto Import
Folder Items
Content Management Application
Collision
Description
Monitors the Age of the Last Item Processed by a Specified CPDI Service
Monitors the Age of the Oldest Item in a Specified CPDI Directory
Monitors the Age of the Oldest Specified CPDI Property
Monitors the Age of the Last Item Processed by a Specified Batch Capture Service
Monitors the Age of the Newest Item in the Batch Capture Audio Import Folders of a Specified
Type
Monitors the Count of Items in the Batch Capture Auto Import Folders of a Specified Type
Monitors Content Management Applications for Collision State
16

High Availability Smart Module Alerting
*Requires Thresholding & Alerting Licensing and High Availability Smart Module Licensing or Enterprise Licensing
Parameter
Database Connectivity
CERRDBMS
CCLReconnect
Filesystem Permissions
Filesystem Ownerships
Login Credentials
LREG Settings
MQ Settings
Security Master Settings
Description
Monitors Database Connectivity configuration
Monitors $CER_RDBMS_CONNECT setting in the Cerner Registry
Monitors CCLReconnect setting in the Cerner Registry
Monitors HA files and filesystem permissions settings
Monitors HA filesystem ownership settings
Monitors HAUser and HAPassword settings in the Cerner Registry
Monitors LREG settings for High Availability
Monitors MQ settings for High Availability
Monitors Security Master is configured properly for HA failover
Multum Smart Module Alerting
*Requires Thresholding & Alerting Licensing and Multum Smart Module Licensing or Enterprise Licensing
Parameter
Multum SDK Server Load
Multum SDK Server Status
Multum Service Manager Status
Multum Version Consistency
Description
Load on each Multum Server as a Percentage of its maximum
Status of each Multum Server
Status of each Multum Service Manager
Determines whether Multum versions are consistent across servers in a farm
Oracle Smart Module Alerting
*Requires Thresholding & Alerting Licensing and Oracle Smart Module Licensing or Enterprise Licensing
Parameter
Description
Oracle Archived Logs
Oracle Archive Percentage Used
Oracle Database Mode
Oracle Excessive Disk Reads
Oracle Database Latches
Oracle DBA Resumable
Oracle Instance Active State
Oracle Instance Status
Oracle Locks
Oracle Locks CPU Time
Oracle Logins Allowed
Oracle Long Running Transactions
Oracle Tablespace Percentage Used
Oracle Tablespace Projection
Monitors Oracle Archived Log Cut Rate
Percentage of used Archive space in Oracle database
Current Database Mode Status
SQL statements that have exceeded a specified number of disk reads
Monitors Oracle Latch Hit Ratio
Monitors DBA Resumable Events on the Database
Oracle Instance Active State Status
Oracle Instance Status
Indicates presence of an Oracle Exclusive Lock
Monitors CPU time of Objects that have a Lock or are waiting on a Locked Object
Oracle Logins Allowed Status
Transactions that have exceeded a specified duration of time
Percentage of used space in each Tablespace
Monitors Projection of Time until Tablespace runs out of space
17

WebSphere Smart Module Alerting
*Requires Thresholding & Alerting Licensing and WebSphere Smart Module Licensing or Enterprise Licensing
WAS Free Memory
WAS Heap Size
WAS Status
Parameter
Description
Measures the amount of Memory available for each WebSphere Application Server (Bytes)
Measures the amount of used Heap Size for each WebSphere Application Server (Bytes)
Indicates the State of a particular WebSphere Application Server
18