Certified and Dockerized Templates Superposition

By default, when new dockerized stack templates are integrated during Platform upgrade, they are automatically set as published for being used by default (whilst legacy certified ones remain listed in JCA). However, since this setting can be easily adjusted, potentially there could be various combinations of published/unpublished template types being provisioned for a single stack,  which could vary in actual template designation. Thus, if modifying the default settings, you should consider some specifics of different template types correlation.

Note: In order to avoid possible confusion on certified and dockerized templates superposition, it is highly recommended to keep only one of them published per each software stack.
If making multiple same-named templates of any type simultaneously available, they will be automatically grouped together (based on Display Name parameter) into the expandable list of server versions within the topology wizard.

Herewith, if providing several minor stack version of the same major release, templates are automatically grouped further under the {major_version}.x.x nested list.

You could also notice that some dockerized templates are assigned multiple identifiers In the Templates JCA sections - e.g. Tomcat:

  • tomcat
  • tomcat6
  • tomcat7
  • tomcat85

Here, identifiers with an indicated version (tomcatX) represent Node Type aliases and hold metadata on certified templates this image substitutes. As a result, the dockerized Tomcat template (if published) will be used when referring directly to the tomcat6, tomcat7, or tomcat85 IDs within API or JPS.

The table below presents a short overview of published (✔) and unpublished (-) templates superposition on the example of referring to the *tomcat7 *node identifier:

The certified tomcat7 template is used by default.
-The dockerized tomcat7 template is used by default.
-The certified tomcat7 template is used by default.
--The certified tomcat7 template is used by default.

This way, dockerized template would be used only if it’s published solely, whilst in the rest of cases (i.e. when different type templates are both published/unpublished or only certified one is available) the corresponding legacy template will be fetched.

What’s next?