Configuring the production environment by using the command line

You must configure the production environment before you deploy your solutions to that production environment. You configure the production environment after you configure the development environment. You can use the command line to configure the production environment.

To configure the production environment:

1. Run the BPMConfig command to create the profiles for your production environment.
   If you have already created the dmgr and node profiles for your production environment, skip to the next step.
2. Change the current directory to the dmgr_profile_root/CaseManagement_DE_name/profiles/ICM_prod directory.
3. Referring to Production environment tasks and files, edit the property values in the configuration XML files that you generated:
   1. Use a text editor or XML editor to open one of the configuration XML files that you generated.
   2. Replace each occurrence of ****INSERT VALUE**** with a value that is appropriate for your site.
      To change the default value to a blank value, replace <value>****INSERT VALUE****</value> with <value />. See the descriptions in the file for more information.

      Important notes:

      • You are not required to store values for passwords in the file. You can run the storePasswords command later to add encrypted passwords to the file before you run the task.
      • The profile that is generated by the BPMConfig command creates a cluster deployment type. If the Content Platform Engine server is not using a cluster deployment type, then the Deploy the Content Platform Engine Workflow Service task (which has the file deployibmbpmis.xml) must be changed. You must delete the task and add it to the profile again with the correct deployment type. The profile name is dmgr_profile_root/CaseManagement/DE_name/profiles/ICM_prod. For example:

        
        configmgr_cl removeTask -profile /opt/ibm/Workflow/v18.0/profiles/DmgrProfile/CaseManagement/De1/profiles/ICM_prod -task deployibmbpmis
        configmgr_cl generateConfig -profileType devenv -profile /opt/ibm/Workflow/v18.0/profiles/DmgrProfile/CaseManagement/De1/profiles/ICM_prod -task deployibmbpmis -deploy standard

   3. Replace empty values that have the format <value /> with a value appropriate for your site.
      Use the format <value>my_value</value>.
   4. Verify that the default values for the remaining properties are correct for your site.
   5. Verify that the task is enabled for each required task. Set the enabled attribute value in the <configuration> element to true in any configuration XML file that you edit if you want to run the configuration task.
      When a task is disabled, the execute command skips the task. For example, the registerexternaldatauri.xml file has the enabled attribute value in the <configuration> element set to false by default, and the task will be skipped.
   6. Save your edits and close the XML file.
   7. Repeat as needed until you edit all the required files.
      Important: You must provide values for all of the entries in the websphereapplicationserver.xml file, the contentengineserver.xml file, and the contentnavigatorserver.xml file before you can run any of the tasks.
4. If you are running Linux on POWER Little Endian (LE), modify the install_root/CaseManagement/configure/comfigmgr.ini file to point to JDK 1.8 by making the following change:

   -vm
   /opt/install_root/java_1.8_64/bin

5. Optional: Add encrypted passwords to the XML files by running the storePasswords command for the profile.
   Tip: If you do not add passwords to the XML files, you are prompted for the passwords when you run the task for each file.
   For example, the following command stores all the passwords in the profile named myprofile1:

   configmgr_cl storePasswords -profile myprofile1

6. Change to the install_root/CaseManagement/configure directory and run all of the tasks in the development profile by using the following command:

   configmgr_cl execute -profile myprofile
    [-silent] [-force]

   For more information about the syntax, see execute command.
7. Restart the application server.