You can monitor distributed application scenarios that make use of the following components:
z/OS | UNIX | Windows | z/VSE | BS2000 | |
---|---|---|---|---|---|
EntireX Broker (1) | x | x | x | x | x |
Listener for XML/SOAP | x | x | x | ||
EntireX Adapter (2) | x | x | |||
Java RPC Client | x | x | x | ||
.NET RPC Client | x | ||||
Natural RPC Client | x (3) | x | x | x | |
COBOL RPC Client | x | x | |||
C RPC Client | x | x | |||
Natural RPC Server | x (3) | x | x | x |
In addition, all EntireX RPC Servers support application monitoring. See EntireX RPC Servers.
Notes:
EntireX RPC Connection
EntireX Direct RPC Connection
EntireX RPC Listener Connection
EntireX Direct RPC Listener Connection
IMS Connect Connection
CICS ECI Connection
CICS Socket Listener Connection
AS/400 Connection
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 broker stub is statically included, you will need to relink your Natural nucleus.