Accessing the Administration Console

You can use the advanced functions provided in the administration console to change settings in your server configuration.

Note: These advanced functions are only for advanced users.

To access the administration console:

  1. If you are using WebSphere® v5.x servers1, you need to enable the administrative console in the server editor by completing the following steps:
    1. In the Servers view, double-click your WebSphere server v5.x to open the server editor.
    2. Click the Configuration tab and expand the Server Configuration section. Ensure that the Enable administration console check box is selected. Save your changes.
  2. If you are using WebSphere v6.0 servers, you no longer need to enable the administrative console in the server editor. For WebSphere Application Server v6.0, the development environment no longer has the server configuration in the workspace. By default, the administrative console is enabled in the default profile of the server.
    Attention: Server-specific configurations for WebSphere Application Server v6.0 are now set in the WebSphere Administrative Console. The configuration settings that are specific to an enterprise application can be set using the WebSphere Enhanced EAR editor. The WebSphere Enhanced EAR editor is the Deployment page in the Application Deployment Descriptor editor. Use the WebSphere Enhanced EAR editor to configure the following configurations that are specific to an enterprise application:
    • Data Sources
    • Resource adapters and connection factories
    • Substitution Variables
    • Authentications
    • Shared Libraries
    • Virtual Hosts
    • Class loader policies
  3. Start the WebSphere server.
  4. In the Servers view, right-click the server, and then select Run administrative console. The Administrative Client logon window opens in the Web Browser view.
  5. Type the user ID for the administration console. This user ID can be anything. It is only needed for logging purposes.

Once you have made changes, you need to restart the server.

Note: For WebSphere v5.x servers: In the local test situation, after you have made changes to the server, you need to refresh the server folder from the Navigator view. In the remote test situation, after you have made changes to the server, you need to import the modified version into the workspace. Then you need to restart the server.
Related concepts
Application testing and publishing
Related reference
Admin console login fails when running in secure mode
Server Tools extension types

Related information

Importing a server configuration

Exporting a server configuration

1 WebSphere Application Server v5.x test environments and servers are not available in WebSphere Application Server Toolkit.
Terms of use | Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.