1. Backend Integration for Mobile Enterprise Apps
Mobile Integration
Matthias Biehl, Senior Consultant
2014-02-28

2. Signing an Insurance Contract –
Situation Today
24.06.2014 © 2013 [ipt] Switzerland Seite 2

3. Signing an Insurance Contract–
Situation with Mobile Enterprise Apps
24.06.2014 © 2013 [ipt] Switzerland Seite 3
Internet

4. Backend
Frontend
Mobile Apps
Mobile Apps
Mobile Apps
Enterprise Backend
Systeme
Challenge
Currently, the biggest challenge for
enterprise mobile applications is
backend integration.
Enterprise Mobility Report, VDC Research, 09-2013

5. Backend
Frontend
Mobile Apps
Mobile Apps
Mobile Apps
Enterprise Backend
Systeme
Challenge
Currently, the biggest challenge for
enterprise mobile applications is
backend integration.
Enterprise Mobility Report, VDC Research, 09-2013
“Currently, backend integration
accounts for approximately 30%
[cost, effort] of a typical mobile
initiative”
Enterprise Mobility Report, VDC Research, 09-2013

6. Why is this so difficult?

7. 24.06.2014 Seite 7© 2013 [ipt] Switzerland
Mobile vs Backend: Different Technologies
WebSocket
SOAPXML
REST
JSON

8. 24.06.2014 Seite 8© 2013 [ipt] Switzerland
Mobile vs Backend: Different Devices

9. 24.06.2014 Seite 9© 2013 [ipt] Switzerland
Mobile vs Backend: Different Technology Cycles

10. 24.06.2014 Seite 10© 2013 [ipt] Switzerland
Mobile vs Backend: Development Cultures

11. 24.06.2014 Seite 11© 2013 [ipt] Switzerland
Mobile vs Backend: New Security Exploits

12. Backend
Frontend
Mobile Apps
Mobile Apps
Mobile Apps
Enterprise Backend
Systeme
WebSocket
SOAPXML
REST
Mobile vs Backend: Summary
JSON
24.06.2014 Seite 12© 2014 [ipt] Switzerland

13. Reference Architecture

14. API Gateway
Backend
Frontend
AuthN
AuthZ
IAM
Mobile Apps
Mobile Apps
Mobile Apps
Enterprise Backend
Systeme
Internet
Mobile Integration Reference Architecture
24.06.2014 Seite 14© 2014 [ipt] Switzerland

15. Runtime Sequence

16. 6/24/2014 16
{"jsonrpc": "2.0", "method":
"GetGeoIP", "params": {"IPAddress":
"1.1.1.1"}, "id": 3}
<soapenv:Envelope xmlns:soapenv=“.."
xmlns:web=“..">
<soapenv:Header/>
<soapenv:Body>
<web:GetGeoIP>
<web:IPAddress>1.1.1.1</web:IPAddress>
</web:GetGeoIP>
</soapenv:Body>
</soapenv:Envelope>
<soapenv:Envelope xmlns:soapenv=„.." xm
<soapenv:Header/>
<soapenv:Body>
<web:GetGeoIPResponse>
<web:GetGeoIPResult>
<web:ReturnCodeDetails>Success
<web:CountryName>Switzerland</
</web:GetGeoIPResult>
</web:GetGeoIPResponse>
</soapenv:Body>
</soapenv:Envelope>
{"jsonrpc": "2.0”, "id": "3“, "result": {
"CountryName": "Switzerland",
"ReturnCodeDetails": "Success",
"ReturnCode": "1",
"IP": "1.1.1.1",
"CountryCode": "CH”},
}

17. Policy

19. Technical Benefits

20. 24.06.2014 Seite 20© 2014 [ipt] Switzerland
 Mediation Layer: Separate
Concerns of Business Logic &
Technology
 Security: Protect Client Data
and Business Services
 Efficient Support for
Development and Maintenance
 Protect Investment in Backend
 Support new Mobile Standards
 Clustering - Scalability and
Performance
Benefits od the Mobile Reference Architecture
API Gateway
Backend
Frontend
AuthN
AuthZ
IAM
Mobile AppsMobile Apps
Mobile Apps
Enterprise Backend
Systeme
Internet
API Gateway
API Gateway

21. APIs for Mobile Integration

22. 24.06.2014 Seite 22© 2014 [ipt] Switzerland
Matthias Biehl
Senior Consultant
matthias.biehl@ipt.ch