Configuring clients

After installing Operational Decision Manager, you must configure the client side to secure the communications with the servers.

Enabling communication with self-signed certificates
You can use self-signed SSL certificates for internal or backend servers. You need to configure the client module in the client-server exchange if you want communication to work for self-signed certificates.
Importing a server certificate to your environment
After creating a keystore with a security certificate in the server.xml file of each Liberty server, a client imports the certificate to its truststore to interact with the server.
Connecting Rule Designer with a server certificate
To be able to securely connect your Rule Designer to Decision Server and Decision Center, you need to establish a connection with a server certificate.
Verifying server certificates
When Operational Decision Manager is installed, you can go to an application by using a URL from a web browser. The first step to secure the communication is to examine the server certificate.
Configuring proxy servers
You need to configure proxy servers if your enterprise uses an HTTP proxy to connect to Rule Execution Server or Decision Center. If you need to use an HTTP proxy server connection, you must configure the client module involved in the client-server exchange.
Decision Center authentication and permission
Security features in Decision Center provides authentication to control access to user interface in the consoles. Decision Center also provides permission management to enable permissions on the different rule artifacts.

Parent topic: Securing Operational Decision Manager