Installing the administrative console on version 5 releases of Base Edition
 Technote (troubleshooting)
 
Problem(Abstract)
WebSphere® Application Server Base Edition comes with the administrative console installed on server1. If another server is created, it can only be viewed and cannot be administered from the console running on server1.
 
Cause
The adminconsole application runs in the server1 JVM™ and therefore does not have access to administer another server on Base Edition.
 
Resolving the problem
Base Edition installation does not have the ability to administer additional servers by default. For an environment that needs additional servers, IBM recommends installing Network Deployment and federating the Base installation with deployment manager.

If this is not possible, follow these steps to allow administrative console administration of additional servers.

Install or map the adminconsole process to the additional server so that it can be administered properly.

Mapping the adminconsole application to the additional server

  1. Open the console running on server1.

  2. Go to Enterprise Applications and select the adminconsole application.

  3. Select Map modules to application servers in the Additional Properties section.

  4. Click the check box next to the adminconsole module, highlight both servers in the Clusters and Servers: box, then click Apply.

  5. Click OK, then Save to update your configuration files.

For additional information on this process see the following technote:

Administrative_Console__all_non_scripting_/swg21141430.html

See the section on Adding the HTTP Transport port to the admin_host below to complete the action.

The adminconsole application can also be installed to the additional server with a different name. The main difference is that with the mapping, there is only one application and it is running on both servers; however, if it installed again there are now two applications. Functionally, these have the same result. If fix packs are applied later, the reinstallation of the application must occur again, because the update installer cannot update the second console application.

Following these steps to install the adminconsole application again to the additional server:

  1. Start the newly-created server from the command line. Ex: $WAS_ROOT/bin> startServer.sh server2.
  2. Start wsadmin. Ex: $WAS_ROOT/bin>wsadmin.sh.
  3. Install the adminconsole application to the second server. For example: "wsadmin>$AdminApp install C:/$WAS_ROOT/installableApps/adminconsole.ear {-server server2 -appname adminconsole2}" Remember to use the forward slash, even in Windows and keep in mind that the brackets "{" and "}" are required in the wsadmin command above.
  4. Save the configuration. For example: wsadmin> $AdminConfig save

Now that the administrative console is either mapped or installed to the new server, you must set up the virtual host alias to allow access to the console.

Adding the HTTP Transport port to the admin_host

  1. Go to the server.xml to find the HTTPTransport port. $WAS_ROOT\config\cells\<cell_name>\nodes\<node_name>\servers\<new_server_name>\server.xml

  2. Find the one called HTTPTransport_3 and note the port number for this entry. The default port number is 9092.

  3. Open the administrative console running on server1 and navigate to Environment > Virtual Hosts.

  4. Click on admin_host, then select Host Aliases under Additional Properties.

  5. Click new. For Host Name add *; for Port add the port number from Step 2.

  6. Click Apply and save the configuration.

  7. Recycle the added server to pick up these changes.

  8. Access the console on the new server. For example:
    'http://hostname:'<port from #2 above>/admin

Some users may want to use HTTPS for their console and can therefore add the SSL HTTP Transport port to the virtual host alias list. If additional HTTP Transports are added, HTTPTransport_3 might not be the desired port, but by default it is as described above.

NOTE:
If security is enabled the only way to get console users and groups to work is by doing the following:

Go to Applications>(new_adminconsolename)
under additional properties click on Map security roles to users/groups place a check under role. This will place a check under all the different roles like so:
X administrator
X operator
X configurator
X monitor

Also place a check under all 4 roles on the all Authenticated part like so:
X Role Everyone All Authenticated?
X administrator X
X operator X
X configurator X
X monitor X

Click OK
Save the changes
and recycle WebSphere
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Administrative Console (all non-scripting)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1173344
IBM Group: Software Group
Modified date: Jul 27, 2005