Infrared simulation and processing on Nvidia platforms
Connect Your Clouds with Force.com
1. Connect Your Clouds with
Force.com
Developer Track
Jeff Douglas, Senior Technical Consultant, Appirio
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, 2011. 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. Jeff Douglas
Senior Technical Consultant
Appirio
Developer Evangelist
CloudSpokes
Co-Author
“Salesforce Handbook”
@jeffdonthemic
http://blog.jeffdouglas.com
4. What to Walk Away With
Solid understanding of Force.com integration options
and patterns.
Strategies for connecting various cloud platforms with
Force.com.
Best practices with Force.com integration options.
A deep love and appreciation for the Force.com
platform.
9. Apex Callouts – Don’t Forget!
Governor Limits!!
– 10 callouts per transaction
– 3MB payload maximum
– 120 timeout for all callouts
Dreaded “You have uncommitted work pending” error
Callouts from Triggers must be made asychronously -
@future(callout=true)
The joy of writing test coverage for callouts
Invoke WSDL/SOAP or REST services. Be careful
parsing returned JSON data. Parser is not yet native.
18. Demo - Microsoft Azure
Inbound integration from SQL Azure
Java app loads Sales Order data using the Bulk API
19. Recap - Microsoft Azure
Inbound integration from SQL Azure using Java and the
Bulk API
Best Practices
CVS column names should be same as target org
Consolidate data into SQL Views for easy querying
Schedule the app (.jar file) to run periodically on a server
with email notifications for failures.
Monitor imports (success & failures) in Salesforce
20. Demo - Google App Engine
Inbound integration using the Google App Engine Toolkit
for Force.com (Java) to process customer RMAs.
21. Recap - Google App Engine
Inbound integration using the Google App Engine
Toolkit for Force.com (Java)
Best Practices
Use the “GAE” version of the Toolkit for App Engine.
Use the precompiled “Partner” jar
URL fetch service limited to 5 seconds so streamline
queries and returned results
Cache connection for improved performance
22. Demo - Amazon AWS
Outbound integration to Amazon S3 using the Amazon
Web Services toolkit.
Customer service rep approves RMA, creates PDF and
stores in Amazon S3.
23. Recap - Amazon AWS
Outbound integration to Amazon S3 using the Amazon
Web Services toolkit.
Best Practices
Setup different S3 buckets for sandbox and production
Watch bucket permissions
Guard your API keys!
24. Demo - Heroku
Platform/lauguage integration with Ruby and Heroku
Customer checks the status of their RMA on mobile
device.
Ruby on Rails application using the REST API.
25. Recap - Heroku
Inbound integration with Heroku.
Ruby on Rails application using the REST API.
Best Practices
Use OmniAuth for authorization
Use HTTPS for OAuth2 callback
Use the Heroku SSL add-on for quick & easy
encryption
Treat access tokens like passwords!!
26. Recap – What Did We See?
Strategies for Force.com integration depending on use
case.
Force.com Toolkits for different services and language
How do develop integrations regardless of platform and
language.
How to use different Force.com APIs depending on
application purpose.
Best practices for technologies, toolkits and platforms
27. Additional Resources
Github code repo
http://www.github.com/jeffdonthemic/df11preso
Cloud to Cloud Integrations with Force.com
http://wiki.developerforce.com/index.php/Webinar:_Cloud_to_Cloud_Integrations_with_Force.com
Loading Large Data Sets with the Force.com Bulk API
http://wiki.developerforce.com/index.php/Loading_Large_Data_Sets_with_the_Force.com_Bulk_API
Google App Engine Toolkit for Force.com
http://code.google.com/p/sfdc-wsc/
Force.com Toolkit for Amazon Web Services
http://wiki.developerforce.com/index.php/Amazon_Toolkit
OmniAuth
https://github.com/intridea/omniauth
29. But wait, the DevZone has more!
Open Source Lab
Discover new & interesting open projects
Lightning Forum
Drop in for a quick blast of knowledge
Tech Demos
See and learn the latest from the experts
Code Consultations
Sign up for 1:1 sessions at the Welcome Desk
@forcedotcom
30. How Could Dreamforce Be Even Better? Tell Us!
Every session
survey you submit
is a chance to win
an iPad 2!
Watch your inbox at the end of each day for an email from
our survey partner, Alliance Tech.
Click on the personalized link to be directed to the survey
page for the sessions you attended.
Notas do Editor
Any purchase decisions customer make should be made based on currently available technology. Please visit our website sto review our Safe Harbor statement in detail.
So what’s my goal today? Here’s what I want you to walk away with. After this session I’d like you to have…
Need to setup exactly what this is. This is a “cloud to cloud” integration session. Rip off sandeep’swebinar text for his webinar. Why we are talking about cloud to cloud and why they are different.
Inbound – Material master records from SAP, Sales data from Siebel or maybe a social app on Heroku is pushing over Facebook data.Outbound – Push employee changes to Workday, storing documents on Amazon S3 or geocoding account records with SimpleGeoHybrid – typically an outbound call to an external service that then makes a callback to Force.com to process Force.com data. We are not gonna cover that but describe sandeep’s demo.
List the toolkits again for the toolkits. Looks at different toolkits. Twitter is outbound. FB is outbound.
By far the most popular and common is apex callouts. Tell why talking about callouts and not the others.
Force.com is pretty much an open platform and it likes to play with other platform and languages. There are a number of toolkits with basically wrap around the web services API and allows you to interact with Force.com with native code. There are ton of examples available so you can download the individual toolkits and get started.-- mention that there are also mobile toolkit available. Probably made the announcement alaredy.
I posted this graphic on my website a month or so ago and my buddy Jason Venable said it should have the disclaimer, “Do not design a system like this! Demo purpose only.” In reality you could build this entire process on Force.com. However, there are a lot of companies that have a landscape that looks similar to this.-- make this a build slide and talk about each in the process.-- Explain what an rma is.
I posted this graphic on my website a month or so ago and my buddy Jason Venable said it should have the disclaimer, “Do not design a system like this! Demo purpose only.” In reality you could build this entire process on Force.com. However, there are a lot of companies that have a landscape that looks similar to this.-- make this a build slide and talk about each in the process.
Talk about how this could be done in .NET but this is different use case.Make sure you increase the font size of eclpse!!!!! Font size 18Show the demo with shaded out sections not being explained. This is the recap slide.
Talk about how this could be done in .NET but this is different use case.Make sure you increase the font size of eclpse!!!!! Font size 18Show the demo with shaded out sections not being explained. This is the recap slide.
Explain what an RMA is.
Recap on THIS section and what an rma is.Next slide do a recap after each section of the demo. Outline Force.com Toolkit on the graphic
Just show the controller, template for the pdf & rmas3. talk about why we are storing in sfdc and aws… want to outline future method. Tell what we could do to fix it.
Just show the controller, template for the pdf & rmas3. talk about why we are storing in sfdc and aws… want to outline future method. Tell what we could do to fix it.