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
- Open the console running on server1.
- Go to Enterprise Applications and select the adminconsole
application.
- Select Map modules to application servers in the Additional
Properties section.
- Click the check box next to the adminconsole module, highlight both
servers in the Clusters and Servers: box, then click Apply.
- 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:
- Start the newly-created server from the command line. Ex:
$WAS_ROOT/bin> startServer.sh server2.
- Start wsadmin. Ex: $WAS_ROOT/bin>wsadmin.sh.
- 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.
- 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
- 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
- Find the one called HTTPTransport_3 and note the port number for this
entry. The default port number is 9092.
- Open the administrative console running on server1 and navigate to
Environment > Virtual Hosts.
- Click on admin_host, then select Host Aliases under
Additional Properties.
- Click new. For Host Name add *; for Port
add the port number from Step 2.
- Click Apply and save the configuration.
- Recycle the added server to pick up these changes.
- 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 |