Systems on the edge of an enterprise have special challenges regarding availability, scalability, security, and external interactions with systems or people. This applies to external portals, B2B interactions, workflows that involve external actors, mobile APIs, and integrations with software-as-a-service (SaaS) instances. These systems are candidates to move to a public cloud and handle these requirements on the platform-as-a-service (PaaS) platform. This session discusses Oracle PaaS cloud services, their mutual interaction, and how they can be leveraged to move these systems into the cloud: Oracle Java Cloud Service, Oracle Integration Cloud Service, Oracle Process Cloud Service, Oracle Mobile Cloud Service, Oracle SOA Suite Cloud Service, and Oracle Messaging Cloud Service. Conference Session

1. Lucas Jellema
Oracle OpenWorld 2015, San Francisco, 27th October 2015
Systems on the Edge—Your Stepping
Stones into Oracle Public Cloud and the
PaaS Platform [CON3122]

2. 2
Overview
• Promises of the Cloud
• Edge Systems
– What are they – attributes
– Common Challenges
– How can cloud help address these challenges
• Use cases and
mapping to Oracle Public Cloud Services
• How to get going with edge systems in the public cloud
– And pick the low hanging cloud fruit

3. 3
Cloud Benefits
• Ease and Comfort
• Cost effective
• Flexibility – quick, agile
• Quality
• Security
• Any time, Any place

4. 4
Why is the cloud hot?
• Web Scale for the rest of us
– Availability, Scalability, Security, …
• No specific expertise or even effort for consuming services
– No need to acquire skills, build up experience and hire special resources
• No physical facilities – room, cooling, cleaning,
physical security, power
• No/Low initial investment (low entry level)
• Pay per use (no gain, no pain) (CAPEX => OPEX)
• Flexible up and down scaling (capacity on demand)
• Quick Ramp-Up, Rapid Start
• Enterprise functionality for small businesses
– Out of reach in the on premises world
• Accessibility from anywhere
• Global market place
• Lifting the burden from your shoulders
SaaS
PaaS
IaaS

5. 5
Cloud adoption in
bottom-up steps
IaaS/PaaS
Self study
PoC
Training
Load Test
Func Test
Peak, Failover
Peripheral Applications
Backup
BI
Edge Systems
Core Systems & Secure Data
[Distributed] Development
BPO

6. 6
How to get to the cloud?
• Well, that is not the question we will address in this session
• It is a bottom up approach, thinking from current systems
– We will get there - eventually

7. 7
Layered Architecture
Data
Business
Interface

8. 8
Focused Layered Architecture
Data
Business
Interface• Modern
• Volatile
• Tailored
• Variety
• Visible
• Reuse
• Consolidation
• Slowly
evolving
• Long lasting

9. 9
Enterprise Application
Architecture
Data
Business
Interface
Internal UI
Applications
Portal
Web
Applications
External
Web
Services
Citizens, Companies,
Government, Agencies
Internal StaffB2B
Mobile
Web Sites &
Content
Multi
Channel
3rd
party
App
3rd
party
App
Integration
Process
Automation

10. 10
Edge Systems
• What are edge systems?
– Systems accessed by parties (people
or systems) from outside the enterprise
• Typical characteristics
– Visible to business partners & the general public
– Interactions initiated externally – large numbers of
unknown individuals/devices/systems
• External entities accessing systems
– Uses data only indirectly (does not store data)
• Except application specific data and perhaps for caching reasons
Enterprise
DMZ
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents
X
Z
Y
Q
API
Gateway

11. 11
Edge Systems
• Typical Challenges
– High availability requirements
– Scalability/volume/peaks
• License consequences
– Latency
– Security: potentially large numbers of fairly
unknown parties accessing the enterprise realm
– Provisioning environments and network
configuration (timely)
Enterprise
DMZ
Document
Exchange
Website
& Portal
CX
B2B API
3rd Party
Workflow
IoT data
drop-off
Mobile
APIs
API
Gateway
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents
X
Z
Y
Q

12. 12
Edge Systems
moving towards the cloud
Enterprise
DMZ
Document
Exchange
Website
& Portal
CX
B2B API
3rd Party
Workflow
IoT data
drop-off
Mobile
APIs
API
Gateway
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents

13. 13
Edge Systems
moving towards the cloud
Enterprise
DMZ
API
Gateway
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents
Document
Exchange
Website
& Portal
CX
B2B API
3rd Party
Workflow
IoT data
drop-off
Mobile
APIs

14. 14
Edge Systems moving towards the
Oracle Public Cloud
Enterprise
DMZ
API
Gateway
Enterprise
Database
ERP
ESB
Core
Business
Application
Enterprise
Documents
DCS
Sites &
JCS &
Portal
CX
ICS &
SOA CS
PCS
IoT,
Node.JS
MCS

15. 15
How cloud addresses
challenges for edge systems
• High availability requirements
– Web Scale operations
– Multi-site (region)
• Scalability/volume/peaks
– Dynamic, rapid, on-demand upscaling/downscaling
– Pay per use, no upfront investment
• Latency
– Multi Data Center topology, Distributed Content Delivery
• Security: potentially large numbers of fairly unknown parties accessing the
enterprise realm
– Relocation of the DMZ to the cloud
– The only interaction with the enterprise realm is by well-known cloud based systems
– not by many third parties
– Web Scale security measures
• Provisioning environments and network configuration
– Out of the box, click-next-finish, minutes to completion

16. 16
Edge on Cloud <=> On Premises
integration challenges
• Data Pipe
– Two way (cloud  enterprise)
– Synchronous & Asynchronous (event push)
– Secure
– Approach: SSH or even VPN channel, API Gateway in DMZ, local agent on
premises, leverage message cloud (aysnchronous push and pull)
• Data Cache (refresh) & Data Replication
• Identity Management – replication of identities & roles
• UI Integration
– “mash up” and deeplink navigation
– Session sharing and Single Sign On
– consolidated search and menu
– style & web content synchronization
• Software Delivery
– (no more challenging than on site)
Enterprise
DMZ

17. 17
Case:
Monthly Reporting obligation

18. 18
Case:
Monthly Reporting obligation
• Financial institution is faced with the requirement
to monthly report events and status to a
dozen stakeholders such as government agencies
– Each stakeholder receives a customized report
• The challenge: how to deliver the report
– Given functional and non-functional requirements
• Options
– On paper
– Email attachment
– (S)FTP server
– Read only secure web site
– …
• Requirements
– Electronic, On line
– Archive/history
– Searchable
– Multi-format
Enterprise
Enterprise
Database
Core
Business
Application
Enterprise
Documents
Report
Generator
sftp
web
site
email
paper
mail
IAM

19. 19
Case:
Monthly Reporting obligation
Business Partners,
Government Agencies and
other stakeholders
Document
Cloud
Service
Enterprise
Enterprise
Database
Core
Business
Application
Enterprise
Documents
Report
Generatorupload through APIIdentity Cloud
Service
Doc History & Archive
Search
Mobile Access
Secure
Access Audit trail
Social integration
Format conversion

20. 20
Mobility

21. 21
Case:
Mobile App for veterinarians
Enterprise
Service
Bus
SOA
Composite
3rd party
case mgt
Mobile Veterinarian
Enterprise
Database
Core
Business
Application
Enterprise
Documents
B2B Partners
3rd party
ERP
Portal
SOAP2
REST
SOAP  REST
XML  JSON
Some Concerns:
• Volume
• Security
• API unfriendliness
• Development &
maintenance effort
• Monitoring &
Analytics

22. 22
Case:
Mobile App for veterinarians
Enterprise
Service
Bus
SOA
Composite
3rd party
case mgt
Mobile Veterinarian
Enterprise
Database
Core
Business
Application
Enterprise
Documents
3rd party
ERP
Portal
Mobile
ICS |
SOA CS
B2B Partners
API
con
nect
push
anal
ytics
user
mgt

23. 23
Case:
ISV scale down and scale out

24. Customer
Customer
24
Case:
ISV scale down and scale out
• Developing an application for long term project budget management
– Especially for local and regional governments
• Implemented on premises
– Done by technical implementation consultants that go on site with customer
– Challenging to get servers, network, database => long implementation times
• Objective:
– Offer the product to smaller
organizations
(increase reach)
– Offer the product in the
global market place
• Requirement:
– Very rapid implementation
- (turn key == enter URL)
without on site consultancy
– Global accessibility
– Flexible capacity
ISV
IDE
ISV
Developers
Customer
WLS
Database
WLS
Database
End users

25. 25
Case:
ISV scale down and scale out
Enterprise
IDE
ISV
Developers
Database
Java
Optionally use the User Experience
Rapid Development Kit to achieve
Simplified UI based on ADF & Alta
Developer
CS
Social
Document
PCS
MCS
Management
CS
Analytics
ABCS

26. 26
Case: lift and shift application
or replace custom or 3rd party
COTS with SaaS

27. 27
Case: lift and shift application or replace
custom or 3rd party COTS with SaaS
Interface
Internal UI
Applications
Portal
Web
Applications
External
Web
Services
Mobile
Web Sites &
Content
Multi
Channel
3rd
party
App
• Replace custom or COTS application
on premises with SaaS offering
– More functionality, less effort,
easier admin & maintenance,
work anytime any place
– Note: SaaS == Silo as a Service
• Move custom or COTS
application from on premises
to PaaS
– Easier admin & maintenance, better
scaling (up and down), work anytime
any place
• Challenges
– Existing integrations – both API
– UI Mash-up
– Single Sign On (and IAM)
– Data replication & governance

28. 28
Case: lift and shift application or replace
custom or 3rd party COTS with SaaS
Enterprise
IAM
API
Gateway
VPN
Service
Bus
Portal
Enterprise
Users
Enterprise
Database
Core
Business
Application
Enterprise
Documents
Java for SaaS
UI mash up
SSO
Integration
CS
IdM CS

29. 29
Case: lift and shift application or replace
custom or 3rd party COTS with SaaS
SOA
Message
Enterprise
IAM
API
Gateway
VPN
Service
Bus
Portal
Enterprise
Users
Enterprise
Database
Core
Business
Application
Enterprise
DocumentsDatabase
Java
Java for SaaS
UI mash up
SSO
Data Replication
Event Pub/Sub
Integration
CS
IdM CS

30. 30
Case:
the ultimate digital user experience

31. 31
Case:
the ultimate digital user experience
• Pension Fund with high ambitions
– Themes: Digital, self service, 24/7, paperless, STP , Google fast and Apple friendly
– User benefits: higher quality and faster (even pro active) response, great experience
– Business benefits: cost reduction, competitive position, new services, agile: quick time
to market
• Portal and Customer Experience are crucial in this strategy
– Multiple user groups (employees, employers, financial consultants, …
– Multiple brands
– Both public (web site) and personal (authenticated portal)
– Strong integration with back end enterprise systems
– Easy web content management (dialogs, documents, FAQ/knowledge, events& news)
– End to end “interaction & process analytics”
– Security and compliancy regulations
– Multi-channel strategy: portal and B2B are main channels – but not the only ones
(telephone, chat, social, email and for now paper based mail); perhaps mobile as well
• Traditionally, most applications are custom built with Oracle technology and
deployed on-premises

32. 32
Case:
the ultimate digital user experience
WebCenter
Portal
Service
Cloud
Mobile
Document
Cloud
Service
SOA CS
Message CS
Enterprise
IAM
API
Gateway
VPN
Service
Bus
SOA
Composite
BAM
Cloud
Events
BPM
Various
End User Groups
Enterprise
Database
Core
Business
Application
Enterprise
Documents
CRM
B2B Partners

33. 33
The first step in the Case of
the ultimate digital user experience
Service Cloud
Enterprise
IAM
VPN
Service
Bus
SOA
Composite
BAM
BPM
Various
End User Groups
Enterprise
Database
Core
Business
Application
Enterprise
Documents
CRM
B2B Partners
WebCenter
Portal
WebCenter
Content
Service
Bus
Multi-Channel
• Telephone
• Chat
• Email
• Portal
Call Center
App

34. 34
Case: IoT

35. 35
Case: IoT
• Collect physical measurements and
signals from the real world in real time
– Security Sensors, Traffic Flow Signals,
Biomedical Measurements, Weather Conditions,
Earth-Movement-Registration, Logistics Recordings,
• Gather, Filter, Analyze, Process signals to
data, information and findings
• Challenges:
– Availability – real time, 24/7, quick reaction required (sometimes, but very quick)
– Accessibility (from many different locations, many outside enterprise reach)
– Volume (and real time peak capacity)
– Latency (local data drop-off points and decentralized initial processing)
• Conditions
– Limited (initial) enrichment
– Eventual hand-over of findings to enterprise infrastructure and systems

36. 36
Case IoT
IoT
Node.JS
Mobile
ICS
SOA CS
Message CS
Enterprise
Agent
API
Gateway
VPN
Service
Bus
SOA
Composite
BAM
Cloud
Events
Stream
Explorer
High volume
IoT signals

37. 37
How to get going
with an Edge System on the cloud
Enterprise

38. 38
Oracle Public Cloud
Terminology
Identity Domain
DBaaS JCS HCM
Oracle Public
Cloud Services
Account
Data Center
(Region)
Service
Service
Association
Users &
Roles
Oracle
(OTN)
Account
Access
Privilege
Identity
Domain
Identity
Domain
Data
Center
(Region)
Data
Center
(Region)
Identity Domain
JCS SalesICS

39. 39
How to get going
with an Edge System on the cloud
• Create an Oracle Public Cloud account + Identity Domain
• Subscribe to relevant Cloud Services
– Configure these services to (be able to) work together (associations within identity
domain)
• Manage users within identity domain plus service access privileges

40. 40
Oracle Cloud My Home
Services Console

41. 41
How to get going
with an Edge System on the cloud
• Perform development locally (for most cloud services)
– ICS, PCS, ABCS and MCS have development through the browser in the cloud
– Optionally use the Developer Cloud Service to organize (distributed) development
• Implement automated build and deployment to the cloud (Cloud targeted
CD), possibly using Oracle Developer Cloud Service
• All testing is done in the cloud
– unit test, system integration test, acceptance test, automated regression test

42. 42
How to get going
with an Edge System on the cloud
• Implement the bridge between (API calls, navigate/deeplink, UI mash up)
– the various cloud services
– the final cloud services and the on-premises systems
– Also: network configuration to support the bridge
• Arrange for user friendly URLs – for end user User Interface systems
• Implement Identity & Access Management for internal and external users
– Integrate with on-premises IAM systems (replicate to cloud?)
– Single Sign On across cloud and from on premises to cloud
• Set up Cloud Ops – Operations for the cloud based systems & flows
– Oracle Management Cloud

43. 43
Summary
• Do not ask: how to get to the cloud
• Starting point is why?
Cloud fulfills a business need or provides a
business opportunity
– That is the driver and the business case justification
• Edge systems have common requirements, challenges and opportunities
– Many of which are dealt with by cloud based solutions
– The business case is quickly defined – using speed, capacity, flexibility, availability,
security, functionality and TCO
• Typical edge systems use cases include:
– B2B, Portal, Mobility, Silo-as-a-service (lift and shift)
• Other low hanging cloud fruit
– Development automation, Back up, Long term archive, Monitoring (real time analytics
on log files and operational metrics), BI and Tactical Analytics
• An initial investment is required: time, effort, frustration, learning curve
– Opportunity to be an early adopter and reap benefits quickly

44. Blog: http://technology.amis.nl
Twitter: lucasjellema
Mail: lucasjellema@gmail.com