Tutorials building connectors
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Tutorials building connectors

on

  • 1,136 views

Slides to accompany this post: http://www.dekho.com.au/building-integration-connectors-with-dekho-tutorial-now-available/

Slides to accompany this post: http://www.dekho.com.au/building-integration-connectors-with-dekho-tutorial-now-available/

Statistics

Views

Total Views
1,136
Views on SlideShare
920
Embed Views
216

Actions

Likes
0
Downloads
2
Comments
0

1 Embed 216

http://www.dekho.com.au 216

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Tutorials building connectors Presentation Transcript

  • 1. Building SystemIntegration Connectors with Dekho
  • 2. Agenda• What are we integrating?• “The link”- Integration queries• Ready, go, launch… – Custom tools – Launching web applications – Launching client applications• And now in reverse… launching Dekho
  • 3. Integration is key…
  • 4. What are we integrating? Data System Integration Integration Launch 3rd Requires Search party app Coding Dekho In Flash + C# LaunchAdmin with Layer Info Dekho from a (or other) no coding 3rd party app Feature info URL and Images
  • 5. Launching a system from Dekho1. Selected feature(s) in Dekho2. Click a button3. Open a 3rd party app at specific context
  • 6. The processLocate specific asset Launch doc. mgmt. system View asset related documents
  • 7. I need to…1. Get the right data ?2. Create a launch button ?3. Connect and launch ?
  • 8. Getting the data you need AssetID is an attribute for the feature in the GDB ObjectID Asset ID Asset MgmtGDB system
  • 9. GDB link to 3rd party systems
  • 10. We need to map Spatial IDsto non-spatial IDs
  • 11. Dekho Integration Query• SQL query that translates one set of values (OBJECTID) to another (ASSETID)
  • 12. Dekho Integration Query
  • 13. Dekho Integration Query
  • 14. Building Integration queries
  • 15. I need to…1. Get the right data INTEGRATION QUERY2. Create a launch button ?3. Connect and launch ?
  • 16. What are Dekho custom tools?• Developed in flex• Plugged to Dekho as ‘Add Ins’• Loaded at run time• Add buttons to Toolbar• Reuse in different apps
  • 17. Custom tool code behind• Invoked on custom tool ‘click’ event• Using the integration query – Dekho web service API – SessionID – Integration QueryID• Generate launch URL – Web application – Client application
  • 18. Building custom tools• Watch ‘Building custom tools’ tutorial – Build – Compile – Deploy – Maintain
  • 19. Building a simpleintegration custom tool
  • 20. I need to…1. Get the right data INTEGRATION QUERY2. Create a launch button CUSTOM TOOLS3. Connect and launch ?
  • 21. Integration Patterns• Generating Web-App URL • Launching desktop installed software• URL structure (permalinks?) • Requires stepping outside the• Requires NO installation on the client browser sandbox side • Launching techniques: – SDK – Command line – File generation – COM
  • 22. Launching a web app• Generating Web-App URL• Completely custom tool driven HTTP://[Web_Based_Parameterized_URL]
  • 23. LaunchingNeatStreets.com.au
  • 24. Integration Patterns• Generating Web-App URL • Launching desktop installed software• Web app URL structure (permalinks?) • Requires stepping outside the• Requires NO installation on the client browser sandbox side • Launching techniques: – SDK – Command line – File generation – COM
  • 25. Stepping out side the browser sand box Desktop Windows Application
  • 26. Registering a new protocol extensionMapping URL protocol to an installed EXE file KEY_CLASSES_ROOT alert (Default) = "URL:MyProtocol Protocol" URL Protocol = "" DefaultIcon (Default) = “My_Protocol_Handler.exe,1" New protocol shell ‘Name’ open command (Default) = "C:Program FilesDekhoMy_Protocol_Handler.exe" "%1" Path to protocol handler executable
  • 27. Registering a new protocol extensionMapping URL protocol to an installed EXE file KEY_CLASSES_ROOT alert (Default) = "URL:http Protocol" URL Protocol = "" DefaultIcon (Default) = “My_Protocol_Handler.exe,1" shell open command (Default) = "C:Program FilesInternet Exploreriexplore.exe" "%1"
  • 28. Stepping out side the browser sand boxdekhoto[MYAPP]:param_string Custom tool click Desktop Windows Application My.exe • SDK • Command line • File generation • COM Integration Connector
  • 29. How connectors work args[0] = param string
  • 30. How connectors workDekhoToTrim:1234,9873,524,12 args[0] = “DekhoToTrim:1234,9873,524,12”
  • 31. Installing connectors• Deploy connector files• Register protocol + handler
  • 32. BaseConnector• VS2010 solution• BaseConnector class – Logging – Exception handling• Installer – Files – Registry manipulation
  • 33. Building a simpleconnector
  • 34. Integration Patterns• Generating Web-App URL • Launching desktop installed software• Web app URL structure (permalinks?) • Requires stepping outside the• Requires NO installation on the client browser sandbox side • Launching techniques: – SDK – Command line – File generation – COM
  • 35. I need to…1. Get the right data INTEGRATION QUERY2. Create a launch button CUSTOM TOOLS3. Connect and launch WEB/CLIENT PATTERNS
  • 36. Esri Australia Integration Library• Applications we have integrated with• Owned and managed by professional services• Install and configure• Check for vendor versioning
  • 37. Hansen 8 Pathway Custom Trim Custom tool Hansen 8 Custom tool code code tool codePathway client Trim client connector connector
  • 38. Agenda• What are we integrating?• “The link”- Integration queries• Ready, go, launch… – Custom tools – Launching web applications – Launching client applications• Launching Dekho
  • 39. Launching Dekho in 3.1• URL is your way in• System specific ‘Plug-Ins’• Separate Dekho instance every time http::appserver/dekho/Parameters... Application Launch!
  • 40. Dekho URL• Specific map and extentDekho?map=1&x=331809.928&y=5818278.314&distance=100• Specific bookmarkDekho?bookmark=bookmarkname
  • 41. Dekho URL• Running a search queryDekho?queryid=12&queryvalues=12345|Main||Melbourne
  • 42. Dekho Integration Query• Reverse mapping (AssetID -> ObjectID)• Used in Dekho URL
  • 43. Dekho URL• Select and zoom to featuresDekho?integrationqueryname=…&externalids=…
  • 44. Launching Dekho usingURL Parameters
  • 45. Agenda• What are we integrating?• “The link”- Integration queries• Ready, go, launch… – Custom tools – Launching web applications – Launching client applications• Launching Dekho
  • 46. Building your own integration connectors• What is the desired outcome?• Web or client application?• How ‘difficult’ is it to launch – Well documented parameterized URL structure? – Command line arguments? – SDK / API?• Follow web/client integration patterns discussed earlier• Handle logging and errors well
  • 47. 3.1 Open Integration Framework• ‘Custom tools’ based approach – No More ‘Integration Tools’• ‘Open’ – Build your own – Extend integration logic• Cleaner versioning and easier maintenance
  • 48. Product Information:www.esriaustralia.com.au/dekhowww.esriaustralia.com.au/dekhohelpwww.esriaustralia.com.au/dekhoblog