A deployment manager provides a single administrative interface
to a logical group of servers on one or more machines. After installing WebSphere Process Server, you can configure
a deployment manager.
Before you begin
Why and when to perform this task
If you have decided that your solution requires network deployment,
you require a deployment manager from which to manage the multiple nodes.
This procedure assumes you are
Creating profiles using the Profile wizard or
Augmenting profiles using the Profile wizard, and have followed the instructions
in the relevant procedure. As a result, you have started the Profile wizard
and have selected to create or augment a deployment manager profile. You must
now configure it.
Using the Profile wizard, complete the following steps
to configure a new deployment manager profile.
Steps for this task
- Do one of the following depending on whether you are creating or
augmenting a deployment manager profile.
- If you are augmenting a profile, much of the profile configuration will
be inherited from the WebSphere Application Server Network Deployment profile.
The Service Component Architecture configuration panel is displayed. Proceed
to step 7.
- If you are creating a profile, you must configure it with unique values.
The Profile name panel is displayed. Proceed to step 2.
- In the Profile name panel, specify a name for the
profile that is unique among the profiles on the machine or accept the default
name. If any other profiles exist, you can make this profile the default profile
by selecting the check box next to Make this profile the default. Then
select Next.
Each profile that you create must have a
name. When you have more than one profile, you can distinguish them at their
highest level by this name. See Naming considerations for profiles, nodes, hosts, and cells for information on issues you must consider when naming
the profile, such as restrictions on the length of the directory name.
- In the Profile directory panel,
either accept the default directory location for the profile or select Browse to
specify another location, then select Next.
This directory
will contain the files that define the runtime environment, such as commands,
configuration files, and log files. By default, this directory location is:
On Linux and UNIX platforms: install_root/profiles/profile_name
On Windows platforms: install_root\profiles\profile_name
where
profile_name is the name you specified in step
2. If the directory already exists, it must
be empty or an error will be displayed.
If you select Back and
change the name of the profile, you might have to manually change the name
on this panel when it is displayed again.
- In the Node, host, and cell names panel, specify a node name unique
to the cell, the actual host name of the machine, and a unique cell name for
the deployment manager, or accept the defaults, then select Next.
Use a unique name for each deployment manager that you create. See Naming considerations for profiles, nodes, hosts, and cells for information
on reserved terms and other issues you must consider when naming the node,
host, and cell.
- In the Port value assignment panel, verify that the ports specified
for the deployment manager are unique, then select Next.
On Windows platforms: Choose
whether to run the deployment manager as a Windows service and select Next. If the profile is configured as a Windows service, the product starts
Windows services for server deployment manager processes started by a startManager command.
For example, if you configure a deployment manager as a Windows service and
issue the startManager command, the wasservice command starts
the defined service.
Important: If you choose to log on
as a specified user account, you must specify the user ID and the password
for the user who is to run the service, and the startup type (default is Manual).
The user ID must not have spaces in its name, it must belong to the Administrator
group, and it must have the advanced user rights Act as part of the operating
system and Log on as a service. If the user ID belongs to the Administrator
group, the Profile wizard grants it the advanced user rights if it does not
already have them.
- In the Service Component Architecture configuration
panel, choose to enable the Service Component Architecture to connect to a
secured bus. To do so, perform the following steps:
- Select the Configure the Service Integration Bus in a secured
mode check box.
- Enter the user ID and password, and confirm the password.
- Select Next.
Important: When both global security and Service Component
Architecture system bus security are turned on, proper credentials are required
to connect to the Service Component Architecture system bus to send or receive
messages. In order for the Service Component Architecture to connect to a
secured system bus, it makes use of the identity of an authorized user that
you supply in this panel. The user ID supplied must be a valid user in the
designated user registry. The user directory can be LDAP, operating system,
flat file, or any other registries that WebSphere Application Server is configured
to use for user authentication.
To set or update this user ID and
password after profile creation or augmentation, simply edit the J2C authentication
alias name "SCA_Auth_Alias" to provide the user ID and password information.
For information on how to modify this alias, see the topic Modifying authentication aliases.
For more information on the Service
Integration Bus, see the topic Service integration buses.
- In the Database configuration panel, configure the Common database
used by selected WebSphere Process Server components.
Refer
to the topic Configuring the Common database using the Profile wizard for details and
return to this step when you have completed the fields on the Database configuration
and Additional database configuration information panels.
- In the Profile summary panel, review the profile
characteristics and select Next to create the profile or select Back to
change the characteristics of the profile.
The Profile wizard
shows a progress panel to indicate that the profile is being created or augmented.
If no errors are detected, the Profile creation is complete or Profile augmentation
is complete panel is displayed at the end of the process.
Attention: If
errors are detected, other panels might be displayed in place of this panel.
Examples include the following:
- Profile creation is complete with warnings panel, which indicates that
a profile was created but warnings were generated.
- Profile creation is incomplete panel, which indicates that a profile was
created but exists in an unusable state.
- Profile creation failed panel, which indicates that a profile was unable
to be created.
- Profile augmentation is complete with warnings panel, which indicates
that a profile was augmented but warnings were generated.
- Profile augmentation is incomplete panel, which indicates that a profile
was augmented but exists in an unusable state.
- Profile augmentation failed panel, which indicates that a profile was
unable to be augmented.
Each of these panels identifies the log file to reference in order to
troubleshoot the problems. Also refer to
Recovering from profile creation or augmentation failure for troubleshooting tips.
- Complete the deployment manager profile configuration by doing
one of the following, depending on whether you must manually configure the
Common database.
- If you completed configuration of the Common database using the Profile
wizard, ensure the check box to start the First Steps console is selected,
and select Finish to close the Profile wizard and start the First Steps
console, as instructed in Starting the First Steps console.
- If you elected to postpone actual database configuration by producing
scripts to be run manually, do the following:
- Unselect the check box to launch the First Steps console and select Finish to
close the Profile wizard.
- You or your database administrator must now edit and run the generated
scripts to create and configure the WPRCSDB database (or
its equivalent if it has a different name on your system). See Common database specifications for
the locations of these scripts. When you have completed configuring the database,
start the First Steps console associated with the profile, as instructed in Starting the First Steps console.
Result
A new WebSphere Process Server deployment manager profile exists.
The node within the profile has a deployment manager named Dmgr01.
What to do next
Check server operation by selecting
Start the deployment manager from
the First Steps console. An output window opens. If you see a message similar
to the following, your deployment manager is operating properly:
ADMU3000I: Server dmgr open for e-business; process id is 3072
In
a network deployment environment, you must create and configure other databases,
create custom profiles and federate them to your deployment manager, create
servers, create clusters if you desire workload management capabilities, and
perform other tasks specific to your planned installation environment. Your
planned environment dictates which tasks you must perform and the order in
which you perform them. See the following topics for more information on planning
topologies and the databases required by WebSphere Process Server:
- Planning installation topologies for example installation
scenarios to help in designing your own environment.
- Database specifications for detailed information on the
database tables WebSphere Process Server requires to hold, store and track
information. You can create some of these database tables during profile creation
or you can choose to create them separately using scripts.
- Scripts for configuring DB2 on a remote z/OS server for the locations of default
scripts you or your database administrator can use to create the databases
and storage groups needed when using DB2 on a remote z/OS machine.
Last updated: Wed 01 Nov 2006 07:47:12
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)