OAuth2 error in Activity stream popout

I’ve just finished with installing IBM Docs; an install post will follow shortly.

Users were reporting issues of the Activity stream popout failing with “An error has occurred”

Selecting more details, reveals the following.

000002a7 BasicOAuth2Re W BasicOAuth2Request exception
at java.util.zip.InflaterInputStream.<init>(InflaterInputStream.java:77)
at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:65)
at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:76)

I then backtraced the changes we had made. As the issue referred to GZIP, I thought of compression and what changes I’d made in the installation of Docs.

One step of this installation is to modify the httpd.conf file on the IBM HTTP Server to enable compression for various data streams. This is done by invoking the mod_deflate directive.

The main winners when this form of compression is enabled is the end user on a low bandwidth connection. Users on a local LAN the benefits aren’t as drastic, but it’s still a good idea.

For example, text can be compressed by up to 70%. That baeing said, some types of data don’t lend well to compression, i.e jpg, pdf, etc.

Read here for IBM’s technote on enabling mod_deflate.

Anyway, back to my error.  I had added the following  changes to our httpd.conf file as part of the docs install. Please note these are all commented out.

#AddOutputFilterByType DEFLATE application/atom+xml 
  #AddOutputFilterByType DEFLATE application/atomcat+xml 
  #AddOutputFilterByType DEFLATE application/javascript 
  #AddOutputFilterByType DEFLATE application/json 
  #AddOutputFilterByType DEFLATE application/octet-stream 
  #AddOutputFilterByType DEFLATE application/xhtml+xml 
  #AddOutputFilterByType DEFLATE text/css 
  #AddOutputFilterByType DEFLATE text/plain 
  #AddOutputFilterByType DEFLATE text/xml 
  #AddOutputFilterByType DEFLATE text/xsl

By a method of deduction, we worked out that the “application/octet-stream” was the culprit for killing the Activity stream popout. We’ve disabled this entry, and all works again.

Hope this saves someone half a day of stuffing around!

Updating Connections 5 WAS to

Connections 5 runs on WebSphere Application Server 8.5.x.

We recently deployed on the release, but as part of keeping the WAS stack as up to date as possible, I updated to the recent release We were experiencing an error that is resolved in the update.

Details on this fix are located here

Just to save time, if you are going to do the same, uninstall fix IFP119108, or you’ll get the error below when you go to update using IIM.


Hope this saves time for someone out there.

EDIT…It appears that IBM have decided not to support Connections on this version of WAS.

So if you need to update to resolve an issue in the WAS stack, beware…

Updating a user’s personal library quota in Connections Files

I get asked quite a bit on how to do some routine things in Customers environments. You’d think the simple task of increasing a users File quota would be pretty straight forward. Unfortunately, it’s more complex and convoluted then it should be. I can only hope the upcoming versions of Connections start integrating the great Administration tools that are available from BP’s out there into the Core product.

Overview of the process 

  1. Create a policy – refer to this blog on how to create a policy.
  2. Find the user
  3. Find the library belonging to the user
  4. Apply the policy to the Library

Start up wsadmin on the Deployment manager

D:\>cd IBM\WebSphere\AppServer\profiles\Dmgr01\bin
D:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin>wsadmin.bat -lang jython -user <connectionsadminuser> -password <connectionsadminuserpassword>-port 8879
WASX7209I: Connected to process “dmgr” on node CellManager01 using SOAP connector; The type of process is: DeploymentManager
WASX7031I: For help, enter: “print Help.help()”

Start Files Administration, and connect to a node
1: WebSphere:name=FilesSchedulerMBean,process=Cluster2_server1,platform=dynamicproxy,node=Node01,version=,type=LotusConnections,mbeanIdentifier=FilesSchedulerMBean,cell=Cell01,spec=1.0
2: WebSphere:name=FilesSchedulerMBean,process=Cluster2_server2,platform=dynamicproxy,node=Node01,version=,type=LotusConnections,mbeanIdentifier=FilesSchedulerMBean,cell=Cell01,spec=1.0
Which service do you want to connect to?

Connecting to WebSphere:name=FilesAdminService,type=LotusConnections,cell=Cell01,node=Node01,*
Files Administration initialized.

Find the users ID, notated below in bold by using their email address.
{directoryGroupLastUpdate=Tue Sep 09 12:48:02 EST 2014, lastVisit=Tue Sep 09 12:46:01 EST 2014, communityLastUpdate=Tue Sep 09 12:48:02 EST 2014, createDate=Thu Jul 04 16:50:43 EST
2013, id=97ea886e-fa34-415f-9883-2658af528bb6, name=User Who, email=userwhoneedsmorespace@blah.com, directoryLastUpdate=Tue Sep 09 12:46:01 EST 2014, isOprhan=false}

Take note of the value in “id=” . This is the internal representation of the user in the Files Application.

In this case it is  “id=97ea886e-fa34-415f-9883-2658af528bb6″

Use the ID, and find the users Library ID

{maximumSize=524288000, size=524174032, percentUsed=0.9997826232910156, summary=, createDate=Thu Jul 04 16:50:43 EST 2013, policyId=00000000-0000-0000-0000-000000000000, externalContainerId=null, themeName=, label=036841EC-8E19-4118-986A-B55B53BA663A, title=User Who, ownerUserId=97ea886e-fa34-415f-9883-2658af528bb6, type=personal, id=021b4d54-c47a-41ca-97d3-46b301b3bc34, externalInstanceId=null, lastUpdate=Thu Jul 04 16:50:43 EST 2013}

Note that some pretty interesting information is displayed, i.e Policy currently applied “policyId”, Current percent used “percentUsed” etc. The bit we are interested in is the id of the Library, which in this case is “id=021b4d54-c47a-41ca-97d3-46b301b3bc34″.

Assign the policy to the Library

I had already created a policy for 1GB, and taken note of it’s ID. For completeness, it was “d60abd07-5d86-45b3-8500-20ce95596bd5”

Syntax of the command is FilesLibraryService.assignPolicy(“LibraryID”,”PolicyID”)


If complete, you’ll get a confirmation, like below.
The policy with the id d60abd07-5d86-45b3-8500-20ce95596bd5 is now assigned to the library with the id 021b4d54-c47a-41ca-97d3-46b301b3bc34″)