Introduction to IBM Tivoli Directory Server 6.0 - Server Administration and Maintenance An overview of IBM Tivoli Directory Server Administration and Maintenance Excerpt taken from presentation given on April 10, 2007
Introduction to IBM Tivoli Directory Server 6.0 - Server Administration and Maintenance An overview of IBM Tivoli Directory Server Administration and Maintenance Excerpt taken from presentation given on April 10, 2007
Section 3
Section 3 Server Administration and Maintenance Tasks Keep your server level up to date with the latest fixpack level Resource Considerations Performance Maintenance Perform Periodic Backups
Downloading the latest available fixpack
Downloading the latest available fixpack Visit the ITDS support page to see the latest available fixpacks. (http://www-306.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html) Select the fixpack link and download the latest fixpack and fixpack readme. The fixpack readme will provide an explanation of each fix included and the installation instructions.
Installing the latest fixpack
Installing the latest fixpack There are two main tasks which need to be completed as part of a fixpack upgrade. The installation of the fixpack The deployment of the latest war file for the Web Administration tool.
A pot file is a Design Template file, which provides you the “look” of the presentation You apply a pot file by opening the Task Pane with View > Task Pane and select Slide Design – Design Templates. Click on the word Browse… at bottom of Task Pane and navigate to where you stored BlueOnyx Deluxe.pot (black background) or BluePearl Deluxe.pot (white background) and click on Apply. You can switch between black and white background by navigating to that pot file and click on Apply. Another easier way to switch background is by changing color scheme. Opening the Task Pane, select Slide Design – Color Schemes and click on one of the two schemes. All your existing content (including Business Unit or Product Names) will be switched without any modification to color or wording. Start with Blank Presentation, then switch to the desired Design Template Start a new presentation as Blank Presentation You can switch to Blue Onyx Deluxe.pot by opening the Task Pane with View > Task Pane and select Slide Design – Design Templates. Click on the word Browse… at bottom of Task Pane and navigate to where you stored BlueOnyx Deluxe.pot (black background) and click on Apply. Your existing content will take on Blue Onyx’s black background, and previous black text will turn to white. You should add your Business Unit or Product Name by modifying it on the Slide Master You switch to the Slide Master view by View > Master > Slide Master. Click on the Title Page thumbnail icon on the left, and click on the Business Unit or Product Name field to modify it. Click on the Bullet List Page thumbnail icon on the left, and click on the Business Unit or Product Name field to modify it. Click on Close Master View button on the floating Master View Toolbar You can turn on the optional date and footer fields by View > Header and Footer Suggested footer on all pages including Title Page: Presentation Title | Confidential Date and time field can be fixed, or Update automatically. It appears to the right of the footer. Slide number field can be turned on as well. It appears to the left of the footer.
Installing the latest fixpack
Installing the latest fixpack Download and extract the latest fixpack from the ITDS support site.
Installing the latest fixpack
Installing the latest fixpack
Run the “idsinstall” script with the –u flag to update all of the installed ITDS packages. When the “idsinstall” script completes you will see the “All packages were installed successfully!” message.
Installing the latest fixpack
Installing the latest fixpack The second task in upgrading to the latest fixpack is to deploy the latest war file for the Web Admin. cd /opt/IBM/ldap/V6.0/idstools run the deploy script using the following syntax: # ./deploy_IDSWebApp.sh –w -p For Example: # ./ deploy_IDSWebApp.sh –w “/opt/IBM/ldap/V6.0/idstools/IDSWebApp.war” –p “/opt/IBM/ldap/V6.0/appsrv”
Installing the latest fixpack
Installing the latest fixpack The “deploy_IDSWebApp.sh” will generate several messages. When the command completes, you will see the following output indicating that the Web Admin has been updated.
Fixpack Installation Success!
Resource Considerations
Resource Considerations There are several resource limits that might need to be adjusted for IBM Tivoli Directory Server. By default on AIX the ulimits are set way too low. If these limits are not corrected you run the risk of a variety of limitation issues. Limit Effect Data Limit Silent server abend, poor performance File Descriptor limit Clients may receive a DSA is unwilling to perform Memory limit Silent server abend, poor performance
Resource Considerations
Resource Considerations To verify your ulimit settings issue the following command: # ulimit –a This will return output similar to the following:
Resource Considerations
Resource Considerations The are two options for updating these values: Set the ulimits from command line each time you start the server OR On AIX, permanently update the values in the /etc/security/limits file **Note: You can always check to see what values were picked up by the ITDS server by reviewing the messages in the ibmslapd.log file, which is located in the following directory: //idsslapd-/logs
Resource Considerations
Resource Considerations Option 1: Note that these values are set for this session only. If I log out and log back in, I will need to rerun these commands.
Resource Considerations
Resource Considerations Option 2: cd /etc/security vi limits Define the limits for the “root” user and any other user you might use to start the server. **Note: you will need to restart your system for these changes to take effect.
Resource Considerations
Resource Considerations For additional information regarding ulimits: http://www-1.ibm.com/support/docview.wss?uid=swg21206894 http://www-1.ibm.com/support/docview.wss?uid=swg21206894 http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDS.doc/tuning07.htm
Performance Maintenance
Performance Maintenance For performance tuning recommendations please refer to the: ITDS 6.0 Performance Tuning Guide The most critical task that can be taken by the ITDS admin is to take steps to make db2 as efficient as possible. This can be achieved by following the recommendations specified in the Optimization and Organization section within the DB2 tuning and commands chapter of the Performance Tuning guide.
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDS.doc/tuning06.htm
Performance Maintenance
Performance Maintenance Optimization and organization (reorgchk and reorg) DB2 uses a sophisticated set of algorithms to optimize the access to data stored in a database. These algorithms depend upon many factors, including the organization of the data in the database, and the distribution of that data in each table. Distribution of data is represented by a set of statistics maintained by the database manager. In addition, IBM Tivoli Directory Server creates a number of indexes for tables in the database. These indexes are used to minimize the data accessed in order to locate a particular row in a table. In a read-only environment, the distribution of the data changes very little. However, with updates and additions to the database, it is not uncommon for the distribution of the data to change significantly. Similarly, it is quite possible for data in tables to become ordered in an inefficient manner. To remedy these situations, DB2 provides tools to help optimize the access to data by updating the statistics and to reorganize the data within the tables of the database.
Performance Maintenance
Performance Maintenance Optimization Optimizing the database updates statistics related to the data tables, which improves performance and query speed. Optimize the database periodically or after heavy database updates (for example, after importing database entries). The Optimize database task in the IBM Tivoli Directory Server Configuration Tool uses the DB2 runstats command to update statistical information used by the query optimizer for all the LDAP tables. Note: The reorgchk command also updates statistics. If you are planning to do a reorgchk, optimizing the database is unnecessary. See Database organization (reorgchk and reorg) for more information about the reorgchk command.
Performance Maintenance
Performance Maintenance Optimization To optimize the database using the Configuration Tool: Start the Configuration Tool by typing idsxcfg on the command line. Click Optimize database on the left side of the window. On the Optimize database window, click Optimize. After a message displays indicating the database was successfully optimized, you must restart the server for the changes to take effect. To optimize the database using the command line, run the following command: runstats -I See "idsrunstats, runstats" in the IBM Tivoli Directory Server Version 6.0 Administration Guide for more information. Again, you must restart the server for the changes to take effect.
Performance Maintenance
Performance Maintenance Optimization The frequency that you will need to run runstats or reorgchk depends on your workload. We typically recommend that you perform these operations at least once per week. If you have high write activity you may need to run runstats / reorgchk more frequently.
Performance Maintenance
Performance Maintenance One of the most significant performance improvements is typically seen when proper indexing is done. The ibmslapd.log will point out attributes which are frequently used but are not correctly indexed. For Example: Attribute is not indexed but is used in search filters times Use the directions in the ITDS 6.0 Performance and Tuning Guide to index this attribute; or use the following technote: http://www-1.ibm.com/support/docview.wss?rs=767&context=SSVJJU&dc=DB520&uid=swg21256987&loc=en_US&cs=UTF-8&lang=en&rss=ct767tivoli
Perform Regular Back Ups
Perform Regular Back Ups The most important element to a Directory is the data which is stored within its structure. Regularly backing up this data can be achieved through a couple of options: Option 1: Full backup of the data can be achieved with the idsldif2db command. This command has two advantages: This command can be run while IBMSLAPD is running The file can be transferred to any other ITDS 6.0 server which is cryptographically synced to receive the data. #idsdb2ldif –I inst_name –o /filesystem/full_backup.date.ldif Depending on how often your data changes it’s advised to do this form of backup often (for example: changes frequently – daily, or fairly static – monthly). When the ldif completes it a good idea to view the data to make sure its valid. It's important to have a test system to test out the resulting backups. An ITDS admin would regularly check the ldif files resulting from the idsdb2ldif: to make sure ldif files are valid (have the right format etc) To make sure the ldif files have the complete data set. It's important to have a test environment to test out the resulting backups. Please note: you will still need to manually back up all files in //idsslapd-/etc (ibmslapd.conf, ibmslapddir.ksf, schema files, etc)
Perform Regular Back Ups
Perform Regular Back Ups Option 2: Included with ITDS version 6.0 is an ITDS utility called: idsdbback. Its important to note this utility will back up: The instance ibmslapd.conf (The “config” file) The instance ibmslapddir.ksf (Key Stash File) The database instance. To run this you must have ibmslapd stopped: # idsdbback –I inst_name –k /filesystem/dbbackup You have chosen to perform the following actions: GLPDBB029I The database and configuration files for directory server instance 'db2inst1' will be backed up to '/home/db2inst1'. Do you want to.... (1) Continue with the above actions, or (2) Exit without making any changes: 1 ? Select 1
If you try to run this with ibmslapd up it will give the error: GLPCTL088E Unable to run the command on directory server instance ‘inst_name', while it is running. GLPDBB004W The program did not complete successfully. View earlier error messages for information on the exact error. When you issue the command you will see the following prompt: idsdbback -I db2inst1 -k /home/db2inst1 You have chosen to perform the following actions: GLPDBB029I The database and configuration files for directory server instance 'db2inst1' will be backed up to '/home/db2inst1'. Do you want to.... (1) Continue with the above actions, or (2) Exit without making any changes:1
Administrative Tasks and Server Maintenance
Administrative Tasks and Server Maintenance You should now understand the following: Where to get the latest fixpacks for ITDS 6.0 How to install a fixpack How to set the ulimits How to optimize the database The importance of setting indexes How to back up your data
Copyright and trademark information
Copyright and trademark information © Copyright IBM Corporation 2000 - 2007. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM web site pages may contain other proprietary notices and copyright information which should be observed. IBM trademarks http://www.ibm.com/legal/copytrade.shtml#ibm Fair use guidelines for use and reference of IBM trademarks http://www.ibm.com/legal/copytrade.shtml#fairuse General rules for proper reference to IBM product names http://www.ibm.com/legal/copytrade.shtml#general Special attributions IBM, the IBM logo and DB2 are trademarks of International Business Machines Corporation in the United States, other countries, or both. MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product or service names may be trademarks or service marks of others.