Updating HTTP server configuration for the proxy server

Every time when you automatically or manually regenerate or re-propagate the configuration file plugin-cfg.xml for Web Server, remember to update the HTTP server configuration of the proxy server.

Before you begin

If there are multiple IHS servers configured for load balance in the environment, make sure the WebSphere environment variable Environment > Websphere variables > IHS_FOR_DOCS_PROXY is empty.
If multiple IHS servers are managed in the cell, but only one is used for HCL Docs, make sure WebSphere environment variable Environment > Websphere variables > IHS_FOR_DOCS_PROXY is the name of the IHS sever host.
Verify the trust to web server, perform the following steps:
1. Open a web browser and navigate to the Integrated Solutions Console:
```
https://DocsLab01.renovations.com:9043/ibm/console
```
2. Navigate to Clusters > Proxy server clusters.
3. Click DocsProxyCluster.
4. Expand HTTP proxy server settings and click Proxy settings.
5. Under the security section, find the section Trusted security proxies. Make sure each IBM HTTP server’s host name and also the load balancer host name are in the list. Click New if you need additional fields.
```
Connections.renovations.com
        DocsLab01.renovations.com
        DocsLab02.renovations.com
```
6. After you have added the host names to the list, click OK.
7. Save the changes to the master configuration.
8. Synchronize all the nodes.
9. Log out of the Integrated Solutions console.
To ensure that the proxy server accepts requests for virtual hosts:
1. Click Environment > Virtual hosts.
2. On the virtual hosts page, select default_host and then click Host Aliases. Check whether the proxy server's listening ports, such as 80, 81, 443, 444, are on this list. If not, add the ports to the list.
  Note: You can get the proxy server ports by clicking Servers > Server Types > WebSphere proxy servers > {proxy_server_name} > Communications > Ports.

Procedure

By default, update_webserver.bat/.sh uses the cfg.properties file located in same folder. You can also point it to other cfg.properties files via -configFile. If you use multiple IHS servers, set the value of webserver_name to empty in cfg.properties. If not, set it as the name of the only IHS server that is used.
Run update_webserver.bat -acceptLicense (Windows) or update_webserver.sh -acceptLicense (Linux) that is located in the DocsProxyInstaller directory, for example, C:\IBM\ConnectionsDocs\DocsProxyInstaller\installer, or /opt/IBM/ConnectionsDocs/DocsProxyInstaller/installer.
To make sure the HTTP server is configured correctly, verify that you can get the version, for example:
- http://DocsLab01.renovations.com/docs/version, where DocsLab01.renovations.com is the IBM® HTTP Server for HCL Docs.
- http://DocsLab01.renovations.com/conversion/version, where DocsLab01.renovations.com is the IBM® HTTP server for the Conversion application.
- http://DocsLab01.renovations.com/viewer/version, where DocsLab01.renovations.com is the IBM® HTTP server for File Viewer.
For Proxy server, check the log file at: <SERVER_NAME>/logs/DocsProxyMember1/ and<WAS_ROOT>/AppServer/profiles/<SERVER_NAME>/logs/DocsProxy1/
After running update_webserver.bat/.sh successfully, do the following steps:
1. Check whether there are docs proxy cluster configured at the end of plugin-cfg.xml which is located in <IHS plugin root>/config/<webserver name>/plugin-cfg.xml, for example, IBMDocsProxyCluster is the name of docs proxy server cluster name.
2. When the deployment manager is installed on a machine that is remote from where the IHS server is installed, you might need to manually propagate plugin-cfg.xml. Find the new generated plugin-cfg.xml with HCL Docs proxy server configuration in <Dmgr root>/config/cells/<cell name>/nodes/<node name>/servers/<webserver name>/plugin-cfg.xml. Copy the plugin-cfg.xml file to the remote IHS server <IHS plugin root>/config/<webserver name>/plugin-cfg.xml. Restart IHS. You can refer to Restarting the IBM HTTP servers.