Notesale: Turn your study into money

Document Preview

Extracts from the notes are below, to see the PDF you'll receive please use the links above

---

Chapter 3
...


- Status of the cloud
* Cloud service providers (CSP) are experimenting new cool things
3-1

# Infrastructure as a service (IaaS), platform as a service (PaaS), software as a service (SaaS),
security as a service (SaaS), storage as a service (STaaS), network as a service (Naas),
database as a service (DBaaS), communication as a service (Caas), monitoring as a service
(MaaS), cloud migration as a service (C-Maas), IT as a service (ITaaS), …
* Enterprises are moving their business services and applications to the cloud
# Currently, enterprise data and applications are linked via standard-compliant integration
platforms within the corporate intranet
# Enterprises are going global
# Moving to and integration with the cloud: ERP, B2B, B2C, …

- An enterprise’s cloud integration
* Enterprise-to-enterprise (E2E)
* Enterprise-to-cloud (E2C)
* Cloud-to-cloud (C2C)

(b) The challenges of SaaS
- Challenges of SaaS
* Integration problem
# SaaS applications are point solutions and service one line of business
# Problem: data synchronization between multiple lines of business
* APIs are insufficient
# Accessing and managing data via API requires a significant amount of coding and
3-2

maintenance due to frequent API updates
# There is little or no standardization on SaaS APIs: IT department expends time dealing with
the APIs of each SaaS applications
* Data transmission security
# Data are secure within the hosted environment
# Data transfer between on-premise systems and SaaS applications may not be secure
# Require integration efforts for the diverse, distributed, and decentralized data
# Data integrity, confidentiality, quality, and value have to be preserved

(c) Integration as a service
- Integration as a service (IaaS)
* Migration of the functionality of enterprise applications into the cloud and provide smooth
data transport between enterprise and SaaS applications
* Data may be duplicated between on-premise and off-premise applications: need to be
completely and compactly synchronized
* Dynamic SaaS APIs worsen the integration problem
* Limited access to the cloud presents another problem
# Accessing local applications is much easier than clouds
# Set local integration points are easy in local applications, but difficult in SaaS applications
# E
...
, SalseForce
...
e
...
g
...
com Integration
- Link enterprise and cloud systems via messaging
* Messaging: asynchronous information delivery as oppose to a request-response architecture
* Message-oriented middleware (MoM): software or hardware infrastructure that supports
3-11

sending and receiving messages between distributed systems
* Allows applications to be distributed over heterogeneous platforms
* Reduces the complexity of developing applications that span multiple operating systems and
network protocols
* Cloud services and applications could be loosely or lightly coupled, or decoupled
* Examples:
# Informatica On-Demand Services
- On-demand data integration in
SaaS applications
# Microsoft Internet Service Bus (ISB)
- Microsoft
...
NET service bus: provides the
messaging channel for connecting
cloud applications to on-premises
applications, services and systems
(see right figure)
-
...
NET workflow service: rule-based control flow based on Windows Workflow Foundation
3-12

(WWF)

(e) Business-to-business integration services
- Business-to-business integration (B2Bi)
→ Extend business processes to business partners including customers, vendors, suppliers,
distributors, and other alliances
* Pure EAI: only for internal data share
* B2Bi has the following capabilities:
# Encrypt files for safe passage across the public network
# Manage large data volumes, transfer batch files, and convert disparate file formats
# Guarantee data accuracy, integrity, confidentiality, and delivery
* Provides connectors for major ERP, CRM, SCM, …

- Cloud-based enterprise mashup integration services for B2B scenarios
* Mashup: combination of different and distributed resources including content, data or
application functionality
# Resources represent the core building blocks for mashups, and can be accessed through
APIs
# Widgets or gadgets put a face on the underlying resources by providing a graphical
representation and piping the data received from the resources
# Piping can include data aggregation, merging, or filtering
* Enterprise mashups: users integrate heterogeneous digital data and applications from multiple
3-13

sources
* In an enterprise mashup, the product is typically a combination of internal corporate data and
applications with externally sourced data, SaaS, and Web content
* Why enterprise mashups are needed?
# Mashups gives faster answers
# Mashups improve resource use (of both personnel and soft/hard computing resources)
# Mashups help address new business opportunities by letting users assemble internal and
external data in an opportunistic way
* SOA: one of the promising solutions to enterprise mashup

- Enterprise mashups platforms and tools: FAST project
* Mashup integration services are being implemented as a prototype (see the following figure)
* The prototype architecture shows the services and their relations to each other
* Users access the services through a mashup platform of their choice
* Mashup platforms are connected via APIs to the mashup integration services
* All data coming from the users go through a translation engine to unify the data objects and
protocols, so that different mashup platforms can be integrated

- B2Bi examples
* Clarizen Salesforce

---