A single-server development sandbox with IBM BPM (or BAW) on Red Hat and Oracle, in the order that avoids the classic mistakes:
- Machine: RHEL 8/9 (check the BAW system requirements for your version), 8 vCPU, 32 GB RAM (16 GB minimum), 150 GB disk; hostname resolvable (fixed IP or /etc/hosts), ulimit -n 65536, SELinux permissive or configured, ksh and 32-bit compat libs when the installer asks.
- Oracle: 19c (XE is fine for a sandbox), a pluggable database, and the BPM users / tablespaces created with the scripts BAW generates (BPMConfig.sh -create -sqlfiles <properties> writes the DDL you run as SYS): BPMDB, PDWDB, CMNDB schemas; set open_cursors=1000, processes=500; the Oracle JDBC driver ojdbc8.jar path for the profile creation.
- Install: Installation Manager + WebSphere ND + BAW from the repositories with the silent response file (imcl install ...), then create the single-cluster environment with the Single Cluster properties file sample for Oracle: BPMConfig.sh -create -de myEnv.properties - one deployment manager, one node, one cluster member, Process Center (or Process Server). This also bootstraps the databases.
- Start: startManager, startNode, startServer; log in to https://host:9443/ProcessCenter; install Process Designer on a Windows client or use the web designer.
- After: snapshot the VM (rollback), set up daily database exports, and keep the properties file and response files in Git - the same files build the next sandbox in an hour.
# skeleton of the BPMConfig properties (Oracle, single cluster, Process Center)
bpm.de.name=De1
bpm.de.type=ProcessCenter
bpm.de.db.1.type=Oracle
bpm.de.db.1.hostname=oracle.example.com
bpm.de.db.1.portNumber=1521
bpm.de.db.1.databaseName=ORCLPDB1 # service name
bpm.de.db.1.schema=BPMUSER
bpm.de.db.1.user=BPMUSER
bpm.de.db.1.password=...
bpm.de.deploymentEnvironmentType=Workflow # or Process Center
# ... node / cluster / admin user sections from the sample: BPMConfig_samples/Oracle/Standard/DE/Workflow-SingleCluster-Oracle.properties
Alternatives that are faster for pure development: the CP4BA starter deployment on a small OpenShift (or the IBM-provided trial images), or Workflow Process Service as a container - no Oracle, no WebSphere. Keep the traditional sandbox when you must mirror a traditional production.
References