You can use IBM® Installation
Manager to install the manager and its associated databases and data
files to an application server computer. However, installation is
not complete until you deploy the manager Web archive (WAR) file to
the application server. Use this task to deploy the manager WAR file
on WebSphere® Application
Server.
Before you begin, install WebSphere Application Server.
To avoid path length issues, avoid installing WebSphere Application Server into a long
path. For example, if you install WebSphere Application
Server to a Windows computer, C:\WAS70 is
an acceptable installation location.
After
you install WebSphere Application
Server, start the instance of the Apache Derby database that is installed
with WebSphere Application
Server. To start the Derby database, complete the following, where
was_folder is
the folder in which WebSphere Application
Server is installed.
- Windows: Run the was_folder\derby\bin\networkServer\startNetworkServer.bat batch
file.
- AIX®/Linux/Solaris: Run the was_folder/derby/bin/networkServer/startNetworkServer script.
You must also use WebSphere Application
Server to create the users and user groups that are to be used for
the manager. During this task, you must map users and user groups
in WebSphere Application
Server to the user roles available for the manager. For more information
about how to create users and user groups, see the documentation for WebSphere Application Server.
Use the Integrated Solutions
Console of WebSphere Application
Server to deploy the WAR file. The default location of the administrative
console is http://hostname:9043/ibm/console,
where hostname is the host
name of the computer on which WebSphere Application
Server is installed.
To deploy the manager WAR file by using
the Integrated Solutions Console of WebSphere Application Server:
- Click and create a data source with the
following properties. Use the defaults for all other properties:
- Step
1: Enter basic data source information
- Data
source name: OptimConsoleDS
- JNDI
name: jdbc/optimconsoleDS
- Step
2: Select JDBC provider
- Select
an existing JDBC provider: Derby Network Server Using
Derby Client 40 (XA)
- Step
3: Enter database specific properties for the data source
- Database
name: OptimConsoleDB;create=true
When you are
done, click Save to save the
data source, and then click Test connection to
test the data source.
- Click and
deploy the WAR file with the following properties. Use the defaults
for all other properties:
- Preparing
for the application installation
- The manager WAR file is shared_installation_directory/console/app/optim.war,
where shared_installation_directory is
the installation directory that you specified for the IBM Optim Shared package
group. For example, the default location for the manager WAR file
on Microsoft Windows is C:\Program Files\IBM
Optim\shared\console\app\optim.war. If
you prefer, you can click Browse to
browse for the file. Use Fast Path to install the application.
- Step 3: Map
resource references to resources
- Click Browse, select optimConsoleDS, and
click Apply.
- Step 5: Map
context roots for Web modules
- Context
Root: /optim
The WAR file
can take several minutes to deploy. When
you are done, click Save to
save the configuration.
- Click and map the
user roles available for the manager to the users or user groups in WebSphere Application Server.
To map one or more roles to a set of users or user groups:
- Select the box by each role that you want to map to
users or user groups. You can map multiple roles to a user
or user group.
- Click Map Users to
assign roles to users or Map Groups to
assign roles to user groups.
- Select the Available users
or user groups that you want to map, click the right arrow button
to move the users or user groups to Selected,
and click OK.
When you are done, click OK,
and click Save.
- Click , select Enable application security, click OK, and click Save.
- Click , select the Select box for optim_war and
click Start. The application can take several minutes to start.
You can now access the manager from a browser. The default
location is http://hostname:port/optim/console. hostname is
the name of the host on which you installed WebSphere Application Server, and port is
the port number used by the manager. By default, the port number is
9080 when you deploy the manager on WebSphere Application Server.