This my presentation for my colleagues who need to know about Cloud specially Oracle Cloud Integration basics , through these few slides I tried to cover the basics and some Integration patterns using (ICS , JCS paas / saas).

1. Oracle Cloud Integrations
Overview
BY : ABDELRAHMAN EL-SHEIKH
SOFTWARE ENGINEER
1

2. Integrations 2

3. Agenda
 1- Integration Challenges
 2- PaaS - SaaS Integration Patterns
 3- Java Cloud Service - ( SaaS Extension - PaaS)
 4- Oracle ICS
 5- Five Ways to Simplify Cloud Integration
3

4. Agenda
 1- Integration Challenges
 2- PaaS - SaaS Integration Patterns
 3- Java Cloud Service - ( SaaS Extension - PaaS)
 4- Oracle ICS
 5- Five Ways to Simplify Cloud Integration
4

5. Integration Challenges 5

6. Integration Challenges cont.
 The rapid shift from on-premise applications to a hybrid mix of
Software-as-a-Service (SaaS) and on-premise applications has
introduced big challenges for companies attempting to simplify
enterprise application integration .
6

7. Integration Challenges cont.
Challenges with Cloud Integration - Source: Dynamic Markets – Cloud for Business Managers, the Good, the Bad, the Ugly
7

8. Agenda
 1- Integration Challenges
 2- PaaS - SaaS Integration Patterns
 3- Java Cloud Service - ( SaaS Extension - PaaS)
 4- Oracle ICS
 5- Five Ways to Simplify Cloud Integration
8

9. Introducing Oracle Cloud Platform 9

10. PaaS - SaaS Integration Patterns 10

11. PaaS - SaaS Integration Patterns 11

12. Agenda
 1- Integration Challenges
 2- PaaS - SaaS Integration Patterns
 3- Java Cloud Service ( SaaS Extension - PaaS)
 4- Oracle ICS
 5- Five Ways to Simplify Cloud Integration
12

13. Java Cloud Service - SaaS Extension
 Java platform specially built to deploy extension for Oracle Software
as a Service offerings, including Sales Cloud, Service Cloud, and
Marketing Cloud.
 Dedicated environment running WebLogic Server.
 Three pre-configured sizes available: S1 (small one-node cluster), S2
(medium two-node cluster), and S4 (large four-node cluster).
 Fully managed by Oracle.
 Applications are managed through Oracle Cloud tooling; no
customer access to the underlying infrastructure is required.
13

14. Java Cloud Service - SaaS Extension 14

15. Java Cloud Service - PaaS
 Pre-configured WebLogic Server software, with your choice of the 11g or 12c version.
 Full access to the underlying infrastructure, with the ability to customize the environment for your
application.
 Ideal for development, testing, user acceptance testing, staging, and production.
15

16. Java Cloud Service - SaaS Extension
 How is Oracle Java Cloud Service - SaaS Extension different from Oracle Java
Cloud Service?
 The differences lie in how you will use the service: Java Cloud Service supports
deployment of custom business application development while you would use Java
Cloud Service–SaaS Extension to build extensions to existing Oracle SaaS products, such
as CRM, HCM, and so on.
 With Oracle Java Cloud Service - SaaS Extension, you cannot access the configuration
of the underlying application server, JVM, and/or operating system for any services,
while this is possible with Oracle Java Cloud Service.
 Java Cloud Service - SaaS Extension supports Single-Sign On (SSO) out of the box. Once
federation is enabled in the data center where your Software as a Service (such as Sales
Cloud, Service Cloud, Marketing Cloud, and so on) is running, your Java Cloud Service -
SaaS Extension applications won’t require any changes to enable SSO capabilities.
16

17. To simplify : JCS vs JCS-SX
JCS JSC - SaaS Extension
Ideal for development, testing, user acceptance testing,
staging and production
Ideal for extending your Oracle SaaS applications.
Seamlessly embed new functionality in existing SaaS
services' UI, and create standalone mashup applications
using data feeds from SaaS services
Maintain complete control and customization of your
environment, including full access to the underlying
infrastructure
Fully managed by Oracle to create a SaaS-like
experience from start to finish and you cannot access the
configuration of the underlying application server, JVM,
and/or operating system
Built-in continuous build and deployment platform, with
complete project and team management for highly agile
teams.
Build extensions with guaranteed compatibility with Oracle
SaaS apps by utilizing the exact same platform that
delivers Oracle SaaS services.
17

18. Agenda
 1- Integration Challenges
 2- PaaS - SaaS Integration Patterns
 3- Java Cloud Service - ( SaaS Extension - PaaS)
 4- Oracle ICS
 5- Five Ways to Simplify Cloud Integration
18

19. What is Oracle Integration Cloud Service?
 What it does:
 Integrates applications across clouds and on-premises
 Key Features
 Easy to use for LOB developed integration
 Prebuilt integrations for common scenarios
 Recommendations to guide mapping
 Automated back-up, patch updates, and upgrades
 Library of connectors for Oracle and 3rd party
applications
 Benefits
 Faster integration of applications
 Increased business agility
 Lower cost of ownership
ON-PREMISES
3rd Party
Salesforce
Oracle
Integration Cloud Service
Oracle SaaS
Applications
19

20. What is Oracle Integration Cloud Service?
Key Features
 Simplified: web based, point & click integration experience
 Intuitive Visibility: Rich monitoring & error management
 Lifecycle : Support both on-premise, cloud lifecycle tools
 Managed: Oracle back-ups, patches, upgrades
Benefits
 Pre-integrated: SaaS, Auto-Association
 Rich Connectivity: Cloud & On-premise connectors
 Rapid: fully automated provisioning
20

21. Agenda
 1- Integration Challenges
 2- PaaS - SaaS Integration Patterns
 3- Java Cloud Service - ( SaaS Extension - PaaS)
 4- Oracle ICS
 5- Five Ways to Simplify Cloud Integration
21

22. Five Ways to Simplify Cloud Integration
 #1 – Prebuilt integration:
Until recently, all integrations needed to be created from the ground up, requiring
integration architecture design, testing, debugging, redesigning due to lessons
learned, pushing into production and then fine-tuning some more of the design. This
time consuming and costly development cycle may be required for niche
integrations that are not common to most businesses. But what about integrations
that are used by a wide range of different industries…should these common
integrations be re-invented by every company?
22

23. Five Ways to Simplify Cloud Integration
 #2 – Recommendations :
Recommendations such as these are now
indispensable on retails sites. However, applying the
recommendation concept to integrations inside a
mission critical integration platform is new. Within
Oracle Integration Cloud Service, a recommendation
can come from many sources including Oracle,
customers, and partners. For the customer-based
recommendations, guidance comes from crowd
sourced input of previous users of Oracle Integration
Cloud Service.
 Oracle Recommends – Guidance on
recommended integrations between
applications
23

24. Five Ways to Simplify Cloud Integration
 #3 – Auto Association of Oracle SaaS Applications :
Auto association of Oracle SaaS applications removes the time consuming and error
prone step of having to configure your integration platform prior to integrating
applications. As a customer of Oracle Cloud Applications such as Oracle Sales
Cloud, Oracle Service Cloud, Oracle Marketing Cloud, Oracle CPQ Cloud, Oracle
HCM Cloud or others, you have the ability to bypass the complexity of setting up the
integration platform for these applications.
24

25. Five Ways to Simplify Cloud Integration
 #4 – Intuitive User Experience :
Oracle Integration Cloud Service uses a completely new paradigm to simplify
integration relying only on knowledge of the application itself and not on complex
deep-dive integration terminology.
25

26. Five Ways to Simplify Cloud Integration
 #5 – Public/Private Cloud Portability
What factors determine the level of difficulty in
transitioning an integration platform from public to
private or visa-versa?
There are three primary factors to consider:
1. The use of common integration components for
public and private cloud-based models.
2. The use of common architecture between the on-
premise integration and the cloud-based integration.
3. The use of common standards simplifies integration
portability.
26

27. Why Oracle ICS ? 27

28. Why Oracle ICS ? 28

29. Thanks any Questions ?
29

30. Reference
 oracle.com/integration
 docs.oracle.com/cloud/latest/jcs_gs/index.html
 oracle.com/cloud/index.html
30