Recomendados
Mais conteúdo relacionado
Destaque
Destaque (18)
Jive World 12 ~ Apps 102: The best of both worlds- powerful apps - easy development-final
- 1. Jive Apps Development 102 The Best of Both Worlds: Powerful Apps - Easy Development Brian Shoemaker Development Manager, Enabling Technologies Thomson Reuters Mark Weitzel Director, Platform & Ecosystem, Jive Software President, OpenSocial Foundation © Jive confidential
- 2. Introductions: Mark Weitzel • http://www.linkedin.com/in/weitzelm • Twitter: weitzelm • Did you know… I lived through a Hurricane AND an Earthquake in the SAME week? © Jive confidential
- 3. Introductions: Brian Shoemaker • http://www.linkedin.com/in/brianshoemaker • Twitter: shoemaker • Did you know… I began racing triathlons in 2010. © Jive confidential
- 4. Objectives • Recognize how apps can solve real business problems • Best practices on exposing your business logic • Understanding the changes between 5 & 6/Cloud and how to manage them © Jive confidential
- 5. Agenda • Our “real world” apps • Building and using a proper API: The example app • How Apps will evolve from 5 to 6/Cloud © Jive confidential
- 6. Our “real world” apps “Be your own dentist!” Rube Goldberg © Jive confidential
- 7. Our approach Adopting Jive apps at Thomson Reuters • Needed to move tools from legacy portal to Jive • Involved in the Jive Developer community. • “Hello World” example basis for learning. • Developer community great resource to answer questions. • “Developer Challenge” to learn and use Jive. © Jive confidential
- 8. Phonebook App Our first app at Thomson Reuters • The problem: create a new “Colleague Finder” tool as an app within Jive. • Paired an API and UI developer. • Using Jive Connects. • Developer Console. © Jive confidential
- 9. Email Signature App • The problem: provide employees the ability to generate a brand-compliant email signature. • Simple app pulls attributes of the current user from Jive. • Call external API to email the signature. • Developer Console. © Jive confidential
- 10. Building a social business app A more complete example © Jive confidential
- 11. Building a proper API: The example app • How to aggregate content from Jive & elsewhere • What is a RESTful API & why is JSON important? • Best-practices and attributes (CORS, JSONP, GET/POST/PUT/DELETE, content-types) • Demonstrate the API we'll be using for our sample application, including methods to call API. © Jive confidential
- 12. Using the API within our app • Demonstrate calling the API from within the app. • What do we do with the data once we get it? © Jive confidential
- 13. Illustrating the Social Business Application Patterns • Posting to the Activity Stream • App Mentions. • Sending content to home server • Aggregate external content © Jive confidential
- 14. How Apps will evolve from 5 to 6/Cloud © Jive confidential
- 15. How Apps will evolve from 5 to 6/Cloud • Reuse what you build today • From Dashboard to Quick Launcher • Repurposing “Home View” • Moving from V2 to V3 © Jive confidential
- 16. Phonebook App • Describe change to take advantage of App Mention. • New stuff with V3? © Jive confidential
- 17. Demonstration Materials • Find us on the Jive Developer Community • Brian and Mark’s Most Excellent Jive World Adventure © Jive confidential
Notas do Editor
- Thomson Reuters moved from an 8-year-old portal with a large number of legacy tools and content to Jive. Several legacy tools needed to ported to our new Jive portal. Writing an app to replace these tools was the easiest and most desirable solution. We became very involved with the Jive developer community (https://developers.jivesoftware.com/). The “Hello World” example provided the basis for our development, demonstrating the basics of an app. The community is quick to answer questions, Mark seems to be contributing to every discussion thread. We rarely went more than a day before getting a helpful answer. Put challenge to development team to create an app. Goal to immerse developers in this new environment. The challenge: * Create a Jive application that displays items from either the Twitter, LinkedIn or Flickr API. * From an app, post an update to the Activity stream.
- We needed to replicate the Thomson Reuters Colleague Finder tool in our Jive instance. The Phonebook uses our own LDAP information to search colleagues. Not all LDAP detail is available from within a Jive search. API is protected using OAuth2. Using Jive Connects to expose API to apps within Jive.Using Developer Console to instantiate app within our Jive UAT environment and publish to app market. Workflow:App sends query to API via Jive Connects. API queries LDAP. Search result formatted to JSON, returned to the caller. App displays the result. Our approach:One API developer. One UI developer.
- We needed to replicate the Thomson Reuters Email Signature Generator tool in our Jive instance. Tool is important for brand compliance in communications. Simple app that pulls attributes of the current user from Jive. User can edit their signature, then have the formatted signature emailed to them. The API call to create the signature does not use Jive Connects, using an XHR (POST) request, sending JSON.
- Talk through the origins of Jive Apps -- From OpenSocial* List of people you're following.* Retieve data from outside RESTful API.* Display results.* Post activity/update to your stream.
- Methods to call API to demonstrate: makeRequest() and osapi.http.get()
- Talk through the origins of Jive Apps -- From OpenSocial
- The phonebook app will be updated to allow for app mention. The location app we’re demonstrating will also use app mention. This has been completed.