To use the manager on an application server, you must first
start the manager on its application server. After the manager is
started on the application server, you can access the manager at any
time.
Unless you use the manager with WebSphere® Application Server Community
Edition in its default configuration, you must install and configure
the manager before you can start the manager.
To start the manager on an application server:
- Start the application server. If the application
server is set to start the manager web application automatically,
then the manager is started with the application server. If
you use the manager with WebSphere Application
Server Community Edition in its default configuration, then complete
the following step. In this step, shared_installation_directory is
the installation directory that you specified for the manager.
- Microsoft Windows computers: Click , or run the script shared_installation_directory\WebSphere\AppServerCommunityEdition\bin\startup.bat.
- Linux or UNIX computers: Run the script shared_installation_directory/WebSphere/AppServerCommunityEdition/bin/startup.sh.
- If necessary, start the manager web application by using
the application server console. If you use the manager
with WebSphere Application
Server Community Edition in its default configuration, then complete
the following steps:
- Use a web browser to access and sign into the Administrative
Console. The default location is at http://hostname:port/console/,
where hostname is the host
name or IP address of the WebSphere Application
Server Community Edition computer and port is
the port number. The default port number is 8080. Use
user ID system and password manager to
access the Administrative Console.
- Click Web App WARs.
- Click Start for the component
with an URL of /optim.
To automate the starting of the manager after you restart
the computer, configure the application server as a Windows service or Linux or UNIX daemon.