You can deploy patterns in an environment that contains a single IBM®
PureApplication® processor. You can deploy the
predefined patterns that are available with WebSphere® Service
Registry and Repository Pattern, or deploy patterns that you created,
into the cloud.
Before you begin
To deploy a pattern, you must have either a predefined pattern, or a custom pattern with all
required components configured.
Before you deploy, also request the following details about the
environment to deploy into from your
IBM
PureApplication system administrator:
- The environment profile
- The cloud group
- The IP group
About this task
Deploying a pattern creates a virtual system or a newly provisioned
WSRR environment that is running in the cloud.
You can deploy the pattern by using the console.
Procedure
- In IBM
PureApplication V2.1, click .
- From the list of patterns on the Virtual System Patterns page, select the
pattern to deploy. The predefined WSRR patterns
that you can select are as follows:
- WebSphere Service Registry and Repository cluster -
external database
- WebSphere Service Registry and Repository cluster -
internal DB2® for AIX®
- WebSphere Service Registry and Repository cluster -
internal DB2 for Linux
- WebSphere Service Registry and Repository
stand-alone - internal DB2 for AIX
- WebSphere Service Registry and Repository
stand-alone - internal DB2 for Linux
- Click the Deploy icon.
- Complete the required fields to deploy the pattern.
- On the Deploy Pattern page, enter a meaningful name for the virtual
system.
Restriction: The maximum number of characters allowed for a name is 64.
- Enter any other required information:
- Select the environment profile that you want to use for the deployment. Internally or externally
managed environment profiles can be used for single-system deployments.
- Specify, or accept the default cloud group and IP group to deploy into. These fields are
displayed only for internally managed environment profiles.
- Set a priority for the deployment.
- Optional: Set up Secure Shell (SSH) access to the deployment either by generating an SSH
public/private key pair, or by specifying an externally generated SSH public key. The generated or
specified public key is uploaded to the virtual machines during deployment. If you generated a key
pair, be sure to download the private key file to a secure location. You can distribute this file
later to users who are allowed to access the deployed virtual machines in the cloud group for
troubleshooting and maintenance
purposes.
- Set the schedule for the deployment to be at the current time or a later time that you
specify.
- Click Pattern attributes to set parameters that can be
applied to all components in the pattern. Complete the Password fields to set
a single password at the pattern level, which can be propagated to all password fields throughout
the pattern. If you want to use different passwords, you must clone the relevant pattern and either
specify the passwords directly in the pattern, or unmap the passwords that you want to specify at
deployment time.
Also click the component names to set the parameters for
the individual software components. Components that have a blue dot next to the name contain
required parameters that you must set before the pattern is deployed.
You can accept all or
most of the default values, although you might prefer to override some of them. For example, you
might want to override the cell name or node name to conform to your site naming conventions. In
most cases, only passwords need to be additionally specified.
Important: For the cluster-based virtual system patterns with internal DB2 components, the
primary and standby DB2 passwords must be the same for each user. For example, the
Password (Fenced User) value must be the same on both the primary and
standby, but can be different from the Password (Instance Owner) value,
which itself must be the same on the primary and standby.
For more information about the
parameters in the predefined patterns, see:
- Click Quick Deploy to start the deployment process. The length of time required for the deployment to complete depends on the complexity of the
pattern being deployed.
Results
The deployment process creates and starts virtual machines for the components that are
defined, and provides links to required consoles.
What to do next
You can view the status of your instance, and begin to administer it
from the Virtual System Instances page, which you can access in IBM
PureApplication V2.1 by clicking .