IBM Connections Review
IBM Connections on IBM i - DB2, JDBC and IASPs


For anyone looking to do an IBM Connections install on IBM i, the biggest "gotcha" I encountered was due to the fact that I have an Independent Auxilliary Storage Pool (IASP) defined in my relational database directory entries list (think WRKRDBDIRE). If you're using IBM PowerHA for replication then you'll have an IASP defined. I would log into the Connections homepage successfully but then get an error that the request couldn't be completed. I found errors in the systemout.log for each application like "SQLException: Relational database not in relational database directory. DSRA0010E: SQL State = 42705, Error Code = -99,999."

Connections tries to connect to DB2 using the JDBC databaseName custom property, not find it in the WRKRDBDIRE list and then the DB2 connection fails. Errors like this happen regardless if your DB2 databases for Connections are in the IASP or in *SYSBAS. IBM support tells me if you don't have an IASP defined then the databaseName parameter is ignored and you won't run into this problem. In case you don't have an IASP defined and still get these errors it can't hurt to give the below solution a try. I may prove it out on a test partition later.

The solution is to blank out the databaseName custom property for each JDBC data source. Once I did this and restarted the applications I was then able to access the Connections applications that interact with DB2.


My first impressions of Connections on IBM i? It rocks!

I saved a lot of time on the installation because I already had WebSphere Application Server 8, Installation Manager and of course the integrated DB2 for i up and running already. Most of my time was spent was on configuration after the fact. Much thanks to Stuart McIntyre, Sharon Bellamy and Gab Davis for a few pointers when I was scratching my head a little.

Disclosure: I am a real user, and this review is based on my own experience and opinions.

Add a Comment

Guest
Why do you like it?

Sign Up with Email