JahnTech Package Manager for webMethods Integration

Make your developer experience for webMethods Integration fast and pain-free with a single command to get all your packages installed for development. And this tool can even be used in automation because it so easy to install and configure.

JahnTech Package Manager for webMethods Integration (JTWPM) is a powerful tool to work with Integration Server packages:

Easy and error-free on-boarding for developers
CI/CD: Build, upload, download, and install ZIP archives of packages
Quick switching between different project setups
Catalogs (like app store) to make packages available to developers (via Git) and consumers (as ZIP)
Create packages that adhere to corporate standards (requires additional IS package)
Install JTWPM incl. creation of alias for easy use from everywhere
Development for containers with specific packages
Build different editions of package (e.g. Core and Pro)
Manage external jar files via configuration instead of adding them to the VCS
A single command sets up all the packages
webMethods Designer detects all packages with a single operation
Leverages the power of Git as today’s standard Version Control System (VCS)
Works with Windows, Linux, and macOS

				
					JahnTech Package Manager for webMethods Integration (v2.3.0)
Copyright (c) 2025 by JahnTech GmbH. All rights reserved.
https://jahntech.com/jtwpm

Usage: jtwpm.sh [OPTIONS] pkg {src|status|refresh|build|rebuild|cfg|new|update} NAME
       jtwpm.sh [OPTIONS] pkg {new|edit|show} NAME
       jtwpm.sh [OPTIONS] -c SOURCE_CATALOG_ALIAS pkg copy NAME TARGET_CATALOG_ALIAS
       jtwpm.sh [OPTIONS] pkg create NAME
       jtwpm.sh [OPTIONS] pkg {enable|disable|reload|activate} NAME
       jtwpm.sh [OPTIONS] pkg {install|archive|download|upload} NAME
       jtwpm.sh [OPTIONS] pkg {link|unlink} NAME

       jtwpm.sh [OPTIONS] dwn {show|get|pkgs}
       jtwpm.sh [OPTIONS] dwn {show|get} PKG_NAME
       jtwpm.sh [OPTIONS] dwn {new|edit|path} PKG_NAME CFG_FILE_NAME[.cnf]

       jtwpm.sh [OPTIONS] edt {show}
       jtwpm.sh [OPTIONS] edt {show} PKG_NAME
       jtwpm.sh [OPTIONS] edt {new|edit|path|build} PKG_NAME EDITION_NAME

       jtwpm.sh [OPTIONS] app {src|refresh|build|rebuild|update} NAME
       jtwpm.sh [OPTIONS] app {new|edit|show} NAME
       jtwpm.sh [OPTIONS] -c SOURCE_CATALOG_ALIAS app copy NAME TARGET_CATALOG_ALIAS

       jtwpm.sh [OPTIONS] cat {update|show|edit|all}
       jtwpm.sh [OPTIONS] cat add ALIAS GIT_URL
       jtwpm.sh [OPTIONS] cat copy PKG_CONFIG TARGET_CATALOG_ALIAS
       jtwpm.sh [OPTIONS] cat rename OLD_CATALOG_ALIAS NEW_CATALOG_ALIAS

       jtwpm.sh [OPTIONS] cfg {show|edit}

       jtwpm.sh [OPTIONS] srv [-f] start
       jtwpm.sh [OPTIONS] srv {stop|restart|log|pwd}

       jtwpm.sh [OPTIONS] prg install [TARGET_DIR]

       jtwpm.sh version

       Options:
         -c CATALOG_ALIAS     : Specify custom catalog alias
                                - Default: default
         -d CONFIG_DIR        : Specify custom config directory
                                - Default: /Users/chris/.JahnTech/jtwpm
         -a CONNECTION_ALIAS  : Specify custom connection alias
                                - Default: DEV
         -b BINARY_REPO_CREDS : Credentials file for binary repo
                                - Default: /Users/chris/.JahnTech/jtwpm/binary_repo.netrc
         -e EDITOR_COMMAND    : Specify custom editor
                                - Default: code
         -v                   : Enable verbose output

       Scope:
         pkg : Single package repo (may contain additional packages, e.g. for testing, samples, etc.)
         dwn : Download of external file (e.g. jar)
         edt : Create editions of package (e.g. core vs. pro) by removing selected files/directories
         app : Multiple packages that together make an application
         cat : Catalog
         cfg : Main configuration
         srv : Integration Server
         prg : JTWPM

       For details run the script with only the scope as parameter
       Example: 'jtwpm.sh pkg' will display detailed information on the commands for packages


       Environment variables:
         JTWPM_EDITOR      : Default editor
         JTWPM_CFG_HOME    : Default directory for configuration
         JTWPM_CFG_CATALOG : Default catalog alias

JTWPM is available at no charge, so all webMethods Integration users are able to experience the value it brings to application development.

Please note that JTWPM is not open source and therefore subject to either an individual contract or the standard contract for software of JahnTech.

Screenshots

Click on thumbnail to enlarge (not all pictures show the latest version)

Getting started

Online shop

JahnTech Package Manager for webMethods Integration (JTWPM) is available through our online shop (at a “virtual” price of 0 Euros).

Video

A short video on YouTube demonstrates the use of JTWPM.

Due to the fast-paced development, there are some minor differences with how the latest version works. But no fundamental changes have been made.

Notably, when Integration Server is running, packages will automatically be activated and enabled, if possible.

Setup and first run

For installation instructions got to the “Getting started with JTWPM” page.

Register for updates

To receive updates on JTWPM, please enter your contact information in the form below. Those data will not be used for any other purposes.

After a successful registration, you will receive an email with the subject line “JahnTech newsletter: Confirm your subscription”. You must click the link in there to confirm your registration. This ensures that only you can register here. (It is also required by law in Germany.)

If you feel uncomfortable clicking the link in the email, or the email gets lost in a spam filter, feel free to get in touch directly. This can happen via email, the general contact form of the website, or via LinkedIn.