This document covers the following topics:
For infrastructure monitoring of Software AG's enterprise products with webMethods Optimize for Infrastructure, specific components are required and specific prerequisites must be met. This is described in the topics below.
The following components are required on the monitoring platform:
webMethods Optimize for Infrastructure.
Optional, only if an EntireX Broker is not yet available in the customer environment: EntireX Broker.
An existing EntireX Broker can be used instead.
Optional, only if the Optimize API for Natural is to be used: Web Service Data Collector of Optimize.
Note:
A Broker is required to monitor Adabas, Natural and related
products. The Broker attribute
MAX-MESSAGE-LENGTH should be set to greater than
or equal to 60000.
After download and installation of webMethods Optimize, use the Central Configuration tool to select the metadata definition for the Software AG enterprise product groups which are to be monitored. You can load the following metadata packages (the name in parentheses is the related package name):
Adabas Definitions (AdabasDC). This comprises the Adabas-related monitoring objects and Entire Net-Work for mainframes.
Adabas SOA Gateway Definitions (SOAGatewayDC).
ApplinX Definitions (ApplinXDC).
Com-plete Definitions (CompleteDC).
EntireX Definitions (EntireXDC).
Natural Definitions (NaturalDC). This comprises the Natural-related monitoring objects.
Natural Ajax Definitions (NaturalAjaxDC).
For detailed information on the Central Configuration tool, see the Configuring BAM guide.
The following components are required on the monitored platform:
Monitored product/component.
EntireX Mini Runtime (Broker stubs).
Notes:
Supported mainframe platforms:
z/OS
z/VSE
BS2000/OSD
Supported Open Systems platforms:
Windows Server
AIX
HP-UX
Solaris
SUSE Linux
Red Hat Linux
If an EntireX Broker is not available, an EntireX Broker for the Natural RPC communication must be installed. The Broker can be downloaded and installed using the Software AG Installer 9, for the same platform on which Optimize for Infrastructure is installed.
For installation details, see the EntireX installation documentation.
If EntireX is not available on one of the monitored platforms, the EntireX Broker stubs (EntireX Mini Runtime) must be installed.
Depending on the platform to be monitored, the Broker stubs for z/OS, z/VSE or BS2000/OSD need to be installed from the EntireX package which is part of the delivery.
There is no need to set up EntireX via SMA. Only the library needs to be installed. You can simply generate the JCL for downloading the library from the Tape function of the SMA main menu.
It is recommended to set up the Natural RPC environment for using the TCP transport method and loading the stubs dynamically. For further information, see Preparing Your Application to Perform Broker Calls.
For UNIX and Windows platforms, the EntireX Mini Runtime can be downloaded and installed from Software AG's Empower site at https://empower.softwareag.com/. For configuration details, see the readme file which is provided with the mini runtime.
For the monitored products, no specific installation steps are required. For the installation or updates, refer to the particular documentation. In general, all versions of a product which are supported by Software AG can be monitored by Optimize. If not all versions of a product are supported by Optimize, the version which is at least required is listed in the topics below. Some products have additional prerequisites which are also described.
For Adabas Version 8.1.4, the following Zaps must be applied:
z/OS: AO814007, AO814008, AO814009 and AO814011.
z/VSE: AD814010.
For Adabas Version 8.2.2, the following Zaps must be applied:
z/OS: AO822011, AU822011, AU822018.
z/VSE: AU822011, AU822018.
BS2000/OSD: AB822011, AB822023, AU822011, AU822018.
If Adabas is to be monitored under BS2000/OSD:
For the generation of the Natural front end, use the setting
ADACOM=ADABAS.
Set the following NATPARM parameter:
CSTATIC=(...,ADATMZ,...)
Use the following job card for the Natural startup job deck:
/SET-FILE-LINK DDLIB,$PRD.ADA822.MOD
Or if the old ISP format is used:
/FILE $PRD.ADA822.MOD,DDLIB
The ADALNK and SSFB2C should not be
bound to the Natural front end. Bind the Natural front end with
ADAUSER and TMZLOD instead. For example:
INCLUDE ADAUSER ,$PRD.ADA822.MOD INCLUDE TMZLOD ,$PRD.ADA822.MOD
For Adabas Version 8.2.3, copy the element TMZLOD(R)
in ADA823.BS2LX01 into the Adabas library.
When running in a clustered environment, Entire Net-Work must be installed. Otherwise, the monitoring data from the cluster nuclei cannot be collected for the database totals.
For Adabas or Entire Net-Work monitoring, link the
AOSASM module to the Natural nucleus of the RPC server.
Only databases of Adabas Version 6.1 or above can be monitored.
One of the following is required on the monitored platform. The databases need not be upgraded.
Adabas Version 6.1.10 Fix 4 and the Adabas Client Package Version 6.2.1.
Adabas Version 6.3.
On UNIX, the following is required:
$ADADIR/$ADAVERS/lib must be defined in
LD_LIBRARY_PATH. It is not set automatically.
For Adabas Client Version 6.3.1.8, the module
libsagovo5.so has to be copied from
$ADADIR/$ADAVERS/lib into $ACLDIR/ACLVERS/lib.
Notes:
Client add-on product (such as Adabas Fastpath or Adabas Transaction Manager) Version 8.1.2 with the latest service packs.
If Adabas client add-on products are to be monitored, Natural
Security must be configured in such a way that the Natural RPC server has
access to the library SYSMWnnn, where
nnn is the Adabas version.
Adabas Event Replicator Version 3.2.1
The following Zaps must be applied:
Adabas Event Replicator Version 3.2.1: AZ321021 and AAZ321022.
Adabas Review Version 4.6.1.
The following Zaps must be applied:
AO813059, AO814029, AO822027.
Adabas SOA Gateway Version 2.4.1.
Com-plete Version 6.7.
For monitoring Com-plete: install the Com-plete HTTP server.
Entire Net-Work Version 6.2.1.
The following Zaps must be applied:
Entire Net-Work Version 6.2.1: WY621001 and WM621006.
Entire Net-Work Version 6.2.2: WY622001.
Entire Net-Work Version 6.3.1: WY631001.
Note:
The Entire Net-Work Zaps must be applied if a password different
from ALL is to be set.
Entire Operations Version 5.3.1 Cumulative Fix 3.
Entire Output Management Version 3.3.1.
Entire System Server Version 3.5.1.
If Entire System Server Version 3.4.1 is installed, the following Zap must be applied:
XC72033 for z/OS
XC72040 for z/VSE
This is regardless of whether you plan to monitor Entire System Server nodes or not. Otherwise, it may happen that Entire System Server nodes are included in the list of Adabas servers.
Natural Version 8.2.3 Fix 2.
The following Zaps must be applied:
NA93074
NA93075
Note:
For a list of products monitored through the Natural Optimize
Monitor Buffer Pool, see Natural >
Mainframe in the section Product-Specific
Environment Configuration.
Natural Version 6.3.13 for UNIX.
Natural Version 6.3.13 for Windows.
One of the following Natural Development Server versions:
z/OS: Natural Development Server Version 2.2.7.
z/VSE: Natural Development Server Version 2.2.7 Fix 3.
BS2000/OSD: Natural Development Server Version 2.2.7 Fix 6 or Natural Development Server Version 8.2.2 Fix 2; and Smarts Version 2.7.2 PL20.
Natural for Ajax Version 8.2.1.
One of the following Natural Web I/O Interface versions:
z/OS: Natural Web I/O Interface Version 1.1.6.
z/VSE: Natural Web I/O Interface Version 1.1.6 Fix 3.
BS2000/OSD: Natural Web I/O Interface Version 1.1.6 Fix 6 or Natural Web I/O Interface Version 8.2.2 Fix 2; and Smarts Version 2.7.2 PL20.
All supported versions.
All supported versions.
Configure your products and your environment as described in the Configuration part of this documentation.
For products that are monitored using a Natural RPC server: Start a
Natural session, log on to SYSEDM, invoke the Natural program
MENU and discover all objects. You should get a list of all
Natural and Adabas objects which can be monitored from within this Natural
session. For detailed information, see Testing the Adabas and Natural Data
Collectors later in this documentation.
For products that are monitored directly: Use a browser to access the system on which your Infrastructure Data Collector is installed and check the result. For detailed information, see Testing the Infrastructure Data Collector later in this documentation.
Define assets in the webMethods discovery function and perform a discovery. The result "completed" means that the product could be called successfully.
Go to the Monitored Components page and select the objects and KPIs for monitoring.
Note:
For detailed information on how to add assets and how to monitor
components, see the Administering webMethods Optimize
guide.
