Connections 4.0 – Metrics and CR2

There is an issue with displaying Metrics within IBM Connections 4.0 if your servers are in the GMT timezone, the effect of which is that Metrics are simply not displayed (as shown in the screen shot below).

Screen Shot 2013-02-06 at 11.06.01

There is a fix for this issue, ifix LO72778,  but after installing CR2 I found the problem re-occurred. To resolve it I realised I would need to re-apply ifix LO72778 which meant I had to do the following:

1. Uninstall the Metrics component of CR2 (LO72170-IC4000-CR02-Metrics)
2. Uninstall ifix LO72778
3. Install the Metrics component of CR2 (LO72170-IC4000-CR02-Metrics)
4. Install ifix LO72778.

What I should have done (and have done subsequently) is uninstall ifix LO72778 before installing CR2 and then re-install it after CR2.

 

Connections 3.0.1 Fix Pack 1 installation issue

During the installation of fix pack 1 for IBM Connections 3.0.1 I had an issue with the upgrade of the News application.
One of the (many) good things about Connections is that it writes a separate insallation/upgrade log for each application which really helps narrow down the search for the cause of installation/upgrade issues, so in this instance I opened the newsUpdate.log (located in /opt/IBM/LotusConnections/logs) and found the following:

 [exec]   [wsadmin] An unexpected exception was thrown.  Halting execution.
 [exec]   [wsadmin] Shutting down workbench.
 [exec]   [wsadmin] Error executing deployment: java.lang.IllegalStateException. Error is Platform not running.
 [exec]   [wsadmin] java.lang.IllegalStateException: Platform not running
 [exec]   [wsadmin]      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:374)
 [exec]   [wsadmin]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [exec]   [wsadmin]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
 [exec]   [wsadmin]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
 [exec]   [wsadmin]      at java.lang.reflect.Method.invoke(Method.java:611)
 [exec]   [wsadmin]      at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:494)
 [exec]   [wsadmin]      at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:114)
 [exec]   [wsadmin]      at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:107)
 [exec]   [wsadmin]      at com.ibm.etools.ejbdeploy.EJBDeploy.deploy(EJBDeploy.java:348)
 [exec]   [wsadmin]      at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:310)
 [exec]   [wsadmin] EJBDeploy level: @build@
 [exec]   [wsadmin] ADMA5008E: The EJBDeploy program failed on file /tmp/app7307803356142343542.ear. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy
 [exec]   [wsadmin] ADMA0063E: An error occurred during Enterprise JavaBeans (EJB) deployment. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy
 [exec]   [wsadmin] ADMA5011I: The cleanup of the temp directory for application News is complete.
 [exec]   [wsadmin] ADMA5069E: The installation of application News failed. This application was in the middle of a full update and therefore is uninstalled from the configuration session. Discard your current configuration session immediately to recover the application. Do not save changes to the WebSphere Application Server configuration repository. The application is not uninstalled from this repository. Until the current configuration session is discarded you do not see this application in the current session.
 [exec]   [wsadmin] WASX7017E: Exception received while running file "/opt/IBM/LotusConnections/ConfigEngine/config/work/was/EarUpdate.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for News failed: see previous messages for details.

After some investigation I eventually found a technote ( EJB Deploy Error: java.lang.IllegalStateException: Unable to acquire application service ), which whilst not directly relating to Connections, looked as though it could help resolve the issue.

The technote says “The problem may occur when Enterprise JavaBeans Deploy is updated as part of a Fix Pack install and there are files in the EJB Deploy configuration directory from the previous EJB Deploy install.” and the recommended fix is to delete the contents of the EJB Deploy Configuration directory.

As I was fortunate enough to be doing the install on virtual machines I reverted to the snapshots taken just prior to starting the upgrade, then removed the contents of the EJB Deploy Confiuration directory (/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/ejbdeploy/configuration) and re-ran the installation of fix pack 1, which this time completed successfully.

IBM Connections – Incorrect Global Moderation Alerts

I’ve been working with a customer recently on Moderation within IBM Connections 3.0.1 and we discovered an issue where alerts are being sent to Global Moderators when they shouldn’t.

In this scenario pre-moderation (content approval) is disabled but post-moderation (content flagging) is enabled and Blog owners (both Community and standalone) are allowed to moderate comments on their blogs.

If a Blog owner enables moderation on comments then they will receive a notification asking them to approve (or not) comments when they are submitted. The problem is that the Global Moderators also receive this notification which they shouldn’t (as pre-moderation is disabled).

There is now an iFix available to resolve this (LO64314) which is well worth applying to avoid your Global Moderators getting emails asking them to approve comments they can’t even access.

Quickr hotfix adventures

A colleague of mine, Ben Williams, has been working extensively over the last few weeks with IBM to resolve a Quickr 8.2 instability issue for a customer. The initial fix was upgrading from fix pack 11 (8.2.0.11) to fix pack 12 (8.2.0.12), this didn’t resolve the issue and actually created a new one; creating a Quickr Place from a Lotus Connections Community failed and produced the following error – “Failed to create or update an associated application.” (fig. 1)

fig. 1

IBM provided a Quickr hotfix – 14-003a – which resolved the new issue (not the original issue though) but during the testing of it two new issues where discovered.
1. The Quickr Place widget in Lotus Connections Communities stopped working.
2. Disconnecting a Quickr Place from a Community caused Quickr to crash.

IBM quickly (no pun intended) gave us another hotfix – 14-005a – to resolve the two new issues unfortunately the Quickr Place widget for Lotus Connections Communities created whilst hotfix 14-003a was installed were still broken (thankfully this was only test Communities and Places), these Places needed to be disconnected from the Community and then deleted (qptool remove -cleanup) from Quickr.

The support and assistance from IBM has been good and the rollback to fix pack 11 was always an option, but the moral of the story is make sure you test hot fixes and for Quickr if your using Lotus Connections test the Connector functionality as well.

Meanwhile Ben and IBM are still working on the original issue of the Quickr 8.2 instability…..

IE8 and Lotus Connections Rich-Text-Editor

In two seperate Lotus Connections environments each where the customer is using HTTPS we’ve seen an issue where the Rich-Text-Editor does not load for people when using IE8, instead you get “Navigation to the webpage was canceled”

This issue does not occur in FireFox, Google Chrome, IE6 or IE7 (and IE8 when using just HTTP).

Now I know IE8 is not a supported browser but it’s out there and this had the potential to start becoming a real problem for customers. The good news is that installing Fix Pack 2 resolves the issue.

Lotus Connections Fix Pack 2

Lotus Connections Fix Pack 2 (2.5.0.2) is now available from Fix Central and the list of fixes is fairly extensive at over 100 fixes.

The full install instructions can be found in IBM technote 1431472 , and it’s worth being aware that as well as an update to TDI you need the new update installer (download.updii.2502.multi.00001,  File name: LotusConnectionsUpdateInstaller.zip).

Follow

Get every new post delivered to your Inbox.