Infor EPM session time-outs
Different types of session are subject to different time-outs. Time-outs also vary
according to the product’s environment.
This table shows the different session time-outs in applications and the different behaviors of time-outs in on-premises and cloud environments:
| Type of session time-out | Description | On-premises | Cloud |
|---|---|---|---|
| Session time-out for web access | The period of inactivity after which a session ends. | You can set this time-out on the Global Settings tab in Service Expert. | The time-out is determined by the Infor Ming.le time-out, which is set in Infor Ming.le admin and which is always shorter than the default Infor EPM time-out. |
| Elastic Load Balancing (ELB) session time-out | The session time-out for APIs of Infor EPM towards other Infor components in the cloud. This time-out affects ION APIs, Provisioning APIs, OLAP APIs. | Not applicable | Not configurable. The session is controlled by the cloud infrastructure. Configured at 30 min. |
| Operation time-out | Time-out for operations that take place between different services of the Infor EPM farm. It affects long running operations such as Application Engine processes and Workforce Budgeting calculations. | Not configurable. The limit is 2 hours. |
Not configurable. The limit is 2 hours. |
| Transaction time-out of the Repository Service | Time-out for operations against the repository. There is service to service time-out (transaction time-out) and client to service time-out (transaction API time-out). | Transaction time-out (service to service): 10 min. You can configure it on the
Services dashboard. This time-out does not affect full clients. Transaction API time-out: This time-out affects clients of a repository. You can configure it on the Services dashboard. |
Transaction time-out (service to service): Not configurable. The limit is 10
min. Transaction API time-out: Not configurable. The limit is 2 min. |
| Session time-out for data connections | Data connections have keep-alive behavior which is defined by service settings. | Relational connections in an on-premises environment can be configured per connection. | Not applicable |