Fernando Malard, OFCdesk
This class will introduce the Forge platform from the perspective of an early adopter – starting with business aspects, paradigm shift, cloud concepts, and the future of Autodesk cloud platform strategy. We will cover some of the technical challenges with web programming from the perspective of someone migrating from a desktop programming environment to the cloud, and discuss how to overcome them. We will then walk through some simple yet representative code samples helping you to get started with the Forge platform through Model Derivative API and Design Automation services.
4. This class will introduce the Forge platform starting with
business aspects, paradigm shift, cloud concepts and the
future of Autodesk cloud platform strategy. We will introduce
and present technical challenges with web programming,
how to overcome them and take full advantage of cloud
resources leveraging your business. We will then present
some simple yet representative code samples helping you to
get started with the Forge platform through View & Data and
AutoCAD I/O services.
Class summary
6. “It’s clear now that while organizations may
have come to the cloud to reduce costs, it’s not
why they stay. The true potential of cloud lies
in an organization’s ability to leverage this agile
delivery model to transform the business.”
Rick Wright, Principal and Global Cloud Enablement Leader at
KPMG
From Desktop to the Cloud – Agile delivery
7. From Desktop to the Cloud - Usage
*KPMG: 2014 Cloud Survey Report
8. From Desktop to the Cloud – Improvements / Challenges
*KPMG: 2014 Cloud Survey Report
9. From Desktop to the Cloud – Facts
Desktop
• Download & install
• High resource demand
• Security and setup time
• High initial investment
• Poor file/data sharing
• Vulnerable information
• Per user license
• Complex backups
Cloud
• Fast disaster recovery
• Centralized maintenance
• Low initial investment
• Enhances teamwork
• Centralized file storage
• Accessible to small businesses
10. From Desktop to the Cloud – Development
• New languages and paradigms
• Libraries and packages
• Client-server architecture
11. From Desktop to the Cloud – Data security
• Access control
• Token based authentication
• Encrypted user data storage
12. From Desktop to the Cloud – Debugging / testing
• Desktop debugging
• Web debugging
• Browser cache…Refresh!
19. • Powerful core engines
• Consumed via web services
• Zero-client installs
• Web based interfaces
• Major Browsers supported
• WebGL for viewing
• JavaScript for client programming
Autodesk Forge
21. • REST = Representational State Transfer
• Based on resources
• Used for cloud solutions through web services
• Web services calls: GET, PUT, POST and DELETE
• Work with HTTP responses
• Uniform Resource Identifier (URI)
• Uniform Resource Locator (URL)
• Uniform Resource Name (URN)
Autodesk Forge - Technologies
22. • OData = Open Data Protocol
• Simplifies business logic
• Easy access to data and services from any client
Autodesk Forge - Technologies
23. • OAuth = Open Standard for Authorization
• Based on access tokens issued
• Uses an authorization
server
• Three-legged workflow*
• Scoping*
Autodesk Forge - Technologies
24. The challenge:
• Product specification tool
• Accessible and easy to use
• Avoid desktop installation
• Rich zero-client 3D viewer
• Integrated with custom data
Autodesk Forge – Use case / ofcdesk Connect
25. The solution: Autodesk Forge
• Simple web interface
• No desktop software
• No installation
• WebGL 3D viewer
• Dedicated servers
Autodesk Forge – Use case / ofcdesk Connect
28. • New name: Design Automation API
• Create, edit or query DWG files
• Save DWG files to other formats
• Run AutoCAD native commands (non-UI)
• Simplify the DWG manipulation process
• Scalable resources (run at Autodesk cloud)
• Extensible with apps (CRX, DBX, LSP and DLL)
Autodesk Forge – AutoCAD I/O
29. Abstractions:
• AppPackage: Extensions in DBX, CRX, LSP or DLL
modules, written in AutoLISP, C++ or .NET
• Activity: Pre-configured action, in AutoCAD script
language, that can refer to one or more AppPackages
• WorkItem: Represents each execution of your Activities
(actions) providing input and output parameter values
Autodesk Forge – AutoCAD I/O
30. Autodesk Forge – AutoCAD I/O
AutoCAD I/O
Your
Cloud
AppPackage 1
AppPackage 2
AppPackage 3
Activity A
Activity B
Activity C
WorkItem A
WorkItem B
WorkItem C
31. • New name: Viewer API
• Upload models via REST API
• Return a viewing stream
• Access to model data using JavaScript
• Rich 2D and 3D models into the web browser
• No plug-in, runs in Chrome, Safari, IE11, Firefox
• More than 60 design file formats
Autodesk Forge – View&Data
32. Abstractions and concepts:
• Bucket: It is a storage folder where you upload the input
files. Can be Transient, Temporary or Persistent
• OSS: Object Storage Service is responsible for storing and
maintaining, secured by OAuth 2.0, uploaded files
• Viewing Services: Translation service with the input URN
then return other URN to stream the resulting model
Autodesk Forge – View&Data
33. Autodesk Forge – View&Data
View & Data
Your
Cloud
Bucket
Viewing Services
WebGL
Viewer
File Upload
URN result
34. Workflow:
• Upload empty DWG to AWS and receive URL
• Collect user input data from a web page
• Submit URL and script to AutoCAD I/O service
• Receive processed DWG
• Submit DWG to View&Data service
• Receive URN for viewing
Autodesk Forge – Sample
38. • Cloud is a business evolution
• Scalable, ubiquitous, reliable
• Hide complexity from users
• Reduce cost of ownership and maintenance
• Forge APIs available as web services
• Bring the power of desktop apps to the cloud
• Enrich cloud solutions
Conclusion