Note: From WebSphere Application Server V8, additional server runtime performance

tuning option has been introduced during profile creation. You have three performance
tuning options to choose from:
_ Standard, which is the standard default configuration settings that are optimized for
general purpose usage.
_ Peak, which is appropriate for a production environment where application changes
are rare and optimal runtime performance is important.
_ Development, which is appropriate for a development environment where frequent
application updates are performed and system resources are at a minimum. Do not
use the development setting for production servers
startingport, portprops <filename>
The new node agent is assigned a range of ports automatically. If you want to specify the
ports for the node rather than taking the default, you can specify a starting port using the
startingport parameter. The numbers are incremented from this number.
For example, if you specify 3333, the BOOTSTRAP_ADDRESS port will be 3333,
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS will be 3334, and so on.
As an alternative, you can provide specific ports by supplying a file with the port
properties.
includeapps, includebuses
If you are federating an application server, you can keep any applications or service
integration buses that are deployed to the server. The default behavior is not to include
any of these resources during federation, so they will be lost.

Example 3-2 Registering a stand-alone application server to an administrative agent

C:\IBM\WebSphere\AppServer\profiles\AdminAgent01\bin>registerNode.bat
-profileName
AdminAgent01 -host was85.ral.ibm.com -profilePath
"C:\IBM\WebSphere\AppServer\profiles\AppSrv02" -connType SOAP -port 8877
-username
aaadmin -password aapassw0rd -nodeusername wasadmin -nodepassword
passw0rd
After registering a new server to the administrative agent, log in to the administrative agent
console to manage the server. Notice that now you can select which server to administrator,
the administrative agent, or the new stand-alone profile, as illustrated on Figure 3-22.

The manageprofile command takes many parameters and for complex WebSphere
environments it can be difficult to use. There is an interactive tool called Manage Profiles
Interactive that guides you through the important manageprofile use cases.
This command is not shipped with the WebSphere package, but it is available to download at
no cost. You will find the tool, documentation, and a sample video on its usage at the following
website:
http://www-01.ibm.com/support/docview.wss?uid=swg21442487

After you download the tool, you must unpack its content in the install_root/bin directory.
After you unpack it, you can use two scripts to run it:
_ run_manageprofilesInteractive.bat for Windows operating systems
_ run_manageprofilesInteractive.sh for UNIX operating systems

The administrative console application name is isclite, and it is a system application. This
means that the application is central to a WebSphere Application Server product, and it is
installed when the product is installed. In this case, the administrative console application is
installed during profile creation, if selected, or afterwards using the command line. You do not
see system applications in the list of installed applications when using the administrative
console. You cannot stop or start the application directly or uninstall the application directly.

The user ID specified during login is used to track configuration changes made by the user.
This allows you to recover from unsaved session changes made under the same user ID, for
example, when a session times out or the user closes the web browser without saving. The
configuration files are copied from the master repository and cached in the temporary
workspace because you navigate through different console areas. Configuration changes are
stored in the profile_home/wstemp temporary workspace directory until the changes are
merged with the master repository during a save operation in the administrative console.
Workspaces are not removed when you log out, so they can be reused in another login
session for the same login user ID.
WebSphere administrative security also affects the log in procedure. The following scenarios
relate how to maneuver in either security state:
_ If WebSphere administrative security is not enabled
You can enter any user ID, valid or not, to log in to the administrative console. The user ID
is used to track changes to the configuration but is not authenticated. You can also simply
leave the User ID field blank and click the Log In button. The administrative security is not
enabled, so you cannot see any password field in the administrative console login window.
Note: You cannot log into two instances of administrative consoles that are running on the
same machine from a single browser type. For example, if you use Firefox to log into the
deployment manager administrative console, you cannot also log into a job manager
running on the same machine.
There is a limitation that cookies are unique per domain rather than a combination of
domain and port. Therefore, the cookies that control the session and authentication data in
the first browser tab or window get overwritten when logging into the other console in a
new browser tab or window. However, it is possible to log into two consoles simultaneously
from two completely different browsers, for example, Firefox and Internet Explorer.

Unfederated application servers, administrative agents, deployment managers, and job

managers can have their own administrative consoles. If you plan to install the administrative
console, a profile that does not have an administrative console installed must exist. You
cannot have two administrative consoles running in the same profile.
To install an administrative console after profile creation or to uninstall the administrative
console, use the wsadmin command to run a jython script named deployConsole.py. This
script is located in the bin folder of the IBM WebSphere Application Server installation root
and can be run in either connected or disconnected mode. The usual security restrictions for
the wsadmin command apply to this script. In connected mode, the user must authenticate if
security is enabled.

D:\was85\IBM\WebSphere\AppServer\profiles\Dmgr_85_01\bin>wsadmin -lang jython

-c AdminControl.getNode() -user admin85 -password admin85 -f
"D:\was85\IBM\WebSphere\AppServer\bin\deployConsole.py" install
Chapter 6. Administration consoles and commands 191
Example 6-3 Uninstalling the administrative console with the Jython script deployConsole.py

D:\was85\IBM\WebSphere\AppServer\profiles\Dmgr_85_01\bin>wsadmin -lang jython

-c AdminControl.getNode() -user admin85 -password admin85 -f
"D:\was85\IBM\WebSphere\AppServer\bin\deployConsole.py" remove

The default session timeout value for the administrative console is 15 minutes. The
timeout value can be modified by using a JACL script that is available at the information
center.
To change the session timeout value, refer to the information center at the following website:
http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/com.ibm.websphere.nd.doc/isc/
cons_sessionto.html

Console identity
The banner displays a user ID and it can be customized to show a unique identifier for the
administrative console. This can be helpful in cases where administrators log on to multiple
administrative consoles. Glancing at the banner lets you know which system you are logged
on to. You can add a Console Identity from the administrative console.
To customize the banner:
1. click System administration Console Identity. Select Custom, and enter the
identity

To set administrative console preferences, click System administration Console

Preferences in the navigation tree. You have the following options:

TIP: If you enable administrative security, and then find that you cannot log in, you can
disable security through scripting or manually editing the security.xml profile. This action
allows you to go back through the security configuration to see what is causing the
problem.

Editing an XML configuration file manually is not a best practice. Use scripting to enable or
disable administrative or application security and to modify other security settings. To disable
administrative security through scripting:
1. Navigate to the dmgr_profile_home/bin directory.
2. Start the wsadmin scripting client with the -conntype none argument.
3. Enter the securityoff command in JACL mode or securityoff () command in Jython
mode.
4. Exit the wsadmin scripting client.
5. Restart your processes.

Note: When running command-line tools on Microsoft Windows Vista or later Microsoft
operating systems, on Windows Vista, Windows Server 2008, and Windows 7 operating
systems, you can install WebSphere Application Server as either Administrator or
non-administrator. When it is installed as Administrator, certain operations (such as
those involving Windows Services) require Administrator privileges