1 ecm system monitor in the cmod environment. © 2013 ibm corporation enterprise content management...

1

ECM System Monitor in the CMOD Environment

© 2013 IBM Corporation

Enterprise Content Management

IBM ECM System Monitor Improve Availability / Lower TCO of IBM ECM

Proactive monitoring of IBM ECM platforms functional ECM health monitoring– IBM ECM components– Middleware components, e.g. database & application servers– Input & Output Management– Custom monitoring for add-on applications (3rd party & custom-built)

Holistic ECM Service Level Management – Simple Red / Yellow / Green traffic light paradigm– IT Service Management (ITSM) integration

• Event forwarding to central Event Management (IT Operations)• Trouble Ticket opening in Incident Management (Service Desk)

Single Point of Control with end to end visibility– Monitoring and Logfile Management– Knowledge Base– Tasks Automation – Reporting



3

Before IBM ECM System Monitor – no proactive monitoring of CMOD Platform

No application health status information= black box!

Processes – up/down

Processes and details – up/down, tablespaces, etc.



4

IBM ECM System Monitor Automates the Management of your CMOD Platform

ECM System

1. Database error preventsdocument access

3. Increased uptime, meeting your SLA, satisfied users

Problem Solution Result

2. System Monitor identifies error, alerts Administrator who instantly solves the problem with the built in knowledge base, or SysMon can auto correct the outage



5

IBM ECM System Monitor Capabilities

Proactive monitoring and logfile management– 1800+ performance & system parameters– 900+ RPC level Listener metrics– 28+ ECM logfiles– JMX for Webserver and WMI object interface– Real-time alerts via Blackberry, pager, email, console, SMS

InstallAnywhere support

Automation of manual administration tasks

Seamless integration with enterprise system mgmt. tools– Pre-defined SNMP MIB– Logfile– Email / Command Line– Direct API Integration into IBM Tivoli and HP OpenView

New Management reports and enhanced knowledge base– Analysis of historical events – identifying weak spots– Analysis of resource utilization – trending and capacity planning



ECM System Monitor Integration with CMOD (zOS and MP)

On Demand is integrated with ECM System Monitor via two methods

– System Monitor can monitor the OnDemand system log and report when errors occur. This is done through an ODWEK module provisioned for ECM System Monitor. ECM System Monitor can also monitor the status of the arssockd program via the new command-line options to provide thread listings and “ping” status

– Via the ECM System Monitor listener which is directly implemented in the arssockd program and can be attached to via a network port to relay information to the listening program, ECM System Monitor. The port is defined in the ars.cfg file for the appropriate server. The environment variable is ARS_LISTENER_PORT. If not defined, the listener is inactive. If defined as 0, the default port of 32775 is used.



Monitoring IBM Content Manager OnDemand Multi Platform

OnDemand Archives– Database (DB2, MSSQL, Oracle)

• Status• Usage• Details (Statistics, Logspace,

Rollback Segments, etc.)– Services & Processes– System Logging Entries - SL2

(Database table) OnDemand Logon Status OnDemand System and User

Error

Knowledge Base - for SL2-related Log entries

OnDemand Tasks– Status OnDemand Services /

Processes– Start and Stop OnDemand

Services / Processes

OnDemand Web Applications – WebSphere Application Server

Application Status (WEBi, Admin GUI)

JMX Monitoring (JVM parameters like HeapSize, Connections, Threads, etc)

– Logfiles• Web Application Server Status Logfile• Web Application Server Error Logfile

Listener Metrics– Performance Metrics– Capacity Metrics– Events

Content Navigator

New

New

New

New



Monitoring IBM Content Manager OnDemand – cont.

Latest version adds support for

– WAS 8.5– Websphere logfile parsing– OD Full Text Server server 9.0– CSS 5.2– Report Distribution Server start/stop functionality



Monitoring IBM Tivoli Storage Manager

TSM Accounting (global, per Client / Client Type / OS / Authentication Method)– Server Session Exit code (Normal=X'01', Abnormal=X'00')– Number of Archive Storage / Retrieve Transactions of a Session– Number of Backup Storage / Retrieve Transactions of a Session– Volume of Archive Files and Backup Files sent from Client to Server– Volume requested (in KB) for archived objects and by stored objects– Volume (in KB) of session transferred between Client and Server– Completion Time and Idle Wait Time of a Session in seconds– Active Communication Time and Wait Time for Media of a Session in seconds– Client Session Type (1-4 for normal session, 5 for scheduled session)– Number of ‘space-managed’ Storage / Retrieve Transactions of a Session– ‘Space-managed’ Volume (in KB) sent from Client to Server– Volume (in KB) requested by ‘space-managed’ objects

Requires activation of TSM Accounting

Monitoring of TSM Storage Pools (TSM Volume Log) Monitoring of TSM Error Logs incl. Knowledge Base entries



Monitoring IBM Content Manager OnDemand Multi Platform – Listener Specific via arssockd

New



CMOD Monitoring Screenshots



CMOD Reporting with Trend Analysis



Questions

Contact Steven Bass at IBM – [email protected]

1 ecm system monitor in the cmod environment. © 2013 ibm corporation enterprise content management...

Documents