This document covers the following topics:
This document describes the product-specific configuration of the environments that are used for monitoring the enterprise product lines.
Any product or associated subproduct can only be monitored if the required version is installed in your environment. For information on the required versions, see Prerequisites.
In general, a component discovered by a specific RPC server will be monitored by the same RPC server. Any restrictions regarding RPC server settings described in here apply in the same way for discovery as for monitoring.
A single Natural RPC server can be used to monitor components of both Adabas and Natural by specifying the same RPC server in the Adabas asset definition and in the Natural asset definition in the Optimize discovery. For monitoring multiple instances of some components, it may be necessary to set up multiple RPC servers. For example, if Natural Review is to be monitored in multiple CICS environments, an RPC server must run in each CICS. The sections below describe for each product which RPC servers are required for the monitoring.
For each RPC server monitoring Adabas or Natural components, one instance of the "Adabas Collector" or "Natural Collector" product component is automatically created. The collector component monitors the monitoring itself. The "Collector State" KPI indicates whether the collector has been reached. If it is "offline", the connection from Optimize to the "Adabas Collector" or "Natural Collector" must be checked and re-established. Therefore, it is strongly recommended that you keep an eye on the corresponding rules (Adabas or Natural Collector not reached).
The following table lists all monitored product components and the asset type to which the component belongs.
| Product Component | Asset Type |
|---|---|
| Adabas Caching Facility | Adabas |
| Adabas Delta Save | Adabas |
| Adabas Event Replicator | Adabas |
| Adabas Event Replicator - Destination | Adabas |
| Adabas Event Replicator - Input Queue | Adabas |
| Adabas Event Replicator - Subscription | Adabas |
| Adabas Fastpath | Adabas |
| Adabas Fastpath - Database | Adabas |
| Adabas Review | Adabas |
| Adabas SAF Security | Adabas |
| Adabas Server (Mainframe) | Adabas |
| Adabas Server (UNIX and Windows) | Adabas |
| Adabas SOA Gateway | Adabas SOA Gateway |
| Adabas SOA Gateway Operation | Adabas SOA Gateway |
| Adabas Transaction Manager | Adabas |
| Com-plete | Com-plete |
| Data Collector - Adabas | Adabas |
| Data Collector - Natural | Natural |
| Entire Net-Work | Adabas |
| Entire Operations | Natural |
| Entire Operations - Task | Natural |
| Entire Output Management | Natural |
| Entire Output Management - Monitor Task | Natural |
| Entire Output Management - Printer | Natural |
| Entire System Server | Natural |
| Natural Advanced Facilities - Spool | Natural |
| Natural Advanced Facilities - Printer | Natural |
| Natural Buffer Pool (Mainframe) | Natural |
| Natural Buffer Pool (UNIX and Windows) | Natural |
| Natural CICS | Natural |
| Natural CICS - Thread Group | Natural |
| Natural Connection | Natural |
| Natural Development Server | Natural |
| Natural for Adabas | Natural |
| Natural for Ajax - Server | Natural Ajax |
| Natural for Ajax - Web Context | Natural Ajax |
| Natural for DB2 | Natural |
| Natural for VSAM | Natural |
| Natural Nucleus | Natural |
| Natural Optimize | Natural |
| Natural Review | Natural |
| Natural Roll Server | Natural |
| Natural RPC | Natural |
| Natural SAF Security | Natural |
| Natural Security | Natural |
| Natural SQL Gateway | Natural |
| Natural Swap Pool | Natural |
| Natural Web I/O Interface - Server | Natural |
| Software AG Editor | Natural |
| webMethods ApplinX - Server | ApplinX |
| webMethods ApplinX - Application | ApplinX |
| webMethods ApplinX - Service | ApplinX |
| webMethods EntireX - Broker | EntireX |
| webMethods EntireX - Server | EntireX |
| zIIP Enabler for Natural | Natural |
In the following sections, the products are listed according to their asset types.
The following topics are covered below:
A Natural RPC server monitors the databases and associated subproducts, the Fastpath buffer and Entire Net-Work nodes of one SVC entry of one LPAR. It is recommended to use a batch RPC server for this task.
The SVC number is derived from the database that is used for the
FNAT of the current Natural session. The name of the LPAR is the
one in which this Natural session actually runs.
The following components are monitored:
Adabas Server
Adabas Caching Facility
Adabas Delta Save
Adabas Event Replicator
Destination
Input Queue
Subscription
Adabas Fastpath
Database
Adabas Review
Adabas SAF Security
Adabas Transaction Manager
Entire Net-Work
Adabas Data Collector
If an implicit discovery is to be performed, the load library of
Adabas Version 8.1.4 or higher is required on the monitored platform, and the
latest ADATMZ delivered in the LX library ADA814LX02.
There is no need to upgrade the databases.
Implicit discovery of Adabas Review requires ADATMZ and
ADALNKR of Adabas Version 8.2.3.
Implicit discovery on BS2000/OSD requires Adabas Version 8.2.2.
If the Adabas Version 8.1.4 (or higher) load library (or the latest
ADATMZ and ADALNKR members) is not present, the
objects that are to be monitored can be explicitly specified in the
Adabas/Natural Data Collector
profile.
To get a higher resolution for the KPI CPU Time of an Adabas server, apply AN822285, AN823161, AN824095 or AN825030 for the appropriate Adabas version.
One Natural RPC server monitors one Adabas environment (ADABAS.INI file). All Adabas servers of Adabas Version 6.1 and above can be monitored if they were created with the workbench. It is required that the Adabas server is online during the discovery process.
The following Adabas components are monitored:
Adabas Server
Adabas Data Collector
Monitoring of the following Adabas Server space KPIs requires at least Natural Version 6.3.14 and at least Adabas Version 6.3.1 with hotfix 10:
Space - ASSO Used
Space - ASSO Used (Large Blocks)
Space - ASSO Used (Small Blocks)
Space - DATA Used
Space - DATA Used Largest
Monitoring requires no specific environment. There is a one-to-one correlation between the asset and the Adabas SOA Gateway.
The following components are monitored:
Adabas SOA Gateway
Operation
Important:
For monitoring the Adabas SOA Gateway, the Server
Stats collection option must be set to On in
the SOA Gateway Control Center. You find this option in the
Properties view for the selected server, on the
Statistics tab.
See also Infrastructure Data Collector Configuration.
Monitoring requires no specific environment. There is a one-to-one correlation between the asset and the ApplinX server.
The following components are monitored:
ApplinX - Server
Application
Service
Monitoring requires no specific environment. There is a one-to-one correlation between the asset and Com-plete.
The following component is monitored:
Com-plete
See also Infrastructure Data Collector Configuration.
Monitoring requires no specific environment. There is a one-to-one correlation between the asset and one EntireX Broker.
The following components are monitored:
EntireX - Broker
Server
See also Infrastructure Data Collector Configuration.
The products and components listed below are monitored by the Natural Data Collector. Therefore, you have to set up a Natural asset if it has not already been set up for another Natural component.
The following topics are covered:
With Natural 8.2.1 on z/OS, Natural 8.2.3 on z/VSE and Natural 8.2.4 on BS2000/OSD, the Natural Optimize Monitor Buffer Pool has been introduced, which collects statistical data of Natural components. The Natural Optimize Monitor Buffer Pool is able to monitor all component instances running in one LPAR. Therefore, only one batch RPC server per LPAR is required for all of these components.
For information on how to start the Natural Optimize Monitor Buffer
Pool, see Optimize Monitor Buffer Pool in the
Operations documentation which is part of the Natural for
Mainframes documentation. The data collection of the Natural Optimize Monitor
Buffer Pool is activated with the Natural parameter O4I=ON.
The following products and components do not use the Natural Optimize Monitor Buffer Pool for data collection and are monitored without it:
Natural
Natural Roll Server
Natural Advanced Facilities
Spool
Printer
Natural Review
Natural SAF Security
Entire Operations
Task
Entire Output Management
Monitor task
Printer
Entire System Server
Natural Data Collector
The following products and components can only be monitored with the Natural Optimize Monitor Buffer Pool:
Natural
Natural for Adabas
Natural Nucleus
Natural Optimize
Natural Connection
Natural for DB2
Natural for VSAM
Natural RPC
Natural SQL Gateway
zIIP Enabler for Natural
The following products and components are monitored with the Natural Optimize Monitor Buffer Pool if the used Natural version supports this feature in general. If the Natural Optimize Monitor Buffer Pool is not activated or in error, the component will neither be discovered nor monitored. If the Natural version does not support the Natural Optimize Monitor Buffer Pool, the products and components are monitored without it.
Natural
Natural buffer pool
Natural swap pool
Software AG Editor
Natural CICS
Thread group
Natural Development Server
Natural Security
Natural Web I/O Interface (server)
Note:
In Optimize, the Software AG Editor is referred to as Natural
Editor, and the zIIP Enabler for Natural is referred to as Natural zIIP.
Natural Review is the only product requiring a CICS RPC server. All other Natural products and components are monitored by default by a batch RPC server only. This is because a CICS RPC server would be unable to monitor the components when CICS is not active.
For test environments, a parameter is available which allows monitoring all Natural components from a CICS RPC server. See Adabas/Natural Data Collector Profile for more information.
Natural local components (such as local buffer pools) can only be monitored by an RPC server in the same environment. Natural global components (such as global buffer pools) are monitored by default by a batch RPC server only. This is because a CICS RPC server would be unable to monitor the components when CICS is not active.
For test environments, a parameter is available which allows monitoring Natural global components from a CICS RPC server. See Adabas/Natural Data Collector Profile for more information.
A CICS Natural RPC server monitors the following products and local components:
Natural
Local Natural buffer pool
Natural swap pool
Software AG Editor (using a local editor buffer)
Natural CICS
Thread group
Natural Review
Natural Data Collector
A batch Natural RPC server monitors the following products and components:
Natural
Natural buffer pool
Natural Roll Server
Natural swap pool (BS2000/OSD)
Software AG Editor
Natural Advanced Facilities
Spool
Printer
Natural Development Server
Natural SAF Security
Natural Security
Natural Web I/O Interface (server)
Entire Operations
Task
Entire Output Management
Monitor task
Printer
Entire System Server
Natural Data Collector
Note:
In Optimize, the Software AG Editor is referred to as Natural
Editor.
The following Natural products and components are monitored:
Natural
Natural buffer pool
Natural Security
Entire Operations
Task
Entire Output Management
Monitor task
Printer
Natural Data Collector
The Natural Data Collector is a Natural-written component of Optimize for Infrastructure. It collects the Natural-related data on the server side. A Natural Collector instance is automatically created for each RPC server monitoring a Natural asset.
Monitoring Entire Operations requires a batch RPC server. In general,
the Entire Operations system file (LFILE 216) used by the Natural
RPC server is monitored. Additional system files are monitored if they are
specified in the Adabas/Natural Data
Collector profile.
Monitoring Entire Output Management requires a batch RPC server. In
general, the Entire Output Management system file (LFILE 91) used
by the Natural RPC server is monitored. Additional system files are monitored
if they are specified in the Adabas/Natural Data Collector profile.
Monitoring Entire System Server requires a batch RPC server. The
Natural RPC server must be started with the settings ASIZE > 0,
DB=(PROCESS,148) and the Natural nucleus must be linked with
NATGWNPR.
The implicit discovery of Entire System Server nodes requires the
member ADATMZ. For more information on this member, see the
information provided for Adabas. Additional Entire System Server
nodes are monitored if they are specified in the
Adabas/Natural Data Collector
profile.
Note:
Some Entire System Server KPIs are not available under
BS2000/OSD.
Monitoring Natural Advanced Facilities requires a batch RPC server. In
general, the FSPOOL system file used by the Natural RPC server is
monitored. Additional FSPOOL system files are monitored if they
are specified in the Adabas/Natural Data
Collector profile.
Monitoring a spool file or any printer defined in the spool file requires that the user statistics of the spool file are activated. The user statistics can be activated in the Natural Spool Administration in the following way:
Enter the Natural system command SYSPOOL.
Enter "30" to invoke the function "Spool File Properties".
Enter "5" to invoke the function "Set Spool Option".
Enter "1" to invoke "Spool File Options".
If the user statistics are not activated, the KPI "Natural Spool User Statistics State" indicates "offline". In this case, no other KPIs are provided and printers cannot be monitored.
Monitoring a specific printer defined in the spool file requires that the printer statistics are activated. The printer statistics can be activated in the Natural Spool Administration in the following way:
Enter the Natural system command SYSPOOL.
Enter "31" to invoke the function "Objects".
Enter "4" to invoke the function "Printer".
Specify the printer name or enter an asterisk (*) to select a printer from a list.
Set "Statistics" to "Y".
If the printer statistics are not activated, the KPI "Printer Statistics Activated" indicates "offline". In this case, only static KPIs are provided. Especially the number of lines/pages/reports printed cannot be monitored.
Monitoring a Natural buffer pool requires a batch RPC server. It monitors all local and global buffer pools.
A local Natural buffer pool will be monitored only if the Natural RPC server is running with the local Natural buffer pool.
Monitoring a global Natural buffer pool requires a batch RPC server.
It monitors all global Natural buffer pools of the Natural subsystem
(identified by the Natural profile parameter SUBSID) in
which this RPC server is running.
If multiple local Natural buffer pools or if global buffer pools from multiple Natural subsystems have to be monitored, multiple RPC servers have to be started.
For each particular Natural buffer pool to be monitored, a Natural RPC server running with this buffer pool has to be started.
Note:
The same interface could be used to monitor a read-only buffer
pool, however, not all returned values may be meaningful. Therefore, it is not
recommended to monitor a read-only buffer pool.
Monitoring Natural CICS requires a batch RPC server. It monitors all Natural CICS components in all CICS systems.
Natural CICS with its threads can be monitored if the RPC server is running with the same Natural CICS system directory. If multiple Natural CICS systems or multiple CICS systems have to be monitored, multiple RPC servers must be set up.
Natural Connection can only be monitored with the Natural Optimize Monitor Buffer Pool. A batch RPC server is required for the monitoring.
Monitoring an NDV or NWO server requires a batch RPC server. The HTTP monitor is not required for monitoring, and the HTTP monitor state KPIs ("NdvHttpMonitorState" and "NwoHttpMonitorState") are obsolete.
Monitoring an NDV or NWO server requires a batch RPC server.
The Natural Data Collector calls an HTTP monitor to access the NDV or NWO servers. The data for Optimize for Infrastructure will be collected by the servers themselves. The HTTP monitor must be configured at the installation of an NDV or NWO server. See the corresponding configuration descriptions in the Natural Development Server documentation and in the Natural Web I/O Interface documentation (the Natural Web I/O Interface documentation is part of the Natural documentation).
An NDV or NWO server is only monitored if the host name and the port number of an HTTP monitor is specified in the Adabas/Natural Data Collector profile. Multiple NDV or NWO servers can be monitored from one Natural RPC server.
The RPC server must be configured so that it is able to perform an HTTP request (see Installation for REQUEST DOCUMENT and PARSE XML Statements in the installation documentation for Natural for Mainframes).
The monitoring of the Natural Development Server CPU time on BS2000/OSD requires SMARTS BS2000 V272 PL20 or above.
Natural for Adabas can only be monitored with the Natural Optimize Monitor Buffer Pool. A batch RPC server is required for the monitoring.
Natural for DB2 can only be monitored with the Natural Optimize Monitor Buffer Pool. A batch RPC server is required for the monitoring.
Natural for VSAM can only be monitored with the Natural Optimize Monitor Buffer Pool. A batch RPC server is required for the monitoring.
The Natural Nucleus component monitors the Natural Unicode and code
page support (ICU) and the Natural PARSE XML and REQUEST
DOCUMENT statement usage.
A Natural nucleus can only be monitored with the Natural Optimize Monitor Buffer Pool. A batch RPC server is required for the monitoring.
The Natural Optimize component monitors the Natural Optimize Monitor Buffer Pool. If the Natural Optimize Monitor Buffer Pool is deactivated or in error, the Natural products and components using the Natural Optimize Monitor Buffer Pool cannot be monitored and the Natural Optimize state KPI ("NatOptState") indicates "offline". It is therefore strongly recommended to keep an eye on the corresponding rule ("Natural Optimize Not Active") in every environment in which the Natural Optimize Monitor Buffer Pool is available. A batch RPC server is required for the monitoring of Natural Optimize.
Monitoring Natural Review requires a CICS RPC server. It monitors the
Natural CICS-environmental information collected by Natural Review. Natural
Review collects runtime statistics about all CICS Natural transactions started
with RDCSIZE greater than or equal to 2. If multiple CICS systems
have to be monitored, multiple RPC servers must be set up.
Monitoring a Natural Roll Server requires a batch RPC server. It monitors all Natural Roll Servers.
Natural RPC can only be monitored with the Natural Optimize Monitor Buffer Pool. A batch RPC server is required for the monitoring.
Monitoring Natural SAF Security requires a batch RPC server.
The implicit discovery of Natural SAF Security requires the member
ADATMZ. For more information on this member, see the information
provided for Adabas.
Additional Natural SAF Security instances are monitored if they are specified
in the Adabas/Natural Data Collector
profile.
Monitoring Natural Security requires a batch RPC server. It monitors
all Natural Security FSEC system files.
Monitoring Natural Security requires a batch RPC server. It monitors
its current FSEC system file. Additional FSEC system
files are monitored if they are specified in the
Adabas/Natural Data Collector
profile.
Natural Security collects statistical data for Optimize. The monitoring of this statistical data requires that the Natural Security statistics are activated. Optimize administrates the Natural Security statistics automatically at the monitoring call. If the statistics are found to be disabled or expired at a monitoring call, they are switched on for one day. The KPI "Natural Security State" is set to "online" but no other KPIs are provided with this first monitoring call. If the current time is close to the expiration time (2 hours or less), the expiration time is prolonged by a week. Note that an Optimize discovery does not change the Natural statistics state or expiration date.
Natural SQL Gateway can only be monitored with the Natural Optimize Monitor Buffer Pool. A batch RPC server is required for the monitoring.
Monitoring a Natural swap pool requires a batch RPC server. It monitors all Natural swap pools.
z/OS and z/VSE
A Natural swap pool can be monitored if the RPC server is running
with the same Natural CICS system directory as the Natural swap pool. If
multiple Natural swap pools have to be monitored, multiple RPC servers must be
set up.
BS2000/OSD
Monitoring the Natural swap pool requires a batch RPC server.
For the monitoring of a global swap pool, an RPC server of its own has to be set up for each swap pool that is to be monitored. For the installation of these servers, the following applies:
For the generation of the Natural RPC batch server, the front-end
part of the Natural batch driver (macro NAMBS2) has to be
assembled with the new keyword parameter KPI=SWP.
For the generation of the module BS2STUB (front-end
part of the RPC batch server), you have to define the necessary common memory
pools, including the swap pool to be monitored.
The following example shows the ADDON entry for the
global swap pool:
ADDON NAME=SWP42XGA, -
TYPE=SWP, -
STAT=GLOBAL
Note:
For swapping of its own threads, the RPC server is not able to
use the global swap pool which is to be monitored. Therefore, do not specify
KPI=SWP together with SERVER=YES.
If multiple Natural swap pools have to be monitored, multiple RPC servers must be set up.
Note:
In Optimize, the Software AG Editor is referred to as Natural
Editor.
Monitoring Software AG Editor requires a batch RPC server. It monitors all local and global Software AG Editor buffer pools.
A local Software AG Editor buffer pool will be monitored only if the Natural RPC server is running with the local Software AG Editor buffer pool.
Monitoring a global Software AG Editor buffer pool requires a batch
RPC server. It monitors all global Software AG Editor buffer pools of the
Natural subsystem (identified by the Natural profile parameter
SUBSID) in which this RPC server is running.
If multiple local Software AG Editor buffer pools or if global editor buffer pools from multiple Natural subsystems have to be monitored, multiple RPC servers have to be started.
Note:
In Optimize, the zIIP Enabler for Natural is referred to as Natural
zIIP.
The zIIP Enabler for Natural can only be monitored with the Natural Optimize Monitor Buffer Pool. A batch RPC server is required for the monitoring.
For the monitoring of Natural for Ajax, the Natural for Ajax web service for Optimize for Infrastructure must be installed. For detailed information, see the Natural for Ajax documentation.
There is a one-to-one correlation between the asset and Natural for Ajax on an application server or servlet container.
The following components are monitored:
Natural for Ajax - Server
Web context