Issue with Connections after WAS update to 8.5.5.8

After WAS Update from 8.5.5.6 to 8.5.5.8 I could login only into “Profiles” Connections Application, all other Connections Applications were not “reachable”. After digging little further I found the following Errors in the “AppsCluster” Logs:

0000016f LotusConnecti E com.ibm.openactivities.exception.OpenActivitiesException: com.ibm.connections.directory.services.exception.DSException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: CLFRK0004E: Directory Service Extension(DSX) received a HTTP response from URL ‘https://social-d.bat-groupware.at/profiles/dsx/instance.do?login=WBTSTT’ expected XML, received unexpected content-type ‘text/html;charset=UTF-8’!

javax.servlet.ServletException: com.ibm.openactivities.exception.OpenActivitiesException: com.ibm.connections.directory.services.exception.DSException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: CLFRK0004E: Directory Service Extension(DSX) received a HTTP response from URL ‘https://social-d.bat-groupware.at/profiles/dsx/instance.do?login=WBTSTT’ expected XML, received unexpected content-type ‘text/html;charset=UTF-8’!

E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[action]: com.ibm.openactivities.exception.OpenActivitiesException: com.ibm.connections.directory.services.exception.DSException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: com.ibm.connections.directory.services.exception.DSOutOfServiceException: CLFRK0004E: Directory Service Extension(DSX) received a HTTP response from URL ‘https://social-d.bat-groupware.at/profiles/dsx/instance.do?login=WBTSTT’ expected XML, received unexpected content-type ‘text/html;charset=UTF-8’!

After that I found out that the “Domain Name” setting for the Single sign-on (SSO) Configuration has changed after the update. You can get to this setting by logging into ISC Console and navigating to: “Security à Global security à Web and SIP security à Single sign-on (SSO)”.

This may be specific to our environment, usually all our Windows Servers use “bat.dir” Domain, after a service is installed on them which is going to be used in the production we create a “Alias (CNAME)” entry in the DNS for it in the “.bat-groupware.at” Domain.

Connections Applications on this server are configured to use “.bat-groupware.at”, so after I changed the “Domain name” setting to the correct value, all Applications were working fine.

Advertisements

IBM Connections 5.5 CR1 and IBM Docs 2.0 iFix 005 Available

The IBM Connections 5.5 CR1 and IBM Docs 2.0 iFix 005 are available for download on FixCentral.

IBM Connections 5.5 CR1 Fix List.

IBM Connections 5.5 CR1 Download.

Cumulative Refresh 1 requires a Homepage Database Schema update which can be found here.

IBM Docs 2.0 iFix 005 Release Notes.

IBM Docs 2.0 iFix 005 Download.

It is recommended to update to the latest software release, so happy downloading… 🙂

Changing the IP-Address of a Connections Server

There are a few things to consider before changing the IP-Address of a DMGR or a WAS node where Connections applications are running.

It is important to make sure that you have used a DNS record instead of the IP-Address you wish to change in course of the installation and configuration of IBM Connections. This way you can be sure that there are no other changes you have to apply in order to successfully change the IP, assumed you do not change the name of the DNS record.

This is where a good documentation matters, the easiest way to check if IP-Addresses were used in course of the configuration would be to check the documentation of the Connections environment.

The other way is to search for the IP-Address you want to change in the XML configuration files of the WAS cell, if you don´t find it there than you can be pretty sure that you are good to go. Since undocumented configuration changes are frequent this should be a recommended course of action.

The XML files mentioned above are located under:

<WAS_Installation_Root>\AppServer\profiles\<DMGR_Profile>\config\cells\<Cell_Name>\LotusConnections-config\

It is also important to check the other possible consequences in your network environment.

After that you can continue with the following steps:

  1. Shutdown all WAS Application Servers running on a Server whose IP needs to be changed.
  2. Shutdown the Node Agent.
  3. Shutdown the DMGR, if it is running on the same server.
  4. Shutdown the IBM HTTP Server, if it is running on the same server.
  5. Change the IP-Address.
  6. Delete the WAS directories with temporary data.
    • <WAS_Installation_Root>\AppServer\profiles\<DMGR_Profile>\temp
    • <WAS_Installation_Root>\AppServer\profiles\<DMGR_Profile>\wstemp
    • <WAS_Installation_Root>\AppServer\profiles\<Node_Profile>\temp
    • <WAS_Installation_Root>\AppServer\profiles\<Node_Profile>\wstemp
  7. Start all components in a reverse order.
  8. Check if your Connections Applications are working correctly.
  9.  Document the IP-Address change.