Integration Server 10.15 | Configuring On-Premise Integration Servers for webMethods Cloud | Configuring Accounts for webMethods Cloud | Creating Accounts on an On-Premise Integration Server
 
Creating Accounts on an On-Premise Integration Server
An account specifies the connection parameters needed to access webMethods Cloud. Each account on an on-premise Integration Server is associated with a single tenant, however, you can choose which tenant the account uses. Multiple accounts can use the same tenant.
Note:
Accounts existing on the on-premise Integration Server prior to the application of a fix that includes PIE-68485 or migration to a release that includes PIE-68485 can use the default tenant only. This cannot be changed. Only accounts created after PIE-68485 is applied (or the Integration Server is migrated to a release that includes PIE-68485) can use a tenant besides the default.
*To create an account
1. Open Integration Server Administrator.
2. Go to webMethods Cloud > Accounts.
3. Click Create On-Premise Account.
4. Under General Settings, complete the fields as follows:
Field
Description
Enable
Enables or disables the webMethods Cloud account. Valid values:
*Yes - Enables the webMethods Cloud account.
*No - Disables the webMethods Cloud account.
Alias Name
A unique name for the account.
Description
Description of the account.
Tenant Alias
The tenant used with the account. The tenant alias specifies the credentials used to connect to webMethods Cloud.
Stage
The webMethods Cloud environment from which the on-premise Integration Server receives requests. The list is populated by the stages or environments defined on webMethods Cloud.
Note:
The typical life cycle of an integration development involves creating integrations, testing them, and making them production worthy. Each of these activities can be termed as different stages of an integration life cycle development.
5. Under Account Settings, complete the fields as follows:
Field
Description
Maximum Reconnection Attempts
Specify the maximum number of reconnection attempts that Integration Server should make if the connection to webMethods Cloud fails. When the connection between webMethods Cloud and on-premise Integration Server is down, Integration Server attempts to reconnect to webMethods Cloud with a random interval between 100 milliseconds to 10 seconds for the first two minutes and then waits for a period of 30 to 60 seconds before attempting to retry the connection. The on-premise Integration Server continues in this manner until connectivity to webMethods Cloud is restored.
Request Timeout
Maximum amount of time (in milliseconds) that webMethods Cloud waits for the on-premise Integration Server to process a request. If the on-premise Integration Server is not listening for a request or if it takes longer to process the request than the specified time, webMethods Cloud issues an error and stops listening for a response. The default is 60000 milliseconds (1 minute).
When the request timeout expires, webMethods Cloud shows this exception "[ISS.0021.8042E] Error occurred while executing service <on-prem-servicename> with request ID <requestID>. The on-premise Integration Server did not respond within the configured request timeout of <requestTimeoutValue> milliseconds. Check on-premise logs."
If the invoked on-premise service takes more time to execute than the Request Timeout value, Integration Server writes the following error message to the server log: [ISS.0021.8041E] Error occurred while executing service <serviceName> with request ID <requestID>. Service execution took <x> milliseconds, which is more than the configured request timeout of <y> milliseconds.
When responding to a request from webMethods Cloud, the on-premise Integration Server adds a time-to-live (TTL) property to the response. The on-premise Integration Server uses the Request Timeout value set for the webMethods Cloud account as the TTL value for the response. If the on-premise Integration Server sends the response after the timeout value for the request elapses on webMethods Cloud, the response remains on webMethods Cloud only until the response expires (that is, only until the TTL in the response elapses).
Time to Live
If you are batching the data from the on-premise Integration Server, the length of time in seconds that the execution results remain in the cache of the on-premise Integration Server. The value must be greater than 0. The default is 60 seconds.
Enable Compression
Specify whether on-premise Integration Server and webMethods Cloud must compress the request and response payloads during hybrid messaging.
Note: 
Selecting the Enable Compression checkbox enables compression only if both the on-premise Integration Server and webMethods Cloud installations are configured to use the compression functionality.
The compression process starts at webMethods Cloud. If webMethods Cloud compresses the request payload, on-premise Integration Server decompresses, processes, and compresses the payload in the response to webMethods Cloud. However, if webMethods Clouddoes not perform compression, then on-premise Integration Server returns the payload in its original, uncompressed form.
Allowed On-Premise Hosts
(Optional.) The on-premise Integration Server might use multiple addresses, depending on which network or proxy it uses to access webMethods Cloud. Specify a comma-separated list of IP addresses that can receive requests from webMethods Cloud. Only those IP addresses specified can receive requests.
If no value is specified, webMethods Cloud derives the IP address of the on-premise Integration Server that uploads the account to webMethods Cloud and allows only that IP address to receive requests from webMethods Cloud.
Run As User
Specify the user name you want the on-premise Integration Server to use when running the service. Click to search for a user and select the user. You can select users from the local or central directory.
The on-premise Integration Server runs the service as if the user you specify is the authenticated user who invoked the service. If the service is governed by an ACL, ensure that you specify a user who is allowed to invoke the service.
6. If you want to test the account, click Test Account Settings.
Integration Server Administrator displays a status line that indicates whether the account is successful or not. The status line is displayed at the top of the screen.
7. Click Save Changes.