You can create a custom profile (with customized configuration
values) to be used in an existing deployment environment pattern.
Use the instructions in this topic to learn how to use the Profile
Management Tool to create and configure a WebSphere® ESB profile.
About this task
Select the
Deployment environment profile
creation or augmentation 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, and host. You must specify how to federate
the node to an existing deployment manager, which has a deployment
environment pattern already defined. You can also specify the clusters
to define on that deployment environment, as well as your own values
for the Common database configuration.
As a result of following
the procedure in either Augmenting profiles using the Profile Management Tool or Creating profiles using the Profile Management Tool, you are viewing either
the Federation panel or the Profile name and location panel. Complete
the following steps to configure a new custom profile with customized
configuration values for a deployment environment.
Procedure
- The panel you see in the Profile Management Tool depends
on whether you are creating or augmenting a profile.
Task |
First step |
Deployment environment profile augmentation |
The Federation panel is displayed. Proceed to step 4. |
Deployment environment profile creation |
The Profile name and location panel is displayed. Proceed
to step 2. |
- For Deployment environment profile creation
only: 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. The default directory is dependent on the platform:
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 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.
The Profile Management Tool detects ports
currently used by other WebSphere products,
but not those of other applications that might use specified ports.
When federating a custom profile, the addNode command uses
non-conflicting ports. This means that you can take the default port
assignments as you create the profile, and let the addNode command
specify non-conflicting ports as you federate the node. Port assignments
must be unique on a server. Server processes on different servers
can use the same port assignments without conflict.
- 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 and
host names panel is displayed.
- For Deployment environment profile creation only: In
the Node and host names panel, specify the node and host names for
the profile, 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 and host.
The Federation panel is displayed.
- In the Federation panel, you must federate
the node into the deployment manager now as part of the profile creation
or augmentation. The Federate this node later check
box does not appear on the Federation panel for this type of profile
creation or augmentation. Specify the host name or IP address
and SOAP port of the deployment manager, and an authentication user
ID and password. Then click Next.
To find the SOAP port number of the deployment manager,
go to the dmgr_profile_root/logs directory
for the deployment manager associated with this custom profile. In
this directory, open the AboutThisProfile.txt file and find the value
for the entry "Deployment manager SOAP connector port:".
The
Profile Management Tool verifies that the deployment manager exists
and can be contacted, and that the authentication user ID and password
are valid for that deployment manager. It also validates that there
is a valid deployment environment defined on the deployment manager,
and retrieves the pattern and database type back from the deployment
manager.
Important: Do not federate the node if any
one of the following is true:
- You plan to use this custom node as a migration target.
- Another profile is being federated. (Node federation must be serialized.)
- The deployment manager is not running or you are not sure if it
is running.
- The deployment manager has not yet been augmented into a WebSphere ESB deployment
manager.
- The deployment manager is not at a release level the same or higher
than that of the custom profile you are creating or augmenting.
- The deployment manager does not have a JMX administrative port
enabled.
- The deployment manager is reconfigured to use the non-default
remote method invocation (RMI) as the preferred Java™ Management Extensions (JMX) connector.
(Select System administration > Deployment manager > Administration
services in the administrative console of the deployment manager
to verify the preferred connector type.)
If you attempt to federate a custom node when the deployment
manager is not running or is not available for other reasons, a warning
panel prevents you from continuing. If this warning panel appears,
click OK to exit from it, cancel this profile
creation or augmentation, and make the necessary changes to your system.
The
next step depends on whether you are creating or augmenting a profile.
Task |
Next step |
Deployment environment profile creation |
The Port values assignment panel is displayed. Proceed to
step 5. |
Deployment environment profile augmentation |
The Deployment environment configuration panel is displayed.
Proceed to step 6. |
- For Deployment environment profile creation
only: 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:
- The ports are assigned to a profile created under an installation
performed by the current user.
- The ports 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 succeeding 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 Deployment environment
configuration panel is displayed.
- In the Deployment environment configuration
panel, select at least one cluster to assign this node to on the deployment
environment pattern and click Next. The
panel offers one to three clusters based on the deployment environment
pattern defined previously on the deployment manager:
Table 1. Clusters offered per deployment environment
pattern on existing deployment managerDeployment environment pattern on deployment
manager |
Clusters offered |
Remote messaging and remote support |
- Application deployment target: consists
of a cluster to which user applications need to be deployed.
- Messaging infrastructure: consists of a
cluster where messaging engines are located.
- Support infrastructure: consists of a cluster
that hosts the Common Event Infrastructure server and other infrastructure
services that are used to manage your system.
|
Remote messaging |
- Application deployment target: consists
of a cluster to which user applications need to be deployed. With
a remote messaging deployment environment pattern, the application
deployment target cluster also assumes the functionality of the supporting
infrastructure cluster.
- Messaging infrastructure: consists of a
cluster where bus members are located.
|
Single cluster |
- Application deployment target: consists
of a cluster to which user applications need to be deployed. With
a single cluster deployment environment pattern, the application deployment
target cluster also assumes the functionality of the messaging and
the supporting infrastructure clusters.
|
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 need to understand the functionality
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.
The Database configuration panel is displayed.
- In the Database configuration panel, perform
the following steps:
- Review the database product. The database that matches the database
used on the deployment manager to which this custom profile will be
federated is displayed.
Note: DB2® UDB for iSeries® (Native) and DB2 for i5/OS® (Native)
can be accessed locally on i5/OS platforms.
Derby Network Server, DB2 UDB
for iSeries (Toolbox), and DB2 for i5/OS (Toolbox) can be accessed both locally
and remotely. All other databases can still be used by i5/OS systems, but only as remote databases.
- Provide the location (directory) of the JDBC driver class path
files for the database. You can accept the default values for Derby
Network Server and DB2 Universal Database™.
- Click Next.
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.
- In the Profile complete panel, select Launch
the First steps console, Create another profile,
or both; click Finish to exit. Use
the First steps console to access product documentation. Use the Create
another profile option to restart the Profile Management
Tool to create additional profiles.
Results
You have completed one of the following tasks:
- Created a WebSphere ESB profile.
- Augmented a WebSphere Application
Server, WebSphere Application
Server Network Deployment, profile
into a WebSphere ESB profile.
What to do next
Use the deployment manager to customize the node. You
might add more custom nodes if not all of the cluster members are
assigned.