EntireX RPC Servers and Listeners

This document lists EntireX RPC servers and EntireX listeners:


EntireX RPC Servers

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 graphics/toc_closed.png More info (1) graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC Server for CICS ECI graphics/toc_closed.png More info (1) graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC Server for CICS Socket Listener graphics/toc_closed.png More info (1) graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC Server for IMS Connect graphics/toc_closed.png More info (1) graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC Server for Java graphics/toc_closed.png More info (1) graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC Server for IBM MQ graphics/toc_closed.png More info (1) graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC-ACI Bridge graphics/toc_closed.png More info (1) graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC Server for AS/400   graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC Server for Micro Focus   graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC Server for C   graphics/toc_closed.png More info graphics/toc_closed.png More info    
RPC Server for .NET     graphics/toc_closed.png More info    
RPC Server for CICS graphics/toc_closed.png More info     graphics/toc_closed.png More info  
RPC Server for Batch graphics/toc_closed.png More info     graphics/toc_closed.png More info graphics/toc_closed.png More info
RPC Server for IMS graphics/toc_closed.png More info        

Notes:

  1. z/OS UNIX. The component is included in a TAR file in the z/OS installation kit. See Installing EntireX Java Components under z/OS UNIX in the z/OS Installation documentation.

EntireX Listeners

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 graphics/toc_closed.png More info (1) graphics/toc_closed.png More info graphics/toc_closed.png More info    
Listener for IBM MQ graphics/toc_closed.png More info (1) graphics/toc_closed.png More info graphics/toc_closed.png More info    

Notes:

  1. z/OS UNIX. The component is included in a TAR file in the z/OS installation kit. See Installing EntireX Java Components under z/OS UNIX in the z/OS Installation documentation.

Introduction to RPC Server and Listener Technology

EntireX RPC Servers

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.

graphics/intro_server.png

An RPC server calls the requested server implementation. The Software AG Designer tool you choose depends on your scenario. For example:

EntireX Listeners

Listener components connect clients that are not RPC-based (XML/SOAP, IBM MQ, etc.) to an RPC server. See EntireX RPC Servers.

graphics/intro_listener.png

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.