MuleSoft Manchester Meetup slides 4th July 2019

Manchester, UK | 4th July, 2019
API foundation development with the
Anypoint Platform
Kevin Jervis
Ricston
CTO
Ryan Young
Open Answers
Integration Architect
Dave Felcey
MuleSoft
Lead Solution
Engineer
David Morris
MuleSoft
Customer Success
Architect

© Ricston Ltd. 2019
Kevin Jervis, CTO Ricston Ltd

“Together, Salesforce and MuleSoft will enable customers to connect
all of the information throughout their enterprise across all public
and private clouds and data sources — radically enhancing innovation”
~ Marc Benioff, Chairman & CEO Salesforce
“Together, Salesforce and MuleSoft will accelerate our customers' digital transformations
enabling them to unlock their data across any application or endpoint.
~ Greg Schott, CEO MuleSoft
What’s missing? If the data maintained in your systems really is the crown jewel, then APIs are the gateways to your crown
jewels and ultimately how would you expose your APIs securely becomes a fundamental question!
Source: https://www.cbronline.com/qa/mulesoft-founder-interview
https://www.salesforce.com/company/news-press/press-releases/2018/03/180320/

● HTTPS
○ Secure channel over an insecure network to ensure conﬁdential transfer of information
● HTTP Basic Authentication
○ Rudimentary scheme that requires authentication credentials transmitted on every request
● 2-Way TLS (Mutual Authentication)
○ Public Key Infrastructure; scaling certiﬁcate management across 100s or 1000s of endpoints
not viable
● SAML
○ Enterprise scale; many IT systems and services use SAML today to provide single sign-on
● OAuth 2.0
○ Web scale: delegated authorisation framework
○ Open-ID connect (an authentication layer on top of OAuth 2.0)
○ JSON Web Token (JWT) - JSON Web Signature (JWS)
● WS-Security/WSSE

● Convenient and concise way of representing
authentication and authorization claims for an
application
○ Essentially a series of claims encoded within a
compact JSON object
○ Applications don’t have to understand access token
schema
● Token Veriﬁcation
○ Self-encoded access token
○ Token introspect
● JSON Web Signature (JWS)
○ Header known as the JOSE header (JSON Object
Signing and Encryption)
○ Payload
○ Signature
Header
Algorithm + Token Type
Signature Verification
{
"alg": "RS256",
"typ": "JWT",
"kid": "QgwSWOFEgNNpgv_JdFmfMokgEsfewt"
}
RSASHA256(
base64UrlEncode(header) + "." +
base64UrlEncode(payload), <Private Key>
)
Payload
{
"jti": "e72b4009-823b-40ac-...",
"exp": 1562235644,
"iat": 1562235344,
"iss":
"https://keycloak.ricston.com/auth/realms/me
etup-realm",
… ,
"typ": "Bearer",
"azp": "meetup-client",
"scope": "profile email",
"clientId": "meetup-client"
}

Policy driven API management enables a single point
of:
● Enforcement
● Control
● Visibility
Anypoint Platform
Great … in principle!
For Mule 3.x there was no JWT policy ...
However we can leverage a custom policy!

OAuth Client
Authorization Server
Keycloak
Client
App
Resource Server
API
Access Service
with Token
Authenticate,
Grant Access
Policy enforces Authorization
Issue Identity &
Access Token
Access
Data
Clients Scopes
Keys Tokens
Policy
Realm

Platform provided policies now include:
● Tokenization
● De-Tokenization
● Spike Control
● Header Injection/Removal
● Caching
● JWT Validation

Security is never absolute; there are always trade-offs to be made Top tips
● Use HTTPS by default
● JWT is an internet-scale
approach for both identity tokens
(i.e. authentication via Open-ID
connect) and access tokens
(authorisation)
● Use digital signatures to provide
non-repudiation
● Encryption is required for
conﬁdentiality
Layers
of Security
Performance
& Scalability
Avoid reinventing
the wheel

Commercial in Confidence - not for distributionopenanswers.co.uk
NHS App - Organ Donor Register
integration using the HL7 FHIR standard
July 2019
Ryan Young

Open Answers
What we do
• Integration
• Support
• Professional Services
• Software Development
• Managed Services
• Education
For customers including
Anthony Nolan
ASOS.com
BDB Law
Bloomberg NEF
British Airways
Buckingham Palace
Camelot Group
Care Quality Commission
Cambridge Satchel Company
Channel 4 Television
Dixons Stores Group
Drum Cussac Group
GoldMoney.com
London Borough of Ealing
London Borough of Hounslow
London Borough of Redbridge
MuleSoft
NCR
NHS Blood & Transplant
NHS SBS (Sopra Steria)
Ofsted
Picsolve
Red Hat
Shared Services Connected Ltd
SSP
Sun Microsystems (now Oracle)
Thomson Reuters
Xerox Europe
Open Answers (founded in 1988) is a provider of premium quality digital technology services to blue chip customers and the
public sector, specialising in cloud systems integration.
Public sector frameworks
GCloud
Digital Outcomes and Specialists

Project Intro - The NHS App
• In September 2017 the Health Secretary announced
that a new ‘NHS App’ will be built offering 7 key
functions such as making GP appointments and
ordering repeat prescriptions
• One of these core functions will allow App users to
register their organ donation decision on the
NHS Organ Donor Register

The NHS
App

NHS App - Organ Donor Register Integration
• Phase 1: MVP to reuse existing fire-and-forget
webform and flat-file interface....
• https://www.organdonation.nhs.uk/
• Provided create and update but no retrieve
• Functional but user experience not great
• Phase 2: Real-time integration using FHIR based
REST APIs....
• Full CRUD capability supported including retrieve
• Industry standard based interface specification
• Pre-populated forms provide a better user experience
• Ability to recall and amend requested by No.10 and
DHSC to support a legislative change

NHS Organ Donor Register - Before

NHS Organ Donor Register - MVP

NHS Organ Donor Register - After

HL7 FHIR Standard
Fast
Healthcare
Interoperability
Resources
Resource
Based Content
Model
Real-time
RESTful
Interface Spec

FHIR
Resource
Content
Model

NHS and FHIR
NHS Digital, Data and Technology Standards Framework

Want to know more?
• Visit http://build.fhir.org/
• Search “fhir intro” on YouTube
• NHS FHIR implementations....
• NHS Care Connect API....
https://nhsconnect.github.io/CareConnectAPI/
• NHS GP Connect API....
https://nhsconnect.github.io/gpconnect/index.html
• Search “FHIR accelerator” on Anypoint Exchange....

Anypoint Exchange FHIR Assets
MuleSoft provided example RAML Specifications,
Implementation Templates and API Spec Fragments

Anypoint Exchange Healthcare Accelerator
MuleSoft provided example FHIR based RAML Specification

Organ Donor Register FHIR API
Organ Donor Register FHIR API RAML Specification (within private Anypoint Exchange)

RAML Data Type Reuse Stats

RAML Reuse Caution
• Make sure RAML fragments are fit for purpose
• Ensure RAML data types are well documented
• Ensure RAML data type patterns are secure
• Don’t be afraid to extend/enhance RAML fragments
as required

Address Data Type Deep Dive
HL7 Standard FHIR Spec MuleSoft provided RAML Data Type
Spot the difference!

Address Data Type Deep Dive
Extended RAML Data Type…
...with additional validation

Key Takeaways
• The HL7 FHIR standard is complex but
comprehensive
• There is a learning curve but the MuleSoft provided
Anypoint Exchange Accelerators help reduce some of the
up-front effort
• The FHIR standard provided a large number of reusable
Data Types straight out-of-the-box
• The NHS have put their weight behind it (so, if you work
in the healthcare industry, ignore it at your peril!)

Key Takeaways
• Use Anypoint Exchange API Spec examples and
RAML API fragments to accelerate API design
• However, make sure RAML examples are fit for purpose,
e.g. secure and well documented
• RAML supports inheritance so don’t be afraid to extend
RAML fragments
• Productionised RAML fragments can be re-published in
Exchange and reused on future projects

Download it now!
• The NHS App is available on iOS and Android via the
App Store and Google Play…

Thank you!
Q&A
ryan@openanswers.co.uk

Dave Felcey - Solution Engineer
David Morris - Customer Success Architect
Salesforce Integration
Using MuleSoft

All contents © MuleSoft Inc.
Agenda
35
● Introduction and Context
● Why use MuleSoft to integrate Salesforce with other applications?
● Common Salesforce Integration Scenarios using MuleSoft
● Q & A

All contents © MuleSoft Inc. 37
Since inception, Salesforce has evolved… significantly!
Sales
Cloud
Salesforce Platform
& AppExchange
Service Cloud
Heroku
Salesforce
Mobile
Lightning
Platform
Analytics Salesforce
IoT
Trailhead
Einstein
Commerce
Cloud
Quip
Chatter
Marketing
Cloud
1999 2006 2011 2012 2014 2015 20162009 2013
AI for
Everyon
e
2018 2019
MuleSoft
Tableau
Salesforce has a number of products, developed from a combination of our R&D
team and 59 acquisition in the last 20 years.

HOSTED ON OTHER PLATFORMS
HOSTED ON CORE PLATFORM
These products have many Integration options, BUT...
SALES SERVICE
MARKETING COMMERCE
COMMUNITYPLATFORM
ANALYTICS
INDUSTRIES APP EXCHANGE
COLLABORATIO
N
HEROKU
Native Connectors
Core Platform Integration Options
● REST API - fast, lightweight and most commonly used integration method.
● SOAP API - larger, legacy method of integration to Salesforce.
● Bulk API (REST) - Load or delete large numbers of records.
● Salesforce Connect - displays external data without storing on platform, using ODATA.
● Platform Events - on-platform event bus that enables for pub/sub behaviour.
● SOAP Outbound Messages - configurable XML messages to SOAP endpoints.
● Apex REST/SOAP API - Create custom Web Services in Apex and expose via API.
● API Callouts (SOAP/REST) - custom code to make a callouts when triggered
Native Connectors
● Marketing Cloud Connect (to Core - in-built)
● Commerce Cloud
○ .. to Service Cloud Connector
○ .. to Marketing Cloud Connector
● Analytics Connect (to Core - in-built)
● Quip Connect (to Core - AppExchange)
● Heroku Connect (to Core)
● Salesforce-to-Salesforce
*Configuration, not code.
*Code - beware of complexity and assess long-term suitability

Why use MuleSoft to integrate Salesforce
with other applications?

Why use MuleSoft for Salesforce integration?
40
• Speed and ease of use
– Pre-built connectors, examples and templates.
– Reusable integration components.
– Create integrations from ‘graphical flow diagrams’.
– Implement once, deploy anywhere.
• Non-functional benefits, like
– Management, monitoring and alerting.
– Apply dynamic security policies.
– Multiple Processing Options (real-time, batch, schedule, multi-threading).
– Supports various integration patterns.
– Cloud, on-premise and hybrid deployment strategies.

Salesforce Integration with MuleSoft
41
Benefits
• Many years of investment in
Salesforce integration with 100+
blueprints, connectors,
examples to accelerate your
connectivity.
• First to market connectivity to
new Salesforce products and
API revisions as part of a unified
product experience.
• Clear product vision between
MuleSoft and Salesforce to
increase developer productivity
and choice, to build connected
experiences faster.

Common Salesforce Integration Scenarios
using MuleSoft

Common Integration Scenarios
43
1. Share and Synchronize data and entities - e.g. Accounts etc
– Master and sync business entities in different applications
– Provide a “single customer view” from across systems
– Scheduled bulk or ETL operations / Real-time and event driven
2. Augment processes across applications - e.g. “Order to Cash”
– Automation to eliminate manual processing and improve data quality
– Harness “best of breed” applications for different business areas
3. Extend and develop new services - e.g. Mobile apps
– Omni Channel services that extend application functionality
– Enables new, innovative apps / solutions

Synchronise and Share - RT customer experience
45

Salesforce synchronization templates
46

Share data with/in Salesforce using OData
47
Problem
• A Service Agent needs to a complete view of a
customer to provide the best experience
• But core business data is mastered in multiple
other applications
Solution
• Capture keys/Ids for related entities in
Salesforce.
• Use these to query/update external data in
other systems using Salesforce Connect and
MuleSoft’s Data Gateway or OData Extension
MuleSoft Data Gateway
MuleSoft OData Extension

In response to increasing competitive pressure, Hologic implemented Salesforce’s
Sales, Services and Marketing clouds to deliver best in class customer sales and
service. The existing integration toolset was complicated to use and did not allow for
asset reuse, jeopardizing the go-live deadline set by the exec team.
With MuleSoft, Hologic was able to easily build, edit and document integrations that
could be reused across projects, tripling their project delivery speed. By building
reusable APIs that can then be leveraged across multiple business processes, Hologic
was able to deliver their Salesforce integration projects on-time and within budget.
“With MuleSoft, I can code simple
integrations end-to-end in a week. With
our previous SOA suite, it would take 3
weeks.”
- Vasil Valkov, Systems Integration and Software
Development Manager
MuleSoft accelerated project delivery speed from 3 weeks to one week by
enabling the creation of reusable, self-service APIs for Salesforce integration.
Accelerating Salesforce integration to
improve customer retention
Leading developer, manufacturer and supplier
of diagnostic and medical imaging systems
3x faster

Augment - To provide “straight through processing”
SAP
Connector
EBS
Connector
Amazon
SQS
Workday
Connector
CORE PLATFORM
SALES SERVICE
Platform Events
Sales Team
Process
3. Platform Event is published
to the Salesforce Event Bus
4. MuleSoft subscribes to Event
(it can also publish events).
1. Sales Team update an
Opportunity in Salesforce
2. Sales Cloud workflow fires,
generates Platform Event.
5. Action taken
in other system.
Problem
Salesforce process needs to trigger an
update in a back-end system.
Solution
Salesforce publishes Event, and
MuleSoft subscribes, picks it up and
takes action downstream.
Find out more...
For more information, and a guided
tutorial, search for How to Use
Platform Events with MuleSoft’s
Salesforce Connector on
blogs.mulesoft.com.
Note: you could use APEX to code a callout from
Salesforce, but you should consider the impact of
custom development before doing this!

Salesforce Event Driven Orchestration
51

Salesforce Process Automation Templates
52

4x faster
Manual operational processes and batch integration from their current ETL tool were
hindering Splunk from providing employees and customers with real-time access to
necessary services.
Prioritizing a 100% cloud infrastructure to give them speed and scalability, Splunk
chose MuleSoft’s Anypoint Platform to streamline processes such as quote-to-cash,
employee lifecycle management and user provisioning.
“MuleSoft enables Splunk to orchestrate across
multiple cloud services in a matter of weeks
versus months. We are accelerating our
business by leveraging their continuous
innovation.”
- Declan Morris, CIO
MuleSoft enabled Splunk to deploy the integration of its quote-to-cash process in
four weeks instead of the four months it would have taken with their ETL solution.
Building a cloud infrastructure for continued growth
Market-leading platform that powers Operational Intelligence
to make organizations more efficient, secure and profitable

3. Extend and develop new services

Extend - Create new services and products
SAP Connector
Salesforce
Connector
Customer
Mktg. Cloud
Connector
System
APIs
Process
APIs
Experience
APIs
Mobile API Web API Partner API
Customer Product Orders
Partners
Problem
How to gather and expose Salesforce
(and other data) to other, external
facing channels.
Solution
Using an API-led approach, build an
Application Network of Experience,
Process and System APIs.
Find out more...
For more information, search for API
templates with reusable System
and Process APIs on
blogs.mulesoft.com.

Extending Salesforce templates
56

DRIVING A SEAMLESS CUSTOMER JOURNEY WITH
OMNICHANNEL
“MuleSoft and Salesforce are at the core of our strategy to
deliver great capabilities to our customers, to our guests,
and to our team members.”
- Michael Rodgers, Chief Strategy and Information Officer
for Pilot Flying J
58
Transforming the experience of
1.6 million customers daily
• In order to create a fully personalized
experience for their guests, Pilot Flying J needed
to abandon its siloed approach to customer
service, and replace it with a user-friendly
omnichannel strategy.
Launched feature-rich mobile app
• By connecting 5+ systems with MuleSoft’s
Anypoint Platform, Pilot Flying J launched
myPilot, an integrated mobile app saving drivers
time and improving quality of life on the road. In
the myPilot app, guests can find nearby fueling
station, plan overnight parking and book shower
reservations.
2X YOY growth in active app users
• Active users on the myPilot app have doubled
year-over-year, resulting in millions of new
in-app loyalty offers, 80% increase in showers
booked in-app and a 90% reduction in the steps
required for professional drivers to complete
fueling.

Further Links
59
● How to Use Platform Events with MuleSoft’s Salesforce Connector (Tutorial)
https://blogs.mulesoft.com/dev/connectivity-dev/how-to-use-platform-events-mulesoft-salesforc
e-connector/
● Introducing Bulk API v2 support with the Salesforce Connector (Tutorial)
https://blogs.mulesoft.com/dev/connectivity-dev/bulk-api-v2-support-salesforce-connector/
● Introducing New Triggers with the Salesforce Connector (Tutorial)
https://blogs.mulesoft.com/dev/connectivity-dev/introducing-new-triggers-with-the-salesforce-co
nnector/
● Top 5 Salesforce integration patterns (Whitepaper)
https://www.mulesoft.com/ty/wp/salesforce-integration-patterns
● Deliver a connected service experience with MuleSoft and Salesforce (Article)
https://blogs.mulesoft.com/biz/connectivity/connected-service-experience-mulesoft-salesforce/
● Learn more about how MuleSoft can help connect Salesforce (Trailhead)
https://trailhead.salesforce.com/en/search?keywords=mulesoft

MuleSoft Manchester Meetup slides 4th July 2019

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to MuleSoft Manchester Meetup slides 4th July 2019

Similar to MuleSoft Manchester Meetup slides 4th July 2019 (20)

Recently uploaded

Recently uploaded (20)

MuleSoft Manchester Meetup slides 4th July 2019