|
6 | 6 | "iconClass": "icon-eap",
|
7 | 7 | "tags": "eap,javaee,java,jboss",
|
8 | 8 | "version": "1.4.10",
|
9 |
| - "openshift.io/display-name": "JBoss EAP 6.4 + A-MQ (with https)", |
| 9 | + "openshift.io/display-name": "JBoss EAP 6.4 + AMQ (Persistent)", |
10 | 10 | "openshift.io/provider-display-name": "Red Hat, Inc.",
|
11 |
| - "description": "An example EAP 6 A-MQ application. For more information about using this template, see https://github.com/jboss-openshift/application-templates.", |
12 |
| - "template.openshift.io/long-description": "This template defines resources needed to develop Red Hat Enterprise Application Server 6.4 based application, including a build configuration, application deployment configuration, using Red Hat JBoss A-MQ with persistence and secure communication using https.", |
| 11 | + "description": "An example EAP 6 AMQ application. For more information about using this template, see https://github.com/jboss-openshift/application-templates.", |
| 12 | + "template.openshift.io/long-description": "This template defines resources needed to develop Red Hat Enterprise Application Server 6.4 based application, including a build configuration, application deployment configuration, using Red Hat JBoss AMQ with persistence and secure communication using passthrough TLS.", |
13 | 13 | "template.openshift.io/documentation-url": "https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/",
|
14 | 14 | "template.openshift.io/support-url": "https://access.redhat.com"
|
15 | 15 | },
|
|
19 | 19 | "template": "eap64-amq-persistent-s2i",
|
20 | 20 | "xpaas": "1.4.10"
|
21 | 21 | },
|
22 |
| - "message": "A new EAP 6 and A-MQ persistent based application with SSL support has been created in your project. The username/password for accessing the A-MQ service is ${MQ_USERNAME}/${MQ_PASSWORD}. Please be sure to create the following secrets: \"${HTTPS_SECRET}\" containing the ${HTTPS_KEYSTORE} file used for serving secure content; \"${JGROUPS_ENCRYPT_SECRET}\" containing the ${JGROUPS_ENCRYPT_KEYSTORE} file used for securing JGroups communications.", |
| 22 | + "message": "A new EAP 6 and AMQ persistent based application with SSL support has been created in your project. The username/password for accessing the AMQ service is ${MQ_USERNAME}/${MQ_PASSWORD}. Please be sure to create the following secrets: \"${HTTPS_SECRET}\" containing the ${HTTPS_KEYSTORE} file used for serving secure content; \"${JGROUPS_ENCRYPT_SECRET}\" containing the ${JGROUPS_ENCRYPT_KEYSTORE} file used for securing JGroups communications.", |
23 | 23 | "parameters": [
|
24 | 24 | {
|
25 | 25 | "displayName": "Application Name",
|
|
64 | 64 | "required": false
|
65 | 65 | },
|
66 | 66 | {
|
67 |
| - "displayName": "A-MQ Volume Size", |
68 |
| - "description": "Size of the volume used by A-MQ for persisting messages.", |
| 67 | + "displayName": "AMQ Volume Size", |
| 68 | + "description": "Size of the volume used by AMQ for persisting messages.", |
69 | 69 | "name": "VOLUME_CAPACITY",
|
70 | 70 | "value": "1Gi",
|
71 | 71 | "required": true
|
|
85 | 85 | "required": false
|
86 | 86 | },
|
87 | 87 | {
|
88 |
| - "displayName": "A-MQ Protocols", |
| 88 | + "displayName": "AMQ Protocols", |
89 | 89 | "description": "Broker protocols to configure, separated by commas. Allowed values are: `openwire`, `amqp`, `stomp` and `mqtt`. Only `openwire` is supported by EAP.",
|
90 | 90 | "name": "MQ_PROTOCOL",
|
91 | 91 | "value": "openwire",
|
|
106 | 106 | "required": false
|
107 | 107 | },
|
108 | 108 | {
|
109 |
| - "displayName": "A-MQ Serializable Packages", |
| 109 | + "displayName": "AMQ Serializable Packages", |
110 | 110 | "description": "List of packages that are allowed to be serialized for use in ObjectMessage, separated by commas. If your app doesn't use ObjectMessages, leave this blank. This is a security enforcement. For the rationale, see http://activemq.apache.org/objectmessage.html",
|
111 | 111 | "name": "MQ_SERIALIZABLE_PACKAGES",
|
112 | 112 | "value": "",
|
|
148 | 148 | "required": false
|
149 | 149 | },
|
150 | 150 | {
|
151 |
| - "displayName": "A-MQ Username", |
| 151 | + "displayName": "AMQ Username", |
152 | 152 | "description": "User name for standard broker user. It is required for connecting to the broker. If left empty, it will be generated.",
|
153 | 153 | "name": "MQ_USERNAME",
|
154 | 154 | "from": "user[a-zA-Z0-9]{3}",
|
155 | 155 | "generate": "expression",
|
156 | 156 | "required": false
|
157 | 157 | },
|
158 | 158 | {
|
159 |
| - "displayName": "A-MQ Password", |
| 159 | + "displayName": "AMQ Password", |
160 | 160 | "description": "Password for standard broker user. It is required for connecting to the broker. If left empty, it will be generated.",
|
161 | 161 | "name": "MQ_PASSWORD",
|
162 | 162 | "from": "[a-zA-Z0-9]{8}",
|
163 | 163 | "generate": "expression",
|
164 | 164 | "required": false
|
165 | 165 | },
|
166 | 166 | {
|
167 |
| - "displayName": "A-MQ Mesh Discovery Type", |
| 167 | + "displayName": "AMQ Mesh Discovery Type", |
168 | 168 | "description": "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.",
|
169 | 169 | "name": "AMQ_MESH_DISCOVERY_TYPE",
|
170 | 170 | "value": "dns",
|
171 | 171 | "required": false
|
172 | 172 | },
|
173 | 173 | {
|
174 |
| - "displayName": "A-MQ Storage Limit", |
175 |
| - "description": "The A-MQ storage usage limit", |
| 174 | + "displayName": "AMQ Storage Limit", |
| 175 | + "description": "The AMQ storage usage limit", |
176 | 176 | "name": "AMQ_STORAGE_USAGE_LIMIT",
|
177 | 177 | "value": "100 gb",
|
178 | 178 | "required": false
|
|
0 commit comments