You can use the Profile Management Tool to create and configure
a WebSphere® ESB deployment manager profile. Use the instructions
in this topic to configure profiles with customized configuration
values and use this profile in a new deployment environment based
on a supplied pattern.
Before you begin
This topic assumes that you are using the Profile Management
Tool to create profiles and are following the procedure in
Creating profiles using the Profile Management Tool. As a result, it is assumed
that you have started the Profile Management Tool, have chosen to
create a deployment manager profile, and have selected the
Deployment
environment profile creation option. You cannot augment
existing deployment manager profiles using the
Deployment
environment option.
About this task
Select the
Deployment environment profile
creation option to set up a fully configured profile for your deployment
environment. This option configures and installs all components needed
for
WebSphere ESB to
work. The following components are configured as part of this option:
- Common Event Infrastructure
- Service Component Architecture
In this type of configuration, you can specify your own
values for settings such as ports, the location of the profile, and
names for the profile, node, host, and cell. You can supply an administrative
user ID and password for administrative security. If your operating
system and the privileges of your user account permit, you can create
a system service to run the server. You can also choose the deployment
environment pattern to use, as well as your own values for the Common
database configuration.
As a result of following the procedure
in Creating profiles using the Profile Management Tool, you are viewing
the Profile name and location panel. Complete the following steps
to configure a new deployment manager profile with customized configuration
values for a deployment environment.
Procedure
- In the Profile name and location panel, perform
the following steps:
- Specify a unique name and directory path for the profile, or accept
the defaults.
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.
The directory you specify will contain
the files that define the runtime environment, such as commands, configuration
files, and log files. By default, this directory location is:

install_root/profiles/profile_name
install_root\profiles\profile_name
user_data_root/profiles/profile_name
where
profile_name is the name you specified. An error
message is displayed if:
- The profile_name you specify is not unique.
- The directory you specify is not empty.
- Your user ID does not have sufficient permissions for the directory.
- There is insufficient space to create the profile.
- You can make the profile that you are creating the default profile
(so commands work automatically with it) by selecting the Make
this profile the default check box. This check box appears only
if you have an existing profile on your system.
The first profile
that you create on a workstation is the default profile.
The
default profile is the default target for commands that are issued
from the bin directory in the product installation root.
When only one profile exists on a workstation, every command operates
on that profile. If more than one profile exists, certain commands
require that you specify the profile to which the command applies.
See Profile commands in a multiprofile environment for more information.
- Click Next. (If you click Back and
change the name of the profile, you might have to manually change
the name on this panel when it is displayed again.)
The Node, host,
and cell names panel is displayed.
- In the Node, host, and cell names panel, specify the node,
host, and cell names for the deployment manager, or accept the defaults
and click Next. Try to keep the node name as short
as possible, but ensure that node names are unique within the deployment
environment. See Naming considerations for profiles, nodes, hosts, and cells for
information about reserved terms and other issues you must consider
when naming the node, host, and cell.
The Administrative security
panel is displayed.
- In the Administrative security panel, supply
a user name and password to log onto the administrative console and
click Next.
Important: If
you are performing a Deployment environment profile creation, administrative
security is required.
The Port values assignment panel
is displayed.
- Verify that the ports specified for the profile
are unique and click Next.
The
Profile Management Tool detects ports currently used by other WebSphere products and displays
recommended port values that do not conflict with existing ones. If
you have applications other than WebSphere ones
that use specified ports, verify that the ports do not conflict.
Ports
are recognized as being in use if the following conditions are satisfied:
- They are assigned to a profile created under an installation performed
by the current user.
- They are currently in use.
Although the tool validates ports when you access the Port values
assignment panel, port conflicts can still occur resulting from selections
you make on subsequent Profile Management Tool panels. Ports are not
assigned until profile creation completes.
If you suspect a
port conflict, you can investigate it after the profile is created.
Determine the ports used during profile creation by examining the
following file:

profile_root/properties/portdef.props
profile_root\properties\portdef.props
profile_root/properties/portdef.props
Included in this file are the keys and values used in setting
the ports. If you discover port conflicts, you can reassign ports
manually. To reassign ports, see the topic
Updating ports in an existing profile in the WebSphere Application Server
Network Deployment, version 6.1 information center, and run the
updatePorts.ant file
through the
ws_ant script.
The next step depends on your
platform and whether you are installing as a root (Administrator)
or non-root user.
Installation Type |
Next step |
On a Linux® platform
with the Profile Management Tool running as the root user |
The Linux service
definition panel is displayed. Proceed to step 6. |
On a Windows® platform
with Administrator group privileges |
The Windows service
definition panel is displayed. Proceed to step 5. |
On any other platform, or as a non-root user on a Linux or Windows platform. |
The Deployment environment configuration panel is displayed.
Proceed to step 7. |
Choose whether to run
the server as a Windows service
and select Next. The Windows service definition panel is displayed
for the Windows platform
only if the ID that installs the Windows service
has the Administrator group privilege. If the profile is configured
as a Windows service, the
product starts Windows services
for server processes started by a
startManager command. For
example, if you configure a server 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 you must specify the startup type (the 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 Log on as a service and Act as part of the operating system.
If the user ID belongs to the Administrator group, the Profile Management
Tool grants it the advanced user rights if it does not already have
them.
During profile deletion, you can remove
the Windows service that
is added during profile creation.
IPv6 considerations
when running profiles as Windows services
Servers created to run as a Windows service fail to start when using
IPv6 if the service is configured to run as Local System. Create
a user-specific environment variable to enable IPv6. Because this
environment variable is a user variable instead of a Local System variable,
only a Windows service that
runs as that specific user can access this environment variable. By
default, when a new profile is created and configured to run as a Windows service, the service
is set to run as Local System. When the WebSphere ESB Windows service
tries to run, the service is unable to access the user environment
variable that specifies IPv6, and thus tries to start as IPv4. The
server does not start correctly in this case. To resolve the problem,
when creating the profile, specify that the WebSphere ESB Windows service
runs as the same user ID under which the environment variable that
specifies IPv6 is defined, instead of as Local System.
After
you click the Next button, the Deployment environment configuration
panel is displayed.
Choose whether to run
the server as a Linux service
and click Next. The Linux service definition panel is displayed
only if the current operating system is a supported version of Linux and the current user has
the appropriate permissions.
WebSphere ESB attempts
to start Linux services for
server processes that are started by a startManager command.
For example, if you configure a server as a Linux service and issue the startManager command,
the wasservice command attempts to start the defined service.
By
default, WebSphere ESB is
not selected to run as a Linux service.
To
create the service, the user that runs the Profile Management Tool
must be the root user. If you run the Profile Management Tool with
a non-root user ID, the Linux service
definition panel is not displayed, and no service is created.
You
must specify a user name under which the service runs.
To delete
a Linux service, the user
must be the root user or have proper privileges for deleting the service.
Otherwise, a removal script is created that the root user can run
to delete the service on the user's behalf.
The Deployment environment
configuration panel is displayed.
- In the Deployment environment configuration
panel, click the pattern to use for the deployment environment on
this deployment manager profile.
Select the radio button
beside one of the following patterns and click
Next.
- Remote Messaging and Remote Support defines
one cluster for the application deployment, one remote cluster for
the messaging infrastructure, and one remote cluster for the Common
Event Infrastructure and other supporting applications. This pattern
configures a setup that performs well for most of your business integration
needs. When in doubt, select this pattern.
- Remote Messaging defines one cluster for
the application deployment and one remote cluster for the messaging
infrastructure. The Common Event Infrastructure and other supporting
applications are configured on the application deployment target cluster.
- Single Cluster defines one cluster for
application deployment. Both messaging infrastructure and Common Event
Infrastructure with supporting applications are configured on the
application deployment cluster.
See the following topics for more information:
- Deployment environment patterns. A deployment
environment pattern specifies the constraints and requirements of
the components and resources involved in a deployment environment.
The patterns are designed to meet the needs of most business requirements
and are intended to help you create a deployment environment in the
most straightforward way.
- Deployment environment functions. To design a
robust deployment environment, you must understand the functions each
cluster can provide in a particular IBM-supplied deployment environment
pattern or a custom deployment environment. This knowledge can help
you make the correct decisions as to which deployment environment
pattern best meets your needs.
After you choose the pattern to use for the deployment
environment on this deployment manager profile, the Database configuration
panel is displayed.
- In the Database configuration panel, configure
the Common database used by all WebSphere ESB components,
including the Common Event Infrastructure
database and the system bus messaging database.
If
you want to use databases other than the Common one for these components,
you have the following options:
- Cancel this deployment environment profile creation
and instead create your deployment environment using the administrative
console. See Creating
deployment environments for more information.
- If you intend to use a different database product created by the
same database vendor, you can still proceed with this profile creation
and change the database configuration later in the administrative
console. See Configuring a JDBC provider and data source in
the WebSphere Application
Server Network Deployment, version 6.1 information center for more
information on configuring JDBC drivers and data sources.
Refer to the topic
Configuring the Common database and the Common Event Infrastructure database using the Profile Management Tool for
details and return to this step when you have completed the fields
on the Database configuration and Database configuration (Part 2)
information panels. The Profile Management Tool validates your database
configuration selections and displays a message if any are in error.
For example, if you enter a database name that already exists and
you are creating a new database, an error message informs you that
the database exists.
Restriction: Database administrator (DBA)
privileges are required for the database configuration panels that
are part of creating a deployment manager profile for a deployment
environment. If you plan to use the deployment environment feature
of the product installer or Profile Management Tool, and want to use
a database other than Derby Network Server as your database product,
the user ID you provide for the "User name to authenticate with the
database" field on the database configuration panels must have DBA
privileges.
Once
you configure the Common database, the Profile summary panel is displayed.
- In the Profile summary panel, click Create to
create the profile or Back to change the characteristics
of the profile.
When
the profile creation or augmentation is complete, the Profile complete
panel is displayed with the message The Profile Management tool
created the profile successfully or The Profile Management
tool augmented the profile successfully.
- Complete the profile configuration by doing one of the
following tasks, depending on whether you must manually configure
the Common database.
Results
You have completed created a WebSphere ESB profile.
The node within the profile has a deployment
manager named dmgr.
What to do next
Ensure that your database instance is running before starting
the deployment manager, even if the database is located locally. Then
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
Configure
custom nodes in the deployment environment to complete the deployment
environment pattern.
For more information on
planning your installation, see the topics under Planning for WebSphere ESB.