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

New features:

• Enhancements to adding jar files via configuration files instead of putting binaries into the VCS 
  • Configuration files can now be added directly via URL, which is quite a bit faster than manually editing the config file.
  • Use a Maven POM file to define dependencies. They will be resolved (incl. transient dependencies) and configuration file be created.
• Compilation for specific Java version, especially useful for older versions of Integration Server
• Support for multiple webMethods installations from one profile
• Replaced call to jcode script with built-in logic for tighter control (still using setenv script for compatibility)

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.
• Switching between projects: People who are working on multiple projects in parallel (e.g. in support) can easily change between workspaces and/or package sets.

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

Thanks,
Christoph