Running the development environment case configuration tasks

Use the development environment profile that was created by the BPMConfig command when you run the tasks in the Case configuration tool.

Before you begin

Ensure that the cluster and your IBM® Content Navigator instance are running when you run the Case configuration tool tasks.

Tip: The information here is about using the GUI to configure the case development environment. However, you can use the command line if you prefer. For more information, see Configuring the development environment by using the command line.

Procedure

To configure the development environment, complete the following steps:

Set the application server timeout values to at least 600 seconds. The following sample settings are for WebSphere® Application Server Version 8.5.5:
- Servers > Server Types > WebSphere application servers > Configuration tab > Container Settings > Container Services > Transaction service > Total transaction lifetime timeout
- Servers > Server Types > WebSphere application servers > Configuration tab > Container Settings > Container Services > Transaction service > Maximum transaction lifetime timeout
- Servers > Server Types > WebSphere application servers > Configuration tab > Container Settings > Container Services > ORB service > Request timeout
- Servers > Server Types > WebSphere application servers > Configuration tab > Container Settings > Container Services > ORB service > Locate request timeout
  Note: For WebSphere Application Server Version 8.5.5, the maximum value for the locate request timeout is 300.
- Resources > JDBC > Data sources > [Content Engine or Case Manager data source name] > Connection Pool properties > Connection timeout
- Resources > JDBC > Data sources > [Content Engine or Case Manager XA data source name] > Connection Pool properties > Connection timeout
Restart your entire environment.

Start the Case configuration tool by running one of the following commands:

Operating system	Command
AIX®	Change to the `install_root`/CaseManagement/configure directory. Run the following command: `./configmgr`
Linux®	Change to the `install_root`/CaseManagement/configure directory. Run the following command: `./configmgr`
Linux for System z®	Change to the `install_root`/CaseManagement/configure directory. Run the following command: `./configmgr`
Linux on POWER Little Endian (LE)	Change to the `install_root`/CaseManagement/configure directory. Modify the comfigmgr.ini file to point to JDK 1.8 by making the following change: `-vm /opt/install_root/java_1.8_64/bin` Run the following command: `./configmgr`
Windows	Change to the `install_root`\CaseManagement\configure directory. Run the following command: `configmgr.exe`

Click Open Profile to open the predefined profile for your current development environment.
The predefined profile is located in the following directory: dmgr_profile_root/CaseManagement_DE_name/profiles/ICM_dev

Edit, save, and run the following tasks.

You must run the tasks in the order listed.

Most of the configuration values are set based on your workflow environment. However, review the values to ensure they are set correctly.

Table 1. Task requirements for a development environment
Task	Required
Register the Administration Console for Content Platform Engine (ACCE) Plug-in	Always if you are using the embedded Content Platform Engine. The ACCE Plug-in is disabled if you are using an external Content Platform Engine, because it might not be compatible with the external Content Platform Engine server. Instead, use the ACCE console that is provided by your external Content Platform Engine server. Always Restriction: When you run the administration console for the Content Platform Engine from IBM Content Navigator, you cannot run Process Administrator or Process Configuration Console from the administration console. To use the Process Administrator or Process Configuration Console applets, follow the instructions in Configuring Process Designer to run from IBM Content Navigator.
Configure the Case Management Object Stores	Always
Define the Default Project Area	Always Important: If you are using an external Content Platform Engine, enter the correct configuration values for your environment.
Configure Case Integration with IBM Business Automation Workflow	Always
Deploy the Content Platform Engine Workflow Service	Always Important: If you are using an external Content Platform Engine, enter the correct configuration values for your environment.
Deploy the Content Platform Engine Gateway Service	Always Note: The parameter value for the IBM Business Automation Workflow server cluster name is not dependent on the cell environment of the Content Platform Engine application server, which is specified by several other parameter values in the configuration of this task. The Business Automation Workflow server cluster name must be looked up separately in the server cell of the Business Automation Workflow server application and its value must be entered manually.
Register the IBM Business Automation Workflow Plug-in	Always Important: If you are using an external IBM Content Navigator, enter the correct configuration values for your environment.
Register the Case Management Services Plug-in	Always Note: After you configure a Business Automation Workflow environment, you can select the any other desktop as the Case Client desktop instead of the Business Automation Workflow default desktop: IBM Business Automation Workflow. To re-use your legacy environment or a customized desktop as the Case Client desktop instead of the new default desktop that changed to IBM Business Automation Workflow after the legacy IBM Case Manager environment was augmented to a Business Automation Workflow environment, select it and run the task. Important: If you are using an external IBM Content Navigator, enter the correct configuration values for your environment.
Register the IBM Content Platform Engine Applets Support Plug-in	Required only if you want to launch the IBM FileNet® Process Designer applet from Case Builder. You do not need to run this task to use the standalone IBM FileNet Process Designer. Important: If you are using an external IBM Content Navigator, enter the correct configuration values for your environment.
Register the Case Widgets Package	Always Important: Do not modify the file path that is predefined for the Case Widgets package. If you are using an external IBM Content Navigator, enter the correct configuration values for your environment. If you are using an external IBM Content Navigator, enter the correct configuration values for your environment.
Register the IBM Business Automation Workflow Case Administration Client Plug-in	Always Important: If you are using an external IBM Content Navigator, enter the correct configuration values for your environment.
Configure Box Collaboration	Required if you want to enable case workers to use Box to collaborate with external users. This task configures the connection to the Box server.
Register the Case Box Event Listener Plug-in	Required if you want Box events to trigger the creation of cases or work items. Important: If you are using an external IBM Content Navigator, enter the correct configuration values for your environment.
Register Project Area	Always. When the Case Operations component queue is created in FileNet Content Platform Engine, it is named `ICM_Operations`.
Configure Business Rules	Required if you use business rules in your solution. Tips: You can select only one locale in which to write the business rules for your solutions. If you must create solutions with business rules in other locales, rerun this task to change the rule persistence locale before you create the solution. After the first rule for a solution is saved, the rule persistence locale cannot be changed. If you rerun this task to change the location of the rules repository directory after you deploy any solutions, complete the following steps after you run the task: Stop Content Platform Engine. From the previous rules repository directory, move the res_data directory to the new location of the rules repository directory. In a cluster environment, the rules directory must be a shared directory that can be accessed by all Content Platform Engine cluster servers. Restart Content Platform Engine.
Register the Case Monitor Widgets Package	Always Important: Do not modify the file path that is predefined for the Case Monitor Widgets package. If you are using an external IBM Content Navigator, enter the correct configuration values for your environment.
Register the External Data Service	Required for solutions that use the external data service.
Deploy and Register Custom Widgets Package	Required if you have a custom widgets package that you want to use with your case solution. Important: If you run this task in a cluster environment, you must ensure that the plug-in is loaded on each node of the cluster. Either restart the cluster to force the plug-in to be loaded on all nodes or manually load the plug-in on each node by using the IBM Content Navigator administration client. If you are using an external IBM Content Navigator, enter the correct configuration values for your environment.
Deploy and Register Extensions Package	Required only when you add an extensions package for a custom property editor or controller. Important: If you run this task in a cluster environment, you must ensure that the plug-in is loaded on each node of the cluster. Either restart the cluster to force the plug-in to be loaded on all nodes or manually load the plug-in on each node by using the IBM Content Navigator administration client. If you are using an external IBM Content Navigator, enter the correct configuration values for your environment.

If you are using an external Content Platform Engine, restart the external Content Platform Engine server.
Restart the cluster.