The deploy operation is used to deploy webMethods applications into target environment .Target environment assets to target server or cluster. Targets can be a standalone Integration Server (or) a group of Integration Servers in a cluster. Deployment process is also implemented with 2 options as shown in the below diagram.
This deploy operation performs the following deployment activities, If the build is generated by webMethods ABE component;.
Generate the Project Automator XML file based on the
givenconfigured environment properties & the build version selected
in FlexDeploy projectfor deployment.
Execute webMethods Project Automator command line script to facilitate automatic project creation
.in webMethods Deployer.
Execute webMethods Deployer command line script to
automate the deployment for the specified project towards target environmentdeploy assets.
Deploy operation should be used in deploy workflows.
...
. Make sure to set the endpoint resource type to WM Deployer Server.
| Tip |
|---|
TipAs a best practice, use webMethods Deployer based deployment which has efficient features such as simulation, handling clusters, detailed reports & logs, inter-dependency check etc. |
...
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 |
Used to connect and navigate into webMethods Deployer server.
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. |
Inputs
...
Input Code
...
Required
...
Description
Outputs
Output Name
Required
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. |
Artifacts
This operation consumes artifacts from the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instance.
...
Target which have a resource type of WM Deployer Server.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.webMethods Server endpoint selected using the WM Deployer Server resource type and the given inputs/properties.
Special Considerations
This operation will select all available endpoints associated to the Target which have resource type of {WM Deployer Server}.