The build operation allows for building webMethods packages (from 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 . Generated artifacts are stored in FlexDeploy internal artifact repository.
This operation should be used in build workflows and must be preceded by operation to extract code from SCM or any File System folder. This means that this operation has a dependency on the existing SCM plugins such as cloneProjectSources, extractProjectSources etc to checkout the source code from SCM tools. Source code is checked out in to temp folder of FlexDeploy workflow execution.
| Tip |
|---|
Build is implemented with 2 options as depicted in below.
It is best practice to match FlexDeploy project name to webMethods package name. |
Blog Posts
- https://flexagon.com/2018/03/cicd-with-webmethods-using-flexdeploy/
- https://flexagon.com/2018/05/manage-webmethods-integrationservers-using-flexdeploy/
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
| BUILD Server | FDWM_BUILDSERVER_HOME | AssetBuild Asset build environment installation home | Used to connect and navigate into webMethods Asset Build Environment-Build Script Path & run the script. Installation Home Dir of webMethods Build Server installed with Asset Build Environment(e.g. /opt/SoftwareAG) This folder will have sub-folders including common/lib/ant and common/AssetBuildEnvironment. It may also contain the IntegrationServer folder. |
Project Properties
Property Name | Property Code | Required | Description |
|---|
webMethods RunTime Type | FDWM_ |
| RUNTIME_ |
| TYPE | Yes |
Select type of artifacts from IS, TN or IS & TN options. |
WM Parent |
Project Path | FDWM_PARENT_PROJECT_PATH | No |
Parent directory of webMethods source code, do not include |
webMethods Package Name here. Relative path is assumed to be in workflow execution temp folder. You can provide more than one path using comma(,) separator. This is optional property and can be left empty, in which case plugin will derive location automatically. For Git and CVS parent folder of each extract is considered and for other SCM temp directory is assumed. |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
...