The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

Deploy to webMethods Integration Server Plugin

deployintegrationserver: Deploy to webMethods Integration Server

  • singleTargetAliases : String (optional)
    Comma-separated alias (without white-spaces) names of the target Integration Servers. These should have already been defined using Deployer.
  • groupTargetAliases : String (optional)
    Comma-separated alias (without white-spaces) names of the target groups of Integration Servers. These should have already been defined using Deployer.
  • deployerHomeDirectory : String (optional)
    File path to bin directory in WmDeployer package of Integration Server.
  • deployerHost : String (optional)
    Host machine domain name.
  • deployerPort : String (optional)
    Port number.
  • deployerCredentialsId : String (optional)
    Administrators credentials to connect with Deployer.
  • repositoryAlias : String (optional)
    Repository alias. This can be any name.
  • repositoryDirectory : String (optional)
    Repository directory path where all the composites exist after build.
  • deployAssets : String (optional)
    Comma-separated name (without white-spaces) of the composites that needs to be deployed to the target. Examples:
    • * for all composites.
    • isconfiguration for config files.
    • TestPackage for specific package composite.
    • TestPackage1,TestPackage2 for multiple package composites.
    • Test* for package composites beginning with Test.
  • projectName : String (optional)
    Project name in Deployer.

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

    


See existing feedback here.