Architecting Multi-Org Solutions

4,916 views

Published on

Architecting Multi-Org Solutions

  1. 1. Architecting Multi-Org SolutionsDevelopers
  2. 2. Safe Harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward- looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other litigation, risks associated with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
  3. 3. Rajesh MadhawarayanTechnical Solution ArchitectRichard VanhookSenior Technical Solution Architect
  4. 4. Informal Poll Who currently works in a Multi-Org environment? Who’s an Architect? Administrator? IT Manager or Exec? Company has less than $500 mil revenue? Over $500 mil? Over $5 billion?
  5. 5. Agenda • Ingredients • Share • Cross Org Data • Integrate • Login • Just-in-Time (JIT) Provisioning
  6. 6. Multi-Org Ingredients Hub & Spoke Share Login Integrate
  7. 7. Agenda • Ingredients • Share • Cross Org Data • Integrate • Login • Just-in-Time (JIT) Provisioning
  8. 8. Sharing Data Across Orgs Hub Hub (1) Hub Broadcast (2) Spoke Aggregation
  9. 9. Salesforce to Salesforce (S2S) • Replicates data from one org to another • Native to Force.com, data never leaves the platform • Originally designed to share data with partners (and still is) • Practical, cheap option to enable sharing across multiple orgs • No external middleware required
  10. 10. Easy, useMoving data from one Salesforce toorg to another – how Salesforce. do we do that? Bad Architect! It’s not that simple!
  11. 11. Salesforce to Salesforce (S2S) • S2S is not for sharing data to an entity external to salesforce.com platform • Not a ‘true’ middleware substitute – It wont perform translations, transformations and validations. You still have to do them in Apex • Does not enrich data from 3rd party sources • Not a replacement for serious ETL use cases • S2S does not have an SLA. So latency must be accounted in your architecture for transferring & sharing parent – child records
  12. 12. Hub Hub Spoke Account Object Account ObjectName Phone After S2S Name Phone S2S S2S Data Insert Connec-Acme (800) 123-4567 Config Config Acme (800) 123-4567 Trigger tion 1 2 3 4
  13. 13. Demo: Hub Broadcast
  14. 14. Hub Spoke HubUser Object User Shadow User Shadow Name After Name S2S Name Insert S2S S2S Data Connec- Richard Trigger Richard Config Config Richard tion 1 2 3 4 5
  15. 15. Demo: Spoke Aggregation
  16. 16. S2S replicates dataWhat if I don’t want to replicate data?
  17. 17. Agenda • Ingredients • Share • Cross Org Data • Integrate • Login • Just-in-Time (JIT) Provisioning
  18. 18. Cross Org Data (XOrg) • Share data across orgs without replicating data! • One org designated Hub; Spokes are invited (similar to S2S) • Spokes contain “proxy” objects created from Hub “sync” • Proxy objects (Foo__y) can be queried or referenced in Apex • Pilot Spring ’13, GA Summer ’13 (Safe Harbor) • Notable limitations: Custom Objects only; Unsupported field types: Currency, Geolocation (beta), Lookup Relationship, Picklist, Picklist (Multi- Select), Text Area (Encrypted), Text Area (Long), Text Area (Rich)
  19. 19. Demo: Cross Org Data
  20. 20. Agenda • Ingredients • Share • Cross Org Data • Integrate • Login • Just-in-Time (JIT) Provisioning
  21. 21. External System IntegrationNot talking about “how” you integrate (the APIs, tools, etc) Most common issue: do you integrate with the Hub or each Data Hub individual Spoke? Data Considerations  Maintenance  Data Stewardship
  22. 22. External System Integration Lead REST API Hub
  23. 23. Demo: External System Integration
  24. 24. Agenda • Ingredients • Share • Cross Org Data • Integrate • Login • Just-in-Time (JIT) Provisioning
  25. 25. Login through Single Sign-On (SSO)Term DefinitionIdentity Provider (IdP) Server that authenticates user and generates the SAML assertionAssertion XML elements in a SAML token that contain user credentialsService Provider (SP) System that trusts the IdP user information and provides access to the ServiceMy Domain Custom URL for an orgFederation ID Org unique user identifier
  26. 26. Single Sign-On (SSO) Federation ID: john.smith Hub IdP Federation ID: john.smith SP Reminder: IdP = Identity Provider, SP = Service Provider
  27. 27. Demo: Multi-Org SSO
  28. 28. That was simple…You set up the Hub, Spokes and then create users in each org
  29. 29. How many of you think settingup Multi-Org SSO was simple?
  30. 30. How about?Create the user once in Hub, then automatically create in Spokes
  31. 31. Agenda • Ingredients • Share • Cross Org Data • Integrate • Login • Just-in-Time (JIT) Provisioning
  32. 32. Just-in-Time (JIT) Provisioning (Winter ‘13 GA) • Enable “Service Provider SAML Attributes” • Users can now be created on the fly (“lazy load”) • JIT existed prior to Winter ‘13, but not across orgs • User fields are mapped accordingly
  33. 33. Demo: Multi-Org JIT Provisioning
  34. 34. Agenda • Ingredients • Share • Cross Org Data • Integrate • Login • Just-in-Time (JIT) Provisioning
  35. 35. More at #DF12Building an Enterprise MDM StrategyThursday 10:30am Moscone Center West 2007Single or Multi-Org: Whats Right for My Deployment?Thursday 10:30am Moscone Center West 3024Driving Multi-Org Collaboration with S2SThursday 11:30am Moscone Center West 3006/3008
  36. 36. Rajesh Madhawarayan Richard VanhookTechnical Solution Architect Senior Technical Solution Architect

×