Create a Deployment Environment

Use this page as the first step to configure your deployment environment. The deployment environment includes the application deployment target for your applications and all other clusters needed to support the application deployment target. Use this page to create a deployment environment based on one of the IBM-supplied patterns.

To view this administrative console page, select Servers > Deployment Environments > New.

The following options are available on this page:
Deployment environment name
Specifies the name used to identify the deployment environment you are creating. If a design exists with the same name, you receive a warning and are prompted to supply a unique name for the deployment environment. Use a short and concise name to identify the created clusters and to ensure that the named resources are not too long.
Deployment environment administrator user name
Specifies the administrator user name for managing the deployment environment. It is recommended to use a different administrator for each deployment environment and also the cell administrator.
Password
Specifies a password for the deployment environment administrator.
Confirm password
A password check for the deployment environment administrator. This must be the same as the deployment environment administrator password you specified.
Virtual host
Specifies a virtual host to map to all web modules of the IBM BPM applications in the deployment environment. The default selection is (none).
IBM BPM Deployment Environment Type
Specifies features for the deployment environment. Features represent the runtime processing capabilities of your deployment environment. The features that display on this page are based on the configuration of the deployment manager profile.

The following options are available based on your installation:

For IBM® Business Process Manager Advanced
  • Advanced Process Center: For storing, testing and administering process applications and toolkits that are authored in Process Designer and Integration Designer.
  • Advanced Process Server: For running processes, services and modules contained in process applications that are deployed from the Advanced Process Center, or for running SCA modules deployed directly.
  • Standard Process Center: For storing, testing and administering process applications and toolkits that are authored in Process Designer.
  • Standard Process Server: For running processes and services contained in process applications that are deployed from the Standard Process Center.
  • Advanced-only Process Server: For running SCA modules only. You deploy these modules from the command line or the WebSphere administrative console. This server is the IBM BPM equivalent of IBM WebSphere Process Server.
For IBM Business Process Manager Advanced-only Process Server
  • Advanced Process Server: For running processes, services and modules contained in process applications that are deployed from the Advanced Process Center, or for running SCA modules deployed directly.
  • Standard Process Server: For running processes and services contained in process applications that are deployed from the Standard Process Center.
  • Advanced-only Process Server: For running SCA modules only. You deploy these modules from the command line or the WebSphere administrative console. This server is the IBM BPM equivalent of IBM WebSphere Process Server.
For IBM Business Process Manager Standard
  • Standard Process Center: For storing, testing and administering process applications and toolkits that are authored in Process Designer.
  • Standard Process Server: For running processes and services contained in process applications that are deployed from the Standard Process Center.
Deployment Environment Patterns
Specifies a pattern that provides the topological characteristics of the deployment environment.
The following patterns are available:
  • Application, Remote Messaging, Remote Support

    Use this pattern when you have separate clusters each for application deployment, remote messaging, and remote support.

  • Single Cluster

    Use this pattern when the application deployment target includes the messaging infrastructure and supporting applications. This is the default pattern for a z/OS installation.