#Glassfish server logs password#

# Set glassfish2 application at root URL of the new virtual server Set ID to glassfish2, Hosts to and select http-listener-1 and http-listener-2 on Network Listeners list Go to Configurations - server-config - Virtual Servers - New. Create new virtual server for glassfish2 application Now we will be adding glassfish2 aplication to the secondary domain. Still both domains will show the same content - now at root URL. Go to Applications - glassfish1 and make sure 'server' is selected on Virtual server list and Context Root is set to '/'. Set glassfish1 application at root URL of default Virtual Server 'server' Now you have both apps open but they are not bound to a domain and also use application name in the path. You can use any of the domains because the WARs are not yet bound to a specific domain (virtual host). In a moment 2 files will show up in the directory:Īlternatively you could upload the WARs to ~/appservers/glassfish-4.0-web/glassfish/domains/domain1/applications and deploy them in Administration Console - Applications. To ~/appservers/glassfish-4.0-web/glassfish/domains/domain1/autodeploy At the starting point both domains display the same content namely Glassfish default page. Both domains are fully (using catch-all mapping in Java Control Panel) proxied (mapped) to Glassfish. Our primary domain in cPanel is and secondary (Addon) domain is. The WARs used are slightly modified sample.war provided by Tomcat project. If you have not done it already see instructions at the bottom of article.

#Glassfish server logs password#

We assume you have pristine Glassfish 4 installed with admin password set and remote access to GlassFish Server Administration Console enabled. Here we use default domain1 Glassfish domain and refer by domain to DNS domains. Note the term domain has a bit different meaning in Glassfish terminology and means an administrative domain. In this scenario we will setup 2 different web application at root URLs of 2 different domains: Let's see example deployments with Glassfish 4. Similar setups can also be done with JBoss and Tomcat. Glassfish 4 allows for easy browser based setup of multiple domains each serving different web application using domain's root URL or any arbitrary subpath as document root.