Introduction to the commands
To create a Process Server deployment environment using the command line, there are several tools and commands provided within the installation. This section introduces these tools and commands. This section also explains how to use the DBDesignGenerator tool.
Typical production environments for Process Server will have several databases configured. These are:
- Process Server Common database holding the tables for Failed Event Manager
- Business rules, relationships, and so on
- Business Process Choreographer database for Business Process Choreographer and Human Task container
- Common Event Infrastructure database
- Messaging engine database that hosts the database schema for the standard messaging engines in Process Server
You can configure the databases along with the profile creation provided that the user has sufficient rights and privileges to perform the various database operations. Typically, this is restricted to the database administrators (DBAs). Therefore, you have the option to defer the database creation, and only generate the database scripts during profile creation. The database scripts can then be executed by the DBA to complete the requirements before the deployment manager is started.
The DBDesignGenerator tool shipped in Process Server V7.0. It is an interactive command line tool used to configure the database according to the design requirements for your environment. For the output of the tool, you get a database design file, which is used as an input file for the deployment manager profile creation, or alternatively during the deployment environment creation. The database scripts are generated at the end of the tasks, which are required to be executed to complete the database configuration. A detailed tutorial for the DBDesignGenerator tool is available in WebSphere Process Server database configuration made easy. The rest of the tutorial assumes that you have a valid design file and scripts ready.
A clustered environment requires a deployment manager profile and at least one custom profile. Ensure that these profiles use the Process Server template. Therefore, the next stage is to create these profiles on the Process Server installation. A command is available in the installation, namely “manageprofiles”.
This command is not only used for profile creation, but also for verifying, deleting, backing up, and restoring profiles. Therefore, it is important to note the various parameters that this command takes as input. A detailed overview of the command is described in this Information Center topic, manageprofiles parameters. Table 1 shows the frequently used parameters.
Table 1. Parameters for the manageprofiles command
||Creates the profile.|
||Deletes a profile. Automatically unaugments the profile, and deletes the servers within this profile.|
||Unaugments and deletes all the profiles and servers within the profile.|
||Lists all existing and valid profiles.|
||Validates and updates newly added or removed profiles to the profile registry.|
You can use the manageprofiles command along with a response file for a silent mode operation. The response file will have the parameters for the manageprofiles command typically in key and value format as shown in Listing 1.
Listing 1. Command syntax
manageprofiles –response <response file name>
For manageprofiles command examples for various database providers and various profile types, see this Information Center topic, Creating profiles using the manageprofiles command-line utility.
The deployment environment is a collection of servers or clusters based on reference patterns that helps in quickly setting up clustered topologies for Process Server. It eliminates the need for creating nodes, clusters, servers (one followed by the other), and then manually configuring Service Runtime Architecture (SCA), messaging engines, Common Event Infrastructure (CEI), and associated resources. By choosing one of the reference patterns, a clustered topology is configured on the fly. Apart from the ease in setup, deployment environments also provide an option to import or export if you want to quickly set up a topology based on an existing pattern. To learn more about deployment environments, see this Information Center topic, Deployment environments.
Commands are available to create and configure a deployment environment of any of the reference pattern types – single cluster, remote messaging, and remote messaging and remote support. There are other topologies that are possible using the deployment environment pattern, such as the double remote messaging and remote support and custom patterns. More information is available in the Resources section of the tutorial. These commands help to create the deployment environment in silent mode. The other option is using the administrative console to generate one interactively. The frequently used commands are shown in Table 2.
Table 2. Deployment environment commands
||Defines a new deployment environment based on a reference pattern. Click here to learn more.|
||Adds an application target or messaging or support nodes to a deployment environment. Click here to learn more.|
||Validates a deployment environment whether all the required constraints are met. Click here to learn more.|
||Configures the deployment environment on the deployment manager. Click here to learn more.|
||Exports topologies from a deployment manager. Click here to learn more.|
||Imports topologies to a deployment manager. Click here to learn more.|
||Starts the deployment environment. Click here to learn more.|
||Displays the current status of the deployment environment as to whether it is generated or started. Click here to know more.|
||Stops the deployment environment by stopping all the clusters. Click here to know more.|
||Deletes a deployment environment from a deployment manager without removing the configured servers or clusters. Click here to know more.|