Configuring routes in Red Hat OpenShift
When you deploy an integration server, HTTP and HTTPS routes are created by default in Red Hat® OpenShift® to externally expose a service that identifies the set of pods where the integration runs. You can disable the automatic creation of external routes if you want to expose the service to internal traffic only. You can also add custom routes.
You can enable or disable the automatic creation of external routes while creating an integration server by using the spec.disableRoutes parameter. For more information, see Custom resource values.
To create your own custom routes, either navigate to in the Red Hat OpenShift web console, or use the CLI to run the oc expose command for an unsecured route or the oc create route command for a secured route.
After you deploy an integration server in the App Connect Dashboard, you can click the integration server tile to access the API Explorer and view details about the defined operations, including the generated endpoints for the operations. If you want to create and expose custom HTTP or HTTPS routes to a service, and ensure that the API Explorer reflects the correct endpoint, you must add a set of environment variables to your integration server deployment, to specify the custom host names and ports for the routes.
The following table lists the environment variables that you can add to your integration server
deployment. (An integration server deployment is typically named in the format
integrationServerName-is, where
integrationServerName is the metadata.name value; for
example, is-toolkit-is.)
| Transport | Environment variable names and values |
|---|---|
| HTTP |
Name:
Name:
|
| HTTPS |
Name:
Name:
|
For information about setting these environment variables, see Managing integration server environment variables in Red Hat OpenShift.