Allow Web servers to access the admin console



Search Tips   |   Advanced Search


Web server ports must be higher than 1023 for the dmgr to stop and start a Web server process on a non-root node agent. Otherwise the node agent must be running as root.

The plug-ins installation wizard creates a Web server definition on the appserver system, either directly when the web and app servers are on the same machine, or by a script when web and app servers are on separate machines.

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

When plugin-cfg.xml is generated, it does not include admin_host on the list of virtual hosts. To configure the admin_host so that Web servers can access the admin console.

  1. Use the admin console to change the admin_host virtual host group to include the Web server port.

    1. Go to...

      Environment | Virtual Host | admin_host | Host Aliases | New

      The default port 80.

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

  2. Click Apply > Save.

  3. Stop and restart the appserver.

    Stand-alone appserver...

    cd $WP_PROFILE/bin
    ./ server1
    ./ server1


    cd $WP_PROFILE/bin

  4. Edit plugin-cfg.xml to include...

    <VirtualHostGroup Name="admin_host">
        <VirtualHost Name="*:9060"/>
        <VirtualHost Name="*:80"/>
        <VirtualHost Name="*:9043"/>
    <ServerCluster Name="server1_s1host_s1cluster">
        <Server LoadBalanceWeight="1" 
            <Transport Hostname="s1host_" 
            <Server Name="s1host_server1_dmgr"/>
    <UriGroup Name="admin_host_server1_s1host_s1cluster_URIs">
        <Uri AffinityCookie="JSESSIONID"
    <Route ServerCluster="server1_s1host_s1cluster"

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

    <VirtualHost Name="*:HTTP_server_port"/>