Artifact support in traditional and container runtime environments
In IBM® Business Automation Workflow, all artifacts are generally supported in the traditional WebSphere environment. However, not all artifacts are supported in the container runtime environment, such as most deprecated artifacts (like BPDs, integration services and some other services).
The following table lists the artifacts that are supported in the traditional runtime environment and the container runtime environment. All of these artifacts are editable in the web Process Designer, the deprecated desktop Process Designer, or both. For information about editing these artifacts in the web or desktop Process Designer, or for information on converting these artifacts to other formats (where applicable), see Where to edit Process Designer artifacts.
|Artifacts||Traditional environment||Container environment|
|Advanced Integration Service (AIS)||Yes||No|
|Ajax Service (deprecated)||Yes||No|
|Blueworks Live Subscription||Yes||Yes|
|Business Process Definition (BPD) (deprecated)||Yes||No
To convert BPDs to processes that are supported in a container environment, see Converting BPDs to processes.
|Client-Side Human Service||Yes||Yes|
|Content Management toolkit||Yes. You can use either version 188.8.131.52 or version 184.108.40.206_TC of the toolkit in a traditional environment. For more information, see System toolkits||Yes. You must use version 220.127.116.11_TC of the toolkit. For more information, see System toolkits|
|Decision Service (deprecated)||Yes||No|
|Decision support in Service Flows||Yes||Yes|
|Exposed Process Value||Yes||Yes|
To convert external implementations to external services that are supported in a container environment, see Converting an external implementation.
|External Service: REST service||Yes||Yes|
|External Service: Java service||Yes||Yes. However, Java classes that rely on features specific to WebSphere® Application Server Network Deployment are not supported.|
|External Service: Web service||Yes||Yes, however, only External Services of type Web Service that were discovered in v18.104.22.168 or newer can run in a container environment. To use other External Services of type Web Service, you must rediscover them as described in Calling an external service.|
|General System Service (deprecated)||Yes||No|
|Heritage Coach (deprecated)||Yes||No|
|Heritage Human Service (deprecated)||Yes||Yes
However, heritage coaches included in heritage human services are not supported in a container environment.
|Historical Analysis Scenario (deprecated)||Yes||No|
|IBM Case Manager Integration Service||Yes||No|
|Integration Service (deprecated)||Yes||No|
|Key Performance Indicator (KPI)||Yes||No|
|Layouts (Chart Type, Report Filter, etc.)||Yes||No|
However, processes that use the deprecated Basic Case Management feature are not supported in a container environment.
Note: If you want to reference an external service with an external implementation binding, you must use a user task.
|Process Application Setting||Yes||Yes
However, process application settings for servers are restricted to the following servers in the container environment:
|Service-Level Agreement (SLA)||Yes||No|
|Simulation Analysis Scenario (deprecated)||Yes||No|
|System Data toolkit||Yes. You can use either version 22.214.171.124 or version 126.96.36.199_TC of the toolkit in a traditional environment. For more information, see System toolkits||Yes. You must use version 188.8.131.52_TC of the toolkit. For more information, see System toolkits|
|User Attribute Definition||Yes||Yes|
|Web Service (inbound)||Yes||Yes|