Use this scenario when you have quality of service requirements
or need a more complex deployment environment than those defined by
the IBM-supplied patterns.
Before you begin
Important: Installing a custom deployment environment
is more complicated than installing a default deployment environment
and requires a understanding of network deployment, clustering and
other WebSphere® Process Server features. IBM® recommends that you plan and
implement each portion of the deployment environment separately and
gradually.
Familiarize yourself with the information
about these topics and any related topics, if you have not done so
already.- Servers
- Clusters
- Profiles
- Custom deployment environments and their functions
Diagram what hardware you are using for your
deployment environment and indicate what server each piece of equipment
hosts. Also indicate which servers will provide the deployment environment
functions so you have a clearer idea of how to cluster the servers
together.
Your
design should specify which clusters provide messaging, Common Event
Infrastructure and application support for the deployment environment.
About this task
When your design does not match any of the IBM-supplied patterns
or when you want to expand an existing deployment environment use
these steps. Consider using an iterative method so that you are only
adding, configuring and verifying one portion of the deployment environment
at a time to minimize any complexity.
Procedure
- Select the database product to support the
deployment environment.
Some
systems, such as z/OS and i5/OS do not have automated methods to create
databases and tables for messaging engines and Common Event Infrastructure
(CEI). When creating databases for these systems, make sure you have
sufficient authorization to run database definition scripts
successfully.
Important: If
your future plans include federating this environment into a deployment
manager cell, make sure that you use a database and database drivers
that support remote access. Examples of these types of products are
Derby Network and Java toolbox JDBC.
- Decide how you create the database tables.
Either create the tables during product installation, have
the product install process create scripts to create the tables for
you, or create scripts yourself to perform this step.
- Analyze the applications that you will deploy to this deployment
environment to determine the clusters you require to support those
applications.
- Design the physical layout of the deployment environment.
- Map the servers as members of the cluster
that provides the function you identified in your design.
You
decide on the functions the deployment environment delivers and which
nodes are involved with each cluster.
- Decide how clients are to access the
applications in the deployment environment.
Based
on your needs there are many ways to access including Web services
(SOAP/HTTP and SOAP/JMS), synchronous or asynchronous Service Component
Architecture (SCA) requests, Java™ Message
Service (JMS), MQ (either JMS or native), or through adapters. These
choices impact what other software and resources you must install.
- Decide how the applications access
any resources they require.
Based
on your needs there are many ways to access including Web services
(SOAP/HTTP and SOAP/JMS), synchronous or asynchronous Service Component
Architecture (SCA) requests, Java Message
Service (JMS), MQ (either JMS or native), or through adapters. These
choices impact what other software and resources you must install.
- Decide how to install the software,
create the servers and configure the created servers.
Restriction: For a custom deployment environment in a single
cell you cannot use the installer or Profile Management Tool to create
servers.
- Identify or create any user IDs with the
authorization you need to complete installation.
- Optional: Contact your database
administrators, if your site policies restrict database creation and
access to a centralized department.
Important: If
your future plans include federating this environment into a deployment
manager cell, make sure that you use a database and database drivers
that support remote access. Examples of these types of products are
Derby Network and Java toolbox JDBC.
- Schedule and coordinate the installation
of WebSphere Integration Developer and WebSphere ESB to
minimize impacts to the development community.
What to do next
Install your deployment environment.