Breaking Changes

Release 12.1

• Summary: Namespace change from softwareag* to webmethods*.

  Background: The "softwareag" namespace has been replaced with the "webmethods" namespace. Configurations, parameters, and file names that used the "softwareag" namespace have been updated to use the "webmethods" namespace.

  If you are installing IBM webMethods 12.1 products for the first time, you are not affected and use the new webMethods namespace directly. If you are upgrading from webMethods 10.x to webMethods 12.1, version 12.1 of Command Central and Platform Manager supports only the webMethods namespace.

  Action: Update composite templates that use the "softwareag" namespace in configurations and scripts to use the "webmethods" namespace.

• Summary: Jakarta EE adoption.

  Background: This release moves from javax.* to jakarta.* namespace as part of Jakarta EE adoption. The server and built-in packages have been updated. However, only user-written Java code that imports javax.* packages are affected by this change and will fail to compile or run unless updated to use jakarta.* imports.

  Action: Before upgrading, identify all custom Java services that use these javax.* packages, update the imports to jakarta.*, and recompile the code with Java 21. As per the Jakarta Specification, only Java EE packages need to be migrated from javax.* to jakarta.*. Java SE packages should remain unchanged.

• Summary: You can no longer execute composite template remote actions that use shell scripts on Windows environments.

  Background: Remote actions run on target hosts using the SSH connection configured for those hosts. Command Central no longer supports configuring OpenSSH through Cygwin on Windows. Instead, Command Central now supports the native Windows OpenSSH server. Older versions of Command Central relied on the Linux shell of Cygwin-based OpenSHH configurations to run shell scripts in remote actions on Windows environments. Because this Linux shell is no longer available, remote actions that execute shell scripts will fail when applied to Windows environments.

  Action: Rewrite any shell scripts or POSIX‑style commands for remote actions on Windows as .bat scripts.

• Summary: You can create mirror repositories and image repositories only for version 12.1.

  Background: In versions 11.1 or earlier of Command Central, you can create mirror repositories and image repositories for any product version. In version 12.1, Command Central restricts mirror and image repository creation to version 12.1. Command Central validates the source repositories and product repositories you provide. If any source or product repository uses a version earlier than 12.1, Command Central rejects the operation. If you do not provide any product repositories when creating a fix mirror repository, Command Central automatically sets the fix mirror repository version to 12.1. When you upgrade Command Central, existing mirror repositories, image repositories, and connections to master repositories are not migrated to the new installation.

  Action: When you create mirror repositories or image repositories, provide source repositories with version 12.1. After you upgrade Command Central, recreate connections to IBM webMethods repositories. Before you install products, you must accept the IBM product license agreement. You can accept the license agreement by running the Command Central bootstrapper with the --accept-license argument, when connecting to an IBM webMethods master repository in the Command Central web user interface, or by running the appropriate CLI commands with the --accept-license argument. If you use CLI scripts to install or upgrade products, or to connect to IBM webMethods product repositories, update the scripts to include the --accept-license argument.