This plugin is used to build and deploy webMethods IntegrationServer(ESB) assets into their target environments.
Plugin implements Continuous integration and deployment process for Software AG webMethods ESB assets (IntegrationServer packages) using FlexDeploy tool along with the use of webMethods ABE, Deployer components.
This Document contains instructions for automating the build and deployment of webMethods ESB (named IntegrationServer) assets (named packages)using FlexDeploy.
Supported Versions
Latest version of SoftwareAG-webMethods10 product suite.
Older versions of webMethods standalone server should work as well, but have not been tested.
Plugin supports all the SCM system Integrations supported by FlexDeploy
, but GitHub, SVN etc are tested.. (Git, Subversion, TFVC, CVS, Perforce etc.)
Key Features
Easily configurable. No configurations required
on target webMethods environment side.
webMethods Deployer’s repository-based deployment scenario has been chosen as recommended by SoftwareAG and implemented.
Automate the process of Project Automator Files generation and project creation in webMethods Deployer for each deployment. This will reduce manual efforts and avoid human errors during deployment.
Deploy webMethods Applications to Standalone target Servers without manual efforts.
Continuous Integration from Source Control Systems to Build and Deployment phases.
Plugin handles build for both SCM controlled and developer checked out source code from webMethods Designer(eclipse based development tool).
Plugin supports build and deployment using webMethods ABE & Deployer tools and traditional Zip & Unzip tools as well.
Only webMethods ESB Assets (IntegrationServer packages) are considered in scope for build and deployments.
Limitations
Deploying Applications to webMethods Cluster is not implemented in the current version but will be planned for Next Release.
Plugin operations to start/stop webMethods standalone Server instances and cluster
are not yet available.
To support webMethods Deployer's Runtime based deployment scenario.
Plugin Operations
Child pages (Children Display) |
---|