Business interfaces are organized into interface types according to the integration technologies on which they're based.
Based on the natural way of how interfaces are formed or established, Oracle Integration Repository supports the following interface types:
Native Interfaces
Native integration interfaces or Oracle seeded interfaces are integration endpoints shipped with the Oracle Integration Repository by default. It includes the following interface types:
Apart from normal Java APIs, Java interface includes the following subcategories:
Please note that in this release Java APIs for Forms are not serviceable interfaces and cannot be exposed as SOAP services.
Building upon native interfaces, a composite interface consists of a collection of native interfaces that belong to a specific product or product family available in the Integration Repository.
The supported composite interface type is Composite - BPEL.
Note: Oracle Integration Repository supports custom integration interfaces that are created and annotated based on Integration Repository annotation standards. After appropriate validation, these annotated custom source files can be uploaded and displayed along with Oracle interfaces through the Integration Repository browser tree, based on the interface types to which they belong.
To easily differentiate custom interfaces from Oracle ones, all custom integration interfaces are categorized with interface source 'Custom' while Oracle interfaces are marked with interface source 'Oracle'. For more information about custom integration interfaces and services, see Working With Custom Integration Interfaces and Services.
A business interface can be based on a PL/SQL package from which you invoke procedures and functions appropriate to an integration.
PL/SQL APIs are serviceable interfaces and can be exposed as both SOAP-based and REST-based Web services.
For more information about PL/SQL interface type in the Integration Repository, see PL/SQL Information.
Oracle XML Gateway comprises a set of services that allows easy integration with Oracle E-Business Suite to support XML messaging. Oracle E-Business Suite utilizes Oracle Workflow Business Event System to support event-based XML message creation and consumption.
Oracle XML Gateway consumes events raised by Oracle E-Business Suite and subscribes to inbound events for processing. It uses the message propagation feature of Oracle Advanced Queuing to integrate with Oracle Transport Agent to deliver messages to and receive messages from business partners. XML Gateway message maps can be used directly, or they can be exposed as Web services.
Additional Information: The message map is a file of type .xgm and is created using the XML Gateway Message Designer. Message maps define the data source and data target, any hierarchies between the source and the target, and actions for data transformation and process control.
For more information about XML Gateway map interface type in the Integration Repository, see XML Gateway Map Information.
For more information about Oracle XML Gateway, see the Oracle XML Gateway User's Guide.
A concurrent program runs as a concurrent process that executes multiple programs running in the background. Functions performed by concurrent programs are normally data-intensive and long-running, such as posting a journal, and generating an EDI flat file.
For more information about Concurrent Program interface type in the Integration Repository, see Concurrent Program Information.
For more information about how to use concurrent programs, refer to the Oracle E-Business Suite Setup Guide.
A business event is an occurrence in an internet application that might be significant to other objects in a system or to external agents. An example of a business event can be the creation of a new sales order or changes to an existing order.
Oracle Workflow uses the Business Event System that leverages the Oracle Advanced Queuing (AQ) infrastructure to communicate and manage business events between systems. When a local event occurs, the event subscribing code is executed in the same transaction as the code that raised the event. Subscription processing can include executing custom code on the event information, sending event information to a workflow process, and sending event information to other queues or systems.
For more business event information, see Events.
For more information about business event interface type in the Integration Repository, see Business Event Information.
An open interface consists of the interface tables to store data from external sources and concurrent programs, as well as to validate and apply this data into the Oracle E-Business Suite base tables. All open interfaces are implemented using concurrent programs.
Please note that Open Interface Table is often referred as Open Interface.
For more information about Open Interface Table interface type in the Integration Repository, see Open Interface Information.
Interface views are database objects that make data from Oracle E-Business Suite products available for selection.
For more information about Interface View interface type in the Integration Repository, see Interface View Information.
Electronic Data Interchange (EDI) is one form of electronic commerce. Interface data files are electronically exchanged between trading partners as messages in a standard format to minimize manual effort. EDI message transactions are supported by Oracle e-Commerce Gateway.
Oracle e-Commerce Gateway provides users the ability to conduct business electronically between trading partners based on Electronic Commerce standards and methodology. When used for EDI solutions, Oracle e-Commerce Gateway integrates with EDI translators to provide specific EDI standard formats and versions.
For more information about EDI messages in the Integration Repository, see EDI Message Information.
For more information about Oracle e-Commerce Gateway, see the Oracle e-Commerce Gateway User's Guide.
A business service object, formerly known as Service Bean, is a high-level service component that allows OA Framework or BC4J components to be deployed as Web services.
Business service object interfaces provide access to SOA services to facilitate integration between Oracle E-Business Suite and trading partners. They often employ service data objects as parameters to pass complex data.
Note: A service data object is not actually an interface type; rather, it is an object used by one or more business service objects or other service data objects to pass data.
For more information about Business Service Object interface type in the Integration Repository, see Business Service Object.
A business interface can be based on a Java class from which you invoke methods that are appropriate to an integration.
Java APIs for Forms interfaces are not serviceable interfaces and cannot be exposed as SOAP services.
Java Bean Services are also a subtype of Java interface. This type of Java APIs whose methods must use parameters of either serializable Java Beans or simple data types such as String, Int, and so forth can be categorized as Java Bean Services. Such Java APIs can be exposed as REST services only.
Similar to the PL/SQL REST services, Java Bean Services have simplified development life cycle - Deploy and Undeploy - and are implemented with the same security mechanism. Java Bean Services can be deployed as REST service operations with POST and GET HTTP methods in this release.
For annotation guidelines on Java Bean Services, see Annotations for Java Bean Services.
Application Module Implementation class is a Java class that provides access to business logic governing the OA Framework-based components and pages. Such Java classes are called Application Module Services and are categorized as a subtype of Java interface.
Similar to Java Bean Services, Application Module Services can be exposed as REST services only.
For annotation guidelines on Application Module Services, see Annotations for Application Module Services.
Security services, built on Java, are a set of predefined and predeployed REST services from Oracle Application Object Library. These services including Authentication and Authorization services are developed for mobile applications.
Please note that security services will not require any REST service life cycle activities such as Deploy or Undeploy. Additionally, they are available to all users.
For more information about Java interface type in the Integration Repository, see Java Information.
A composite interface consists of a collection of native packaged interfaces or services available in the Integration Repository.
Composite interfaces orchestrate the invocation sequence of Web services into an end-to-end business process through a Web service composition language BPEL (business process execution language).
Additional Information: Composite interfaces can be designed and created in Oracle JDeveloper and Oracle Eclipse. Based on the creation methods, composite services have various composite types such as BPEL, ESB (enterprise service bus), or SCA (service component architecture) types. Composite - BPEL type is the only supported composite interface in this release.
For more information about composite interfaces, see Working with Composite Interfaces.