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.

Table 1. Artifacts supported in the runtime environments
Artifacts Traditional environment Container environment
Advanced Integration Service (AIS) Yes No
Ajax Service (deprecated) Yes No
Blueworks Live Subscription Yes Yes
Business Object 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.

Chart Type Yes No
Client-Side Human Service Yes Yes
Content Management toolkit Yes. You can use either version 8.6.0.0 or version 8.6.0.0_TC of the toolkit in a traditional environment. For more information, see System toolkits Yes. You must use version 8.6.0.0_TC of the toolkit. For more information, see System toolkits
Content Objects Yes Yes
Decision Service (deprecated) Yes No
Decision support in Service Flows Yes Yes
Design File Yes No
Document Type Yes No
Event Subscription Yes Yes
Exposed Process Value Yes Yes
External Implementation Yes No

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.0.0.2 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
Localization Resource Yes Yes
Process Yes Yes

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:

  • Enterprise Content Management Server
  • REST Server
  • Web Service Server
Report Yes No
ScoreBoard Yes No
Server File Yes Yes
Service Flow Yes Yes
Service-Level Agreement (SLA) Yes No
Simulation Analysis Scenario (deprecated) Yes No
System Data toolkit Yes. You can use either version 8.6.0.0 or version 8.6.0.0_TC of the toolkit in a traditional environment. For more information, see System toolkits Yes. You must use version 8.6.0.0_TC of the toolkit. For more information, see System toolkits
Team Yes Yes
Theme Yes Yes
Timing Interval Yes No
Tracking Group Yes Yes
Undercover Agent Yes Yes
User Attribute Definition Yes Yes
View Yes Yes
Web File Yes Yes
Web Service (inbound) Yes Yes