IHS V8.5 does not resolve to jts, ccm, rm or qm.
In our environment, we are forced to use non well known ports for iHS. I have configured IHS ports as 8080 and SSL 8088.
The httpd.conf file is also correct for our environment. The plugin.xml file is correct for all our component systems, but IHS seems to refuse to use the plugin.xml file, but rather tries to look for it in htdocs. Example for the error_log file on IHS [Mon Feb 24 16:41:52 2014] [error] [client 10.162.58.112] File does not exist: /export/gcs1/data/opt/ibm/ihs/htdocs/ccm The net of this is what is necessary for configuring IHS to run on non well known ports so that IHS can connect to the component systems? |
One answer
If you get errors from IHS rather than from WAS, it means the traffic is not being forwarded to WAS, then the configuration of the IHS Plugin is not correct.
I did a quick test in my environment and managed to make it work without much trouble. Here are the steps. 1. Modify httpd.conf and change the ports. ......2. Observe the path to the plugin-cfg.xml in the httpd.conf file (normally at the bottom of it). LoadModule was_ap22_module /opt/IBM/WebSphere/Plugins/bin/64bits/mod_was_ap22_http.so3. Modify the plugin-cfg.xml file and change the ports to match that in the httpd.conf file. <VirtualHostGroup Name="default_host">4. Log on to the WAS profile admin console, navigate to the Environment > Virtual Hosts > default_host > Host Aliases, and change (or add) the ports so that they match to those defined in the plugin-cfg.xml Host Name Port5. Restart IHS and WAS. I believe you definitely missed step 4 but cannot imagine what might be wrong in the plugin-cfg.xml file. Edit to add: if you have already configured your CLM applications, remember to do a server rename after you change the ports. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.