| Quick Reference |
This document lists RPC servers, listeners and bridges; provides an overview of zero-footprint solutions; and gives links to information for administration and installation:
For Natural RPC servers, see Setting Up a Natural RPC Environment in your Natural documentation.
RPC servers are important components of RPC Technology. They receive RPC requests from RPC clients using EntireX RPC and call the requested server implementation using RPC Wrapper technology of the EntireX Workbench. The Workbench tool you choose to extract existing servers or generate them depends on your environment. For example:
to extract existing server implementations, use an IDL Extractor ( COBOL | PL/I | webMethods Integration Server | WSDL | XML Document | XML Schema)
to generate a new RPC-based server, use a Wrapper ( Java | COBOL | PL/I | C | XML/SOAP | .NET); you can also generate RPC-based clients
A listener can be described as follows:
In terms of EntireX, a listener is a component listening on a port using a protocol other than RPC, for example IBM MQ or XML/SOAP. Incoming requests on the non-RPC listening port are forwarded to an RPC server, using RPC Technology. In this way, a listener expands the access to RPC servers to non-RPC-based clients such as IBM MQ, XML/SOAP, etc.
In terms of the webMethods EntireX Adapter for Integration Server, listening is seen from inside IS (listening for incoming requests to IS), so a listener created with the EntireX Adapter is listening for RPC.
This section lists RPC servers, listeners and bridges, and provides links to administration and installation documentation.
There are also RPC server, listener and bridge components available for z/OS UNIX. See List of Components per Platform under Platform Coverage in the Release Notes and RPC Servers, Listeners and Bridges under UNIX and Windows below.
The EntireX z/OS CICS® RPC Server allows standard RPC clients to communicate with RPC servers on the operating system z/OS under CICS. It supports the programming languages COBOL and PL/I.
For COBOL, it works together with the COBOL Wrapper and IDL Extractor for COBOL.
For PL/I, it works together with the PL/I Wrapper and IDL Extractor for PL/I.
More info
The EntireX z/OS Batch RPC Server allows standard RPC clients to communicate with RPC servers on the operating system z/OS running in batch mode. It supports the programming languages COBOL, PL/I and C and works together with the COBOL Wrapper and IDL Extractor for COBOL.
For COBOL, it works together with the COBOL Wrapper and the IDL Extractor for COBOL.
For PL/I, it works together with the PL/I Wrapper and the IDL Extractor for PL/I.
For C, use the C Wrapper.
More info
The EntireX z/OS IMS RPC Server allows standard RPC clients to communicate with RPC servers on the operating system z/OS running with IMS in BMP mode. It supports the programming languages COBOL, PL/I and C and can provide IMS-specific PCB pointers for access to IMS databases if needed.
For COBOL, it works together with the COBOL Wrapper and IDL Extractor for COBOL.
For PL/I, it works together with the PL/I Wrapper and IDL Extractor for PL/I.
For C, use the C Wrapper.
More info
Most of the RPC server, listener and bridge components are also available for a z/OS UNIX environment. See List of Components per Platform under Platform Coverage in the Release Notes.
Under Windows, an RPC server can run as a Windows Service. See Running the RPC Server as a Windows Service (C | .NET | Micro Focus | Java | XML/SOAP | IMS Connect | CICS ECI | IBM MQ | RPC-ACI Bridge).
The XML/SOAP RPC Server allows RPC clients to communicate with target servers via HTTP(S).
The XML/SOAP RPC Server transforms RPC client calls into XML/SOAP calls.
It works together with the XML/SOAP Wrapper. More info.
The EntireX XML/SOAP Listener runs in a servlet-enabled Web server with an installation of the Software AG Web Services Stack.
It plugs the Web service's archives (EntireX Workbench file with extension .aar) into Web servers.
Typically the Web service clients access the XML/SOAP Listener and send/receive XML/SOAP documents using HTTP/HTTPS.
This component was formerly referred to as "XML Servlet". More info
The EntireX Java RPC Server allows standard RPC clients to communicate with servers written in Java. It works together with
the Java Wrapper and calls Java server interface objects. See More info.
The .NET RPC Server allows standard RPC clients to communicate with .NET server assemblies. It works together with the .NET Wrapper. More info
The EntireX C RPC Server allows standard RPC clients to communicate with servers written in C. It works together with the
C Wrapper and calls standard libraries (Windows DLLs or UNIX shared objects/libraries). More info
The EntireX Micro Focus COBOL RPC Server allows standard RPC clients to
communicate with COBOL servers written with Micro Focus COBOL.
It works together with the COBOL Wrapper and the IDL Extractor for COBOL. More info
The EntireX IMS Connect RPC Server allows standard RPC clients to communicate with IMS MPP programs.
It works together with the IDL Extractor for COBOL and transforms RPC requests from clients into message to IMS, using IMS Connect. More info
The EntireX CICS® ECI RPC Server allows standard RPC clients to communicate with
CICS programs running on IBM CICS®. It supports the programming languages COBOL and PL/I and transforms the RPC requests from
clients into messages to CICS ECI. More info
The RPC Server for IBM® MQ runs as an RPC server and processes RPC client
calls. It is used
to send messages to and receive messages from an IBM MQ queue.
This means that existing EntireX wrappers can be used for communication with
IBM MQ. More info.
The Listener for IBM® MQ runs as a listener on an IBM MQ queue and passes messages to an RPC server.
It is used to send messages received from an IBM MQ queue to an RPC server application.
This means that existing RPC servers can be used for communication with IBM MQ. More info.
The EntireX RPC-ACI Bridge allows standard RPC clients to communicate with an ACI server.
The RPC-ACI Bridge transforms RPC requests from clients into ACI messages. More info.
The EntireX z/VSE CICS® RPC Server allows standard RPC clients to communicate with RPC servers
on the operating system z/VSE under CICS. It supports the programming language COBOL. More info.
The EntireX z/VSE Batch RPC Server allows standard RPC clients to communicate with RPC servers
on the operating system z/VSE under Batch. It supports the programming language COBOL and works together with
the COBOL Wrapper and IDL Extractor for COBOL. More info.
The EntireX BS2000 Batch RPC Server allows standard RPC clients to communicate with
RPC servers on the operating system BS2000.
It supports the programming languages COBOL and C. More info.
The EntireX IBM i RPC Server enables you to call server programs written in all ILE-based languages, for example C, COBOL,
RPG. More info
This section lists RPC servers and listeners with which you can access the mainframe without installing any EntireX component on the mainframe.
The EntireX CICS® ECI RPC Server allows standard RPC clients to communicate with
CICS programs running on IBM CICS®. It supports the programming languages COBOL and PL/I and transforms the RPC requests from
clients into messages to CICS ECI. More info
The EntireX IMS Connect RPC Server allows standard RPC clients to communicate with IMS MPP programs.
It works together with the IDL Extractor for COBOL and transforms RPC requests from clients into message to IMS, using IMS Connect.
The IMS Connect RPC Server acts on one side as an
RPC server and on the other side as a client for IMS Connect. The
IMS Connect RPC Server is a Java-based component that can run on a different host
to the one where IMS is running. This allows it to operate with a zero footprint
of EntireX on the IMS host. More info
The RPC Server for IBM® MQ runs as an RPC server and processes RPC client
calls. It is used
to send messages to and receive messages from an IBM MQ queue.
This means that existing EntireX wrappers can be used for communication with
IBM MQ. More info
The Listener for IBM® MQ runs as a listener on an IBM MQ queue and passes messages to an RPC server.
It is used to send messages received from an IBM MQ queue to an RPC server application.
This means that existing RPC servers can be used for communication with IBM MQ. More info
Data sets for the EntireX RPC Servers are prefixed with EXP on the installation medium. See Contents of Mainframe Installation Medium.
See also Installing EntireX Java Components under z/OS UNIX