Version 9.6
 —  EntireX Adapter Installation and User's Guide  —

Direct RPC

Direct RPC is a component that enables RPC clients and RPC servers to connect directly to the EntireX Adapter without the EntireX Broker. This document covers the following topics:


Configuring Direct RPC

To enable Direct RPC, choose Direct RPC Administration in the EntireX Adapter's administration menu and follow the wizard. The table below gives an overview of parameters to be specified:

Name Values Default Action Description
Status "Stopped", "Running" "Stopped" Start or stop. Current status of the Direct RPC component.
Logging Level "Fatal", "Error", "Warning", "Info", "Debug", "Trace" "Fatal" Change logging level. Logging level. See Notes.
TCP Port Number Port number "1971" Change port number. TCP listening port for Direct RPC.
SSL Port Number Port number - Change port number. SSL (or TLS) listening port for Direct RPC.
Keystore Alias (for SSL) The alias name of a keystore defined in the Integration Server. - Change alias name. Only needed for SSL. Defined in the IS web admin "Security > Keystore".
Auto Start Enabled, Disabled "Disabled" Enable or disable. Automatic start of Direct RPC during startup of the Adapter.

Notes:

Top of page

Encoding for RPC Clients and Servers (Default and Available Codepages)

The default encoding of an RPC client or server is the same as the default encoding of the platform used. The table below gives an overview on default and available codepages:

Platform Default Codepage Available Codepages (single byte only)
Windows/UNIX/Linux ISO 8859-1 ASCII codepages
IBM mainframe (z/OS, z/VSE) CP037 EBCDIC codepages
Fujitsu mainframe (BS2000/OSD) CP273 EBCDIC codepages

To specify the encoding of an RPC client or server, see webMethods EntireX documentation.

Top of page

Monitoring

The following table gives an overview on monitored objects:

Item Description
Servers Number of registered servers.
RPC Requests Number of RPC requests.
Socket Connections Number of plain socket connections (TCP) from RPC clients or servers.
Secure Socket Connections Number of secure socket connections (SSL or TLS) from RPC clients or servers.
Direct Connections Number of direct connections from Adapter services or Adapter Listeners.
Calls Number of calls (including calls such as logon).
Conversations Number of conversational calls.

Notes:

  1. For each item the following information is provided: Current (number of items currently active), maximum (high watermark) and total (number of activations so far).
  2. If Direct RPC connections are enabled, the value of Direct Connections can be greater than zero even if Direct RPC is stopped.

Top of page

Services

The following information is displayed for each service:

Name The name of the service
Type "External RPC Server" or "Direct RPC Server".
Instances Number of registered replicates.
Wait for Server Number of client requests that are waiting for a free server to be processed. The percentage (number of calls waiting compared to the total number of calls) is helpful in deciding if further server replicates are necessary.
Action Shutdown (only for external RPC servers).

Note:
As a prerequisite, at least one server must be registered or listener enabled.

Top of page

Servers

The following information is displayed for each service:

Service Name The name of the service
Type "Listener" or "RPC Server".
Name Name of the Direct Listener or the external RPC server.
Host Host where the external RPC Server is running.
Version Version of the external RPC server.
Action Shutdown (only for external RPC Servers).

Note:
Host, Name and Version can only be displayed if the RPC server provides this information.

Top of page

Built-in Services for Direct RPC

The functionality of Direct RPC as shown on the IS Administration Console's page is available with built-in services in the WmEntireX package. They correspond to the parameters on the IS Administration Console's page. When a service is executed, the signature of the input and output parameters is shown. The following services are available:

In addition, there are 4 services for advanced configuration of the SSL transport:

Note:
Use the setSSLClientAuthentication service to switch on SSL client authentication. Client authentication requires that a truststore alias has been set with pub.wmentirex.directrpc.admin:setTrustStoreAlias. The truststore alias is defined in the IS web admin Security > Keystore. Note that the names of the keystore alias and the truststore alias must be different.

Top of page

Limitations of Direct RPC

Top of page