This chapter includes the following sections:
Table 7-1 contains a description of the different APIs supported in BPM 10gR3 and details on how to migrate them to the BPM 12c version.
For examples on PAPI-to-BPM12c migration, see the following resources:
Oracle Technology Network (OTN): http://www.oracle.com/technetwork/index.html
Table 7-1 API Migration
| API | Description | MIgration |
|---|---|---|
|
FDI |
Enabled access to the organization information repository directly. This API was not officially supported in BPM 10gR3. Only access through the fuego.fdi block was officially supported. However some customers were given access to this internal API. |
Not available. |
|
PAPI |
Enabled the interaction with the 10gr3 BPM Engine from a custom Java application. |
Migrate the code that uses this API manually. |
|
PAPI-WS |
Enabled the interaction with the 10gr3 BPM Engine from a custom web service. |
Migrate the code that uses this API manually. |
|
WAPI |
Provided a framework to run functions similar to the ones provided by the PAPI API using HTTP requests. |
Migrate the code that uses this API manually. Most BPM services provide a web service interface. For more information, see Developing Business Processes with Oracle Business Process Management Studio. |
|
Oracle BPM 10.3 Java Interfaces |
Java classes and interfaces used to extend BPM functionality. |
Not Available |