This document lists EntireX RPC servers and EntireX listeners:
This section lists EntireX RPC server components. They can be accessed by RPC clients. For Natural RPC servers, see your Natural documentation.
EntireX RPC Server | z/OS | UNIX | Windows | z/VSE | BS2000 |
---|---|---|---|---|---|
RPC Server for XML/SOAP | More info (1) | More info | More info | ||
RPC Server for CICS ECI | More info (1) | More info | More info | ||
RPC Server for CICS Socket Listener | More info (1) | More info | More info | ||
RPC Server for IMS Connect | More info (1) | More info | More info | ||
RPC Server for Java | More info (1) | More info | More info | ||
RPC Server for IBM MQ | More info (1) | More info | More info | ||
RPC-ACI Bridge | More info (1) | More info | More info | ||
RPC Server for AS/400 | More info | More info | |||
RPC Server for Micro Focus | More info | ||||
RPC Server for C | More info | More info | |||
RPC Server for .NET | More info | ||||
RPC Server for CICS | More info | More info | |||
RPC Server for Batch | More info | More info | More info | ||
RPC Server for IMS | More info |
Notes:
This section lists EntireX listener components. They extend access to RPC servers for clients that are not RPC-based.
EntireX Listener | z/OS | UNIX | Windows | z/VSE | BS2000 |
---|---|---|---|---|---|
Listener for XML/SOAP | More info (1) | More info | More info | ||
Listener for IBM MQ | More info (1) | More info | More info |
Notes:
RPC servers are important components of EntireX RPC Technology. They are accessed by RPC clients.
The EntireX Adapter is fully integrated into the RPC technology. Through an Integration Server service, the adapter works as an RPC client. Using an Integration Server listener, it acts as an RPC server calling an IS service. This means that every endpoint supported by EntireX can be accessed from Integration Server.
An RPC server calls the requested server implementation. The Software AG Designer tool you choose depends on your scenario. For example:
to extract existing server implementations, use an IDL Extractor (COBOL | Integration Server | PL/I | WSDL | XML Document | XML Schema)
to generate a new server implementation, use an EntireX Wrapper (C | COBOL | DCOM | .NET | Java | PL/I | XML/SOAP)
the RPC-ACI Bridge calls the server implemented using ACI-based Programming
Listener components connect clients that are not RPC-based (XML/SOAP, IBM MQ, etc.) to an RPC server. See EntireX RPC Servers.
EntireX listeners are components listening on a port using a protocol other than RPC. Incoming requests on the non-RPC listening port are forwarded to an RPC server (see EntireX RPC Servers) using RPC Technology. In this way, an EntireX listener extends the access to RPC servers for clients that are not RPC-based, such as IBM MQ, XML/SOAP, etc. The Designer tool you choose depends on your scenario. For example:
to extract from an existing interface, use an IDL Extractor (WSDL | XML Document | XML Schema)
to expand an existing server implementation where you have a Software AG IDL file, use the XML/SOAP Wrapper
etc.