While configuring the deployment manager, you might need
to need to specify your own settings for ports, nodes and profiles.
This topic provides instructions on how to use the Profile Management
Tool to create and configure a WebSphere® ESB deployment manager profile with customized configuration
settings.
About this task
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 optionally choose
whether to deploy the administrative console or enable 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 specify your own configuration values for the Common
database.
As a result of following the procedure in either Augmenting profiles using the Profile Management Tool or Creating profiles using the Profile Management Tool one of the following panels
is displayed, the Administrative security panel, the Database configuration
panel, or the Optional application deployment panel. Complete the
following steps to configure a new deployment manager profile with
customized configuration values.
Procedure
- The panel you see in the Profile Management Tool depends
on whether you are creating or augmenting a profile, and if you are
augmenting, on whether administrative security is enabled on the profile.
Task |
Next Step |
Advanced profile augmentation with
administrative security enabled on the profile you are augmenting. |
The Administrative security panel is displayed. Proceed to
step 5. |
Advanced profile augmentation with
administrative security disabled on the profile you are augmenting. |
The Database configuration panel is displayed. Proceed to
step 9. |
Advanced profile creation |
The Optional application deployment panel is displayed. Proceed
to step 2. |
- In the Optional application deployment
panel, select whether to deploy the administrative console to the
profile environment you are creating, then click Next.
The administrative console is a Web-based tool that manages
the server. To choose to deploy the administrative console, leave
the Deploy the administrative console (recommended) check
box selected. Clear the check box to deselect it.
The Profile
name and location panel is displayed.
- 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. If you choose not to use the default name, see Naming considerations for profiles, nodes, hosts, and cells for information
about issues you must consider when naming the profile, such as restrictions
on the length of the directory 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:
user_data_root/profiles/profile_name

install_root/profiles/profile_name
install_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 that 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 your 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 and host.
The Administrative
security panel is displayed.
- Enable administrative security.
This
screen differs depending on whether you are creating or augmenting
a profile.
If you are creating a profile, you can enable administrative
security now, or later from the administrative console. To enable
administrative security now, leave the Enable administrative
security check box selected, supply a user name and password
to log onto the administrative console, and click Next.
To disable administrative security, clear the check box. To enable
administrative security later from the administrative console, open
the console and select Security > Business Integration
Security.
If you are augmenting a profile and see
the Administrative security panel, the profile you are augmenting
has security enabled. You must reenter the administrative user ID
and password for that profile.
The next step depends on whether
you are creating or augmenting a profile.
Task |
Next step |
Advanced profile augmentation |
The Database configuration panel is displayed. Proceed to
step 9. |
Advanced profile creation |
The Port values assignment panel is displayed. Proceed to
step 6. |
- Verify that the ports specified for the
profile are unique and clickNext.
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. If
you chose not to deploy the administrative console on the Optional
application deployment panel in step 2, the administrative
console ports are not available on the Port values assignment panel.
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 8. |
On a Windows® platform
with Administrator group privileges |
The Windows service
definition panel is displayed. Proceed to step 7. |
On any other platform, or as a non-root user on a Linux or Windows platform. |
The Database configuration panel is displayed. Proceed to
step 9. |
Choose whether to run
the server as a Windows service
and click 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 (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 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 service
runs as the same user ID under which the environment variable that
specifies IPv6 is defined, instead of as Local System.
After
you have finished the Advanced profile creation the Database 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 Database configuration
panel is displayed.
- In the Database configuration panel, configure
the Common database used by the selected product components.
See
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) panels.
The Profile summary panel is displayed.
- In the Profile summary panel, click Create or Augment to
create or augment 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 one of the following tasks:
- Created a WebSphere ESB profile.
- Augmented a WebSphere Application
Server or WebSphere Application
Server Network Deployment profile into a Websphere ESB profile.
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 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 want 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.
For more
information about planning your installation and on the databases
required by WebSphere ESB,
see the topics under Introduction: Planning for WebSphere ESB.