Allow Web servers to access the administrative console

 

+

Search Tips   |   Advanced Search

 

Overview

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

Install...

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.

This task gives you the option of configuring the admin_host so that Web servers can access the administrative 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 administrative 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 administrative console application. For example, if you installed a WAS product on a machine that is named wastricia.rtp.ibm.com, specify the name in this field.

  2. Click Apply > Save.

  3. Stop and restart the application server. For example, to access the administrative console of a stand-alone application server, stop and restart the server1 process. To stop server1

    cd WAS_HOME/profiles/profile/bin directory
    ./stopServer.sh server1

    After receiving the following message, one can restart the application server

    Server server1 stop completed.

    To start the application server, issue the following command

    ./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 administrative console of a deployment manager, stop and restart the deployment manager. To stop the deployment manager...

    cd WAS_HOME/profiles/profile/bin
    ./stopManager.sh

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

    Server dmgr stop completed.

    To start the deployment manager, issue the following command

    ./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"/>

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

    <ServerCluster Name="server1_wastriciaserver1_Cluster">