Allowing Web servers to access the console

 

This topic describes how to add the virtual host that servers the console to the plug-in configuration file so that you can access the console through a Web server.

If a Web server is in a configuration, its port must be higher than 1023 to use a non-root node agent. Otherwise the node agent must be running as root in order for the administrative console of the deployment manager to stop and start the Web server process in that managed node.

Install your V6 WebSphere Application Server product, a Web server, and the Web server plug-ins for WebSphere Application Server.

The Plug-ins installation wizard creates a Web server definition on the Application Server system, either directly when they are on the same machine, or by a script for remote scenarios.

After creating the Web server definition, the plug-in configuration file exists within the Web server definition.

The plugin-cfg.xml file can be overwritten by the deployment manager synchronization operation, the GenPluginCfg script or any other method that regenerates the file. If you make changes to the plugin-cfg.xml file, and want to keep those changes, it is recommended that you create a copy of the file in a separate location. Make your manual updates each time the file is automatically refreshed by another process.

 

Overview

This task gives you the option of configuring the admin_host so that Web servers can access the console. When the Web server plug-in configuration file is generated, it does not include admin_host on the list of virtual hosts.

 

Procedure

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

   1. Click Environment > Virtual Host > admin_host > Host Aliases > New.

      The default port that displays is 80, unless you specify a different port during profile creation.

   2. Specify the IP address, or the name of the machine that is hosting the HTTP server.

      For example, if you installed a WebSphere Application Server product on a machine that is named waslwaj.rtp.ibm.com, specify the name in this field.

2. Click Apply > Save.

3. Stop and restart the appserver.

   For example, to access the console of a stand-alone appserver, stop and restart the server1 process. To stop server1, open a command window and navigate to the profile_root/bin directory. Then...

   ./stopServer.sh server1
   

   After receiving the following message, you can restart the appserver:

   Server server1 stop completed.
   

   To start the appserver,...

   ./startServer.sh server1
   

   When you receive a message that is similar to the following message, the server1 process is running:

   Server server1 open for e-business; process id is 1719
   

4. Stop and restart a deployment manager.

   For example, to access the console of a deployment manager, stop and restart the deployment manager. To stop the deployment manager, open a command window and navigate to the profile_root/bin directory. Then issue this command:

   ./stopManager.sh
   

   Then issue the following command to stop the deployment manager:

   ./stopManager.sh
   

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

   Server dmgr stop completed.
   

   To start the deployment manager,...

   ./startManager.sh
   

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

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

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

   <VirtualHostGroup Name="admin_host">
           <VirtualHost Name="*:9060"/>
           <VirtualHost Name="*:80"/>
           <VirtualHost Name="*:9043"/>
       </VirtualHostGroup>
       ...
       ...
       ...
       <ServerCluster Name="server1_SERVER1HOSTserver1_Cluster">
           <Server LoadBalanceWeight="1" Name="SERVER1HOSTserver1_dmgr">
               <Transport Hostname="SERVER1HOST" Port="9060" Protocol="http"/>
           </Server>
           
           <PrimaryServers>
               <Server Name="SERVER1HOSTserver1_dmgr"/>
           </PrimaryServers>
       </ServerCluster>
       ...
       ...
       ...
       <UriGroup Name="admin_host_server1_SERVER1HOSTserver1_Cluster_URIs">
           <Uri AffinityCookie="JSESSIONID"
               AffinityURLIdentifier="jsessionid" Name="/ibm/console/*"/>
       </UriGroup>
       <Route ServerCluster="server1_SERVER1HOSTserver1_Cluster"
           UriGroup="admin_host_server1_SERVER1HOSTserver1_Cluster_URIs" VirtualHostGroup="admin_host"/>
           
   

   If your HTTP server has an HTTP port other than 80, add an entry to the VirtualHostGroup:

   <VirtualHost Name="*:port"/>
   
   
   

   The port variable is your HTTP server port.

 

Results

You can configure your supported Web servers to access the console application of a deployment manager or a stand-alone appserver.