This topic describes how to add the virtual host that servers the administrative console to the plug-in configuration file so that you can access the administrative console through a Web server.
Before you begin
Install your Version 6 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 sync 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.
Why and when to perform this task
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.
Steps for this task
The default port that displays is 80, unless you specify a different port during profile creation.
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.
For example, to access the administrative console of a stand-alone application server, stop and restart the server1 process.
./stopServer.sh server1
Server server1 stop completed.
To start the application server, issue the following command:
./startServer.sh server1
Server server1 open for e-business; process id is 1719
For example, to access the administrative console of a deployment manager, stop and restart the deployment manager.
./stopManager.sh
Then issue the following command to stop the deployment manager:
./stopManager.sh
Server dmgr stop completed.
To start the deployment manager, issue the following command:
./startManager.sh
Server dmgr open for e-business; process id is 1720
<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"/>
<VirtualHost Name="*:port"/>
The port variable is your HTTP server port.
Result
You can configure your supported Web servers to access the administrative console application of a deployment manager or a stand-alone application server.