| Page Properties | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
You can use the Incremental DataStage Deployment task to deploy an entire directory of ISX files to an existing DataStage Project. Functionally, this is the equivalent of deleting everything from the existing project, importing all ISX files, provisioning all QualityStage rules and compiling all Jobs, Sequence, Server Routines and BuildOps. However, the task will minimize the deployment time by performing as few operations based on the content of the existing project.
| Info | ||
|---|---|---|
| ||
This task is available after installing the MettleCI - DataStage Deployment Plugin (dm-dsdeploy-plugin.jar) |
To configure an Incremental DataStage Deployment task
StepsProperties Configuration Task in Bamboo Jobs to replace specially formatted text placeholders in DataStage configuration files (e.g. DSParams) with environment-specific values as part of the MettleCI-automated deployment process. The replacement values can be taken from Plan Variables (e.g. ${bamboo.buildResultKey}) and / or MettleCI Override files.
Placeholders are written in the following format: ${PlanVariableNameOrOverrideFileReference}
Using the Properties Configuration Task user interface
Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
Click the name of an existing
...
Properties Configuration Task or click Add Task and then search '
...
Properties Configuration' to easily locate
...
the Properties Configuration Task type, in order to create a new task.
Complete the following settings:
...
Task Description | A description of the task, which is displayed in Bamboo. |
|---|---|
Disable this task | Check, or clear, to selectively run this task. |
...
Optional: Root directory containing ISX files to deploy
If no value is specified, the agents working directory will be used
...
Required if previous option is checked.
Specifies a directory of parameter set value files. This should match the format found on your DataStage Engine under ${DSHOME}../Projects/${Project Name}/ParameterSets directory
Base Directory | Optional: A relative path from the working directory to the root directory of configuration file(s). This path will be the root of file patterns. If not specified, the agent working directory will be used. | ||
|---|---|---|---|
File Patterns | Relative paths to different configuration files from the base directory (wild card is acceptable). Each line is one pattern. Examples could include …
| ||
Override File | Optional: A relative path from the working directory to a Java properties file containing variable values to be used during substitution. | ||
Output Directory | Optional: A relative path from working directory to write all filled configuration files to (all relative path from the base directory will be preserved. If output directory is the same as base directory, all original configuration files will be replaced. If not specified, the agent working directory will be used. |
Click Save
Using the Properties Configuration Task in a YAML pipeline
| Code Block | ||
|---|---|---|
| ||
- mci-properties-configuration:
baseDir: datastage
filePatterns: |-
*.apt
DSParams
Parameter Sets/*/*
outputDir: config
overrideFile: var.${bamboo.EnvironmentID}
description: Substitute parameters in DataStage configuration file |