"path": "/@websphere.cell@/JDBC Providers/@NAME@",
"description": "Discovered WebSphereJDBCProvider",
To easily tokenize values in a snippet, use the WebSphere – Templatize Snippet Configuration Data step. This step can replace values such as the cell name, server name, and so on with tokens. Additionally, the User Defined Tokenization property of this step runs a find-and-replace operation on text in your configuration data. You can easily use the User Defined Tokenization field to convert values to tokens in your configuration data.
The following diagram shows a process that retrieves a snippet from source control, replaces the tokenized values, and then checks in the snippet to source control and updates the component version.
IBM UrbanCode Deploy properties (environment properties, component properties, resource properties, and so on) are used to replace the tokenized values. The following examples show the use of component process properties:
When the process runs, you are prompted to enter values for the component process properties, as shown in the following screen capture:
In this example, the tokenized values in a copy of the JDBCProvider.json snippet are replaced, and then the snippet is moved to cell directory under the cell component artifact.
Instead of replacing all values as shown in the previous process, you can leave some values tokenized, and then use properties to set those values when the Apply process runs. For example, if the JVM heap size property changes for different environments, you can leave the JVM heap size tokenized in the snippet. In the Apply process, replace the token with a corresponding property.