Determining the values

max_connections – The maximum number of connections that the LDAP server will accept. Set this value to 20 more than the enrole.connectionpool.maxpoolsize specified in the

enRole.properties file.

Setting the values

1)Edit GLD.CNFOUT(SLAPDCNF)

2)Modify the maxConnections value to max_connections.

3)Restart LDAPSRV

6.4Changelog limits

The LDAP Server changelog can be limited either by the number of entries or the maximum age of an entry. High LDAP add or modify operation rates initiated by Tivoli Identity Manager can result in lock escalations due to the large volume of entries being added and removed from the changelog. For this reason, it is recommended that the changelog be limited by the maximum age of an entry (changeLogMaxAge) instead of the number of entries (changeLogMaxEntries). Both of these values can

be set in GLD.CNFOUT(SLAPDCNF).

6.5Row locking on SEARCHTS

To improve locking parallelism, particularly on single server installations, it is recommended to change the locking on SEARCHTS table space in GLDDB and GLDDBG databases to row level. This can be done with the following DB2 commands:

ALTER TABLESPACE GLDDB.SEARCHTS LOCKSIZE ROW;

ALTER TABLESPACE GLDDBG.SEARCHTS LOCKSIZE ROW;

These commands can be executed from SPUFI interface, option 6 using SYSADM login.

6.6Indexing

Indexing the attributes that applications search on increases LDAP Server performance. The LDAP Server indexes are automatically translated into IBM DB2 indexes when you update the LDAP Server schema for those attributes.

If you extend the LDAP schema in LDAP Server to include additional attributes, index those attributes that you will search for. Any filter in the Tivoli Identity Manager application (such as with dynamic roles) is translated into a search string for the LDAP Server.

The Tivoli Identity Manager application frequently searches against the organization (o), organizational unit (ou), and owner attributes.

After updating the LDAP schema, run DB2 runstats on the database to update the statistics for the newly created indexes.

In addition, the following DB2 index has shown to increase performance and is required by the LDAP JCL REORG and RUNSTATS scripts:

CREATE UNIQUE INDEX LDAPSRV.DIR_DESCX2

ON LDAPSRV.DIR_DESC( AEID, DEID )

USING STOGROUP SYSDEFLT PRIQTY 22000 SECQTY 10000

CLOSE NO BUFFERPOOL BP1 DEFER NO;

6.7Runstats

See the IBM DB2 - Reorg and Runstats section.

IBM Tivoli Identity Manager Performance Tuning Guide

Page 17

Page 18 Page 20
Page 19
Image 19
IBM 4.6 manual Changelog limits, Row locking on Searchts, Indexing, Runstats
Page 18 Page 20

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