Optimize for Infrastructure Version 9.8
 —  Guide for Enterprise Transaction Systems  —

Installation for Infrastructure Monitoring

This document covers the following topics:


General Information

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.

Top of page

Prerequisites for the Monitoring Platform

The following components are required on the monitoring platform:

  1. webMethods Optimize for Infrastructure.

  2. Optional, only if an EntireX Broker is not yet available in the customer environment: EntireX Broker.

    An existing EntireX Broker can be used instead.

  3. 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):

For detailed information on the Central Configuration tool, see the Configuring BAM guide.

Top of page

Prerequisites for the Monitored Platform

The following components are required on the monitored platform:

  1. Monitored product/component.

  2. EntireX Mini Runtime (Broker stubs).

Notes:

  1. For monitoring the Adabas product group and Entire Net-Work, Natural is required.
  2. EntireX Broker stubs have to be available to set up the Natural RPC server.

Supported mainframe platforms:

Supported Open Systems platforms:

Top of page

Installing the EntireX Broker (Optional)

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.

Top of page

Installing the EntireX Broker Stubs (EntireX Mini Runtime)

If EntireX is not available on one of the monitored platforms, the EntireX Broker stubs (EntireX Mini Runtime) must be installed.

Mainframe

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.

UNIX and Windows

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.

Top of page

Prerequisites for the Monitored Products

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.

Adabas - Mainframe

Adabas - UNIX and Windows

Notes:

  1. For monitoring Adabas 6.1 and 6.3, Natural Version 6.3.13 is required.
  2. Adabas Version 6.2 is currently not supported.

Adabas Client Add-On Products

Adabas Event Replicator

Adabas Review

Adabas SOA Gateway

Com-plete

Entire Net-Work - Mainframe

Entire Operations - Mainframe and UNIX

Entire Output Management - Mainframe and UNIX

Entire System Server

Natural - Mainframe

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 - UNIX and Windows

Natural Development Server - Mainframe

One of the following Natural Development Server versions:

Natural for Ajax

Natural Web I/O Interface (Server) - Mainframe

One of the following Natural Web I/O Interface versions:

webMethods ApplinX

webMethods EntireX

Top of page

Installation Verification

  1. Configure your products and your environment as described in the Configuration part of this documentation.

  2. 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.

  3. 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.

  4. Define assets in the webMethods discovery function and perform a discovery. The result "completed" means that the product could be called successfully.

  5. 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.

Top of page