The document discusses the integration of enterprise systems with social platforms using Salesforce, highlighting the benefits, layers, and methodologies for successful integration. It outlines forward-looking statements regarding risks and uncertainties in Salesforce's operations while detailing integration strategies and tools, including API usage and data management practices. The emphasis is on how to leverage social media for customer insight and engagement while ensuring secure and efficient integration across systems.

1. Enterprise and Social Integration
Bridging Enterprise with Social using Salesforce
Shesh Kondi, Solutions Architect
Tuhin Kumar, Solutions Architect
@sheshzilla
@tuhink

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 any
litigation, risks associated with completed and any 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-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent
fiscal quarter. These 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. Agenda
• The Integration Landscape
• Benefits of Integration
•
Layers of Integration
•
How to approach Integration
•
Integration Tools
•
Demonstration
• Q&A

4. Defining Enterprise Integration
Enterprise Integration is considered to denote connecting computer systems
and IT applications to support business process operations
Enterprise Integration facilitates information, control, and material flows across
organizations by connecting all necessary functions and functional entities
to improve communication, cooperation, and coordination within the
Enterprise
»
KTH Royal Institute of Technology, Sweden

5. Benefits of Integration
• Build a layer of Agility
•
Provide a 360º view of relevant data sets
•
Eliminate data redundancy and enable business productivity
•
Ease of use for end users; eliminate navigation between multiple systems
•
Manage Secure access to data

6. The Salesforce.com Integration Layer
Rapid Development
Open Integration
Connect the Clouds
Open APIs
600M+ calls/day
Open
>50% of Transactions via API
Consume External Web Services
Social
Choice of development
languages
Easy to build social
applications
Build New Web Services
Leverage Existing Investments
100+ Certified Integration Middleware
Connectors
Rapid 100% Cloud
Development
Force.com for Facebook
Force.com for Google
Force.com for Amazon Web Services
Force.com for Azure
Salesforce.com’s Release Strategy provides backward
integration compatibility With Zero Customer Effort

7. Layers of Integration
• Data Layer – Exchange and Aggregate Data Sets between Salesforce and
Enterprise Systems
• Process Layer – Implement Service call-outs and Service listeners on
Salesforce for process orchestration
• Interface Layer – Build composite views from disconnected Web Apps
• Social Insight, Listening and Authentication – Capture relevant data from
Social Feeds, Monitor Brand and/or implement Social-Sign-On

8. Social Integration : Insight
• Tap into Social Networking as a New
Channel
• Integrate with Social Networks
(eg: LinkedIn) for Contacts/Leads
• Obtain better Customer insight

9. Social Integration: Listen and Analyze
• Listen to what your Customers say
about you
• Service your customer Gauging
Sentiments
• Analyze, Manage, Track and
Report on Social Engagement

10. Social Integration: Authentication
• Use Social network credentials to
access Salesforce
• Bridge Social and Enterprise profile
• Manage User Registrations

11. Data Layer: Direct Access to Data through APIs
Salesforce Contact
Data
Customer Master Integrated to
SFDC Custom Object via API
Integration with On-Premise
Database via 3rd Party
ODBC / JDBC connectors*

12. Presentation (UI) Layer: Embed UI in Salesforce
▪ Salesforce allows building and hosting
of custom web pages and present
Mash-Ups*
▪ Embed UI using an iFrame
Account,
Opportunity data
Order Management
data
▪ Salesforce ‘Canvas’
Account/Open Orders Mash-up

13. Presentation (UI) Layer: Embed Social Feed

14. Business Logic/Process Layer:
Enables “Composite” Application Creation
Real-time
Call Out via custom
button
Order Info
Returned
to SFDC

15. Approaching Enterprise Integration: Three Steps to Success
1. Define the
Process
2. Identify the
Integration Layers
3. Choose the
Approach
Data
User Interface
Build vs Buy
Tasks
Application Logic
Integration Methodology
Timing
Data Model
Resources

16. Data Layer: Volume Considerations
• For smaller data volumes (< 100K records), the standard API is recommended
• Use the Bulk API for large volume transactions (> 100K records)
• Bulk transactions now perform faster due to “Smart Bulk” capabilities of API
• To improve performance on Bulk transactions, avoid triggers on the object
when upserting / inserting bulk records
• Any post processing should be done as a separate isolated process (Apex
Batch Job)
• Identify data dependencies and perform Bulk jobs in corresponding order

17. Business Process Layer: Real Time Call Outs
Outbound Messages
▪ Point and Click Configuration
▪ Asynchronous (request does not wait for
response)
Call Outs are secure:
•Secure HTTP is supported
•Calls originate from a single IP address
•Request token is made up of Org ID + User
SessionID
Call back using Partner/Enterprise URL, Session
ID Token contained in the original Outbound
Message

18. Business Logic Layer: Force.com Streaming API
Administrator creates a topic based on a SOQL query
▪ PushTopic standard object
Client applications subscribe via the Bayeux protocol
▪ http://svn.cometd.com/trunk/bayeux/bayeux.html
Client applications receive notifications on creates and updates that match
WHERE clause of query

19. Presentation Layer: Force.com Canvas
Canvas – A platform service allows for external applications
to be easily and securely integrated into Salesforce from
their native environment with little re-design.
▪ Services Include
• JavaScript SDK
• Simplified Authentication (Signed Request or OAuth)
• Context Services
• Cross Domain API Calls
• App Registration and Management

20. Best Practices
Do
Don’t
•Understand the key processes,
integration layers, and approaches at
your disposal
•Consider existing integration
Infrastructure, including SOA and ESB
•Map requirements to key integration
patterns and corresponding solutions
•Approach Integration from the Pace
Layering viewpoint with a focus on
agility
•Consider Salesforce as an “SOA
Endpoint”
•
•
•
•
•
Deploy Salesforce.com without a basic
governance strategy.
Adopt Salesforce.com as it’s own “Silo” of
Technology; it is a full-fledged enterprise platform
Introduce new integration technologies unless
timing, transaction volumes, or other
requirements warrant.
Invent new integration methods unless extreme
conditions exist.
Accept the status quo when considering
Integration with Legacy and ERP applications
(SAP, Oracle, or COBOL); these problems have
been solved.

21. Integration Tools
Workbench

22. Enterprise and Social Integration
DEMO

23. Social Sign-On Integration
Successful Login
OAuth
Social Sign On Request

24. Enterprise SAP Integration
Closed Won Opportunity
Update Customer
Create Order
Update Invoice Number
Update Order Number
Fulfill Order
Create Invoice

25. Shesh Kondi
Tuhin Kumar
Solutions Architect
@sheshzilla
Solutions Architect
@tuhink