Recommended
Recommended
More Related Content
Similar to Ektron DxH Developer Dive - Synergy 2012
Similar to Ektron DxH Developer Dive - Synergy 2012 (20)
Recently uploaded
Recently uploaded (20)
Ektron DxH Developer Dive - Synergy 2012
- 1. Developing on the Digital Experience Hub Derek Barka, Chief Software Architect Follow me @dsbarka
- 2. Digital Experience Hub • Overview • Managing Connections • Use Case: Sharepoint Integration • Use Case: Html Forms Integration • Developer Framework • Code: Building a Connector • Code: Using the ContextBus Framework
- 3. Connected Systems ektron ee e e e Connector Connector e • Extensible Platform Connector e • Lower Risk • Faster Delivery • Lower TCO Connector e • Re-useable Connectors • Leverages current investments
- 4. Digital Experience Hub • Overview • Managing Connections • Use Case: Sharepoint Integration • Use Case: Html Forms Integration • Developer Framework • Code: Building a Connector • Code: Using the ContextBus Framework
- 7. Digital Experience Hub • Overview • Managing Connections • Use Case: SharePoint Integration • Use Case: Html Forms Integration • Developer Framework • Code: Building a Connector • Code: Using the ContextBus Framework
- 10. Digital Experience Hub • Overview • Managing Connections • Use Case: Sharepoint Integration • Use Case: Html Forms Integration • Developer Framework • Code: Building a Connector • Code: Using the ContextBus Framework
- 13. Digital Experience Hub • Overview • Managing Connections • Use Case: Sharepoint Integration • Use Case: Html Forms Integration • Developer Framework • Code: Building a Connector • Code: Using the ContextBus Framework
- 14. DxH: Core Components • Connector • ObjectDefinition • ObjectInstance • Workflow
- 15. IConnector
- 16. Object Definition - Id : HubSpot.Contact - Name : Contact Field Definition • Name : vid • DataType : long • IsKey : true Field Definition • Name : Job Title • DataType : string Field Definition • Name : email • DataType : string
- 17. Object Instance - Id : HubSpot.Contact - Name : Contact Field • Name : vid • value: 222345 Field • Name : Job Title • Value: Engineer Field • Name : email • Value: db@ektron.com
- 18. Ektron HubSpot Html Form Contact Name Email e Email e Name e Role Title Reason for e Downloading Company Comment
- 19. DxH WorkFlow Payload LoginTask MappingTask SaveInstance Logout
- 21. Questions? Follow me on Twitter @dsbarka Blog at Ektron.com/Community/DerekBarkaBlog
Editor's Notes
- So why did we build the Digital Experience Hub? How many of your companies use Salesforce or another CRM? Hubspot? Campaign Management?As you know, most web sits don’t exist in a vacuum and enterprise need to use the tools they already own and enjoy. So site’s need to integrate with other tools in your enterprise – marketo, salesforce, sharepoint, hubspot. Bottom line – there’s a number of tools besides your cms that you use to interact with customers and they need to coordinate better to drive leads and conversions. Were you all blown away by Mark Roberge this morning? We’ll see how to deliver relevant content with the DxH.Leverage Existing Systems – Leverage Best of breed Software – we can’t do inbound marketing better than hubspot, CRM better than salesforce, so why limit our customers?Generic platform for integrating your many enterprise applicationsEveryone is building these same integrations over and over – now you can build one connector and re-use it.Context Bus itself is just a Service that manages connections, provides endpoints to connectors, runs workflows.The key is for organizations to be able to integrate their mission-critical sales and marketing applications into one comprehensive digital experience hub. The EktronContextBus™, a new integration layer that passes content and context between connected marketing applications, powers the Digital Experience Hub. Marketers have a number of technologies – they have marketing automation tools to nurture leads, CRM tools to help manage customer relationships, web analytics to understand performance to see what’s working and not working. But these have always worked separately. Leverage all this data on your website. Now, marketers can easily connect what they deliver on a website to their marketing programs, trigger emails to be sent out to customers based on user activity, personalize the experience based on the context (site behavior, demographic, traffic source and customer data) of the user, and monitor social conversations so they can respond in real-time as well as gain insight into the hot topics in their industry allowing them to recognize where and when an opportunity exists. Ektron is helping connect these technologies together to solve customer experience. The Digital Experience Hub provides out-of-the-box integrations into popular marketing applications like Marketo and Silverpop for marketing automation, Omniture and Webtrends for web analytics, and Microsoft Dynamics and Salesforce for Customer Relationship Management.Differentiate from our peers because we believe strongly in concept of integration – bringing together these marketing technologies to solve your business problems. Our competitors who are creating suites can’t keep up with best of breed technologies.
- So how do you go about managing all these connectors in the digital experience hub?We have a UI in the CMS for setting up and managing connections to systems.UI will be in its own application in the future. All existing OOTB integrations are in workarea now.
- Simple UI in WorkareaGo to Settings DxH and select Add ConnectionAuto-populates all connectors installed with the DxH
- Next, you can name the connection and supply the information needed to connect to the external system. This connection info will be saved in the DxH so you can easily connect to the system later.
- Lets take a quick look at a few things you can do with the DxH – I think to understand the system, it might be first, useful to see what types of things you can do with it.Sharepoint – I LOVE Sharepoint. Its fantastic for intranets and internal collaboration. HORRIBLE for web sites. So why not leverage the right tool for the job???Co-Exist with SharePoint!
- The next OOTB use case we support is HTML forms integration with your external systems. So if a site visitor fills out a form to download an ebook, you can wore that form up to immediately publish that customer information right to Salesforce, Marketo, HubSpot or any other connector.
- When you’re creating an HTMl Form, you can use this new “Map to DxH wizard” to map your form to an external objectThe first step is choosing the connection you want to use and then the Object from that connection.
- Next, you can map your Form Fields to fields available of the External Object.When you’re done, you simply save and any new form submissions will be pushed to your connected system.Internally, the CMS will also track cms:id to external system:id so we can track visitors easier.
- DxH made up of 4 major components
- Represents an external system to the DxHConnector – supports logging in, and CRUD operations for external system.Exposes 3 Object Types that represent external system – Objects, Events, Operations (methods).Operation – Approve Content, Publish Content
- IConnector supports an API for retrieving a list of support Objects in the systemYou can then say “Oh – what does an Account look Like?” and retrieve a full object definition for an account --including all the fields that
- Once you know what an object looks like you can ask the connector for instances of those objects. ObjectDefinition = schema of an objectObject instance = actual instance of an object – Contact info for db@ektron.comConnectors support retrieving and saving ObjectInstances through the DxH.
- DxH also supports mapping one object instance to another so you can migrate data from one application to another.Define a map once and execute it multiple times.
- Workflow – as the name suggests – supports multiple tasks or operations as a unit of work.This example represents the workflow definition we use for SP integration.It begins with a: 1. payload which is the SP ObjectInstance, 2. Login to Ektron Connector 3. executes a mapping task to convert to Ektron Object Instance 4. Saves the Transformed Object Instance to Ektron Connector 5. Logout of Ektron.Workflows can be tied to Events so when a connector raises an event, a saved workflow is executed.