My NWTL Sessions – Verse On Premises

As part of Alan Hamilton’s NWTL (New Way To Learn) initiative, I have recorded sessions on Verse on Premises, the first on Installing and the second on integrating it with Connections. My installation session has been updated into this blog entry for VOP 1.0.1 which shipped today May 8th.  I am sharing that and  my second presentation which is on how to integrate Verse On Premises with IBM Connections.  In my example I use Connections 6 as the instructions are the same as for Connections 5.5 but that isn’t supported by IBM currently to YMMV.

To access all the NWTL sessions if you’re a Business Partner you can register here.  Thank you to Amanda Bauman for recording the session with me.

​ 

Integration Verse On Premises & Connections – Small Problem

This week I have been working on integrating Verse On Premises running on Domino 9.0.1 with IBM Connections.  Alright Connections 6 which isn’t supported right now.  The actual configuration is fairly simple and detailed on one page of IBM documentation.  It involves pasting some CORS redirection lines from the IBM document into your httpd.conf file and then replacing the server hostname with your own.

When I first did it against new servers the profiles integration worked fine but the Files (both accessing and uploading) as well as Follow/Unfollow actions failed.  That pointed fairly clearly to an issue with the OPTIONS request type and firebug confirmed that was throwing a 401 unauthorized error.  Finally I started to run out of ideas and asked Roberto Boccadaro if he could share his httpd.conf with me.  When I compared three separate environments the most glaring difference was with the SetEnvIf variable which is Step 5d on this page

SetEnvIf Origin “^https://(vop_server_hostname\.)?(domain_name)$” origin_is=$0

IBM’s instructions on that page tell us to use escape characters before each full stop so my variable setting would be

SetEnvIf Origin “^https://(mail\.)?(turtleweb\.com)$”origin_is=$0

However that was the problem.  The https:// caused the 401 error and I had to replace it with escaped forward slashes so my new URL is

SetEnvIf Origin “^https:\/\/(mail\.)?(turtleweb\.com)$”origin_is=$0

I applied that single change and everything immediately worked.

I have let the IBM documentation team know but if you have the same problem, check your SetEnvIf variable.