此内容没有您所选择的语言版本。

Chapter 4. OpenShift template reference information

Red Hat Decision Manager provides the following OpenShift templates. To access the templates, download and extract the rhdm-7.3.0-openshift-templates.zip product deliverable file from the Software Downloads page of the Red Hat customer portal.

rhdm73-trial-ephemeral.yaml provides a Business Central and a Decision Server connected to the Business Central. This environment uses an ephemeral configuration without any persistent storage. For details about this template, see Section 4.1, “rhdm73-trial-ephemeral.yaml template”.

4.1. rhdm73-trial-ephemeral.yaml template

Application template for an ephemeral authoring and testing environment, for Red Hat Decision Manager 7.3

4.1.1. Parameters

Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. References can be defined in any text field in the objects list field. Refer to the Openshift documentation for more information.

Variable name	Image Environment Variable	Description	Example value	Required
`APPLICATION_NAME`	—	The name for the application.	myapp	True
`DEFAULT_PASSWORD`	`KIE_ADMIN_PWD`	Default password used for multiple components for user convenience in this trial environment.	RedHat	True
`KIE_ADMIN_USER`	`KIE_ADMIN_USER`	KIE administrator username.	adminUser	False
`KIE_SERVER_USER`	`KIE_SERVER_USER`	KIE server username. (Sets the org.kie.server.user system property)	executionUser	False
`KIE_SERVER_BYPASS_AUTH_USER`	`KIE_SERVER_BYPASS_AUTH_USER`	Allows the KIE server to bypass the authenticated user for task related operations e.g. queries. (Sets the org.kie.server.bypass.auth.user system property)	false	False
`KIE_SERVER_CONTROLLER_USER`	`KIE_SERVER_CONTROLLER_USER`	KIE server controller username. (Sets the org.kie.server.controller.user system property)	controllerUser	False
`KIE_SERVER_MODE`	`KIE_SERVER_MODE`	The KIE Server mode. Valid values are 'DEVELOPMENT' or 'PRODUCTION'. In production mode, you can not deploy SNAPSHOT versions of artifacts on the KIE server and can not change the version of an artifact in an existing container. (Sets the org.kie.server.mode system property).	`DEVELOPMENT`	False
`KIE_MBEANS`	`KIE_MBEANS`	KIE server mbeans enabled/disabled. (Sets the kie.mbeans and kie.scanner.mbeans system properties)	enabled	False
`DROOLS_SERVER_FILTER_CLASSES`	`DROOLS_SERVER_FILTER_CLASSES`	KIE server class filtering. (Sets the org.drools.server.filter.classes system property)	true	False
`KIE_SERVER_HOSTNAME_HTTP`	`HOSTNAME_HTTP`	Custom hostname for http service route. Leave blank for default hostname, e.g.: <application-name>-kieserver-<project>.<default-domain-suffix>	—	False
`KIE_SERVER_ACCESS_CONTROL_ALLOW_ORIGIN`	`AC_ALLOW_ORIGIN_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Allow-Origin response header value in the KIE Server (useful for CORS support).	*	False
`KIE_SERVER_ACCESS_CONTROL_ALLOW_METHODS`	`AC_ALLOW_METHODS_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Allow-Methods response header value in the KIE Server (useful for CORS support).	GET, POST, OPTIONS, PUT	False
`KIE_SERVER_ACCESS_CONTROL_ALLOW_HEADERS`	`AC_ALLOW_HEADERS_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Allow-Headers response header value in the KIE Server (useful for CORS support).	Accept, Authorization, Content-Type, X-Requested-With	False
`KIE_SERVER_ACCESS_CONTROL_ALLOW_CREDENTIALS`	`AC_ALLOW_CREDENTIALS_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Allow-Credentials response header value in the KIE Server (useful for CORS support).	true	False
`KIE_SERVER_ACCESS_CONTROL_MAX_AGE`	`AC_MAX_AGE_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Max-Age response header value in the KIE Server (useful for CORS support).	1	False
`DECISION_CENTRAL_HOSTNAME_HTTP`	`HOSTNAME_HTTP`	Custom hostname for http service route. Leave blank for default hostname, e.g.: <application-name>-rhdmcentr-<project>.<default-domain-suffix>	—	False
`IMAGE_STREAM_NAMESPACE`	—	Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you installed the ImageStreams in a different namespace/project.	openshift	True
`KIE_SERVER_IMAGE_STREAM_NAME`	—	The name of the image stream to use for KIE server. Default is "rhdm73-kieserver-openshift".	rhdm73-kieserver-openshift	True
`IMAGE_STREAM_TAG`	—	A named pointer to an image in an image stream. Default is "1.1".	1.1	True
`KIE_SERVER_CONTAINER_DEPLOYMENT`	`KIE_SERVER_CONTAINER_DEPLOYMENT`	KIE Server Container deployment configuration in format: containerId=groupId:artifactId:version\|c2=g2:a2:v2	—	False
`MAVEN_REPO_ID`	`MAVEN_REPO_ID`	The id to use for the maven repository, if set. Default is generated randomly.	repo-custom	False
`MAVEN_REPO_URL`	`MAVEN_REPO_URL`	Fully qualified URL to a Maven repository or service.	http://nexus.nexus-project.svc.cluster.local:8081/nexus/content/groups/public/	False
`MAVEN_REPO_USERNAME`	`MAVEN_REPO_USERNAME`	Username to access the Maven repository, if required.	—	False
`MAVEN_REPO_PASSWORD`	`MAVEN_REPO_PASSWORD`	Password to access the Maven repository, if required.	—	False
`DECISION_CENTRAL_MAVEN_USERNAME`	`KIE_MAVEN_USER`	Username to access the Maven service hosted by Decision Central inside EAP.	mavenUser	True
`GIT_HOOKS_DIR`	`GIT_HOOKS_DIR`	The directory to use for git hooks, if required.	`/opt/eap/standalone/data/kie/git/hooks`	False
`DECISION_CENTRAL_MEMORY_LIMIT`	—	Decision Central Container memory limit.	2Gi	False
`KIE_SERVER_MEMORY_LIMIT`	—	KIE server Container memory limit.	1Gi	False
`SSO_URL`	`SSO_URL`	RH-SSO URL.	https://rh-sso.example.com/auth	False
`SSO_REALM`	`SSO_REALM`	RH-SSO Realm name.	—	False
`DECISION_CENTRAL_SSO_CLIENT`	`SSO_CLIENT`	Decision Central RH-SSO Client name.	—	False
`DECISION_CENTRAL_SSO_SECRET`	`SSO_SECRET`	Decision Central RH-SSO Client Secret.	252793ed-7118-4ca8-8dab-5622fa97d892	False
`KIE_SERVER_SSO_CLIENT`	`SSO_CLIENT`	KIE Server RH-SSO Client name.	—	False
`KIE_SERVER_SSO_SECRET`	`SSO_SECRET`	KIE Server RH-SSO Client Secret.	252793ed-7118-4ca8-8dab-5622fa97d892	False
`SSO_USERNAME`	`SSO_USERNAME`	RH-SSO Realm Admin Username used to create the Client if it doesn’t exist.	—	False
`SSO_PASSWORD`	`SSO_PASSWORD`	RH-SSO Realm Admin Password used to create the Client.	—	False
`SSO_DISABLE_SSL_CERTIFICATE_VALIDATION`	`SSO_DISABLE_SSL_CERTIFICATE_VALIDATION`	RH-SSO Disable SSL Certificate Validation.	false	False
`SSO_PRINCIPAL_ATTRIBUTE`	`SSO_PRINCIPAL_ATTRIBUTE`	RH-SSO Principal Attribute to use as username.	preferred_username	False
`AUTH_LDAP_URL`	`AUTH_LDAP_URL`	LDAP Endpoint to connect for authentication.	ldap://myldap.example.com	False
`AUTH_LDAP_BIND_DN`	`AUTH_LDAP_BIND_DN`	Bind DN used for authentication.	uid=admin,ou=users,ou=exmample,ou=com	False
`AUTH_LDAP_BIND_CREDENTIAL`	`AUTH_LDAP_BIND_CREDENTIAL`	LDAP Credentials used for authentication.	Password	False
`AUTH_LDAP_JAAS_SECURITY_DOMAIN`	`AUTH_LDAP_JAAS_SECURITY_DOMAIN`	The JMX ObjectName of the JaasSecurityDomain used to decrypt the password.	—	False
`AUTH_LDAP_BASE_CTX_DN`	`AUTH_LDAP_BASE_CTX_DN`	LDAP Base DN of the top-level context to begin the user search.	ou=users,ou=example,ou=com	False
`AUTH_LDAP_BASE_FILTER`	`AUTH_LDAP_BASE_FILTER`	LDAP search filter used to locate the context of the user to authenticate. The input username or userDN obtained from the login module callback is substituted into the filter anywhere a {0} expression is used. A common example for the search filter is (uid={0}).	(uid={0})	False
`AUTH_LDAP_SEARCH_SCOPE`	`AUTH_LDAP_SEARCH_SCOPE`	The search scope to use.	`SUBTREE_SCOPE`	False
`AUTH_LDAP_SEARCH_TIME_LIMIT`	`AUTH_LDAP_SEARCH_TIME_LIMIT`	The timeout in milliseconds for user or role searches.	10000	False
`AUTH_LDAP_DISTINGUISHED_NAME_ATTRIBUTE`	`AUTH_LDAP_DISTINGUISHED_NAME_ATTRIBUTE`	The name of the attribute in the user entry that contains the DN of the user. This may be necessary if the DN of the user itself contains special characters, backslash for example, that prevent correct user mapping. If the attribute does not exist, the entry’s DN is used.	distinguishedName	False
`AUTH_LDAP_PARSE_USERNAME`	`AUTH_LDAP_PARSE_USERNAME`	A flag indicating if the DN is to be parsed for the username. If set to true, the DN is parsed for the username. If set to false the DN is not parsed for the username. This option is used together with usernameBeginString and usernameEndString.	true	False
`AUTH_LDAP_USERNAME_BEGIN_STRING`	`AUTH_LDAP_USERNAME_BEGIN_STRING`	Defines the String which is to be removed from the start of the DN to reveal the username. This option is used together with usernameEndString and only taken into account if parseUsername is set to true.	—	False
`AUTH_LDAP_USERNAME_END_STRING`	`AUTH_LDAP_USERNAME_END_STRING`	Defines the String which is to be removed from the end of the DN to reveal the username. This option is used together with usernameEndString and only taken into account if parseUsername is set to true.	—	False
`AUTH_LDAP_ROLE_ATTRIBUTE_ID`	`AUTH_LDAP_ROLE_ATTRIBUTE_ID`	Name of the attribute containing the user roles.	memberOf	False
`AUTH_LDAP_ROLES_CTX_DN`	`AUTH_LDAP_ROLES_CTX_DN`	The fixed DN of the context to search for user roles. This is not the DN where the actual roles are, but the DN where the objects containing the user roles are. For example, in a Microsoft Active Directory server, this is the DN where the user account is.	ou=groups,ou=example,ou=com	False
`AUTH_LDAP_ROLE_FILTER`	`AUTH_LDAP_ROLE_FILTER`	A search filter used to locate the roles associated with the authenticated user. The input username or userDN obtained from the login module callback is substituted into the filter anywhere a {0} expression is used. The authenticated userDN is substituted into the filter anywhere a {1} is used. An example search filter that matches on the input username is (member={0}). An alternative that matches on the authenticated userDN is (member={1}).	(memberOf={1})	False
`AUTH_LDAP_ROLE_RECURSION`	`AUTH_LDAP_ROLE_RECURSION`	The number of levels of recursion the role search will go below a matching context. Disable recursion by setting this to 0.	1	False
`AUTH_LDAP_DEFAULT_ROLE`	`AUTH_LDAP_DEFAULT_ROLE`	A role included for all authenticated users.	guest	False
`AUTH_LDAP_ROLE_NAME_ATTRIBUTE_ID`	`AUTH_LDAP_ROLE_NAME_ATTRIBUTE_ID`	Name of the attribute within the roleCtxDN context which contains the role name. If the roleAttributeIsDN property is set to true, this property is used to find the role object’s name attribute.	name	False
`AUTH_LDAP_PARSE_ROLE_NAME_FROM_DN`	`AUTH_LDAP_PARSE_ROLE_NAME_FROM_DN`	A flag indicating if the DN returned by a query contains the roleNameAttributeID. If set to true, the DN is checked for the roleNameAttributeID. If set to false, the DN is not checked for the roleNameAttributeID. This flag can improve the performance of LDAP queries.	false	False
`AUTH_LDAP_ROLE_ATTRIBUTE_IS_DN`	`AUTH_LDAP_ROLE_ATTRIBUTE_IS_DN`	Whether or not the roleAttributeID contains the fully-qualified DN of a role object. If false, the role name is taken from the value of the roleNameAttributeId attribute of the context name. Certain directory schemas, such as Microsoft Active Directory, require this attribute to be set to true.	false	False
`AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK`	`AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK`	If you are not using referrals, you can ignore this option. When using referrals, this option denotes the attribute name which contains users defined for a certain role, for example member, if the role object is inside the referral. Users are checked against the content of this attribute name. If this option is not set, the check will always fail, so role objects cannot be stored in a referral tree.	—	False
`AUTH_ROLE_MAPPER_ROLES_PROPERTIES`	`AUTH_ROLE_MAPPER_ROLES_PROPERTIES`	When present, the RoleMapping Login Module will be configured to use the provided file. This parameter defines the fully-qualified file path and name of a properties file or resource which maps roles to replacement roles. The format is original_role=role1,role2,role3	—	False
`AUTH_ROLE_MAPPER_REPLACE_ROLE`	`AUTH_ROLE_MAPPER_REPLACE_ROLE`	Whether to add to the current roles, or replace the current roles with the mapped ones. Replaces if set to true.	—	False

4.1.2. Objects

The CLI supports various object types. A list of these object types as well as their abbreviations can be found in the Openshift documentation.

4.1.2.1. Services

A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the container-engine documentation for more information.

Service	Port	Name	Description
`${APPLICATION_NAME}-rhdmcentr`	8080	http	All the Decision Central web server’s ports.
`${APPLICATION_NAME}-rhdmcentr`	8001	git-ssh	All the Decision Central web server’s ports.
`${APPLICATION_NAME}-kieserver`	8080	—	All the KIE server web server’s ports.

4.1.2.2. Routes

A route is a way to expose a service by giving it an externally-reachable hostname such as www.example.com. A defined route and the endpoints identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists of a route name, service selector, and (optionally) security configuration. Refer to the Openshift documentation for more information.

Service	Security	Hostname
`${APPLICATION_NAME}-rhdmcentr-http`	none	`${DECISION_CENTRAL_HOSTNAME_HTTP}`
`${APPLICATION_NAME}-kieserver-http`	none	`${KIE_SERVER_HOSTNAME_HTTP}`

4.1.2.3. Deployment Configurations

A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. Refer to the Openshift documentation for more information.

4.1.2.3.1. Triggers

A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the Openshift documentation for more information.

Deployment	Triggers
`${APPLICATION_NAME}-rhdmcentr`	ImageChange
`${APPLICATION_NAME}-kieserver`	ImageChange

4.1.2.3.2. Replicas

A replication controller ensures that a specified number of pod "replicas" are running at any one time. If there are too many, the replication controller kills some pods. If there are too few, it starts more. Refer to the container-engine documentation for more information.

Deployment	Replicas
`${APPLICATION_NAME}-rhdmcentr`	1
`${APPLICATION_NAME}-kieserver`	1

4.1.2.3.3. Pod Template

4.1.2.3.3.1. Service Accounts

Service accounts are API objects that exist within each project. They can be created or deleted like any other API object. Refer to the Openshift documentation for more information.

Deployment	Service Account
`${APPLICATION_NAME}-rhdmcentr`	`${APPLICATION_NAME}-rhdmsvc`
`${APPLICATION_NAME}-kieserver`	`${APPLICATION_NAME}-rhdmsvc`

4.1.2.3.3.2. Image

Deployment	Image
`${APPLICATION_NAME}-rhdmcentr`	rhdm73-decisioncentral-openshift
`${APPLICATION_NAME}-kieserver`	`${KIE_SERVER_IMAGE_STREAM_NAME}`

4.1.2.3.3.3. Readiness Probe

${APPLICATION_NAME}-rhdmcentr

/bin/bash -c curl --fail --silent -u '${KIE_ADMIN_USER}:${DEFAULT_PASSWORD}' http://localhost:8080/kie-wb.jsp

${APPLICATION_NAME}-kieserver

/bin/bash -c curl --fail --silent -u ${KIE_ADMIN_USER}:${DEFAULT_PASSWORD} http://localhost:8080/services/rest/server/readycheck

4.1.2.3.3.4. Liveness Probe

${APPLICATION_NAME}-rhdmcentr

/bin/bash -c curl --fail --silent -u '${KIE_ADMIN_USER}:${DEFAULT_PASSWORD}' http://localhost:8080/kie-wb.jsp

${APPLICATION_NAME}-kieserver

/bin/bash -c curl --fail --silent -u ${KIE_ADMIN_USER}:${DEFAULT_PASSWORD} http://localhost:8080/services/rest/server/healthcheck

4.1.2.3.3.5. Exposed Ports

Deployments	Name	Port	Protocol
`${APPLICATION_NAME}-rhdmcentr`	jolokia	8778	`TCP`
	http	8080	`TCP`
	git-ssh	8001	`TCP`
`${APPLICATION_NAME}-kieserver`	jolokia	8778	`TCP`
`${APPLICATION_NAME}-kieserver`	http	8080	`TCP`

4.1.2.3.3.6. Image Environment Variables

Deployment	Variable name	Description	Example value
`${APPLICATION_NAME}-rhdmcentr`	`KIE_ADMIN_USER`	KIE administrator username.	`${KIE_ADMIN_USER}`
	`KIE_ADMIN_PWD`	Default password used for multiple components for user convenience in this trial environment.	`${DEFAULT_PASSWORD}`
	`KIE_MBEANS`	KIE server mbeans enabled/disabled. (Sets the kie.mbeans and kie.scanner.mbeans system properties)	`${KIE_MBEANS}`
	`KIE_SERVER_CONTROLLER_USER`	KIE server controller username. (Sets the org.kie.server.controller.user system property)	`${KIE_SERVER_CONTROLLER_USER}`
	`KIE_SERVER_CONTROLLER_PWD`	Default password used for multiple components for user convenience in this trial environment.	`${DEFAULT_PASSWORD}`
	`KIE_SERVER_USER`	KIE server username. (Sets the org.kie.server.user system property)	`${KIE_SERVER_USER}`
	`KIE_SERVER_PWD`	Default password used for multiple components for user convenience in this trial environment.	`${DEFAULT_PASSWORD}`
	`WORKBENCH_ROUTE_NAME`	—	`${APPLICATION_NAME}-rhdmcentr`
	`MAVEN_REPO_ID`	The id to use for the maven repository, if set. Default is generated randomly.	`${MAVEN_REPO_ID}`
	`MAVEN_REPO_URL`	Fully qualified URL to a Maven repository or service.	`${MAVEN_REPO_URL}`
	`MAVEN_REPO_USERNAME`	Username to access the Maven repository, if required.	`${MAVEN_REPO_USERNAME}`
	`MAVEN_REPO_PASSWORD`	Password to access the Maven repository, if required.	`${MAVEN_REPO_PASSWORD}`
	`KIE_MAVEN_USER`	Username to access the Maven service hosted by Decision Central inside EAP.	`${DECISION_CENTRAL_MAVEN_USERNAME}`
	`KIE_MAVEN_PWD`	Default password used for multiple components for user convenience in this trial environment.	`${DEFAULT_PASSWORD}`
	`GIT_HOOKS_DIR`	The directory to use for git hooks, if required.	`${GIT_HOOKS_DIR}`
	`SSO_URL`	RH-SSO URL.	`${SSO_URL}`
	`SSO_OPENIDCONNECT_DEPLOYMENTS`	—	ROOT.war
	`SSO_REALM`	RH-SSO Realm name.	`${SSO_REALM}`
	`SSO_SECRET`	Decision Central RH-SSO Client Secret.	`${DECISION_CENTRAL_SSO_SECRET}`
	`SSO_CLIENT`	Decision Central RH-SSO Client name.	`${DECISION_CENTRAL_SSO_CLIENT}`
	`SSO_USERNAME`	RH-SSO Realm Admin Username used to create the Client if it doesn’t exist.	`${SSO_USERNAME}`
	`SSO_PASSWORD`	RH-SSO Realm Admin Password used to create the Client.	`${SSO_PASSWORD}`
	`SSO_DISABLE_SSL_CERTIFICATE_VALIDATION`	RH-SSO Disable SSL Certificate Validation.	`${SSO_DISABLE_SSL_CERTIFICATE_VALIDATION}`
	`SSO_PRINCIPAL_ATTRIBUTE`	RH-SSO Principal Attribute to use as username.	`${SSO_PRINCIPAL_ATTRIBUTE}`
	`HOSTNAME_HTTP`	Custom hostname for http service route. Leave blank for default hostname, e.g.: <application-name>-rhdmcentr-<project>.<default-domain-suffix>	`${DECISION_CENTRAL_HOSTNAME_HTTP}`
	`AUTH_LDAP_URL`	LDAP Endpoint to connect for authentication.	`${AUTH_LDAP_URL}`
	`AUTH_LDAP_BIND_DN`	Bind DN used for authentication.	`${AUTH_LDAP_BIND_DN}`
	`AUTH_LDAP_BIND_CREDENTIAL`	LDAP Credentials used for authentication.	`${AUTH_LDAP_BIND_CREDENTIAL}`
	`AUTH_LDAP_JAAS_SECURITY_DOMAIN`	The JMX ObjectName of the JaasSecurityDomain used to decrypt the password.	`${AUTH_LDAP_JAAS_SECURITY_DOMAIN}`
	`AUTH_LDAP_BASE_CTX_DN`	LDAP Base DN of the top-level context to begin the user search.	`${AUTH_LDAP_BASE_CTX_DN}`
	`AUTH_LDAP_BASE_FILTER`	LDAP search filter used to locate the context of the user to authenticate. The input username or userDN obtained from the login module callback is substituted into the filter anywhere a {0} expression is used. A common example for the search filter is (uid={0}).	`${AUTH_LDAP_BASE_FILTER}`
	`AUTH_LDAP_SEARCH_SCOPE`	The search scope to use.	`${AUTH_LDAP_SEARCH_SCOPE}`
	`AUTH_LDAP_SEARCH_TIME_LIMIT`	The timeout in milliseconds for user or role searches.	`${AUTH_LDAP_SEARCH_TIME_LIMIT}`
	`AUTH_LDAP_DISTINGUISHED_NAME_ATTRIBUTE`	The name of the attribute in the user entry that contains the DN of the user. This may be necessary if the DN of the user itself contains special characters, backslash for example, that prevent correct user mapping. If the attribute does not exist, the entry’s DN is used.	`${AUTH_LDAP_DISTINGUISHED_NAME_ATTRIBUTE}`
	`AUTH_LDAP_PARSE_USERNAME`	A flag indicating if the DN is to be parsed for the username. If set to true, the DN is parsed for the username. If set to false the DN is not parsed for the username. This option is used together with usernameBeginString and usernameEndString.	`${AUTH_LDAP_PARSE_USERNAME}`
	`AUTH_LDAP_USERNAME_BEGIN_STRING`	Defines the String which is to be removed from the start of the DN to reveal the username. This option is used together with usernameEndString and only taken into account if parseUsername is set to true.	`${AUTH_LDAP_USERNAME_BEGIN_STRING}`
	`AUTH_LDAP_USERNAME_END_STRING`	Defines the String which is to be removed from the end of the DN to reveal the username. This option is used together with usernameEndString and only taken into account if parseUsername is set to true.	`${AUTH_LDAP_USERNAME_END_STRING}`
	`AUTH_LDAP_ROLE_ATTRIBUTE_ID`	Name of the attribute containing the user roles.	`${AUTH_LDAP_ROLE_ATTRIBUTE_ID}`
	`AUTH_LDAP_ROLES_CTX_DN`	The fixed DN of the context to search for user roles. This is not the DN where the actual roles are, but the DN where the objects containing the user roles are. For example, in a Microsoft Active Directory server, this is the DN where the user account is.	`${AUTH_LDAP_ROLES_CTX_DN}`
	`AUTH_LDAP_ROLE_FILTER`	A search filter used to locate the roles associated with the authenticated user. The input username or userDN obtained from the login module callback is substituted into the filter anywhere a {0} expression is used. The authenticated userDN is substituted into the filter anywhere a {1} is used. An example search filter that matches on the input username is (member={0}). An alternative that matches on the authenticated userDN is (member={1}).	`${AUTH_LDAP_ROLE_FILTER}`
	`AUTH_LDAP_ROLE_RECURSION`	The number of levels of recursion the role search will go below a matching context. Disable recursion by setting this to 0.	`${AUTH_LDAP_ROLE_RECURSION}`
	`AUTH_LDAP_DEFAULT_ROLE`	A role included for all authenticated users.	`${AUTH_LDAP_DEFAULT_ROLE}`
	`AUTH_LDAP_ROLE_NAME_ATTRIBUTE_ID`	Name of the attribute within the roleCtxDN context which contains the role name. If the roleAttributeIsDN property is set to true, this property is used to find the role object’s name attribute.	`${AUTH_LDAP_ROLE_NAME_ATTRIBUTE_ID}`
	`AUTH_LDAP_PARSE_ROLE_NAME_FROM_DN`	A flag indicating if the DN returned by a query contains the roleNameAttributeID. If set to true, the DN is checked for the roleNameAttributeID. If set to false, the DN is not checked for the roleNameAttributeID. This flag can improve the performance of LDAP queries.	`${AUTH_LDAP_PARSE_ROLE_NAME_FROM_DN}`
	`AUTH_LDAP_ROLE_ATTRIBUTE_IS_DN`	Whether or not the roleAttributeID contains the fully-qualified DN of a role object. If false, the role name is taken from the value of the roleNameAttributeId attribute of the context name. Certain directory schemas, such as Microsoft Active Directory, require this attribute to be set to true.	`${AUTH_LDAP_ROLE_ATTRIBUTE_IS_DN}`
	`AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK`	If you are not using referrals, you can ignore this option. When using referrals, this option denotes the attribute name which contains users defined for a certain role, for example member, if the role object is inside the referral. Users are checked against the content of this attribute name. If this option is not set, the check will always fail, so role objects cannot be stored in a referral tree.	`${AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK}`
	`AUTH_ROLE_MAPPER_ROLES_PROPERTIES`	When present, the RoleMapping Login Module will be configured to use the provided file. This parameter defines the fully-qualified file path and name of a properties file or resource which maps roles to replacement roles. The format is original_role=role1,role2,role3	`${AUTH_ROLE_MAPPER_ROLES_PROPERTIES}`
	`AUTH_ROLE_MAPPER_REPLACE_ROLE`	Whether to add to the current roles, or replace the current roles with the mapped ones. Replaces if set to true.	`${AUTH_ROLE_MAPPER_REPLACE_ROLE}`
`${APPLICATION_NAME}-kieserver`	`KIE_ADMIN_USER`	KIE administrator username.	`${KIE_ADMIN_USER}`
	`KIE_ADMIN_PWD`	Default password used for multiple components for user convenience in this trial environment.	`${DEFAULT_PASSWORD}`
	`KIE_SERVER_MODE`	The KIE Server mode. Valid values are 'DEVELOPMENT' or 'PRODUCTION'. In production mode, you can not deploy SNAPSHOT versions of artifacts on the KIE server and can not change the version of an artifact in an existing container. (Sets the org.kie.server.mode system property).	`${KIE_SERVER_MODE}`
	`KIE_MBEANS`	KIE server mbeans enabled/disabled. (Sets the kie.mbeans and kie.scanner.mbeans system properties)	`${KIE_MBEANS}`
	`DROOLS_SERVER_FILTER_CLASSES`	KIE server class filtering. (Sets the org.drools.server.filter.classes system property)	`${DROOLS_SERVER_FILTER_CLASSES}`
	`KIE_SERVER_BYPASS_AUTH_USER`	Allows the KIE server to bypass the authenticated user for task related operations e.g. queries. (Sets the org.kie.server.bypass.auth.user system property)	`${KIE_SERVER_BYPASS_AUTH_USER}`
	`KIE_SERVER_CONTROLLER_USER`	KIE server controller username. (Sets the org.kie.server.controller.user system property)	`${KIE_SERVER_CONTROLLER_USER}`
	`KIE_SERVER_CONTROLLER_PWD`	Default password used for multiple components for user convenience in this trial environment.	`${DEFAULT_PASSWORD}`
	`KIE_SERVER_CONTROLLER_SERVICE`	—	`${APPLICATION_NAME}-rhdmcentr`
	`KIE_SERVER_CONTROLLER_PROTOCOL`	—	ws
	`KIE_SERVER_ID`	—	`${APPLICATION_NAME}-kieserver`
	`KIE_SERVER_ROUTE_NAME`	—	`${APPLICATION_NAME}-kieserver`
	`KIE_SERVER_USER`	KIE server username. (Sets the org.kie.server.user system property)	`${KIE_SERVER_USER}`
	`KIE_SERVER_PWD`	Default password used for multiple components for user convenience in this trial environment.	`${DEFAULT_PASSWORD}`
	`KIE_SERVER_CONTAINER_DEPLOYMENT`	KIE Server Container deployment configuration in format: containerId=groupId:artifactId:version	c2=g2:a2:v2
	`${KIE_SERVER_CONTAINER_DEPLOYMENT}`	`MAVEN_REPOS`	—
	RHDMCENTR,EXTERNAL	`RHDMCENTR_MAVEN_REPO_ID`	—
	repo-rhdmcentr	`RHDMCENTR_MAVEN_REPO_SERVICE`	—
	`${APPLICATION_NAME}-rhdmcentr`	`RHDMCENTR_MAVEN_REPO_PATH`	—
	`/maven2/`	`RHDMCENTR_MAVEN_REPO_USERNAME`	Username to access the Maven service hosted by Decision Central inside EAP.
	`${DECISION_CENTRAL_MAVEN_USERNAME}`	`RHDMCENTR_MAVEN_REPO_PASSWORD`	Default password used for multiple components for user convenience in this trial environment.
	`${DEFAULT_PASSWORD}`	`EXTERNAL_MAVEN_REPO_ID`	The id to use for the maven repository, if set. Default is generated randomly.
	`${MAVEN_REPO_ID}`	`EXTERNAL_MAVEN_REPO_URL`	Fully qualified URL to a Maven repository or service.
	`${MAVEN_REPO_URL}`	`EXTERNAL_MAVEN_REPO_USERNAME`	Username to access the Maven repository, if required.
	`${MAVEN_REPO_USERNAME}`	`EXTERNAL_MAVEN_REPO_PASSWORD`	Password to access the Maven repository, if required.
	`${MAVEN_REPO_PASSWORD}`	`SSO_URL`	RH-SSO URL.
	`${SSO_URL}`	`SSO_OPENIDCONNECT_DEPLOYMENTS`	—
	ROOT.war	`SSO_REALM`	RH-SSO Realm name.
	`${SSO_REALM}`	`SSO_SECRET`	KIE Server RH-SSO Client Secret.
	`${KIE_SERVER_SSO_SECRET}`	`SSO_CLIENT`	KIE Server RH-SSO Client name.
	`${KIE_SERVER_SSO_CLIENT}`	`SSO_USERNAME`	RH-SSO Realm Admin Username used to create the Client if it doesn’t exist.
	`${SSO_USERNAME}`	`SSO_PASSWORD`	RH-SSO Realm Admin Password used to create the Client.
	`${SSO_PASSWORD}`	`SSO_DISABLE_SSL_CERTIFICATE_VALIDATION`	RH-SSO Disable SSL Certificate Validation.
	`${SSO_DISABLE_SSL_CERTIFICATE_VALIDATION}`	`SSO_PRINCIPAL_ATTRIBUTE`	RH-SSO Principal Attribute to use as username.
	`${SSO_PRINCIPAL_ATTRIBUTE}`	`HOSTNAME_HTTP`	Custom hostname for http service route. Leave blank for default hostname, e.g.: <application-name>-kieserver-<project>.<default-domain-suffix>
	`${KIE_SERVER_HOSTNAME_HTTP}`	`AUTH_LDAP_URL`	LDAP Endpoint to connect for authentication.
	`${AUTH_LDAP_URL}`	`AUTH_LDAP_BIND_DN`	Bind DN used for authentication.
	`${AUTH_LDAP_BIND_DN}`	`AUTH_LDAP_BIND_CREDENTIAL`	LDAP Credentials used for authentication.
	`${AUTH_LDAP_BIND_CREDENTIAL}`	`AUTH_LDAP_JAAS_SECURITY_DOMAIN`	The JMX ObjectName of the JaasSecurityDomain used to decrypt the password.
	`${AUTH_LDAP_JAAS_SECURITY_DOMAIN}`	`AUTH_LDAP_BASE_CTX_DN`	LDAP Base DN of the top-level context to begin the user search.
	`${AUTH_LDAP_BASE_CTX_DN}`	`AUTH_LDAP_BASE_FILTER`	LDAP search filter used to locate the context of the user to authenticate. The input username or userDN obtained from the login module callback is substituted into the filter anywhere a {0} expression is used. A common example for the search filter is (uid={0}).
	`${AUTH_LDAP_BASE_FILTER}`	`AUTH_LDAP_SEARCH_SCOPE`	The search scope to use.
	`${AUTH_LDAP_SEARCH_SCOPE}`	`AUTH_LDAP_SEARCH_TIME_LIMIT`	The timeout in milliseconds for user or role searches.
	`${AUTH_LDAP_SEARCH_TIME_LIMIT}`	`AUTH_LDAP_DISTINGUISHED_NAME_ATTRIBUTE`	The name of the attribute in the user entry that contains the DN of the user. This may be necessary if the DN of the user itself contains special characters, backslash for example, that prevent correct user mapping. If the attribute does not exist, the entry’s DN is used.
	`${AUTH_LDAP_DISTINGUISHED_NAME_ATTRIBUTE}`	`AUTH_LDAP_PARSE_USERNAME`	A flag indicating if the DN is to be parsed for the username. If set to true, the DN is parsed for the username. If set to false the DN is not parsed for the username. This option is used together with usernameBeginString and usernameEndString.
	`${AUTH_LDAP_PARSE_USERNAME}`	`AUTH_LDAP_USERNAME_BEGIN_STRING`	Defines the String which is to be removed from the start of the DN to reveal the username. This option is used together with usernameEndString and only taken into account if parseUsername is set to true.
	`${AUTH_LDAP_USERNAME_BEGIN_STRING}`	`AUTH_LDAP_USERNAME_END_STRING`	Defines the String which is to be removed from the end of the DN to reveal the username. This option is used together with usernameEndString and only taken into account if parseUsername is set to true.
	`${AUTH_LDAP_USERNAME_END_STRING}`	`AUTH_LDAP_ROLE_ATTRIBUTE_ID`	Name of the attribute containing the user roles.
	`${AUTH_LDAP_ROLE_ATTRIBUTE_ID}`	`AUTH_LDAP_ROLES_CTX_DN`	The fixed DN of the context to search for user roles. This is not the DN where the actual roles are, but the DN where the objects containing the user roles are. For example, in a Microsoft Active Directory server, this is the DN where the user account is.
	`${AUTH_LDAP_ROLES_CTX_DN}`	`AUTH_LDAP_ROLE_FILTER`	A search filter used to locate the roles associated with the authenticated user. The input username or userDN obtained from the login module callback is substituted into the filter anywhere a {0} expression is used. The authenticated userDN is substituted into the filter anywhere a {1} is used. An example search filter that matches on the input username is (member={0}). An alternative that matches on the authenticated userDN is (member={1}).
	`${AUTH_LDAP_ROLE_FILTER}`	`AUTH_LDAP_ROLE_RECURSION`	The number of levels of recursion the role search will go below a matching context. Disable recursion by setting this to 0.
	`${AUTH_LDAP_ROLE_RECURSION}`	`AUTH_LDAP_DEFAULT_ROLE`	A role included for all authenticated users.
	`${AUTH_LDAP_DEFAULT_ROLE}`	`AUTH_LDAP_ROLE_NAME_ATTRIBUTE_ID`	Name of the attribute within the roleCtxDN context which contains the role name. If the roleAttributeIsDN property is set to true, this property is used to find the role object’s name attribute.
	`${AUTH_LDAP_ROLE_NAME_ATTRIBUTE_ID}`	`AUTH_LDAP_PARSE_ROLE_NAME_FROM_DN`	A flag indicating if the DN returned by a query contains the roleNameAttributeID. If set to true, the DN is checked for the roleNameAttributeID. If set to false, the DN is not checked for the roleNameAttributeID. This flag can improve the performance of LDAP queries.
	`${AUTH_LDAP_PARSE_ROLE_NAME_FROM_DN}`	`AUTH_LDAP_ROLE_ATTRIBUTE_IS_DN`	Whether or not the roleAttributeID contains the fully-qualified DN of a role object. If false, the role name is taken from the value of the roleNameAttributeId attribute of the context name. Certain directory schemas, such as Microsoft Active Directory, require this attribute to be set to true.
	`${AUTH_LDAP_ROLE_ATTRIBUTE_IS_DN}`	`AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK`	If you are not using referrals, you can ignore this option. When using referrals, this option denotes the attribute name which contains users defined for a certain role, for example member, if the role object is inside the referral. Users are checked against the content of this attribute name. If this option is not set, the check will always fail, so role objects cannot be stored in a referral tree.
	`${AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK}`	`AUTH_ROLE_MAPPER_ROLES_PROPERTIES`	When present, the RoleMapping Login Module will be configured to use the provided file. This parameter defines the fully-qualified file path and name of a properties file or resource which maps roles to replacement roles. The format is original_role=role1,role2,role3
	`${AUTH_ROLE_MAPPER_ROLES_PROPERTIES}`	`AUTH_ROLE_MAPPER_REPLACE_ROLE`	Whether to add to the current roles, or replace the current roles with the mapped ones. Replaces if set to true.
	`${AUTH_ROLE_MAPPER_REPLACE_ROLE}`	`FILTERS`	—
	AC_ALLOW_ORIGIN,AC_ALLOW_METHODS,AC_ALLOW_HEADERS,AC_ALLOW_CREDENTIALS,AC_MAX_AGE	`AC_ALLOW_ORIGIN_FILTER_RESPONSE_HEADER_NAME`	—
	Access-Control-Allow-Origin	`AC_ALLOW_ORIGIN_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Allow-Origin response header value in the KIE Server (useful for CORS support).
	`${KIE_SERVER_ACCESS_CONTROL_ALLOW_ORIGIN}`	`AC_ALLOW_METHODS_FILTER_RESPONSE_HEADER_NAME`	—
	Access-Control-Allow-Methods	`AC_ALLOW_METHODS_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Allow-Methods response header value in the KIE Server (useful for CORS support).
	`${KIE_SERVER_ACCESS_CONTROL_ALLOW_METHODS}`	`AC_ALLOW_HEADERS_FILTER_RESPONSE_HEADER_NAME`	—
Access-Control-Allow-Headers	`AC_ALLOW_HEADERS_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Allow-Headers response header value in the KIE Server (useful for CORS support).
`${KIE_SERVER_ACCESS_CONTROL_ALLOW_HEADERS}`	`AC_ALLOW_CREDENTIALS_FILTER_RESPONSE_HEADER_NAME`	—
Access-Control-Allow-Credentials	`AC_ALLOW_CREDENTIALS_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Allow-Credentials response header value in the KIE Server (useful for CORS support).
`${KIE_SERVER_ACCESS_CONTROL_ALLOW_CREDENTIALS}`	`AC_MAX_AGE_FILTER_RESPONSE_HEADER_NAME`	—
Access-Control-Max-Age	`AC_MAX_AGE_FILTER_RESPONSE_HEADER_VALUE`	Sets the Access-Control-Max-Age response header value in the KIE Server (useful for CORS support).

4.1.2.4. External Dependencies

4.1.2.4.1. Secrets

This template requires the following secrets to be installed for the application to run.

4.2. OpenShift usage quick reference

To deploy, monitor, manage, and undeploy Red Hat Decision Manager templates on Red Hat OpenShift Container Platform, you can use the OpenShift Web console or the oc command.

For instructions about using the Web console, see Create and build an image using the Web console.

For detailed instructions about using the oc command, see CLI Reference. The following commands are likely to be required:

To create a project, use the following command:
```
$ oc new-project <project-name>
```
For more information, see Creating a project using the CLI.
To deploy a template (create an application from a template), use the following command:
```
$ oc new-app -f <template-name> -p <parameter>=<value> -p <parameter>=<value> ...
```
For more information, see Creating an application using the CLI.
To view a list of the active pods in the project, use the following command:
```
$ oc get pods
```
To view the current status of a pod, including information whether or not the pod deployment has completed and it is now in a running state, use the following command:
```
$ oc describe pod <pod-name>
```
You can also use the oc describe command to view the current status of other objects. For more information, see Application modification operations.
To view the logs for a pod, use the following command:
```
$ oc logs <pod-name>
```
To view deployment logs, look up a DeploymentConfig name in the template reference and run the following command:
```
$ oc logs -f dc/<deployment-config-name>
```
For more information, see Viewing deployment logs.
To view build logs, look up a BuildConfig name in the template reference and run the command:
```
$ oc logs -f bc/<build-config-name>
```
For more information, see Accessing build logs.
To scale a pod in the application, look up a DeploymentConfig name in the template reference and run the command:
```
$ oc scale dc/<deployment-config-name> --replicas=<number>
```
For more information, see Manual scaling.
To undeploy the application, you can delete the project by using the command:
```
$ oc delete project <project-name>
```
Alternatively, you can use the oc delete command to remove any part of the application, such as a pod or replication controller. For details, see Application modification operations.