Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The build operation allows for building webMethods packages , whether they are VCS controlled or not. It automatically build the code and copy the completed zip file over to the from source code. Generated artifacts are stored in FlexDeploy internal artifact repository. It

This operation should be used in build workflows . We need to use SCM-ExportProjectSources plugin flow to checkout the webMethods code from Subversionand 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

It is best practice to match FlexDeploy project name to webMethods package name.

Environment/Instance Properties

Property Name

Property Code

Required

Description

webMethods Asset Build Environment exists?

FDWM_ABE_EXISTS

Yes

Used to invoke the corresponding Build flow based on the existence of ABE build script check.

webMethods HOME Dir for BUILD Server

FDWM_BUILDSERVER_HOME

ONLY IF above property is selected TRUEAsset 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 may have sub-folder like common/lib/ant or common/AssetBuildEnvironment.

Project Properties

Input Name

Input Code

Required

Description

WebMethods

Property Name

Property Code

Required

Description

Inputs

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

This is the folder that typically is named for your application and contains your [src] folder. Relative paths are sourced from the FD_TEMP_DIR.
 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





Outputs

Output Name

Required

Description




...