Overview
When you create an account on the on-premises Integration Server, you specify the connection parameters that the on-premises Integration Server uses to access IBM webMethods Cloud. For each account, you specify the 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
IBM webMethods Cloud. If an account is disabled on the on-premises
Integration Server, any requests sent from
IBM webMethods Cloud will time out depending on the amount of time specified in the
Request Timeout field. For more information about the
Request Timeout field, see
Creating Accounts on an On-Premises Integration Server
.
You can upload accounts in two ways: as part of an application or individually, separate from applications. To upload an account as part of an application, you must first create the account and then associate it to the application when you upload it to
IBM webMethods Cloud as described in
Uploading Applications.
You can upload accounts separately from applications if you need to override the settings of a previously uploaded account. You might do this if you associate an account while uploading an application to IBM webMethods Cloud and later change the account details. This way, you can change the account details without having to upload the entire application.
When an Integration Server is registered as a webMethods Edge Runtime, Integration creates two accounts on the Integration Server:
EdgeRuntimeAccount_
EdgeRuntimeName_admin account is used by
Integration for retrieving and displaying data for Integration Mesh in
Integration.
EdgeRuntimeAccount_
EdgeRuntimeName_services is used for listening for service requests from
Integration.