Quick Info
Description
Configuration templating system built into HCL Launch. Configuration Templates are text files held within HCL Launch that have placeholders for variable configuration. This plugin writes out these configuration files at deployment time substituting in environment or target specific properties. This plugin also reads in properties from a file.Quick Info
20.1155711 
launch-configmanagement-20.1155711.zip
Uploaded: 21-Apr-2023 14:07
launch-configmanagement-19.1150664.zip
Uploaded: 01-Feb-2023 14:25
launch-configmanagement-18.1142532.zip
Uploaded: 10-Oct-2022 16:03
Release Note
Updating jettison library for CVE-2022-40150 CVE-2022-40149.launch-configmanagement-17.1132359.zip
Uploaded: 26-Apr-2022 19:06
Release Note
Update for java 17 compatibility.launch-configmanagement-16.1131570.zip
Uploaded: 08-Apr-2022 15:34
Release Note
Update log4j 2.17 and uDeployRestClient libraries.launch-configmanagement-15.1131547.zip
Uploaded: 31-Mar-2022 16:15
Release Note
Fixes APAR PH45332 - Restore file permissions after token substitution.launch-configmanagement-14.1128763.zip
Uploaded: 07-Feb-2022 17:00
Release Note
Remove log4j functionality related to: CVE-2019-17571, CVE-2020-9488. CVE-2021-4104, CVE-2022-23302, CVE-2022-23305, CVE-2022-23307.launch-configmanagement-13.1106796.zip
Uploaded: 26-May-2021 07:06
Release Note
Fixing CVE: CVE-2019-4233launch-uconfigmanagement-13.1102023.zip
Uploaded: 16-Mar-2021 11:06
Summary
Steps
TroubleshootingSummary
This plugin includes steps that install configuration templates and import properties.
Compatibility
This plugin requires HCL Launch version 7.0 or later.
This plugin runs on all operating systems that are supported by the HCL Launch agent, including z/OS with UNIX System Services.
This plugin includes one or more steps, click Steps for step details and properties.
Installation
See Installing plugins in HCL Launch for installing and removing plugins.
History
The following table describes the changes made in each plugin version.
| Version | Description |
|---|---|
| 13 | Minor enhancements |
Steps
The following process steps are available in the HCL Launch Configuration Management plugin.
Batch Import Properties
Import Component Environment Properties from a properties file.
| Name | Type | Description | Required |
|---|---|---|---|
| Delete Extra Properties | Boolean | Remove all properties not present in the properties file. | No |
| Excludes | String | Property files or directories containing property files to exclude. | No |
| Includes | String | Property files or directories containing property files to include. | Yes |
Import Properties
Import Component Environment Properties from a properties file.
| Name | Type | Description | Required |
|---|---|---|---|
| Component Name | String | The component to import properties to. | Yes |
| Delete Extra Properties | Boolean | Remove all properties not present in the properties file. | No |
| Properties File | String | The properties file to import. | Yes |
| Template File | String | The property file to output property resolution values to. | Yes |
Import Resource Properties
Import Resource Properties from a properties file.
| Name | Type | Description | Required |
|---|---|---|---|
| Properties File | String | The properties file to import. This file must be in EBCDIC format for z/OS systems. | Yes |
| Resource Name | String | The path/id of the resource to import properties to. | Yes |
Install Template
Install a configuration template from HCL Launch.
| Name | Type | Description | Required |
|---|---|---|---|
| Environment Property List | String | Yes | |
| File Name | String | The name of the template file to download. | No |
| Repository URL | String | The base URL of the VFS server. | Yes |
| Request Id | String | The request Id to lookup the correct template to download. | Yes |
Troubleshooting
When using the Batch Import Properties step, you must include the component name in the properties file as shown in the following example code:
ComponentName=Component A name=myName state=myState
If you do not include the component name in the properties file, the following error message is displayed:
Error Updating Properties! java.io.IOException: 404 Not Found No component for null