Learn how to create a custom profile and choose cluster
members within an existing deployment environment.
About this task
This topic assumes that you want to create a custom profile
and choose cluster members within an existing deployment environment.
As a result of following the procedure in
Installing WebSphere ESB with a deployment environment interactively, you are viewing the Deployment
manager connection panel. Perform the following steps to complete
your installation.
Procedure
- On the Deployment manager connection panel,
specify the host name or IP address and SOAP port of the deployment
manager that has the deployment environment to which you want to add
clusters. Also supply an authentication user ID and password (administrative
security is always enabled on the deployment manager of a deployment
environment). Then click Next. The
deployment manager must be a WebSphere ESB deployment
manager at the same version level or higher as the custom profile
you are creating.
To find the SOAP port number of the deployment manager,
open the AboutThisProfile.txt file for the deployment manager located
in profile_root/logs/, and review the value for
"SOAP connector port."
The installation wizard verifies that
the deployment manager exists, can be contacted, that the authentication
user ID and password are valid for that deployment manager, and that
it has a deployment environment defined.
The Cluster and database
configuration (part 1) panel is displayed, which identifies the deployment
environment pattern of the deployment manager.
- On the Cluster and database configuration panel
(part 1), 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 the installation wizard identified 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 messaging engines 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 Cluster and database configuration (part 2) panel
is displayed, which identifies the database used by the deployment
manager.
- On the Cluster and database configuration (part 2) panel,
indicate the location of the JDBC driver classpath files (or accept
the default), and click Next.
The
Installation summary panel is displayed.
Note: An integrated
installation package (IIP) containing WebSphere Application Server Network Deployment
and Feature Pack for Web Services is installed as part of the WebSphere Process Server installation.
If IIP validation fails, an error panel displays and provides information
on how to correct the problem.
- In the Installation summary panel, review the
components that will be installed, the amount of space they will consume,
and where they will be located on the system, and click Next to
install or Back to change your specifications.
The installation wizard creates the uninstaller program
and shows a progress panel to indicate that components are being installed.
If
you chose to install
WebSphere ESB over
an existing version of WebSphere Application
Server Network Deployment with Web Services Feature Pack, the installation
wizard examines it and takes one of the following actions:
- If the installation is at the correct service level, the installation
wizard does nothing.
- If the installation is at an earlier service level, the installation
wizard applies the necessary fixes to bring the installation up to
the appropriate level and also applies any necessary interim fixes.
Restriction: If the WebSphere Application Server Network Deployment
with Web Services Feature Pack installation is at an earlier service
level and the
WebSphere ESB installation
is being done remotely from a Windows® client,
then the WebSphere Application
Server Network Deployment with Web Services Feature Pack needs to
be updated using a local silent install from the i5/OS® system before continuing with this installation.
- If you selected the WebSphere ESB Samples
feature, and you are installing over an installation of WebSphere Application Server Network Deployment
with Web Services Feature Pack that does not have its Samples gallery
feature installed, the installation wizard adds the Samples gallery
feature silently to the WebSphere Application
Server Network Deployment with Web Services Feature Pack installation.
Restriction: On i5/OS platforms: If you selected the
WebSphere ESB Samples
feature and you are installing over an installation of WebSphere Application Server Network Deployment
with Web Services Feature Pack that does not have the Samples gallery
feature installed, then the Samples Gallery feature needs to be added
to WebSphere Application
Server Network Deployment with Web Services Feature Pack using a local
silent installation from the i5/OS system
before continuing with this installation.
If you chose to install WebSphere ESB over
an existing version of WebSphere Application
Server Network Deployment, the installation wizard first installs
the Web Services Feature Pack and then takes one or more actions mentioned
above to bring the installation up to the appropriate level.
At
the end of the installation, the Installation results panel is displayed
with a Success indication.
Attention: If errors are detected during
installation, other messages might appear in place of Success.
A
message of
Partial success indicates that the
installation completed but errors were generated. If an installation
is partially successful, the Installation results panel identifies
the exact log files required to troubleshoot the problems, together
with their locations in your installation. The log files include the
following:
- install_error.log
- log.txt
See descriptions of these log files in Installation and profile creation log files.
See descriptions of relevant log files in Installation and profile creation log files.
You can review other useful
troubleshooting information in the following topics:
- Ensure that the check box to launch the First steps console
is selected, and click Finish to close the installation wizard
and start the First steps console.
Results
If the Installation results panel indicates
Success,
the components you selected were installed successfully, and your
deployment environment was updated successfully. The custom profile
was federated to the running deployment manager of the deployment
environment.
What to do next
Install the most recent
WebSphere ESB fix
pack on top of the installation (if any fix packs exist at the time
of installation). For information about installing fix packs on
WebSphere ESB, see
the instructions on the support pages at
http://www.ibm.com/software/integration/wsesb/support/.

On Linux and UNIX, platforms: If you removed
the freeware directory from your PATH (instructed
in an earlier topic), add the freeware directory
back to the PATH variable.
If the WebSphere ESB deployment
manager is not already running, start it from its First steps console
so you can add additional clusters to the deployment environment.
After the deployment manager is started, you can administer the nodes
that belong to that cell.