ibm ecm system monitor: monitoring ondemand on unix, … · 2014-04-14 · now switch to the...

February 14 ECM System Monitor 5.1 of 11

IBM ECM System Monitor: Monitoring OnDemand on UNIX, Windows, Linux and z/OS Configuration settings and requirements 07.02.2014 CENIT AG Autor: Michael Wohland , Mathias Faas


PREFACE: ............................................................................................................................................................ 3

REQUIREMENTS OF THE IBM ECM-SM SERVER: ................................................................................... 3

REQUIREMENTS FOR MONITORING OF LUW-BASED CMOD SERVER: ........................................... 3

REQUIREMENTS FOR Z/OS BASED CMOD ENVIRONMENTS: ............................................................. 4

STEP BY STEP GUIDE: ...................................................................................................................................... 5


Preface:

IBM FileNet System Monitor version 4.5 was the first release to monitor IBM Content Manager OnDemand (CMOD). With IBM ECM System Monitor (ECM-SM) version 5.1 remote monitoring support for z/OS based IBM Content Manager V8 and IBM Content Manager OnDemand systems had been added. As IBM ECM System Monitor does not contain z/OS Monitoring Agents these systems are being monitored from remote.

This article describes the system requirements and required configuration steps to implement monitoring for IBM Content Manager OnDemand systems (LUW / Linux, UNIX and Windows) as well as z/OS based systems.

Requirements of the IBM ECM-SM server:

Before you can configure and activate the monitoring for CMOD systems please verify whether all required ECM-SM server requirements are fulfilled:

Required products and versions:

• IBM ECM System Monitor 5.1

• IBM ECM System Monitor 5.1 Fixpack 2

• IBM ECM System Monitor 5.1 Fixpack 2 IF8 (required only for monitoring of z/OS based CMOD environments)

Requirements for Monitoring of LUW-based CMOD server:

Before you can configure and activate the monitoring for Linux, UNIX or Windows based CMOD systems please verify whether the following required ECM-SM agent requirements are fulfilled:

• IBM ECM-SM CALA_REX Agent installed and configured locally on the CMOD server(s) Note: Use the CALA_REX agent installation image from the ECM-SM Version 5.1 Fixpack 2 server installation. See Install Guide for CALA_REX agent installation details.

The ECM-SM Monitoring agent installation step processed later requires CMOD components locally on the system, which are used by the monitors. Please verify the installation location and status of the following components / tools:

• OnDemand Installation directory

• OnDemand Web Enablement Kit (ODWEK)

• RDBMS installation (DB2, MSSQL or Oracle installation including JDBC driver files for the appropriate DB vendor)

• Optionally: OnDemand Full Text Search (FTS) server installation


Requirements for z/OS based CMOD environments:

As IBM ECM System Monitor does not provide an agent for the z/OS platform all monitoring functionality is done from a remote system. Therefore the ECM-SM agent architecture has to be installed on a supported platform (Windows, Linux, UNIX), further called ‘virtual CMOD’ Server.

To be able configure and use all existing z/OS CMOD-related monitoring-functionality the following OnDemand and Database related components are required on the ‘virtual CMOD’ server as well:

• DB2 JDBC driver files for z/OS installed (copied) to the ‘virtual CMOD’ server (Note: use a appropriate version of the drivers files. File names are: db2jcc.jar and db2jcc_license_cisuz.jar)

• ODWEK (OnDemand Web Enablement Kit) installed on the ‘virtual CMOD’ server

On the so called ‘virtual CMOD’ system the following ECM-SM component has to be installed and configured, too:

• IBM ECM-SM CALA_REX Agent installed and configured locally on the CMOD server(s) Note: Use the CALA_REX agent installation image from the ECM-SM Version 5.1 Fixpack 2 server installation. See Install Guide for CALA_REX agent installation details.

ECM-SM Server/s

ECM-SM Agent installed on managed system, representing a ‚virtual CMOD‘ system

Remote monitoring of CMOD on z/OS IP

connection required


The following communication requirements have to be fulfilled between the z/OS based CMOD server and the ‘virtual CMOD’ server:

• Requires IP communication

• Open ports for JDBC communication (ask your administrator for the port numbers)

• Open ports for ODWEK communication (ask your administrator for the port numbers)

Step by step guide:

1. Open the ECM-SM ECM Core Agents Installation Manager from the ECM-SM Web Console Tools menu.

Note: Use an administrative ECM-SM account to run this task.

2. Once started select the ‘Configure IBM CM v8, CMOD, CSx and IIDE…’ Button.


3. Start with the creation of your System. Finish the configuration for all your connected CMOD Servers etc. in the “Infrastructure” tab except for the z/OS Servers. Define the settings for all host and environments.

Hosts tab example:

WebEnvironment tab example:

4. Now switch to the “Product Configuration” tab and select the CMOD sub-tab to define the

CMOD Servers related settings. This configuration step is either required for all of your

CMOD server(s) or through the ‘virtual CMOD’ server for the z/OS based CMOD system.

The following examples will help you to configure monitoring for either CMOD systems

running in the distributed world (UNIX, Linux or Windows) or for z/OS based CMOD system

monitored through a “virtual” system.


Upper part of the parameters for a remotely monitored z/OS CMOD system:

Upper part of the parameters for a CMOD system on Windows using DB2 as local database

system:


Description of all parameters (LUW and z/OS based CMOD systems):

The parameter called ‘Server’ is the name of the “virtual” server where the monitoring agent is

installed on and where the OnDemand configuration of ECM-SM has to be configured on. In

the case of a local LUW-based system this is the name of the CMOD server.

The parameter “OnDemand Install Path” normally points to the OnDemand Server installation

directory. This parameter can be left unset for “virtual” servers that monitor remote z/OS

systems. Note: Please use forward slashes (/) instead of backslashes (\) on Windows, too.

The OS (Operating system) user parameter is not required in the case of remote z/OS based

monitoring (even if the “virtual” server is a UNIX or Linux system) and for Windows based

CMod servers. This parameter is only required for UNIX/Linux based CMOD servers.

Specify the OnDemand Logon user and corresponding password in the case you want to use

ODWEK based logon to a local or remote CMOD system (ODWEK installation directory and

port parameters specified in the lower part of the configuration windows). This user is used for

the monitors “OnDemand Logon Status”, “OnDemand API Logon Perf” and “OnDemand

Syslog Errors” monitors. Important note: ECM-SM does not support passwords containing

any of the following characters: $,;#\&/”. Please adjust the user password if this is the case.

Select the database type used by CMOD. Note: Only DB2-based z/OS OnDemand

installations are supported at the moment. LUW-based CMOD installation support DB2,

MSSQL and Oracle.

Check the box ‘OnDemand on z/OS’ for remote z/OS monitoring, otherwise leave it

unchecked.

The parameter ‘Database path’ should contain either the installation path of the database or the

Java installation path. In the case of a local installation using the Database vendor specific tool

to access the CMOD database this parameter should point to the Database installation

directory. In the case the database should be remotely monitored (either a z/OS based DB2 or

any other remote Database used by a UNIX, Linux or Windows CMOD installation) the

parameter ‘Database path’ should contain the path to the Java installation to be used. In the

case the Java-JDBC-based communication is used/required the next parameter ‘Database

Library path’ is not required and will be ignored. Note: It is recommended to use the JRE

installation the ECM-SM agent provides. Note: Please use forward slashes (/) instead of

backslashes (\) on Windows, too.


The ‘Database name’ normally is the name of the OnDemand archive, for instance called

‘ARCHIVE’. Note: For DB2 on z/OS the Database Name is the database location name.

The ‘Database instance name’ parameter is used by the DB2 database monitors to connect to

the local or remote DB2 (on z/OS. For DB2 on z/OS the JDBC access is used. The syntax is:

<dbserver>,<jdbcdriverpath>,<dbport>,<driverclass>,<jdbcurl>

Example:

SYS1.MVS.ABC.COM,F:/Software/db2_jdbc_v10,446,com.ibm.db2.jcc.DB2Driver,jdbc:db2

://SYS1.MVS.ABC.COM:446/SYS1

The JDBC URL must contain the database name (in the example SYS1, not the database

location name).

Specify the “Database user” and corresponding password to monitor the database. This user is

used for logon directly to the database. This Database user is used to monitor all CMOD

related database monitors. For Database access details have a look at the ECM-SM monitoring

guides. Note: DB2 on z/OS based installations use this monitor to run the DB2 Database

Status and DB2 Tablespace Status monitors. These monitors need read access to the DB tables

SYSIBM.SYSDATABASE and SYSIBM.SYSTABLESPACE


In the lower part of the configuration window the following parameters have to be specified:

The ‘Java Install Path’ parameter should point to the directory where an appropriate JRE

version 6 is located. It is recommended using the ECM-SM agent JRE installation as described

above. Note: Please use forward slashes (/) instead of backslashes (\) on Windows, too.

The ‘Jar Files’ parameter should contain the required Database JDBC driver file(s). The

example shows the IBM DB2 jar files to connect to the remote z/OS based DB2 server. Check

the Installation guide for details about the required JDBC driver files(s) for DB2 LUW,

MSSQL or Oracle. Note: The DB2 LUW jar files are: db2jcc.jar and db2jcc_license_cu.jar,

the DB2 for z/OS jar files are: db2jcc.jar and db2jcc_license_cisuz.jar. Don’t forget and add

the fill qualified path to both jar-files.

The JDBC URL parameter should contain the full qualified Database JDBC URL that should

be used by the Database reader component to read the SL2 database table. In the case this

parameter is not specified the SL2 (SLX) database table reader won’t be configured on the

system. Note: The OnDemand system log errors can also be monitored using the “OnDemand

Syslog Errors” monitor, the JDBC URL can be left empty in that case, the ODWEK parts must

be configured instead. Check the Installation guide for details about the required JDBC URL

parameter for DB2, MSSQL and Oracle.

The TWO_TASK variable is only used for Oracle based CMOD installations.

In the case you are specifying a remote monitored z/OS CMOD system specify the Remote

System name and the Remote IP address (IP version 4). Note: The events / messages from

your remote CMOD system will be displayed under the name and IP address you specify with

these parameters.


If your system contains a TSM (Tivoli Storage Manager) component you want to monitor

check the appropriate checkbox and specify the TSM installation path, otherwise leave both

unchecked.

In the case you want to monitor different thresholds and values through the ODWEK API

please specify the ODWEK installation path and port with the next two parameters. Note:

Please use forward slashes (/) instead of backslashes (\) on Windows, too. In the case you want

to remotely monitor a z/OS-based CMOD system based on ODWEK the ODWEK installation

has to be done on the ‘virtual CMOD server’, since all monitors that leverage the ODWEK

API run locally from this ‘virtual CMOD System’ against the remote host. In this case you

have to specify the ODWEK installation path and the port, too.

In the case you plan to run Listener based ODWEK monitors (supported starting with CMOD

version 9.0) the following 2 Parameters (Listener name and Listener port) are required.

Normally you do not have to adjust the default settings displayed.

In the case you want to monitor the IBM OnDemand Full Text Search server (new with

CMOD version 9) please specify the CMOD FTS installation directory, too. Note: Please use

forward slashes (/) instead of backslashes (\) on Windows, too.

5. Once all parameters are specified press the ‘OK’ button, the configuration window will close automatically.

6. Press the ‘Save Configuration’ button to store the settings on the ECM-SM server.

7. Press the ‘Install client…’ button from the Installation Manager window to initialize the installation of the monitoring agent on the CMOD server / the ‘virtual CMOD’ server

8. Select the CMOD Server / ‘virtual CMOD’ server you want to install from the list of available servers. Note: only systems having a installed IBM ECM-SM CALA_REX Agent’ running are listed here. Press the ‘Ok’ once the server selection is done.

9. Proceed with the installation described in the ECM-SM Installation guide.

ibm ecm system monitor: monitoring ondemand on unix, … · 2014-04-14 · now switch to the...

Documents