Integration Of Applications,

1
Integration Of Applications, A Challenge Of Any
Modern Company
Marilza Maia Sr. IT Architect mmaia_at_us.ibm.com
2
Agenda

• SOA Reference Architecture
• BPM Suite and Technology
• Integrating information, services, processes,
  and policies for variability
• Customer Experiences
• Large TELCO Company in Europe
• Police Services SOA Solution
• Large Bank in the United States
• Insurance Company in the United States
• Energy and Utilities in the United States

3
SOA Reference Architecture
4
Targeting an Integrated Business Integrity
Management Framework
Today
Emerging
Future
Business Integrity
Policy
Core Entities
Process
Services
An integrated and automated approach to policy,
process, services and core entity management
emerges.
Today information, processes, services and
policies are typically inconsistent and incomplete
Emerging solutions address consistencies and
management of policies, processes, services and
core entities independently
5
The Engine of a Robust, Integrated BPM Suite
Composite Business Applications
Business Services
Pre-built Industry Accelerators
Business
Roles
Channels
Content
Process Execution
Business Processes
ESB
Registry Repository
BPM
SOA
IT
Partners
Outsourced
On-premises
Respond Quickly to Business Demands with Powerful
Capabilities
6
Manage BPM and SOA Assets across their
LifecycleAccelerate time to value across the BPM
lifecycle
Manage IT Assets (e.g. BPEL, WSDL)
Manage Business Assets (e.g. Models, Roles)
IT Leader
IT Architect
Govern and Perform Impact Analysis
Publish and Deploy
Administer Repository


Federated Search And Publish

Design-time
Run-time
WebSphere Services Registry and Repository
Advanced Lifecycle Edition
7
Integrating information, services, processes, and
policies for variability
8
Moving business logic away from Business Process
design into metadata and policies
Business Process
Process segment with many different service
permutations and complex service mediation. Eg
Billing service to access either Mobile Billing
System, or Fixed Line Billing system
Services
B
B
C
C
A
A
A
End Points
a1
b1
b2
c1
c2
a2
a3
Business Process
Services
A
A
End Points
a1
a2
Business Services
B
C
Business Service Repository
Policies
Composition development
Meta-Data
Business Services Dynamic Assembler
End Points

b2
b3
c1
c2
N
d1
d2
b1
9
Defining modularity from Business Process
Modeling Notation (BPMN) categories
There are three basic types of sub-models within
an end-to-end BPMN model 1. Collaboration
Processes exchanges between 2 independent
business entities. 2. Abstract (public)
processes End to end view from a participant
point of view. 3. Private
(internal) business processes single business
owner and a main core entity
e.g. Supplier/Partner Interactions
Monitoringmodel
e.g. Order to bill
Contract variability between the wagons-
Separation of services
e.g. Customer Service
e.g. Manufacturing
e.g. Billing
e.g. Accounting
e.g. Supply Chain
Automationmodel
Business Services link the private processes
together
10
Example of Rules and Policies for simplifying
processes and for dynamicity Activation Service
Specific Process is Plugged In at Runtime
Customer Location Wellington, Auckland,
Policy owned by the business controls which
variation is used.
Product Type Multiple Play, High Definition
VoD,
If the customer's category is residential and
the value of the customer's average spending is
more than 150 Then change the Elite Status to
Gold
For the ActivateConnection Business ServiceWhen
Product is Triple Play AND Channel is Web AND
Role is Self Service OR Customer is
Residential Then Elite Status is Gold AND Use
the Activate Fiber To Home Process
Activate Connection Service
ILog Rules
The lifecycle and implementation of each
variation is now de-coupled from the main
process.
Business Space Policy
Activate DSL
Activate Fiber To Home
Activate Wireless (FUTURE)
11
Normalization of enterprise activities
Business and technical information model
normalization
Business city planning map and business
processes normalization
SID, ACORD, CIM, IFW
APQC, SCOR, eTOM, IFW
Application city planning implementation map
normalization including interfaces and services
CIM, IEC 61968, OAGIS, IFW, TAM (TMF).
Technical infrastructure normalization
OSGi, WS-I, SOA reference architecture
12
Large TELCO Company in Europe
13
eTOM Processes also are at Level 3 Order
Handling
14
Catalog Driven Business Process
eTOM Processes
SID Catalog
Decompose each products in services and loop on
services
Service Characteristic Specification
Characteristic Value in Catalog contain the
configuration values to use
15
Using SID Product Customer Resource Facing
Service structure to create Catalog driven
business processes
Commercial View Product
Multiple Play
Pasarella (multiple play for family)
TV
Voice
Broadband
Music
Monitoring
HDTV
TV Packages
STB Rental
STB Sale

Functional View Service
IPTV (VoD)
GPON
DTH
VoIP Account(s)
ADSL Access
Wireless
VoIP Config
Ethernet
ATM
Resource
VoIP Buddy List
VoIP URI
VOD Channels
ATM Circuit
Set Top Box VoIP
Set Top Box TV
Set Top Internet access
16
Information Variability Pattern from Telco SID
Standard
Name of ASE Definition
Entity Entities represent classes of objects that play a business function. Entities can be either managed or unmanaged.
Specification Specifications are used to define the invariant characteristics (attributes, methods, constraints, and relationships) of an object. Specifications exist for ManagedEntities, Products, Resources, Services, Locations, Roles, Policies, and Processes.
Role (can be defined for human and non-human) Roles characterize the function that a particular object plays. The characterization may be to specify attributes, methods, constraints, and/or relationships that the entity has.
Location Locations are used to identify a position, address, geographic area, or particular structure.
Identity Identities are used to enable an object to be recognized. Some objects can be recognized by one of several identities.
Policy A Policy is a set of rules that is used to manage and control the changing or maintaining of the state of one or more objects. This ASE contains objects that can represent policies as well as define how they are used by management applications.
Interaction An Interaction is an arrangement, contract, communication or joint activity between one or more participants (which can be Parties or Entities). An Interaction may refer to a Product, Service, Resource, and involve particular Locations.
Party A Party is an abstract concept that represents groups of People and/or Organizations.
ManagementDomain A ManagementDomain represents a special grouping of ManagedEntities that has two important properties. First, it is used to partition managed objects into a meaningful logical grouping. Second, it defines a common administrative domain that is used to administer the managed objects that it contains.
Process A Process is a systematic sequence of actions used to achieve a goal.
Characteristic A Characteristic represents the essential attributes, methods, constraints, and/or relationships that typify the object that it applies to.
Capacity The Capacity of an object represents the total measured amount that the object can contain.
17
Use case for a Telco Company in Europe
Product Catalog
CRM
Custom Order Repository
Process Integration
Order Management WPS/WBSF/TOCP
Transformation Mediations
Service Provisioning
Resource Provisioning
Enterprise Service Bus
18
Order Management Performance Scenario
19
Police Services SOA Solution
20
Enterprise Service Bus Architecture Vision
Browsers
Pervasive
SAP
Oracle Apps
Business Processes Modeled
PDA
Mobile
ICDMS
New CompositeApplications
Portal Server
Process Server
Enterprise Service Bus
External Connections
Existing Applications Data
InformationAggregation
Other Transaction Mgmt
CICS/IMS
Document Mgmt
Security Agencies
Solaris / Sun
Windows / Intel
DBMS other information sources
Linux
Other Apps
Partners and Vendors
21
Service Oriented Interface - Pilot Solution
Information Services
J2EE App Server(WAS,SUN)
.Net App Server
CICS/IMS
Web Services
Web Services
Web Services
Web Services
Service Repository/Registry
Enterprise Service Bus
Common Data Model
Data Models (XML Schema)Service Contracts
(WSDL WS-Policy)
Code Tables
Auditing Logging
22
Large Bank in United States
23
Retail Banking - Account Open System Overview
24
Account Open Component Model
25
Insurance Company in United States
26
BPM Solution for Insurance Claims Payment
Insurance App1
Insurance App2
BPEL
Claims User Interface
Insurance App3
Claims Business Process Choreographer
Adapter
ACORD MSG
Insurance App4
OFAC Compliance
ACORD MSG
27
Energy Utilities in United States
28
SmartGrid - Meter Operations Integration
Smart Grid Meter Integration (Canonical CIM Based
Message Format )
Meter Data System
Metering Operations
Internet App
WS
JMS
WS
Adapters Layer
Integration Persistence Store
Adapters Layer
WS
JMS
WS
Meter System1
Meter System2
29
Meter Reading Request Business Object Model
30
Meter Reading Response Business Object Model
31
Meter Reading Request and Response Messages
Meter Reading Request
Meter Reading Response
32
Conclusion

• A flexible approach needs to look at information,
  processes and services with variability. A policy
  vocabulary derives from the business information
  model
• Variability and flexibility are not only
  technical but more important are business related
  and include semantic aspects
• Time to value comes from business and technical
  accelerators that we have constructed from
  standards and experience

33
Questions?
34
(No Transcript)