Chapter 4. OpenShift template reference information

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

rhpam71-authoring.yaml provides a Business Central and a Process Server connected to the Business Central. The Process Server uses an H2 database with persistent storage. You can use this environment to author processes, services, and other business assets. For details about this template, see Section 4.1, “rhpam71-authoring”.
rhpam71-authoring-ha.yaml provides a high-availability Business Central, a Process Server connected to the Business Central, and a MySQL instance that the Process Server uses. You can use this environment to author processes, services, and other business assets. The high-availability functionality is in technical preview. For details about this template, see Section 4.2, “rhpam71-authoring-ha”.

4.1. rhpam71-authoring

Application template for a non-HA persistent authoring environment, for Red Hat Process Automation Manager 7.1

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
`KIE_ADMIN_USER`	`KIE_ADMIN_USER`	KIE administrator username	adminUser	False
`KIE_ADMIN_PWD`	`KIE_ADMIN_PWD`	KIE administrator password	`${KIE_ADMIN_PWD}`	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_CONTROLLER_PWD`	`KIE_SERVER_CONTROLLER_PWD`	KIE server controller password (Sets the org.kie.server.controller.pwd system property)	`${KIE_SERVER_CONTROLLER_PWD}`	False
`KIE_SERVER_CONTROLLER_TOKEN`	`KIE_SERVER_CONTROLLER_TOKEN`	KIE server controller token for bearer authentication (Sets the org.kie.server.controller.token system property)	`${KIE_SERVER_CONTROLLER_TOKEN}`	False
`KIE_SERVER_USER`	`KIE_SERVER_USER`	KIE server username (Sets the org.kie.server.user system property)	executionUser	False
`KIE_SERVER_PWD`	`KIE_SERVER_PWD`	KIE server password (Sets the org.kie.server.pwd system property)	`${KIE_SERVER_PWD}`	False
`KIE_SERVER_BYPASS_AUTH_USER`	`KIE_SERVER_BYPASS_AUTH_USER`	KIE server bypass auth user (Sets the org.kie.server.bypass.auth.user system property)	false	False
`KIE_SERVER_PERSISTENCE_DS`	`KIE_SERVER_PERSISTENCE_DS`	KIE server persistence datasource (Sets the org.kie.server.persistence.ds system property)	java:/jboss/datasources/rhpam	False
KIE_SERVER_H2_USER	—	KIE server H2 database username	sa	False
KIE_SERVER_H2_PWD	—	KIE server H2 database password	—	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
`BUSINESS_CENTRAL_HOSTNAME_HTTP`	`HOSTNAME_HTTP`	Custom hostname for http service route. Leave blank for default hostname, e.g.: <application-name>-rhpamcentr-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`	False
`BUSINESS_CENTRAL_HOSTNAME_HTTPS`	`HOSTNAME_HTTP`	Custom hostname for https service route. Leave blank for default hostname, e.g.: secure-<application-name>-rhpamcentr-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`	False
`KIE_SERVER_HOSTNAME_HTTP`	`HOSTNAME_HTTP`	Custom hostname for http service route, if set will also configure the KIE_SERVER_HOST. Leave blank for default hostname, e.g.: <application-name>-kieserver-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`	False
`KIE_SERVER_HOSTNAME_HTTPS`	`HOSTNAME_HTTP`	Custom hostname for https service route. Leave blank for default hostname, e.g.: secure-<application-name>-kieserver-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`	False
`KIE_SERVER_USE_SECURE_ROUTE_NAME`	`KIE_SERVER_USE_SECURE_ROUTE_NAME`	Use https for the KIE_SERVER_HOST when it is not explicit configured to a custom value.	false	False
`BUSINESS_CENTRAL_HTTPS_SECRET`	—	The name of the secret containing the keystore file	—	True
`BUSINESS_CENTRAL_HTTPS_KEYSTORE`	`HTTPS_KEYSTORE`	The name of the keystore file within the secret	keystore.jks	False
`BUSINESS_CENTRAL_HTTPS_NAME`	`HTTPS_NAME`	The name associated with the server certificate	jboss	False
`BUSINESS_CENTRAL_HTTPS_PASSWORD`	`HTTPS_PASSWORD`	The password for the keystore and certificate	mykeystorepass	False
`KIE_SERVER_HTTPS_SECRET`	—	The name of the secret containing the keystore file	—	True
`KIE_SERVER_HTTPS_KEYSTORE`	`HTTPS_KEYSTORE`	The name of the keystore file within the secret	keystore.jks	False
`KIE_SERVER_HTTPS_NAME`	`HTTPS_NAME`	The name associated with the server certificate	jboss	False
`KIE_SERVER_HTTPS_PASSWORD`	`HTTPS_PASSWORD`	The password for the keystore and certificate	mykeystorepass	False
`DB_VOLUME_CAPACITY`	—	Size of persistent storage for database volume.	1Gi	True
`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’ve 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 "rhpam71-kieserver-openshift".	rhpam71-kieserver-openshift	True
`IMAGE_STREAM_TAG`	—	A named pointer to an image in an image stream. Default is "1.1".	1.1	True
`MAVEN_REPO_ID`	`MAVEN_REPO_ID`	The id to use for the maven repository, if set. Default is generated randomly.	`${MAVEN_REPO_ID}`	False
`MAVEN_REPO_URL`	`MAVEN_REPO_URL`	Fully qualified URL to a Maven repository or service.	`${MAVEN_REPO_URL}`	False
`MAVEN_REPO_USERNAME`	`MAVEN_REPO_USERNAME`	Username to access the Maven repository, if required.	`${MAVEN_REPO_USERNAME}`	False
`MAVEN_REPO_PASSWORD`	`MAVEN_REPO_PASSWORD`	Password to access the Maven repository, if required.	`${MAVEN_REPO_PASSWORD}`	False
`BUSINESS_CENTRAL_MAVEN_USERNAME`	—	Username to access the Maven service hosted by Business Central inside EAP.	mavenUser	True
`BUSINESS_CENTRAL_MAVEN_PASSWORD`	—	Password to access the Maven service hosted by Business Central inside EAP.	—	True
`GIT_HOOKS_DIR`	`GIT_HOOKS_DIR`	The directory to use for git hooks, if required.	`${GIT_HOOKS_DIR}`	False
`BUSINESS_CENTRAL_VOLUME_CAPACITY`	—	Size of the persistent storage for Business Central’s runtime data.	1Gi	True
`BUSINESS_CENTRAL_MEMORY_LIMIT`	—	Business Central Container memory limit	2Gi	False
`KIE_SERVER_MEMORY_LIMIT`	—	KIE server Container memory limit	1Gi	False
`SSO_URL`	`SSO_URL`	RH-SSO URL	`${SSO_URL}`	False
`SSO_REALM`	`SSO_REALM`	RH-SSO Realm name	`${SSO_REALM}`	False
`BUSINESS_CENTRAL_SSO_CLIENT`	`SSO_CLIENT`	Business Central RH-SSO Client name	`${BUSINESS_CENTRAL_SSO_CLIENT}`	False
`BUSINESS_CENTRAL_SSO_SECRET`	`SSO_SECRET`	Business Central RH-SSO Client Secret	`${BUSINESS_CENTRAL_SSO_SECRET}`	False
`KIE_SERVER_SSO_CLIENT`	`SSO_CLIENT`	KIE Server RH-SSO Client name	`${BUSINESS_CENTRAL_SSO_CLIENT}`	False
`KIE_SERVER_SSO_SECRET`	`SSO_SECRET`	KIE Server RH-SSO Client Secret	`${BUSINESS_CENTRAL_SSO_SECRET}`	False
`SSO_USERNAME`	`SSO_USERNAME`	RH-SSO Realm Admin Username used to create the Client if it doesn’t exist	`${SSO_USERNAME}`	False
`SSO_PASSWORD`	`SSO_PASSWORD`	RH-SSO Realm Admin Password used to create the Client	`${SSO_PASSWORD}`	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	`${AUTH_LDAP_URL}`	False
`AUTH_LDAP_BIND_DN`	`AUTH_LDAP_BIND_DN`	Bind DN used for authentication	`${AUTH_LDAP_BIND_DN}`	False
`AUTH_LDAP_BIND_CREDENTIAL`	`AUTH_LDAP_BIND_CREDENTIAL`	LDAP Credentials used for authentication	`${AUTH_LDAP_BIND_CREDENTIAL}`	False
`AUTH_LDAP_JAAS_SECURITY_DOMAIN`	`AUTH_LDAP_JAAS_SECURITY_DOMAIN`	The JMX ObjectName of the JaasSecurityDomain used to decrypt the password.	`${AUTH_LDAP_JAAS_SECURITY_DOMAIN}`	False
`AUTH_LDAP_BASE_CTX_DN`	`AUTH_LDAP_BASE_CTX_DN`	LDAP Base DN of the top-level context to begin the user search.	`${AUTH_LDAP_BASE_CTX_DN}`	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}).	`${AUTH_LDAP_BASE_FILTER}`	False
`AUTH_LDAP_SEARCH_SCOPE`	`AUTH_LDAP_SEARCH_SCOPE`	The search scope to use.	`${AUTH_LDAP_SEARCH_SCOPE}`	False
`AUTH_LDAP_SEARCH_TIME_LIMIT`	`AUTH_LDAP_SEARCH_TIME_LIMIT`	The timeout in milliseconds for user or role searches.	`${AUTH_LDAP_SEARCH_TIME_LIMIT}`	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.	`${AUTH_LDAP_DISTINGUISHED_NAME_ATTRIBUTE}`	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.	`${AUTH_LDAP_PARSE_USERNAME}`	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.	`${AUTH_LDAP_USERNAME_BEGIN_STRING}`	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.	`${AUTH_LDAP_USERNAME_END_STRING}`	False
`AUTH_LDAP_ROLE_ATTRIBUTE_ID`	`AUTH_LDAP_ROLE_ATTRIBUTE_ID`	Name of the attribute containing the user roles.	`${AUTH_LDAP_ROLE_ATTRIBUTE_ID}`	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.	`${AUTH_LDAP_ROLES_CTX_DN}`	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}).	`${AUTH_LDAP_ROLE_FILTER}`	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.	`${AUTH_LDAP_ROLE_RECURSION}`	False
`AUTH_LDAP_DEFAULT_ROLE`	`AUTH_LDAP_DEFAULT_ROLE`	A role included for all authenticated users	`${AUTH_LDAP_DEFAULT_ROLE}`	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.	`${AUTH_LDAP_ROLE_NAME_ATTRIBUTE_ID}`	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.	`${AUTH_LDAP_PARSE_ROLE_NAME_FROM_DN}`	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.	`${AUTH_LDAP_ROLE_ATTRIBUTE_IS_DN}`	False
`AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK`	`AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK`	If you are not using referrals, this option can be ignored. 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}`	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}-rhpamcentr`	8080	http	All the Business Central web server’s ports.
	8443	https
	8001	git-ssh
`${APPLICATION_NAME}-kieserver`	8080	http	All the KIE server web server’s ports.
`${APPLICATION_NAME}-kieserver`	8443	https	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}-rhpamcentr-http`	none	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`
`${APPLICATION_NAME}-rhpamcentr-https`	TLS passthrough	`${BUSINESS_CENTRAL_HOSTNAME_HTTPS}`
`${APPLICATION_NAME}-kieserver-http`	none	`${KIE_SERVER_HOSTNAME_HTTP}`
`${APPLICATION_NAME}-kieserver-https`	TLS passthrough	`${KIE_SERVER_HOSTNAME_HTTPS}`

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}-rhpamcentr`	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}-rhpamcentr`	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}-rhpamcentr`	`${APPLICATION_NAME}-rhpamsvc`
`${APPLICATION_NAME}-kieserver`	`${APPLICATION_NAME}-rhpamsvc`

4.1.2.3.3.2. Image

Deployment	Image
`${APPLICATION_NAME}-rhpamcentr`	rhpam71-businesscentral-openshift
`${APPLICATION_NAME}-kieserver`	`${KIE_SERVER_IMAGE_STREAM_NAME}`

4.1.2.3.3.3. Readiness Probe

${APPLICATION_NAME}-rhpamcentr

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

${APPLICATION_NAME}-kieserver

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

4.1.2.3.3.4. Liveness Probe

${APPLICATION_NAME}-rhpamcentr

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

${APPLICATION_NAME}-kieserver

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

4.1.2.3.3.5. Exposed Ports

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

4.1.2.3.3.6. Image Environment Variables

Deployment	Variable name	Description	Example value
`${APPLICATION_NAME}-rhpamcentr`	`KIE_ADMIN_USER`	KIE administrator username	`${KIE_ADMIN_USER}`
	`KIE_ADMIN_PWD`	KIE administrator password	`${KIE_ADMIN_PWD}`
	`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`	KIE server controller password (Sets the org.kie.server.controller.pwd system property)	`${KIE_SERVER_CONTROLLER_PWD}`
	`KIE_SERVER_CONTROLLER_TOKEN`	KIE server controller token for bearer authentication (Sets the org.kie.server.controller.token system property)	`${KIE_SERVER_CONTROLLER_TOKEN}`
	`KIE_SERVER_USER`	KIE server username (Sets the org.kie.server.user system property)	`${KIE_SERVER_USER}`
	`KIE_SERVER_PWD`	KIE server password (Sets the org.kie.server.pwd system property)	`${KIE_SERVER_PWD}`
	`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`	—	`${BUSINESS_CENTRAL_MAVEN_USERNAME}`
	`KIE_MAVEN_PWD`	—	`${BUSINESS_CENTRAL_MAVEN_PASSWORD}`
	`GIT_HOOKS_DIR`	The directory to use for git hooks, if required.	`${GIT_HOOKS_DIR}`
	`HTTPS_KEYSTORE_DIR`	—	`/etc/businesscentral-secret-volume`
	`HTTPS_KEYSTORE`	The name of the keystore file within the secret	`${BUSINESS_CENTRAL_HTTPS_KEYSTORE}`
	`HTTPS_NAME`	The name associated with the server certificate	`${BUSINESS_CENTRAL_HTTPS_NAME}`
	`HTTPS_PASSWORD`	The password for the keystore and certificate	`${BUSINESS_CENTRAL_HTTPS_PASSWORD}`
	`WORKBENCH_ROUTE_NAME`	—	`${APPLICATION_NAME}-rhpamcentr`
	`SSO_URL`	RH-SSO URL	`${SSO_URL}`
	`SSO_OPENIDCONNECT_DEPLOYMENTS`	—	ROOT.war
	`SSO_REALM`	RH-SSO Realm name	`${SSO_REALM}`
	`SSO_SECRET`	Business Central RH-SSO Client Secret	`${BUSINESS_CENTRAL_SSO_SECRET}`
	`SSO_CLIENT`	Business Central RH-SSO Client name	`${BUSINESS_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>-rhpamcentr-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`
	`HOSTNAME_HTTPS`	Custom hostname for https service route. Leave blank for default hostname, e.g.: secure-<application-name>-rhpamcentr-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTPS}`
	`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, this option can be ignored. 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}`
`${APPLICATION_NAME}-kieserver`	`DATASOURCES`	—	`RHPAM`
	`RHPAM_DATABASE`	—	rhpam7
	`RHPAM_JNDI`	—	`${KIE_SERVER_PERSISTENCE_DS}`
	`RHPAM_JTA`	—	true
	`RHPAM_DRIVER`	—	h2
	`RHPAM_USERNAME`	—	`${KIE_SERVER_H2_USER}`
	`RHPAM_PASSWORD`	—	`${KIE_SERVER_H2_PWD}`
	`RHPAM_XA_CONNECTION_PROPERTY_URL`	—	jdbc:h2:/opt/eap/standalone/data/rhpam
	`RHPAM_SERVICE_HOST`	—	dummy_ignored
	`RHPAM_SERVICE_PORT`	—	12345
	`KIE_SERVER_PERSISTENCE_DIALECT`	—	org.hibernate.dialect.H2Dialect
	`DROOLS_SERVER_FILTER_CLASSES`	KIE server class filtering (Sets the org.drools.server.filter.classes system property)	`${DROOLS_SERVER_FILTER_CLASSES}`
	`KIE_ADMIN_USER`	KIE administrator username	`${KIE_ADMIN_USER}`
	`KIE_ADMIN_PWD`	KIE administrator password	`${KIE_ADMIN_PWD}`
	`KIE_MBEANS`	KIE server mbeans enabled/disabled (Sets the kie.mbeans and kie.scanner.mbeans system properties)	`${KIE_MBEANS}`
	`KIE_SERVER_BYPASS_AUTH_USER`	KIE server bypass auth user (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`	KIE server controller password (Sets the org.kie.server.controller.pwd system property)	`${KIE_SERVER_CONTROLLER_PWD}`
	`KIE_SERVER_CONTROLLER_TOKEN`	KIE server controller token for bearer authentication (Sets the org.kie.server.controller.token system property)	`${KIE_SERVER_CONTROLLER_TOKEN}`
	`KIE_SERVER_CONTROLLER_SERVICE`	—	`${APPLICATION_NAME}-rhpamcentr`
	`KIE_SERVER_CONTROLLER_PROTOCOL`	—	ws
	`KIE_SERVER_ID`	—	`${APPLICATION_NAME}-kieserver`
	`KIE_SERVER_HOST`	Custom hostname for http service route, if set will also configure the KIE_SERVER_HOST. Leave blank for default hostname, e.g.: <application-name>-kieserver-<project>.<default-domain-suffix>	`${KIE_SERVER_HOSTNAME_HTTP}`
	`KIE_SERVER_ROUTE_NAME`	—	`${APPLICATION_NAME}-kieserver`
	`KIE_SERVER_USE_SECURE_ROUTE_NAME`	Use https for the KIE_SERVER_HOST when it is not explicit configured to a custom value.	`${KIE_SERVER_USE_SECURE_ROUTE_NAME}`
	`KIE_SERVER_PERSISTENCE_DS`	KIE server persistence datasource (Sets the org.kie.server.persistence.ds system property)	`${KIE_SERVER_PERSISTENCE_DS}`
	`KIE_SERVER_USER`	KIE server username (Sets the org.kie.server.user system property)	`${KIE_SERVER_USER}`
	`KIE_SERVER_PWD`	KIE server password (Sets the org.kie.server.pwd system property)	`${KIE_SERVER_PWD}`
	`MAVEN_REPOS`	—	RHPAMCENTR,EXTERNAL
	`RHPAMCENTR_MAVEN_REPO_SERVICE`	—	`${APPLICATION_NAME}-rhpamcentr`
	`RHPAMCENTR_MAVEN_REPO_PATH`	—	`/maven2/`
	`RHPAMCENTR_MAVEN_REPO_USERNAME`	Username to access the Maven repository, if required.	`${BUSINESS_CENTRAL_MAVEN_USERNAME}`
	`RHPAMCENTR_MAVEN_REPO_PASSWORD`	Password to access the Maven repository, if required.	`${BUSINESS_CENTRAL_MAVEN_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}`
	`HTTPS_KEYSTORE_DIR`	—	`/etc/kieserver-secret-volume`
	`HTTPS_KEYSTORE`	The name of the keystore file within the secret	`${KIE_SERVER_HTTPS_KEYSTORE}`
	`HTTPS_NAME`	The name associated with the server certificate	`${KIE_SERVER_HTTPS_NAME}`
	`HTTPS_PASSWORD`	The password for the keystore and certificate	`${KIE_SERVER_HTTPS_PASSWORD}`
	`SSO_URL`	RH-SSO URL	`${SSO_URL}`
	`SSO_OPENIDCONNECT_DEPLOYMENTS`	—	ROOT.war
	`SSO_REALM`	RH-SSO Realm name	`${SSO_REALM}`
	`SSO_SECRET`	Business Central RH-SSO Client Secret	`${KIE_SERVER_SSO_SECRET}`
	`SSO_CLIENT`	Business Central 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>-rhpamcentr-<project>.<default-domain-suffix>	`${KIE_SERVER_HOSTNAME_HTTP}`
	`HOSTNAME_HTTPS`	Custom hostname for https service route. Leave blank for default hostname, e.g.: secure-<application-name>-rhpamcentr-<project>.<default-domain-suffix>	`${KIE_SERVER_HOSTNAME_HTTPS}`
	`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, this option can be ignored. 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}`

4.1.2.3.3.7. Volumes

Deployment	Name	mountPath	Purpose	readOnly
`${APPLICATION_NAME}-rhpamcentr`	businesscentral-keystore-volume	`/etc/businesscentral-secret-volume`	ssl certs	True
`${APPLICATION_NAME}-kieserver`	kieserver-keystore-volume	`/etc/kieserver-secret-volume`	ssl certs	True

4.1.2.4. External Dependencies

4.1.2.4.1. Volume Claims

A PersistentVolume object is a storage resource in an OpenShift cluster. Storage is provisioned by an administrator by creating PersistentVolume objects from sources such as GCE Persistent Disks, AWS Elastic Block Stores (EBS), and NFS mounts. Refer to the Openshift documentation for more information.

Name	Access Mode
`${APPLICATION_NAME}-rhpamcentr-claim`	ReadWriteOnce
`${APPLICATION_NAME}-h2-claim`	ReadWriteOnce

4.1.2.4.2. Secrets

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

businesscentral-app-secret kieserver-app-secret

4.2. rhpam71-authoring-ha

Application template for a HA persistent authoring environment, for Red Hat Process Automation Manager 7.1

4.2.1. Parameters

Variable name	Image Environment Variable	Description	Example value	Required
`APPLICATION_NAME`	—	The name for the application.	myapp	True
`KIE_ADMIN_USER`	`KIE_ADMIN_USER`	KIE administrator username	adminUser	False
`KIE_ADMIN_PWD`	`KIE_ADMIN_PWD`	KIE administrator password	`${KIE_ADMIN_PWD}`	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_CONTROLLER_PWD`	`KIE_SERVER_CONTROLLER_PWD`	KIE server controller password (Sets the org.kie.server.controller.pwd system property)	`${KIE_SERVER_CONTROLLER_PWD}`	False
`KIE_SERVER_CONTROLLER_TOKEN`	`KIE_SERVER_CONTROLLER_TOKEN`	KIE server controller token for bearer authentication (Sets the org.kie.server.controller.token system property)	`${KIE_SERVER_CONTROLLER_TOKEN}`	False
`KIE_SERVER_USER`	`KIE_SERVER_USER`	KIE server username (Sets the org.kie.server.user system property)	executionUser	False
`KIE_SERVER_PWD`	`KIE_SERVER_PWD`	KIE server password (Sets the org.kie.server.pwd system property)	`${KIE_SERVER_PWD}`	False
`KIE_SERVER_BYPASS_AUTH_USER`	`KIE_SERVER_BYPASS_AUTH_USER`	KIE server bypass auth user (Sets the org.kie.server.bypass.auth.user system property)	false	False
`KIE_SERVER_PERSISTENCE_DS`	`KIE_SERVER_PERSISTENCE_DS`	KIE server persistence datasource (Sets the org.kie.server.persistence.ds system property)	java:/jboss/datasources/rhpam	False
`KIE_SERVER_MYSQL_USER`	`MYSQL_USER`	KIE server MySQL database username	rhpam	False
`KIE_SERVER_MYSQL_PWD`	—	KIE server MySQL database password	—	False
`KIE_SERVER_MYSQL_DB`	—	KIE server MySQL database name	rhpam7	False
`MYSQL_IMAGE_STREAM_NAMESPACE`	—	Namespace in which the ImageStream for the MySQL image is installed. The ImageStream is already installed in the openshift namespace. You should only need to modify this if you’ve installed the ImageStream in a different namespace/project. Default is "openshift".	openshift	False
`MYSQL_IMAGE_STREAM_TAG`	—	The MySQL image version, which is intended to correspond to the MySQL version. Default is "5.7".	5.7	False
`DB_VOLUME_CAPACITY`	—	Size of persistent storage for database volume.	1Gi	True
`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
`BUSINESS_CENTRAL_HOSTNAME_HTTP`	`HOSTNAME_HTTP`	Custom hostname for http service route. Leave blank for default hostname, e.g.: <application-name>-rhpamcentr-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`	False
`BUSINESS_CENTRAL_HOSTNAME_HTTPS`	`HOSTNAME_HTTP`	Custom hostname for https service route. Leave blank for default hostname, e.g.: secure-<application-name>-rhpamcentr-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`	False
`KIE_SERVER_HOSTNAME_HTTP`	`HOSTNAME_HTTP`	Custom hostname for http service route, if set will also configure the KIE_SERVER_HOST. Leave blank for default hostname, e.g.: <application-name>-kieserver-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`	False
`KIE_SERVER_HOSTNAME_HTTPS`	`HOSTNAME_HTTP`	Custom hostname for https service route. Leave blank for default hostname, e.g.: secure-<application-name>-kieserver-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`	False
`KIE_SERVER_USE_SECURE_ROUTE_NAME`	`KIE_SERVER_USE_SECURE_ROUTE_NAME`	Use https for the KIE_SERVER_HOST when it is not explicit configured to a custom value.	false	False
`BUSINESS_CENTRAL_HTTPS_SECRET`	—	The name of the secret containing the keystore file	—	True
`BUSINESS_CENTRAL_HTTPS_KEYSTORE`	`HTTPS_KEYSTORE`	The name of the keystore file within the secret	keystore.jks	False
`BUSINESS_CENTRAL_HTTPS_NAME`	`HTTPS_NAME`	The name associated with the server certificate	jboss	False
`BUSINESS_CENTRAL_HTTPS_PASSWORD`	`HTTPS_PASSWORD`	The password for the keystore and certificate	mykeystorepass	False
`KIE_SERVER_HTTPS_SECRET`	—	The name of the secret containing the keystore file	—	True
`KIE_SERVER_HTTPS_KEYSTORE`	`HTTPS_KEYSTORE`	The name of the keystore file within the secret	keystore.jks	False
`KIE_SERVER_HTTPS_NAME`	`HTTPS_NAME`	The name associated with the server certificate	jboss	False
`KIE_SERVER_HTTPS_PASSWORD`	`HTTPS_PASSWORD`	The password for the keystore and certificate	mykeystorepass	False
`APPFORMER_ELASTIC_RETRIES`	`APPFORMER_ELASTIC_RETRIES`	The number of times that appformer will try to connect to the elasticsearch node before give up.	`${APPFORMER_ELASTIC_RETRIES}`	False
`APPFORMER_JMS_BROKER_PORT`	`APPFORMER_JMS_BROKER_PORT`	The port to connect in the JMS broker. Defaults to 61616	`${APPFORMER_JMS_BROKER_PORT}`	False
`APPFORMER_JMS_BROKER_USER`	`APPFORMER_JMS_BROKER_USER`	The username to connect in the JMS broker.	jmsBrokserUser	True
`APPFORMER_JMS_BROKER_PASSWORD`	`APPFORMER_JMS_BROKER_PASSWORD`	The password to connect in the JMS broker.	`${APPFORMER_JMS_BROKER_PASSWORD}`	True
`ES_HOSTNAME_HTTP`	`HOSTNAME_HTTP`	Custom hostname for http service route. Leave blank for default hostname, e.g.: <application-name>-rhpamindex-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`	False
`APPFORMER_ELASTIC_CLUSTER_NAME`	`APPFORMER_ELASTIC_CLUSTER_NAME`	Sets the ES cluster.name and configure it on Business Central. Defaults to kie-cluster.	`${APPFORMER_ELASTIC_CLUSTER_NAME}`	False
`ES_NODE_NAME`	`ES_NODE_NAME`	Sets the ES node.name property. Defaults to HOSTNAME env value.	`${ES_NODE_NAME}`	False
`ES_TRANSPORT_HOST`	`ES_TRANSPORT_HOST`	Sets the ES transport.host property. This will set the transport address of the main ES cluster node. Used for communication between nodes in the cluster. Defaults to container address.	`${ES_TRANSPORT_HOST}`	False
`APPFORMER_ELASTIC_PORT`	`APPFORMER_ELASTIC_PORT`	Sets the ES http.host property. This will set the http address of the main ES cluster node. Used for communication between nodes in the cluster and the communication with Business Central.	`${APPFORMER_ELASTIC_PORT}`	False
`ES_HTTP_HOST`	`ES_HTTP_HOST`	Sets the ES http.host property. This will set the http address of the main ES cluster node. Used to interact with cluster rest api. Defaults to the container ip address	`${ES_HTTP_HOST}`	False
`ES_HTTP_PORT`	`ES_HTTP_PORT`	Sets the ES http.port property. This will set the http port of the main ES cluster node. Used to interact with cluster rest api.	`${ES_HTTP_PORT}`	False
`ES_JAVA_OPTS`	`ES_JAVA_OPTS`	Appends custom jvm configurations/properties to ES jvm.options configuration file.	`${ES_JAVA_OPTS}`	False
`AMQ_IMAGE_STREAM_NAMESPACE`	—	Namespace in which the ImageStream for the AMQ image is installed. Default is "openshift".	openshift	True
`AMQ_IMAGE_STREAM_NAME`	—	The name of the image stream to use for the AMQ broker. Default is "amq-broker71-openshift".	amq-broker71-openshift	True
`AMQ_IMAGE_STREAM_TAG`	—	The AMQ image stream tag. Default is "1.0".	1.0	True
`AMQ_ROLE`	`AMQ_ROLE`	User role for standard broker user.	admin	True
`AMQ_NAME`	`AMQ_NAME`	The name of the broker	broker	True
`AMQ_GLOBAL_MAX_SIZE`	`AMQ_GLOBAL_MAX_SIZE`	Maximum amount of memory which message data may consume (Default: Undefined, half of the system’s memory).	100 gb	False
`ES_VOLUME_CAPACITY`	—	Size of persistent storage for Elasticsearch volume.	1Gi	True
`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’ve 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 "rhpam71-kieserver-openshift".	rhpam71-kieserver-openshift	True
`IMAGE_STREAM_TAG`	—	A named pointer to an image in an image stream. Default is "1.1".	1.1	True
`MAVEN_REPO_ID`	`MAVEN_REPO_ID`	The id to use for the maven repository, if set. Default is generated randomly.	`${MAVEN_REPO_ID}`	False
`MAVEN_REPO_URL`	`MAVEN_REPO_URL`	Fully qualified URL to a Maven repository or service.	`${MAVEN_REPO_URL}`	False
`MAVEN_REPO_USERNAME`	`MAVEN_REPO_USERNAME`	Username to access the Maven repository, if required.	`${MAVEN_REPO_USERNAME}`	False
`MAVEN_REPO_PASSWORD`	`MAVEN_REPO_PASSWORD`	Password to access the Maven repository, if required.	`${MAVEN_REPO_PASSWORD}`	False
`BUSINESS_CENTRAL_MAVEN_USERNAME`	—	Username to access the Maven service hosted by Business Central inside EAP.	mavenUser	True
`BUSINESS_CENTRAL_MAVEN_PASSWORD`	—	Password to access the Maven service hosted by Business Central inside EAP.	—	True
`GIT_HOOKS_DIR`	`GIT_HOOKS_DIR`	The directory to use for git hooks, if required.	`${GIT_HOOKS_DIR}`	False
`TIMER_SERVICE_DATA_STORE_REFRESH_INTERVAL`	`TIMER_SERVICE_DATA_STORE_REFRESH_INTERVAL`	Sets refresh-interval for the EJB timer database data-store service.	60000	True
`BUSINESS_CENTRAL_VOLUME_CAPACITY`	—	Size of the persistent storage for Business Central’s runtime data.	1Gi	True
`BUSINESS_CENTRAL_MEMORY_LIMIT`	—	Business Central Container memory limit	2Gi	False
`KIE_SERVER_MEMORY_LIMIT`	—	KIE server Container memory limit	1Gi	False
`SSO_URL`	`SSO_URL`	RH-SSO URL	`${SSO_URL}`	False
`SSO_REALM`	`SSO_REALM`	RH-SSO Realm name	`${SSO_REALM}`	False
`BUSINESS_CENTRAL_SSO_CLIENT`	`SSO_CLIENT`	Business Central RH-SSO Client name	`${BUSINESS_CENTRAL_SSO_CLIENT}`	False
`BUSINESS_CENTRAL_SSO_SECRET`	`SSO_SECRET`	Business Central RH-SSO Client Secret	`${BUSINESS_CENTRAL_SSO_SECRET}`	False
`KIE_SERVER_SSO_CLIENT`	`SSO_CLIENT`	KIE Server RH-SSO Client name	`${BUSINESS_CENTRAL_SSO_CLIENT}`	False
`KIE_SERVER_SSO_SECRET`	`SSO_SECRET`	KIE Server RH-SSO Client Secret	`${BUSINESS_CENTRAL_SSO_SECRET}`	False
`SSO_USERNAME`	`SSO_USERNAME`	RH-SSO Realm Admin Username used to create the Client if it doesn’t exist	`${SSO_USERNAME}`	False
`SSO_PASSWORD`	`SSO_PASSWORD`	RH-SSO Realm Admin Password used to create the Client	`${SSO_PASSWORD}`	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	`${AUTH_LDAP_URL}`	False
`AUTH_LDAP_BIND_DN`	`AUTH_LDAP_BIND_DN`	Bind DN used for authentication	`${AUTH_LDAP_BIND_DN}`	False
`AUTH_LDAP_BIND_CREDENTIAL`	`AUTH_LDAP_BIND_CREDENTIAL`	LDAP Credentials used for authentication	`${AUTH_LDAP_BIND_CREDENTIAL}`	False
`AUTH_LDAP_JAAS_SECURITY_DOMAIN`	`AUTH_LDAP_JAAS_SECURITY_DOMAIN`	The JMX ObjectName of the JaasSecurityDomain used to decrypt the password.	`${AUTH_LDAP_JAAS_SECURITY_DOMAIN}`	False
`AUTH_LDAP_BASE_CTX_DN`	`AUTH_LDAP_BASE_CTX_DN`	LDAP Base DN of the top-level context to begin the user search.	`${AUTH_LDAP_BASE_CTX_DN}`	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}).	`${AUTH_LDAP_BASE_FILTER}`	False
`AUTH_LDAP_SEARCH_SCOPE`	`AUTH_LDAP_SEARCH_SCOPE`	The search scope to use.	`${AUTH_LDAP_SEARCH_SCOPE}`	False
`AUTH_LDAP_SEARCH_TIME_LIMIT`	`AUTH_LDAP_SEARCH_TIME_LIMIT`	The timeout in milliseconds for user or role searches.	`${AUTH_LDAP_SEARCH_TIME_LIMIT}`	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.	`${AUTH_LDAP_DISTINGUISHED_NAME_ATTRIBUTE}`	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.	`${AUTH_LDAP_PARSE_USERNAME}`	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.	`${AUTH_LDAP_USERNAME_BEGIN_STRING}`	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.	`${AUTH_LDAP_USERNAME_END_STRING}`	False
`AUTH_LDAP_ROLE_ATTRIBUTE_ID`	`AUTH_LDAP_ROLE_ATTRIBUTE_ID`	Name of the attribute containing the user roles.	`${AUTH_LDAP_ROLE_ATTRIBUTE_ID}`	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.	`${AUTH_LDAP_ROLES_CTX_DN}`	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}).	`${AUTH_LDAP_ROLE_FILTER}`	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.	`${AUTH_LDAP_ROLE_RECURSION}`	False
`AUTH_LDAP_DEFAULT_ROLE`	`AUTH_LDAP_DEFAULT_ROLE`	A role included for all authenticated users	`${AUTH_LDAP_DEFAULT_ROLE}`	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.	`${AUTH_LDAP_ROLE_NAME_ATTRIBUTE_ID}`	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.	`${AUTH_LDAP_PARSE_ROLE_NAME_FROM_DN}`	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.	`${AUTH_LDAP_ROLE_ATTRIBUTE_IS_DN}`	False
`AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK`	`AUTH_LDAP_REFERRAL_USER_ATTRIBUTE_ID_TO_CHECK`	If you are not using referrals, this option can be ignored. 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}`	False

4.2.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.2.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}-rhpamcentr`	8080	http	All the Business Central web server’s ports.
	8443	https
	8001	git-ssh
`${APPLICATION_NAME}-ping`	8888	ping	The JGroups ping port for clustering.
`${APPLICATION_NAME}-kieserver`	8080	http	All the KIE server web server’s ports.
`${APPLICATION_NAME}-kieserver`	8443	https	All the KIE server web server’s ports.
`${APPLICATION_NAME}-rhpamindex`	9200	rest	All the Business Central Indexing Elasticsearch ports.
`${APPLICATION_NAME}-rhpamindex`	9300	transport	All the Business Central Indexing Elasticsearch ports.
`${APPLICATION_NAME}-amq-tcp`	61616	—	The broker’s OpenWire port.
`${APPLICATION_NAME}-mysql`	3306	—	The MySQL server’s port.

4.2.2.2. Routes

Service	Security	Hostname
`${APPLICATION_NAME}-rhpamcentr-http`	none	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`
`${APPLICATION_NAME}-rhpamcentr-https`	TLS passthrough	`${BUSINESS_CENTRAL_HOSTNAME_HTTPS}`
`${APPLICATION_NAME}-kieserver-http`	none	`${KIE_SERVER_HOSTNAME_HTTP}`
`${APPLICATION_NAME}-kieserver-https`	TLS passthrough	`${KIE_SERVER_HOSTNAME_HTTPS}`
`${APPLICATION_NAME}-rhpamindex-http`	none	`${ES_HOSTNAME_HTTP}`

4.2.2.3. Deployment Configurations

4.2.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}-rhpamcentr`	ImageChange
`${APPLICATION_NAME}-kieserver`	ImageChange
`${APPLICATION_NAME}-rhpamindex`	ImageChange
`${APPLICATION_NAME}-amq`	ImageChange
`${APPLICATION_NAME}-mysql`	ImageChange

4.2.2.3.2. Replicas

Deployment	Replicas
`${APPLICATION_NAME}-rhpamcentr`	2
`${APPLICATION_NAME}-kieserver`	2
`${APPLICATION_NAME}-rhpamindex`	1
`${APPLICATION_NAME}-amq`	1
`${APPLICATION_NAME}-mysql`	1

4.2.2.3.3. Pod Template

4.2.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}-rhpamcentr`	`${APPLICATION_NAME}-rhpamsvc`
`${APPLICATION_NAME}-kieserver`	`${APPLICATION_NAME}-rhpamsvc`

4.2.2.3.3.2. Image

Deployment	Image
`${APPLICATION_NAME}-rhpamcentr`	rhpam71-businesscentral-openshift
`${APPLICATION_NAME}-kieserver`	`${KIE_SERVER_IMAGE_STREAM_NAME}`
`${APPLICATION_NAME}-rhpamindex`	rhpam71-businesscentral-indexing-openshift
`${APPLICATION_NAME}-amq`	`${AMQ_IMAGE_STREAM_NAME}`
`${APPLICATION_NAME}-mysql`	mysql

4.2.2.3.3.3. Readiness Probe

${APPLICATION_NAME}-rhpamcentr

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

${APPLICATION_NAME}-kieserver

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

${APPLICATION_NAME}-rhpamindex

Http Get on http://localhost:9200/_cluster/health

${APPLICATION_NAME}-amq

/bin/bash -c /opt/amq/bin/readinessProbe.sh

${APPLICATION_NAME}-mysql

/bin/sh -i -c MYSQL_PWD="$MYSQL_PASSWORD" mysql -h 127.0.0.1 -u $MYSQL_USER -D $MYSQL_DATABASE -e 'SELECT 1'

4.2.2.3.3.4. Liveness Probe

${APPLICATION_NAME}-rhpamcentr

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

${APPLICATION_NAME}-kieserver

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

4.2.2.3.3.5. Exposed Ports

Deployments	Name	Port	Protocol
`${APPLICATION_NAME}-rhpamcentr`	jolokia	8778	`TCP`
	http	8080	`TCP`
	https	8443	`TCP`
	ping	8888	`TCP`
`${APPLICATION_NAME}-kieserver`	jolokia	8778	`TCP`
	http	8080	`TCP`
	https	8443	`TCP`
`${APPLICATION_NAME}-rhpamindex`	es	9300	`TCP`
`${APPLICATION_NAME}-rhpamindex`	http	9200	`TCP`
`${APPLICATION_NAME}-amq`	jolokia	8161	`TCP`
	amqp	5672	`TCP`
	mqtt	1883	`TCP`
	stomp	61613	`TCP`
	artemis	61616	`TCP`
`${APPLICATION_NAME}-mysql`	—	3306	`TCP`

4.2.2.3.3.6. Image Environment Variables

Deployment	Variable name	Description	Example value
`${APPLICATION_NAME}-rhpamcentr`	`KIE_ADMIN_USER`	KIE administrator username	`${KIE_ADMIN_USER}`
	`KIE_ADMIN_PWD`	KIE administrator password	`${KIE_ADMIN_PWD}`
	`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`	KIE server controller password (Sets the org.kie.server.controller.pwd system property)	`${KIE_SERVER_CONTROLLER_PWD}`
	`KIE_SERVER_CONTROLLER_TOKEN`	KIE server controller token for bearer authentication (Sets the org.kie.server.controller.token system property)	`${KIE_SERVER_CONTROLLER_TOKEN}`
	`KIE_SERVER_USER`	KIE server username (Sets the org.kie.server.user system property)	`${KIE_SERVER_USER}`
	`KIE_SERVER_PWD`	KIE server password (Sets the org.kie.server.pwd system property)	`${KIE_SERVER_PWD}`
	`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`	—	`${BUSINESS_CENTRAL_MAVEN_USERNAME}`
	`KIE_MAVEN_PWD`	—	`${BUSINESS_CENTRAL_MAVEN_PASSWORD}`
	`GIT_HOOKS_DIR`	The directory to use for git hooks, if required.	`${GIT_HOOKS_DIR}`
	`HTTPS_KEYSTORE_DIR`	—	`/etc/businesscentral-secret-volume`
	`HTTPS_KEYSTORE`	The name of the keystore file within the secret	`${BUSINESS_CENTRAL_HTTPS_KEYSTORE}`
	`HTTPS_NAME`	The name associated with the server certificate	`${BUSINESS_CENTRAL_HTTPS_NAME}`
	`HTTPS_PASSWORD`	The password for the keystore and certificate	`${BUSINESS_CENTRAL_HTTPS_PASSWORD}`
	`WORKBENCH_ROUTE_NAME`	—	`${APPLICATION_NAME}-rhpamcentr`
	`JGROUPS_PING_PROTOCOL`	—	openshift.DNS_PING
	`OPENSHIFT_DNS_PING_SERVICE_NAME`	—	`${APPLICATION_NAME}-ping`
	`OPENSHIFT_DNS_PING_SERVICE_PORT`	—	8888
	`APPFORMER_ELASTIC_PORT`	Sets the ES http.host property. This will set the http address of the main ES cluster node. Used for communication between nodes in the cluster and the communication with Business Central.	`${APPFORMER_ELASTIC_PORT}`
	`APPFORMER_ELASTIC_CLUSTER_NAME`	Sets the ES cluster.name and configure it on Business Central. Defaults to kie-cluster.	`${APPFORMER_ELASTIC_CLUSTER_NAME}`
	`APPFORMER_ELASTIC_RETRIES`	The number of times that appformer will try to connect to the elasticsearch node before give up.	`${APPFORMER_ELASTIC_RETRIES}`
	`APPFORMER_ELASTIC_HOST`	—	`${APPLICATION_NAME}-rhpamindex`
	`APPFORMER_JMS_BROKER_ADDRESS`	—	`${APPLICATION_NAME}-amq-tcp`
	`APPFORMER_JMS_BROKER_PORT`	The port to connect in the JMS broker. Defaults to 61616	`${APPFORMER_JMS_BROKER_PORT}`
	`APPFORMER_JMS_BROKER_USER`	The username to connect in the JMS broker.	`${APPFORMER_JMS_BROKER_USER}`
	`APPFORMER_JMS_BROKER_PASSWORD`	The password to connect in the JMS broker.	`${APPFORMER_JMS_BROKER_PASSWORD}`
	`SSO_URL`	RH-SSO URL	`${SSO_URL}`
	`SSO_OPENIDCONNECT_DEPLOYMENTS`	—	ROOT.war
	`SSO_REALM`	RH-SSO Realm name	`${SSO_REALM}`
	`SSO_SECRET`	Business Central RH-SSO Client Secret	`${BUSINESS_CENTRAL_SSO_SECRET}`
	`SSO_CLIENT`	Business Central RH-SSO Client name	`${BUSINESS_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>-rhpamcentr-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTP}`
	`HOSTNAME_HTTPS`	Custom hostname for https service route. Leave blank for default hostname, e.g.: secure-<application-name>-rhpamcentr-<project>.<default-domain-suffix>	`${BUSINESS_CENTRAL_HOSTNAME_HTTPS}`
	`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, this option can be ignored. 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}`
`${APPLICATION_NAME}-kieserver`	`AUTO_CONFIGURE_EJB_TIMER`	—	true
	`TIMER_SERVICE_DATA_STORE_REFRESH_INTERVAL`	Sets refresh-interval for the EJB timer database data-store service.	`${TIMER_SERVICE_DATA_STORE_REFRESH_INTERVAL}`
	`DATASOURCES`	—	`RHPAM`
	`RHPAM_DATABASE`	—	`${KIE_SERVER_MYSQL_DB}`
	`RHPAM_DRIVER`	—	mysql
	`RHPAM_USERNAME`	—	`${KIE_SERVER_MYSQL_USER}`
	`RHPAM_PASSWORD`	—	`${KIE_SERVER_MYSQL_PWD}`
	`RHPAM_SERVICE_HOST`	—	`${APPLICATION_NAME}-mysql`
	`RHPAM_SERVICE_PORT`	—	3306
	`KIE_SERVER_PERSISTENCE_DIALECT`	—	org.hibernate.dialect.MySQLDialect
	`KIE_SERVER_PERSISTENCE_DS`	KIE server persistence datasource (Sets the org.kie.server.persistence.ds system property)	`${KIE_SERVER_PERSISTENCE_DS}`
	`RHPAM_JNDI`	—	`${KIE_SERVER_PERSISTENCE_DS}`
	`RHPAM_JTA`	—	true
	`DROOLS_SERVER_FILTER_CLASSES`	KIE server class filtering (Sets the org.drools.server.filter.classes system property)	`${DROOLS_SERVER_FILTER_CLASSES}`
	`KIE_ADMIN_PWD`	KIE administrator password	`${KIE_ADMIN_PWD}`
	`KIE_ADMIN_USER`	KIE administrator username	`${KIE_ADMIN_USER}`
	`KIE_MBEANS`	KIE server mbeans enabled/disabled (Sets the kie.mbeans and kie.scanner.mbeans system properties)	`${KIE_MBEANS}`
	`KIE_SERVER_BYPASS_AUTH_USER`	KIE server bypass auth user (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`	KIE server controller password (Sets the org.kie.server.controller.pwd system property)	`${KIE_SERVER_CONTROLLER_PWD}`
	`KIE_SERVER_CONTROLLER_TOKEN`	KIE server controller token for bearer authentication (Sets the org.kie.server.controller.token system property)	`${KIE_SERVER_CONTROLLER_TOKEN}`
	`KIE_SERVER_CONTROLLER_SERVICE`	—	`${APPLICATION_NAME}-rhpamcentr`
	`KIE_SERVER_CONTROLLER_PROTOCOL`	—	ws
	`KIE_SERVER_ID`	—	`${APPLICATION_NAME}-kieserver`
	`KIE_SERVER_HOST`	Custom hostname for http service route, if set will also configure the KIE_SERVER_HOST. Leave blank for default hostname, e.g.: <application-name>-kieserver-<project>.<default-domain-suffix>	`${KIE_SERVER_HOSTNAME_HTTP}`
	`KIE_SERVER_ROUTE_NAME`	—	`${APPLICATION_NAME}-kieserver`
	`KIE_SERVER_USE_SECURE_ROUTE_NAME`	Use https for the KIE_SERVER_HOST when it is not explicit configured to a custom value.	`${KIE_SERVER_USE_SECURE_ROUTE_NAME}`
	`KIE_SERVER_PWD`	KIE server password (Sets the org.kie.server.pwd system property)	`${KIE_SERVER_PWD}`
	`KIE_SERVER_USER`	KIE server username (Sets the org.kie.server.user system property)	`${KIE_SERVER_USER}`
	`MAVEN_REPOS`	—	RHPAMCENTR,EXTERNAL
	`RHPAMCENTR_MAVEN_REPO_SERVICE`	—	`${APPLICATION_NAME}-rhpamcentr`
	`RHPAMCENTR_MAVEN_REPO_PATH`	—	`/maven2/`
	`RHPAMCENTR_MAVEN_REPO_USERNAME`	Username to access the Maven repository, if required.	`${BUSINESS_CENTRAL_MAVEN_USERNAME}`
	`RHPAMCENTR_MAVEN_REPO_PASSWORD`	Password to access the Maven repository, if required.	`${BUSINESS_CENTRAL_MAVEN_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}`
	`HTTPS_KEYSTORE_DIR`	—	`/etc/kieserver-secret-volume`
	`HTTPS_KEYSTORE`	The name of the keystore file within the secret	`${KIE_SERVER_HTTPS_KEYSTORE}`
	`HTTPS_NAME`	The name associated with the server certificate	`${KIE_SERVER_HTTPS_NAME}`
	`HTTPS_PASSWORD`	The password for the keystore and certificate	`${KIE_SERVER_HTTPS_PASSWORD}`
	`SSO_URL`	RH-SSO URL	`${SSO_URL}`
	`SSO_OPENIDCONNECT_DEPLOYMENTS`	—	ROOT.war
	`SSO_REALM`	RH-SSO Realm name	`${SSO_REALM}`
	`SSO_SECRET`	Business Central RH-SSO Client Secret	`${KIE_SERVER_SSO_SECRET}`
	`SSO_CLIENT`	Business Central 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>-rhpamcentr-<project>.<default-domain-suffix>	`${KIE_SERVER_HOSTNAME_HTTP}`
	`HOSTNAME_HTTPS`	Custom hostname for https service route. Leave blank for default hostname, e.g.: secure-<application-name>-rhpamcentr-<project>.<default-domain-suffix>	`${KIE_SERVER_HOSTNAME_HTTPS}`
	`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, this option can be ignored. 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}`
`${APPLICATION_NAME}-rhpamindex`	`ES_CLUSTER_NAME`	—	`${APPFORMER_ELASTIC_CLUSTER_NAME}`
	`ES_NODE_NAME`	Sets the ES node.name property. Defaults to HOSTNAME env value.	`${ES_NODE_NAME}`
	`ES_TRANSPORT_HOST`	Sets the ES transport.host property. This will set the transport address of the main ES cluster node. Used for communication between nodes in the cluster. Defaults to container address.	`${ES_TRANSPORT_HOST}`
	`ES_TRANSPORT_TCP_PORT`	—	`${APPFORMER_ELASTIC_PORT}`
	`ES_HTTP_PORT`	Sets the ES http.port property. This will set the http port of the main ES cluster node. Used to interact with cluster rest api.	`${ES_HTTP_PORT}`
	`ES_HTTP_HOST`	Sets the ES http.host property. This will set the http address of the main ES cluster node. Used to interact with cluster rest api. Defaults to the container ip address	`${ES_HTTP_HOST}`
	`ES_JAVA_OPTS`	Appends custom jvm configurations/properties to ES jvm.options configuration file.	`${ES_JAVA_OPTS}`
`${APPLICATION_NAME}-amq`	`AMQ_USER`	—	`${APPFORMER_JMS_BROKER_USER}`
	`AMQ_PASSWORD`	—	`${APPFORMER_JMS_BROKER_PASSWORD}`
	`AMQ_ROLE`	User role for standard broker user.	`${AMQ_ROLE}`
	`AMQ_NAME`	The name of the broker	`${AMQ_NAME}`
	`AMQ_TRANSPORTS`	—	openwire
	`AMQ_GLOBAL_MAX_SIZE`	Maximum amount of memory which message data may consume (Default: Undefined, half of the system’s memory).	`${AMQ_GLOBAL_MAX_SIZE}`
`${APPLICATION_NAME}-mysql`	`MYSQL_USER`	KIE server MySQL database username	`${KIE_SERVER_MYSQL_USER}`
	`MYSQL_PASSWORD`	—	`${KIE_SERVER_MYSQL_PWD}`
	`MYSQL_DATABASE`	—	`${KIE_SERVER_MYSQL_DB}`

4.2.2.3.3.7. Volumes

Deployment	Name	mountPath	Purpose	readOnly
`${APPLICATION_NAME}-rhpamcentr`	businesscentral-keystore-volume	`/etc/businesscentral-secret-volume`	ssl certs	True
`${APPLICATION_NAME}-kieserver`	kieserver-keystore-volume	`/etc/kieserver-secret-volume`	ssl certs	True
`${APPLICATION_NAME}-rhpamindex`	`${APPLICATION_NAME}-rhpamindex-pvol`	`/opt/elasticsearch/data`	rhpamindex	false
`${APPLICATION_NAME}-mysql`	`${APPLICATION_NAME}-mysql-pvol`	`/var/lib/mysql/data`	mysql	false

4.2.2.4. External Dependencies

4.2.2.4.1. Volume Claims

Name	Access Mode
`${APPLICATION_NAME}-rhpamcentr-claim`	ReadWriteMany
`${APPLICATION_NAME}-mysql-claim`	ReadWriteOnce
`${APPLICATION_NAME}-rhpamindex-claim`	ReadWriteOnce

4.2.2.4.2. Secrets

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

businesscentral-app-secret kieserver-app-secret

4.2.2.4.3. Clustering

Clustering in OpenShift EAP is achieved through one of two discovery mechanisms: Kubernetes or DNS. This is done by configuring the JGroups protocol stack in standalone-openshift.xml with either the <openshift.KUBE_PING/> or <openshift.DNS_PING/> elements. The templates are configured to use DNS_PING, however `KUBE_PING`is the default used by the image.

The discovery mechanism used is specified by the JGROUPS_PING_PROTOCOL environment variable which can be set to either openshift.DNS_PING or openshift.KUBE_PING. openshift.KUBE_PING is the default used by the image if no value is specified for JGROUPS_PING_PROTOCOL.

For DNS_PING to work, the following steps must be taken:

The OPENSHIFT_DNS_PING_SERVICE_NAME environment variable must be set to the name of the ping service for the cluster (see table above). If not set, the server will act as if it is a single-node cluster (a "cluster of one").
The OPENSHIFT_DNS_PING_SERVICE_PORT environment variables should be set to the port number on which the ping service is exposed (see table above). The DNS_PING protocol will attempt to discern the port from the SRV records, if it can, otherwise it will default to 8888.
A ping service which exposes the ping port must be defined. This service should be "headless" (ClusterIP=None) and must have the following:
1. The port must be named for port discovery to work.
2. It must be annotated with service.alpha.kubernetes.io/tolerate-unready-endpoints set to "true". Omitting this annotation will result in each node forming their own "cluster of one" during startup, then merging their cluster into the other nodes' clusters after startup (as the other nodes are not detected until after they have started).

Example ping service for use with DNS_PING

kind: Service
apiVersion: v1
spec:
    clusterIP: None
    ports:
    - name: ping
      port: 8888
    selector:
        deploymentConfig: eap-app
metadata:
    name: eap-app-ping
    annotations:
        service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"
        description: "The JGroups ping port for clustering."

For KUBE_PING to work, the following steps must be taken:

The OPENSHIFT_KUBE_PING_NAMESPACE environment variable must be set (see table above). If not set, the server will act as if it is a single-node cluster (a "cluster of one").
The OPENSHIFT_KUBE_PING_LABELS environment variables should be set (see table above). If not set, pods outside of your application (albeit in your namespace) will try to join.
Authorization must be granted to the service account the pod is running under to be allowed to access Kubernetes' REST api. This is done on the command line.

Example 4.1. Policy commands

Using the default service account in the myproject namespace:

oc policy add-role-to-user view system:serviceaccount:myproject:default -n myproject

Using the eap-service-account in the myproject namespace:

oc policy add-role-to-user view system:serviceaccount:myproject:eap-service-account -n myproject

4.3. OpenShift usage quick reference

To deploy, monitor, manage, and undeploy Red Hat Process Automation 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 CLI operation.

Chapter 4. OpenShift template reference information

4.1. rhpam71-authoring

4.1.1. Parameters

4.1.2. Objects

4.1.2.1. Services

4.1.2.2. Routes

4.1.2.3. Deployment Configurations

4.1.2.3.1. Triggers

4.1.2.3.2. Replicas

4.1.2.3.3. Pod Template

4.1.2.3.3.1. Service Accounts

4.1.2.3.3.2. Image

4.1.2.3.3.3. Readiness Probe

4.1.2.3.3.4. Liveness Probe

4.1.2.3.3.5. Exposed Ports

4.1.2.3.3.6. Image Environment Variables

4.1.2.3.3.7. Volumes

4.1.2.4. External Dependencies

4.1.2.4.1. Volume Claims

4.1.2.4.2. Secrets

4.2. rhpam71-authoring-ha

4.2.1. Parameters

4.2.2. Objects

4.2.2.1. Services

4.2.2.2. Routes

4.2.2.3. Deployment Configurations

4.2.2.3.1. Triggers

4.2.2.3.2. Replicas

4.2.2.3.3. Pod Template

4.2.2.3.3.1. Service Accounts

4.2.2.3.3.2. Image

4.2.2.3.3.3. Readiness Probe

4.2.2.3.3.4. Liveness Probe

4.2.2.3.3.5. Exposed Ports

4.2.2.3.3.6. Image Environment Variables

4.2.2.3.3.7. Volumes

4.2.2.4. External Dependencies

4.2.2.4.1. Volume Claims

4.2.2.4.2. Secrets

4.2.2.4.3. Clustering

4.3. OpenShift usage quick reference

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

Making open source more inclusive

About Red Hat

Red Hat legal and privacy links

Red Hat legal and privacy links