Creating the Advanced-only Process Server deployment environment

Create an Advanced-only Process Server deployment environment if you only want function that is equivalent to WebSphere® Process Server or WebSphere Enterprise Service Bus. You can run SCA modules that are created in Integration Designer. You can deploy the modules either from the command line or from the WebSphere administrative console.

Complete the following steps to create the deployment environment.

1. From the administrative console, navigate to the Deployment Environments page by clicking Servers > Deployment Environments.
2. Launch the Deployment Environment wizard by clicking New on the Deployment Environments page. The Create new deployment environment page is displayed.
   Note: The database provides isolation of internal groups, such as administrators. If the database is shared by two deployment environments, one administrators group is shared between them. When such a situation occurs, both administrators are able to login as administrator for each of the deployment environment.
   1. Enter a unique name for the deployment environment in the Deployment environment name field.
   2. Enter a user name for the deployment environment administrator in the Deployment environment administrator user name field.
      Note: It is recommended to use a different administrator for each deployment environment and also the cell administrator.
   3. Enter a password for the deployment environment administrator in the Password field.
   4. Reconfirm the password in the Confirm password field.
   5. Optional: In the Virtual host list, select a virtual host to map to all web modules of the IBM BPM applications in the deployment environment. The default selection is (none).
3. From the IBM BPM Deployment Environment Type section, select Advanced-only Process Server. Features represent the runtime processing capabilities of your deployment environment.
4. From the Select the deployment environment pattern section, select a pattern for the deployment environment and click Next to display the Select Nodes page. The available patterns are:
   • Single Cluster: The application deployment target includes the messaging infrastructure and supporting applications.
   • Application, Remote Messaging, Remote Support: A separate cluster each for application deployment, remote messaging, and remote support.
5. On the Select Nodes page, select the nodes that you want to include in this deployment environment, then click Next to display the Define Clusters page.

   Select nodes that have the required capabilities for the environment you selected on the IBM BPM Deployment Environment Features section.

   Select at least one node for the deployment environment. For high-availability and failover environments, select at least two nodes. For scalability, you can add more nodes.

6. On the Define Clusters page, assign the required number of clusters for each node and click Next to display the Customize Cluster Name and Ports page.

   By default one cluster member is assigned on each node for each function. You change the number by replacing the number in each column. If you are unfamiliar with the different cluster roles and functions provided by each type of cluster, see "Topology types and deployment environment patterns."

   A 0 (zero) value for a node means that the node does not contribute to the selected function, based on features that you have selected.

7. On the Customize Cluster Name and Ports page, customize the cluster names or cluster member names for the cluster type. You can use the default values provided, or customize the cluster details, and click Next.
   Note: You can specify the starting port for the cluster members. The system generates default values for cluster member names and the starting port.

   Ensure that the starting port numbers you specify are at least 20 ports apart. Port numbers are reserved and assigned to each node for the cluster members using the port number that is specified. If you specify an initial port when you create the deployment environment, that same initial port specified would be assigned to the cluster member. For example, if the port number for the first cluster member is 2000, it would use the port numbers 2000, 2001, 2002, and so on. The port number of the second cluster member would be 2020 and the port numbers would be 2020, 2021, 2022, and so on. The port number of the third cluster member would be 2040.

   If there is already a node on that physical system then there may be port conflicts and these must be resolved manually by changing the port values.

   If you use additional servers with unique ports, WebSphere Application Server does not automatically configure the virtual host for the server. Specifically, WebSphere Application Server does not automatically add the host alias ports to a virtual host. However, you can use the administrative console to add a new host alias for each of the ports that are used by the new server. For more information, see the WebSphere Application Server documentation about configuring virtual hosts.

8. Required: On the Configure Databases page, select DB2 On ZOS, configure the database parameters for data sources of the deployment environment, click Test connection, and after the connection succeeds click Next to go to the Summary page.
   On this page, define the database information for the components that are included in this deployment environment. Where possible, the wizard supplies default information for the parameters, but change those values to match the values that you defined when you planned the environment.

   Important: The databases specified in this panel need to be created by the DB2 z/OS System Administrator.

   • Shared parameters
     • User name: Type the user name to connect to the database.
     • Password: Type the password for the user name.
     • Confirm password: Type to confirm the password for the user name.
     • Server: Type a server name where the database subsystem is located.
     • Port: Type the port number to connect to the database subsystem.
     • Database connection location: Type the database connection location name.
     • Storage group: Type the storage group name.
     • Volume Catalog: Type the volume catalog name.
     • Buffer pool of 4k size: Type a name for the buffer pool with size 4k.
     • Index buffer pool : Type the index buffer pool name.
     • LOB buffer pool : Type the LOB buffer pool name.
     • Buffer pool of 8k size: Type a name for the buffer pool with size 8k.
     • Buffer pool of 16k size: Type a name for the buffer pool with size 16k.
     • Buffer pool of 32k size: Type a name for the buffer pool with size 32k.
   • cellDB
     Note: The cellDB option is only visible when you create the first advanced deployment environment. After this, every advanced deployment environment that you create shares the cellDB of the first environment.
     • Name: Type a name for the cell database.
     • Schema name: Type the schema name for the cell database.
   • Common database
     • Name: Type a name for the common database which is used for CommonDB components, Business Space, Business Process Choreographer, and Messaging.
     • Schema name: Type the schema name for the common database.
   • Select the databases that you want to separate from the Common database.
     • Messaging: Select this option to create a separate messaging engine database.
       • Name: Type a name for the messaging engine database.
       • Schema name: Type the schema name for the messaging engine database.
     • Business Process Choreographer: Select this option to create a separate Business Process Choreographer database.
       • Name: Type a name for the Business Process Choreographer database.
       • Schema name: Type the schema name for the Business Process Choreographer database.
   Attention: The default schema names that are displayed on this page might conflict with your site naming convention or might conflict with existing schemas. As such, it is likely that you will need to change the schema name. Pay close attention to the values specified to avoid potential naming conflicts.

   You can edit all key parameters, such as the database name, whether or not to create tables, the data source runtime user name, and the password for the deployment environment. You can select which database to use for the given component.

   Tip: Steps that cannot be completed through the Deployment Environment wizard, and which need to be completed manually, are listed on the Deferred Configuration page. You can view this page after you have created your deployment environment. To view this administrative console page, click Servers > Deployment Environments > Deployment environment name > Deployment Environment Configuration > Additional Properties > Deferred Configuration.
9. Verify that the information on the Summary page is correct and perform the following substeps:
   1. Optional: If you want to exit without generating the configuration, click Cancel.
   2. Optional: If you want to save the environment configuration to configure a similar Deployment Environment, click Export for Scripting.
   3. If you are satisfied with the deployment environment configuration, click Generate Deployment Environment to save and complete the configuration of the deployment environment. This will also generate a properties file in the BPM_Install_Root/logs/config folder on the deployment manager machine with a timestamp in the file name, bpmconfig-de_name-timestamp.properties. Save this file for future reference or for troubleshooting any issues.