integration messaging patterns & best practices...• benefits of process integration within...

© Copyright 2015. Apps Associates LLC. 1

Integration Messaging Patterns & Best Practices Force.com

25 June 2015

Jon Collins Director, SaaS, Apps Associates LLC


Presenter – Jon Collins

Certifications • Salesforce

– Admin – Developer – Service Cloud Consultant

• Microsoft – MCP – MBSS

• MuleSoft – Developer

• Apttus – Quote to Cash

Experience • 65+ full lifecycle Salesforce

implementations, 50 of which required complex process integrations


Key Takeaways

• Benefits of Process Integration within Force.com (Salesforce1) Paradigm

– Optimize organizational processes

– Reduce the compound cost of manually addressing inconsistencies, lack of data or the impact to business as a result of bad data

– Front <--> back office 360° customer view can be very powerful, but also very dangerous if data isn’t consistent across the enterprise

• Define a System of Record (SOR)

• Process Integration demands an integration platform

• Salesforce can help to maintain data synchronization and integrity

• Real Life Example: Build a data-driven business case to justify investment


Integration Types

• Data Integration

– Synchronize data that resides in two or more systems so that both systems always contain timely and meaningful data

– Simple, but requires proper information management techniques to make the solution sustainable and cost-effective

– Aspects of Master Data Management (MDM), data governance, mastering, de-duplication, data flow design, etc.

• Process Integration

– Business process must leverage two or more applications to complete its task

– Triggering application has to call across process boundaries to other applications

– Complex design, testing, and exception handling requirements

– Includes • Orchestration – one application is the

central “controller” (System of Record)

• Choreography – applications are multi-participants and there is no central “controller” (System of Record)


Integration Methods

Batch Integration

• Integration of data is not real time • High volume data • Complex data manipulations • Data Extraction • Data Transformation • Data Loading • Change data capture • Audit trail • Web services/SOA • Cross Referencing • Reprocessing allowed • Point to Point • Scheduled • Automated tools vs. custom

development

Asynchronous Integration

• Integration of data close to real time • Medium volume data • Medium complex data manipulations • Data Extraction, Transform and Loading • Change data capture • Data pooling and DB streams • Web services / SOA • Audit trail • Cross references • Multiple sources and multiple target

systems • Reprocessing allowed • Automated tools vs. custom

development

Synchronous Integration

• Integration of data is real time • Source transaction is posted only if the

target system data is successfully posted

• Extract, Transform and Loading • Web services/SOA • Single transaction integrations • No reprocessing is allowed • One source and many source systems • Audit trail • Automated tools vs. custom

development


Key Concepts

Event Handling

• Identifying where an event should be forwarded

• Executing that forwarding action • Receiving a forwarded event • Taking some kind of appropriate

action in response • Error or recovery process, or sending

an additional message

Transformation

• Map one data format to another to ensure interoperability between the various systems being integrated

Choreography

• Behavior resulting from a group of interacting individual entities with no central authority

Service Orchestration

• Behavior resulting from a central conductor coordinating the behaviors of individual entities performing tasks independent of each other

Routing

• Specifying the complex flow of messages from component to component

• Message flows can be based in a number of criteria, including

• Header • Content type • Rule • Priority


Key Concepts

Reference Data

• Customer type • Item type

Transactional Data

• Sales orders • Purchase orders • Shipments/Deliveries • Invoices • Receivables • Returns

System of Record (SOR)

• The authoritative data source for a given data element or piece of information

Master Data

• Customers • Contacts • Employees • Vendors • Locations (Ship-To, Bill-To) • Organization • Products


System of Record

Why

• Multiple systems may disagree about the same piece of information

– Semantic differences

– Differences in opinion

– Different sources

– Differences in the timing of extracts that create the data they report against

– Simply be the result of bugs

• The integrity and validity of any data set is open to question when there is no traceable connection to a good source

Use Case: CRM vs. ERP – default to ERP


Quote to Cash: Sold

Lead Opportunity Quotation Sales Order

Delivery Invoicing


Discovered


Reality


You Need an Integration Platform

• Abstraction

• Event and Error Handling

• Transformation and Translation

• Protocol conversion

• Queuing and buffering

• Mediation routing

• “Transactionality” (encryption, signing, reliable delivery, transaction management)

• Routing


Best in Breed

• Only leader in BOTH Gartner iPaaS and on-premises markets, ideal hybrid solution

• Open Source

• 210k active developer community

• 10k+ published APIs

• 100’s of pre-built connectors to Salesforce, SAP, Oracle, NetSuite,

• 119 Salesforce connectors alone

• API-led connectivity

• Middleware Market Leader

• Mature and stable

• Very flexible

• Pre-built connectors to many legacy systems and ERP solutions

• Built for data integration

• Capable of large scale batch processes

• ETL roots allow for complex data transformations

• Pre-built connectors to many legacy systems and ERP solutions


Use Salesforce to Maintain Data Integrity

• Custom objects for message processing

– Inbound messages

– Outbound messages

– Routing, mapping, config

• Field-level validation

• Workflow

• Chatter trigger for error notification

• Outbound messages

– Beware Salesforce limits


Sell It

Qualify and Quantify Business Problems

• Focus on one area impacting business performance (Quote-to-Cash, for instance)

Process Analysis

• Current state (“as is”)

– Model current process with client specific or industry cost assumptions

– Build and run simulation to determine business cost

• Future state (“to be”)

– Model desired process with client specific or industry cost assumptions

– Build and run simulation to determine business cost

Findings and Recommendations Report

• Business case – is the problem worth solving?


Sell It

Free Innovation Workshop: Real Life Customer Example


Web: www.appsassociates.com

Email: [email protected]

YouTube: www.youtube.com/user/AppsAssociates

LinkedIn: www.us.linkedin.com/company/apps-associates

Twitter: @AppsAssociates

Facebook: www.facebook.com/AppsAssociatesGlobal

Google+: www.plus.google.com/+AppsAssociatesGlobal/

Connect With Us

http://www.appsassociates.com/

mailto:[email protected]

http://www.youtube.com/user/AppsAssociates

http://www.us.linkedin.com/company/apps-associates



http://www.twitter.com/appsassociates

http://www.facebook.com/AppsAssociatesGlobal

http://www.plus.google.com/+AppsAssociatesGlobal/

Thank You!


Agile, Value-Driven Cloud Services

integration messaging patterns & best practices...• benefits of process integration within...

Documents