|
Problem(Abstract) |
For security reasons, the admin_host virtual host and
corresponding host aliases are not included in the plugin_cfg file. |
|
Resolving the
problem |
- The admin_host virtual host is not displayed in the plugin_cfg.xml
file for security reasons. The administrative console runs under the
admin_host port . If you want to access the administrative console through
the plug-in file, you must change the virtual host for the administrative
console and file transfer applications to another virtual host and add the
administrative port to the new virtual host and the HTTP Transport port.
- If any of the IBM® WebSphere® Application Server transport ports use
the administrative host port, that Application Server port does not
display in the plugin-cfg.xml file. In the plug-in regen trace, you see
something similar to this:
[5/13/04 13:50:13:231 MST] 702a95d8 PluginDocumen d Not including
virtual host "admin_host" in plugin-cfg.xml
[5/13/04 13:50:13:238 MST] 702a95d8 PluginDocumen d Admin transport
-->lpqwa001: 25001<-- will not be added to plugin-cfg.xml
[5/13/04 13:50:13:239 MST] 702a95d8 PluginDocumen d Admin transport
-->lpqwa002: 25001<-- will not be added to plugin-cfg.xml
[5/13/04 13:50:13:239 MST] 702a95d8 PluginDocumen d Admin transport
-->ndm_lx01q: 25001<-- will not be added to plugin-cfg.xml
[5/13/04 13:50:13:240 MST] 702a95d8 PluginDocumen d Admin transport
-->ndm_lx01q: 25051<-- will not be added to plugin-cfg.xml
To avoid this problem, change the Application Server transport port to
anything other than the administrative host port . The Application Server
does not have to be in the same node. |
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|
|