As a rule, the application monitoring capability of your applications is ensured by using application monitoring-enabled components. Additional configuration is not required.
Notes:
The various environments and their requirements are listed below.
z/OS Batch and CICS RPC Server
The application monitoring-enabled components are loaded
automatically. Configuration is not required. Make sure to use EntireX Version
9.0 or above.
Natural RPC Client and Server for z/OS
Natural RPC supports application monitoring with Natural Version
8.2.3 or above for z/OS in all supported Natural environments. To enable
application monitoring for Natural RPC on z/OS, install the required load fix
for the appropriate Natural version. For the exact names of the load fix, see
Prerequisites for
Application Monitoring.
Make sure that an EntireX Broker stub of EntireX Version 9.0 or above
is used and that the EXX load library of EntireX Version 9.0 or above is part
of your steplib chain. We recommend the usage of EntireX Broker stub
NATETB23 for all of your Natural RPC environments and a Natural
configuration allowing a dynamic load of the stub. This can be achieved by
using the following Natural parameters:
RCA=(BROKER) RCALIAS=(BROKER,NATETB23)
If your EntireX Broker stub is statically included, a re-link of the Natural nucleus is required.
Natural RPC Client and Server for UNIX and Windows
Natural RPC supports application monitoring with Natural Version
6.3.14 or above for UNIX and Windows. To enable application monitoring for
Natural RPC on UNIX or Windows, install the appropriate Natural version.
Make sure that an EntireX Broker stub of EntireX Version 9.0 or above is used.
XML/Soap Listener and RPC Server, Java RPC Client and
Server
Make sure that EntireX Java runtime (entirex.jar)
Version 9.0 or above is installed on your system.
.NET RPC Client and Server
Make sure that EntireX runtime Version 9.0 or above is installed on
your system.
EntireX Adapter
Make sure that the EntireX Adapter is of Version 9.0 or above.
