I am happy to announce the release of v2.3.0 of the JahnTech Package Manager for webMethods Integration (JTWPM).

New features:

• jar files:
  • Configure jar files instead of adding them as binaries to the VCS
  • Download from public (e.g. Maven Central) and private repositories
  • Or copy from local file system, if jar is also under development, to save the roundtrip of uploading to e.g. Artifactory
  • Secure via SHA512 checksum (can be turned off for local file system copy)
  • Add jar files to Designer project classpath automatically
• Package releases (ZIP):
  • Remove files and/or directories (e.g. Java source code)
  • Create multiple editions (e.g. Core and Pro) by removing services that shall only be available for certain users
• Create packages that adhere to corporate standards (requires additional IS package)
• Watch log file of package
• Add default Git username and email address to global configuration
• Support rename of catalogs
• Check for lock file when starting Integration Server

In addition numerous small improvements and bug fixes were applied.

Please find below the direct link to get your free copy via the online shop.

Providing JTWPM via the online shop (for free) helps me to fulfill some compliance requirements. So I hope this small extra step is not too much of a hazzle.

There is a number of areas where JTWPM makes your life easier. They basically all revolve around various phases of the SDLC (Software Development Life Cycle).

• Developer on-boarding: Prepare development environment for as many packages as you want with a single command. No more clicking around in Designer dozens of times with a lot of potential to miss something and then spend hourse trying to find what it was.
• Java development. Integration Server is an extremely powerful platform for Java. Designer sometimes makes this more difficult than it needs to be. With a single command you can compile all your Java code (optional: pull other changes from Git) and reload your package.
• CI/CD: Being able to create ZIP archives easily, transfer them to and from a binary repo, and then install them on the next stage in the deployment pipeline makes CI/CD a lot easier.

If you have any questions, please get in touch via email.

Thanks,
Christoph