Whitepaper IBM FSM - Cenit AG Systemhaus

2.2.4 getting the Whole pictuRe
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
FSM does not only monitor the various ECM components, but also their underlying infrastructure,
so that the administrator gets the whole picture of his entire ECM platform in one Single Point of
Control. This is important, as the failure of an infrastructure component may result in a failure of
an ECM component. So even if the responsibility for such an infrastructure component resides in a
different administrator group in the IT organization the ECM administrator must have knowledge
of such events, as they have a negative impact on the availability of his ECM application. Because
it is the ECM administrator who will get blamed for the outage as the end users only see the ECM
front-end application, but not the complex environment behind it (actually they don‘t have to care
about IT complexity).
Out-of-the-box and based on CENIT Best Practices FSM can manage the following components:
• Databases: IBM DB2, Microsoft SQL Server and Oracle database server are monitored. This
covers not only the database health status (e.g. tablespace capacity), but checks the database
also from the ECM perspective, i.e. can the IBM ECM application connect to the database. If
the ECM administrator has the need for custom SQL queries against the database which are not
covered with FSM standard monitors, predefined custom SQL query monitors are available for
all supported databases. FSM database monitors can be configured for local or remote databases
and can use either the corresponding database command line tools or a JDBC connection to
monitor the databases.
• J2EE Application Servers: IBM WebSphere Application Server, JBoss, Oracle (BEA) WebLogic
and Tomcat are monitored via JMX. This allows FSM to collect all application server specific
health information that this server is providing through JMX.
• Web Servers: Monitoring of Apache, IBM HTTP Server and MS Internet Information Server.
• Input Management: Captiva InputAccel, Foxray xbound, Kofax, Moreen.
• Output Management: Compart DocBridge Pilot.
• System logfiles: UNIX Syslog, Linux Syslog, Windows Eventlog, AIX error log.
Other applications can be added on demand. This includes custom built applications, which are using
or which are connected to the ECM platform, as they are an integral part of the IT Service ECM.
09