On-Premises Applications
On-Premises applications uploaded from on-premises systems are listed in the On-Premises Applications page, but you will not be able to create Accounts or Operations for on-premises applications. Those can be uploaded only from webMethods Integration Server. Further, when you upload services as part of an application from the on-premises webMethods Integration Server to webMethods Integration Cloud, the comments field of the service is uploaded and displayed in the webMethods Integration Cloud application. This field will be displayed if present and cannot be edited. See the Configuring On-Premise Integration Servers for webMethods Cloud document for more information.
If you select an Account for an on-premises Application and click Test Connection, the screen displays the status of the connection. If you have configured the Account details incorrectly in any stage, the state appears in red color in the Connectivity Status column. If an Account is configured correctly in a particular stage, the state appears in green color and if an Account is not configured in a particular stage, the state appears in white color. For on-premises Applications, you can use the Account to execute services on the on-premises webMethods Integration Server.
Performance, scalability, and availability of on-premises connectivity for hybrid integration scenarios have been enhanced by having dedicated
Software AG Universal Messaging (UM) nodes for each tenant. A tenant can be associated with dedicated UMs based on the license. Contact
Software AG Global Support for assistance in setting up the dedicated hybrid infrastructure. If you are using hybrid connectivity and when you update the on-premises settings for the first time after the upgrade, restart the on-premises
webMethods Integration Server to resume hybrid connectivity. If you have whitelisted the Cloud UM hostname or IP in the firewall, then you have to also whitelist the new UM hostname and IP along with the old ones. Click
here for information on the IP addresses.
Note:
The maximum message size, that is, the hard limit for message sizes that can be transported between on-premises webMethods Integration Server and Integration Cloud is 20 MB (20971520 bytes). This is the hard limit on the size of messages that can be transported over Software AG Universal Messaging between Integration Cloud and on-premises webMethods Integration Server. Overloading the Software AG Universal Messaging cluster with large payloads may adversely impact performance. If you need to transport larger volumes of data, consider an alternative approach that is better suited for file transfers, such as, webMethods ActiveTransfer.