Allowing Web servers to access the administrative console

This task gives you the option of manually configuring WebSphere Application Server so that Web servers can access the administrative console.

1. Use the administrative console to change the virtual host group admin_host to include the Web server port (80 by default).

   1. Click Environment > Virtual Host > admin_host > Host Aliases > New.The default port that appears is 80 unless you specified a different port on the coexistence panel during installation.

   2. Specify the IP address, or the name of the machine hosting the administrative console application.For example, if you installed the base Application Server or the Deployment Manager on a machine named wastricia.rtp.ibm.com, specify the name in this field.

2. Click Apply > Save.

3. Stop and restart the deployment manager machine, or the Application Server machine.For example, to access the administrative console of a deployment manager machine, stop the deployment manager and restart it. To stop the deployment manager, open a command window and navigate to the /bin directory of the installation root. Then issue this command

   C:\Program Files\WebSphere\DeploymentManager\bin> stopManager.bat
   

   After receiving the following message, you can restart the deployment manager

   ADMU4000I: Server dmgr stop completed.
   

   To start the deployment manager, issue the following command

   C:\Program Files\WebSphere\DeploymentManager\bin> startManager.bat
   

   When you receive a message that is similar to the following message, the deployment manager is running

   ADMU3000I: Server dmgr open for e-business; process id is 1720
   

4. Edit the plugin-cfg.xml file to include the following entries

   <VirtualHostGroup Name="admin_host">
           <VirtualHost Name="*:9090"/>
           <VirtualHost Name="*:80"/>
           <VirtualHost Name="*:9043"/>
       </VirtualHostGroup>
       ...
       ...
       ...
       <ServerCluster Name="dmgr_DMGRHOSTNAMEManager_Cluster">
           <Server LoadBalanceWeight="1" Name="DMGRHOSTNAMEManager_dmgr">
               <Transport Hostname="DMGRHOSTNAME" Port="9090" Protocol="http"/>
           </Server>
           
           <PrimaryServers>
               <Server Name="DMGRHOSTNAMEManager_dmgr"/>
           </PrimaryServers>
       </ServerCluster>
       ...
       ...
       ...
       <UriGroup Name="admin_host_dmgr_DMGRHOSTNAMEManager_Cluster_URIs">
           <Uri AffinityCookie="JSESSIONID"
               AffinityURLIdentifier="jsessionid" Name="/admin/*"/>
       </UriGroup>
       <Route ServerCluster="dmgr_DMGRHOSTNAMEManager_Cluster"
           UriGroup="admin_host_dmgr_DMGRHOSTNAMEManager_Cluster_URIs" VirtualHostGroup="admin_host"/>
   

   Replace DMGRHOSTNAME with the host name of your deployment manager. For example, if the host name is wastricia

   <ServerCluster Name="dmgr_wastriciaManager_Cluster">
   
   

You can configure your supported Web servers to access the administrative console application of the WAS, V5.0.1 and later.

To continue, return to Preparing to install and configure a Web server.

 

See Also

Preparing to install and configure a Web server

 

---