The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Configuring global security in WebSphere Lombardi Edition V7.2 using Tivoli Directory Server V6.3

Ashok Iyengar (ashoki@us.ibm.com), Executive IT Specialist, IBM

Ashok Iyengar is a member of the IBM Software Services for WebSphere (ISSW) Pre-sales Tech Team. He has worked extensively with the WebSphere Business Integration platform doing proof of concepts, pilots, and architecture design. He enjoys writing. Ashok’s latest book is WebSphere Business Integration Primer.

Summary: Learn how to configure global security in IBM® WebSphere® Lombardi® Edition V7.2 using an LDAP server. This helps enterprise users to log in and use the various applications in Lombardi Edition and allows the IT department better access control. This tutorial uses IBM Tivoli® Directory Server V6.3 as the LDAP server and IBM DB2® as the database.

Date: 26 Jan 2011
Level: Intermediate
PDF: A4 and Letter (1052 KB | 19 pages)Get Adobe® Reader®

Activity: 38836 views
Comments:

Conclusion

This tutorial showed how to install and configure an LDAP server, specifically Tivoli Directory Server. It then described how to import an LDIF file and configure WebSphere global security using federated repositories. The procedure is the same if you use any other LDAP server and you can import the same LDIF file into any LDAP server.

Comments