(ATS6-Dev08) Integrating Contur ELNwith other systems using a RESTful APIMats KihlénDirector R&D and Pre-salesStockholm, S...
The information on the roadmap and future software development efforts areintended to outline general product direction an...
Content• Contur ELN basics• Extending the ELN capabilities• RESTful API – strategy and architecture• Solution examples
Contur ELN basics• Corporate documentation system for capturing andsharing experimental observations• Experiment rather th...
”Demo section”
”Demo section”
”Demo section”
Technology choice• Traditionally we connect to other systems using ODBC– Limited functionality– Hard to access all data, e...
Extending the capabilitiesFormulations Analytical PackagingDomainspecificcapabilitiesDomainspecificcapabilitiesDomainspeci...
API development scope• Based on RESTful services– State-of-the-art technology based on http– Very general operations: GET,...
REST API Syntax - exampleOperation URLStart Client http://w2k8-contur-eln.accelrys.net/Get Information about the system: U...
• Launch PLP protocols from the Contur ELN client and have theresult documented in an experiment– List of available protoc...
Application example : Run PipelinePilot protocolChoose protocolfrom new toolbox inthe experimenteditor
Application example : Run PipelinePilot protocolInput data can beread from an ELNsection
Application example : Run PipelinePilot protocolRun the protocol...
Application example : Run PipelinePilot protocolProtocol reads datafrom experimentand providesoptions
Application example : Run PipelinePilot protocol...get results
Application example : Run PipelinePilot protocol...and push backinto the experiment
Application example : Ad hoc reportingLaunch reportingingprotocol
Application example : Ad hoc reporting...select sectionsto publish
Application example : Ad hoc reportingView report
Application example : Ad hoc reporting...post toSharePoint
• First version planned for June 2013 release– All GET, some PUT and POST– Focus on experiment content– The Web client is ...
• Keeping the core ELN out-of-the-box is critical• The new API provides an efficient communication methodallowing integrat...
(ATS6-DEV08) Integrating Contur ELN with other systems using a RESTful API
(ATS6-DEV08) Integrating Contur ELN with other systems using a RESTful API
Upcoming SlideShare
Loading in...5
×

(ATS6-DEV08) Integrating Contur ELN with other systems using a RESTful API

302

Published on

In order to enable easy integration between Contur ELN and other informatics systems a RESTful API has been developed. Data may be extracted from ELN experiments using GET calls, but external applications can also insert results directly into the ELN record. In particular the API can be used with Accelrys Enterprise Platform to create complex flows for resolving scientific problems. Such protocols may be launched from within the ELN client.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
302
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "(ATS6-DEV08) Integrating Contur ELN with other systems using a RESTful API"

  1. 1. (ATS6-Dev08) Integrating Contur ELNwith other systems using a RESTful APIMats KihlénDirector R&D and Pre-salesStockholm, Swedenmats.kihlen@accelrys.com
  2. 2. The information on the roadmap and future software development efforts areintended to outline general product direction and should not be relied on in makinga purchasing decision.
  3. 3. Content• Contur ELN basics• Extending the ELN capabilities• RESTful API – strategy and architecture• Solution examples
  4. 4. Contur ELN basics• Corporate documentation system for capturing andsharing experimental observations• Experiment rather than data centric• Out-of-the-box solution– No customized workflows– Basic connections to other systems through lookup sections• Common for all disciplines
  5. 5. ”Demo section”
  6. 6. ”Demo section”
  7. 7. ”Demo section”
  8. 8. Technology choice• Traditionally we connect to other systems using ODBC– Limited functionality– Hard to access all data, e.g. due to serialized objects– Vulnerable to database changes– Not available for Cloud customers• Communicating via an API on the application serverwould be better!
  9. 9. Extending the capabilitiesFormulations Analytical PackagingDomainspecificcapabilitiesDomainspecificcapabilitiesDomainspecificcapabilitiesContur ELN
  10. 10. API development scope• Based on RESTful services– State-of-the-art technology based on http– Very general operations: GET, DELETE, PUT, POST• Focus on experiment content– Extract selected information from one or several experiments (GET)– Data returned as XML or JSON objects– Insert data into specified experiments (PUT, POST)• Ability to call external applications from the client– Limited configuration of icons and buttons – currently from an experiment– Through PipelinePilot protocols
  11. 11. REST API Syntax - exampleOperation URLStart Client http://w2k8-contur-eln.accelrys.net/Get Information about the system: Users Fetch all usershttp://w2k8-contur-eln.accelrys.net/api/v1/users <--A userhttp://w2k8-contur-eln.accelrys.net/api/v1/users/1704http://w2k8-contur-eln.accelrys.net/api/v1/users/821Get information about experiments of a user http://w2k8-contur-eln.accelrys.net/api/v1/users/1704/experimentsFetch author of an experiment http://w2k8-contur-eln.accelrys.net/api/v1/experiments/EXP-12-AA0103/authorGet an experiment http://w2k8-contur-eln.accelrys.net/api/v1/experiments/EXP-12-AA0103Get a sections of an experiment http://w2k8-contur-eln.accelrys.net/api/v1/experiments/EXP-12-AA0103/sectionsGet data of a section http://w2k8-contur-eln.accelrys.net/api/v1/sections/1050http://w2k8-contur-eln.accelrys.net/api/v1/sections/{ID}/datahttp://w2k8-contur-eln.accelrys.net/api/v1/data/1051API Help file
  12. 12. • Launch PLP protocols from the Contur ELN client and have theresult documented in an experiment– List of available protocols in the experiment toolbox– Synchronous or asynchronous running mode– Input interactively and/or from Contur ELN sections– Results pushed back into ELN experiment (as text, image, Excel-file,file attachment etc)• Component collection embedding API calls will be available– Direct API calls from any application also possibleCalling applications
  13. 13. Application example : Run PipelinePilot protocolChoose protocolfrom new toolbox inthe experimenteditor
  14. 14. Application example : Run PipelinePilot protocolInput data can beread from an ELNsection
  15. 15. Application example : Run PipelinePilot protocolRun the protocol...
  16. 16. Application example : Run PipelinePilot protocolProtocol reads datafrom experimentand providesoptions
  17. 17. Application example : Run PipelinePilot protocol...get results
  18. 18. Application example : Run PipelinePilot protocol...and push backinto the experiment
  19. 19. Application example : Ad hoc reportingLaunch reportingingprotocol
  20. 20. Application example : Ad hoc reporting...select sectionsto publish
  21. 21. Application example : Ad hoc reportingView report
  22. 22. Application example : Ad hoc reporting...post toSharePoint
  23. 23. • First version planned for June 2013 release– All GET, some PUT and POST– Focus on experiment content– The Web client is refactored to use API communication– Available on the Cloud• Second version November 2013– All PUT/POST actions– Non-experiment calls (user statistics etc)– Finalize Web client to only use API as communication method– Call PLP protocols from the Web clientStatus and Release plans
  24. 24. • Keeping the core ELN out-of-the-box is critical• The new API provides an efficient communication methodallowing integration, both with external systems and to buildfunctional extensions• The API will also be available for the Cloud• Building clients on the API facilitates good quality andperformanceConclusions

×