Configuring Communication Protocols

CA RiskMinder Administration Guide › Managing RiskMinder Server Instances › Configuring Communication Protocols

Configuring Communication Protocols

The Protocol Configuration page allows you to configure protocols for the RiskMinder Server instance or the Case Management Queuing Server instance.

By selecting the RiskMinder Server instance from the drop-down list, you can configure the protocols that Administration Console, SDKs, and Web Services use to communicate with your RiskMinder Server instance for authentication and administration purposes. In addition to the port on which the server listens to each of these enabled components, you can also specify the transport security mechanism (TCP or SSL). In case you specify this mechanism as SSL, then you must also specify the valid and trusted client component’s certificate and private key that are required for establishing a secure connection.

The following table explains the protocols that you see in the List of Protocols table for the RiskMinder Server instance and lists their default port numbers.

Protocol	Default Port Number	Description
Native (TCP)	7680	This is the protocol to enable communication between the RiskMinder Server instance and the RiskMinder Java SDKs, which include Risk Evaluation and Issuance (deprecated). Note: The Web service interface is available for Issuance as part of the user management Web Service Definition Language (WSDL).
Administration Web Service	7777	This is the protocol for communication between RiskMinder Server and Administration Web services. RiskMinder Server listens to the Administration Web service calls on this port. Note: These calls do not include the RiskMinder Issuance (deprecated) or Risk Evaluation calls.
Transaction Web Service	7778	This protocol is used by the Risk Evaluation and the Issuance (deprecated) Web services to connect to the RiskMinder Server instance. This protocol receives Web services requests that are sent by Authentication and Issuance Web services. Note: These calls do not include the Administration service calls.
Native (SSL)	7681	This is an binary protocol to enable SSL-based communication between the RiskMinder Server instance and the RiskMinder Java SDKs, which include Risk Evaluation and Issuance (deprecated).
Server Management	7980	The arrfclient tool communicates with the RiskMinder Server instance for server management activities (graceful shutdown and server cache refresh) by using this protocol. See "arrfclient: Server Refresh and Shutdown Tool" for detailed information on this Administration Console tool.

Similarly, by selecting the Case Management Queuing Server instance from the drop-down list, you can configure the protocols that Administration Console and the Case Management Queuing Server use to communicate with your RiskMinder Server instance for authentication and administration purposes. In addition to the port on which the server listens to each of these enabled components, you can also specify the transport security mechanism (TCP or SSL). In case you specify this mechanism as SSL, then you must also specify the valid and trusted client component’s certificate and private key that are required for establishing a secure connection.

The following table explains the protocols that you see in the List of Protocols table for the Case Management Queuing Server instance and lists their default port numbers.

Protocol	Default Port Number	Description
Case Management Queuing Server	7779	This protocol is used by the Queuing Server module to listen to the Case Management requests (at the server end) on the specified port.
Case Management Queuing Administration	7780	This is the protocol for communication between RiskMinder Server and Case Management Queuing Server. RiskMinder Server listens to the Case Management Web service calls on this port.

Protocol

Default Port Number

Description

Case Management Queuing Server

7779

This protocol is used by the Queuing Server module to listen to the Case Management requests (at the server end) on the specified port.

Case Management Queuing Administration

7780

This is the protocol for communication between RiskMinder Server and Case Management Queuing Server.

RiskMinder Server listens to the Case Management Web service calls on this port.

To configure RiskMinder Server and the Case Management Queuing Server network protocols:

Ensure that you are logged in as the MA.
Activate the Services and Server Configurations tab in the main menu, and ensure that the RiskFort tab in the submenu is displaye.
Under the Instance Configuration section, click the Protocol Configuration link to display the Protocol Configuration page.
Select the RiskMinder Server instance or Case Management Queuing Server instance from the drop-down list.
The List of Protocols appears.
In the List of Protocols table, click the link corresponding to the protocol that you want to configure.
The corresponding Protocol page appears.
Edit the fields on the page, as required. The following table explains these fields.

Column	Action Description
Change Protocol Status	Select this check box to enable the Action drop-down list and change the status of the protocol.
Action	Select Enable to enable the required protocols. See the previous two tables for more information on the supported protocols.
Port	Enter the port number where the corresponding service is available. Following are the default port numbers for RiskMinder protocols: RiskFort Native (TCP): 7680 RiskFort Native (SSL): 7681 Administration Web Services: 7777 Transaction Web Services: 7778 Queuing Server: 7779 Queuing Administration: 7780 Server Management: 7980
Minimum Threads	Minimum number of threads processed on the port.
Maximum Threads	Maximum number of threads processed on the port.
Transport	Specify one of the following modes that are supported for data transfer: TCP: Transmission Control Protocol (TCP) mode is the default mode that is supported by both RiskMinder protocols. It sends data in the clear. SSL: Secure Sockets Layer (SSL) provides higher security for transactions, because it encrypts and decrypts data that is transmitted.
Key in HSM	Enable this check box if the private key for the SSL communication needs to be in the HSM device. In this case, RiskMinder Server and Case Management Queuing Server will find the private key based on the certificate chain provided. This checkbox is enabled only if you select SSL in "Transport".
Server Certificate Chain	Specify the certificate chain that is used by the SSL transport security mode. Use the Browse button to upload the Server Certificate Chain. Important! Ensure that the certificates in the chain that you upload here follow the Leaf certificate --> Intermediate CA certificates --> Root certificate hierarchy. The certificate and the key must be in PEM format.
Server Private Key	Use the Browse button to upload the Server Private Key. Note: This field will be enabled only if you did not select the Key in HSM check box.
Select Client Store	Select the trust store that contains the root certificates of the trusted CAs. See "Creating Trust Stores" for more information on configuring trust stores.

Click Save after you complete the configurations on the page.