Creating Process Server deployment manager and custom profiles using manageprofiles

Use the manageprofiles command-line utility to create Process Server deployment manager and custom profiles for a network deployment configuration.

1. Determine the kind of profile you want to create, which in turn determines the template to use for your new 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.procsvr: for a deployment manager profile, which defines a deployment manager. A deployment manager provides one administrative interface to a logical group of servers on one or more workstations.
   • dmgr.procsvr.adv: for Process Server deployment manager profiles, which define deployment manager servers with capabilities and functionality specific to an IBM® BPM Advanced configuration.
   • managed.procsvr: for a Process Server custom profile, which, when federated to a deployment manager, defines a managed node. If you have decided that your solution requires a network deployment configuration, your runtime environment requires one or more managed nodes. A custom profile contains an empty node that you must federate into a deployment manager cell to make operational. Federating the custom profile changes it into a managed node. Do not federate a node unless the deployment manager you are federating to is at a release level the same or higher than that of the custom profile you are creating. Also, IBM Business Process Manager Advanced: Process Server profiles cannot use a WebSphere® Enterprise Service Bus deployment manager, but WebSphere Enterprise Service Bus profiles can use a IBM Business Process Manager Advanced: Process Server deployment manager.
   • managed.procsvr.adv: for Process Server custom profiles which, when federated to a deployment manager, define a managed node with capabilities and functionality specific to an IBM BPM Advanced configuration.
   • dmgr.esbserver: for a WebSphere Enterprise Service Bus deployment manager profile, which defines a deployment manager.
   • managed.esbserver: for a WebSphere Enterprise Service Bus custom profile, which, when federated to a deployment manager, defines a managed node. Do not federate a node unless the deployment manager you are federating to is at a release level the same or higher than that of the custom profile you are creating. WebSphere Enterprise Service Bus profiles can use a Enterprise Service Bus or IBM Business Process Manager Process Server deployment manager.
2. Determine which parameters are required for your type of profile by reviewing the example profile creation commands in manageprofile examples.
3. Determine the values that you want to supply for the profile by reviewing the default values in the manageprofiles parameters topic to see if they are what you need for your profile.
4. Create a response file.

   Sample response files are available under the install_root/BPM/samples/manageprofiles/ directory. Choose an appropriate response file based on the profile that you want to create (stand-alone or network, Process Center or Process Server) and customize the file for 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.
   See Creating a response file using the IBM Business Process Manager samples.
5. Run the manageprofiles command from the command line, using the -response parameter and the name of the response file that you created.
   • manageprofiles.sh -response myResponseFile
   • manageprofiles.bat -response myResponseFile
   The command displays status as it runs. Wait for it to finish. 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.
6. Manually configure the SMTP server to enable mail notifications. Refer to Configuring the SMTP server.