Completing post-deployment tasks for Operational Decision Manager

Each ODM component that you deploy is exposed by a service so that external clients can reach them.

About this task

By default, if you configure all of the ODM components, the following services are created by the operator when you run the cp4a-post-deployment.sh script. For more information, see the What to do next section in Deploying the custom resource without the OperatorHub catalog.

Table 1. ODM service names
Service Name	Components
`<CR_NAME>`-odm-decisionserverconsole	Decision Server Console
`<CR_NAME>`-odm-decisionserverruntime	Decision Server Runtime
`<CR_NAME>`-odm-decisioncenter	Decision Center Business/RESTAPI/Enterprise Console
`<CR_NAME>`-odm-decisionrunner	Decision Runner

Where <CR_NAME> is the instance name that you set in your custom resource (CR) file.

When the Kubernetes pods are in a "Running" state, you can access the status of the deployments with the following command:

oc status

On Kubernetes, you can retrieve the cluster-info-ip name and port numbers with the following command:

kubectl cluster-info

An OpenShift Container Platform route exposes a service with a host so that external clients can reach it using the hostname, like www.example.com.

On OpenShift, if the shared_configuration.sc_deployment_platform parameter is set to OCP, the deployment of Operational Decision Manager automatically creates the REST API route. For automatic route creation to be successful, configure the shared_configuration.sc_deployment_hostname_suffix parameter. For more information, see Checking the cluster configuration.

The following table shows what you need to do depending on the deployment platform type and the version that you are using.

For 20.0.1 , if you do not configure ODM with User Management Service (UMS), you need to configure the routes manually to expose the ODM services to users.

Table 2. Automatic route generation
Version	Deployment type	Routes
20.0.3	sc_deployment_platform = OCP or ROKS	Routes automatically generated.
20.0.2	sc_deployment_platform = OCP	Routes automatically generated.
20.0.2	sc_deployment_platform = other	Need to generate routes manually.
20.0.1	sc_deployment_platform = OCP or ROKS with UMS	Routes automatically generated.
20.0.1	sc_deployment_platform = OCP or ROKS without UMS sc_deployment_platform = other	Need to generate routes manually.

Procedure

The following procedure shows how to configure the routes by hand. You only need to follow the procedure when routes are not automatically generated.

Optional: Run the following command to expose a service to your users.
```
oc create route passthrough --service=<SERVICE_NAME>
```
Where <SERVICE_NAME> is one of the service names in full.

For example, to create the route for Decision Server console use the following command.
```
oc create route passthrough --service=cp4a-my-instance-odm-decisionserverconsole
```
Where the name of the operator instance name is cp4a-my-instance.
Optional: Repeat step 1 to create routes for all the components.
The OpenShift Cloud Platform has different types of routes, see the OpenShift documentation.
If you did not enable TLS security for ODM, use the following command instead of oc create.
```
oc expose service/<SERVICE_NAME>
```

To view a service route that you created, enter the following command.

oc get routes <SERVICE_NAME>  -o jsonpath='{.spec.host}'

<SERVICE_NAME>.<ClusterIP>

You can now enter the route URL in a web browser to access the service.
```
https://<SERVICE_NAME>.<ClusterIP> 
```
For example, to get the Decision Server console route enter the following command.
```
oc get routes cp4a-my-instance-odm-decisionserverconsole -o jsonpath='{.spec.host}'
```
```
cp4a-my-instance-odm-decisionserverconsole.<ClusterIP>
```
You can then open a browser and enter the route URL.
```
https://cp4a-my-instance-odm-decisionserverconsole.<ClusterIP>
```
Tip: Use odmAdmin/odmAdmin for the user and password to access the applications.

Results

Table 3. ODM service URLs
Component service name	URL	Username	Password
Decision Server Console	https://`<ROUTE_DECISIONSERVERCONSOLE>`/res	resAdmin odmAdmin	resAdmin odmAdmin
Decision Server Runtime	https://`<ROUTE_DECISIONSERVERRUNTIME>`/DecisionService	resExecutor odmAdmin	resExecutor odmAdmin
Decision Center Business Console	https://`<ROUTE_DECISIONCENTER>`/decisioncenter	rtsAdmin odmAdmin	rtsAdmin odmAdmin
Decision Center Enterprise Console	https://`<ROUTE_DECISIONCENTER>`/teamserver	rtsAdmin odmAdmin	rtsAdmin odmAdmin
Decision Runner	https://`<ROUTE_DECISIONRUNNER>`/DecisionRunner	resDeployer odmAdmin	resDeployer odmAdmin

Deprecated feature:

Deprecation icon The Decision Center Enterprise console is deprecated in V8.10.5. See Deprecated features for migration details.

What to do next

To change these settings, see Configuring user access.

To further debug and diagnose deployment problems in the Kubernetes cluster, use the kubectl cluster-info dump command.

If you customized the default user registry, you must synchronize the registry with the Decision Center database. For more information, see Synchronizing users and groups in Decision Center.

For more information about how to check the state and recent events of your pods, see Troubleshooting.