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: However, after talking to an SAG consultant today, I finally came up with a meaningful naming convention: Deployment Set: … Read moreConventions for naming deployment artifacts in WmDeployer for webMethods Integration Server

Unit-testing Flow Services in webMethods’ Integration Server with JUnit

Today, I built a small test bed for unit-testing Flow Services in webMethods’ Integration Server. If you develop Java Services for IS and follow the best practice of “no business logic in the service layer”, you can unit-test your logic in isolation in a plain old Java environment and deploy the library to IS, which … Read moreUnit-testing Flow Services in webMethods’ Integration Server with JUnit