Accessing the Dedicated Runtime Service

To access the dedicated runtime service, you must configure either the ingress parameter for Kubernetes platforms or the enableRoute parameter for OpenShift®.

By configuring either the ingress or enableRoute parameter, you can effectively route traffic to the appropriate runtime service based on your Kubernetes or OpenShift environment.

Using ingress (Kubernetes)

For most Kubernetes platforms, you can use the ingress parameter to create an ingress resource that routes requests to the appropriate service, whether it is the dedicated runtime or the default runtime.

Configuration example:

decisionServerRuntime:
  dedicated:
    - name: claim
      paths:
        - /myclaimprocessing
    - name: loan
      paths:
        - /myloan/1.0/myloanrs
service:
  ingress:
    enabled: true

Accessing the service:

  1. Retrieve the ingress URL by using the command kubectl get ingress.
  2. Format the request URL by using the format https://<INGRESS_URL>/DecisionService/rest/<RULESET_PATH> to access the dedicated runtime service.

Using enableRoutes (OpenShift)

For OpenShift environments, you use the enableRoute parameter to create routes that direct traffic to the dedicated and default runtimes.

Configuration example:

decisionServerRuntime:
  dedicated:
    - name: claim
      paths:
        - /myclaimprocessing
    - name: loan
      paths:
        - /myloan/1.0/myloanrs
service:
  enableRoute: true

Accessing the service:

  1. Retrieve the routes by using the command oc get routes to list the routes that correspond to the default and the dedicated runtimes and check their corresponding hostname.
  2. Format the request URL by using the format . https://<ROUTE_HOST>/DecisionService/rest/<RULESET_PATH> to access the dedicated runtime service.