IHS configuration - CLM Infrastructure Expansion
We are getting ready to add a second CCM application server to an existing environment.
This is not clustered or load balanced in any way - just a second server pointing back to a common JTS.
Background:
The idea is to simply add a new application server to the environment at a new URI of http://clm2.companyname.com/ccm and register it with the existing JTS server.
The existing infrastructure is at URIs like http://clm.companyname.com/[application] (e.g. http://clm.companyname.com/ccm, http://clm.companyname.com/rm, etc.)
Each of the existing applications is on it's own server with the URIs going through an IHS 7 reverse proxy.
The application servers are all WAS 7.
There are no VirtualHost entries in the infrastructure right now - the default rules for IHS all go through a global set of rules in a large plugin configuration file.
Our idea is to reuse the existing IHS reverse proxy and deal with the name resolution using a VirtualHost entry to manage the http://clm2.compoanyname.com/ccm, but we want to validate the approach first, if possible.
Questions:
1 - Can we add a VirtualHost _just for_ the new application server and generate a plugin config for it, without having to touch the existing global default rules?
2 - If not, do we have to move all of the existing default configurations into a VirtualHost block so that we have a VirtualHost block for each case (and basically nothing on the default)?
Obviously our preference would be the scenario in question 1 (ie - simply add a new exception to our default behavior), but we want a sanity check from the community in hopes of avoiding experimentation time.
Thoughts? Feedback?
Thanks!
|
One answer
Depending on where you want to add the "VirtualHost" - IHS or WAS. But I never care about this since I am not a system administrator myself, and I use "*" all the time to make things work. This is what I will do.
1. Add a DNS entry to resolve clm2.companyname.com to be the same IP address as clm.companyname.com, so that you can reuse the IHS server. 2. Add a new set of <VirtualHostGroup/>, <ServerCluster/>, <UriGroup/> and <Route/> in the existing plugin-cfg.xml file to direct the traffic to the new server. You can generate the template in the new WAS server and copy the content over after making necessary changes. So you should have something like this <VirtualHostGroup Name="clm">I can verify this in my own environment using the /Snoop application. |
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.