ICS JUMP Session. IBM Connections Cloud Catalog

Transcription

1 ICS JUMP Session IBM Connections Cloud Catalog

2 The New Connections Catalog is Live! All Clouds Double the Apps New App Providers

3 Why a Catalog in Connections Streamline deployment of 3 rd Party solutions based on App Registry Extensions Increase Awareness of ISV solutions Drive the Value Add of our Ecosystem Buy Partner Integrated Solution Buy Connections with 3 rd Party Solution

4 Catalog and Apps Replaces: 3rd party integrated apps Org extensions Internal apps Chat and Meetings

5 Connections App Dev Strategy Bring to market a unified platform so that users can access the social, cognitive and collaborative capabilities, from IBM and 3rd party developers, that matter to their business as an integrated, cohesive, and tailored experience The unified IBM Collaboration Cloud is a first class development platform where IBM and partners can deliver best of breed solutions and situational applications that when integrated are better because they leverage the unique IBM social cognitive, and collaboration services of the platform. 11/2/2017 5

6 The Connections App A way to add value to Connections An Integrated Experience (IBM, AppFusions, etc) A social/collaboration solution (ISVs like. Trilog) Collection of Extensions 6

7 Conceptual Architecture of an Integrated App Service Service Service ISV Solution Catalog APP Extension Extension Extension Extension IBM Connections Cloud (Multi-tenant) Extension Extension Customizer Registry

8 Trilog ProjExec Live Navbar Extension Connections Style Community Apps Use of Services/APIs

9 Integrated App Provider works! UX, Just Seamless SSO, logical workflows Interactive apps, seamless authenticatio 2017 Common and custom application integrations Activity streams and embedded experiences For cloud OR on-premises v5.5 CR1+

10 ISW Kudos Boards Visual Project Management Community App Native use of Activity as Content Service Mobile

11 Demo

12 Key Requirements To be permitted into the Connections Cloud Catalog an Connections Cloud App must: 1. Integrate into the Connections Cloud experience via well-defined Extensions and/or must provide continuity of the Connections UI as implemented by the customer across remote 3 rd party experiences 2. Must expose to the user value-add experiences by leveraging Connections Cloud services (via APIs or re-using UX components), especially: Profiles and networking Content from Connections Content stored in Connections Events and notifications into Connections 3. Provide user SSO Via customer provided oauth Via IBM provided global oauth

13 Architecture & Security - Configurable by Datacenter A 3 rd -party app can be deployed in all or selected IBM datacenters. IBM Connections data access secured by OAuth2 key pair assigned by IBM to each app. The 3 rd -party app deployed in different datacenter can have different configuration. E.g. extension URL, Oauth2 callback URL, config URL, debug org list ISV1 Site svr for NA & EU svr for AP ISV2 Site svr for all extension URL OAuth2 password OAuth2 callback URL config URL debug mode app1 app2 app1 app2 app1 Americas DC Europe DC IBM Connections Cloud Asia-Pacific DC

14 Configure App Endpoint After enabling the app in Catalog, clicking Partner Site will open the config URL in ISV site. Information as datacenter, orgid, orgname, admin , adminid will be encrypted using jwt token, and sent to config URL.

15 Who Provides Apps to the Catalog Today IBM IBM Integrated Solution Vendors (ISV) registered in PartnerWorld Future App Sharing by Developers within their Org Developers submit to Catalog

16 Onboarding to the Connections Cloud Catalog 1. Submit your App for Validation Manually until Connections Cloud app creation user experience 2. IBM accepts required information 1. About the app 2. Content and metadata for the catalog 3. JSON definition of Extensions 3. IBM reviews based on technical, business, and GTM criteria 4. IBM informs Submitter of approval or recommends remediation 5. IBM loads App into Catalog if approved

17 App Validation 17 11/2/2017

18 Reviews Performed App Functional Review Architecture Security Customizer Code Review Legal Due Diligence Support Sustainability

19 App Functional Review Business Value Must provide a clear benefit to the user while enriching the Connections Cloud experience. No Spam. No objectionable content within the app or posted by the app on a space transcript including links to Web sites hosting objectionable content. We ll reserve the right to classify something as objectionable as per IBM s Business Conduct Guidelines. Use Cases of integrated app a user can Design Quality We reserve the right to reject apps whose design is overtly similar to other apps in our catalog. Apps should be complete. All features must work as advertised. Descriptions, screenshots and demos must depict the app accurately. The app should not include hidden, undocumented or overlooked features. Demos should show actual use. All apps require professional look and experience (polish) What Categories do you see you app fitting Industry alignment, if any ie

20 Architecture Provide information and detailed architecture for the following App must implement requirements for: Extension points implemented How providing UX Continuity All Connections/Cloud APIs used How achieving Connections-enhanced app experience App must use our APIs in the way they're intended to be Expected (or observed) scalability and performance benchmarks and estimates. Cloud Deployment Model Datacenters/URLs

21 Framework and Guidelines for ISV Security Reviews The following are guidelines for ISV application security. The basic principle at work here is the application must provide secure transport of data in motion and secure Connections data at rest (any data retrieved and stored by the application). In addition the application at a minimum maintains a link/page where a customer can review the application's security policy. Application must require authentication Application available via https only (data in motion encrypted) Application must be secure covering OWASP 25. Application must encrypt any Connections data that is read and stored (data at rest) by the application. Application development process must include security practices and policy; this would include anything to help customer evaluate the security of the application.

22 Questions for ISV Security Reviews Does your application require authentication? Is your application available via https only (data in motion encrypted)? Does your application security cover the OWASP 25? [link] Does your application encrypt all Connections data that is read and stored (data at rest) by your application? Do you have within your application development process security practices and policies; this would include anything to help customer evaluate the security of the application?. Specifically: Do you perform security reviews? Eg.?? Do you scan each new release? Do you perform pen testing? Eg.?

23 IBM Connections Blue On Premise IBM Connections Green Cloud IBM Connections Pink

24 Customizer Code Review Provide all files intended for use by the Connections Customizer Provide JSON for Customizer extension definition Code must NOT Degrade performance of Connections Cloud Impact user experience negatively Create a DOS or similar effect Access user data outside of what is documented and agreed to by the user.

25 Legal Due Diligence Own all Intellectual Property associated with app Clearly defined and documented Terms of use and privacy for you app and all associated components If your app collects and shares user or usage data you must secure the user s consent.

26 A comment about T&Cs Catalog Terms for Partners IBM provides no support for 3 rd Party apps read the Provider Terms Some IBM apps, planned AS-IS from the labs, will not be supported

27 Support Documentation must reflect available functionality. It must be accurate, easy to navigate and easy to digest. Must provide SLA Must provide clear contact for app support

28 Sustainability Must have a planned or established delivery cadence and roadmap. Must commit to inform us of any changes to the app that will impact its lifecycle, functionality or content.

29 Get Started Today

30 How to Submit an App Today Send to 1. Company 2. Primary Contact Information 3. Business Partner Number 4. Link to App Info 5. Which DataCenters you want to be in (Americas, Europe, Asian-Pacific)

31 Process Flow - Today 1. IBM OM Sends Document for Validation 2. IBM Engineering Sends Document for Data Collection 3. (Optional) Watson Workspace 4. (Optional) Sandbox in I1 5. Deploy in Debug Mode 6. Test in Your Cloud Connections ORG or Trial

32 How to Test Your App 1. It is app provider s responsibility to test and validate their app. o IBM reserve the right to remove any broken app from Catalog 2. Test in I1 (optional) Provider can raise request to IBM to create a test account in I1. Providers to performance end-to-end test for their apps. 3. Test in production environment Catalog can set an app in debug mode (only listed test org can access) per datacenter. Provider should test and validate their app in each datacenter that to be in, before IBM turn this app on to public in that datacenter. To test the app, provider need to have account in each datacenter, and tell IBM their org IDs. IBM will add their org IDs to their app s o o debug list. For Americas and Europe datacenter, trial account can be applied from IBM Marketplace. For Asia-Pacific datacenter, raise request to IBM to create the trial account.

33 Catalog Roadmap

34

35 Priorities Streamlined Submission, Review, & Onboarding Self-Service and App Version Control App Categorization Support new Pink Extensions Onboard more Apps Viewable by users License management IBM Marketplace integration

36 App Creation Coming Soon App Registry Experience

37 App Creation

38 Sneak Peek: Submission Process

39 39

40

41

42

43

44

45

46