You can monitor distributed application scenarios that make use of the following components:
z/OS | UNIX | Windows | z/VSE | |
---|---|---|---|---|
EntireX Broker 1 | X | X | X | X |
XML/Soap Listener | 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 | ||
XML/Soap RPC Server | X | X | X | |
Java RPC Server | X | X | X | |
Natural RPC Server | X 3 | X | X | X |
CICS RPC Server | X | X | ||
Batch RPC Server | X | X | ||
.NET RPC Server | X | |||
C RPC Server | X | X |
Notes:
EntireX RPC Connection
EntireX Direct RPC Connection
EntireX RPC Listener Connection
EntireX Direct RPC Listener Connection
IMS Connect Connection
CICS ECI 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.