Versions Compared

Old Version 6

changes.mady.by.user Chandresh Patel

Saved on

compared with

New Version Current

changes.mady.by.user Chandresh Patel

Saved on

Key

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

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.

Build is implemented with 2 options as depicted in below.

Image Removed

Tip

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

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 may have sub-folder like common/lib/ant or common/AssetBuildEnvironment.

Project Properties

Property Name

Property Code

Required

Description

WM Package Name

webMethods RunTime Type

FDWM_
PACKAGE
RUNTIME_
NAME
TYPE

Yes

webMethods project Name (source code) i,e IntegrationServer package name

Select type of artifacts from IS, TN or IS & TN options.

WM Parent

Poject

Project Path

FDWM_PARENT_PROJECT_PATH No
  Parent dir of wm source code (where wm package is located/checked out)

Parent directory of webMethods source code, do not include

wm packageName here

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





...