This document describes how to administer the EntireX RPC Server for IMS Connect, using the Command Central graphical user interface. It covers the following topics:
See also Administering the RPC Server for IMS Connect using the Command Central Command Line. The core Command Central documentation is provided separately and is also available under Guides for Tools Shared by Software AG Products on the Software AG documentation website.
Open an Internet browser and specify the URL of the Command Central Server as follows: http://<Command_Central_host>:<Command_Central_port>. This takes you to the Command Central Login page.
On Windows you can also get to the Login page from the Command Central Start Menu entry.
Provide your user credentials in the Login page and click Log In. This takes you to the page Home > Instances:
To create an RPC Server for IMS Connect instance
In the Command Central home page, click the Installations tab.
Click on the desired installation, for example Local, where you want to add an RPC Server for IMS Connect instance.
Click the Instances tab.
Click the 
button in the upper right corner above the list and choose .
In the Create Instance wizard, fill in the fields in the main screen and in the Server, Broker and IMS Connect tabs.
| Parameter | Description |
|---|---|
| Instance name | Required. Name of the runtime component, for example "MyRpcServer".
|
| Register Windows Service for automatic startup | Optional. Register Windows Service for automatic startup. Default is not checked. If this parameter is checked, the RPC server can be controlled by the Windows Service Control Manager. |
| Parameter | Description |
|---|---|
| RPC Server address | Required. The case-sensitive RPC server address has the format: CLASS/SERVER/SERVICE.
|
| Administration port | Required. The administration port in range from 1025 to 65535. |
| Parameter | Description |
|---|---|
| Connection | |
| Transport | Transport over TCP or SSL. Default is TCP.
|
| Broker host | Required. EntireX Broker host name or IP address. See Using the Broker ID in Applications in the RPC Programming documentation. |
| Broker port | Required. Port number in range from 1025 to 65535. |
| SSL trust store | Optional. Specifies the location of the SSL trust store. |
| Credentials | |
| User | Optional. The user ID for secured access to the broker. |
| Password | Optional. The password for secured access to the broker. |
Here you can modify the IMS Connect settings for the RPC Server for IMS Connect.
| Parameter | Description |
|---|---|
| Connection | |
| Transport | Use TCP or SSL to communicate with IMS Connect. |
| IMS host | Host name or IP address where IMS Connect is running |
| IMS port | TCP or SSL port number where IMS Connect is listening. |
| IMS data store ID | Data store ID. Name of the IMS system that will receive transactions. |
| IMS encoding | Specify the appropriate EBCIDIC encoding used by your IMS Connect. This codepage is also used when communicating with the
EntireX Broker. Default cp037 is EBCDIC codepage with full Latin-1 character set.
|
| Credentials | |
| RACF user ID | The user ID (max. 8 chars) as defined in your underlying mainframe security system (e.g. RACF). |
| RACF password | Password (max. 8 chars) as defined in your underlying mainframe security system (e.g. RACF). |
Press to get to the Summary page to verify your input.
Press .
The new instance myRpcServer appears in the list.
To configure an RPC Server for IMS Connect instance
In the Command Central home page, click the Instances tab.
Click on the link associated with this instance to select the RPC server instance you want to configure.
Click the Configuration tab. EntireX supports the following configuration types, which are presented in a drop-down box when you click the down arrow below the Configuration tab label:
Note:
All configuration changes require a restart of the instance to take effect.
Click to modify the parameters on your selected configuration type.
Click to check the correctness of your input or to save your changes.
The configuration options are described in more detail below:
| Parameter | Description |
|---|---|
| Connection | |
| Transport | Transport over TCP or SSL. Default is TCP.
|
| Broker host | Required. EntireX Broker host name or IP address. See Using the Broker ID in Applications in the RPC Programming documentation. |
| Broker port | Required. Port number in range from 1025 to 65535. |
| SSL trust store | Optional. Specifies the location of the SSL trust store. |
| SSL trust password | Optional. The password of the SSL trust store. |
| SSL verify server | Optional. The RPC server as SSL client checks the identity of the broker as SSL server. |
| FIPS-140 mode | Optional. Enable FIPS-140 compliant SSL communication. Default is no.
|
| Credentials | |
| User | Optional. The user ID for secured access to the broker. |
| Password | Optional. The password for secured access to the broker. |
Here you can view/edit the configuration file of the RPC Server for IMS Connect.
Here you can modify the IMS Connect settings for the RPC Server for IMS Connect.
| Parameter | Description |
|---|---|
| Connection | |
| Transport | Use TCP or SSL to communicate with IMS Connect. |
| IMS host | Host name or IP address where IMS Connect is running |
| IMS port | TCP or SSL port number where IMS Connect is listening. |
| IMS data store ID | Data store ID. Name of the IMS system that will receive transactions. |
| IMS encoding | Specify the appropriate EBCIDIC encoding used by your IMS Connect. This codepage is also used when communicating with the
EntireX Broker. Default cp037 is EBCDIC codepage with full Latin-1 character set.
|
| IMS socket timeout | Socket timeout for connection to IMS Connect (in milliseconds). |
| IMS SSL trust store | Specifies the location of the SSL trust store. |
| IMS SSL trust password | The password of the SSL trust store. |
| IMS SSL verify server | The RPC Server as SSL client checks the identity of IMS Connect as SSL server. |
| Credentials | |
| RACF user ID | The user ID (max. 8 chars) as defined in your underlying mainframe security system (e.g. RACF). |
| RACF password | Password (max. 8 chars) as defined in your underlying mainframe security system (e.g. RACF). |
| Use PassTicket (1) | Use PassTicket instead of password. |
| Application Name | Required if PassTicket is to be used instead of a password. Application name (1-8 chars) as defined in your RACF system. This property is ignored if RACF password is set. |
| Secured signon key | Required if PassTicket is to be used instead of a password. Secured signon key as defined in your RACF system. Must be exactly 16 characters long. |
| Exit | |
| IMS Connect exit | Use Old or New. |
| IMS Connect exit name | If left blank, the following defaults will be used: *SAMPLE* for old exit, *SAMPLE1* for new exit. |
Notes:
By default, PassTickets can only be used once during a one-second time interval. They are protected against replay. This limits the workload to one request per second.
 |
Warning: IBM provides a mechanism to bypass the PassTicket's replay mechanism, allowing higher workloads, but this introduces security risks. The option to bypass the PassTicket's replay mechanism should only be used in secure environments where access to generated PassTickets is limited to a secure or internal network. See your IBM documentation for more information. |
Here you can view/set the license file in the EntireX installation. For details see Import Product License Keys for Instances or Components under Getting Started with Command Central in the separate Command Central documentation under Software AG Suite & Cross-Product Guides.
Note:
The license file is used for all EntireX instances in this installation.
Here you can modify margins of monitored key performance indicators (KPIs) available for the RPC Server for IMS Connect: Active Workers and Busy Workers.
Key performance indicators (KPIs) enable you to monitor the health of your RPC Server for IMS Connect. The following KPIs help you administer, troubleshoot, and resolve performance issues:
| KPI | Setting |
|---|---|
| Absolute number of Active Workers | entirex.generic.kpi.1.max=20 |
| Critical alert relative to maximum | entirex.generic.kpi.1.critical=0.95 |
| Marginal alert relative to maximum | entirex.generic.kpi.1.marginal=0.80 |
| Absolute number of Busy Workers | entirex.generic.kpi.2.max=20 |
| Critical alert relative to maximum | entirex.generic.kpi.2.critical=0.95 |
| Marginal alert relative to maximum | entirex.generic.kpi.2.marginal=0.80 |
Do not change the other properties!
Here you can specify the RPC Server settings.
| Parameter | Description |
|---|---|
| RPC Server | |
| RPC Server address | Required. The case-sensitive RPC server address has the format: CLASS/SERVER/SERVICE.
|
| Administration port | Required. The administration port in range from 1025 to 65535. |
| Reconnection attempts | Required. Number of reconnection attempts to the broker. When the number of attempts is reached and a connection to the broker is not possible, the RPC Server for IMS Connect stops. |
| Worker Scalability | |
| Worker model | You can either have a fixed or dynamic number of workers. Default is dynamic (true). For more information see Worker Models.
|
| Fixed number | Required. Fixed number of workers. Must be a number in range from 1 to 255. |
| Minimum number | Required. Minimum number of workers. Must be a number in range from 1 to 255. |
| Maximum number | Required. Maximum number of workers. Must be a number in range from 1 to 255. |
Here you can set the trace level of the RPC Server for IMS Connect.
| Parameter | Value | Description |
|---|---|---|
| Trace level | 0-3 |
One of the following levels: 0 - None - No trace output (default). 1 - Standard - Minimal trace output. 2 - Advanced - Detailed trace output. 3 - Support - Support diagnostic. Use only when requested by Software AG Support. |
To view the runtime status of the RPC server instance
In the Command Central Home page, click the Instances tab and select the RPC Server for IMS Connect instance for which you want to see the runtime status (same as Step 1 under Configuring a Broker Instance).
The visual key performance indicators (KPIs) and alerts enable you to monitor the RPC Server for IMS Connect's health.
| KPI | Description |
|---|---|
| Active Workers | Number of active workers. |
| Busy Workers | Number of busy workers. |
To start an RPC Server for IMS Connect instance from the Instances tab
In the Command Central home page, click the Instances tab.
Select the status, and from the context menu choose .
To start an RPC Server for IMS Connect instance from its Overview tab
In the Command Central home page, click the Instances tab and select the RPC Server for IMS Connect instance you want to start (same as Step 1 under Configuring a Broker Instance).
Select the status, and from the context menu choose .
To stop an RPC Server for IMS Connect instance from the Instances tab
In the Command Central home page, click the Instances tab.
Select the status, and from the context menu choose .
To stop an RPC Server for IMS Connect instance from its Overview tab
In the Command Central home page, click the Instances tab and select the RPC Server for IMS Connect instance you want to stop (same as Step 1 under Configuring a Broker Instance).
Select the status, and from the context menu choose .
To inspect the log files of an RPC Server for IMS Connect instance
In the Command Central home page, click the Instances tab, then click the link associated with the RPC Server for IMS Connect instance for which you want to inspect the log files (same as Step 1 under Configuring a Broker Instance).
Click the Logs tab:
In the Alias column, click the link of the log file you want to inspect, for example server.log:
To temporarily change the trace level of an RPC Server for IMS Connect instance
In the Command Central home page, click the Instances tab then click the link associated with the RPC Server for IMS Connect instance for which you want change the trace level temporarily (same as Step 1 under Configuring a Broker Instance).
In the Administration tab, select the trace level and press .
Note:
If you want to set the trace level permanently, see Trace Level under Configuring an RPC Server Instance.
To delete an RPC Server for IMS Connect instance
In the list of EntireX RPC Server for IMS Connect instances for your selected installation (for example Local), select the
instance you want to delete and click the 
button in the upper right corner above the list.
Click to confirm the uninstall of this RPC Server for IMS Connect instance.
In the next window, click . The selected instance is removed from the list.