webMethods cloud accounts
An account specifies the connection parameters that are needed to access webMethods Integration.
An account on an on-premises Integration Server is associated with a single tenant alias. However, you can choose which tenant alias the account uses.
When you create an on-premises account on the on-premises Integration Server, you specify the connection parameters that the on-premises Integration Server uses to access webMethods Integration. For each account, you specify a tenant alias that communicates with the on-premises Integration Server.
Each account can be associated with a different tenant alias. You create accounts on the on-premises Integration Server to allow them to serve any requests that originate from webMethods Integration. If an account is disabled on the on-premises Integration Server, any requests that are sent from webMethods Integration times out depending on the time that is specified in the Request timeout field.
The Accounts page lists all the accounts that are available on your on-premises Integration Server. It also displays whether each account is enabled.
Hybrid invocation routing behavior
Hybrid invocation routing is based entirely on account‑level configuration and does not consider individual application deployments, even when a webMethods Integration account is connected to multiple on‑premises Integration Servers.
In case of multiple Integration Server setup where multiple Integration Servers are configured with the same account, the following behavior is expected:
- Requests from webMethods Integration are distributed across all Integration Servers associated with the account.
- Routing is performed using a round‑robin mechanism.
When migrating an application from one Integration Server to another, it is recommended to configure the target Integration Server with a new account. This helps prevent requests from being routed to the source Integration Server after the application has been removed.