Hello Shekhar,
First of all, I don't think it is a good idea to use Apache as a load balance when you move to production as it doesn't have any essential capabilities(HA/ load based routing is poor, administration is tedious) of a commercial LTM.
To use Apache as a load balancer, you have two options use http based load balancing or mod_jk based.
http based - You can google and find a lot of how to s on http based load balancer using the proxy feature of Apache.
mod_jk based load balancing - This is in fact used in windchill, when you have multiple method servers in a monolithic environment, apache load balances multiple request using mod_jk to embedded tomcats in method servers. When you have a cluster what you have to do is define load balancing workers on different hosts and define routes. This is detailed in 10.1 advanced deployment guide and in https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS40808
I don't think you can run PSI and convert an existing install to cluster, it is used when you have are doing a new install. Anyhow, the PSI doesn't do anything other than providing additional wt.properties specific to master and slaves. To configure cluster, you will still have to copy the load points - JDK, Apache and Windchill and so on to all the members. So the best option for you is to copy the load points to slave hosts and reconfigure the properties wt.cache.master.codebase, wt.cache.master.hostname, wt.cache.master.slaveHosts and so on. The example detailed in advanced deployment guide is good to easy to follow. Ensure that you have a commonly accessible storage for vaults as well. Since you are in 10.2, do configure the dynamic cache master which would help you get past the single master - SPOF
Thank you,
Binesh Kumar
Barry Wehmiller
