HomeDocumentation > Configuring and administering > Configuring and administering the Apache Geronimo Server > Configuring the Web Container > Configuring virtual host > Configuring Virtual Host in Tomcat

This article shows how to configure Virtual Hosts in Apache Geronimo with Tomcat. By default, when you deploy and start an application in Geronimo, that application will be listening on every available host name. By configuring a virtual host you can make an application listen on a specific host name or IP. The configuration steps described in this article are also valid when you are sharing a single IP among several host names.
To configure a virtual host in Geronimo you basically need to:

This article used the simple HelloWorld application as a reference, this application is covered in the Quick start - Apache Geronimo for the impatient section.

Configure local host or DNS

To make this configuration work you need to ensure that Geronimo can resolve the virtual host name you are about to define. Depending on your network configuration you can add an entry to you DNS, an alias to the Geronimo server IP. Alternatively you can add an entry to the local host table, each operating system has its own way to define a local host table. For example Windows will have %SystemRoot%\system32\drivers\etc\hosts, UNIX based operating systems would normally have an /etc/hosts.

For this example we will be using the following host names defined in the local host table:

127.0.0.1 localhost virtualhost1.com virtualhost2.com virtualhost3.com virtualhost4.com

Make sure your system can resolve these names.

Define Virtual host

Now you need to define those virtual hosts in Geronimo's config.xml so that Geronimo can recognize them. This section provides two different virtual host definitions, that is creating two new HostGBean ( TomcatVirtualHost1 and TomcatVirtualHost2 ) in the Geronimo configuration, one of which will have multiple host names aliases. The goal of this example is to have an application listening on a single virtual host ( this will be virtualhost1.com ) and another application listening on a different virtual host ( this will be virtualhost2.com ) with two additional aliases ( this will be virtualhost3.com and virtualhost4.com ).

Open the config.xml file located in the <geronimo_home>/var directory and look for the following line <module name="org.apache.geronimo.configs/tomcat6/2.2/car">. This is the beginning of the Tomcat configuration module. All the additional virtual host configuration will be done immediately after this line.

To define the first HostGBean TomcatVirtualHost_1 add the following lines right after <module name="org.apache.geronimo.configs/tomcat6/2.2/car">.

Excerpt from config.xml

To add the second HostGBean TomcatVirtualHost_2 add the following lines right after the first HostGBean. These two HostGBeans have been split so it is easier to identify them. The main difference between these two is the <attribute name="aliases">..,..</attribute> line to define the aliases.

Excerpt from config.xml

At this point you have successfully configured two different virtual hosts in Geronimo. Make sure you save the changes to the config.xml file and start Geronimo.

For additional reference, this is an excerpt from config.xml of the entire <module name="org.apache.geronimo.configs/tomcat6/2.2/car"> entry with the two HostGBean already defined.

config.xml

Note: Some tags in the config.xml shown above are presented in multiple lines for displaying purposes only.

Declare the virtual host in the deployment plan

As mentioned before, for this example we are using the HelloWorld sample application covered in the Quick start - Apache Geronimo for the impatient section. Since this is a Web application, the deployment plan that we are modifying is the geronimo-web.xml. If you use a different type of application you may need to modify a different deployment plan, for example geronimo-application.xml.

In the previous section we defined two Virtual Hosts, now we will be configuring two applications so they can be deployed to those Virtual Hosts exclusively.

We will use the same application in both cases but will differentiate one deployment from the other by giving it a different artifactId, this way we avoid modifying the code but still can identify each deployment.

Assuming you followed the steps covered in the Quick start - Apache Geronimo for the impatient section you should have the following structure:

<APP_HOME>\
          + HelloWorld.jsp
          + WEB-INF\
                    + geronimo-web.xml
                    + web.xml

Open the geronimo-web.xml file and edit the artifactId and context-root to make this deployment unique. Within the <web-app> section add the host attribute and specify the Virtual Host you want this application to listen on, in this case virtualhost1.com.

geronimo-web.xml for HelloWorld_1

Save the changed to the geronimo-web.xml file and generate a WAR file by typing the following command from the <APP_HOME> directory:

jar -cvf HelloWorld_1.war *

Once deployed this application should only listed in the virtualhost1.com host name.

We will now repeat this steps to create a second WAR. Edit once again the geronimo-web.xml file and copy the content form the following example. Note that we are only changing the <artifactId>, <context-root> and <host>.

geronimo-web.xml for HelloWorld_2

Save the changed to the geronimo-web.xml file and generate a second WAR file by typing the following command from the <APP_HOME> directory:

*jar -cvf HelloWorld_2.war* *

You now have two applications ready to be deployed to two different virtual hosts.

Deploy the application

At this point you have configured Geronimo to use two different Virtual Hosts, one of them is also configured to listen under additional aliases. All you need to do now is to deploy the applications and test them. To deploy the applications type the following commands from the <GERONIMO_HOME>\bin directory:

deploy --user system --password manager deploy <APP_HOME>\HelloWorld_1.war

You should get a successful confirmation message similar to this one:

D:\geronimo-tomcat6-jee5-2.2\bin>deploy --user system --password manager deploy \HelloWorld_2.2\HelloWorld_1.war
Using GERONIMO_BASE:   D:\geronimo-tomcat6-jee5-2.2
Using GERONIMO_HOME:   D:\geronimo-tomcat6-jee5-2.2
Using GERONIMO_TMPDIR: var\temp
Using JRE_HOME:        C:\Java\jdk1.5.0_06\jre
    Deployed sample.applications/HelloWorldApp_1/2.2/war @/hello_1

Repeat the deployment for the second application.

deploy --user system --password manager deploy <APP_HOME>\HelloWorld_2.war

You should get a successful confirmation message similar to this one:

D:\geronimo-tomcat6-jee5-2.2\bin>deploy --user system --password manager deploy \HelloWorld_2.2\HelloWorld_2.war
Using GERONIMO_BASE:   D:\geronimo-tomcat6-jee5-2.2
Using GERONIMO_HOME:   D:\geronimo-tomcat6-jee5-2.2
Using GERONIMO_TMPDIR: var\temp
Using JRE_HOME:        C:\Java\jdk1.5.0_06\jre
    Deployed sample.applications/HelloWorldApp_2/2.2/war @/hello_2

With the applications deployed the only thing left is to test them. Test hello_1 first, try to access the hosts names defined on the Geronimo server machine:

Now repeat the tests for hello_2.

Congratulations!!! you have successfully configured and deployed two applications to two different virtual hosts and aliases.