Client connection
The following table shows the properties for Business Rules Server client connections.
| Property name | Values (default value) | Description |
|---|---|---|
| serverName | PaymentsDirectorServer | A unique name to identify this instance of the Business Rules Server. The name is used to establish a unique JMS subscription client ID and cannot contain any special characters, such as a quotation mark. |
| serverIPAddress | Use this property when you are running the server on a computer with two or more NIC cards. This property is the IP address that is put into the component table and is used by the Control Center to connect to the Business Rules Server. | |
| serverPort | 1 - 65,535 (2005) | The local port number that is used by the client application to connect. |
| serverQueueSize | 1 - 500 (20) | Size of the client connection queue. This property configures the number of clients that can be queued to wait for a client processor. |
| serverTimeout | 0 - 120,000 ms (30,000) | The amount of time the server waits on a client connection before it checks for other requests. |
| serverReuseAddress | true, false (true) | Controls whether the server binds to a socket that might already be in use. When a well-known port is used, and to avoid waiting for the port to be available from a previous shutdown request, set this property to true. |
| serverRegion | 0 | An integer that defines a logical region that this server is a member of. An example would be to define all servers in Dallas in region 1 and all servers in Columbus in region 2. Data can be distributed just to servers in a particular region. |
Business Rules Server secure socket layer (SSL) properties
Secure socket layer (SSL) connections in WebSphere® enable
Business Rules Server and its client applications to communicate securely instead of sending and
receiving requests in plain text. Business Rules Server supports SSL connections between it and the
client applications for components such as:
- Approvals
- Gateway engine
- Gateway Server
- TCR
- Vetting
If an instance of Business Rules Server is configured to connect by using SSL, each client application that connects to the instance must also be configured to use SSL. Depending on the component for the client application, the SSL properties are configured by using either user interface pages or a properties file. The minimum number of required properties is used to configure the SSL communication between Business Rules Server and the client applications.
The following list describes how Business Rules Server and the client applications are configured.
- Business Rules Server
- Add the SSL properties that are shown in Table 2 to the SSL/TLS connection parameter section in the configuration file. The certificate that is extracted from the key database of the client must be added to the Business Rules truststore database.
- Client applications except for Gateway Server
- Use the properties pages for each component to configure it to use SSL. Add the SSL configuration alias to
use for the Business Rules SSL configuration to the Business Rules SSL configuration
name property for the component for each client application. Set the value of the property to a null value if
an SSL connection is not used. An example of an SSL configuration alias is
NodeDefaultSSLSettings.
Use WebSphere SSL certificate and key management to display the SSL configuration alias for the SSL configuration that is being used. The alias is needed to add the certificate that is extracted from the Business Rules Server key database to the WebSphere truststore database.
- Gateway Server
- Configure the SSL properties in the configuration file for the Gateway Server.
Important: You must restart all J2SE servers and WebSphere Application Server after these
properties are changed.
| Property name | Value or example | Description |
|---|---|---|
| enableSSL | true or false | Indicates whether the server is configured to connect by using SSL. |
| keyStore | C:\Key\Server\keyStore.jks | Location of the keystore. A keystore is a database of private keys. |
| keyStoreFormat | JKS, PKCS12 | Type of key database. |
| keyStorePassword | Password | Password for the key database. |
| trustStore | C:\Key\Server\trustStore.jks | Location of the trusted key database. A truststore is a database of trusted keys. |
| trustStoreFormat | JKS, PKCS12 | Type of trusted key database. |
| trustStorePassword | Password | Password for trusted key database. |