Chris Whisonant and I had fun preparing and presenting this one together at IBM Connect 2014. Â If you are using IBM Connections this should help you get even more out of Profiles
Category Archives: TDI
Speaking at IamLUG
IamLUG is back in St Louis, MO next week and I will be there and be presenting.  My Session is titled “Fast track users for IBM Smart Cloud for Social Business with Tivoli Directory Integrator“.
I will be showing how to use Tivoli Directory Integrator to provision your users in to IBM SmartCloud. Â In addition I will be covering the basics of Tivoli Directory Integrator, so if you are working with SmartCloud, IBM Connections Profiles, or have any other Directory Integration needs this session will have something for you.
Looking forward to seeing many of you in St. Louis next week.
Connecting Tivoli Directory Integrator to a Domino Database
Most of my work in Tivoli Directory Integrator has been using CSV Files,  LDAP, AD, and DB2 as sources/destination for data occasionally but not often I connect TDI to read/write from a  Domino Database.
This morning I banged my head against the wall for a bit having forgotten one simple step to make this work, so saving this here as much as a note to myself as anything else.
TDI ships with a Notes Connector, but requires a Jar file to be copied from Domino to TDI before it will work, if you are planning on using the Notes Connector make sure you copy NCSO.jar from <dominodata>\domino\java to <tdiprogram>\jars\3rdparty\others and restart TDI.
If you are not using TDI remember both IBM Connections and IBM Lotus Domino both ship with entitlements to TDI, it might be the best free tool you aren’t using.
Default tdiserver Will Not Launch
Yesterday I was working with a fresh install of Tivoli Directory Integrator 7.0 Fix Pack 5 (the required version for IBM Connections), every time I tried to run an assembly line I was faced with this message
Looking at the log I saw this error ‘api.remote.naming.port’ : ‘1099null’
Searching around I find suggestions to check the Default.tdiserver file in the Workspace directory, but the value there looked correct.
Finally I found this entry in the Lotus Connections Wiki, which contained this information
“Tivoli Directory Integrator Configuration Editor port issue: If you see the message "Invalid value specified for ‘api.remote.naming.port’ " when working with the Tivoli Directory Integrator Configuration Editor, you can resolve the issue by manually setting the api.remote.naming.port in the solution.properties file located in the <TDI_solution _directory>.â€
Sure enough when I looked in my solution.propertied I found the bad entry
Once I removed the ‘null’ appended to the port and restarted TDI, the default server started right up
TDI Install Error:null (and how to fix it)
The other day I was installing Tivoli Directory Integrator 7.0 on a Windows XP machine, when I ran into this error during installation.
Very useful error screen, I know. In all fairness this machine has has Tivoli Directory Integrator 6.1, 7.0, 7.1 beta, 7.1 GA, installed, uninstalled, reinstalled any number of times, I suspect that might have something to do with why I ran in to this.
I tried uninstalling all TDI installations from this machine, and cleaning up temp directories, etc., yet was still stuck on “nullâ€.
Fortunately with a little help from my friends in support, I was able to resolve this fairly easily.
The first step was to get a better idea what was actually happening during the install, something a little more detailed then “nullâ€, to do this I ran the installer from the command line with the is:log option, the command line looked like this:
“install_tdiv70_win_x86.exe –is:log install.logâ€
The output from the log file indicated that Installshield was having a problem
“(Mar 8, 2011 1:34:15 PM), Install, com.installshield.product.service.product.PureJavaProductServiceImpl$PatchCheck, err, nullâ€
The resolution turned out to be to remove the Installshield VPD file, the location of which differs based on platform:
Locations of VPD according to ISMP documentation:
* AIX /usr/lib/objrepos/InstallShield/Universal/common
* Generic UNIX /usr/lib/InstallShield/Universal/common
* HP-UX $J(user.home)/InstallShield/Universal/common
* Linux $J(user.home)/InstallShield/Universal/common
* Mac $J(user.home)/InstallShield/Universal/common
* i5OS /InstallShield/VitalProductData/InstallShield/Universal/common
* Solaris $J(user.home)/InstallShield/Universal/common
* Windows — $C:\Program Files\Common Files\InstallShield\Universal\common (if available)
* $J(user.home)\InstallShield\Universal\common (otherwise)
In my case "C:\Program Files\Common Files\InstallShield\Universal\common" where there is a Gen1 and Gen2 directory, I was advised to backup and remove the _vpddb directory from the Gen2 folder
Magically ran the installer again and like magic
You can find more information on manually uninstalling TDI 7.0 in the Infocenter, and support has committed to releasing some technotes around these install errors as well.