Learn how to use the Profile Management Tool to create
and configure a WebSphere® ESB deployment manager profile using default configuration
values.
About this task
Selecting the Typical profile creation
or augmentation option creates or augments a profile with default
configuration settings. In this type of configuration, the Profile
Management Tool assigns default values to ports, to the location of
the profile, and to the names of the profile, node, host, and cell.
The administrative console is installed. You can optionally enable
administrative security (unless you are augmenting a profile that
has security enabled – then you must re-enter the administrative user
ID and password of that profile to augment it to a WebSphere ESB profile). If your operating system and the privileges
of your user account permit, the tool creates a system service to
run the server. The Common database configuration is set to Derby
Network Server.
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 the Administrative
security panel or the Profile summary panel. Complete the following
steps to configure a new deployment manager profile using default
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.
If you are performing |
First step |
Typical profile augmentation and
administrative security is enabled on the profile you are augmenting. |
The Administrative security panel is displayed. Proceed to
step 2. |
Typical profile augmentation and
administrative security is not enabled on the profile you are
augmenting. |
The Profile summary panel is displayed. Proceed to step 3. |
Typical profile creation |
The Administrative security panel is displayed. Proceed to
step 2. |
- 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 click Security > Business Integration Security.
If
you are augmenting a profile and see this panel, the profile you are
augmenting has security enabled. You must re-enter the administrative
user ID and password for that profile.
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 start the server. 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 Network Deployment profile into a WebSphere Enterprise Service Bus profile.
The node defined by the profile has a deployment manager
named Dmgr.
What to do next
Check the 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 desire
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 on planning your installation
and on the databases required by WebSphere ESB, see
the topics under Planning for WebSphere ESB.