Skip to main content

Process Designer & Workflow Tab

Standalone Process Designer​

Version info​

  • IBM Content Platform Engine - 5.5.11.0
  • IBM Content Navigator 3.0.14

Prerequisites​

Setup Steps​

Creating a Workflow System and Connection Point within Filenet​

  1. Log into ACCE
  2. Open the Object Store in which you want to store Workflow data
  3. Click on Administrative ->Workflow System and click New:

  1. Under Table Spaces ->Data, enter the tablespace where you want workflow files to be stored.
tip

See Create Databases for the tablespaces configuration, including their names.

  1. Under Workflow System Security Groups ->Administration Group, enter the admin group you want to assign to the Workflow System. These two can be found in your filenet configuration within the CR.
tip

See Deploying CR. The admin group is specified under initialize_configuration: ic_ldap_admins_groups_name in the CR.

  1. Specify the Connection Point name and description:

  1. Specify the isolated region name and enter the Isolated Region Number (1 if it’s your first in this object store, and so on)

  1. If you wish, you can Specify Isolated Region Table Space (Optional).
  2. Review all the details and click Finish:

  1. The system will display a success message if everything worked:

  1. Navigate to Workflow System ->Connection Points to double check that it was successfully created:

SSL Configuration (adding the site certificate into the jre keystore)​

  1. Launch Google Chrome
  2. Navigate to the ACCE console
  3. Click on the following:
  • The Lock Icon on the left side of the url:

  • Connection is secure:

  • Certificate is valid, Details and then Export...:

  1. Export full certificate chain (usually the second option in Save as) and change extension to .crt instead of .cert:

  1. Run the appropriate command to import it into your JRE keystore (keystore tool is found in the JAVA HOME directory under the bin folder)
path-to-java-home\bin\keytool -import -keystore path-to-java-home\lib\security\cacerts -file cpe_websphere_ssl_cert.crt
  1. When prompted with Trust this certificate? [no], respond with yes
  2. You should see an added to keystore message
keytool error

Importing a key subsequent times will result in the following error given that the alias is the same:

keytool error: java.lang.Exception: Certificate not imported, alias <key-alias-name> already exists

In which case you must delete the old key before importing the new one. Do so by running the following command with administrator priviledges (On Windows, run cmd as an Administrator. On Mac/Linux prepend sudo to the following command):

path-to-java-home\bin\keytool -delete -keystore path-to-java-home\lib\security\cacerts -alias <key-alias-name>

Configuring and Launching the Process Designer​

  1. Unzip the Process Designer zip file and all zip files within it for your platform. Beware that on Windows, unzipping the folders leads to a slightly different folder structure by default- there will be two peclient folders, one inside another. This can be 'fixed' by moving the one with the content into its parent.
  2. Navigate to:
    (unzipped_folder)\cpetools-win\peclient\
  3. Open this folder in any text editor or IDE (e.g. code .).
  4. Open:
    batch\cpetoolenv.bat
  5. Set the PE_CLIENT_INSTALL_DIR to the full path of the cpe_tools-<platform> directory, i.e., /Users/…/<unzipped_folder>/cpetools-linux, beware of any spaces in the folder path.
  6. Open config/WcmApiConfig.properties.
  7. Set the RemoteServerUrl
  • If you access the acce console at <host_link>/acce/, then confirm you can access the ping page at <host_link>/peengine/IOR/ping

  • If you can get to this page, then your RemoteServerUrl is likely <host_link>/wsi/FNCEWS40TOM. Check that you can also reach this page. If successful, it should display an xml document like so:

  1. Open a command line utility (i.e., Terminal [Mac], cmd [Windows]).
  2. Navigate (cd) to:
  cd <unzipped_folder>\cpetools-win\peclient\batch
  1. Run:
  pedesigner.bat <connection-point>
  1. Enter credentials used to login to the ACCE console:

  1. Process Designer should open up!

Enabling Workflow Tab on Content Navigator​

Prerequisites​

  • Workflow system and connection point have been created via the acce console in Object Store X (OSX)
  • A repository has been setup within the Navigator

Configuration Steps​

  1. Open the Navigator
  2. Navigate to Administration->Repositories->OSX (double click)
  3. Click Connect

  1. Navigate to Configuration Parameters -> Workflow Connection Point -> WF_CON_POINT_NAME (for this repo we want to use this connection point):

  1. Click Save and Close
  2. Navigate to Administration->Desktops->icn_desktop (default one)
  3. Double check that the default repo matches OSX:

  1. Navigate to Layout->Check Work:

  1. Navigate to Workflows->Select OSX repo under Repository:

  1. Select ApplicationSpace DefaultApplication and add it to the Selected Application Spaces:

  1. Click Save and Close and Refresh
  2. You should see the Work tab (with in-baskets, if you have created and committed them via the Process Designer):