A stand-alone server profile has its own administrative console
and all of the sample applications (if you installed the Sample applications
gallery feature). Each stand-alone server is fully operational and is managed
independently from all other such servers You can augment an existing WebSphere Application Server or WebSphere Application Server Network
Deployment stand-alone server profile into a WebSphere ESB stand-alone
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 stand-alone
server profile to a WebSphere ESB stand-alone
server 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 or WebSphere
Application Server ensure you disable it before creating the
profile. For information on enabling and disabling global security,
see Configuring
global security.
Why and when to perform this task
Use the following procedure to augment an existing WebSphere Application Server or WebSphere Application Server Network Deployment stand-alone
server profile into a WebSphere ESB stand-alone
server 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 the many 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
a WebSphere Application Server or WebSphere Application Server Network Deployment profile
exists for augmentation, the Existing Profile Detection panels 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.
Cancel the augmentation and review the profile creation procedures described
in
Creating a new WebSphere ESB stand-alone server profile.
- Select Augment an existing WebSphere Application Server profile and
click Next. The Profile Type Selection panel is displayed.
The
list of profile types will include only those types which have valid WebSphere Application Server Network
Deployment profiles that can be augmented into WebSphere ESB profiles.
- Select Stand-alone WebSphere ESB profile,
then 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.
The Service Component Architecture
Configuration panel is displayed.
- Choose whether to configure
the service integration bus in a secured mode. To configure the service integration
bus in a secured mode, perform the following steps:
- Select the check box next to Configure the service integration
bus in a secured mode.
- Enter the user ID and password, and confirm the password, used
to authenticate with a secured service integration bus.
- Click Next.
To not configure the service integration bus in a secured
mode, leave the check box clear and click Next.
The
Common Event Infrastructure Configuration panel is displayed.
- Configure the Common Event Infrastructure by performing the following
steps. (All fields on this panel are mandatory. If you do not want
to use the Common Event Infrastructure, enter dummy values for the user ID
and password, and accept the default values for the server and database.)
- Enter the user ID and password, and confirm the password, used
to authenticate with the WebSphere Messaging queue manager.
- Accept the default value of server1 for WebSphere
server name.
- Choose the database product you want to use for your configuration,
or accept the default value of Cloudscape V5.1.1.
- Click Next.
One of the following panels is displayed:
- If you accept the default value of Cloudscape V5.1.1,
the Profile Summary panel is displayed. In this case, proceed to Step 10.
- If you select any other database, the Additional Database Configuration
Information for Common Event Infrastructure panel is displayed, with fields
specific to the database you have selected. In this case, proceed to Step
9.
- On the Additional Database Configuration
Information for Common Event Infrastructure panel, complete the fields as
detailed in Additional database configuration information for Common Event Infrastructure. Return to this step when
you have followed the instructions in that topic.
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.
Attention: If
errors are detected during profile augmentation, other panels might be displayed
in place of the Profile Augmentation is Complete panel. For example:
- 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 to 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 or WebSphere Application Server Network Deployment stand-alone
server profile is now successfully augmented into a WebSphere ESB stand-alone
server profile.
What to do next
Check server operation by selecting
Start the server from
the First steps console. An output window opens. If you see a message similar
to the following, your server is operating properly:
ADMU3000I: Server server1 open for e-business; process id is 3348
You can also check server operation by running the Installation
Verification Test (IVT) from the First steps console to verify that your installation
is operating properly.