BATTLEFIELD ORM: TIPS, TACTICS AND STRATEGIES FOR CONQUERING YOUR DATABASE
Aurea Software successful integration case study - Patient Travels (patient portal) - Aurea & Helmes Nordic Seminar 2017
1. 1
Avella | Arkitektur & integrasjon
13. juni 2017
PRIMO
God integrasjon handler om helhetsforståelse
2. 2
Avella | Arkitektur & integrasjon
2Background
• The goal of the Mine Pasientreiser project
• Simpler and more accessible solution for users
• The greatest possible degree of equal
treatment
3. 3
Avella | Arkitektur & integrasjon
3Requirements
• Supply necessary integrations between frontend and backend
• Supply a set of common web based services
• Agile development
• Continous build (and deploy)
• 24/7 availability
• Based on Aurea software Takstsoneregister
Meldingstjeneste
NISSY
Oppmøteregister
Virksomhetsregister
NHNPersonregister
ArcGis
Frikortregisteret
Mine Pasientreiser
på helsenorge.no
PRIMO
PRO
PRIMO
TeleformOCR Regelmotor
NHNPersonregister
HelsedirektoratetPasientreiser
DIFIsKontaktogres.
Personlighelsearkiv
ID-porten
Etablert
Nyttellerendret
4. 4
Avella | Arkitektur & integrasjon
4Project
• Scrum
• Using the Atlassian stack to support the
development
• Aurea SDP to support continous builds
• API gateway to expose services
• Common Data Model (CDM)
• Focus on logging
• Average of 4 developers (around 6 resources in
peak periods)
5. 5
Avella | Arkitektur & integrasjon
5Challenges
• Different startup (frontend/primo/backend)
• Backend started half a year before
• Frontend started half a year after
• Government regulation
• Rules based in laws, but they where not adopted at
the start of the project
• Had to assume how it should be implemented
• Technical challenges
• Aurea SDP and Artifactory
• Intermediary and outbound REST
• Intermediary and automated deploy
PROHelsenorge.no
PRIMO
Helsedirektoratet Pasientreiser
6. 6
Avella | Arkitektur & integrasjon
6What did we do?
• Spent much time on the CDM in early stages
• Focused on APIs and mocks
• Created templates and generics
• Built a Track & Trace framework
• Dedicated person to work with the build &
deployment platform
• Working closely with the application management
provider
7. 7
Avella | Arkitektur & integrasjon
7Some technical issues
• Problems with SDP/Maven against Artifactory
• Performed manual updates of Artifactory in the beginning
• Problems with JMS traffic from Sonic to
Intermediary
• Created a custom service on Sonic to solve this issue
• Difficult to handle outbound REST calls form
Intermediary
• Kept outbound REST calls on Sonic Connect
• Difficult to automate the deploy of Intermediary
• Scriped as much as possible
• Some performance issues during load testing
• Ended up as a performance issue on the database
8. 8
Avella | Arkitektur & integrasjon
8The result
• Xx integrations
• Xx common services
• XX new claim for refund pr. day
• Creates around 200 000 transactions on PRIMO
• Map server (ArcGis) traffic, most commonly used
• Latency < 60-80ms
• Scaled for around 100msg/sec
• Xx Brev?
• Samkjøring
• Hvor mange turer pr. dag?
• SMS?
9. 9
Avella | Arkitektur & integrasjon
9Deploy
• At startup
• Only possible to do a full deploy
• Downtime apx. 1 hour
• Long time to create a new release
• Now (after 6 months)
• Partial deploy
• No downtime
• Need around 2 hours to create a new release
• In near future
• Continous deploys
10. 10
Avella | Arkitektur & integrasjon
10Technical aspects
• Products
• Aurea Actional Intermediary 2015 (API Gateway)
• Aurea Sonic ESB 2015
• Platform
• Red Hat Enterprise Linux
• VMware
• Available 24/7
• Failover setup, both on Sonic and
Intermediary
11. 11
Avella | Arkitektur & integrasjon
11What’s next?
• Upgrade to CX Messenger (Q2-Q3 2017)
• Move all web traffic to CX API Manager
• Further speed up the release regime
• Dockerize
• Consider to set up CX Monitor
• Especially the possibility to use big data