Rolling back Connections 6.0 CR3

Roll back IBM Connections™ 6.0 CR3 and optionally restore the previously installed version of the IBM Connections™ Engagement Center.

About this task

This task only applies to CR3 deployments, which now include the former Connections Engagement Center as an integrated feature called Highlights. If you previously installed the stand-alone Connections Engagement Center, you can re-deploy it after you complete the CR3 rollback.

Procedure

IBM Connections™ 6.0 CR3 installs an additional WebSphere® Enterprise Application for the Highlights widget that replaces the stand-alone Connections Engagement Center. If you need to roll back CR3 to Connections 6.0 CR2 for any reason, this additional application must be uninstalled before the rollback can be completed. If you previously used the stand-alone Engagement Center, you can re-install it after the roll-back is complete.

  1. Stop the Connections application on the server or cluster, but leave WebSphere® Application Server running.
  2. On the deployment manager, log in to the WebSphere® Integrated Solutions Console.
  3. Click Applications > Application Types > WebSphere enterprise applications.
  4. In the list of WebSphere® Enterprise Applications, select ICEC and then click Uninstall.
  5. Click OK to uninstall the Highlights feature (ICEC), and then click Save (in the "Messages" box) to update the master configuration.
  6. Delete the authentication data for ICEC:
    1. Click Resources > JDBC > Data sources, and then select icec.
    2. In the "Related Items" section, click JAAS - J2C authentication data and then delete icecJAASAuth.
    3. Click Save (in the "Messages" box) to update the master configuration.
  7. Delete the data source for ICEC:
    1. Click Resources > JDBC > Data sources.
    2. Delete icec.
    3. Click Save (in the "Messages" box) to update the master configuration.
  8. Delete the JDBC provider for ICEC:
    1. Click Resources > JDBC > JDBC Providers, and then select icec.
    2. Delete icecJDBC.
    3. Click Save (in the "Messages" box) to update the master configuration.

Step 9 only applies to deployments where the stand-alone Connections Engagement Center was installed before the CR3 update was applied. If you did not deploy the Engagement Center previously, skip to step 10.

  1. Roll back the previously installed stand-alone Connections Engagement Center.
    1. Click Resources > JDBC > Data sources.
    2. Delete the jdbcProvider that was specified in the ICEC install.properties file when you deployed the stand-alone Connections Engagement Center.

      The default value in the file is activitiesJDB.

    3. In the "Related Items" section, click JAAS - J2C authentication data.
    4. Delete the JaasAuth that was specified in the ICEC install.properties file for the "authAlias=" setting when you deployed the stand-alone Connections Engagement Center.
    5. Click Save (in the "Messages" box) to update the master configuration.

All users, complete the removal of the Highlights feature and then roll back the CR3 update:

  1. Click System Administrator > Nodes and synchronize the nodes.
  2. Remove the icec application from the cfg.py file located in the \connections folder, and then save and close the file: 
    
"icec": {
			"cluster": "ICCluster",
			"dbType": "DB2",
			"dbServer": "l3-conn7.swg.usma.ibm.com",
			"dbPort": 50000,
			"dbName": "XCC",
			"dbUser": "LCUSER",
			"dbPassword": "{xor}Dz4sLChvLTs=",
			"dbDriverPath": "C:/IBM/SQLLIB/java",
			"dbCustomProperties": {
			"resultSetHoldability": 1,
			"downgradeHoldCursorsUnderXa": "true"
			},
			#update#communities
			#remove#communities
			},
  3. Roll back the CR3 update.

    To roll back the update, start IBM® Installation Manager and select the Rollback option.

  4. Install the stand-alone Connections Engagement Center using the instructions in Installing and configuring Connections Engagement Center, using the same install.properties file that you used previously.

    You can only re-install the Engagement Center if you previously purchased it for use with Connections 6; you can optionally purchase it now.