The build operation allows for building webMethods packages(source code), whether they are SCM(Source control management) managed or checked out directly from webMethods Designer tool (development tool) by the developer. It automatically builds the code and copy the completed zip file over to the FlexDeploy internal artifact repository.
...
Build is implemented with 2 options as depicted in below.
| Note |
|---|
Build generation using Zip tool is not suggested by SoftwareAG , because it cannot automatically manage dependencies for the webMethods package you select for deployment. As a best practice, use webMethods Deployer which has efficient features such as simulation, handling clusters, report & logs, dependency check etc. |
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
FDWM_BUILDSERVER_HOME | AssetBuild environment installation home | Used to connect and navigate into webMethods Asset Build Environment-Build Script Path & run the script. |
...
Property Name | Property Code | Required | Description |
|---|---|---|---|
WM Package Name | FDWM_PACKAGE_NAME | Yes | webMethods project Name (source code) i.e. IntegrationServer package name. This property defaults to FD_PROJECT_NAME variable, so if you name FlexDeploy project name same as webMethods Package Name you will save some time in configuration. |
WM Parent Project Path | FDWM_PARENT_PROJECT_PATH | No | Parent directory of webMethods source code (where webMethods package is located/checked out),do not include webMethods Package Name here. This is optional property and can be left empty, in which case plugin will automatically derive location by scanning for manifest.v3 and/or .project files. |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
...