Documente Academic
Documente Profesional
Documente Cultură
October 2012
Disclaimer
The following is intended to outline our general product direction. It is intended
for information purposes only, and may not be incorporated into any contract. It is
not a commitment to deliver any material, code, or functionality, and should not
be relied upon in making purchasing decisions. The development, release, and
timing of any features or functionality described for Oracle’s products remains at
the sole discretion of Oracle.
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
Introduction......................................................................................... 1
Enterprise Application Integration Styles............................................. 2
Data-centric Integration...................................................................... 3
Open Interface Tables, Views, and Concurrent Programs...............3
Oracle Web Applications Desktop Integrator................................... 4
Integration through Native Interfaces.................................................. 6
PL/SQL and Java APIs................................................................... 7
Process-centric Integration................................................................. 7
Oracle Workflow............................................................................. 7
Event-driven Integration...................................................................... 8
Oracle Workflow Business Event System....................................... 9
B2B Integration................................................................................. 10
Oracle XML Gateway and Oracle E-Commerce Gateway.............10
Integration through Web Services..................................................... 11
Oracle E-Business Suite Integrated SOA Gateway.......................11
Oracle Fusion Middleware Adapter for Oracle Applications (also
called Oracle E-Business Suite Adapter)...................................... 13
Oracle Integration Repository........................................................... 14
When to Use What – A Comparative Guide...................................... 16
Native Interfaces Versus Web Services........................................ 16
Service Oriented Integration Versus Event Driven Integration......18
Oracle E-Business Suite Integrated SOA Gateway Versus
Oracle E-Business Suite Adapter.................................................. 19
Oracle E-Business Suite Integrated SOA Gateway Service
Invocation Framework Versus Other Web Service Clients............21
Oracle Workflow Versus Oracle BPEL Process Manager.............21
Oracle Mediator Versus Oracle BPEL Process Manager Versus
Oracle Service Bus....................................................................... 23
Oracle Integration Repository Versus Oracle Enterprise
Repository.................................................................................... 26
Oracle XML Gateway Versus Oracle E-Commerce Gateway
Versus Oracle B2B....................................................................... 28
Conclusion........................................................................................ 29
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
Introduction
One of the most pervasive challenges for organizations is integrating their individual software
applications, ERP, and custom installations that automate their business tasks and processes.
Increasingly, organizations are realizing that collaboration with supply chain partners can
enhance their productivity, and that aligning business processes across enterprise
departments can reduce operational costs. It has become important to address each
integration need with the right approach and the right enabling technology.
Oracle E-Business Suite recognizes the importance of integration and has opened several key
integration points supporting different integration technologies. While an integration point may
be available through various technologies and products, it is important to use the best
approach for the particular integration requirement. This document outlines common enterprise
application integration styles and the various Oracle E-Business Suite products and
technologies provided within the application technology layer to address the specific needs of
these integration styles. This document also presents a comparative guide on when to use
which integration-related Oracle E-Business Suite product.
1
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
• Data-centric integration
• Integration through native interfaces
• Process-centric integration
• Event-driven integration
• B2B integration
• Integration through Web services
Oracle E-Business Suite provides a robust set of native technologies and
products to address each of the above integration styles.
Data-centric Integration
Data integration is the process of consolidating, managing, and moving
information from different data sources, including databases, data files, and
applications such as ERP, CRM, legacy, and data warehouses. In most data
integration scenarios, data is moved on a regular schedule that ranges from
hourly to nightly or biweekly intervals. Data integration is usually used in
conjunction with services that ensure data integrity, such as data de-
duplication and data cleansing.
Data-centric integrations address the requirement of bulk data replication
across different systems and bulk data upload. An example of data-centric
integration is bulk upload of recurring transactions such as sales orders
which need to be tallied for commission payment to appropriate salespeople.
at different layers – that is, a custom user interface in the presentation layer,
custom application logic, and custom tables. Another example is using native
APIs to retrieve statistics from Oracle E-Business Suite database and create
custom reports.
Process-centric Integration
A business process is a coordinated set of business functions that may be
driven by human actions or governed by automated business rules. Complex
business processes may involve multiple enterprise applications, whereas
simple processes happen within one application, such as a performance
appraisal process within an HR application.
Oracle Workflow
Oracle Workflow provides a workflow management system that supports
business process-based integration within Oracle E-Business Suite applications.
It enables modeling, automation, and continuous improvement of business
processes, routing information of any type according to user-defined business
rules. Oracle Workflow Builder provides a graphical drag-and-drop process
designer.
7
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
Event-driven Integration
Event-driven integrations can address the requirement to allow asynchronous
actions or initiate a long-running offline business process on the occurrence of a
business event. This type of integration is also used to monitor key business
events and status updates. It provides a non-intrusive mode of enterprise
application integration. For example, an enterprise application can raise a
business event whenever a purchase order is created or updated. Interested
parties can subscribe to this business event, and depending upon business rules
send an alert or notification to the floor manager on stock levels.
8
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
You can communicate events among systems within your own enterprise and
with external systems as well.
For more information on the Oracle Workflow Business Event System,
refer to the following documentation:
• Oracle Workflow Developer’s Guide
• Oracle Workflow API Reference
9
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
B2B Integration
B2B is the integration of an enterprise application and its business processes
with external business applications operated by customers, suppliers, and
trading partners. Business data are exchanged between trading partners in
standard format. These integrations are driven by industry-level standards
such as OAG, IFX, and EDIFACT.
Oracle Fusion Middleware Adapter for Oracle Applications (also called Oracle E-
Business Suite Adapter)
Oracle E-Business Suite Adapter provides comprehensive, bidirectional,
multimodal, synchronous and asynchronous connectivity to Oracle E-Business
Suite from non-Oracle applications through Oracle Fusion Middleware SOA
Suite. It exposes integration interfaces in Oracle Integration Repository as JCA
services, which can be consumed from Oracle BPEL Process Manager and Oracle
Service Bus.
13
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
Figure 12: Generating Web service artifacts for a PL/SQL API from Oracle
Integration Repository
Oracle E-Business Suite customers can also upload Oracle E-Business Suite
customizations and extensions to the repository to get a unified view of
Oracle E-Business Suite and their customizations. The custom interfaces can
be uploaded to Oracle Integration Repository in three simple steps:
• Annotate the custom interface source file following the published Oracle
Integration Repository annotation standards and guidelines.
• Validate the annotated source file using the Oracle Integration Repository
Parser tool. Annotations are extracted as an ildt file.
• Upload the ildt file containing the parsed annotations using the
FNDLOAD utility. The custom interface information is then accessible
from Oracle Integration Repository.
For more information on Oracle E-Business Suite Integrated SOA
Gateway, Oracle Integration Repository, and Oracle E-Business Suite
Adapter, refer to the following documentation:
• Oracle E-Business Suite Integrated SOA Gateway User’s Guide
• Oracle E-Business Suite Integrated SOA Gateway Developer’s Guide
15
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
Conversely, consider a scenario where you want to select a supplier based on the
quote price. Oracle E-Business Suite has published an API to get the quote price.
Suppose that a business event is also raised whenever there is a change in the
quote price. In this case, it is advisable to use the Web service to get the quote
price from Oracle E-Business Suite instead of subscribing to the business event.
Following are the key considerations for cases in which you should use
Oracle E-Business Suite Web services rather than using business events
through the subscription model:
18
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
Oracle E-Business Suite Integrated SOA Gateway Versus Oracle E-Business Suite
Adapter
The Oracle E-Business Suite Adapter from Oracle SOA Suite is the only
solution that service-enables Oracle E-Business Suite in Release 11i and
Release 12.0. However, from Oracle E-Business Suite Release 12.1.1 on,
customers have two options for SOA-based integration with Oracle E-
Business Suite: Oracle E-Business Suite Adapter and Oracle E-Business
Suite Integrated SOA Gateway. This section will examine when to use Oracle
E-Business Suite Integrated SOA Gateway versus Oracle E-Business Suite
Adapter for SOA-based integrations with the most recent release of Oracle
E-Business Suite, Release 12.1.3.
19
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
interface tables and EDI maps are two interface types that are not supported
as Web services through Oracle E-Business Suite Integrated SOA Gateway in
Release 12.1.3. Consequently, if you know which API you want to use as Web
service, check the underlying interface type. PL/SQL APIs, concurrent
programs, and Oracle XML Gateway message maps can be exposed as Web
services from Oracle E-Business Suite Adapter as well as Oracle E-Business
Suite Integrated SOA Gateway.
The next deciding factor is whether you have any requirements such as
support for an asynchronous interaction pattern, transaction in distributed
processing, and other Web service standards such as MTOM and Reliable
Messaging. These requirements are supported for Oracle E-Business Suite
Adapter by nature of the parent Oracle SOA Suite and OWSM framework.
Finally, if you need a SOAP-based Web service, then you should use Oracle E-
Business Suite Integrated SOA Gateway instead of Oracle E-Business Suite
Adapter, which provides JCA-based Web service binding.
In general, you can define simple to medium business processes using Oracle
Workflow.
Starting in Release 12.1.x, Service Invocation Framework from Oracle E-
Business Suite Integrated SOA Gateway provides a mechanism to invoke
external Web services from Oracle E-Business Suite. As part of a workflow
process in Oracle E-Business Suite, you can invoke an external Web service
by raising a business event. However, if your business requirement is to
invoke a Web service in real-time as part of business process, then you may
need to consider a BPEL process. Because the reason is that SIF uses a Java-
based rule function to invoke a Web service, whereas a workflow process is a
database level process and so the event is executed in deferred mode. Hence,
if you have business logic implemented in Java, then you can invoke web
service synchronously from Java layer.
Also, as of Release 12.1.3 SIF does not support the asynchronous with
callback interaction pattern. Consequently, if the target Web service
prescribes the asynchronous with callback interaction pattern, then you
should use BPEL, which supports this pattern. If a key requirement is
support for advanced notifications such as SMS, voice, or instant messaging,
then you should consider using Human Workflow with BPEL.
Additionally, if you foresee extensive use of XPath, XSLT, or XQuery-based
data manipulation steps between process activities or steps, then you should
consider Mediator with BPEL, since Oracle Workflow does not support these.
Oracle Workflow does support error and exception handling. The Workflow
Engine traps errors produced by function activities by setting a save point
before each function activity. If an activity produces an unhandled exception,
the Oracle Workflow Engine performs a rollback to the save point and sets
the activity to the ERROR status. However, if you need to implement complex
compensation and error handling logic in your business process, then BPEL
supports these.
Another aspect to consider is how you model business processes. Oracle
Workflow processes can be defined using a standalone desktop tool called
Oracle Workflow Builder. BPEL and BPM provide a more user-friendly
graphical tool to build and review business process, available as a plug-in to
Oracle JDeveloper.
Oracle Mediator Versus Oracle BPEL Process Manager Versus Oracle Service Bus
If your requirement calls for SOA components from Oracle Fusion
Middleware, consider the following points to decide when to use Oracle
Mediator versus Oracle Service Bus, and Oracle Service Bus versus BPEL.
23
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
Figure 17: Oracle Service Bus versus Oracle BPEL Process Manager
The key considerations for choosing BPEL over Oracle Service Bus are:
• Service needs to maintain state
• Service requires complex transaction management
• Multiple transactions required
• Compensation logic required on rollback
• Long-running business process
25
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
Oracle XML Gateway Versus Oracle E-Commerce Gateway Versus Oracle B2B
Oracle E-Business Suite provides built-in support for various business-to-
business transactions across various industries. Oracle XML Gateway and
Oracle E-Commerce Gateway provide the infrastructure to support the
business-to-business transactions, while the relevant Oracle E-Business Suite
applications predefine and ship the transactions to provide a meaningful
transaction process flow. These transactions support industry standards such
as OAG, Rosettanet, UCCNet, cXML, EDIFACT, ASX12, and ODETTE. XML-
based transactions are provided through Oracle XML Gateway, whereas
ASCII flat file-based transactions are provided through Oracle E-Commerce
Gateway. The EDI transactions through Oracle E-Commerce Gateway are
batch-oriented, while Oracle XML Gateway messages are event-based and are
transactional in nature.
In fact, because Oracle XML Gateway provides a set of tools and services to
define custom transactions, you can use Oracle XML Gateway for any DTD-
based XML transactions. However, Oracle XML Gateway does not support
XSD-based XML message creation or consumption. Consequently, Oracle E-
Business Suite supports built-in OAG transactions only through version 7.2.1;
the more recent versions of OAG based on XSD are not supported through
Oracle XML Gateway. Oracle XML Gateway supports the following transport
and communication protocols: HTTP, HTTPS, SMTP, JMS, and SOAP over
HTTP/HTTPS. Similarly, you can use Oracle E-Commerce Gateway for any
ASCII flat file-based transactions. You may need to use third party EDI
translators for mapping and conversion to industry standards such as
EDIFACT, ASX12, and ODETTE. The transport and communication of EDI
transactions through VAN depends on third party implementation.
Oracle B2B is a binding component from the Oracle SOA Suite platform that
enables the secure and reliable exchange of business documents between an
enterprise and its trading partners. Oracle B2B supports business-to-business
document standards, security, transports, messaging services, and trading
partner management. Oracle B2B also supports Health Level 7, which enables
health care systems to communicate with each other.
Protocol Oracle XML Oracle E- Oracle B2B
Gateway
Type Commerce
Gateway
Document Only DTD based ASCII flat file All versions of EDIFACT, EDI X12,
HL7.
Protocol versions of OAG based only, RosettaNet PIP business
(7.1, documents, OAG,
7.2) and cXML depends on cXML, Positional flat file (includes
third SAP
transactions that party EDI iDoc). UCCnet, NCPDP Telecom,
are EDIEL.
shipped by Oracle translators.
E-
Business Suite
applications.
RosettaNet PIP
business
documents
are supported
through
Supply Chain
Trading
28
Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer
Connector.
Packaging MIME, SOAP Not applicable. MIME 1.0, S/MIME 2.0, S/MIME
3.0,
protocol ASCII flat files SOAP, XML digital signature
(XMLDSig),
are generated XML encryption (XMLEncrypt)
and
consumed.
Transport SMTP, HTTP, Not applicable. AQ, Email (SMTP 1.0, IMAP 1.0,
POP3),
Protocol HTTPS, JMS ASCII flat files File, FTP and SFTP (SSH FTP),
HTTP
are placed in (HTTP 1.0, HTTP 1.1) and HTTPS
file
system. File (HTTPS 1.0, HTTPS 1.1), JMS,
TCP/IP
transport may
be
handled by
third
party software.
Message AS1-1.0, AS2-1.1, MLLP-1.0,
ebMS-1.0,
exchange ebMS-2.0 (ebXML Messaging
Service),
protocol RosettaNet-01.10, RosettaNet-
V02.00,
Generic File-1.0, Generic AQ-1.0,
Generic
FTP-1.0, Generic SFTP-1.0,
Generic JMS-
1.0, Generic HTTP-1.0, Generic
Email-1.0,
Generic TCP
Conclusion
Oracle E-Business Suite provides various options to integrate its functional
capabilities with other Oracle applications as well as third party enterprise
applications. To completely use the power of integration, it is imperative to
understand different enterprise integration styles and the different products
in the application technology layer of Oracle E-Business Suite that cater to
each of these integration styles, as well as the other Oracle products that
supplement these products from Oracle E-Business Suite. It is important to
understand when to use which product offering. This white paper outlines
the recommended integration strategy for Oracle E-Business Suite
applications with any other application.
29
Oracle E-Business Suite Release 12.1.3: Copyright © 2012, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the
Integration Products and Technologies Primer contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
October 2012 warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
Author: Rekha Ayothi fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are
Contributing Authors: Clara Jaeckel, Rajesh formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
Ghosh , Steven Chan, Veshaal Singh means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle Corporation
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
World Headquarters
500 Oracle Parkway
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
Redwood Shores, CA 94065
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
U.S.A.
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open
Worldwide Inquiries: Company, Ltd. 0112
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com