Introduction to the RPC Server for AS/400


Overview

The RPC Server for AS/400 acts on one side as an RPC server and on the other side as a client for calling AS/400 server programs.

graphics/as4Rpc.png

For local extraction, all source files have to be stored locally on the same machine where the Designer is running. For existing AS/400 programs, use the Software AG IDL Extractor for COBOL to extract the Software AG IDL File for the RPC clients.

Post-installation Steps

After installation of EntireX, the EntireX RPC Server for IBM® AS/400® cannot be started successfully. To access the AS/400 system you need the IBM ToolBox for Java (JTOpen).

Start of instruction setTo download and install the IBM ToolBox for Java

  1. From http://jt400.sourceforge.net/, click Downloads. From https://sourceforge.net/projects/jt400/, select the latest version.

  2. From the downloaded zip file, extract the file lib/java8/jt400.jar.

  3. Copy the file jt400.jar to directory EntireX/Classes.

Worker Models

graphics/intro_workerModels-as4.png

RPC requests are worked off inside the RPC server in worker threads. Every RPC request occupies during its processing a worker thread. If you are using RPC conversations, each RPC conversation requires its own thread during the lifetime of the conversation. The RPC Server for AS/400 can adjust the number of worker threads to the number of parallel requests. The RPC server provides two worker models:

  • FIXED
    The fixed model creates a fixed number of worker threads. The number of worker threads does not increase or decrease during the lifetime of an RPC server instance.

  • DYNAMIC
    The dynamic model creates worker threads depending on the incoming load of RPC requests.

For configuration and technical details, see property entirex.server.fixedservers under Administering the RPC Server for AS/400.