Accessing your deployment

After you configure and deploy your containers, you can use Red Hat® OpenShift® Cloud Platform to determine the routes you use to access the services in your content services environment.

About this task

If you are deploying on OCP, the Content operator will create a route for each of your selected components. The same behavior exists on CNCF, if ingress is configured. The full list of routes can be viewed in the content-fncm-access-info configmap found under Workloads > ConfigMaps under your project namespace in the OCP console.

If an application needs session affinity, use the routes without the 'stateless' in the name. This ensures that the load balancing for the back-end services provide for sticky session affinity based on the client IP.

Applications interacting with the Content Platform Engine that need to use sticky session affinity perform metadata authoring followed (within 2 minutes) by CRUD, which attempts to use the newly authored metadata. These applications must use the routes without 'stateless' in the name. Examples of applications that need the sticky route are Content Platform Engine tools such as the FileNet® Deployment Manager and Process Designer.

The Content Cortex components can now have either stateless or sticky routes, depending on the component:

Table 1. Content Cortex Content Routes
Component	Route
Content Platform Engine	One sticky route, one stateless route
GraphQL	One stateless route
Content Management Interoperability Service	One sticky route
Navigator	One sticky route
Task Manager	One sticky route

Table 2. Content Cortex AI Services Routes
Component	Route
Reasoning Service	One stateless route
Core MCP Server	One stateless route

You can find these routes in the deployment-name-fncm-access-info configmap. For more information, see Validating your deployment.

To determine your routes, you can use either the console settings or the command line.

Procedure

To determine your service routes:

Retrieve all route or ingress information from the generated configmap. All URLs and context routes will be listed.
1. Log in to your cluster.
2. Retrieve the deployment-name-fncm-access-info configmap.
```
kubectl get cm deployment-name-fncm-access-info -o yaml  
```
Determine the route that uses the OpenShift Container Platform console:
1. From the console, go to the project where your content services containers are deployed.
2. Go to Networking > Routes.
3. Start the route for the service that you want to access.
  For example, use the following root additions to the route:
  - To access the Administration Console for Content Platform Engine, add /acce to the end of the URL for the route that is not 'stateless'.
Determine the route by using the command line:
1. Log in to your cluster.
2. Get the routes for a project deployed on OCP:
```
oc get routes
```
3. Get the routes for the project deployed on CNCF:
```
kubectl get ingress
```
4. Start the route for the service that you want to access.
  For example, use the following root additions to the route:
  - To access the Administration Console for Content Platform Engine, add /acce to the URL for the route.