Case management is part of every BAW 19.0.0.x installation, but it is only configured when you ask for it. On an existing 19.0.0.3 cell:
- Prerequisites: Content Platform Engine (CPE) and Content Navigator (ICN) - BAW installs them into the same cell when you choose the Workflow (not Workflow Enterprise "process only") configuration; a design object store (DOS) and a target object store (TOS) plus the CMNDB / DOSDB / TOSDB databases; LDAP (case management needs a real registry, not the file registry).
- Enable with BPMConfig: edit the properties file used to create the environment (or export it with BPMConfig -export), fill the bpm.de.caseManager.* section (object store names, Navigator settings, CPE database properties) and run the case configuration action of BPMConfig (BPMConfig -update -caseConfigure <properties file> on 19.0.0.x; BPMConfig -help lists the exact option of your level).
- Run the Case configuration tool (configmgr_cl) tasks that BPMConfig drives: create the DOS / TOS, deploy Case Builder, Case Client and the Case REST API into ICN, register the Workflow server as the Case "process engine".
- Verify: https://host:9443/CaseBuilder and /CaseManager (Case Client via Navigator) open; Process Designer shows the Case artifacts (Case types) in process apps; the System toolkit "Case Management" is available.
On CP4BA the same is done by adding ba_workflow.case settings to the BAW custom resource (workflow authoring / runtime with case section) - the operator configures CPE, Navigator and the object stores.
Note the 19.0.0.3 quirk: a Process Center (authoring) cell needs case management enabled as well as every Process Server (runtime) cell; enabling only the runtime leaves Process Designer without case artifacts.
References