The adminconsole application is not installed
properly
If you have problems bringing up the administrative console , check the
following items:
- Ensure that the adminconsole application is installed and started.
- Check it in the SystemOut.log file of the server or DMGR located at:
Install Root /logs/server1/SystemOut.log
- If the adminconsole started properly, you see something like the
following.
ApplicationMg A WSVR0221I: Application started: adminconsole
- If the application did not start successfully, use the following
technote to reinstall the adminconsole application.
Administrative_Console__all_non_scripting_/swg21163938.html
Most administrative console problems, such as blank pages or missing
links, are solved by reinstalling the adminconsole application.
The adminconsole application is installed and started properly but you
are unable to access the administrative console
- By default the HTTP Transport port for adminconsole is set to 9090.
Check the HTTP Transport port in the server.xml file
Install_Root
/config/cells/cellname/nodes/nodename/servers/server1/server.xml
<transports xmi:type="applicationserver.webcontainer:HTTPTransport"
xmi:id="HTTPTransport_3" sslEnabled="false">
<address xmi:id="EndPoint_3" host="" port="9090"/>
</transports>
- The same port is also be available in:
Install_Root /config/cells/cellname/virtualhosts.xml file.
You should see a similar XML tag in the file:
<aliases xmi:id="HostAlias_5" hostname="*" port="9090"/>
If the port number has changed in virtualhosts.xml, change it back to
9090, then restart the server.
If SSL is enabled , make sure you check the same for the secured transport
port . The default secured HTTP transport is 9043.
If you want to use a virtual host other than admin_host
By default, the adminconsole application runs under the admin_host
virtual host. For security reasons, the admin_host virtual host is not
generated or displayed in the pluginCfg file and is not accessible through
the plug-in . If you want to access the administrative console through the
plug-in, or if you want to change the virtual host, follow the steps
below.
Follow the instructions at this Information Center link to create
a new virtual host.
After creating the new virtual host , follow these steps:
- Log on to the administrative console.
- Click Applications > Enterprise Applications > adminconsole >
Map virtual hosts for Web modules (In additional properties).
- Select the checkbox under webmodule and select the new virtual host
under Virtual Host.
- Save the configuration.
- Click Environment > Virtual Hosts > NewVirtualHostName > Host
alias > New Button. In the hostname field type * and in the port
field type 9090 .The default port number is 9090.
- Click Environment > Virtual Hosts > admin_host > Host alias.
Select 9090, then click Delete. The port number must be unique in the
virtual host.
- Save the configuration.
- Restart the server (server1 or DMGR).
Make sure the port number is in the following location:
install_root/config/cells/mynode/nodes/mynode/servers/server1
Be careful if you modify the virtual host for the deployment manager
administrative console. The filetransfer application must also be assigned
to the newvirtualhost, or SyncNode fails with the exception below. Follow
the first 3 steps to assign the filetransfer application to the new
virtual host.
Exception in syncNode.log file
com.ibm.websphere.management.filetransfer.client.TransferFailedException:
404 Not Found
com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.download(FileTransferClientImpl.java:1241)
Changing the administrative console port
You can safely change the administrative console port as follows.
- Edit the Application Server configuration by opening the server.xml
configuration file for the server1 application server. The file path for
the server1 configuration, with nodename mynode, is:
Install_Root /config/cells/mynode/nodes/mynode/servers/server1
Look for transports
xmi:type="applicationserver.webcontainer:HTTPTransport". The
administrative console application uses transport ports 9090 and 9043. The
sample applications use transport ports 9080 and 9443. Change the port
numbers and save the file. Make a record of the new port numbers.
- Open the virtualhosts.xml file in the Install_Root
/config/cells/mynode folder. This file contains alias entries for the
transport ports defined in the server.xml file. Look for aliases xmi:id to
change port number assignments for any ports you changed.
Modifying the Transport port using wsadmin
- Identify the application server and assign it to the server variable.
set server [$AdminConfig getid /Cell:mycell/Node:mynode/Server:server1/]
Example output:
server1(cells/mycell/nodes/mynode/servers/server1:server.xml#Server_1)
- Identify the Web container belonging to the server and assign it to
the wc variable.
set wc [$AdminConfig list WebContainer $server]
Example output:
(cells/mycell/nodes/mynode/servers/server1:server.xml#WebContainer_1)
- List all the transports belonging to the Web Container and assign it
to the transports variable.
set transportsAttr [$AdminConfig showAttribute $wc transports]
set transports [lindex $transportsAttr 0]
These commands return the transport objects from the transports attribute
in a list format.
Example output:
(cells/mycell/nodes/mynode/servers/server1:server.xml#HTTPTransport_1)
(cells/mycell/nodes/mynode/servers/server1:server.xml#HTTPTransport_2)
- Identify the transport to be modified and assign it to the transport
variable.
set transport [lindex $transports 0]
Example output:
(cells/mycell/nodes/mynode/servers/server1:server.xml#HTTPTransport_1)
- Modify the address attribute to change the host and port.
$AdminConfig modify $transport {{address {{host {myHost}} {port 9081}}}}
- Save the changes.
$AdminConfig save
|