webMethods cloud tenant connections

Learn how a tenant connection enables communication between the on-premises Integration Server and the tenant in webMethods Integration.

In hybrid integration, an on-premises Integration Server uses a tenant connection to share account and application information with webMethods Integration. Specifically, the tenant connection enables communication between the on-premises Integration Server and the tenant in webMethods Integration.

A tenant alias contains the location and login details that are needed for the on-premises Integration Server to establish a connection with webMethods Integration. An on-premises Integration Server can have multiple tenant aliases.

Each account on an on-premises Integration Server is associated with one tenant alias. A single tenant alias can be associated with multiple accounts. An on-premises Integration Server contains a pre-defined tenant alias named default. You can edit the default tenant alias to specify different credentials and a different URL for webMethods Integration. However, the default tenant alias cannot be deleted. When an on-premises Integration Server is registered as a self-managed runtime, webMethods Integration creates a tenant alias that is named EdgeRuntime_EdgeRuntimeName on the on-premises Integration Server.

The tenant alias specifies the credentials or tokens that are used to listen for requests and the URL for webMethods Integration with which the on-premises Integration Server shares applications and accounts.

Note:
  • If you are using hybrid connectivity and when you update the on-premises settings for the first time after the webMethods Integration upgrade, restart the on-premises webMethods Integration Server. After restart, upload the on-premises account to resume hybrid connectivity. This is applicable for all the on-premises Integration Servers connecting to webMethods Integration.
  • If you have allowed the Cloud Universal Messaging (UM) hostname in the firewall, you must also allow the new UM hostname along with the old one.
  • If IBM® has provisioned dedicated UMs for your tenants, and the shared UM queues, if applicable, are imported to the new dedicated UMs, ensure that you update the settings so that hybrid integrations work with the newly provisioned dedicated UMs.
  • If you change the tenant password or token, you must update the tenant password or token in webMethods Integration and in the on-premises Integration Server. If you update the tenant password in webMethods Integration, you must update the tenant information in the on-premises Integration Server that connects to webMethods Integration. You can update the tenant password on the on-premises Integration Server when it is not connected to the tenant on webMethods Integration. Further, the pre-defined default tenant alias cannot be deleted. Also, a tenant alias that is associated with an account cannot be deleted.