Using the Configuration Wizard 2-13
2.6 Postconfiguration Steps
After completing the cell configuration, perform the steps in the following sections to:
■
Start the Deployment Manager for the cell
■
Start the Node Agent for the Application node on the Deployment Manager machine
■
Start the Administration Server for the cell
■
Start the Application Servers in the cell
■
Start the Node Agent on each remote node in the cell
Deployment Manager Machine Perform the following steps on the Deployment Manager machine to start the
Deployment Manager, Node Agent, and Administration Server:
1.
If the Deployment Manager is not already running, start the Deployment Manager as follows:
If only one Deployment Manager is configured on the machine or to start the default Deployment Manager, execute the following commands, where WAS_HOME
is the IBM WebSphere ND home directory:
■
UNIX:
cd WAS_HOMEbin .startManager.sh
■
Windows:
cd WAS_HOME\bin startManager.cmd
If multiple Deployment Managers are configured on the machine and you want to start a Deployment Manager other than the default, execute the following
commands, where WAS_HOME is the IBM WebSphere ND home directory, and DepMgrProfile
is the profile name of the Deployment Manager that you want to start for example Dmgr02:
■
UNIX:
Configuration Summary
Always Review the configuration for the cell by
selecting a Summary View, and then selecting individual items in the list for
that view.
If the cell is configured as you want it, click Extend
to save the new cell configuration. To make changes to the configuration, click
Previous
to return to the appropriate screen for the settings that you want to
change. Configuring Cell
Always This page shows the progress of the cell
configuration update.
When the process completes, click Done. Table 2–6
Cont. Configuration Screens for Editing an Existing Cell Screen
When Does This Screen Appear?
Perform the Following Action
2-14 Configuration Guide for IBM WebSphere Application Server
cd WAS_HOMEprofilesDepMgrProfilebin .startManager.sh
■
Windows:
cd WAS_HOME\profiles\DepMgrProfile\bin startManager.cmd
2.
Enter the following commands to start the Node Agent, where Profile is the name of the Application Server profile on the Deployment Manager machine for
example, Custom01:
■
UNIX:
cd WAS_HOMEprofilesProfilebin .startNode.sh -profileName Profile
■
Windows:
cd WAS_HOME\profiles\Profile\bin startNode.cmd -profileName Profile
3.
Enter the following command to start the Administration Server:
■
UNIX:
.startServer.sh OracleAdminServer -profileName Profile
■
Windows:
startServer.cmd OracleAdminServer -profileName Profile
4.
To start individual servers, enter the following command for each server:
■
UNIX:
.startServer.sh server_name -profileName Profile
■
Windows:
startServer.cmd server_name -profileName Profile
Remote Nodes On each remote node, enter the following command to start the Node Agent on the
node, where NodeProfile is the Application Server profile name that you configured on the node for example, Custom04:
■
UNIX:
cd WAS_HOMEprofilesNodeProfilebin .startNode.sh -profileName NodeProfile
■
Windows:
cd WAS_HOME\profiles\NodeProfile\bin startNode.cmd -profileName NodeProfile
2.7 Example Oracle Fusion Middleware Configuration
Kategori