Why should your enterprise be service-oriented? Service Oriented Architecture is not a buzzword or a nice to have. It has become a mandatory approach to support modern businesses and new organizational structures. Your architecture must be ready to provide real value to your business users, partners and customers by aligning with their processes and streamlining their activities. Especially in today’s digital world and this on an organizational, project and architectural level. This makes SOA the foundation for your API management and a controlled outside-in strategy. Still on a nightly batch update for just-in-time information? Or are people still copy & pasting information from one system to another? By 2017 65% of integration efforts will be delivered outside of central IT services. To keep your business competitive, to have a mobile strategy and to support innovation in your business; integration must be top of mind. Your API-management strategy allows you to open up new channels and have trusted partners provide new customers or services in a controlled and secure way. How do you decide where to start? What can be your SOA minimal viable product (MVP)? Join us at our next AE Foyer to get insight on how to implement a successful integration architecture and see inspiring examples in action! Target Audience CxO, Integration Architects, Business and Project Managers. This is a non-commercial seminar. Sales and software vendors cannot register for this event.

1. ae nv/sa
Interleuvenlaan 27b, B3001 - Heverlee
T +32 16 39 30 60 F +32 16 39 30 70
www.ae.be
SOA
INTEGRATION ARCHITECTURE
API MANAGEMENT
AE Foyer 30/09/2015

2. WHO ARE WE?
Roos Uwaerts Johan Luyts Wim Paredis
2

3. SETTING THE SCENE
We live in the age of the customer
3

4. SETTING THE SCENE
Building the digital enterprise for the age of the customer
4

5. Integration
Middleware
Transformation,
routing, validation,
mediation, enrichment,
…
OUR FUTURE DIGITAL ENTERPRISE
Client Tier
Interaction Tier
Systems of Record
Tier
Engagement Tier
Mobile Applications
Native iOS, Android, Windows
Web Site and Content
Management
Api Management
Gateway & portal, throttling, versioning,
discovery, billing, …
Security
Federated
authentication,
single sign-on,
adaptive access
control, digital
identity
Data Capture
Click-streaming,
sensor data, social
media
Customer-Oriented API
Innovative, faster pace, a/b testing, personalisation, agile
Enterprise Data Hub
Relational-, non-relational-, in-memory storage technologies
Big data
Streaming event processing
Search
Analytics
Embedded
Analytics, DWH-BI
integration
Enterprise Applications and Services – Systems of Record
Back-end systems like SAP, Peoplesoft, Oracle, custom-built Java or .NET applications, and Saas solutions like SalesForce.com
Channels & Media
External
Developers
Partners
Security and
Integration Layers
5

6. OUR FUTURE DIGITAL ENTERPRISE
StabilityFlexibility
Core Enterprise
Digital
Ecosystem
BimodalIT
Designed
for
Designed
for
6

7. StabilityFlexibility
OUR FUTURE DIGITAL ENTERPRISE
Internal or to
partners
Reduce IT
Costs
Project Driver
Integration
Goal
External, often
to customers
Generate
Business
Revenues
Reliability
Enterprise
Long-Term
SupportingGoal
Agility
Small and New
Short-Term
BimodalIT
Designed
for
Designed
for
7

8. GROWING
PRESSURE
Company
boundaries
Internal
External
8

9. GROWING INTERNAL
PRESSURE
Company
boundaries
Internal
External
Package Implementation
Core Enterprise
MDM (360° view)
Cloud or on-premise
Efficieny and
standardisation
9

10. GROWING INTERNAL AND EXTERNAL
PRESSURE
Internal
External
Package Implementation
Core Enterprise
MDM (360° view)
Cloud or on-premise
Efficieny and
standardisation
Omni-channel
Services Offerings
Suppliers and
Partners
FEE Architecture
requiring API’s
Company
boundaries
10

11. API management is
no alternative for SOA
SOA, INTEGRATION ARCHITECTURE
AND API MANAGEMENT
11
API
Management

12. TACKLING YOUR CHALLENGES
External services
Internal services
New
application
Legacy
application
Legacy
application
12
API
Management

13. DIGITAL TRANSFORMATION
13
Core Enterprise
Digital
Ecosystem
API
Management
Reference Architecture Get Control
Service Categories
Canonical data and
behaviour model
Governance
Organization

14. REFERENCE ARCHITECTURE
class MedicalDecisionActivityService - Specification Information Model
Object
Information Model::Policy
::Object
- objectId: identifier
- objectIdExtension: Extension
- objectType: Set(Object)
«Release B»
- versionID: NonNegativeInteger
Information Model::PolicyCoverage
- coverId: NonNegativeInteger
CoverAcceptanceDecision
- additionalInfo: String
- coverAccDecision: coverDecision
- declineReason: DeclineReason
- isAutomatic: Boolean
- postponedUntil: date
- postponeReason: PostponeReason
- sumAssured: Money
Decision
- decision: Decision
- decisionDate: Date
- postponedUntil: Date
- Reason: DecisionReason
«nc»
- notificationId: NonNegativeInteger
Surloading
- additionalInfo: String
- amount: Money
- duration: Duration
- isAutomatic: Boolean
- isTemporary: boolean
- surloading: Decimal
- surloadingBase: SurloadingBase
- surloadingID: NonNegativeInteger
- surloadingReason: SurloadingReason
- surloadingSubType: SurloadingSubType
- surloadingUnit: SurloadingUnit
CoverAcceptanceClause
- additionalInfo: String
- coverAccClauseID: NonNegativeInteger
- coverAccClauseReason: CoverAccClauseReason
- coverAccClauseText: MultilanguageString
- isAutomatic: Boolean
- scopeOfCoverage: ScopeOfCoverage
MedicalDecisionRegisterActivityService
PolicyDataService
PartyDataService
Legend
PaymentObject
MedicalFolder
- medicalFolderId: Identifier
Information Model::Insured Person
- dateLastRejected: Date
- dateLastUpdated: Date
- disabilityEffStartDate: Date
- disabilityEffStopDate: Date
- existingInsuranceIndicator: boolean
- heightInCentimeter: Integer
- IsActiveAtWork: boolean
- replacementIndicator: boolean
- smokerState: SmokerState
- weight: Integer
+ smoker(Date): SmokerState
Master Data::Party
- partyId: Identifier
Master Data::Party Role
- beginDate: Date
- endDate: Date
- partyRole: PartyRole
Master Data::Person
1
1..*
+party
1
+party roles
0..*
1
0..1
0..*
1
+person
1
{subsets party}
0..*1
1
1
0..1
1
0..*
1
14

15. LAYERED MODEL
External services
Internal services
New
application
Legacy
application
Legacy
application
15

16. LAYERED MODEL
Internal services
New
application
Legacy
application
Legacy
application
16

17. SEVERAL KINDS OF INTERNAL
17
Internal services
New
application
Legacy
application
Legacy
application
Private API
Inner
Services
Cloud
Services

18. SEVERAL KINDS OF INTERNAL
Private API’s Inner services Cloud services
Who Employees of the
organization
Applications
Why Internal innovation,
channel consistency,
short term agility
Stability, Robustness, Standardization, long term strategic
solutions
Control
18

19. LAYERED MODEL
External services
Internal services
New
application
Legacy
application
Legacy
application
19

20. SEVERAL KINDS OF EXTERNAL
External services
Public API Partner API B2B services
Internal services
20

21. SEVERAL KINDS OF EXTERNAL
Public API Partner API B2B services
Who App developers,
Customers
Business Partners Tailored for specific
Business Partner
Why External innovation
Quickly enter new
customer facing eco
systems
Automate processes
Exchange data
Accelerate partner
onboarding
Build long standing
partnership
Control
21

22. API MANAGEMENT
External Internal
Public API Partner API Private API’s
Who App developers,
Customers
Business Partners Employees of the
organization
Why External innovation
Quickly enter new
customer facing eco
systems
Automate processes
Exchange data
Accelerate partner
onboarding
Internal innovation,
channel consistency,
short term agility
Control
22

23. A DIFFERENT VIEW
External services
Internal services
New
application
Legacy
application
Legacy
application
API management
Service landscape
23
API MANAGEMENT

24. Developer Management
Health Tracking
Workflow
Performance Global Staging Developer
Enrollment
API Docs
Forums
API Explorer
RankingsQuotas
Plans
AnalyticsReporting
Config Migration
Patch Management Policy Migration
Operations Management
Throttling Prioritization Caching
Routing Traffic ControlTransformation
Security
Interface Management
Composition
Authentication Single Sign OnAPI KeysEntitlements
OAuth 1.x OAuth 2.0 OpenIDConnect
Identity Management
TYPICAL FEATURES OF API MANAGEMENT
Token Service
Source : CA Technologies
24

25. External services
Internal services
New
application
Legacy
application
Legacy
application
SERVICE CATEGORIES
25
Internal
services
External
services
Interaction services
Business services
Supporting services
Service Consumers
Providing applications

26. SOA TARGET MODEL – EXAMPLE
26
Internal
Services
External
Services
Technical
Adapters
Technical
Adapters
Business
services
Supporting
services
Interaction
services
Service
Consumers
Providing
applications
Confidential

27. SERVICE CATEGORIES - EXAMPLE
27

28. SERVICE
28
Service
Service
Information Functionality
Providing application 1
Providing application 2
Providing Data store

29. CANONICAL DATA MODEL
29
Service
Information Functionality

30. CANONICAL DATA MODEL
30
Example class PolicyDataService - Specification Information Model
Master Data::Party Role
- beginDate: Date
- endDate: Date
- partyRole: PartyRole
Information Model::Intermediary
- intermediaryId: Identifier
«nc»
- isPrivileged: boolean
Information Model::
InsuranceTaker
Information Model::Insured Person
- dateLastRejected: Date
- dateLastUpdated: Date
- disabilityEffStartDate: Date
- disabilityEffStopDate: Date
- existingInsuranceIndicator: boolean
- heightInCentimeter: Integer
- IsActiveAtWork: boolean
- replacementIndicator: boolean
- smokerState: SmokerState
- weight: Integer
+ smoker(Date): SmokerState
PolicyDataService
ContractDataService
IntermediaryDataService
PartyDataService
Legend
General Contract
Object
Contract
- adminSystem: TechnicalSystem
- adminType: Admin
- beginDate: Date
- collectionType: Collection
- commercialProduct: CommercialProduct
- contractState: ContractState
- contractStateDate: Date
- contractType: Insurance
- currency: CurrencyCode
- effectiveDate: Date
- endDate: Date
- fiscalSystem: FiscalSystem
- investType: Invest
- isReIns: boolean
::Object
- objectId: identifier
- objectIdExtension: Extension
- objectType: Set(Object)
Information Model::IndividualContract
- technicalProduct: TechnicalProduct
Information Model::IndividualPolicy
Object
Policy
- amendmentId: NonNegativeInteger
- annualNetPremium: Money
- annualPremium: Money
- bankingLoanType: BankingLoan
- beginDate: Date
- countryLaw: Country
- effectiveDate: Date
- endDate: Date
- isBankingLoan: boolean
- isPackageProposal: boolean
- isPawn: boolean
- isTransferExt: boolean
- isTransferInt: boolean
- language: LanguageType
- lastConvContractId: Identifier
- lastConvPolId: Identifier
- policyQualification: PolicyQualification
- policyState: PolicyState
- policyStateDate: Date
- policyType: Insurance
- proposalId: Identifier
- proposalIdExtension: Extension
- proposalQualification: ProposalQualification
- recievedDate: Date
- renewalDate: Date
- reserve: Money
- surrenderNetValue: Money
- surrenderValue: Money
- term: Term
- totalAdditionalPremium: Money
- totalInitialPremium: Money
- totalNetPartialSurrender: Money
- totalNetPremium: Money
- totalPartialSurrender: Money
- totalPendingAllocation: Money
- totalPremium: Money
- totalPremiumByDeduction: Money
- valuationDate: Date
- yNetPremium: Money
- yTotPremium: Money
::Object
- objectId: identifier
- objectIdExtension: Extension
- objectType: Set(Object)
«Release B»
- lastConvPolIdExtension: Extension
- lastConvPolReason: ConvPolicyReason
- versionID: NonNegativeInteger
«nc»
- motiveState: MotiveState
- notificationId: Identifier
- proposalState: ProposalState
Contract::GroupContract
- beginDateJuridical: Date
- countryLaw: Country
- dscACntr: MultilanguageString
- numberAffCovered: int
«Release B»
- numberParticipantCoveredByClient: int
Contract::GroupPlan
- beginDate: Date
- choicePlan: ChoicePlan
- comPlan: String
- dscPlan: MultilanguageString
- dscReference: String
- endDate: Date
- fiscalState: FiscalState
- groupPlanId: NonNegativeInteger
- isCoIns: boolean
- numberAffCovered: int
- planType: Plan
- renewalMonth: Month
PolicyCoverage
Information Model::
IndividualPolicyPromise
Master Data::Party
- partyId: Identifier
ContractPartyRole
ObjectInsuranceTaker
ContractInsuranceTaker
::ObjectPartyRole
- beginDate: Date
- endDate: Date
ContractPartyRole
ObjectIntermediary
ContractIntermediary
::ObjectPartyRole
- beginDate: Date
- endDate: Date
ObjectInsuredPerson
PolicyPartyRole
PolicyInsuredPerson
::ObjectInsuredPerson
- birthDate: Date
- IsAbleFulltimeWork: boolean
- occRiskClass: OccRiskClass
- smokerState: SmokerState
::ObjectPartyRole
- beginDate: Date
- endDate: Date
«Release B»
::ObjectInsuredPerson
- socialState: SocialState
Master Data::Person
1
1..*
+party
1
+party roles
0..*
1..*
1
1
1..*
1
1
1
1..*
0..*
1
+person 1
{subsets party}
1..*
1
1..*
1
1
Information Functionality
Service
Confidential

31. Service
Service
Consumers
Business
Services
Providing
Applications
CANONICAL BEHAVIOUR MODEL
31
Application 2
Consumer A Consumer B Consumer C
Service
Application 1
Information Functionality

32. TACKLING YOUR CHALLENGES
32
Key success factors for reference
architecture:
- Layered architecture
- Service categories
- Canonical model
SOA is mandatory, it’s no longer an
option!
SOA is the foundation for API
management.
External services
Internal services
New
application
Legacy
application
Legacy
application

33. TACKLING YOUR CHALLENGES
33
External services
Internal services
New
application
Legacy
application
Legacy
application
Time
SOA Governance

34. “Ensuring and validating that assets and
artifacts within the architecture are
acting as expected and maintaining a
certain level of quality
Gartner, Magic Quadrantfor SOA Governance,2007
34

35. SERVICE LIFECYCLE
35
Deprecated
Analysis
Design
Implementation
Testing
Ready for production
Planning
Operational
Retired

36. SERVICE PORTFOLIO
36
Service Portfolio
Service Catalog
API CatalogService
Candidates

37. TACKLING YOUR CHALLENGES
37
Time
External services
Internal services
New
application
Legacy
application
Legacy
application
Key success factors for SOA
governance:
- Service lifecycle management
- Service catalog
Start small, think big
Align your governance processes with
your way of working

38. TACKLING YOUR CHALLENGES
38
External services
Internal services
New
application
Legacy
application
Legacy
application
Organization

39. Project
Management
Key
Responsibilities
of Integration
Communication
ORGANIZATION
39

40. PROJECT MANAGEMENT
Integration is part of every project charter !
• Planning
• Creation of new services
• Changes to existing services
• Retiring “old” services
• Reuse of existing services
• Budget
• Project team
• Middleware team
• Application teams
40
Operational
Budget !

41. KEY RESPONSIBILITIES OF INTEGRATION
Support &
Advise
Projects
Introduce
Guidelines &
Best Practices
Technology
recommendati
ons
Maintain the
Canonical
Model
Review
Integration
Deliverables
Align Project
& Middleware
team
Maintain the
SOA target
Model
41

42. KEY RESPONSIBILITIES OF INTEGRATION
42
Support &
Advise
Projects
Introduce
Guidelines &
Best Practices
Technology
recommendati
ons
Maintain the
Canonical
Model
Review
Integration
Deliverables
Align Project
& Middleware
team
Maintain the
SOA target
Model

43. KEY RESPONSIBILITIES OF INTEGRATION
43
Support &
Advise
Projects
Introduce
Guidelines &
Best Practices
Technology
recommendati
ons
Maintain the
Canonical
Model
Review
Integration
Deliverables
Align Project
& Middleware
team
Maintain the
SOA target
Model

44. KEY RESPONSIBILITIES OF INTEGRATION
44
Support &
Advise
Projects
Introduce
Guidelines &
Best Practices
Technology
recommendati
ons
Maintain the
Canonical
Model
Review
Integration
Deliverables
Align Project
& Middleware
team
Maintain the
SOA target
Model

45. KEY RESPONSIBILITIES OF INTEGRATION
45
Support &
Advise
Projects
Introduce
Guidelines &
Best Practices
Technology
recommendati
ons
Maintain the
Canonical
Model
Review
Integration
Deliverables
Align Project
& Middleware
team
Maintain the
SOA target
Model

46. COMMUNICATION
46
Communication Plan
Basic
Information
Awareness
Value Related
Information
Comprehension
Reinforcement
and Validation
Conviction

47. TACKLING YOUR CHALLENGES
External services
Internal services
New
application
Legacy
application
Legacy
application
Integration is part of every project
Clearly define the integration responsibilities
and their owners
Adoption won’t work without a good
communication strategy
47

48. TAKE AWAYS
API management is no alternative for SOA
SOA is no longer a nice to have, it is a mandatory architectural approach
Don’t forget your service catalog, everybody is your stakeholder
Integration is part of every project charter
API
SOA Int
Arch
48

49. ae.be