IBM Managing WebSphere Transaction Timeout Settings in Tivoli Identity Manager
Page 8

by other processes. When the WLM timeout is reached the thread is killed resulting in the process being killed.

IBM Tivoli Identity Manager can initiate long-running IIOP requests during processes like reconciliations. To allow long-running reconciliations to complete we recommend disabling the WLM timeout.

Determining the values

wlm_timeout – The time in seconds that IIOP requests wait on the queue before being terminated. Default value: 300. Recommended value: 0 (disabled).

Setting the values

1)Open the Administration Console.

2)Expand the Servers list in the navigation pane.

3)Select Application Servers in the navigation pane.

4)Select the server to manage.

5)Select Container Services.

6)Select ORB Service.

7)Select z/OS additional settings.

8)Change WLM timeout to wlm_timeout.

9)Repeat this procedure for each IBM Tivoli Identity Manager server. Stop and restart each Application Server for these changes to take effect.

2.3Message driven bean (MDB) request timeout

The message driven bean (MDB) request timeout controls how much time MDBs should be limited to. Policy evaluations can often run over the default timeout and should be increased.

Determining the values

mdb_request_timeout – The time in seconds allotted to MDB requests. Default value: 1200.

Recommended value: 7200.

Setting the values

1)Open the Administration Console.

2)Expand the Servers list in the navigation pane.

3)Select Application Servers in the navigation pane.

4)Select the server to manage.

5)Select Custom Properties.

6)Change the value of control_region_mdb_request_timeout to mdb_timeout.

7)Repeat this procedure for each IBM Tivoli Identity Manager server.

Stop and restart each Application Server for these changes to take effect.

2.4Transaction timeout

Complex or long-running transactions within IBM Tivoli Identity Manager can often run past the default transaction timeout. It is recommend that the default transaction timeout be increased.

Determining the values

transaction_timeout – The time in seconds before a transaction timeouts. Default value: 300.

Recommended value: 12000.

Page 6

IBM Tivoli Identity Manager Performance Tuning Guide

Page 7 Page 9
Image 8
Page 7 Page 9
Contents Issue Date Copyright Notice TrademarksTable of contents About this guide Who should use this guideVital tunings Initial tuningsIntroduction Resource allocationDisk space Memory2 CPU Java virtual machine JVM size Workload management WLM timeoutIBM WebSphere Application Server Message driven bean MDB request timeout Transaction timeoutSelect Container Services Select ORB Service Change WLM timeout to wlmtimeoutSetting the values IBM Tivoli Identity Manager application Recycle binReconciliations ThreadsLimiting attributes returned from the adapter Limiting the attributes evaluatedMaximum duration Select ReconciliationSet the Max Duration to maxduration IBM Tivoli Identity Manager adapters Microsoft Active DirectoryIdle thread timeout APARsBuffer pools Determining the values JCL location DescriptionLocks per user limit Active log duplexingReorg and Runstats Default value Recommended value Additional ZparmsMax connections IBM Ldap ServerCache sizes Changelog limits Row locking on SearchtsIndexing RunstatsBest practices Regular maintenance Other resources

4.6 specifications

IBM 4.6, known for its robust and versatile capabilities, represents a significant evolution in the realm of enterprise software solutions. This version is primarily associated with IBM's middleware offerings, notably IBM WebSphere Application Server. It is engineered to support the development, deployment, and management of web applications with a focus on scalability, reliability, and security.

One of the standout features of IBM 4.6 is its enhanced performance optimizations. The platform employs advanced caching strategies and efficient resource management to improve application response times and throughput. This means that businesses can handle heavier loads with fewer resources, making it an economical choice for enterprises of all sizes.

Another notable characteristic is its support for a wide range of programming models and standards, including Java EE. This allows developers to build applications using familiar tools and frameworks, accelerating development timelines and improving productivity. Additionally, IBM 4.6 offers robust integration capabilities with existing enterprise systems through its support for web services and messaging protocols.

IBM 4.6 also emphasizes security. It includes features such as role-based access control, data encryption, and comprehensive auditing capabilities. These measures help organizations safeguard sensitive information and comply with various regulatory requirements.

The compatibility with multiple platforms, including cloud environments, is another significant advantage. IBM 4.6 simplifies deployment across diverse infrastructures, enabling businesses to operate in hybrid environments seamlessly. This flexibility is particularly beneficial as organizations increasingly adopt cloud migration strategies.

Furthermore, IBM 4.6 is equipped with a range of monitoring and management tools. These tools provide insights into application performance and health, allowing IT teams to proactively identify and address potential issues before they impact users. This capability is critical in maintaining high availability and reliability of services.

In summary, IBM 4.6 stands out as a comprehensive solution for enterprise application development and management. Its key features, such as enhanced performance, support for industry standards, strong security measures, platform compatibility, and monitoring tools, make it a compelling choice for organizations seeking to modernize their IT infrastructure. Implementing IBM 4.6 can empower businesses to innovate faster while ensuring their applications remain secure and efficient in a rapidly evolving digital landscape.
Top Page Image Contents