How “Config.Engine.Startup.imsCxnTimeout” property can be used for TIBCO Integration Manager and TIBCO Hawk agent communication?
Article ID: KB0086555
Updated On:
| Products | Versions |
|---|---|
| TIBCO IntegrationManager | - |
| Not Applicable | - |
Description
Description:
Config.Engine.Startup.imsCxnTimeout” property can be used for TIBCO Integration Manager and TIBCO Hawk agent communication.
Config.Engine.Startup.imsCxnTimeout” property can be used for TIBCO Integration Manager and TIBCO Hawk agent communication.
Issue/Introduction
How “Config.Engine.Startup.imsCxnTimeout” property can be used for TIBCO Integration Manager and TIBCO Hawk agent communication?
Resolution
A “Config.Engine.Startup.imsCxnTimeout” property is used for:
1). Specifying a timeout while starting the IM engine with a large repository. The IM engines will timeout because the default timeout is 4000 milliseconds (4 seconds) and larger repositories need more time. You can increase this value to 600000 or more for larger repos.
2). For specifying a timeout value for sending a heartbeat to TIBCO Hawk. A property plays a role during the discovery phase initially and sends a heartbeat at a regular interval to TIBCO Hawk to indicate that the managed application (i.e Integration Manager) is up and running. This property needs to be defined in the IM property file (Properties.cfg) only.
1). Specifying a timeout while starting the IM engine with a large repository. The IM engines will timeout because the default timeout is 4000 milliseconds (4 seconds) and larger repositories need more time. You can increase this value to 600000 or more for larger repos.
2). For specifying a timeout value for sending a heartbeat to TIBCO Hawk. A property plays a role during the discovery phase initially and sends a heartbeat at a regular interval to TIBCO Hawk to indicate that the managed application (i.e Integration Manager) is up and running. This property needs to be defined in the IM property file (Properties.cfg) only.
Feedback
Yes
No
Powered by
