Field | Description |
Enable | Enables or disables the IBM webMethods Cloud account. Valid values: Yes - Enables the IBM webMethods Cloud account. No - Disables the IBM 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 IBM webMethods Cloud. |
Stage | The IBM webMethods Cloud environment from which the on-premises Integration Server receives requests. The list is populated by the stages or environments defined on IBM 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. |
Field | Description |
Maximum Reconnection Attempts | Specify the maximum number of reconnection attempts that Integration Server should make if the connection to IBM webMethods Cloud fails. When the connection between IBM webMethods Cloud and on-premises Integration Server is down, Integration Server reconnects 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-premises Integration Server continues in this manner until connectivity to IBM webMethods Cloud is restored. |
Request Timeout | Maximum amount of time (in milliseconds) that IBM webMethods Cloud waits for the on-premises Integration Server to process a request. If the on-premises Integration Server is not listening for a request or if it takes longer to process the request than the specified time, IBM webMethods Cloud issues an error and stops listening for a response. The default is 60000 milliseconds (1 minute). When the request timeout expires, IBM webMethods Cloud shows this exception "[ISS.0021.8042E] Error occurred while executing service <on-prem-servicename> with request ID <requestID>. The on-premises Integration Server did not respond within the configured request timeout of <requestTimeoutValue> milliseconds. Check on-premise logs." If the invoked on-premises 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 IBM webMethods Cloud, the on-premises Integration Server adds a time-to-live (TTL) property to the response. The on-premises Integration Server uses the Request Timeout value set for the IBM webMethods Cloud account as the TTL value for the response. If the on-premises Integration Server sends the response after the timeout value for the request elapses on IBM webMethods Cloud, the response remains on IBM 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-premises Integration Server, the length of time in seconds that the execution results remain in the cache of the on-premises Integration Server. The value must be greater than 0. The default is 60 seconds. |
Enable Compression | Specify whether on-premises Integration Server and IBM 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-premises Integration Server and IBM webMethods Cloud installations are configured to use the compression functionality. The compression process starts at IBM webMethods Cloud. If IBM webMethods Cloudcompresses the request payload, on-premises Integration Server decompresses, processes, and compresses the payload in the response to IBM webMethods Cloud. However, if IBM webMethods Cloud does not perform compression, then on-premises Integration Server returns the payload in its original, uncompressed form. |
Allowed On-Premise Hosts | (Optional.) The on-premises Integration Server might use multiple addresses, depending on which network or proxy it uses to access IBM webMethods Cloud. Specify a comma-separated list of IP addresses that can receive requests from IBM webMethods Cloud. Only those IP addresses specified can receive requests. If no value is specified, IBM webMethods Cloud derives the IP address of the on-premises Integration Server that uploads the account to IBM webMethods Cloud and allows only that IP address to receive requests from IBM webMethods Cloud. |
Run As User | Specify the user name you want the on-premises 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-premises 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. |