How do I create an Apache virtual host when using a SiteMinder Agent?

Discussion created by masvi10 Employee on Jun 5, 2012
Latest reply on Oct 10, 2013 by SungHoon_Kim

Tuesday Tip by Peter Caliri, Senior Support Engineer, for 6-5-12

How do I create an Apache virtual host when using a SiteMinder Agent?

What is the use and/or the benefit of using a virtual host?

Using an Apache Virtual Host, you can run several websites on the same apache instance utilizing the same apache binary. For example, you can run both and on a single physical server that has one Apache webserver running on it. This can be easier to manage with apache, SiteMinder (e.g. upgrade a single agent) and use fewer resources.

We will discuss Name-Based Virtual Host.

In this configuration, when Apache webserver receives a request, it looks for the hostname in the HTTP header, and depending on the hostname, it servers different websites. This is very easy, as you need only one ip-address on that physical server; but, you update the DNS with multiple website names pointing to the same ip-address. For all practical purpose, you’ll be using only Name-based virtual host configuration.

In the following example, the server can contain only one NIC card, which is configured with ip-address. The DNS entry for both and websites point to the ip-address. When Apache receives a request, it looks for the hostname entry in the HTTP header, and serves the corresponding website.

1.) Create the virtual Host

DocumentRoot /www/docs/

2.) After this is done, the WebAgent.conf for the Apache server needs to be edited. This file needs to be edited in order to create another agent identity for the virtual server to be protected by SiteMinder.


In your ACO (Agent Configuration Object) on the Policy Server, you can have “apache” defined for the “defaultagentname”. (

3.) In the SiteMinder Policy Server User Interface, create a new Agent for the new agent identity “apache2”. The IP addresses and Agent Name must be the identical with what is specified in the WebAgent.conf and httpd.conf.

4.) The virtual server that needs to be protected by SiteMinder, a new realm should be created.

5.) Start/Stop the web server for the changes to take effect.