After designing a deployment environment, you will perform
specific tasks to make that design a reality. Regardless which method
you use to implement the deployment environment, you will perform
the same general steps.
Before you begin
- Plan your topology and record the decisions you make about:
- The servers and clusters involved.
- The number of databases required.
- Which database tables belong in which databases
- Any required userids and authentication roles
- What function each cluster involved in the deployment environment
provides
- Which method you are using to implement the deployment environment
- Make sure the systems on which you are installing the product
meet the hardware and software requirements.
- Prepare the operating system for installation.
- Synchronize the system clocks on all the servers. When adjusted
for the same time zone, the clocks must be within five minutes of
each other.
- Make sure all servers involved in the topology can be located
by both IP address and Domain Name Server (DNS) name.
- Make sure you have a user ID that has the appropriate authority
to create directories and files on all systems.
- Make sure you perform any other preparation that might be needed
to coexist with other products and provide any needed redundancy.
About this task
Now that you have completed planning your deployment environment
and performed all the prerequisite tasks, install and configure the
servers and clusters involved in your design. Regardless of the method
you choose to implement the deployment environment, the following
steps outline creating a single cell of that design.
Note: This procedure
covers all of the steps required to implement a deployment environment
and the order might differ slightly depending on your installation
method.
Procedure
- Install the product binaries on all systems involved in
the deployment environment and verify that the software is correctly
installed.
- Create the deployment manager.
- Start the deployment manager.
- Create as many managed nodes as you need.
- Federate the nodes from step 4 to the deployment manager
created in step 2.
- Configure the cell.
Important: The
configuration can take a long time depending on your deployment environment.
To prevent the process from timing out, set the SOAP request timeout
on the deployment manager to a large value, for example 1800 seconds.
See "Java™ Management Extensions
connector properties" in the WebSphere® Application Server information
center.
This involves creating the clusters to perform the
functions you defined to them in your design and then adding members
to those clusters.
If your design implements a patterned deployment
environment, the system creates all needed clusters and defines cluster
members to provide all necessary functions. Depending on the pattern
you selected, this includes clusters for application deployment, messaging
support and infrastructure support.
If your design implements
a custom deployment environment, you must create all the clusters
needed to provide the necessary functions. These functions include
messaging support for application deployment, application support
and Common Event Infrastructure support.
- Configure the databases or database tables required for
your topology, if you chose deferred table creation.
Configuration
consists of running the scripts generated by the deferred option.
- Configure the common database tables. This table is in the common database.
- Configure the messaging engine database tables. This table is in the common database.
- Create the enterprise service bus logging mediation
database table. This table is in the common database.
- Configure the Common Event Infrastructure database.
- Install and configure a routing server. This
could be an IBM® HTTP server
or another server of your choosing. This server allows clients to
access the applications within this topology.
- Verify the installation by installing and running test
applications.
What to do next
- Create another cell, if desired.
- Deploy the applications that are to run in this deployment environment.