IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced > Install IBM BPM Advanced > On AIX > Network deployment environment > Configure ND using configureNode.sh

Create the deployment environment using configureNode.sh

Use configureNode.sh to create a ready-to-use ND environment.

Before running...

• Create all databases specified in the properties file. Do not create tables.
• Create all the users specified in the properties file. Users should have the installation privileges.

For SQL Server database server, before running...

• Configure the username and schema. Schema value should be the default schema for the chosen user.

• 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.

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

The configureNode command uses default ports to create the dmgr. You cannot customize the ports using this command. Verify no other profiles that are configured with default ports are started on the same machine (netstat).

configureNode.sh creates the following ND topology:

• A single cell environment

• Cluster members (the number is specified in the properties file)

• 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

configureNode.sh performs the following tasks:

1. Creates the dmgr node.
2. Starts the dmgr.
3. Creates the deployment environment definition.
4. Creates a custom node.
5. Federates the node and adds the node to the deployment environment.
6. Generates the deployment environment.
7. Creates the database tables.
8. Runs the bootstrap utility to load the Process Server database with system information.
9. Configures Business Space and Process Portal on the web application cluster.

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

Procedure

To create the deployment environment for the first time:

1. On the machine where you want to create the deployment environment, locate the sample properties file:
   INSTALL_ROOTt/util/ndUtils/samples/

2. Copy the sample files and modify the files to reflect your environment.

   For example, for a dmgr for IBM BPM Advanced for Process Server, choose the file...

   sample_adv_pc_dmgr.properties

   For each database to create, copy the database parameters section and specify the database name, user name, password, and schema name.

   The following databases are required...

   • Process Server database
   • Performance Data Warehouse database
   • Common database
   • Business Process Choreographer database (IBM BPM Advanced)

   They must have different names.

3. Run configureNode.sh...

   cd INSTALL_ROOTt/util/ndUtils/
   ./configureNode.sh -dmgr_response dmgr_response.properties \
                      -response  node01_response.properties
   

   If you receive the error...

   Failed to perform Security setting update

   ...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 dmgr, 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_ROOTt/logs/config/configureNode.log

After you have configured an ND 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.

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 used by the new server.

Related concepts:

Virtual hosts
Topologies of an ND environment

Related tasks:

Configure virtual hosts
Encrypt passwords
Remove profiles using manageprofiles.sh

Configure Process Portal:
Create databases and database design files

Related reference:

Test connection service
configureNode command-line utility
configureNode examples
Database privileges