Академический Документы
Профессиональный Документы
Культура Документы
• Enables you to configure and not code your integration with the
Application.
• Cuts out extensive groundwork required for the integration
• Requires developers with technical skill-sets to implement the integration.
• Most SaaS Apps have Complex APIs - Lengthy documentation of API specs and semantics
• Data Mapping using the out-of-the-box data models of the applications has proven to be complex
• Need for manual management of core capabilities such as security, session management,
connection management etc
• Need to handle customizations and revisions of the SaaS Applications
• Inbound Integrations often require the Apps team to perform configuration/write code
•Design-time Plugin
•The designer-component of the Adapter that implements the UI
and Design-time APIs.
•Needs to be Registered with the design-time Component (Jdev, ICS
etc) for end-user to use.
•Generates integration artifacts that carry information to connect
and exchange messages with the Application.
•Runtime Plugin
•Performs the connection and message exchange at Runtime using
the Runtime APIs
•Integrates with the SOA/SB/ICS Runtime via the JCA Binding
Component.
•Needs to be Registered with the Runtime component (SOA,
Service Bus, ICS etc) to be functional.
Develop Package
Build the Adapter Package the
1 design-time and 2 plugins with the
runtime plugins required
using the SDK. descriptors
Register Consume
Register the Adapter now
3 plugins with the 4 ready to be used
design-time and in Integration
Runtime Projects
Runtime Handlers