Tom Duff and I are presenting a Show ‘n Tell Session at Lotusphere – SHOW106 “Configuring the Tivoli Directory Integrator for IBM Lotus Domino and Active Directory”
Now you may think that with a product name that includes “Directory Integrator” as part of its name that this is only a tool for directories and therefore maybe a tool for admin types only. Not so!
For example, one of the new connectors in TDI 7.0 is an XML parser.Now while I can’t speak for my fellow administrators, when I hear XML parsing my eyes glaze over.But I know developers who will just squeal over the opportunity to manipulate XML between external sources and Domino databases.Remember that TDI has a connector for Domino databases – not only the names.nsf.And with connectors to relational DB’s like SQL wouldn’t you dev’s like to have a way to move that data back and forth between Domino?
TDI is available as a free download with your Domino server license.And you’re entitled to use it as long as your assembly line (TDI process) includes Domino as a component of that process.So whether you’re synching, pushing or pulling data, doesn’t FREE appeal to you?Check it out for yourself.And better yet, if you’re attending Lotusphere be sure to attend our session.We’ll help you get started on building your own “integration engine.”
With the exciting news about Notes/Domino 8.5.1 going gold on Monday October 12th, don’t forget that with 8.5.1 you're now entitled to Tivoli Directory Integrator V.7!
TDI can be found in the “Associated Products at No Charge” section of your Passport downloads.And remember you may use TDI as long as a Domino or Notes process is part of a TDI assembly line.
TDI 7 features a new interface and is loaded with additional features. Be sure to visit the Tivoli Directory Integrator Version 7 Information Center for more details! :-)
In this installment, we’re going to delve a little deeper into Tivoli Directory Integrator by demonstrating how to update an external LDAP server with Domino Directory [Duffbert - Notes Address Book aka NAB or names.nsf using LDAP – for us developer types] data using a TDI LDAP connector.This particular AssemblyLine will also stretch our TDI skills by require some JavaScript to parse the Domino data into the format needed by the external LDAP server.
Before we begin this process, we need to have a Domino server that is running the LDAP server task.We’re using an LDAP type connection for Domino for our demonstration.We only need reader access to the Person documents in the Domino Directory because we are not updating fields in those documents.Likewise, we are going to update records in the external LDAP directory, so we need the appropriate login credentials and update authority in the LDAP tree.We are not deleting attributes, so we do not need delete authority in this example.
In this particular AssemblyLine, our goal is to update some Domino-related attributes in our external LDAP server.We’re including these values in our external LDAP entries for each person, so that Domino can be later configured to use the external LDAP as the source for HTTP, IMAP, and Sametime authentication. [Marie – Domino admins out there will note that Directory Assistance will be used on the Domino side for authentication…this is a handy trick!Duffbert – yeah, yeah… get to the good stuff!] The attributes have already been added to the schema on the external LDAP server, as they did not previously exist.What is important to note is that we need a unique key to match the records from Domino to LDAP.In our example we use unid (which is an LDAP default identifier) and an employee id number.The AssemblyLIne does not require two keys to link data attributes, but in this case we are using two, and as you’ll see the AssemblyLine will allow you to use multiple keys.
The attributes we’re going to work with are the following:
$dn
DominoUserAbbrev
DominoUserName
displayname
mailfile
mailserver
sametimeserver
employeeid
uid
To get started we create a new TDI Configuration.
Next we create a new AssemblyLine.
Now we’ll create a new Connector called DominoLDAP in “Interator” mode.
So now we have a Domino LDAP connector.Next, we’ll create our connector to our external LDAP server.This will work exactly the same as the one we just created, but we’ll call it EDIRLDAP and set it up as an “Add Only” Connector.
So how do we connect to our Domino server via the LDAP connector?We connect using the LDAP url and port of our Domino LDAP server, with a userid and HTTP password that has access to read the Domino Directory. [Marie – we can also set up an SSL connection by selecting that option.]
We’re also limiting the LDAP search filter by using the objectclass=dominoperson.This will give us only those attributes in the dominoperson schema.
We use the same method to connect to the external LDAP by connecting to the specific LDAP server and limiting the search base and search filter based on what we’re going to update in the LDAP schema.
Once we set up our login information, we’ll want to make sure we can actually “talk” to the servers via TDI.To do this, we use the Establish Connection button (the little plug)
If all the information is correct in the previous step, we’ll see that a “Connection Established message.
Now, we can click the “Read the Next Entry” button (the little triangle) to cycle through the entries in the actual LDAP directory.This will allow us to view real “live” data to confirm the formatting.
So to recap – we’ve created a new AssemblyLine, created two new connectors, and tested the connections.What’s next?Now we want to add the connectors to the appropriate places in our AssemblyLine. We can do this by dragging and dropping the “DominoLDAP” connector over to our AssemblyLine Feed indicator.Add the External LDAP connector – as our AssemblyLine “flow” by the same method.
How do we pick fields we want to work with?A couple of things to keep in mind – the Feed connector will have an INPUT tab and your Flow connector will have an OUTPUT tab.These tabs are where we work with selecting our data fields also known as Work Entries:
Okay, these next steps are a little hairy so pay close attention.On the FEED/INPUT Map – we have WORK Attributes.These are the select group of data fields from our Domino Directory.Some of these Work Attributes actually exist in the schema of the Domino Directory, and we can use them as is, so we can drag and drop them from the Schema View over to our Work Attribute list.
Once we’ve selected a Work attribute, say for example “givenname”, if we know that we’re going to use that value as is, we can enable that in the Attribute Map settings (the Attribute Map is displayed when a Work Attribute is selected individually). So we’ve selected the Work Attribute by name in the Attribute Map as well as selected “Enabled” and type as “Simple”.
Now we do need to do some parsing, as the format from Domino does not match that of the LDAP results as we showed in the table above.The method for making those changes involves pulling the data from the feed and making the change to the work items, and then parsing the data when it is output.We’re going to use JavaScript to perform these operations.
Let’s start with one of the Work Attributes – mailfile.Because the data in the mailfile field from the Domino Directory needs to be parsed, we use JavaScript to change how the data appears.We do this in the Attribute Map Setting by selecting Advanced (JavaScript).
We also have some Work Attributes that don’t exist in the Domino Directory, but they will need to map to fields in our external LDAP directory.So we click the Add New Attribute button.In this example we are going to add a Work Attribute called “DominoUserName” that will use data from the Work Attribute called “$dn”, and we’re going to do some Advanced (JavaScript).
Once we have completed updating both the Work Attributes (Feed) and Connector Attributes (Flow), we should have the following fields with the appropriate coding:
So how do we “join” the two separate sets of data?We link them via our keys and the Link Criteria tab on the AssemblyLine Flow attribute.As we said we’re going to make sure that our entries in the External LDAP server are updated only when the unid and $unid are the same AND when the employeeid is the same.So we’ll link those attributes on the Link Criteria.
On the Flow Object – EDIRLDAP – go to the Link Criteria tab.Click on the Add New Link Criteria icon (the little chain) and select “uid” as the connector attribute, “equals” as the operator, and “$uid” as the value.
uid is the value in the Domino Directory, and $uid is the value in the external LDAP Directory.
So we go ahead and create a similar link criteria for “employeeid” as the connector attribute, “equals” as the operator, and the attribute that contains the employeeid in the external LDAP directory.[Marie: Attribute and value names don’t have to match when establishing them as link criteria.]
Now that we’ve set up linking, and customized our Work/Connector Attributes, our Work Entry view should look something like this:
Whew!Now would be a perfect time to save the AssemblyLine configuration as we certainly wouldn’t want to have to rebuild all those connections.And a word of caution before we proceed to the next step… As with any system, you want to make sure that you have a test environment to work with before you put this into the LIVE REAL WORLD!TDI is very powerful, and could easily wipe data from the feed or the flow ends of the AssemblyLine.So please don’t take our names in vain and say that we didn’t warn you!
So we’re ready to start our AssemblyLine and see how we’ve done.We’re going to select Standard as our Run Mode and will click the start button to complete.
A tool that may come in handy when you’re working with LDAP entries on different types of servers is an LDAP browser, so you can review your data.One we’ve used before is the Softerra LDAP Browser (they have a free version!).
Here’s one of our diagrams to display what we’ve done:
Using this example, you can now synchronize your Domino LDAP directories to all your other external LDAP directories without having to invest in an expensive tool to do so.That should make you very popular with your boss, and may be a leverage point when you ask him for permission to go to Lotusphere!
So now that you’ve got TDI set up and running on your workstation, the question becomes how to make it do something useful.In this installment, we’ll take a CSV file containing some data and use TDI to load a Notes database on a local Notes server. This is a very basic example, but it’s something that all Notes developers and administrators have had to do numerous times. And our hope is that it will start to acclimate you with the basic steps to set up a TDI AssemblyLine.
So first, start up TDI as well as your Domino server and Notes client.In this example, we have a CSV file of book titles that Duffbert has read, and we want to import that into a Notes database (so he can keep track of what he’s already read).
Nothing fancy here… We’re just looking to get the basics in connectivity down.
So begin by starting Tivoli Directory Integrator.When it first loads, you’ll see a blank command screen (which is the Java background task loading), then the TDI GUI will load.To begin, you’ll want to create a new configuration. That’s done by using the File > New menu option, which will present you with a dialog screen.For this example we’ll call this configuration blogExample01.xml.
That will create your entire project you’ll use going forward.The next thing you need to do once this is done is to make sure you have a particular entry in your java.library.path setting.This is very important when you are running this in local Notes mode.TDI will attempt to find the nlsxbe.dll file during the running of your import, so you have to be sure to have that path in the above java.library.path setting. In this particular instance, we added c:\Program Files\IBM\Lotus\Domino.Without that entry, you will receive a number of errors when the import starts to run.
Creating your new AssemblyLine comes next by using the Object > New AssemblyLine menu option. We called ours CSVToNotes:
With the AssemblyLine in place, we create our first connector to feed in data from the CSV file.That is created with the Object > New Connector option, and you’ll want to choose the ibmdi.FileSystem connector type.That’s the connector that can read a flat file from your workstation.Give it a descriptive name (ReadCSVFile in our case) and put it in Iterator mode.That means it will iterate through the entire file when used:
Our input connector feed is now created!On the file path field, point to where you have the CSV file stored:
The next step is where things get cool… if you click on the plug icon in the Input Map tab, TDI will automatically make a connection to your CSV file.Then if you click the forward icon next to it, TDI will iterate through the detail of the CSV file so that you can see the data you have stored out there.These two steps will assure that you have connectivity to get to your data:
The final step you need to do here is to highlight all four of the entries, and drag them over to the Work Attribute column next to the field names.This is what will allow us to map the CSV columns to the Notes field names:
Half your work is now done!The next step is to create your other connector, the one that will allow you to write out to the Notes database.This time, select the ibmdi.Notes connector wit h a mode of Add-Only.We named our output connector OutputNotesFile:
Again, we’ll go to the connection tab under the Configuration tab and set up the connection information to the Domino server we have on the workstation.This will obviously be specific to however you have your Domino server configured:
At this point, we are simply mapping the CSV columns to the Notes form fields. Refer to the screen picture below:
To get one or more columns from the CSV file, drag them from the Work Entry area on the lower left side into the Connector Attribute column.You can single-click on the Connector Attribute name in order to change it to the Notes field name.In this case, the column names and the Notes field names were the same.Then when you have the Connector Attribute field selected, make sure it’s connected to the right CSV column in the Select from work entry attributes area.
For our Notes form, we do need to add one field that isn’t in there.The Form field is needed so that Notes knows what form to launch the document with.Here’s the example for that field:
We clicked on the Create New Attribute icon at the top of the Connector Attribute column.We then gave it a name of Form, selected a type of Advanced (JavaScript), and used the code snippet of ret.value=”frmBook”; to make sure that each document we create has a Form field in it.
Go ahead and save your work to make sure nothing happens to it at this point!! :-) Now it’s time to see the fruits ofyour labor.In the upper right corner of the TDI screen, you have your run options:
Once you set it to run, you’ll see an output screen of runtime messages from TDI, and hopefully a newly populated Notes database!
Now that you have the basics set up, you can easily and quickly develop new connectors and AssemblyLines to feed in CSV files to Notes with little programming involved.[Marie – Duffbert are you really saying that this might be useful to application developers?! ;-)]
Here's one of our diagram's summarizing the process:
And this is just the basics!In our next few articles we’ll present a method for connecting to LDAP and we’ll get into more of the programming and hooks you can create with JavaScript that end up making TDI a far easier tool for Domino integration than having to manually set up new LotusScript jobs for every new import.
Before we get started with the nuts and bolts of Tivoli Directory Integrator, we figured it might be a good idea to introduce you to many of the concepts and vocabulary you’ll run into when learning about TDI.That way, when you see terms like “assemblyline”, you‘ll know what is going on.There’s nothing worse than trying to learn how to use a new technology when you don’t even know what the main terms mean!
So, you’ve got Domino directories, you’ve got Domino databases, you’ve got data that resides outside of Domino – in say Active Directory, or LDAP, or SQL.Now what? Well to bring these systems together to merge or update data in either direction, we can use TDI.
To get started we’re going to build an AssemblyLine – just like a factory assembly line for manufacturing, the AssemblyLine in TDI is used to identify, move, transform, push, pull or synch data between various Data Sources.
A Data Source is the data system or group of data objects that you are going to connect via the AssemblyLine.And a Connector acts as your means of setting up a logical connection to the Data Source.
Connectors use authenticated processes like LDAP, DIIOP, JDBC, AD, etc., that provide dialog boxes for configuring exactly how the Data Source will be accessed.
Within the Data Source are Entries. These are the data objects themselves.And each entry has Attributes – or sub parts.Attributes describe and or contain the data values from the various data sources that you’re linking together in the AssemblyLine.Values are the objects that contain the actual data values that are being stored and transported through the AssemblyLine.
These are batch or event-driven processes that handle the identification, routing, and transformation of data between data sources.TDI can run any number of these AssemblyLines at any given time.These AssemblyLines are what the developers and administrators of TDI will put together to accomplish their data needs. [Marie – I think of the AssemblyLine as similar to workflow in Domino.]
Here’s a somewhat oversimplified diagram of the TDI process:
Some more advanced terms include:
EventHandlers – These are actions that are monitored by TDI, and that will trigger an AssemblyLine process.This might be an LDAP change, a SOAP call, or a calendar event.
Scripting – Scripting languages are used to create AssemblyLine steps that go beyond the built-in functionality provided in TDI.JavaScript is the language supported in TDI for this function.
Work Entry – an object created by TDI to move data throughout the AssemblyLine process, that is, the process that moves and/or transforms data from one data source to another.
Delta Detection – When a data source has changed and the system needs to figure out what exactly has changed and what needs to be passed to other data sources that should remain synchronized. This is the first of three steps in the Delta operation.
Delta Tagging – Once the Delta Detection has occurred, the data source needs to be annotated to flag exactly what has changed and how it has changed.This helps the synchronization run efficiently.It is the second part of the Delta operation.
Delta Application – This reads the Delta Tagging (also known as Operation Codes) and makes the changes to synchronize the data sources. This is the final step in the Delta operation.
Change Detection Connectors – used by TDI to find changes in standard data sources, such as LDAP, Active Directory, SQL databases, and Lotus Notes.
Delta Engine – Used by TDI to compute changes for data sources that don’t flag updates in any other way.This uses a Snapshot database to track prior values to determine if changes have occurred.
Obviously, there’s far more to TDI than just this.But if you understand these basic concepts, many things will start to drop into place when you start using TDI to move your own data around.
We hope by now that you have downloaded Tivoli Directory Integrator and taken a look at it for yourself.We’ve had a few questions relating to how to install patches as TDI does use its own unique process for updates.So we’re going to run through the steps for making sure that TDI is patched and good to go!
First things first… For example purposes, we’re going to demonstrate a Windows installation of a fixpack.TDI uses an installation software package called GMI for applying fixpacks.If you’re using TDI on a different operating system, review the fixpack release notes for specific instructions.You may want to confirm the version of TDI you’re running.Start the TDI Config Editor, then go to Help – About Tivoli Directory Integrator.This will display the following screen.As you can see we’re working with Version 6.1.1 Build ididev_070207b.
Okay, now on to the update installer process.Itboils
down to just a few steps – downloading the fixpack from IBM FixCentral,
extracting the files to a drive where you have TDI installed, and then
running the installer.Like the TDI product
installer, GMI also uses Java and Flex, and will display a series of
screens during the course of the install.
You’ll need to go to IBM FixCentral ,
and download the appropriate fixpack for your version and operating
system of TDI. You will need an IBM login to download the fixpacks. If
you don't have one it's really easy to create one. [Duffbert – I had never downloaded fixes from FixCentral so this was new to me!] [Marie – sigh.Developers – do they ever patch their software?!]
Fixpacks are usually shipped as zip files.Save
the zip file to a designated location on the workstation or server
where TDI is installed and extract the folders and files – remember
where you save these!If you don’t extract the folders and files, the GMI installer will not be able to find the fixpack in a later step.
To start the fixpack installation using GMI, first locate the gmi.cmd file.For a Windows installation, the default location isC:\Program Files\IBM\Common\ci\gmi\bin
The GMI installer is included as part of the TDI base installation.
In our example, we go to Start, Run, and then Browse to the the location of the gmi.cmd file:
This launches several Java processes:
You may also see the Auto Deployment Engine: Update Installer screen as well:
Welcome to the Update Installer – Select Next to continue:
Select
Next to continue to the installation of the fixpack after choosing
“Install maintenance packages such as fixes, fix packs or refresh
packs.”:
The installer checks to see if there is a valid product to upgrade – in this case it finds TDI 6.1.1!Select Next:
You will be prompted to choose the location of the maintenance files.Select the folder that you extracted from the zip file when you downloaded the fixpack:
The installer will validate the Fixpack package:
Once the installer has confirmed the version and package, it will display the package that is available for installation.Choose the one you’d like to install and then select Next:
We’ll choose install maintenance on this computer only since we aren’t performing a silent install:
The installer will display the confirmation of what is about to be installed.Click Install:
The installer begins processing the files and applying them to TDI:
If the installer was successful you'll see the following screen:
Congratulations! You have successfully
upgraded TDI from 6.1.1.0 to 6.1.1.7.
Now to confirm your version, open the
Configuration Editor, and click Help > About and see that we're now running Build idi611_090609a:
Once you completed this process, you
should have an up-to-date installation of TDI and be ready to work magic!
To respond to several questions about the "limited" entitlement to Tivoli Directory Integrator. We've received further clarification from members of the TDI team (including Eddie Hartman and Andrea Waugh Metzger). "As long as a Domino database or Directory is somewhere in the mix in your [TDI] assembly line, you are licensed for it". You can have other sources linked to that assembly line. For another source - check out Johan Varno's (the TDI architect) site http://sites.google.com/site/dominointegration/ Thanks again to Ed Brill, Eddie Hartman, Andrea Waugh Metzger and Johan Varno!
In this installment of the TDI series, we’ll take you though the installation process.It’s so easy, even a developer can do it. [Duffbert – so that means I can install it!] And for reference, we’re installing this onto a Windows XP 32 bit machine.But given that Java is a prime component of the installation and running of TDI, you should see many of the same screens regardless of your target OS. [Marie – TDI 6.1.1 is not supported on Windows Vista or the Mac OS. See the release notes for specific instructions for installing TDI on the OS of your choice.]
A quick note on the complexity of the installation… Imagine your complexity scale goes from Notes/Domino on the simple end, to something like WebSphere Portal Server, or WAS, on the “abandon hope, all ye who enter” side.With Notes/Domino, you get a wizard that prompts you for some key information, and everything pretty much sets up from there.With just a little bit of knowledge, you can get the install working nearly every time.TDI does have its own method for installing fixpacks – using the GMI installer which is installed with TDI.
Where does TDI fall in this scale?It actually makes the Notes/Domino installation look complex.But is really that easy…
After downloading the software (you did do that already, right?), you go into the tdi_installer folder and launch the install_tdiv611_windows.exe file:
This will start a FLEXNet installer window that will run for a few seconds…
Once this is completed (again, only a few seconds), you’ll get what looks like a more traditional install splash screen for TDI:
Of course, you accept the license because we ALWAYS accept the license:
And then the package starts to check and make sure it can complete the installation process (yes, it really is this easy):
Your first real decision comes when you choose to take custom or typical installation.Go ahead and select Custom, so you can see exactly what’s about to be installed:
Decide where you want to install the software.In this case, we just took the default choice:
Next, you’ll be given the choice of which components to install.Since we selected Custom earlier, all the options are selected by default.We’re going to leave it that way.One of the most important options to keep selected are the examples, as they will help you when we get to the development part of this series.[Marie – if you’re only installing TDI on a workstation to do development work – there is no need to install the AMC and embedded version of Websphere Application Server. ]
Finally,you’ll be asked for a location for your Solutions Directory.This is where TDI will store your agents and assemblylines that you create.In this case, we’re choosing to just use the install directory on our machine to keep things simple. [Marie – I usually put this in the TDI subdirectory under my TDI home directory – administrators versus developers…what can I say?!]
Again, the installer will check to make sure all is still good to proceed:
The rest is all auto-pilot after you click install:
Congratulations!You’ve installed TDI:
Now, before
we close, let’s make sure you can start TDI with no problems…
Somewhere in
your start menus, you should see the following:
Click on the
Start Config Editor option, and you’ll temporarily get what looks like a
command line interface:
Not to
worry… just let this sit for a few seconds, and you’ll be rewarded with the TDI
workspace:
See -- we said it
would be easy… :-)
Go ahead and
get TDI installed on your workstation or server.Our next article will start to explain some
of the terminology you’ll encounter in the TDI world.
[Marie -- if you do run into install issues -- check out this
technote for some troubleshooting tips. Reference 7013120]
[Note - coauthored by Marie Scott and Thomas “Duffbert” Duff]
If you’ve worked with Domino for any length of time, you’ve run into the request to either move data into or out of Notes.It may be getting data from a Human Resource system to populate a phone directory database in Notes.It may be getting catalog orders from a Notes database to feed into an order fulfillment system fed by an Oracle database.And there’s always the need to keep directories synched up in various platforms (Domino directory, LDAP, Active Directory, and so on).What are your options?
You can always enable Domino Enterprise Connection Services, or DECS, to do some of that.There’s Lotus Enterprise Integrator, or LEI, but that’ll cost you extra.Axceler has their Notrix package, which does a very good job of pushing data back and forth between Domino and other systems, but again, it’s a third-party tool that costs money.And of course, talk to any developer and they’ll swear they can code their own solution that won’t cost a cent because they’re already working there.And we all know how those types of systems work out in the long run… they don’t.
There’s an option you likely haven’t considered, however.It’s probably the best free Domino tool you’ve never heard of.And even better, it’s from IBM so you’re staying within the IBM product family.Its name is officially the IBM Tivoli Directory Integrator or TDI for short.This easy-to-install standalone software product allows you to build import/export/transformation workflows between various data sources, as well as schedule them to run at particular times or on certain events.And while the name may have “directory” in it, don’t be misled.This software is meant to move any data from one source to another. [Duffbert – I think they just put “directory” in there so as to not scare away administrators…] [Marie -- I think administrators know the difference and can develop despite what developers think ;-) ]
Over the next few weeks (or however long it takes us), we’re going to post a series of blog entries on TDI, how to set it up, how to program it, and practical examples on how it can be used.By the time we’re done, we hope that you’ll have a valuable new software tool at your disposal, one that will make you the data manipulation guru where you work.
Where Do You Find It?
If you go out to your Passport Advantage account, you can download the software from there.Do a search for “Tivoli directory integrator”, and you’ll find the following:
The nice thing about TDI is that you don’t have to download a number of additional files and packages to get this set up.If you expand out the eAssembly file listed above, you’ll find the particular TDI download for whatever operating system you’re running.
Oh, did we mention that TDI runs on all the different operating systems just like Domino?J
So, while we’re writing the next installment of the TDI series, you can go download the software. It’s well worth the time to do so, and we think you’ll be amazed at some of the new Domino tricks you’ll be able to show off to your customers and clients.
And throughout this series, please feel free to leave comments and questions.We’ll use those to get this series to move in the directions that are most helpful to you.
Here's some more information about the Domino entitlement: http://www-01.ibm.com/software/lotus/notesanddomino/additionalswentitlements.html Also check out these links too! TDI + Domino: http://sites.google.com/site/dominointegration/ TDI 7 (free trial download): http://sites.google.com/site/tdi7islive/ (Thanks go to Ed Brill and Eddie Hartman for the additional info!)
Do you use Tivoli Directory Integrator in your environment? If so, in what circumstances? Do you know what TDI can do you for you? Would you like to see more information about TDI? I had posted some resources in an earlier blog post, but had some conversations this week that led me to believe that some folks really don't know about TDI and that it's available to you as part of your Domino license. It's a tool I use in my production environment on a daily basis. :-)
One of tools that I consider a genuine "Swiss Army Knife" when it comes to connecting disparate data sources and directories is Tivoli Directory Integrator. Here are a few links to point you in the right direction if you are interested in delving deeper into learning more about TDI.
One of the first places to visit is the IBM Tivoli Directory Integrator Users Group. This users group includes sources for TDI training, glossary of TDI terms and concepts, Javascript tutorials, tips and hints, as well as step by step examples.
Integrating Lotus Notes/Domino with Tivoli Directory Integrator, authored in 2008 by Eddie Hartman, a member of the TDI Development Team. This wiki includes a sample CVS file to use to step through the exercises outlined in the wiki. The wiki also contains chapters on using TDI with Domino databases – other than the Domino Directory, and documentation regarding the different types of Lotus Notes/Domino connectors that ship with the Tivoli Directory Integrator.
And here's a recent posting on developerWorks about using TDI with Lotus Connections.
A tag is a keyword that is used to categorize an entry. To view the entries with a particular tag, click a tag name or enter a tag in the box. The tag cloud indicates the frequency of tag use. Popular tags appear darkest. The slider control adjusts how many tags are displayed in the tag cloud.
Ratings
23
|
Title
|
Most Recommendations
|
Most Comments
|
Most Visits
