For specifying JDBC Jars that can be shared by multiple packages, on-premises users may have placed those files under the custom/jars directory in webMethods Integration Server. For cloud deployment, place those files in the code/jars/static directory of some common package to make the required JDBC classes available when the package is deployed to webMethods Integration Cloud.

If keystores and truststores are created in the customer's environment, location of the keystores and truststores may be pointing to some file on a local file system. It is recommended to place these files in the config directory of some common package. This package can be deployed to webMethods Integration Cloud and keystores and truststores can use the packages/CustomPackage/config/myKeystore.jks path to refer to the keystore location.

In case of failure to send messages from Software AG Universal Messaging, webMethods Integration Server stores the messages in Client side Queue (CSQ), which is currently an embedded database. As webMethods Integration Server is in a Docker container, any such locally stored messages may be lost.

Time out errors like 504 Gateway Time-out may appear, if the processing time is greater than 2 minutes.

Software AG Designer allows you to deploy assets without the required dependencies as well as delete assets which are referenced by other assets. It is recommended to manually check and manage the dependencies.