(Red Hat OpenShift) Determining routes for service access for Enterprise Records

After configuring and deploying the Enterprise Records container, you can use the OpenShift Container Platform (OCP) to determine the routes you use to access the services in your records management environment. To determine your routes, you can use either the console settings or the command line.

About this task

As of Cloud Pak for Business Automation, most traffic, by default, goes through the IBM Cloud Pak Platform user interface (Zen) front door. Clients of Cloud Pak for Business Automation applications need to use a URL that goes through the Zen front door route followed by an application-specific prefix.
The Zen front door route can be determined by running the command: oc get routes | grep cpd. Using the Zen front door has several implications, which include the application URLs, HTTP response headers, and authentication. The following table shows the URLs for each component for Enterprise Records:
Component URL path prefix
Enterprise Records /ier
Some non-Zen routes are provided for batch and other not user-centric applications. The full list of routes can be viewed in the icp4adeploy-cp4ba-access-info ConfigMap found under Workloads > ConfigMaps under your project namespace in the OCP console.

Procedure

  • Determining the route using the OCP console
    1. From the console, navigate to the project where your content services containers are deployed.
    2. Go to Networking > Routes.
    3. Launch the route for the service that you want to access.
      For example, add the following root addition to the route to access the Enterprise Records application plug-in, add /ier/EnterpriseRecordsPlugin/IERApplicationPlugin.jar to the end of the URL.
  • Determining the route by using the command line
    1. Log in to your cluster:
      oc login
    2. Access the project where your container is deployed:
      oc project <your_deployed_project>
    3. Get the routes for the project:
      oc get routes
    4. Launch the route for the service that you want to access.
      For example, add the following root addition to the route to access the Enterprise Records application plug-in, add /ier/EnterpriseRecordsPlugin/IERApplicationPlugin.jar to the end of the URL.