Accelerate your SaaS Integration The Cloud Adapter SDK Copyright © 2014, Oracle and/or its...

Accelerate your SaaS IntegrationThe Cloud Adapter SDK

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |


Cloud Adapters

• 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

Value Proposition


What is the Cloud Adapter SDK?• Java APIs to build Connectors to SaaS Applications from Inception to

Release• Helps Transform Developer-centric API of SaaS Applications to a Simplified

Business Centric View of the Integration• Enables you to Build, Test and Release Connectors Quickly!• Build once and Deploy Anywhere–On Premise : SOA, Service Bus, BPM – Cloud : Integration Cloud Service, SOA Suite Cloud Service


Key Components• The UI Framework– Build a Wizard based UI for JDeveloper based designer experience– Build a Web UI for Service Bus Console/Integration Cloud service designer experience– Provides end user a Highly Refined User Experience

• The Design-time APIs– Connect, Parse and Build a simplified Data Model from the APIs of the SaaS App– Generate required integration artifacts at design-time

• Runtime APIs– Actual Message Exchange with the Application. Could involve security, session

management etc.


A Closer Look at the APIs


•What artifacts you build using the SDK ?• One jar file that contains two plugins: designtime and runtime.

•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.

Components


Adapter Plugin Lifecycle

1 2

43

Develop Package

Register Consume

Build the Adapter design-time and runtime plugins using the SDK.

Package the plugins with the

required descriptors

Register the plugins with the design-time and

Runtime

Adapter now ready to be used

in Integration Projects


Let us watch the Cloud Connector in Action!


Demo overview• Aims to showcase overall lifecycle and key milestones for delivering a Cloud

Connector from Inception to Release• Walk-through of design-time and runtime plugin development• Walk-through of the registration procedure• See the fully built adapter in action in the Cloud!


Development Tasks


1. Plugin Project/Jar Setup


Plugin Project/Jar Setup Demo:

A close look at the key plugin descriptor - cloud-adapter.xml


2. Implement the Connection API• Stores properties (including credentials) required to connect to a SaaS

application• Defines connection properties as metadata (PropertyDefintions)• Stores connection properties as name/value pairs• Provides validation method for testing connections. AKA: Ping


Connection API Demo:

Handling "ping" in Connection API


3. Implement the Metadata Browsing/Modeling API• Metadata browser – read only view of application metadata• Application Metadata includes operations, faults, objects, fields

relationships.• Cloud Application Model – storage for all metadata objects.• Cloud Application Model is produced by parsing various metadata artifacts

for a SaaS application: WSDLs, schemas, JSON schemas, SOAP, etc.• UI loads Metadata using connection info. • Metadata is cached for performance


Metadata Browsing/Modeling API Demo:

Handling static and non-static metadata


4. Implement the Generation API• Generation of standard artifacts (JCA + WSDL) are handled by the

framework.• Custom generators can be plugged in to process files differently• Integration WSDL contains single selected operation, selected data objects,

and any modifications made by plugin or user.• JCA file contains all connection and operation properties.


Artifact Generation API Demo:

Specifying Runtime Properties


5.Implement the Runtime Components


Runtime Transformation API


Runtime API Demo:

Runtime Handlers


6. Package and Register with ICS

See the Adapter in Action

Accelerate your SaaS Integration The Cloud Adapter SDK Copyright © 2014, Oracle and/or its...

Documents

Transcript of Accelerate your SaaS Integration The Cloud Adapter SDK Copyright © 2014, Oracle and/or its...