Creating the deployment environment using the configureNode command

You can use the configureNode command to create a typical network deployment environment. The goal of this command is to provide a ready-to-use environment. The only parameters that can be customized are provided in a properties file.

Before you begin

Restriction: This command is not supported if your database type is DB2® for z/OS®.

You must have installed the product and created all the databases that are specified in the properties file.

Important: You must have already installed the database software and created the databases (but do not create tables). You must also have created all the users that you specify in the properties file. Make sure the users have the installation privileges listed in Database privileges.

For your SQL Server database server:

Make sure that the username and schema exist before the configuration is done. The schema value should be the default schema for the user chosen.
If connections to the database will be made by the current Windows user that the server is running under, the SQL Server must have Windows authentication mode or SQL Server and Windows Authentication mode enabled, as specified through Microsoft SQL Server Management Studio.

Restriction: Run configureNode commands sequentially; do not try to run the command on multiple machines at the same time.

About this task

The configureNode command uses default ports to create the deployment manager. You cannot customize the ports using this command. The parameters listed in the sample files are the only parameters that can be customized. Make sure that no other profiles that are configured with default ports are started on the same machine.

The configureNode command creates the following network deployment topology:

A single cell environment
The environment contains the number of cluster members that you specify in the properties file
The environment uses the Remote Messaging, Remote Support, and Web topology pattern, which includes the following four clusters:
- Messaging infrastructure cluster
- Supporting infrastructure cluster
- Application deployment target cluster
- Web application cluster

The command performs the following tasks:

Creates the deployment manager node based on the values in the deployment manager properties file and starts the deployment manager.
Creates the deployment environment definition.
Creates a custom node based on the values in the custom node properties file.
Federates the node and adds the node to the deployment environment.
Generates the deployment environment.
Creates the database tables. (You must already have created the databases. See "Before you begin" for instructions.)
Runs the bootstrap utility to load the Process Server database with system information.
Configures Business Space and Process Portal on the web application cluster.

The default port is used to create the deployment manager if the optional ports are not specified in the properties file. If a deployment manager is already running on the machine when you run configureNode, creating the deployment environment fails. If a deployment manager has already been created but is not running, you must change the port of one of the deployment managers or you might get a port conflict error when you start the other deployment manager.

Procedure

To create the deployment environment for the first time, complete the following steps:

On the machine where you want to create the deployment environment, locate the sample properties file: install_root/util/ndUtils/samples/.
Copy the sample files and modify the files to reflect your environment. For example, for a deployment manager for IBM® BPM Standard for Process Server, choose the sample_std_ps_dmgr.properties file.
For each database that you want to create, copy the database parameters section and specify the database name, user name, password, and schema name. The Process Server database, Performance Data Warehouse database, and Common database are required, and they must have different names.

For more information about the available properties, read the comments in the sample files, or see the configureNode command reference and the examples.
Restriction: The parameters listed in the sample files are the only parameters that can be customized.
Run the configureNode command, passing it the names of the two files you created. The custom node file is optional, but if you do not include it, only the deployment manager is created. For example:
- install_root/util/ndUtils/configureNode.sh -dmgr_response my_dmgr_response_file.properties -response node01_response_file.properties
Note: If you receive the Failed to perform Security setting update error, check to ensure that the global IP address has not been appended to 127.0.0.1 localhost in the hosts file. For example: 127.0.0.1 localhost example.ibm.com.

Results

You now have a deployment manager, a custom node, and a deployment environment that use the Remote Messaging, Remote Support, and Web topology pattern.

Messages are recorded in the file install_root/logs/config/configureNode.log.

Tip: After you have configured a network deployment environment, if you test the data store connection (for example, in the administrative console, on the page Resources > JDBC > Data sources), you get a message saying that the test connection operation failed with the exception com.ibm.wsspi.runtime.variable.UndefinedVariableException: Undefined Variable WAS_INSTALL_ROOT. This does not necessarily indicate that there will be a problem accessing the data source at run time. Ensure that the location of your JDBC driver files is accessible to every client that must use the data source, and configure the variable with the full path of that location. Disregard the test connection error unless you are also experiencing trouble connecting to the data store at run time. For additional information, see the WebSphere® Application Server documentation about the test connection service.

Important: 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.