IBM 4.6 manual IBM Ldap Server, Cache sizes, Max connections

Page 18

6 IBM LDAP Server

The IBM LDAP Server is a component of the Integrated Security Services base element in z/OS R 1.6 and 1.7, not to be confused with the IBM Tivoli Directory Server released with z/OS 1.8.

6.1APARs

The following APARs are recommended to fix insert and update failures when using IBM Tivoli Identity Manager:

•OA14765 – Addresses LDAP deadlocks

•OA17432 – Moves DIR_MISC table to MISCTS tables pace

6.2Cache sizes

The LDAP Server has internal caches to allow quick access to frequently accessed entries in memory rather than accessing the values from the disk. Better performance can be obtained by increasing the size of the caches.

The LDAP Server allows you to control how many entries the entry cache can store but does not restrict the size of the cache. The size of each entry in the cache is based on the number and the size of attributes that a given LDAP entry has. Typically, many entries are users and their accounts, which have a fairly constant size. When setting the value for the entry cache, calculate the size of the average entry and divide that into the amount of memory used by the LDAP Server process. Users with few attributes can generate entry sizes that are approximately 4 KB where users with more attributes can generate entry sizes around 9k.

Determining the values

dn_cache_size – Size of the DN cache. Default value: 1000. Recommended value: 75000.

dn_to_eid_cache_size – Size of the DN to EID cache. Default value: 1000. Recommended value: 75000.

entry_cache_size – Size of the entry cache. Default value: 1000. Recommended value: 75000.

Note: The recommended values above were determined by assuming 15000 users each with 5 accounts for a total of 75000 objects. You may need to increase this value for larger populations.

Setting the values

1)Edit GLD.CNFOUT(SLAPDCNF)

2)Modify the dnCacheSize value to dn_cache_size.

3)Modify the dnToEidCacheSize value to dn_to_eid_cache_size.

4)Modify the entryCacheSize value to entry_cache_size.

5)Restart LDAPSRV

6.3Max connections

To ensure that IBM Tivoli Identity Manager can connect to the directory server using all available connections, ensure the maximum number of LDAP connections is greater than the size of the LDAP connection pool for Tivoli Identity Manager.

Page 16

IBM Tivoli Identity Manager Performance Tuning Guide

Page 17 Page 19
Image 18
Page 17 Page 19
Contents Issue Date Copyright Notice TrademarksTable of contents About this guide Who should use this guideIntroduction Vital tuningsInitial tunings Resource allocationMemory 2 CPUDisk space Workload management WLM timeout IBM WebSphere Application ServerJava virtual machine JVM size Select Container Services Select ORB Service Message driven bean MDB request timeoutTransaction timeout Change WLM timeout to wlmtimeoutSetting the values Reconciliations IBM Tivoli Identity Manager applicationRecycle bin ThreadsMaximum duration Limiting attributes returned from the adapterLimiting the attributes evaluated Select ReconciliationSet the Max Duration to maxduration IBM Tivoli Identity Manager adapters Microsoft Active DirectoryBuffer pools Idle thread timeoutAPARs Determining the values JCL location DescriptionLocks per user limit Active log duplexingReorg and Runstats Default value Recommended value Additional ZparmsIBM Ldap Server Cache sizesMax connections Indexing Changelog limitsRow locking on Searchts 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