Creating deployment manager profiles using the manageprofiles command-line utility

Instead of using the Profile Management Tool, you can use the manageprofiles command-line utility to create new profiles.

Before you begin

Make sure that you are not already running the manageprofiles command-line utility on the same profile. If an error message is displayed when you run the command, determine if there is another profile creation or augmentation action in progress. If so, wait until it completes.

Procedure

Determine the kind of profile you want to create, which in turn determines the template to use for your profile (using the -templatePath option).
Templates for each profile are located in the install_root/profileTemplates/BPM directory for BPM templates and under install_root/profileTemplates for other products.
The following templates are available:
- dmgr.procctr: for a Process Center deployment manager profile for IBM BPM Standard.
- dmgr.procctr.adv: for a Process Center deployment manager profile for IBM BPM Advanced.
- dmgr.procsvr: for a Process Server deployment manager profile for IBM BPM Standard.
- dmgr.procsvr.adv: for a Process Server deployment manager profile for IBM BPM Advanced.
- dmgr.esbserver: for a WebSphere® Enterprise Service Bus deployment manager profile.
Determine which parameters are required for your profile by reviewing the example profile creation commands. Determine the values that you want to supply for the profile by reviewing the default values in the manageprofiles parameters topic.
To use the -responseFile parameter, look at the provided sample response files and create a response file that is specific to your environment.
Important: Ensure that you do not leave blank spaces after the values; for example 'personalCertValidityPeriod=1 ' or 'winserviceCheck=false '. Spaces will cause profile creation to fail.

The samples are located in the install_root/BPM/samples/manageprofiles directory.
Choose an appropriate response file based on the database and type of profile (stand-alone or network, Process Center or Process Server). The following sample files are available:
- PC_Std_DMgr_DB2.response
- PC_Std_DMgr_DB2zOS.response
- PC_Std_DMgr_Oracle.response
- PC_Std_DMgr_SQLServer.response
- PC_Adv_DMgr_DB2.response
- PC_Adv_DMgr_DB2zOS.response
- PC_Adv_DMgr_Oracle.response
- PC_Adv_DMgr_SQLServer.response
- PC_Std_Managed_DB2.response
- PC_Std_Managed_DB2zOS.response
- PC_Std_Managed_Oracle.response
- PC_Std_Managed_SQLServer.response
- PC_Adv_Managed_DB2.response
- PC_Adv_Managed_DB2zOS.response
- PC_Adv_Managed_Oracle.response
- PC_Adv_Managed_SQLServer.response
- PC_Std_Standalone_DB2.response
- PC_Std_Standalone_DB2zOS.response
- PC_Std_Standalone_Oracle.response
- PC_Std_Standalone_SQLServer.response
- PC_Adv_Standalone_DB2.response
- PC_Adv_Standalone_DB2zOS.response
- PC_Adv_Standalone_Oracle.response
- PC_Adv_Standalone_SQLServer.response
- PS_Std_DMgr_DB2.response
- PS_Std_DMgr_DB2zOS.response
- PS_Std_DMgr_Oracle.response
- PS_Std_DMgr_SQLServer.response
- PS_Adv_DMgr_DB2.response
- PS_Adv_DMgr_DB2zOS.response
- PS_Adv_DMgr_Oracle.response
- PS_Adv_DMgr_SQLServer.response
- PS_Std_Managed_DB2.response
- PS_Std_Managed_DB2zOS.response
- PS_Std_Managed_Oracle.response
- PS_Std_Managed_SQLServer.response
- PS_Adv_Managed_DB2.response
- PS_Adv_Managed_DB2zOS.response
- PS_Adv_Managed_Oracle.response
- PS_Adv_Managed_SQLServer.response
- PS_Std_Standalone_DB2.response
- PS_Std_Standalone_DB2zOS.response
- PS_Std_Standalone_Oracle.response
- PS_Std_Standalone_SQLServer.response
- PS_Adv_Standalone_DB2.response
- PS_Adv_Standalone_DB2zOS.response
- PS_Adv_Standalone_Oracle.response
- PS_Adv_Standalone_SQLServer.response
Copy one of the sample response files to your working directory. Use the chmod command to assign the appropriate permissions to your new copy of the response file. For example:
```
chmod 644 BPM_Dmgr.response
```
Edit the parameters in the response file as appropriate to your configuration and save the edited response file. Make sure that the templatePath property path matches your specific installation directory.
Run the file from the command line. For example:
Note: The following example is an example only and shows optional parameters as well as required parameters. For a more complete set of parameters that can be changed, see the response file for creating deployment manager profiles.
```
manageprofiles.sh -create -templatePath install_root/profileTemplates/BPM/dmgr.procctr.adv -adminUserName bpmadmin -adminPassword bpmsecret -dbType MSSQLSERVER_MICROSOFT -dbHostName dbHost.com -procSvrDbName BPMDB -dbProcSvrUserId procadmin -dbProcSvrPassword procpwd -perfDWDbName PERFDB -dbPerfDWUserId perfadmin -dbPerfDWPassword perfpwd -dbName CMNDB -dbCommonUserId commonadmin -dbCommonPassword commonpwd
```
If you have created a response file, specify the -response parameter without any other parameters. For example:
```
manageprofiles.sh -response myResponseFile
```
The status is written to the console window when the command is finished running. Normal syntax checking on the response file applies as the file is parsed like any other response file. Individual values in the response file are treated as command-line parameters.

Example

The following example commands are used to create a deployment manager profile using the manageprofiles command that includes the following components: CommonDB, Common Event Infrastructure, Messaging Engines, and Business Space.

install_root/bin/manageprofiles -create -templatePath install_root\profileTemplates\BPM\
\dmgr.procsvr.adv -dbHostName hostName -dbServerPort 1433 -dbDelayConfig true
 -configureBSpace true -dbType MSSQLSERVER_Microsoft -dbUserId userID -dbJDBCClasspath 
path to JDBC 2.0 driver -dbName CMNDB
 -dbPassword password

What to do next

Add custom (managed nodes) profiles to be managed by the deployment manager and then configure the deployment environment.
Optionally, configure Business Process Choreographer.