In a production environment, the manager and other components
in your Optim™ solution can
be installed on different computers for greater performance and reliability.
Configuring the components to work together might require the cooperation
of many different people.
The people who collaborate to configure the manager with other
components might include:
- Application server administrator
- System administrator of proxy computer
- Service developer
- User with administrator access to the manager
- User with database administrator access to the manager
Application server administrator
The application
server administrator is responsible for the initial setup of the manager
and the management server. To complete the initial setup of the manager
and the management server, the application server administrator must
complete the following tasks:
- Install the manager and management server by using IBM® Installation Manager.
You can use Installation
Manager to install a version of IBM WebSphere® Application Server
Community Edition that is delivered with the manager. You can deploy
the manager and management server to WebSphere Application Server
Community Edition for test and evaluation purposes.
- Start the application server to which you will deploy the manager
and the management server, if it is not already started.
- Create a data source (or database pool) on the application server
to which you will deploy the management server. Use OptimServerDB
as the database name for this data source.
This data source is
preconfigured when you install the version of WebSphere Application Server Community
Edition that is delivered with the manager.
- Create a data source (or database pool) on the application server
to which you will deploy the manager. Use optimConsoleDB as the database
name for this data source.
This data source is preconfigured when
you install the version of WebSphere Application
Server Community Edition that is delivered with the manager.
- Deploy the management server and manager web archive (WAR) files
to the application server.
If you are upgrading, remove any previous
versions of the management server and manager WAR files before deploying
the new versions of the WAR files.
The WAR files are in the
following locations, where
shared_installation_directory is
the installation directory that you specified for the IBM Optim Shared package
group.
- WAR file for the manager: shared_installation_directory/console/app/optim.war
- WAR file for the management server: shared_installation_directory/server/app/management-server.war
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 are upgrading,
you must notify users that the manager is upgraded. A user might need
to refresh the browser or clear the browser cache to get the upgraded
version of the manager.
- Configure user accounts for the manager.
A security realm called
optimConsoleRealm is preconfigured when you install the version of WebSphere Application Server
Community Edition that is delivered with the manager. The preconfigured
optimConsoleRealm security realm stores security information in the
OOB_ROLE, OOB_USER, and OOB_USER_ROLE tables in the optimConsoleDB
database. You can add accounts, remove accounts, or change passwords
by changing the user information in the OOB_USER and OOB_USER_ROLE
tables.
- To establish a secure connection between a management server and
a proxy that are on separate computers, add a trust relationship between
the management server and the proxy. You might need to work with the
system administrator of the proxy computer to add this trust relationship.
- If the executor is to be used to run services, create and configure
replacement data and sample data tables on the database of your choice.
You
can use Installation Manager to install the Optim Replacement Data Database
with the management server. Alternatively, you can install the data
from the Optim Replacement
Data Database in comma-separated format. The data is installed with
Data Definition Language (DDL) code. Use the DDL code to create and
configure the replacement data and sample data tables on the database
of your choice.
Depending on your needs, the application server administrator
might choose to deploy additional instances of the management server
and manager on other application servers.
System administrator of proxy computer
The
system administrator is responsible for the initial setup of the proxy
and of any service execution components that are used by the proxy.
To complete the initial setup of the components, the system administrator
must complete the following tasks:
- Install the proxy by using Installation Manager.
- Install the service execution component or components that are
included with your solution. For example, if your solution includes
the executor, install the executor by using Installation Manager.
- Configure the proxy to use the service execution component or
components that are included with your solution.
- To establish a secure connection between a management server and
a proxy that are on separate computers, add a trust relationship between
the management server and the proxy. You might need to work with the
administrator of the application server on which the management server
is deployed to add this trust relationship.
Depending on your needs, the system administrator might choose
to install additional instances of the proxy and the service execution
component on other computers.
Service developer
A service developer is
responsible for publishing services to the repository and testing
services by using the manager. Service developers use IBM Optim Designer
to design services, perform initial tests on the services, and publish
services to a repository. The service developer can use the manager
(user role designer) to verify that the service is on the repository
and to test the service further. When the service developer is done
testing, the service developer can promote the service to another
repository.
For example, an enterprise uses a test repository
and a production repository. A service developer at that enterprise
uses Optim Designer to design
services and publish the services to the test repository. The service
developer then tests the services in the test repository. When the
service is ready for production use, the service developer promotes
the services to the production repository.
For more information
about how to design, test, and publish services by using Optim Designer, see the Optim Designer documentation.
User with administrator access to the manager
Users
with administrator access to the manager (user role admin) are responsible
for configuring connections between the manager and the other components.
An administrator must complete the following tasks:
- Set the registry location.
- Add management servers and proxies to the manager.
If the executor is to be used to run services, the administrator
must also add a license to a management server.
User with database administrator access to the manager
If
the executor is to be used to run services, users with database administrator
access to the manager (user role dba) are responsible for adding database
drivers to the repository.