This topic describes how to set up the administrative console environment, to access the administrative console, and to log out of the administrative console.
To access the administrative console, you must first install WebSphere® Application Server and the administrative console.
The administrative console application is installed during the initial installation process.
You start the administrative console, access the console through a Web browser, and then log into the administrative console. After you finish working in the administrative console, save your work and log out.
You can start an unfederated application server, an administrative agent server, a deployment manager server , or a job manager server.
Check the SystemOut.log file of the server that runs the console application to verify that the console application starts successfully. If the console application starts successfully, you see the WSVR0221I: Application started: isclite message.
If you cannot start the administrative console because the
console port conflicts with an application that is already running on the
machine, change the port number in the installation root/profiles/profile
name/config/cells/cell_name/nodes/node_name/serverindex.xml file
and the installation root/profiles/profile name/config/cells/cell_name/virtualhosts.xml files.
Change all the occurrences of the console port to a new port number. Alternatively,
shut down the other application that uses the conflicting port before starting
the WebSphere Application
Server product.
Enablement of JavaScript is required. You must enable JavaScript so that all the features of the administrative console are available.
The administrative consoles for an unfederated application server, the deployment manager and the administrative agent use 9060 as the default port number for an unsecure administrative console and 9043 as the default port number for a secure administrative console. Each new administrative console that you deploy during profile creation is assigned a new unsecure port number, and, if you enable security during profile creation, a new secure port number. Whichever unsecure administrative console you create first is assigned port 9060, as long as the port is available. Likewise, whichever secure administrative console you create first is assigned port 9043, as long as the port is available.
The administrative console for the job manager uses 9960 as the default port number for an unsecure administrative console and 9943 as the default port number for a secure administrative console. Each new administrative console that you deploy during profile creation is assigned a new unsecure port number, and, if you enable security during profile creation, a new secure port number. Whichever unsecure administrative console you create first is assigned port 9960, as long as the port is available. Likewise, whichever secure administrative console you create first is assigned port 9943, as long as the port is available.
For a listing of supported Web browsers, see WebSphere Application Server system requirements.
The your_fully_qualified_server_name string is the fully qualified host name for the machine that contains the administrative console. The administrative console can be for an unfederated application server, a deployment manager, an administrative agent, or a job manager. The port number for the port_number string is 9060 by default for the unfederated application server, the deployment manager, and the administrative agent. For the job manager, the port number for the port_number string is 9960 by default.
http://www.ibm.com/support/docview.wss? rs=180&uid=swg27006921The Web address displays on two lines for printing purposes. Enter the Web address on one line in your browser.
A login page displays after the administrative console starts.
The administrative console can be for an unfederated application server, a deployment manager, an administrative agent, or a job manager.
The node can be the administrative agent node or a node for one of the application servers registered to the administrative agent. After you select a node, the login procedure is the same as that for the other server types, and for administrative agents with no nodes registered.
The user ID lasts only for the duration of the session for which it is used to log in.
Changes made to server configurations are saved to the user ID. Server configurations also are saved to the user ID if a session timeout occurs.
If you close the browser before saving your work, you can recover any unsaved changes the next time that you log in under the same user ID.
You have set up the administrative console environment, accessed the administrative console, and logged out of the administrative console.
Use the administrative console to manage the product.
In this information ... | IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |