Hi
We have gone through the setup of Component pack (all the kubernetes /server install/NGINX) and are now testing that normal Connections functionality is in place before proceeding to configure the different components.
But we see some strange errors in Connections, i.e if people open a bookmark that point to a Community it opens, but doesn't load the widgets correctly, as in they don't show any data. But if the user opens the same community directly from Connections without using a bookmark it works fine. The difference I see it that when opened from the bookmark, the browser url stays like this .... connections.nxxxx.com but when opened directly from Connections it says connectionsproxy.nxxxx.com as in it opens through the NGINX proxy.... it seems like when opened with a bookmark that points to connections.nxxx it doesn't get that changed to connectionsproxy.nxxxxx.com ...
We also see problems with ICEC/XCC where navigation doesn't work. And as you may know the navigation relies on links saved in wiki pages, so again it seems to be an issue with the proxy server ...
We have been through the settings we can think of but have not really found anything that seems to work, so if anyone out there has an idea it would be very much appreciated :-)
As always thanks in advance
Anders
Hi.
I think you have a fundamental thinking error.
There can be only 1 URL in which Connections works correctly.
You should check the Browser Debug tools to see if resources get loaded from different locations (connections and connectionsproxy).
Your official Connections URL should point either to the WebSphere IHS or to the NGINX Proxy.
When you want to go through NGINX, your official Connections URL must point to the NGINX Proxy.
To force WebSphere to calculate the right URL, use the dynamic host configuration in the LC-config.xml.
Of course, you need to rename your Websphere IHS Server to something different (e.g. connections-backend) and configure your services in the LC-config.xml and your IHS Server to use this new URL.
This is the process I describe in may page (Configure your Network): https://becketalservices.github.io/beas-cnx-cloud/AWS/chapter4.html
I have no idea where exactly HCL describes the process in full detail. The dynamic host configuration is mentioned in the official HCL Help page: https://help.hcltechsw.com/connections/v7/admin/install/cp_config_customizer_setup_nginx.html
Hope this helps.
Martin
Hi Martin
Thanks a lot for your valuable input. I must admit we were somewhat confused in regards to how much of the traffic that must come through the NGINX when we have chosen the Standalone install of the proxy. So we have missed the step of renaming the current IHS and pointing the existing connections url to the proxy. We did the configuration of the dynamic host, but having missed the other step that didnt really do it :-)
We'll use your documentation to redo the missed steps and see if that doesn't fix things.
Thanks