Verse is integrated with Connections Docs and failing to preview an attachment

HCL Connections Connections Forum
,
1

Hello,

I have integrated Connections & Verse including Docs.
Connections-related functions (e.g. transfer files from Verse to Connections) are working fine.
File preview inside Verse does not work - "service not available".

The browser console prints "Fail to transfer attachment to Docs Viewer: 404" but all network-related packages are in state/HTTP code "200".
No errors are printed inside the Websphere logs for these nodes at that time.

Any ideas what could cause this issue ? Did you experience something equal with the integration ?

I have several working envoirnments with Docs 2.0 CR3 - this is the first 2.0.1 envoirnment. Since Docs 2.0.1 has few other bugs may this only be a another product bug ? Could anybody at least confirm that Docs<->Verse works for 2.0.1 ?

Thanks in advance !
Regards,
Jan

2

Hello Jan,

I've had a case where customer was getting the 404 issue to preview files from Verse.

Please review the viewer-config.json and have sure the WhiteDomainList is correct.

Integrating with IBM Docs
https://help.hcltechsw.com/verse_onprem/1.0.5/admin/topics/vop_integrating_docs.html

- according to it, in order to have the integration working fine the customer needs to do/check these points:

1 >> Enable CORS on IBM Docs to allow cross origin requests. Verse On-Premises use IBM Docs JavaScript API to communicate with IBM Docs. To enable CORS access, the Domino server's domain name must be added into the WhiteDomainList of IBM Docs. For more information, see the IBM Docs JavaScript API in the IBM Docs documentation. Verse On-Premises communicates with IBM Docs' Viewer component. So in addition to concord-config.json, WhiteDomainList field inside viewer-config.json also needs to be updated.

Example:
"WhiteDomainList": ["https://mail.ibm.com"],
"IHS_fast_download": {
"cache_root_alias": "/rendition_content",
"enabled": "false"
},


Thank you
Marcos Vinicius

3

Thanks for the quick reply.

I have followed official documentation as mentioned in your reply - I can confirm that WhiteDomainList is set. I am running the same configuration for 2.0 CR3 envoirnment & 2.0.1 envoirnment - but only 2.0.1 has the problems.

4

Hi Jan,

Did you make sure that the whitelist entry is in both the concord-config.json and also the viewer-config.json? I had the same issue as you this was even an upgrade the same as yours and I found I had the entry in the concord config but not the viewer config so I changed the entry in the dmgr profile IBMDOCSConfig folder sync the nodes and then restarted and this then worked.

If that doesn't work the only other things could be either the httpd.conf or this is in the Domino servers ini file iNotes_WA_Security_NonceCheck=0

5

Hello Richard,

I have checked your mentioned points but sadly they do not apply / values are set correctly.

@others: I would appreciate any ideas to solve this issue since HCL seems to be struggling with this one here. My case is still open.

Regards,
Jan

6

Did you get it solved? I have the exact same issue after our docs var updated to 2.0.1

7

@Kenneth Holmqvist I had 2 big issues last year with this integration. Cause A: TLS certificate of Verse server did not match the URL that was used for integrating Verse<->Connections.(certificate only valid for "mail.company.com" but integration was done for fqdn "webmail.company.com"). I think this was the case here. Cause B: SSO between Verse & Connections was not configured correctly. Hope this helps ! Or is the problem already solved ?

Regards,
Jan

8

Hi Jan,

Yes i got it solved. My issue was a expired certificate