Conventions for naming deployment artifacts in WmDeployer for webMethods Integration Server

For quite some time now I have used the default names for all the different artifacts (set, build, map, candidate) in WmDeployer, because I simply did not know how to name them in a meaningful way:

Default Deployment Properties in WmDeployer for webMethods Integration Server

However, after talking to an SAG consultant today, I finally came up with a meaningful naming convention:

  • Deployment Set: Simply name the Deployment Set according to the type of deployment it contains, e.g. IS or MWS.
    Create and name a Deployment Set for Integration Server in WmDeployer
  • Build: A meaningful name would contain a version number for the build. Just see the build as a Java artifact (JAR), for which multiple versions can exist. A new version number is only needed, if you plan to revert to an older version later. If you only have minor changes to deploy, you can simply re-build the existing version.
    Create and name a Deployment Set for Integration Server in WmDeployer
  • Deployment Map: You can define mappings for different target servers or groups. Therefore, the target’s name should be contained in the map’s name.
    Create and name a Deployment Set for Integration Server in WmDeployer
  • Deployment Candidate: A Deployment Candiate is simply the combination of a Build und a Deployment Map. This should be reflected in the candidate’s name so you can quickly deploy a specific build to a specific target.
    Create and name a Deployment Set for Integration Server in WmDeployer