IBM Connections 4: Population Wizard fails

The population wizard in IBM Connections enables the user to automatically populate the PEOPLEDB database with the required information from the LDAP. The information from LDAP such as user’s personal information are then displayed in the user’s profile in IBM Connections.

My environment:

  • IBM Connections 4.0 CR4
  • DB2 9.7
  • Domino 8.5.3

Problem Encountered:

The wizard fails when I assign a value in the Country field in Domino.

2-19-2014 10-19-37 AM

Solution I applied:

In Domino, I changed Philippines to ph. Connections validates this as country code; therefore, the entire word is invalid.

 

 

Problem Encountered:

The wizard fails because of telephone number (Office number).

Solution I applied:

Make sure that the character length of the value in Office number does not exceed 32.

Advertisements

Profiles and Communities pages are not rendering properly. Mail and Calendar icons are not showing.

Environment:

IBM Connections 4.0 CR4

IBM Connections Mail 1.0 FP1

Windows Server 2008 R2 SP1

Lotus Domino 8.5.3 FP3

Problem:

After installing CR4 and Connections Mail 1.0 FP1, two problems occurred:

1. The Profiles and Communities pages are not rendering properly.

The Profiles page does not show the Contact Information tab, Background tab, etc. The Communities page only shows one button, “Start a Community”.

2. Mail and Calendar icons are not showing even if Connections Mail 1.0 FP1 is already installed.

Note: When the browser cache is deleted, the Profiles and Communities pages are back to normal, although the mail and calendar icons are still not showing. However, when you refresh the browser, the problems occur again.

Cause:

In my environment, I had previous customization in my customization directory. When I applied CR4, the two errors above occurred. This cause is, in my case, is this:

I inspected header.jsp inside IBM\Connections\customization\common\nav\templates.

On line 128, it should be:

–%><span class=”os-site-mail-notify”></span><%–

Previously it was:

–%><span id=”os-site-mail-notify”></span><%–

I do not know why it was “span id”, though.

Bug: “You are no longer logged in. Click OK to discard your current work and go to the log in screen. Press Cancel to stay on this page so you can copy your current work and preserve any input you have entered.”

This message “You are no longer logged in. Click OK to discard your current work and go to the log in screen. Press Cancel to stay on this page so you can copy your current work and preserve any input you have entered.” is immediately showing up after logging in IBM Connections 4.0! This just happened when I configured the social discovery XML…

Solution:

Well, we have already fixed it! It looks like that we had a misconfiguration in our LDAP (Domino) regarding SSO. We have done the instructions all over again and everything went fine. Too bad we have forgotten what was the exact misconfiguration… But I am sure it was on the side of Domino. We fixed it last December and I left my blog unattended due to busy schedule… 😐

IBM Connections 4 Installation

The IBM Connections 4.0 documentation says that the required fix pack for WebSphere Application Server 7.0 is fix pack 21 together with 5 interim fixes. However, I did not find the interim fixes (I became lazy in reading the labyrinth webpage). What I did was I proceeded with the installation of IBM Connections 4.0 later on.

There was a problem, however. During the validation of the first step of installation, it said that WebSphereOauthsp.ear is missing. Hmmm… A very vague error that misled me! Well, that was the consequence of not finding the interim fixes…

I did not stop thinking and come up with the installation of the latest fix pack for the AppServer, which is fix pack 25. Hooray! The error was gone!

But there’s more! When I successfully installed IBM Connections 4, there was a problem with logging out. When I logged out from some components (Activities, Profiles, etc.), it says “Access Denied”. What the…??

I thought that there might be a problem with the fix pack installed with the IHS and its Plugin. I did some reinstallation of fixes and after long time of working I came up with installing the fix pack 21 for the AppServer, again. And…. hooray!!!

And that’s the end of the story. I just wish that there won’t be any problems in the future with what I did…

Well, there are! In the end I just followed the documentation properly and did not deviate from the procedures.