You can create and configure a profile manually or you
can use the Profile Management Tool. The instructions in this topic
tell you how to use the Profile Management Tool to create and configure
a custom profile with customized configuration settings.
About this task
While configuring custom profiles, you can specify your
own values for settings such as ports, the location of the profile,
and the names for the profile, node, and host. You can choose to federate
the node to an existing deployment manager during the creation or
augmentation process, or federate it later using the addNode command.
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.
Procedure
- The panel you see in the Profile Management Tool depends
on whether you are creating or augmenting a profile.
Tasks |
First step |
Advanced profile augmentation |
The Federation panel is displayed. Proceed to step 4. |
Advanced profile creation |
The Profile name and location panel is displayed. Proceed
to step 2. |
- 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 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 machine 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 machine, 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.
- 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, choose to federate
the node into the deployment manager now as part of the profile creation
or augmentation, or at a later time and apart from profile creation
or augmentation.
- If you choose to federate the node as part of the 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
(if administrative security is enabled on the deployment manager).
Leave the Federate this node later check box
unselected. Then click Next.
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 (if it is secured).
Important: Do
not federate the custom node during
profile creation or augmentation 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, and then
make different selections on the Federation panel.
- If you choose to federate the node at a later time and apart from
profile creation or augmentation, select the Federate this
node later check box and click Next.
See Federating custom nodes to a deployment manager for
more information on how to federate a node by using the addNode command.
Read more about this command in the addNode command topic in
the WebSphere Application
Server Network Deployment, version 6.1, information center.
The next step depends on the type of profile creation or augmentation
you are performing and, in an Advanced profile creation, whether you
elected to federate the profile as part of the profile creation process.
Tasks |
Next step |
- Advanced profile creation without federating
the profile
- Advanced profile augmentation
|
The Database configuration panel is displayed. Proceed to
step 6. |
- Advanced profile creation including federating
the profile
|
The Port values assignment panel is displayed. Proceed to
step 5. |
- For Advanced 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 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 and
run the
updatePorts.ant file through the
ws_ant script.
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.
- Provide the location (directory) of the JDBC driver class path
files for the database. You can accept the default values for Derby
Network Server, DB2 Universal Database™, or Microsoft® SQL
Server Embedded.
- 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 or WebSphere Application
Server Network Deployment profile into a WebSphere Enterprise Service Bus profile.
What to do next
The node within the profile is empty until you federate
it and use the administrative console to customize it.
In a
deployment environment, you must create and configure databases, create
other 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 about the databases
required by WebSphere ESB,
see the topics under Introduction: Planning for WebSphere ESB.