Use this scenario when you need an isolated environment
but cannot use a default single server environment because of your
business requirements.
Before you begin
- Design your deployment environment.
- Make sure that you can satisfy all of your business requirements
with a single server.
- Familiarize yourself with the concept of a stand-alone profile.
About this task
You have a design that requires you
install a default single server environment to meet your needs.
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.
- 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 and configure
the server.
You can create and configure the server
while installing the software or you can create and configure the
server using the Profile Management Tool. You can also use the administrative
console to create and configure the server. Experienced installers
can also use scripts to handle these tasks. Understand the benefits
and drawbacks of all methods before making a choice.
- 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 the software.