Chapter 3. Authoring or managed server environment

You can deploy an environment for creating and modifying services using Decision Central and for running them in Decision Servers managed by Decision Central. This environment consists of Decision Central and one or more Decision Servers.

You can use Decision Central both to develop services and to deploy them to one or several Decision Servers. For example, you can deploy test versions of services to one Decision Server and production versions to another Decision Server.

To avoid accidentally deploying wrong versions to a production Decision Server, you can create separate environments to author services (authoring environment) and to manage deployment of production services (managed server environment). You can use a shared external Maven repository between these environments, so that services developed in the authoring environment are available in the managed server environment. However, the procedures to deploy these environments are the same.

Depending on your needs, you can deploy either a single or high-availability Decision Central. A single Decision Central pod is not replicated; only a single copy of Decision Central is used. In an HA Decision Central deployment, you can scale Decision Central.

An HA Decision Central provides maximum reliability and responsiveness for authoring services, but has higher memory and storage requirements and also requires support for persistent volumes with ReadWriteMany mode.

Important

In the current version, the high-availability functionality is a technology preview.

You can scale Decision Server pods as necessary in any version of the authoring or managed server environment.

To deploy an authoring or managed server environment, first deploy the single or high-availability Decision Central and a single Decision Server using the authoring template.

To add additional Decision Servers, you can deploy the Decision Server template in the same project.

3.1. Deploying single Decision Central and one Decision Server in an authoring or managed server environment

To deploy single Decision Central and one Decision Server in an authoring or managed server environment, use the rhdm71-authoring.yaml template file. You can extract this file from the rhdm-7.1.0-openshift-templates.zip product deliverable file. You can download the file from the Software Downloads page.

Procedure

Use one of the following methods to deploy the template:
- In the OpenShift Web UI, select Add to Project → Import YAML / JSON and then select or paste the rhdm71-authoring.yaml file. In the Add Template window, ensure Process the template is selected and click Continue.
- To use the OpenShift command line console, prepare the following command line:
```
oc new-app -f <template-path>/rhdm71-authoring.yaml -p DECISION_CENTRAL_HTTPS_SECRET=decisioncentral-app-secret -p KIE_SERVER_HTTPS_SECRET=kieserver-app-secret
```
  In this command line:
  - Replace <template-path> with the path to the downloaded template file.
  - Use as many -p PARAMETER=value pairs as needed to set the required parameters. You can view the template file to see descriptions for all parameters.
Set the following parameters as necessary:
- Decision Central Server Keystore Secret Name (DECISION_CENTRAL_HTTPS_SECRET): The name of the secret for Decision Central, as created in Section 2.3, “Creating the secrets for Decision Central”.
- KIE Server Keystore Secret Name (KIE_SERVER_HTTPS_SECRET): The name of the secret for Decision Server, as created in Section 2.2, “Creating the secrets for Decision Server”.
- Application Name (APPLICATION_NAME): The name of the OpenShift application. It is used in the default URLs for Decision Central and Decision Server. OpenShift uses the application name to create a separate set of deployment configurations, services, routes, labels, and artifacts. You can deploy several applications using the same template into the same project, as long as you use different application names. Also, the application name determines the name of the server configuration (server template) on the Decision Central that the Decision Server is to join.
- Decision Central Server Certificate Name (DECISION_CENTRAL_HTTPS_NAME): The name of the certificate in the keystore that you created in Section 2.3, “Creating the secrets for Decision Central”.
- Decision Central Server Keystore Password (DECISION_CENTRAL_HTTPS_PASSWORD): The password for the keystore that you created in Section 2.3, “Creating the secrets for Decision Central”.
- KIE Server Certificate Name (KIE_SERVER_HTTPS_NAME): The name of the certificate in the keystore that you created in Section 2.2, “Creating the secrets for Decision Server”.
- KIE Server Keystore Password (KIE_SERVER_HTTPS_PASSWORD): The password for the keystore that you created in Section 2.2, “Creating the secrets for Decision Server”.
- ImageStream Namespace (IMAGE_STREAM_NAMESPACE): The namespace where the image streams are available. If the image streams were already available in your OpenShift environment (see Section 2.1, “Ensuring the availability of image streams”), the namespace is openshift. If you have installed the image streams file, the namespace is the name of the OpenShift project.
  You can also set the following user names and passwords:
- KIE Admin User (KIE_ADMIN_USER) and KIE Admin Password (KIE_ADMIN_PWD): The user name and password for the administrative user in Decision Central.
- KIE Server User (KIE_SERVER_USER) and KIE Server Password (KIE_SERVER_PWD): The user name and password that a client application must use to connect to the Decision Server.
If you want to deploy additional Decision Servers and connect them to this Decision Central, set the following parameters:
- KIE Server Controller User (KIE_SERVER_CONTROLLER_USER) and KIE Server Controller Password (KIE_SERVER_CONTROLLER_PWD): The user name and password that a Decision Server must use to connect to the Decision Central.
If you want to place the built KJAR files into an external Maven repository, set the following parameters:
- Maven repository URL (MAVEN_REPO_URL): The URL for the Maven repository.
- Maven repository username (MAVEN_REPO_USERNAME): The user name for the Maven repository.
- Maven repository password (MAVEN_REPO_PASSWORD): The password for the Maven repository.
- Maven repository ID (MAVEN_REPO_ID): The Maven ID, which must match the id setting for the Maven repository.
  Alternatively, if you want to use the Maven repository that is built into Decision Central and to connect additional Decision Servers to the Decision Central, set the following parameters:
- Username for the Maven service hosted by Decision Central (DECISION_CENTRAL_MAVEN_USERNAME): The user name for the built-in Maven repository.
- Password for the Maven service hosted by Decision Central (DECISION_CENTRAL_MAVEN_PASSWORD): The password for the built-in Maven repository.
If you want to use RH-SSO or LDAP authentication, complete the following additional configuration:
1. In the RH-SSO or LDAP service, create all user names in the deployment parameters. If you do not set any of the parameters, create users with the default user names. The created users must also be assigned to roles:
  - KIE_ADMIN_USER: default user name adminUser, roles: kie-server,rest-all,admin,kiemgmt,Administrators
  - KIE_SERVER_CONTROLLER_USER: default user name controllerUser, roles: kie-server,rest-all,guest
  - DECISION_CENTRAL_MAVEN_USERNAME (not needed if you configure the use of an external Maven repository): default user name mavenUser. No roles are required.
  - KIE_SERVER_USER: default user name executionUser, roles kie-server,rest-all,guest
2. If you want to configure Red Hat Single Sign On (RH-SSO) authentication, an RH-SSO realm that applies to Red Hat Decision Manager must exist. Decision Server. If the client does not yet exist, the template can create it during deployment. Clients within RH-SSO must also exist for Decision Central and for Decision Server. If the clients do not yet exist, the template can create them during deployment.
  For the user roles that you can configure in RH-SSO, see Roles and users.
  Use one of the following procedures:
  1. If the clients for Red Hat Decision Manager within RH-SSO already exist, set the following parameters in the template:
    RH-SSO URL (SSO_URL): The URL for RH-SSO.
    RH-SSO Realm name (SSO_REALM): The RH-SSO realm for Red Hat Decision Manager.
    Decision Central RH-SSO Client name (DECISION_CENTRAL_SSO_CLIENT): The RH-SSO client name for Decision Central.
    Decision Central RH-SSO Client Secret (DECISION_CENTRAL_SSO_SECRET): The secret string that is set in RH-SSO for the client for Decision Central.
    KIE Server RH-SSO Client name (KIE_SERVER_SSO_CLIENT): The RH-SSO client name for Decision Server.
    KIE Server RH-SSO Client Secret (KIE_SERVER_SSO_SECRET): The secret string that is set in RH-SSO for the client for Decision Server.
    RH-SSO Disable SSL Certificate Validation (SSO_DISABLE_SSL_CERTIFICATE_VALIDATION): Set to true if your RH-SSO installation does not use a valid HTTPS certificate.
  2. To create the clients for Red Hat Decision Manager within RH-SSO, set the following parameters in the template:
    RH-SSO URL (SSO_URL): The URL for RH-SSO.
    RH-SSO Realm name (SSO_REALM): The RH-SSO realm for Red Hat Decision Manager.
    Decision Central RH-SSO Client name (DECISION_CENTRAL_SSO_CLIENT): The name of the client to create in RH-SSO for Decision Central.
    Decision Central RH-SSO Client Secret (DECISION_CENTRAL_SSO_SECRET): The secret string to set in RH-SSO for the client for Decision Central.
    Decision Central Custom http Route Hostname (DECISION_CENTRAL_HOSTNAME_HTTP): The fully qualified host name to use for the HTTP endpoint for Decision Central. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    Decision Central Custom https Route Hostname (DECISION_CENTRAL_HOSTNAME_HTTPS): The fully qualified host name to use for the HTTPS endpoint for Decision Central. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    KIE Server RH-SSO Client name (KIE_SERVER_SSO_CLIENT): The name of the client to create in RH-SSO for Decision Server.
    KIE Server RH-SSO Client Secret (KIE_SERVER_SSO_SECRET): The secret string to set in RH-SSO for the client for Decision Server.
    KIE Server Custom http Route Hostname (KIE_SERVER_HOSTNAME_HTTP): The fully qualified host name to use for the HTTP endpoint for Decision Server. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    KIE Server Custom https Route Hostname (KIE_SERVER_HOSTNAME_HTTPS): The fully qualified host name to use for the HTTPS endpoint for Decision Server. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    RH-SSO Realm Admin Username (SSO_USERNAME) and RH-SSO Realm Admin Password (SSO_PASSWORD): The user name and password for the realm administrator user for the RH-SSO realm for Red Hat Decision Manager.
    RH-SSO Disable SSL Certificate Validation (SSO_DISABLE_SSL_CERTIFICATE_VALIDATION): Set to true if your RH-SSO installation does not use a valid HTTPS certificate.
3. To configure LDAP, set the AUTH_LDAP* parameters of the template. These parameters correspond to the settings of the LdatExtended Login module of Red Hat JBoss EAP. For instructions about using these settings, see LdapExtended Login Module.
  Do not configure LDAP authentication and RH-SSO authentication in the same deployment.
Complete the creation of the environment, depending on the method that you are using:
- In the OpenShift Web UI, click Create.
- Complete and run the command line.

3.2. Deploying high-availability Decision Central and one Decision Server in an authoring or managed server environment

To deploy high-availability Decision Central and one Decision Server in an authoring or managed server environment, use the rhdm71-authoring-ha.yaml template file. You can download the file from the Software Downloads page.

Important

In the current version, the high-availability functionality is a technology preview.

Procedure

Use one of the following methods to deploy the template:
- In the OpenShift Web UI, select Add to Project → Import YAML / JSON and then select or paste the rhdm71-authoring-ha.yaml] file. In the Add Template window, ensure Process the template is selected and click Continue.
- To use the OpenShift command line console, prepare the following command line:
```
oc new-app -f <template-path>/rhdm71-authoring-ha.yaml -p DECISION_CENTRAL_HTTPS_SECRET=decisioncentral-app-secret -p KIE_SERVER_HTTPS_SECRET=kieserver-app-secret
```
  In this command line:
  - Replace <template-path> with the path to the downloaded template file.
  - Use as many -p PARAMETER=value pairs as needed to set the required parameters. You can view the template file to see descriptions for all parameters.
Set the following parameters as necessary:
- Decision Central Server Keystore Secret Name (DECISION_CENTRAL_HTTPS_SECRET): The name of the secret for Decision Central, as created in Section 2.3, “Creating the secrets for Decision Central”.
- KIE Server Keystore Secret Name (KIE_SERVER_HTTPS_SECRET): The name of the secret for Decision Server, as created in Section 2.2, “Creating the secrets for Decision Server”.
- Application Name (APPLICATION_NAME): The name of the OpenShift application. It is used in the default URLs for Decision Central and Decision Server. OpenShift uses the application name to create a separate set of deployment configurations, services, routes, labels, and artifacts. You can deploy several applications using the same template into the same project, as long as you use different application names. Also, the application name determines the name of the server configuration (server template) on the Decision Central that the Decision Server is to join.
- Decision Central Server Certificate Name (DECISION_CENTRAL_HTTPS_NAME): The name of the certificate in the keystore that you created in Section 2.3, “Creating the secrets for Decision Central”.
- Decision Central Server Keystore Password (DECISION_CENTRAL_HTTPS_PASSWORD): The password for the keystore that you created in Section 2.3, “Creating the secrets for Decision Central”.
- KIE Server Certificate Name (KIE_SERVER_HTTPS_NAME): The name of the certificate in the keystore that you created in Section 2.2, “Creating the secrets for Decision Server”.
- KIE Server Keystore Password (KIE_SERVER_HTTPS_PASSWORD): The password for the keystore that you created in Section 2.2, “Creating the secrets for Decision Server”.
- ImageStream Namespace (IMAGE_STREAM_NAMESPACE): The namespace where the image streams are available. If the image streams were already available in your OpenShift environment (see Section 2.1, “Ensuring the availability of image streams”), the namespace is openshift. If you have installed the image streams file, the namespace is the name of the OpenShift project.
  You can also set the following user names and passwords:
- KIE Admin User (KIE_ADMIN_USER) and KIE Admin Password (KIE_ADMIN_PWD): The user name and password for the administrative user in Decision Central.
- KIE Server User (KIE_SERVER_USER) and KIE Server Password (KIE_SERVER_PWD): The user name and password that a client application must use to connect to the Decision Server.
If you want to deploy additional Decision Servers and connect them to this Decision Central, set the following parameters:
- KIE Server Controller User (KIE_SERVER_CONTROLLER_USER) and KIE Server Controller Password (KIE_SERVER_CONTROLLER_PWD): The user name and password that a Decision Server must use to connect to the Decision Central.
If you want to place the built KJAR files into an external Maven repository, set the following parameters:
- Maven repository URL (MAVEN_REPO_URL): The URL for the Maven repository.
- Maven repository username (MAVEN_REPO_USERNAME): The user name for the Maven repository.
- Maven repository password (MAVEN_REPO_PASSWORD): The password for the Maven repository.
- Maven repository ID (MAVEN_REPO_ID): The Maven ID, which must match the id setting for the Maven repository.
  Alternatively, if you want to use the Maven repository that is built into Decision Central and to connect additional Decision Servers to the Decision Central, set the following parameters:
- Username for the Maven service hosted by Decision Central (DECISION_CENTRAL_MAVEN_USERNAME): The user name for the built-in Maven repository.
- Password for the Maven service hosted by Decision Central (DECISION_CENTRAL_MAVEN_PASSWORD): The password for the built-in Maven repository.
If you want to use RH-SSO or LDAP authentication, complete the following additional configuration:
1. In the RH-SSO or LDAP service, create all user names in the deployment parameters. If you do not set any of the parameters, create users with the default user names. The created users must also be assigned to roles:
  - KIE_ADMIN_USER: default user name adminUser, roles: kie-server,rest-all,admin,kiemgmt,Administrators
  - KIE_SERVER_CONTROLLER_USER: default user name controllerUser, roles: kie-server,rest-all,guest
  - DECISION_CENTRAL_MAVEN_USERNAME (not needed if you configure the use of an external Maven repository): default user name mavenUser. No roles are required.
  - KIE_SERVER_USER: default user name executionUser, roles kie-server,rest-all,guest
2. If you want to configure Red Hat Single Sign On (RH-SSO) authentication, an RH-SSO realm that applies to Red Hat Decision Manager must exist. Decision Server. If the client does not yet exist, the template can create it during deployment. Clients within RH-SSO must also exist for Decision Central and for Decision Server. If the clients do not yet exist, the template can create them during deployment.
  For the user roles that you can configure in RH-SSO, see Roles and users.
  Use one of the following procedures:
  1. If the clients for Red Hat Decision Manager within RH-SSO already exist, set the following parameters in the template:
    RH-SSO URL (SSO_URL): The URL for RH-SSO.
    RH-SSO Realm name (SSO_REALM): The RH-SSO realm for Red Hat Decision Manager.
    Decision Central RH-SSO Client name (DECISION_CENTRAL_SSO_CLIENT): The RH-SSO client name for Decision Central.
    Decision Central RH-SSO Client Secret (DECISION_CENTRAL_SSO_SECRET): The secret string that is set in RH-SSO for the client for Decision Central.
    KIE Server RH-SSO Client name (KIE_SERVER_SSO_CLIENT): The RH-SSO client name for Decision Server.
    KIE Server RH-SSO Client Secret (KIE_SERVER_SSO_SECRET): The secret string that is set in RH-SSO for the client for Decision Server.
    RH-SSO Disable SSL Certificate Validation (SSO_DISABLE_SSL_CERTIFICATE_VALIDATION): Set to true if your RH-SSO installation does not use a valid HTTPS certificate.
  2. To create the clients for Red Hat Decision Manager within RH-SSO, set the following parameters in the template:
    RH-SSO URL (SSO_URL): The URL for RH-SSO.
    RH-SSO Realm name (SSO_REALM): The RH-SSO realm for Red Hat Decision Manager.
    Decision Central RH-SSO Client name (DECISION_CENTRAL_SSO_CLIENT): The name of the client to create in RH-SSO for Decision Central.
    Decision Central RH-SSO Client Secret (DECISION_CENTRAL_SSO_SECRET): The secret string to set in RH-SSO for the client for Decision Central.
    Decision Central Custom http Route Hostname (DECISION_CENTRAL_HOSTNAME_HTTP): The fully qualified host name to use for the HTTP endpoint for Decision Central. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    Decision Central Custom https Route Hostname (DECISION_CENTRAL_HOSTNAME_HTTPS): The fully qualified host name to use for the HTTPS endpoint for Decision Central. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    KIE Server RH-SSO Client name (KIE_SERVER_SSO_CLIENT): The name of the client to create in RH-SSO for Decision Server.
    KIE Server RH-SSO Client Secret (KIE_SERVER_SSO_SECRET): The secret string to set in RH-SSO for the client for Decision Server.
    KIE Server Custom http Route Hostname (KIE_SERVER_HOSTNAME_HTTP): The fully qualified host name to use for the HTTP endpoint for Decision Server. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    KIE Server Custom https Route Hostname (KIE_SERVER_HOSTNAME_HTTPS): The fully qualified host name to use for the HTTPS endpoint for Decision Server. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    RH-SSO Realm Admin Username (SSO_USERNAME) and RH-SSO Realm Admin Password (SSO_PASSWORD): The user name and password for the realm administrator user for the RH-SSO realm for Red Hat Decision Manager.
    RH-SSO Disable SSL Certificate Validation (SSO_DISABLE_SSL_CERTIFICATE_VALIDATION): Set to true if your RH-SSO installation does not use a valid HTTPS certificate.
3. To configure LDAP, set the AUTH_LDAP* parameters of the template. These parameters correspond to the settings of the LdatExtended Login module of Red Hat JBoss EAP. For instructions about using these settings, see LdapExtended Login Module.
  Do not configure LDAP authentication and RH-SSO authentication in the same deployment.
If an AMQ 7.1 image is not available in the openshift namespace with default settings, set the following parameters:
- AMQ ImageStream Namespace (AMQ_IMAGE_STREAM_NAMESPACE): Namespace in which the ImageStream for the AMQ image is installed. The default setting is openshift.
- AMQ ImageStream Name (AMQ_IMAGE_STREAM_NAME): The name of the image stream for the AMQ broker. The default setting is amq-broker71-openshift.
- AMQ ImageStream Tag (AMQ_IMAGE_STREAM_TAG): The AMQ image stream tag. The default setting is 1.0.
Complete the creation of the environment, depending on the method that you are using:
- In the OpenShift Web UI, click Create.
- Complete and run the command line.

3.3. Deploying an additional Decision Server

As a part of a managed server infrastructure, you can deploy an additional Decision Server on the OpenShift infrastructure. You can then use Decision Central to deploy, undeploy, and manage services on this Decision Server.

To deploy an additional Decision Server, use the rhdm71-kieserver.yaml template file. You can download the file from the Software Downloads page.

Procedure

Use one of the following methods to deploy the template:
- In the OpenShift Web UI, select Add to Project → Import YAML / JSON and then select or paste the rhdm71-kieserver.yaml file. In the Add Template window, ensure Process the template is selected and click Continue.
- To use the OpenShift command line console, prepare the following command line:
```
oc new-app -f <template-path>/rhdm71-kieserver.yaml -p KIE_SERVER_HTTPS_SECRET=kieserver-app-secret
```
  In this command line:
  - Replace <template-path> with the path to the downloaded template file.
  - Use as many -p PARAMETER=value pairs as needed to set the required parameters. You can view the template file to see descriptions for all parameters.
Set the following parameters:
- KIE server controller service (KIE_SERVER_CONTROLLER_SERVICE): The OpenShift service name for the Decision Central that you installed for this environment.
- KIE server controller user (KIE_SERVER_CONTROLLER_USER): The controller user name for logging onto the Decision Central that you configured.
- KIE server controller password (KIE_SERVER_CONTROLLER_PWD): The controller password for logging onto the Decision Central that you configured.
- KIE Server Keystore Secret Name (KIE_SERVER_HTTPS_SECRET): The name of the secret for Decision Server, as created in Section 2.2, “Creating the secrets for Decision Server”.
- Application Name (APPLICATION_NAME): The name of the OpenShift application. It is used in the default URL for Decision Server. OpenShift uses the application name to create a separate set of deployment configurations, services, routes, labels, and artifacts. You can deploy several applications using the same template into the same project, as long as you use different application names. Also, the application name determines the name of the server configuration (server template) on the Decision Central that the Decision Server is to join.
- KIE Server Certificate Name (KIE_SERVER_HTTPS_NAME): The name of the certificate in the keystore that you created in Section 2.2, “Creating the secrets for Decision Server”.
- KIE Server Keystore Password (KIE_SERVER_HTTPS_PASSWORD): The password for the keystore that you created in Section 2.2, “Creating the secrets for Decision Server”.
Set the parameters for access to the Maven repository, depending on whether you configured the Decision Central to use the built-in or external repository:
1. For a built-in repository:
  - Name of the Maven service hosted by Decision Central (DECISION_CENTRAL_MAVEN_SERVICE): The service name for the built-in Maven repository of the Decision Central.
  - Username for the Maven service hosted by Decision Central (DECISION_CENTRAL_MAVEN_USERNAME): The user name for the built-in Maven repository of the Decision Central. Enter the user name that you configured for the Decision Central as DECISION_CENTRAL_MAVEN_USERNAME.
  - Password to access the Maven service hosted by Decision Central (DECISION_CENTRAL_MAVEN_PASSWORD): The password for the built-in Maven repository of the Decision Central. Enter the password that you configured for the Decision Central as DECISION_CENTRAL_MAVEN_PASSWORD.
2. For an external repository:
  - Maven repository URL (MAVEN_REPO_URL): The URL for the Maven repository with services.
  - Maven repository username (MAVEN_REPO_USERNAME): The user name for the Maven repository.
  - Maven repository password (MAVEN_REPO_PASSWORD): The password for the Maven repository.
    Note
    You can set up access to both the built-in Maven repository of the Decision Central an external Maven repository if your services have dependencies in both repositories.
If you want to use RH-SSO or LDAP authentication, complete the following additional configuration:
1. In the RH-SSO or LDAP service, create all user names in the deployment parameters. If you do not set any of the parameters, create users with the default user names. The created users must also be assigned to roles:
  - KIE_ADMIN_USER: default user name adminUser, roles: kie-server,rest-all,admin,kiemgmt,Administrators
  - KIE_SERVER_USER: default user name executionUser, roles kie-server,rest-all,guest
2. If you want to configure Red Hat Single Sign On (RH-SSO) authentication, an RH-SSO realm that applies to Red Hat Decision Manager must exist. A client within RH-SSO must also exist for
  For the user roles that you can configure in RH-SSO, see Roles and users.
  Use one of the following procedures:
  1. If the client for Red Hat Decision Manager within RH-SSO already exists, set the following parameters in the template:
    RH-SSO URL (SSO_URL): The URL for RH-SSO.
    RH-SSO Realm name (SSO_REALM): The RH-SSO realm for Red Hat Decision Manager.
    KIE Server RH-SSO Client name (KIE_SERVER_SSO_CLIENT): The RH-SSO client name for Decision Server.
    KIE Server RH-SSO Client Secret (KIE_SERVER_SSO_SECRET): The secret string that is set in RH-SSO for the client for Decision Server.
    RH-SSO Disable SSL Certificate Validation (SSO_DISABLE_SSL_CERTIFICATE_VALIDATION): Set to true if your RH-SSO installation does not use a valid HTTPS certificate.
  2. To create the client for Red Hat Decision Manager within RH-SSO, set the following parameters in the template:
    RH-SSO URL (SSO_URL): The URL for RH-SSO.
    RH-SSO Realm name (SSO_REALM): The RH-SSO realm for Red Hat Decision Manager.
    KIE Server RH-SSO Client name (KIE_SERVER_SSO_CLIENT): The name of the client to create in RH-SSO for Decision Server.
    KIE Server RH-SSO Client Secret (KIE_SERVER_SSO_SECRET): The secret string to set in RH-SSO for the client for Decision Server.
    KIE Server Custom http Route Hostname (KIE_SERVER_HOSTNAME_HTTP): The fully qualified host name to use for the HTTP endpoint for Decision Server. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    KIE Server Custom https Route Hostname (KIE_SERVER_HOSTNAME_HTTPS): The fully qualified host name to use for the HTTPS endpoint for Decision Server. If you need to create a client in RH-SSO, you can not leave this parameter blank.
    RH-SSO Realm Admin Username (SSO_USERNAME) and RH-SSO Realm Admin Password (SSO_PASSWORD): The user name and password for the realm administrator user for the RH-SSO realm for Red Hat Decision Manager.
    RH-SSO Disable SSL Certificate Validation (SSO_DISABLE_SSL_CERTIFICATE_VALIDATION): Set to true if your RH-SSO installation does not use a valid HTTPS certificate.
3. To configure LDAP, set the AUTH_LDAP* parameters of the template. These parameters correspond to the settings of the LdatExtended Login module of Red Hat JBoss EAP. For instructions about using these settings, see LdapExtended Login Module.
  Do not configure LDAP authentication and RH-SSO authentication in the same deployment.
Complete the creation of the environment, depending on the method that you are using:
- In the OpenShift Web UI, click Create.
- Complete and run the command line.

Where did the comment section go?

Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.

Log in to Your Red Hat Account

Red Hat Account

Customer Portal

Select Your Language

Infrastructure and Management

Cloud Computing

Storage

JBoss Development and Management

JBoss Integration and Automation

Mobile

Services

Tools

Red Hat Product Security Center

Security Updates

Resources

Customer Portal Community

Customer Events

Stories

Chapter 3. Authoring or managed server environment

3.1. Deploying single Decision Central and one Decision Server in an authoring or managed server environment

3.2. Deploying high-availability Decision Central and one Decision Server in an authoring or managed server environment

3.3. Deploying an additional Decision Server

Where did the comment section go?