An example BPM Suite application with A-MQ and a PostgreSQL database. For more information about using this template, see https://github.com/jboss-openshift/application-templates.
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 |
---|---|---|---|---|
|
|
The KIE Container deployment configuration in format: containerId=groupId:artifactId:version|c2=g2:a2:v2 |
processserver-library=org.openshift.quickstarts:processserver-library:1.4.0.Final |
False |
|
|
The protocol to access the KIE Server REST interface. |
https |
False |
|
|
The port to access the KIE Server REST interface. |
8443 |
False |
|
|
The user name to access the KIE Server REST or JMS interface. |
kieserver |
False |
|
|
The password to access the KIE Server REST or JMS interface. Must be different than username; must not be root, admin, or administrator; must contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), and 1 non-alphanumeric symbol(s). |
— |
False |
|
|
JAAS LoginContext domain that shall be used to authenticate users when using JMS. |
other |
False |
|
|
JNDI name of request queue for JMS. |
queue/KIE.SERVER.REQUEST |
False |
|
|
JNDI name of response queue for JMS. |
queue/KIE.SERVER.RESPONSE |
False |
|
|
JNDI name of executor queue for JMS. |
queue/KIE.SERVER.EXECUTOR |
False |
|
|
Hibernate persistence dialect. |
org.hibernate.dialect.PostgreSQL82Dialect |
False |
|
— |
The name for the application. |
kie-app |
True |
|
— |
Custom hostname for http service route. Leave blank for default hostname, e.g.: <application-name>-<project>.<default-domain-suffix> |
— |
False |
|
— |
Custom hostname for https service route. Leave blank for default hostname, e.g.: secure-<application-name>-<project>.<default-domain-suffix> |
— |
False |
|
— |
Git source URI for application |
True |
|
|
— |
Git branch/tag reference |
1.4 |
False |
|
— |
Path within Git project to build; empty for root project directory. |
processserver/library |
False |
|
|
Database JNDI name used by application to resolve the datasource, e.g. java:/jboss/datasources/ExampleDS |
java:jboss/datasources/ExampleDS |
False |
|
|
Database name |
root |
True |
|
— |
Size of persistent storage for database volume. |
1Gi |
True |
|
|
JNDI name for connection factory used by applications to connect to the broker, e.g. java:/JmsXA |
java:/JmsXA |
False |
|
|
Split the data directory for each node in a mesh. |
false |
False |
|
|
Broker protocols to configure, separated by commas. Allowed values are: |
openwire |
False |
|
|
Queue names, separated by commas. These queues will be automatically created when the broker starts. Also, they will be made accessible as JNDI resources in EAP. |
KIE.SERVER.REQUEST,KIE.SERVER.RESPONSE,KIE.SERVER.EXECUTOR |
False |
|
|
Topic names, separated by commas. These topics will be automatically created when the broker starts. Also, they will be made accessible as JNDI resources in EAP. |
— |
False |
|
— |
The name of the secret containing the keystore file |
processserver-app-secret |
False |
|
|
The name of the keystore file within the secret |
keystore.jks |
False |
|
|
The name associated with the server certificate |
jboss |
False |
|
|
The password for the keystore and certificate |
mykeystorepass |
False |
|
|
Database user name |
— |
True |
|
|
Database user password |
— |
True |
|
|
Sets xa-pool/min-pool-size for the configured datasource. |
— |
False |
|
|
Sets xa-pool/max-pool-size for the configured datasource. |
— |
False |
|
|
Sets transaction-isolation for the configured datasource. |
— |
False |
|
|
The maximum number of client connections allowed. This also sets the maximum number of prepared transactions. |
— |
False |
|
|
Configures how much memory is dedicated to PostgreSQL for caching data. |
— |
False |
|
|
User name for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. |
— |
False |
|
|
Password for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. |
— |
False |
|
|
The discovery agent type to use for discovering mesh endpoints. 'dns' will use OpenShift’s DNS service to resolve endpoints. 'kube' will use Kubernetes REST API to resolve service endpoints. If using 'kube' the service account for the pod must have the 'view' role, which can be added via 'oc policy add-role-to-user view system:serviceaccount:<namespace>:default' where <namespace> is the project namespace. |
dns |
False |
|
|
The A-MQ storage usage limit |
100 gb |
False |
|
— |
GitHub trigger secret |
— |
True |
|
— |
Generic build trigger secret |
— |
True |
|
— |
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 |
|
— |
Maven mirror to use for S2I builds |
— |
False |
|
— |
List of directories from which archives will be copied into the deployment folder. If unspecified, all archives in /target will be copied. |
— |
False |
|
— |
The tag to use for the "postgresql" image stream. Typically, this aligns with the major.minor version of PostgreSQL. |
9.5 |
True |
|
— |
Container memory limit |
1Gi |
False |
The CLI supports various object types. A list of these object types as well as their abbreviations can be found in the Openshift documentation.
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 |
---|---|---|---|
|
8080 |
— |
The web server’s http port. |
|
8443 |
— |
The web server’s https port. |
|
5432 |
— |
The database server’s port. |
|
61616 |
— |
The broker’s OpenWire port. |
|
61616 |
mesh |
Supports node discovery for mesh formation. |
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 |
---|---|---|
|
none |
|
|
TLS passthrough |
|
A buildConfig
describes a single build definition and a set of triggers for when a new build should be created.
A buildConfig
is a REST object, which can be used in a POST to the API server to create a new instance. Refer to
the Openshift documentation
for more information.
S2I image | link | Build output | BuildTriggers and Settings |
---|---|---|---|
jboss-processserver64-openshift:1.6 |
|
GitHub, Generic, ImageChange, ConfigChange |
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.
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 |
---|---|
|
ImageChange |
|
ImageChange |
|
ImageChange |
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 |
---|---|
|
1 |
|
1 |
|
1 |
Deployment | Image |
---|---|
|
|
|
postgresql |
|
jboss-amq-63 |
/bin/bash -c /opt/eap/bin/readinessProbe.sh
/bin/sh -i -c psql -h 127.0.0.1 -U $POSTGRESQL_USER -q -d $POSTGRESQL_DATABASE -c 'SELECT 1'
/bin/bash -c /opt/amq/bin/readinessProbe.sh
/bin/bash -c /opt/eap/bin/livenessProbe.sh
tcpSocket on port 5432
Deployments | Name | Port | Protocol |
---|---|---|---|
|
jolokia |
8778 |
|
http |
8080 |
|
|
https |
8443 |
|
|
|
— |
5432 |
|
|
jolokia |
8778 |
|
amqp |
5672 |
|
|
amqp-ssl |
5671 |
|
|
mqtt |
1883 |
|
|
stomp |
61613 |
|
|
stomp-ssl |
61612 |
|
|
tcp |
61616 |
|
|
tcp-ssl |
61617 |
|
Deployment | Variable name | Description | Example value |
---|---|---|---|
|
|
The KIE Container deployment configuration in format: containerId=groupId:artifactId:version|c2=g2:a2:v2 |
|
|
The protocol to access the KIE Server REST interface. |
|
|
|
The port to access the KIE Server REST interface. |
|
|
|
The user name to access the KIE Server REST or JMS interface. |
|
|
|
The password to access the KIE Server REST or JMS interface. Must be different than username; must not be root, admin, or administrator; must contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), and 1 non-alphanumeric symbol(s). |
|
|
|
JAAS LoginContext domain that shall be used to authenticate users when using JMS. |
|
|
|
JNDI name of request queue for JMS. |
|
|
|
JNDI name of response queue for JMS. |
|
|
|
JNDI name of executor queue for JMS. |
|
|
|
— |
|
|
|
JNDI name for connection factory used by applications to connect to the broker, e.g. java:/JmsXA |
|
|
|
User name for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. |
|
|
|
Password for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. |
|
|
|
Broker protocols to configure, separated by commas. Allowed values are: |
tcp |
|
|
Queue names, separated by commas. These queues will be automatically created when the broker starts. Also, they will be made accessible as JNDI resources in EAP. |
|
|
|
Topic names, separated by commas. These topics will be automatically created when the broker starts. Also, they will be made accessible as JNDI resources in EAP. |
|
|
|
Hibernate persistence dialect. |
|
|
|
— |
|
|
|
— |
|
|
|
Database JNDI name used by application to resolve the datasource, e.g. java:/jboss/datasources/ExampleDS |
|
|
|
Database user name |
|
|
|
Database user password |
|
|
|
Database name |
|
|
|
Sets xa-pool/min-pool-size for the configured datasource. |
|
|
|
Sets xa-pool/max-pool-size for the configured datasource. |
|
|
|
Sets transaction-isolation for the configured datasource. |
|
|
|
— |
|
|
|
Database user name |
|
|
|
Database user password |
|
|
|
Database name |
|
|
|
Sets xa-pool/min-pool-size for the configured datasource. |
|
|
|
Sets xa-pool/max-pool-size for the configured datasource. |
|
|
|
Sets transaction-isolation for the configured datasource. |
|
|
|
— |
false |
|
|
— |
true |
|
|
— |
|
|
|
The name of the keystore file within the secret |
|
|
|
The name associated with the server certificate |
|
|
|
The password for the keystore and certificate |
|
|
|
|
Database user name |
|
|
Database user password |
|
|
|
Database name |
|
|
|
The maximum number of client connections allowed. This also sets the maximum number of prepared transactions. |
|
|
|
Configures how much memory is dedicated to PostgreSQL for caching data. |
|
|
|
|
User name for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. |
|
|
Password for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. |
|
|
|
Broker protocols to configure, separated by commas. Allowed values are: |
|
|
|
Split the data directory for each node in a mesh. |
|
|
|
The discovery agent type to use for discovering mesh endpoints. 'dns' will use OpenShift’s DNS service to resolve endpoints. 'kube' will use Kubernetes REST API to resolve service endpoints. If using 'kube' the service account for the pod must have the 'view' role, which can be added via 'oc policy add-role-to-user view system:serviceaccount:<namespace>:default' where <namespace> is the project namespace. |
|
|
|
— |
|
|
|
— |
— |
|
|
The A-MQ storage usage limit |
|
Deployment | Name | mountPath | Purpose | readOnly |
---|---|---|---|---|
|
processserver-keystore-volume |
|
ssl certs |
True |
|
|
|
postgresql |
false |
|
|
|
kahadb |
false |
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 |
---|---|
|
ReadWriteOnce |
|
ReadWriteMany |