The list as of CP4BA 24.0.x (check the current release notes - items move from "deprecated" to "removed"):
- Heritage human services and heritage coaches - not supported in containers; convert to client-side human services with coach views.
- BAW Advanced - BPEL processes, mediation modules, WebSphere adapters, Integration Designer, human tasks (HTM), Business Space: none of it exists in containers. Replace with service flows, App Connect Enterprise (also in the Cloud Pak), or REST external services.
- Desktop Process Designer - web designer only (Business Automation Studio).
- Classic Process Portal customisations - the classic portal is still deployed for compatibility on some releases but Workplace is the supported UI; portal theme / process app customisations of the classic portal do not carry over.
- WebSphere-specific integrations - JNDI mail sessions, WebSphere work managers, EJB calls, WebSphere admin scripting from processes, file-system paths without a mounted volume, the SIBus (Liberty uses its own embedded messaging or an external MQ).
- Process Federation Server on WebSphere - replaced by the containerised PFS (OpenSearch / Elasticsearch based) that Workplace uses.
- Some REST endpoints - the BPD-related "REST API v1" resources are all there, but Process Admin console functions that were only UI are exposed through the Operations REST API instead; a few undocumented /teamworks URLs are blocked by the Zen front door.
- Kerberos / SPNEGO TAI, SAML TAI - authentication is done by IAM / Zen with OIDC / SAML at the platform level; per-server TAIs are gone.
- Java integrations work, but the classes must not rely on WebSphere traditional APIs (com.ibm.websphere.*), and the jars must be compatible with the Java level of the Liberty image (Java 11 / 17 on recent releases).
Deprecated but still available and worth avoiding in new work: Dojo-based coach views from the old "Coaches" toolkit, the Dashboards toolkit widgets that depend on Business Space, tracking groups with the performance data warehouse when BAI is the target analytics layer.
# find heritage artifacts before migrating: the validation report of a snapshot lists deprecated items
GET /rest/bpm/wle/v1/snapshot/{snapshotId}?parts=validation
# or in the repository database (Process Center): heritage human services have a distinct process type
select name from lsw_process where process_type = 3; -- heritage human services (type ids vary by release; check with a known HHS first)References
- CP4BA - Business Automation Workflow on containers (capabilities and limitations)
- BAW - deprecated and removed features