A custom profile is an empty node that you must federate into a
deployment manager cell to make operational. In contrast to a stand-alone
server profile, a custom profile does not have a default server on its node.
Nor are there any default applications on the custom node. Federating the
custom profile changes it into a managed node. After federation, a custom
profile has a nodeagent process but does not have a server process. You must
use the administrative console of the deployment manager to customize the
empty node for production or other uses. After you start the nodeagent, it
responds to commands from the deployment manager. You can augment an existing WebSphere Application Server Network Deployment
custom profile into a WebSphere ESB custom
profile using the Profile wizard graphical user interface (GUI).
Before you begin
Before using this procedure:
- Ensure you have an existing installation of WebSphere ESB.
- Ensure you want to augment an existing WebSphere Application Server Network
Deployment custom profile to a WebSphere ESB custom
profile and that you want to do so interactively. If your plan does not meet
these criteria, see Creating and augmenting profiles using the Profile wizard for
descriptions of other documented profile creation or augmentation procedures.
- Ensure you have enough disk and temporary space to augment the profile.
Profile |
Required disk space |
Required temp space |
Deployment manager profile |
30 MB |
40 MB |
Custom profile |
10 MB |
40 MB |
Application server profile |
200 MB |
40 MB |
- If you have enabled global security on your installation of WebSphere ESB orWebSphere Application Server Network
Deployment ensure you disable it before creating the profile. For information
on enabling and disabling global security, see Setting up WebSphere ESB security.
- Determine if the custom node you want to augment has already been federated
to a deployment manager:
- If the custom node you want to augment has already been federated to a
deployment manager, you cannot augment it to a WebSphere ESB profile.
- If the custom node you want to augment has not already been federated
to a deployment manager, when you do federate it, the following must be true
of the deployment manager with which it is to be federated, in order for the
augmentation to complete successfully:
- It must be running.
- It must use the default SOAP JMX connector type and the connector must
be enabled.
- It must have already been augmented into a WebSphere ESB profile.
Why and when to perform this task
Use the following procedure to augment an existing WebSphere Application Server Network
Deployment custom profile into a WebSphere ESB custom
profile.
Steps for this task
- Log on as root on a Linux or UNIX system, or as a member of the
Administrator group on a Windows system.
- Start the WebSphere ESB Profile
wizard to create a new runtime environment.
See Starting the Profile Wizard for descriptions of ways to start the Profile
wizard on various platforms.
The system starts InstallShield
Multiplatform to run the Profile wizard and the Welcome panel is displayed.
- Click Next.
If
an unfederated WebSphere Application Server Network
Deployment profile exists for augmentation, the Existing Profile Detection
panel is displayed. Select Augment an existing WebSphere Application Server profile and
click Next.
The Profile Type Selection panel
is displayed.Important: If an Existing Profile Detection panel
is not displayed, no profile exists for augmentation. In this case, do not
follow this procedure. Instead, cancel the augmentation and review the profile
creation procedures described in
Creating and augmenting profiles using the Profile wizard.
- Select Custom profile,
then click Next. The Custom Profile Augmentation
Considerations panel is displayed.
- Review the conditions and click Next.
The
Profile Augmentation Selection panel is displayed.
- Choose the profile you want to augment from the drop-down list
and click Next.
The list includes only those profiles
of the type selected. Only unfederated profiles are displayed as selections.
The Profile Summary panel is displayed.
- Review the profile characteristics
on the Profile Summary panel and click Next to augment the profile
or Back to change the characteristics of the profile.
The
Profile wizard shows a progress panel to indicate that the profile is being
augmented. If no errors are detected, the Profile Augmentation is Complete
panel is displayed at the end of the process.
The Profile wizard shows
a progress panel to indicate that the profile is being augmented. If no errors
are detected, the Profile Augmentation is Complete panel is displayed at the
end of the process.
Attention: If errors are detected during
profile augmentation, other panels might be displayed in place of the Profile
Augmentation is Complete panel. Examples include the following:
- Profile Augmentation is Complete With Warnings panel, which indicates
that a profile was augmented but warnings were generated.
- Profile Augmentation is Incomplete panel, which indicates that a profile
was augmented but exists in an unusable state.
- Profile Augmentation Failed panel, which indicates that a profile was
unable to be augmented.
Each of these panels identifies the log file which contains more details
to help you resolve the errors.
- Ensure the check box to launch the First steps console is selected
and click Finish to close the Profile wizard and start the First steps
console.
Result
A WebSphere Application Server Network
Deployment custom profile is now successfully augmented into a WebSphere ESB custom
profile. The node within the profile is empty until you federate the node
and use the deployment manager to customize the node.
What to do next
You can now federate the node into the deployment manager cell. For
further information about federating nodes, see
Federating custom nodes to a deployment manager.