Preparing to run the case configuration tasks for the development environment

To configure the development environment:

1. Set the application server timeout values. Higher timeout values help avoid transaction timeout issues when you run the configuration tool tasks or deploy case solutions.
   • Set timeout values to the following settings (examples for WebSphere® Application Server V8.5.2):
     • Under Servers > Server Types > WebSphere application servers > Click on your server > Configuration tab > Container Settings > Container Services > Transaction service, set the following timeout values:
       • Total transaction timeout
       • Client inactivity timeout
       • Maximum transaction timeout
     • Under Servers > Server Types > WebSphere application servers > Click on your server > Configuration tab > Container Settings > Container Services > ORB service, set Request timeout to at least 600 and Locate request timeout to maximum 300.
     • Under Resources > JDBC > Data sources > [Content Engine or Case Manager data source name] > Connection Pool properties, set Connection timeout to at least 600.
     • Under Resources > JDBC > Data sources > [Content Engine or Case Manager XA data source name] > Connection Pool properties, set Connection timeout to at least 600.
2. Restart your entire environment.
   Note: If you are using Db2® for z/OS®, your Register Project Area task might hang and fail when you restart your entire environment. To avoid this, after you restart your environment, go to WAS console > Applications >  Application Types > WebSphere enterprise applications, and find IBM_BPM_DocumentStore_YourClusterName. Restart this application again.
3. Start the swing-based Case configuration tool.

   On AIX, Linux, or Linux® for System z®

   1. Change to the following directory:

      install_root/CaseManagement/configure

   2. Edit the appropriate script:

      • For GUI configuration: configmgr.sh
      • For silent or command-line configuration: configmgr_cl.sh
   3. Set the PATH environment variable to the Java™ bin directory of the Business Automation Workflow installation:

      export PATH=/opt/IBM/BAW/java/bin:$PATH

   4. Set the INSTALL_DIR environment variable to the Business Automation Workflow installation directory:

      export INSTALL_DIR=/opt/IBM/BAW

   5. Save the script file.

   6. Ensure the script has execute permissions:

      chmod +x configmgr.sh

   7. Run the configuration script:

      ./configmgr.sh

   On Windows

   1. Change the directory to the configuration folder:

      cd install_root\CaseManagement\configure

   2. Edit the appropriate batch file:
      • For GUI configuration: configmgr.bat
      • For silent or command-line configuration: configmgr_cl.bat
   3. Set the PATH environment variable to the Java bin directory of the Business Automation Workflow installation:

      set PATH=C:\IBM\BAW\java\bin;%PATH%

   4. Set the INSTALL_DIR environment variable to the Business Automation Workflow installation directory:

      set INSTALL_DIR=C:\IBM\BAW

   5. Save the batch file.
   6. Run the configuration script:

      configmgr.bat

4. In the swing-based Case configuration tool, create a new profile for a fresh configuration, or open an existing profile to modify an existing configuration.
   • Go to the File menu and choose either:
     • New Installation Profile – for a fresh setup
     • Open Profile – to modify an existing configuration

   When creating a new profile:

   • Select either development or production based on your environment.
   • Enter the WebSphere Application Server and IBM Content Navigator details.
   • In the Content Platform Engine parameters, ensure that the server URL uses the corbaloc protocol.

   Example:

   corbaloc::<cpe server hostnname>:<portnumber/cell/clusters/<cluster name>/FileNet/Engine

   Important: The iiop protocol is not supported.
5. Save the edited profile.
6. Run the Case configuration tool tasks for the development environment, as specified in Running the configuration tasks.
7. Restart your entire environment, including Business Automation Workflow, Content Platform Engine, and IBM Content Navigator.