Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The deploy operation is used to deploy webMethods applications into target environment.

Deploy is also implemented with 2 options as shown in the below diagram.

The deploy operation performs the following internal activities, If ABE build found;

  • Generate the Project Automator XML file based on the given environment properties and build version selected in FlexDeploy project.
  • Execute webMethods Project Automator command line script to facilitate automatic Deployer project creation.
  • Execute webMethods Deployer command line script to automate the deployment for each project.

In the case of build generated by Zip Utility as part of Build operation;

  • Deploy operation will UnZip the package .zip file into target Integration Server application directory <Integration server home>/packages .The changes will be activated upon the target server restart.
  • Simultaneously, plugin keeps the copy of package zip file into target Integration Server dedicated directory <Integration server home>/packages/replicate/inbound so that webMethods Administrator can login into webMethods Admin UI page and click 'install from Inbound releases' button to activate the package without server restart.

The selected version of Build(webMethods package ZIP file) will be retrieved from internal artifacts repository and will be deployed into target environment. 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, report & logs, dependency check etc.

Environment/Instance Properties

Property Name

Property Code

Required

Description

WMDeployer HOME

FDWM_DEPLOYER_HOME

Yes

Use to connect and invoke Deployer script for deploy operation.

WMDeployer Host

FDWM_DEPLOYER_HOST


Yes

Used to connect and navigate into webMethods Deployer server.

WMDeployer InstanceName


FDWM_DEPLOYER_INSTANCE


Yes

Used to connect Deployer IS instance and navigate into their file system.

Usually the IS Instance Name appear in <IntegrationServer Home>/instances/<INSTANCENAME>

WMDeployer Port

FDWM_DEPLOYER_PORT


Yes

Port on which the server is running on. Used to connect Deployer server through HTTP.

WMDeployer Username

FDWM_DEPLOYER_USER


Yes

Credentials used to connect the server over HTTP

WMDeployer Password

FDWM_DEPLOYER_PASSWORD


Yes

Credentials used to connect the server over HTTP

WM Target Home Dir

FDWM_TARGET_HOME


Yes

Used to deploy the asset into Target env by navigating into this path.

WM Target Server Alias 

FDWM_TARGET_ALIAS


No

WM Deployer use this IsAliase name to create remote HTTP connection with Target server.

WM Target Server Host

FDWM_TARGET_HOST


Yes

Used to connect Target Server over HTTP for deployment.

WM Target Server Port 

FDWM_TARGET_PORT


Yes

Primary Port on which IS is running on. Used to connect Target server over HTTP for deployment

WM Target InstanceName

FDWM_TARGET_INSTANCE


Yes

Used to connect Deployer IS instance and navigate into their file system for deploying the packages.Usually the IS Instance Name appear in <IntegrationServer Home>/instances/<INSTANCENAME> 

WM Target Server Username

FDWM_TARGET_USER


Yes

Credentials used to connect Target server over HTTP

WM Target Server Password

FDWM_TARGET_PASSWORD


 Yes

Credentials used to connect Target server over HTTP

WM Target uses SSL conn?

FDWM_TARGET_USE_SSL

No

Check if  Target Server uses SSL config to establish remote connections from the wm deployer.

Project Properties

Property Name

Property Code

Required

Description





Inputs

Input Name

Input Code

Required

Description





Outputs

Output Name

Required

Description




Artifacts

This operation consumes artifacts from the artifacts repository.

Endpoint Selection

This operation will select all available endpoints associated to the environment/instance.

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

  • No labels