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, when the build is generated by webMethods ABE component (refer the left side steps of the below picture);.
- Generate the Project Automator XML file based on the given configured 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.
| Tip | ||
|---|---|---|
| ||
As a best practice, use webMethods Deployer based deployment which has efficient features such as simulation, handling clusters, detailed reports & logs, inter-dependency check etc. |
Environment/Instance Properties
Property Name | Property Code | Required | Description | |
|---|---|---|---|---|
WMDeployer WmDeployer Installation Home | FDWM_DEPLOYER_HOME | Yes | Installation directory of webMethods Server hosting WmDeployer(e.g./opt/SoftwareAG) Use to connect and invoke Deployer script for deploy operation. | |
WMDeployer WmDeployer Hostname | FDWM_DEPLOYER_HOST | Yes | Used to connect and navigate into webMethods Deployer server. | WMDeployer webMethods Deployer IS Hostname(e.g. dev-sag.company.local) |
WmDeployer IS InstanceName | FDWM_DEPLOYER_INSTANCE | Yes | InstanceName of webMethods Deployer IS hosting WmDeployerInstanceName, displayed available in the default dir 'IntegrationServer/instances/deployerserverdeployerInstance' (e.g.deployerserverdeployerInstance) | |
WMDeployer WmDeployer Port | FDWM_DEPLOYER_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 WmDeployer IS Username | FDWM_DEPLOYER_USER | Yes | Credentials used to connect the WmDeployer server over HTTP | |
WMDeployer WmDeployer IS Password | FDWM_DEPLOYER_PASSWORD | Yes | Credentials used to connect the WmDeployer server over HTTP |
Project Properties
Property Name | Property Code | Required | Description | |||
|---|---|---|---|---|---|---|
FDWM_ TARGET_ALIAS_OR_GROUPS | Yes | WM Parent Project Path | FDWM_PARENT_PROJECT_PATH | No | Parent directory of webMethods source code (where webMethods package is located), do not include webMethods Package Name hereIntegrationServer Server Alias or Target Groups as defined in WmDeployer. If configuring more than one value use comma separator. | |
| WM Package Name | FDWM_PACKAGE_NAME | Yes | webMethods Package Name (source code) i.e. IntegrationServer package name. | |||
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. |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
...
This operation consumes artifacts from the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the environment instance which have a resource type of WM Deployer Server.
Endpoint Execution
This operation will execute on the 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 environment instance which have resource type of {WM Deployer Server}.