Application template for JDG 6.5 applications.
For simple authentication, set
USERNAME=<username> PASSWORD=<password>
This will enable user authentication with the datagrid. Provided username and password will be used to access the cache over both HTTPS and HotRod. With this case, the user will have all permissions configured.
Restrictions for password:
at least 8 characters at least 1 digit at least 1 non-alphanumeric symbol must be different than username must not be root, admin, or administrator
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 name for the application. |
datagrid-app |
True |
|
— |
Custom hostname for http service route. Leave blank for default hostname, e.g.: <application-name>-<project>.<default-domain-suffix> |
— |
False |
|
|
User name for JDG user. |
|
False |
|
|
The password to access the JDG Caches. 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). (optional) |
|
False |
|
— |
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 |
|
|
Comma-separated list of connector types that should be configured (defaults to 'memcached,hotrod,rest') |
hotrod,memcached,rest |
False |
|
|
Comma-separated list of caches to configure. By default, a distributed-cache, with a mode of SYNC will be configured for each entry. |
|
False |
|
|
Comma-separated list of caches to configure for use by Red Hat JBoss Data Virtualization for materialization of views. Three caches will be created for each named cache: <name>, <name>_staging and <name>_alias. |
|
False |
|
|
Default cache type for all caches. If empty then distributed will be the default |
|
False |
|
|
|
False |
|
|
|
The name of the cache to expose through this memcached connector (defaults to 'default') |
default |
False |
|
|
The domain, declared in the security subsystem, that should be used to authenticate access to the REST endpoint |
|
False |
|
|
JGroups cluster password |
|
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. |
|
11211 |
— |
Memcached service for clustered applications. |
|
11333 |
— |
Hot Rod service for clustered applications. |
|
8888 |
ping |
The JGroups ping port for clustering. |
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 |
|
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 |
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 |
| Deployments | Name | Port | Protocol |
|---|---|---|---|
|
jolokia |
8778 |
|
http |
8080 |
|
|
ping |
8888 |
|
|
memcached |
11211 |
|
|
hotrod-internal |
11222 |
|
|
hotrod |
11333 |
|
| Deployment | Variable name | Description | Example value |
|---|---|---|---|
|
|
User name for JDG user. |
|
|
The password to access the JDG Caches. 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). (optional) |
|
|
|
— |
openshift.DNS_PING |
|
|
— |
|
|
|
— |
8888 |
|
|
Comma-separated list of connector types that should be configured (defaults to 'memcached,hotrod,rest') |
|
|
|
Comma-separated list of caches to configure. By default, a distributed-cache, with a mode of SYNC will be configured for each entry. |
|
|
|
Comma-separated list of caches to configure. By default, a distributed-cache, with a mode of SYNC will be configured for each entry. |
|
|
|
Default cache type for all caches. If empty then distributed will be the default |
|
|
|
|
||
|
— |
|
|
|
The name of the cache to expose through this memcached connector (defaults to 'default') |
|
|
|
The domain, declared in the security subsystem, that should be used to authenticate access to the REST endpoint |
|
|
|
The password to access the JDG Caches. 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). (optional) |
|