Last year around this time I posted what became a top 10 page for my blog, the IBM Connections 4.0 installation spreadsheet. I took the IBM Wiki page provided and broke it down by topics (IHS, WAS, DB2, etc) and included some items along the way as well.
For those that need, that is, should be, documenting your installation details, hopefully this helps make your life easier.
Yesterday IBM posted an update for 4.5 CR1 here.
I have updated my spreadsheet and included the changes as posted as well.
You can get the new version and make sure it says 45 in the title here or from my Downloads page.
Enjoy
Speaker, Blogger, Author. Posts about HCL Digital Solutions, HCL Software, Lotus, Management, Collaboration, Competitive Intelligence and Strategy, Productivity, CRM and B2B Marketing.
Showing posts with label TDI. Show all posts
Showing posts with label TDI. Show all posts
Thursday, June 20, 2013
Tuesday, January 10, 2012
TDI Troubleshooting Access Rights
Been working on a TDI project for the last few weeks and it looked to be almost done, then everything stopped working.
So, what to do? Asked around but did not find any great answers, just vague ideas or theories but nothing to point at and go AHA! So I did what I advocate and called in a PMR to IBM when nothing or no one else could help efficiently. Seems everyone is busy trying to finish work before Lotusphere.
Brian H. from support was helpful in pointing me in the right direction although there is a lack of info surrounding the problem experienced.
What we found was we suddenly had messages similar to this:
Checking under the logs directory under my TDISOL directory the ibmdi.log showed some errors but nothing that pointed to anything directly.
So off we went to find how to get more logging details. Knowing there is a log4J reference meant finding out how and where to set logging and what levels it has.
The directory also under TDISOL called etc is where you can find the log4j.properties file. In it you will find a line that says:
In our case it showed some jar files and other pieces could not be read, from the directory one ABOVE TDISOL which is called V70A on our box and in the jars directory, and it's sub directories(V70a/jars/connectors and V70A/jars/3rdparty) among them.. We asked for more access to cover the whole directory and all ran properly.
So it was an access issue and not a code problem, unlike my NULL post which is still testing before I post the conclusions.
So, what to do? Asked around but did not find any great answers, just vague ideas or theories but nothing to point at and go AHA! So I did what I advocate and called in a PMR to IBM when nothing or no one else could help efficiently. Seems everyone is busy trying to finish work before Lotusphere.
Brian H. from support was helpful in pointing me in the right direction although there is a lack of info surrounding the problem experienced.
What we found was we suddenly had messages similar to this:
Log4J: Error Either File or DatePattern options are not set for appender [null]Descriptive. I know.
Checking under the logs directory under my TDISOL directory the ibmdi.log showed some errors but nothing that pointed to anything directly.
So off we went to find how to get more logging details. Knowing there is a log4J reference meant finding out how and where to set logging and what levels it has.
The directory also under TDISOL called etc is where you can find the log4j.properties file. In it you will find a line that says:
log4j.logger.com.ibm.di.config=WARNEdit the WARN to ALL if you are having problems to get a very detailed log, save and run your scripts. More details on the options can be found in this Wiki http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Troubleshooting_problems_with_Tivoli_Directory_Integrator_ic301
log4j.logger.com.ibm.di.loader=WARN
In our case it showed some jar files and other pieces could not be read, from the directory one ABOVE TDISOL which is called V70A on our box and in the jars directory, and it's sub directories(V70a/jars/connectors and V70A/jars/3rdparty) among them.. We asked for more access to cover the whole directory and all ran properly.
So it was an access issue and not a code problem, unlike my NULL post which is still testing before I post the conclusions.
Wednesday, January 4, 2012
Null Users? But They Are Real People but not in TDI
Happy New Year!
So what's wrong with TDI? (This affects 6.0 and 7.0 so far which is the versions running) It seems there is an ominous line that states:
Lotus Connections documentation and wikis here, here and here.
That's fine but what do you do for the Null family? Poor James, Sara, Amy, Fred, John Boy, Scarlett and whomever else with Null as a last name? They can't get in? No Connections for them? So what is going on?
There were some vague TDI references in fix packs to attributes with NULL in them. We are waiting on IBM for some direction because those fix packs are not compatible, per documentation, with Connections 3.0.1.
We also worry what this will do inside Connections when it hits the Null fields on logins or searches or links or whatever. So working around TDI is one thing, Connections is another.
We do know this much, new people never get added to the profiles database. People already added, never get deleted if they left the company and anyone else is there because when you do the first load off a CSV file evidently TDI could care less and accepts what you submit. BUT if TDI is to run and get updates programmatically it checks for any Last Name field which is empty/Null and stops processing that person.
When we have an update from IBM will post it, until then if anyone has some insight please let me know your experience.
PS - My apologies to the IBM QA team for TDI and Connections, you have one more thing to add to your lists.
So what's wrong with TDI? (This affects 6.0 and 7.0 so far which is the versions running) It seems there is an ominous line that states:
And this can be found in 2.5 and 3.0 IBM
"The population wizard populates only those entries where the value for surname is not null."
That's fine but what do you do for the Null family? Poor James, Sara, Amy, Fred, John Boy, Scarlett and whomever else with Null as a last name? They can't get in? No Connections for them? So what is going on?
There were some vague TDI references in fix packs to attributes with NULL in them. We are waiting on IBM for some direction because those fix packs are not compatible, per documentation, with Connections 3.0.1.
We also worry what this will do inside Connections when it hits the Null fields on logins or searches or links or whatever. So working around TDI is one thing, Connections is another.
We do know this much, new people never get added to the profiles database. People already added, never get deleted if they left the company and anyone else is there because when you do the first load off a CSV file evidently TDI could care less and accepts what you submit. BUT if TDI is to run and get updates programmatically it checks for any Last Name field which is empty/Null and stops processing that person.
When we have an update from IBM will post it, until then if anyone has some insight please let me know your experience.
PS - My apologies to the IBM QA team for TDI and Connections, you have one more thing to add to your lists.
Monday, January 17, 2011
TDI Update Gotcha while working on Connections
Tivoli Directory Integrator which I was using for a Connections installation in our office (we had the 2.5 series running, tore that down and rebuilding 3.0) had an update. No problem, follow the usual process.
Unzip the file 7.0.0-TIV-TDI-FP0006.zip(or newest update) to create a folder with the same name. Change to this directory and locate the UpdateInstaller.jar Jar file.
Copy and paste this file in the E:\IBM\TDI\V7.0\maintenance directory, replacing the existing file with the same name.
Open a command prompt and change to the E:\IBM\TDI\V7.0\bin directory and run the following command:
applyUpdates.bat -update e:\whateverdirectorystructure\TDI-7.0-FP0006.zip
Yet it failed. Many times. Tried checking typing, tried downloading it again, but no dice.
Googled it and didn't find a great answer either.
But what seems to be a recurring problem with software these days is the possibility of running out of character space for a file location. Maybe this was the issue, maybe not.
In the end, copied the directory to the root drive, E:\tdi-update-70006 and ran it from there.
This time it worked.
While checking on this I found the Connections Wiki actually says it unzipped to the root of the drive. Doesn't say you must and since installation files are elsewhere hadn't thought of it. So there you go, maybe it's not about character length as much as some odd coded requirement.
Wish there was a gotcha list for Connections?
Wait, there is, if you go to Lotusphere in 2 weeks, you can go to a session with this in mind.
It is given by Stuart Mcintyre and Rob Wunderlich.
BP105 Twelve MORE Things Your Mother Never Told You About Deploying IBM Lotus Connections 3.0
Dolphin S. Hemisphere II - Monday 3:45pm - 4:45pm
No idea if this made it to their session, I wills ee you and them there.
Unzip the file 7.0.0-TIV-TDI-FP0006.zip(or newest update) to create a folder with the same name. Change to this directory and locate the UpdateInstaller.jar Jar file.
Copy and paste this file in the E:\IBM\TDI\V7.0\maintenance directory, replacing the existing file with the same name.
Open a command prompt and change to the E:\IBM\TDI\V7.0\bin directory and run the following command:
applyUpdates.bat -update e:\whateverdirectorystructure\TDI-7.0-FP0006.zip
Yet it failed. Many times. Tried checking typing, tried downloading it again, but no dice.
Googled it and didn't find a great answer either.
But what seems to be a recurring problem with software these days is the possibility of running out of character space for a file location. Maybe this was the issue, maybe not.
In the end, copied the directory to the root drive, E:\tdi-update-70006 and ran it from there.
This time it worked.
While checking on this I found the Connections Wiki actually says it unzipped to the root of the drive. Doesn't say you must and since installation files are elsewhere hadn't thought of it. So there you go, maybe it's not about character length as much as some odd coded requirement.
Wish there was a gotcha list for Connections?
Wait, there is, if you go to Lotusphere in 2 weeks, you can go to a session with this in mind.
It is given by Stuart Mcintyre and Rob Wunderlich.
BP105 Twelve MORE Things Your Mother Never Told You About Deploying IBM Lotus Connections 3.0
Dolphin S. Hemisphere II - Monday 3:45pm - 4:45pm
No idea if this made it to their session, I wills ee you and them there.
Subscribe to:
Posts (Atom)