Hi Anurag
The answer from SungHoon_Kim is probably the solution that will solve the exact issue you have.
But I just wanted to clarify Sharana 's answer above. There are a number of ways that Ag/SPS can be used to support local content. SPS is after all based on apache and tomcat,
For example static content can be placed directly on SPS and served from apache (just need to add httpd/htdocs/ and add a JkIgnore rule in httpd.conf). This is used to optimize requests for common frequently used and static content in a number of clients - the normal webagent login.fcc uses this method for its static content.
You can deploy .fcc pages, which are served from the webagent engine in proxy-engine/tomcat.
In the odd rare circumstance, we've deployed a webapp into the tomcat engine to deliver a login.jsp page, and that worked fine as well.
Another common method was for SPS to forward to an IIS server running on the same machine, although obviously on a different port.
From a supportability perspective, you are allowed to customize the install, there are many modules in the apache, and many ways to add code such as sps filters into tomcat. In fact a lot of these custom deployments come about via some CA Services engagement. So although we can't promise to support the customized code or every feature in vanilla apache, we can usually provide some assistance if something isn't working, even if it is to say the feature is disabled or not working as per the standard apache distribution.
Cheers - Mark
----
Mark O'Donohue
Snr Principal Support Engineer - Global Customer Success