Whitepaper IBM FSM - Cenit AG Systemhaus

WhitepapeR
Reliable and efficient
opeRation of ibM ecM solutions
cenit
industriestraße 52-54
70565 stuttgart
www.cenit.de/eim
telefon: +49 711 7825-30
fax: +49 711 7825-4000
e-Mail: info@cenit.de
www.cenit.de

table of contents
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
1. Reliable and Efficient Operation of IBM ECM Solutions 3
2. The Value Proposition 4
2.1. The Business Challenge 4
2.2. The Solution 6
2.2.1. Automating the Daily Operation of IBM ECM 6
2.2.2. Application Management for IBM FileNet 7
2.2.3. Application Management for IBM Content Manager 8
2.2.4. Getting the Whole Picture 9
2.2.5. Make or Buy 10
2.3. The Benefits 11
3. The Architecture 12
3.1. FSM Server and Agents 12
3.2. High Availability 13
3.3. Event Integration 14
4. The Implementation Approach 16
5. Add-On Solution for End-to-End Performance Management 17
6. Some Impressions of FSM 20
7. Contact 30
02

1. Reliable and efficient
opeRation of ibM ecM
solutions
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
In many enterprises IBM ECM solutions such as IBM FileNet or IBM Content Manager 8 are used
in mission-critical business processes. To ensure a reliable and at the same time efficient operation
of this ECM platform results in complex challenges for the IT Service Management. The ECM
monitoring solution IBM FileNet System Monitor (FSM) offers an IBM ECM specific application
management solution, which can be integrated seamlessly into central Enterprise Systems Management
solutions such as IBM Tivoli.
The benefits are manifold:
• Comprehensive, proactive monitoring of IBM ECM components and their infrastructure in one
Single Point of Control improves availability and end user experience for Lines-of-Business
• Better and cost efficient fulfillment of Service Level Agreements
• Integration of IT Operations and Service Desk for central operation of IBM ECM 24*7
• Automation of non-value-adding routine work of IBM ECM administrators reduces operational
costs
FSM helps to deliver Service Level Agreements related to the IBM ECM platform in a more reliable
and efficient way. The end users get a better experience of ECM and embrace new opportunities
for an enterprise-wide usage. Operational costs are reduced; high costs due to productivity losses
in the LOB are avoided.
03

2. the Value pRoposition
2.1 the business challenge
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
The IBM ECM platforms IBM FileNet and IBM Content Manager / Content Manager OnDemand
often are used in mission-critical business processes e.g. claims processing, underwriting or customer
service. When this platform becomes unavailable, the damage – in employee productivity and lost
revenue as well as lost reputation – is very high. Therefore the Lines of Business (LOB) require a
high availability of this IT service. To guarantee the availability of the IBM ECM platform, most
IT organizations implement High Availability and Disaster Recovery strategies.
However this is not sufficient to deliver the Service Level Agremeents requested by the LOB. In a
survey analysts found that only approx. 20% of application downtime was caused by hardware failures
or environmental issues, whereas approx. 80% of application downtime was caused by application
or operator errors. Addressing these 80% error causes results in high efforts in IT Operations and
Service Desk, often 24*7, due to the fact that the ECM systems in most organizations are still operated
manually. Enterprise Systems Management tools are restricted to a basic monitoring of ECM
components, but they do not provide any ECM specific functional application health monitoring.
The manual operation of ECM systems however compromises the fulfillment of Service Level Agreements
for the LOB and results in high operational costs in the IT organization. The only way
to solve this dilemma is to automate non-value-adding activities in the daily administration and
monitoring of the ECM systems. Therefore it is mandatory to extend an IT organization’s Event
Management processes and tools to the ECM systems in order to monitor and assess their health
status at any given time from a functional perspective, not from a component perspective.
04

07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
A Forrester survey shows the impact of cost reductions in the daily operation on the IT budget.
Leading IT organizations are able to allocate a far higher percentage of the IT budget to new investments
instead of „burning“ the money in maintaining the status quo.
Overall IT budget
New Investments
20%
80%
Source: Forrester Business Technographics Survey, 2006
Grafik
Ongoing Operations
Wasted
Cost
• Best companies are 60/40;
some approaching 50/50
• Ratio is a key indicator of both the
efficiency of IT, as well as IT value
Several IT Service Management studies show that more than 70% of application problems were
not detected by the application administrators, but by the end users. Identifying the root cause of a
problem often takes hours, especially in complex J2EE environments, and involves different groups
in the IT organization. This results in more downtime and operational costs than necessary - and
certainly does not help to meet the end users‘ expectations.
05

2.2. the solution
2.2.1 autoMating the daily
opeRation of ibM ecM
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
The answer to address this challenge is „IBM FileNet System Monitor“ (FSM) – a solution which
allows customers to manage the IBM ECM components and their underlying infrastructure reliably
and efficiently by automating routine work in the daily operation.
FSM manages the various IBM ECM components as well as their underlying infrastructure, such as
Database and J2EE Application Server or server and storage systems, and their overall interoperability
to guarantee the availability of the IT service ECM from an end user perspective. So FSM does
not only monitor the various components, but also the entire document management process chain.
FSM does not only alert for current problems, but also allows identifying upcoming problems.
Hence the ECM administrator is able to proactively intervene, before the LOB experience any
outage of their mission-critical ECM system. Event forwarding from FSM to Enterprise Systems
Management tools allows IT Operations and Service Desk personnel to monitor the ECM systems
24*7 using their standard management console. An ECM specific Knowledge Base supports in the
analysis of problems and events, helping staff without deep knowledge of ECM applications to better
assess problems. Predefined remote tasks allow starting / stopping of ECM systems or even entire
environments without having the support personnel to know the proper sequence and syntax for
starting / stopping and without giving them full administrative rights in ECM systems. Statistical
information or adhoc health information can also be retrieved from the monitored systems. All tasks
are secured by user privileges.
The reporting engine of FSM allows analyzing historical events as well as statistic and performance
data collected by FSM. The reports can be used e.g. to share status information with LOB management,
to identify quality improvements (Problem Management) and to properly plan capacities
(Capacity Management). The event data in the FSM event database can also be used by IT Service
Management Tools for an enterprise-wide Service Level Reporting.
Built in maintenance features, like an automated cleanout of old events or the elimination of duplicate
information in the FSM event database help to reduce the maintenance efforts for FSM.
06

2.2.2 application ManageMent
foR ibM filenet
FSM provides out-of-the-box support for the following IBM FileNet applications:
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
• IBM FileNet Image Manager: Image Services, ISRA, Web Services, HPII/MRII, Content Services
• IBM FileNet Content Manager / Business Process Manager: Content Engine, Process Engine,
Application Engine, Component Manager, Rendition Engine
• BPM Add-ons: Process Analyzer, Business Process Framework, Business Activity Monitor
• Compliance: Email Manager, Records Manager, Records Crawler, IBM Content Collector (ICC)
• Capture, Print, Fax
• BatchIt (for IS and CE)
• Application Connector for SAP
• Storage: SDS Integral and NLS (CSAR, ISAR, MSAR, OSAR, SSAR)
• Integration: Content Federation Services for Image Services (CFS-IS), ISCE Connector, Information
Integrator Content Edition (IICE)
• IBM FileNet Logfiles (e.g. Image Manager and Process Engine elog, P8 server error log, ISRA
log)
• Listeners - real-time monitoring of health parameters and statistical counters provided by the
Listener API
07

2.2.3 application ManageMent
foR ibM content ManageR
FSM provides out-of-the-box support for the following applications on distributed platforms:
• IBM Content Manager 8
• IBM Content Manager OnDemand
• IBM CommonStore for Mail and SAP
• IBM Content Collector (ICC)
• Information Integrator Content Edition (IICE) / Information Integrator for Content (II4C)
The following parameters of IBM Content Manager are of particular interest:
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
• Monitoring of SYSITEMEVENT and SYSADMINEVENT tables on the Library Server. For
selected events FSM provides information about error cause and corrective actions.
• Monitoring of operability and status of Resource Manager (Heartbeat).
• Status monitoring for Migrator, Replicator, Purger and Stager of Resource Manager, which can
be configured individually for each IBM Content Manager instance.
• Resource Manager Volume Space: Monitoring of filling level and online status of seven Device
Managers. Cross-check with definitions in Resource Manager database to allow proactive problem
detection.
• Resource Manager Web Application Status: Monitoring of icmrm application and its Snoop
address to check if Library Manager can connect to the application.
• Monitoring of connectivity and status of Information Integrator for Content and Information Integrator
Content Edition via RMI. This can be extended easily to monitor other RMI applications.
• Web Applications (eClient and custom applications): Monitoring of accessability from an end
user perspective via JMX and http.
• Monitoring of IBM ECM logfiles:
o IBM Content Manager logfiles: CM8 Eventlog, Server Errorlog, Asyncer Logfile, Migrator
Logfile.
o IBM Content Manager OnDemand logfiles: OnDemand Archive Logfile
o (database table).
o IBM CommonStore logfiles: Archive Log, Server Errorlog, Retrieve Log.
o TSM client logs (dsmerror and dsierror logs)
08

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

2.2.5 Make oR buy
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
How does FSM interfere with the Enterprise Systems Management tools? If I have invested millions
of $ into IBM Tivoli, HP OpenView or other vendors, why should I buy FSM? Can‘t I use my ESM
tools and build it on my own?
The answer is very simple. FSM provides the ECM specific application health monitoring using
ECM internal API and tools, which is not covered by the ESM vendors. And it cannot be built on
your own, as it requires deepest knowledge of the ECM components and involves high efforts - for
every new ECM release.
So FSM does not replace any ESM tools, but adds value to them. FSM is targeting the ECM administrators
and application specialists in 2nd Level Support, but is also helping IT Operations and
Service Desk staff by providing the full picture in their existing ESM‘s event consoles – without
the need to reinvent the wheel.
FSM provides additional know-how to the ECM administrators, as for each monitor and thousands
of log file events FSM provides knowledge base entries which will help to identify the problem and
possible corrective actions. This knowledge base is part of the product and represents many years
of ECM administration experience. Of course this knowledge base can be extended with customerspecific
instructions, e.g. organizational specific instructions or information regarding applications,
which have been added to the monitoring during the implementation of FSM (e.g. custom-built
applications).
10

2.3 the benefits
Monitoring IBM ECM environments with FSM provides the following benefits:
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
• Comprehensive monitoring of IBM ECM components and their underlying infrastructure in one
Single Point of Control
• IBM ECM specific Knowledge Base to support and expedite problem analysis
• Stabilization of the IBM ECM platform
• Higher availability of IBM ECM based IT services due to error prevention and reduced problem
resolution efforts improves service quality for LOB
• Better and cost efficient fulfillment of Service Level Agreements
• Reduction of trouble tickets in the Service Desk
• Integration of IT Operations and Service Desk due to event forwarding to Enterprise Systems
Management Tools allows central operation of IBM ECM 24*7
• Automation of non-value-adding routine work in the daily administration and monitoring improves
the productivity of IBM ECM administrators and reduces operational costs
• Integration of IBM ECM as managed application into an enterprise-wide IT Service Management
allows usage of established IT Service Management processes
Thanks to FSM the ECM application specialists in 2nd Level Support can focus their attention to
the further development and optimization of the IBM ECM platform instead of wasting their time
with non-value-adding routine work in the daily administration and monitoring. All the same they
– and IT Operations and Service Desk – can be sure that they will be alerted immediately in case
of a current or an upcoming error or event.
With that FSM helps to deliver Service Level Agreements defined for the ECM platform in a more
reliable and efficient way. The end users get a better experience of ECM and embrace new opportunities
for an enterprise-wide usage. Operational costs are reduced; high costs due to productivity
losses in the LOB are avoided.
Many well-known customers in various industries all over the world rely on FSM to make sure that
their ECM platform is working properly – and is meeting the expectations of their LOB. This is
especially true for the banking, financial services and insurance industries as well as government
agencies, where ECM & BPM applications often are used in customer-facing business processes.
At www.cenit.de/fsminfo you can find customer success stories for download.
11

3. the aRchitectuRe
3.1 fsM seRVeR and agents
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
FSM has a client / server architecture, which is designed to minimize the workload on the managed
systems. Server and client both consist of two components – a monitoring component (client and
server) and an infrastructure component (client and server).
The execution of predefined remote tasks is handled by the FSM Infrastructure Agent, which is
installed on the managed system. The communication between FSM Infrastructure Agent and FSM
Infrastructure Server is TCP/IP based and secured by certificates and SSL encryption. All remote
tasks are initiated and authorized by the FSM Infrastructure Server.
The collection of events is handled by the FSM Monitoring Agent. The communication between Monitoring
Server and Agent is also TCP/IP based and encrypted. (For further details, please see the
FSM Encryption Whitepaper).The processing of events is handled by the FSM Monitoring Server.
Events are stored in the Event Database, where they can also be kept for historical analysis. The
user authentication can be handled FSM internally or FSM can be connected to LDAP systems,
like Microsoft Active Directory Services, Tivoli Directory Services, Sun Directory Server or Novell
eDirectory.
For the FSM Management Server and Management Agents, as well as the Monitoring Server and
Monitoring Agents, the following Operating Systems are supported (FSM V4.0.1).
The FSM Server can also be deployed in a virtualized environment, e.g. run on VMWare or LPAR.
For the Event Database FSM V4.0.1 supports DB2, MS SQL Server and MySQL.
[FSM V4.5 will support DB2, Derby, MS SQL Server and Oracle for the Event Database.]
12

3.2 high aVailability
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
The FSM Management Server can be set up as High Availability solution, e.g. with a backup server
in an ECM DR environment.
(„w/o management function“ means, the passive server is not connected to the infrastructure agents)
13

3.3 eVent integRation
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
FSM can run independently, so no monitoring infrastructure is required to manage the ECM environments.
However FSM can integrate into Enterprise Systems Management tools by forwarding
events to them and by receiving events from them.
This enables IT Operations and Service Desk staff to get ECM related event information within their
event consoles, whether it is the IBM Tivoli Enterprise Portal or TEC, HP OpenView Operations
or any other event console.
The ECM specialists would work with the FSM Management Console, where they see the overall
health information about their ECM environment - broad and deep. They will be alerted in case of
critical situations and they will see warnings to identify upcoming problems. They also get „harmless“
status information that helps them to better assess the status of the ECM platform, e.g. for
planning purposes.
14

07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
IT Operations and Service Desk staff however are not interested in that broad and deep information
about the ECM platform. They need to know if a critical situation occurs that requires immediate
action, so they can follow the processes defined in their operational policies. Exactly this piece of
information is what FSM will bring to their attention - in the central event consoles IT Operations
and Service Desk are using.
In general ESM tools can be fed with FSM events provided in a FSM logfile, which would be analyzed
by the ESM tool‘s logfile adapter, or a predefined SNMP MIB shipped with FSM.
For IBM Tivoli and HP OpenView FSM additionally provides direct event integration:
• IBM Tivoli: Collection of FSM events via the JDBC / ODBC Connector of IBM Tivoli Monitoring
V6.x‘s Universal Agent. Alternatively events can be sent directly to the IBM Tivoli Enterprise
Console or IBM Tivoli Netcool/OMNIbus.
• HP OpenView Operations: FSM provides an event forwarding via HP‘s Java API.
15

4. the iMpleMentation
appRoach
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
IBM and CENIT provide installation packages to support customers in the initial installation and
configuration of FSM.
Going beyond the installation and basic configuration CENIT provides a turnkey implementation
package for FSM, which is tailored to the customer‘s ECM environment and can include other
systems working with the ECM platform, e.g. input & output management systems, as well as an
end-to-end performance management on demand.
This CENIT implementation package is designed to meet customer‘s specific requirements and
covers the following activities:
• Analysis and Conception
o Best Practices
o Customer specific requirements beyond Best Practices, e.g. monitoring of 3rd party applications
or homegrown applications
• Installation of FSM Management Servers and Management Agents in ECM production and
non-production environments
• Customization / configuration of
o Monitoring
o Logfile Management
o Remote Tasks
o Management Consoles
o Knowledge Base
o Reporting
o Event forwarding to Enterprise Systems Management Tools
• Roll-Out into ECM production and non-production environments
• FSM Administrator Training for ECM administrators
• Project Management and Documentation
After approx. 4 weeks of productive usage of FSM it‘s strongly recommended to review the events
detected and adjust the thresholds accordingly, so that you get as many events as necessary and as
few as possible.
The efforts for the implementation of FSM mainly depend on
• Number of ECM environments and servers to be monitored
• Customer requirements going beyond Best Practices
• Training requirements of customer, e.g. multiple sessions of the Administrator Training or extended
Logfile Adapter training
With that CENIT provides a tailored solution and enables the customer‘s ECM administrators to
run their application management based on FSM self-sufficiently.
16

5. add-on solution foR
end-to-end peRfoRMance
ManageMent
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
As the end user‘s performance depends on many components, the performance monitoring within
the ECM engines is not sufficient to guarantee the quality of service requested by the LOB. Only
an end-to-end monitoring from the front-end provides significant information of the end user‘s
experience of his ECM applications.
CENIT offers a special add-on for FSM to monitor the experience of an ECM end user 24x7. This
solution – called „ServiceTracer“ for FSM – monitors both the availability and the response time
of the ECM applications from an end user perspective in central as well as remote locations. That
also includes the network performance for remote locations.
This offering supports the entire Software Lifecycle Management, i.e. is not only used during the
operation of the application. It can also be used prior to its roll-out to support proper quality testing
and performance analysis to make sure that the end users really get what they expect. If performance
problems occur, it helps to do root-cause analysis and to identify bottlenecks. Management
reports provide Key Performance Indicators (KPIs), which can be used for Service Level Reporting,
within the IT department and for the LOB (show them how good you are!). The historical data can
be analyzed to identify trends, e.g. to assess upcoming capacity bottlenecks and to support a proper
sizing of the ECM environment.
„ServiceTracer“ provides multiple features:
• The ServiceTracer Client is a robot which is acting like an end user. This robot is measuring
the response time of ECM transactions, e.g. retrieving a document, against thresholds. The
ServiceTracer Client can be installed in any location in which ECM end users are working and
Service Levels have to be delivered. The measurement is based on image pattern recognition,
so ServiceTracer can measure the performance of any ECM front-end application - whether it
is the IBM FileNet Workplace, IBM eClient or WEBi, front-end applications of IBM Business
Partners, SAP or custom-built front-ends.
• The NetworkTracer measures the performance of the network connecting the ECM platform with
the ServiceTracer Client, i.e. the end user, in the remote locations.
• Both measurements are run against thresholds and if these are breached alerts are sent to the
FSM Management Console. This enables the ECM administrators to run their ECM platform
proactively from a backend and an end user perspective.
• ServiceTracer is very easy to handle and to administrate, so that there are only little training
efforts. A workflow editor simplifies the creation of new robots to monitor additional applications.
This can be done by the ECM administrators, as it does not require expert know-how.
• Service Level Reports can be created automatically and be published through a web portal or
distributed as PDF via email.
17

The benefits are significant:
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
• With ServiceTracer for FSM the ECM administrators cannot only monitor their ECM platform
proactively from a backend perspective, but also from the end users perspective. They always
know about their experience, so that they can detect upcoming performance issues at an early
stage. The Business Service Management provided by IT Service Management tools such as IBM
Tivoli or HP OpenView is fed by FSM with ECM specific performance information.
• Root-cause analysis and identification of bottlenecks are simplified and expedited.
• The automated management reporting provides transparency and allows a better communication
with the LOB.
• The ease of use and administration ensures low cost of ownership for this performance management.
ECM administrators can create their own ECM response time measurements, which allows
them to respond to LOB requirements quickly.
18

07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
ServiceTracer for FSM provides an easy to set up solution for continuous performance measurement
from the end user perspective at low costs that can be run by the ECM administrators themselves.
Solutions such as IBM Tivoli Composite Application Manager for J2EE or HP (Mercury) Business
Availability Center provide more analytic capabilities, but are more complex to implement and
operate at higher costs.
19

6. soMe iMpRessions of fsM
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
The following screenshots show you how FSM helps to identify and handle events:
For the ECM administrators FSM provides one Single Point of Control where they can manage their
IBM FileNet and IBM Content Manager systems as well as 3rd party applications, e.g. capture
solutions, and homegrown applications.
The managed systems can be grouped logically, e.g. by environment (Production, DR, UAT, ...) or
applications (ECM, Input Management, Output Management) or locations (Data Centre, remote
locations), depending on customer‘s requirements and organization.
Picture 1: Critical alert on the IBM Content Manager system
Here we can e.g. see that the IBM Content Manager 8 application is showing a critical event in the
CM8 logfile (Picture 1). After solving this we can see that there is still a warning from our capture
application as well as a performance warning, which is acknowledged by another administrator
who is already working on this issue (Picture 2).
20

2: Warnings related to the IBM Content Manager system
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
The following screenshots show us some detailed application health information provided by the
monitors and logfile management of FSM.
Picture 3: Health information related to the IBM FileNet Process Engine
21

07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
Picture 4: Detailed health information related to the Cache Record Size including the FSM default
knowledge base entry
Picture 5: Detailed health information related to the CM8 Resource Manager Web Status including
the FSM default knowledge base entry
22

07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
Picture 6: Detailed health information related to the DB2 database including the FSM default
knowledge base entry
The configuration of monitor settings, such as thresholds and severities, is handled in the FSM
Monitoring Manager (Picture 7 and 8). Monitoring scripts written by customers can be included
in FSM as custom monitors, i.e. you can continue to use them and protect your investment. If the
customer script is fully integrated in FSM, the ECM administrator can use all FSM troubleshooting
mechanisms to check why the script returns a problem or why a new script does not work as expected.
23

Picture 7: Monitor settings for the IBM FileNet Content Engine‘s Objectstore
performance monitoring
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
24

07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
Picture 8: Monitor settings for the IBM Content Manager‘s Resource Manager Volume Space
monitoring
The execution of remote tasks, e.g. to restart a component that has failed, is handled in the FSM
Task Execution Manager (Picture 9). Here we see the task collections provided out-of-the-box and
a task to restart the Component Manager of an IBM FileNet system. Automation scripts written by
customers can be included in FSM as custom tasks, i.e. you can continue to use them in the controlled
environment of FSM.
25

Picture 9: Remote Tasks in FSM
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
The Knowledge Base of FSM provides information about error cause and potential corrective actions
for events collected by FSM from monitors as well as logfiles (Picture 10). This Knowledge
Base can be extended by the ECM administrator to provide customer-specific instructions how to
handle events, e.g. related to homegrown applications or which are organization-specific, e.g. how
to handle events after hours. For these custom knowledge base entries you can use HTML code,
e.g. to provide direct links to other sources of information or tools.
26

Picture 10: FSM Knowledge Base entries related to IBM FileNet logfiles
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
The end-to-end performance management solution ServiceTracer can be integrated in FSM, allowing
ECM administrators not only to see events coming from the ECM platform, but also from the end
user experience. Here we can see how these performance events collected from ServiceTracer can
be presented in the FSM Management Console in an own area (Picture 11).
Picture 11: ECM performance information collected from ServiceTracer
27

Depending on how granular you define the performance measurement you get detailed information
about response times for single activities performed in a typical end user workflow. The more granular
you define the measurement, the easier it is to identify performance bottlenecks. In Picture
12 we can see the measurement of 5 single activities in an IBM FileNet Workplace application,
executed in the location Stuttgart in the business process „Customer Service“. As all activities were
delivered within their thresholds, the overall status of this measurement is „OK“.
Picture 12: Performance information related to the IBM FileNet Workplace
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
28

07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
ServiceTracer can be used to measure the performance of any front-end application. That allows
you to measure access to documents stored in the ECM platform from 3rd party applications, e.g.
SAP or CENIT‘s advanced case management solution ECLISO, or from homegrown applications.
In Picture 13 we can see the performance measurement for a SAP application connected to the
IBM ECM system.
13: Performance information related to a SAP application
29

7. contact
CENIT provides unparalleled expertise for proactive monitoring of IBM ECM Systems
using FSM – software, implementation services, training, coaching, and onsite support.
For 20 years Cenit has been providing customer-oriented solutions based on IBM and
FileNet offerings.
For further information about FSM please visit www.cenit.de/fsminfo or contact
Roland Merkt
Head of Systems Management
Phone: +49 711 7825 3285
Email: r.merkt@cenit.de
Trademark notice:
All brands and product names are the trademarks of their respective owners
07/2010 | © cenit
WhitepapeR
fsM – application
Management for ibM ecM
30