Customizer Routing

HCL Connections Connections Forum
,
1

We like to enable the customizer in our environment. There is this official documentation about the options how to setup the Customizer: https://help.hcltechsw.com/connections/v7/admin/install/cp_config_customizer_setup_nginx.html

To keep it simple we plan is to install the NGINX on the same servers like IBM HTTP Servers. So NGINX would listen on port 443/80 while we reconfigure the IBM HTTP Server to listen on 444/81.

Within this topology I expect we do not have to reconfigure any DNS entries and even there is no side effect to SPNEGO.

So the incoming HTTP requests are forwarded to the Customizer. But the documentation does not mention how the traffic is routed from Customizer to IBM HTTP Server. Do I just have to change the entries in connections-env.yml and change the port from 443 to 444?

ic:
host: connections.cust.com
internal: connections.cust.com
interserviceOpengraphPort: 443
interserviceConnectionsPort: 443
interserviceScheme: https

I guess with this topology there is no need to use dynamicHosts in lcc.xml There is just the consideration how to handle Interservice traffic.

2

Hi Karl,

you can configure that this way, but I had some issue with port changes on IHS.

I would map nginx on the host ip 443/80 and IHS on 127.0.0.1 443/80

Regards

Christoph

3

hm, if IHS is just listening on 127.0.0.1 then I guess you route everything wich is dealing with the FQDN of Connections via NGINX. And from there either it's routed to Customizer or directly local to 127.0.0.1 (IHS).

Or is there anything else to consider?

4

To be honest I do the same with Apache 2.4 in front of IHS. I tried the approach with Nginx on the IHS server in one environment and moved away from it.

As I think again about this, you won't have a route from Customizer to IHS. You can use different hostnames to get this route back. I can remember we started with different ports for IHS and Nginx, but afaik there were issues. So please ignore my first comment.