A deployment manager provides a single administrative interface
to a logical group of servers on one or more machines. This logical group
of servers is known as a cell. A deployment manager manages the configuration
for all of the managed nodes in its cell and deploys applications to any managed
node in the cell. All of the profiles in a cell share command files and other
product binaries that are created during the installation. You can create
a deployment manager profile using the Profile wizard graphical user interface
(GUI).
Before you begin
Before using this procedure:
- Ensure you have an existing installation of WebSphere ESB.
- Ensure you want to create a deployment manager profile and that you want
to do so interactively. If your plan does not meet these criteria, see Creating and augmenting profiles using the Profile wizard for descriptions
of other documented profile creation or augmentation procedures.
- Ensure you have enough disk and temporary space to create the new profile.
Profile |
Required disk space |
Required temp space |
Deployment manager profile |
30 MB |
40 MB |
Custom profile |
10 MB |
40 MB |
Application server profile |
200 MB |
40 MB |
- If you have enabled global security on your installation of WebSphere ESB, ensure you disable it before creating the profile. For information on enabling
and disabling global security, see Setting up WebSphere ESB security.
Why and when to perform this task
The Full installation procedure for WebSphere ESB creates
one stand-alone server profile named default with a server
named server1. However, to make use of the networking advantage
of the product, you can use the Profile wizard to create additional profiles.
Use
the following procedure to create a new deployment manager profile.
Steps for this task
- Log on as root on a Linux or UNIX system, or as a member of the
Administrator group on a Windows system.
- Start the WebSphere ESB Profile
wizard to create a new runtime environment.
See Starting the Profile Wizard for descriptions of the many ways to start
the Profile wizard on various platforms.
The system
starts InstallShield Multiplatform to run the Profile wizard and the Welcome
panel is displayed.
- Click Next. One
of the following panels is displayed:
- If a WebSphere Application Server or WebSphere Application Server Network Deployment
profile exists, the Existing Profile Detection panel is displayed. This procedure
assumes that you want to create a new profile, rather than augment an existing
one into a WebSphere ESB profile.
To create a new profile, select Create a new WebSphere ESB profile and
click Next. The Profile Type Selection panel is displayed.
- If no profile exists the Profile Type Selection panel is displayed.
- Select Deployment manager
profile, then click Next.
The Profile Name panel
is displayed.
- Specify a unique name for the
profile or accept the default name. If any other profiles exist, you have
the option of making this profile the default profile by selecting the check
box next to Make this profile the default. Then click Next.
Each profile that you create must have a name. When you have more
than one profile, you can tell them apart 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.
The Profile Directory panel is displayed.
- Accept the default directory
location for the profile or use the Browse button to specify another
location, then click 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 that you specified. This directory
location can be changed to any valid directory location on the system. If
the directory already exists, it must be empty or the Profile wizard will
display an error.
The Node And Host Names panel is displayed.
- Specify the node and host names for the deployment manager, or
accept the defaults, then click Next.
Use a unique name
for each node 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 and host.
The Port Value Assignment
panel is displayed.
- The Profile wizard will detect ports currently used by other WebSphere
products, but if you have other applications which use specified ports, verify
that the ports do not conflict. Click Next.
On Windows
platforms: Choose whether to run the server as a Windows service. If the profile is configured as a Windows service, the product will
attempt to start Windows services for server processes started by a startServer command.
For example, if you configure a server as a Windows service and issue the startServer command,
the wasservice command will attempt to start the defined service.
To
run the server as a Windows service, perform the following steps:
- Ensure you have selected the check box next to Run the WebSphere ESB process as a
Windows service.
- Choose to log on as either a local system account or a specified
user account.
If you choose to log on as a local system account,
you do not have to specify a user ID or password. 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.. 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.
The Profile wizard grants the user ID the advanced
user rights if it does not already have them, if the user ID belongs to the
Administrator group.
- Select the startup type (default is Manual).
- Click Next.
To not create a Windows service, clear the check box and click Next.
The Service Component Architecture Configuration panel is displayed.
- Choose whether to configure
the service integration bus in a secured mode. To configure the service integration
bus in a secured mode, perform the following steps:
- Select the check box next to Configure the service integration
bus in a secured mode.
- Enter the user ID and password, and confirm the password, used
to authenticate with a secured service integration bus.
- Click Next.
To not configure the service integration bus in a secured
mode, leave the check box clear and click Next.
The
Profile Summary panel is displayed.
- Review the profile characteristics
and click Next to create the profile or Back to change the characteristics
of the profile.
The Profile wizard shows a progress panel to
indicate that the profile is being created. If no errors are detected, the
Profile Creation is Complete panel is displayed at the end of the process.
Attention: If errors are detected during profile creation, other panels
might be displayed in place of the Profile Creation is Complete panel, for
example:
- 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 not
created.
Each of these panels identifies the log file which contains more details
to help you to resolve the errors.
- Ensure the check box to launch the First steps console is selected
and click Finish to close the Profile wizard and start the First steps
console.
Result
A new 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
You can also check server operation by running the Installation
Verification Test (IVT) from the First steps console to verify that your installation
is operating properly.