IBM Connections in combination with Chrome version 60


Update 17-08-17

IBM PMR update

“thank you very much for your update. It will be an ifix for IBM Connections but unfortunately we did not have any information about an ETA Date.
The priority is high as many customers reported this problem.

I will check the status for the defect and the technote for any update and keep you informed.”

TechNote -> http://www-01.ibm.com/support/docview.wss?uid=swg22007236&myns=swglotus&mynp=OCSSYGQH&mync=R&cm_sp=swglotus-_-OCSSYGQH-_-R

 


Since the update to Chrome version 60 we started to notice that some

of the functionality of IBM Connections breaks when using it with the Google browser.

Until so far we have found three items of IBM Connections which no longer work
with Chrome version 60.

  • Creating a Community event doesn’t work.
  • Content in the Events widget on the Homepage isn’t always displayed correctly.
    ( An error occurred while displaying content. Contact your system administrator. )
  • Placing a comment on status update in the ActivityStream doesn’t work.
    ( This goes for the ActivityStream on the Homepage and for
    the “Recent Updates” stream on a Profile page.
    When performing the same action in the popout window it works okay. )

We see that it happens with IBM Connections 5.0 CR4, 5.5 CR3 and with 6.0.

Related to these issues we raised two PMR’s. If you want to increase the weight of your
PMR’s you could refer to these two.

28607,211,788 – IBM Connections 5.5 – Chrome version > 60 Creating events.

28593,211,788 – IBM Connections 5.5 – Chrome 60 causes problems commenting in IBM Connections

Below some screenshots of the issues we see.

Creating a Community event doesn’t work

 

 

Content in the Events widget on the Homepage isn’t always displayed correctly.

Placing a comment on status update in the ActivityStream doesn’t work

 

 

Posted in ibm connections | Tagged , , , | 1 Comment

IBM Connections 6.0 – June update

Update Strategy for IBM Connections 6.0

http://www-01.ibm.com/support/docview.wss?uid=swg21999492

Updates for Orient Me ( Connections Pink ) , Connections Blue and the
Ephox TextBox.IO editor.

Ephox Editors for IBM Connections Version: 3.5.1.3

Update: The new version of Ephox Editors for IBM Connections Version: 3.5.1.3 which includes Textbox.io Version: 2.2.1.58 is now available. The Ephox editor can the found at Fix Central here

IBM Connections Orient Me June 2017 Update (Released June 27, 2017)

Fix Central download link for the IBM Connections Orient Me 2017 June Update (Orient Me 6.0.0.1)

IBM Connections 6.0 June 2017 Update iFix (Released June 27, 2017)

Fix Central download link for the IBM Connections 6.0 Required June 2017 Update iFix
(APAR LO92151)

Posted in ibm connections | Tagged , , , , | Leave a comment

WAS 8.5.5 FP10 – java.lang.ClassCastException: javax.management.ObjectName incompatible with javax.management.AttributeList

The WAS version that is comes with IBM Connections 6.0 suffers from the following bug.
Within the WAS console GUI you can’t add a administrative group. it will print out the following error message.

The following error will be logged in the SystemOut.log of the DMGR.

[6/23/17 10:21:31:222 CEST] 00000145 GroupDetailAc W   listRegistryGroups: Command not successful: java.lang.ClassCastException: javax.management.ObjectName incompatible with javax.management.AttributeList

The following technote describes this issue.

PI69518: GROUP SEARCH FAILS WITH A CLASSCAST EXCEPTION AFTER UPGRADE TO 8.5.5.10 –  http://www-01.ibm.com/support/docview.wss?uid=swg1PI69518

It is fixed for WAS 8.5.5.10 with iFix PI69518 or you have to upgrade to FP 11.
But for now Fixpack 11 isn’t supported for IBM Connections VI.

Download PI69518 from -> http://www-01.ibm.com/support/docview.wss?uid=swg24042833

 

Posted in ibm connections | Tagged , , , , | Leave a comment

Connections Pink – cleaning up the elasticsearch log files

When running the Connections Pink stack which is equipped with elasticsearch its log
directory can grow pretty big in a short period of time.

The log files from elasticsearch can be found on the master node under

/var/lib/elasticsearch/data/elasticsearch-default/

A quick fix to clean up some of these old logs is the following procedure.

Retrieve the containerId of the ibmcom/indices-cleaner:0.1 image.

Now run the following command to use conductor which exist inside the indices-cleaner
image to purge some of the old log files.

 

Posted in ibm connections | Tagged , , , , | Leave a comment

Deploy Connections iFixes in a cluster without downtime

Following the documentation of IBM regarding deploying iFixes on a Connections
environment they state that all of your Connections JVM’s should be stopped
during the upgrade process.

“But I have a cluster why can’t this be done online?”,
” Yeah but the IBM documentation says so.”

There you have your challenge. Not much downtime is caused by deploying a single iFix
but there is some chance on data loss. This because running the update installer with online JVM’s will cause an automatic restart of the EAR when they are being upgraded/modified. A restart of an EAR in a clustered environment is most likely to occur simultaneously and can result in HTTP 500 errors for the end user.

Below the steps that work for me to perform an iFix deployment online. It is not a scenario supported by IBM but it can help in improving the process speed of deploying that little iFix that is so desperately needed by a set of end-users. Maybe giving you some ammunition to cut some corners at the CAB meeting.

In this made up example I need to deploy an iFix for Files ( LO66666 ).

Steps:

  • In order to prevent the updateInstaller of Connections from modifying the second node we need to shutdown the nodeagent for this node. Navigate to the WAS console. In the WAS console go to System Administration -> Node agents.
  • Select the node agent of the second node and press stop.
    Tail the SystemOut.log of the nodeagent to check if the nodeagent indeed is stopped.
  • Now logon to the IHS webserver.
  • Open httpd.conf on the webserver. Locate the plugin-cfg.xml line.
  • Open the plugin-cfg.xml, and save a copy of it with another name
    ( i.e. plugin-cfg-primary2ndnode.xml )

 

  • Within this file locate all the ServerCluster sections. For a medium Connections deployment you should find four sections.This example works with a cluster setup consisting of two nodes. One is marked as primary and one is marked as backup. We want to temporarily redirect all traffic primarily to the second node.To do so replace the server line in the BackupServers section with the one of the PrimaryServers section and vice versa.Note the customized CloneID’s. This helps you to verify on which JVM’s you are working. These CloneID’s are mentioned in the JSESSIONID cookie value. Later more about this.
  • Save the changes.
  • Now navigate back to the httpd.conf. Replace the WebSpherePluginConfig with a line pointing to the modified one.

  • Restart the IHS webserver to make this change effective.
  • Now check with a browser that your new Connections session is really being redirect to the correct node. Press F12 and drill down to a cookie information screen
    for one of the requested URL’s. The last part of the JSESSIONID should mention the CloneID’s of the second server.( The screenshot below shows a session to JVM’s on the primary server: infra_srv1 and apps_srv1. )
  • Now go ahead and run the updateInstaller on the DMGR.
    updateSilent.bat -fix -installDir D:\IBM\Connections -fixDir D:\IBM\Connections\updateInstaller\Fixes -install -fixes LO66666 -wasUserId wasadmin -wasPassword ******* -featureCustomizationBackedUp yes
  • Wait for the installer to finish. To make sure the primary node is fully in sync perform
    a full sync from the WAS console interface.
  • Now stop the AppsCluster_server1 ( hosting the Files application ) on the primary node. Now clear all AppsCluster_server1 temp files under
    app_server_root/profiles/AppSrv01/temp/AppsCluster_server1
    and start the AppsCluster_server1 JVM again.
  • Now back to the IHS webserver and switch back to the httpd.conf. Make the original
    plugin-cfg.xml active again and restart the IHS webserver.
    Verify if the traffic routed to the primary server again.
  • Now to also make this change effective for the secondary node start the nodeagent.
    Make sure that all changes are synced if not entirely sure just perform a full sync to
    this server from within the WAS console.
  • Now perform the same procedure as for the primary node. Stop the AppsCluster_server2 JVM, clean all temp files and start the JVM again.
  • And you’re done.
Posted in ibm connections | Tagged , , , , | Leave a comment

IBM Connections Desktop Plugin 17.01 without server OS check

Version 17.01 of the IC Desktop Plugin without server OS check. Download here.

For background information see -> http://www.ibmconnections.org/wordpress/index.php/2014/10/run-the-ibm-connections-desktop-plug-in-on-windows-server/

Posted in ibm connections | Tagged , , , | Leave a comment

Sametime Community configure HTTP tunneling + push settings

Per default Sametime will listen on port 1533. As some network infrastructures will
not allow outgoing connections on this port, as an alternative you can specify to
use the HTTP port 80. This technique is called HTTP tunneling.

To configure your Domino/Sametime Community setup for this you can
follow the steps in the Blog item.

With your Notes client open the names.nsf on your Sametime Community server. Navigate to Configuration -> Servers -> “All server documents” and double click on the entry of the Sametime Community server

Within this document go to Ports ->Internet Ports -> Web.

ports 1

 

ports 2

 

 

 

 

 

 

 

Change the TPC/IP port number to something different then port 80. We will
go with port 8080.

Save the changes and restart the http task.

In the Domino console use the following commands to do this.

tell http quit

load http

Change the connection for the Sametime Community server in the SSC. Per default the SSC will make contact to the Sametime server through the Domino HTTP port.

As this changes you will need to change this connection setting in the SSC.

Navigate to the Community server.

ssc1

 

 

 

Click edit “Connection Properties”

ssc2

Change the HTTP port to the value you now configured as the HTTP port for Domino.
In our situation this is port 8080. Press Save.

ssc3

 

 

 

Now click on the “Deployment Identifier” link.

The configuration page of the Community server should open without any errors.

ssc4

 

 

 

 

Scroll down to the “HTTP Tunneled Client Connections” section on the Connectivity tab.

ssc5

 

 

 

 

 

Set the port to 80. Now press OK at the bottom of the page to save the changes.

Now switch back to the Domino console and restart the Sametime Community server.

res server

Now with “managed-settings.xml” and “managed-community-configs.xml” you can
push these setting to the clients. Pushing settings to Sametime clients with these files
is the preferred way to go. Working with Domino policies is far from predictable.

Follow these steps to configure the location from where to provide these two XML files.

Within the SSC menu on the left side go to “Manage policies”

policy1

 

 

 

 

policy 2
Click Edit for the “Sametime Instant Messaging Default Policy”.

policy 3

 

 

 

Find the “Sametime update site URL (IC):” entry.

We use the FQDN of the Sametime Community server + the update directory.

policy 4

 

 

On filesystem level on the Community server you should create this update
directory under /local/notesdata/domino/html/

When done press OK at the bottom of the page.

For initially setting the correct port you can configure the following settings in the
managed-settings.xml file.

<?xml version=”1.0″ encoding=”UTF-8″?>
<ManagedSettings>

>>SNIP<<

 

<settingGroup name=”com.ibm.collaboration.realtime.community”>
<setting name=”loginByToken” value=”true” isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”loginAtStartup” value=”true” isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”useCanonicalNamesOverride” value=”1″ isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”name” value=”sametime.acmecorp.org” isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”host” value=”sametime.acmecorp.org” isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”port” value=”80″ isLocked=”false” overwriteUnlocked=”true”/>

</settingGroup>

 

>>SNIP<<

</ManagedSettings>

For updating existing server communities you can use the following section
in the managed-community-configs.xml file.

<?xml version=”1.0″ encoding=”utf-8″?>
<managed-communities>

>>SNIP<<

<managed-community id=”sametime.e-office.com” host=”sametime.acmecorp.org” port=”80″/>
<managed-community-action type=”update” managed-community-id=”sametime.acmecorp.org”/>

>>SNIP<<

</managed-communities>

A complete list of configurable options can be found here

The settings should work for the stand-alone Sametime Connect client
and the embedded version within IBM Notes.

Shutdown your Sametime Connect client and start it again.
The server community port should now be listed as 80.

Posted in sametime | Tagged , , , | Leave a comment

IBM Connections Desktop Plugin 16.10 without server OS check

Version 16.10 of the IC Desktop Plugin without server OS check. Download here.

For background information see -> http://www.ibmconnections.org/wordpress/index.php/2014/10/run-the-ibm-connections-desktop-plug-in-on-windows-server/

Posted in Uncategorized | 1 Comment

55-CR1-homepage-db2.sql – 705 vs. 704

If you were one of the early birds deploying Connections 5.5 and you used the
Connections SQL files from the initial supplied Wizard tools then applying CR1 will fail.

The 55-CR1-homepage-db2 SQL script checks on DBSCHEMAVER 705. This is the version used within the Connections SQL files from the Day1Fix Wizard tools.
The “old” scripts use version 704 for the DBSCHEMAVER column.

UPDATE  HOMEPAGE.HOMEPAGE_SCHEMA SET DBSCHEMAVER = 706, RELEASEVER = '5.5.0.0 CR1'
WHERE   DBSCHEMAVER = 705@

Change the 55-CR1-homepage-db2 SQL script upfront befor applying or make the change after in the HOMEPAGE.HOMEPAGE_SCHEMA table.

.Wizards\connections.sql\homepage\db2\createDb.sql

--------------------------------------
-- INSERT THE SCHEMA VERSION
--------------------------------------
INSERT INTO HOMEPAGE.HOMEPAGE_SCHEMA (COMPKEY, DBSCHEMAVER, RELEASEVER) 
VALUES ('HOMEPAGE', 704, '5.5.0.0')@

.\Wizards_IC55day1fix\connections.sql\homepage\db2\createDb.sql

--------------------------------------
-- INSERT THE SCHEMA VERSION
--------------------------------------
INSERT INTO HOMEPAGE.HOMEPAGE_SCHEMA (COMPKEY, DBSCHEMAVER, RELEASEVER) 
VALUES ('HOMEPAGE', 705, '5.5.0.0')@

 

 

Posted in ibm connections | Tagged , , , | Leave a comment

Customize the new Hikari theme in IBM Connections 5.5

With IBM Connections version 5.5 a new default theme was introduced, the
Hikari theme. In order to customize this new theme new directory paths are
required. You can find the source sprite files ( images ) and the CSS files of this
theme in the following location.

D:\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\ACMECORPCell01\Common.ear\connections.web.resources.war\WEB-INF\eclipse\plugins

Now open the following JAR file. ( Running IC55 CR1 )

com.ibm.social.hikari.theme_1.0.0.20160515-0614.jar

Under \resources\sprite you can find the images used within this theme.

com.ibm.social.hikari.theme_1.0.0.20160515-0614.jar\resources\sprite
WinrarSpriteFolderHikariTheme

 

Place customized versions of these images under the CONNECTION_CUSTOMIZATION_PATH. Find the current customization path in the WAS console under Environment -> WebSphere variables.

For example, CONNECTIONS_CUSTOMIZATION_PATH  =
\\\\fs01.ACMECORP.net\\connections55\\customization

Additions and customization’s for the Hikari theme style-sheet needs to be placed under
the following path in a file with the name custom.css.

\\fs01.acmecorp.net\\connections55\customization\themes\HikariTheme

Custom sprites used by the Hikari theme need to be placed in the below mentioned directory. You can just create a copy of an existing sprite file and make adjustments to it, use other colors or create complete new icons.

\\fs01.acmecorp.net\connections55\customization\javascript\com\ibm\social\hikari\theme\sprite

This way you can easily re-style the images used for the Apps menu or the Mail & Calendar icons as used by Connections Mail.

HikariThemeCustomizedMailIcons

IC55 Hikari theme custom mail icons

HikariThemeCustomizedAppsIcons

IC55 Hikari theme custom Apps icons

 

 

 

The caching mechanism of Connections can be very persistent. When activating new
theme changes for Connections I always go for removing all the temp files of the
WAS IC nodes. So stopping all JVM’s, removing everything under AppSrv01/temp and
starting all JVM’s again. Then in the browser go for a CTRL + F5 to see the theme changes.

A strange phenomenon in the combination of Connections 5.5, Connections Mail 1.7 and Windows servers is that temp files are created in directory paths which are longer than the supported length of Windows. ( running Windows 2012R2 )

Whenever you try to remove the Common temp folder you will get this prompt.

WindowsConnectionsMailtempfiles

 

 

 

 

 
Whenever you try to browse to certain directories you will notice that the path
gets so long that you will not be able to open the underlying directories anymore.

For example:

D:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\NLDELCONN98Node01\InfraCluster_server1\Common\connections.web.resources.war\eclipse\workspace\.metadata\.plugins\com.ibm.servlets.amd.dojo.1.9.resources\__build-version__\domjs\dojo_trunk\131.20160119-0324

In order to delete these temp files you will need to make the full path length smaller.
So in case of the path as mentioned  above rename some of the directories to a
single character.

AppSrv01\temp\NLDELCONN98Node01\1\2\2\eclipse\

 

 

Posted in ibm connections | Tagged , , , , , | Leave a comment