- Generate the Project Automator XML file based on the configured environment properties & the build version selected for deployment.
- Execute webMethods Project Automator command line script to facilitate automatic project creation in webMethods Deployer.
- Execute webMethods Deployer command line script to deploy assets.
Blog Posts
- https://flexagon.com/2018/03/cicd-with-webmethods-using-flexdeploy/
- https://flexagon.com/2018/05/manage-webmethods-integrationservers-using-flexdeploy/
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
WmDeployer Installation Home |
| Yes | Installation directory of webMethods Server hosting WmDeployer(e.g./opt/SoftwareAG) Use to connect and invoke Deployer script for deploy operation. It will likely contain the IntegrationServer folder. |
WmDeployer Hostname |
| Yes | webMethods Deployer IS Hostname (e.g. dev-sag.company.local) |
WmDeployer IS InstanceName |
| Yes | webMethods Deployer IS InstanceName, available in the default dir ‘IntegrationServer/instances/deployerInstance’ (e.g.deployerInstance) |
WmDeployer Port |
| Yes | The primary port in which IntegrationServer instance hosting WmDeployer is running, e.g. 5555(by default). Used to connect Deployer server through HTTP. |
WmDeployer IS Username |
| Yes | Credentials used to connect the WmDeployer server over HTTP |
WmDeployer IS Password |
| Yes | Credentials used to connect the WmDeployer server over HTTP |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Server Alias or Target Groups |
| Yes | Server Alias or Target Groups as defined in WmDeployer. If configuring more than one value use comma separator. You can override the value for each environment if name is different based on environment. You must configure Server Alias or Target Groups in WmDeployer to indicate the target for deployment of artifacts. |