This topic summarizes how to configure the application serving
environment.
- At
the end of product installation, select the Launch the Profile Management tool check
box to create a deployment manager profile.
This step creates
the deployment manager and the cell. Later steps in this procedure create
an application server profile and optionally, a custom profile.
See Creating a deployment manager profile.
- Start the First steps console by selecting the check box on the
last panel of the wizard.
The
First steps console for the deployment manager profile can start automatically
at the end of profile creation. Select the check box on the last panel of
the Profile Management tool.
The First
steps console is an easy way to start using the product. The console provides
one-stop access to the administrative console, Samples Gallery, Profile Management tool,
installation verification test, Migration wizard, and other activities.
See
the description of the firststeps command for
more information.
- Click Installation verification on the First
steps console.
The installation
verification test starts the deployment manager process named dmgr and runs
several tests to verify that the dmgr process can start without error.
See Using the installation verification tools for more information.
- Click Profile Management tool on
the First steps console to create an application server profile.
See Creating an application server profile.
- Start the First steps console by selecting the check box on the
last panel of the Profile Management tool.
This First steps console belongs to the Application Server profile
that you just created. Each profile has its own First steps console.
- Click Installation verification on the First
steps console.
The installation verification test starts the
new application server process named server1 and runs several tests to verify
that the server1 process can start without error.
- Federate the application server into
the deployment manager cell.
If both server processes are running,
use the administrative console of the deployment manager to add the application
server node into the cell.
Point your browser at http://localhost:9060/ibm/console for
example, to start the administrative console. Or start it from the First steps
console of the deployment manager profile.
Log in and click and
follow the wizard to add the node into the cell. You can use localhost for
the Host field if both processes are on the same machine. The SOAP port for
the application server node is 8880 unless you changed the port during profile
creation.
If the deployment manager is running, you
can use the addNode command instead. See addNode command.
- Federate
the application server into the deployment manager cell.
If
both server processes are running, use the administrative console of the deployment
manager to add the application server node into the cell.
Point
your browser at http://localhost:9060/ibm/console for example, to start
the administrative console. Or start it from the First steps console of the
deployment manager profile.
Log in and click and follow the wizard to add the node into
the cell. You can use localhost for the Host field if
both processes are on the same machine. The SOAP port for the application
server node is 8880 unless you changed the port during profile creation.
If the deployment manager is running, you can use the addNode command
instead. See addNode command.
- Optional:
Click Profile Management tool on
the First steps console to create a custom profile.
Verify that
the deployment manager is running. The Profile Management tool can
federate the custom node for you if the deployment manger is running.
Supply
the host name and the SOAP port for the deployment manager while creating
the custom profile.
Choose to federate the custom node into the deployment
manager cell. A custom profile must be part of a cell.
Use the deployment
manager to customize the node at your leisure. Add servers, add clusters,
and install applications on the node, for example.
See Creating a custom profile.