Integrating Forge Data Management API with other storage providers, with Augusto Goncalves

1. © Autodesk, Inc. 2017
Integrating Forge Data Management API with
Other Storage Providers
Augusto Goncalves
Forge Developer Advocate at Autodesk
November, 2017

2. © Autodesk, Inc. 2017
Class Summary
Data is spread over different providers, so you often need to around to take advantage of each web
service.
Using the Forge Data Management API you can access the storage structure, download and
upload files from A360 Team, BIM 360 Docs and Fusion Team.
And this allows integration with other providers using apps and programming.
This class will cover the basics to create your own storage provider integration and show samples
with Box, Google Drive and Dropbox.

3. © Autodesk, Inc. 2017© Autodesk, Inc. 2017
Key Learning Objectives
At the end of this class you’ll be able to:
 Understand how files are stored with Forge
 Learn steps to download, upload, and interact with files via the Data Management API Learn
about integration with other web-services providers
 Review storage providers’ common practices (Box, Google Drive, Dropbox)
 Learn how to transfer files according to provider rules

4. © Autodesk, Inc. 2017© Autodesk, Inc. 2017
Forge Data Structure

5. © Autodesk, Inc. 2017
Overview
• User data, needs 3-legged token
•
Hubs, Projects, Folders, Items (and versions)
Abstraction on top of OSS
•
Access to:
BIM 360 Team & Docs
Collaboration for Revit
Fusion 360
OSS (app bucket)

6. © Autodesk, Inc. 2017
Overview
API endpoints
Projects, Data & OSS endpoints, here are a few (of many):
/projects/
 Hubs /project/v1/hubs
 Projects /project/v1/hubs/:hub_id/projects
/data/
 Folders /data/v1/projects/:project_id/folders/:folder_id/contents
 Items /data/v1/projects/:project_id/items/:item_id
 Version /data/v1/projects/:project_id/versions/:version_id
/oss/
 Buckets /oss/v2/buckets (POST to create, GET to list)
 Upload /oss/v2/buckets/:bucketKey/objects/:objectName

7. © Autodesk, Inc. 2017
 Hubs
 Enterprise (shared with me): hubs:autodesk.core:Hub
 Personal: hubs:autodesk.a360:PersonalHub
 BIM 360 Docs account: hubs:autodesk.bim360:Account
 Projects
 Other projects: projects:autodesk.core:Project
 BIM 360 Docs Projects: projects:autodesk.bim360:Project
 Items
 Folders folders:autodesk.core:Folder or folders:autodesk.bim360:Folder
 Files items:autodesk.core:File or items:autodesk.bim360:File
 Others items:autodesk.bim360:Document
items:autodesk.bim360:ReviewDocument
BIM 360: Listing files
About the attributes.extension.type

8. © Autodesk, Inc. 2017
 Tutorial: https://developer.autodesk.com/en/docs/data/v2/tutorials/upload-
file/
 POST projects/:project_id/items
Creates a new item (and first version)
 data.attribute.extension.type
"items:autodesk.core:File" : "items:autodesk.bim360:File"
 included[0].attribute.extension.type
"versions:autodesk.core:File" : "versions:autodesk.bim360:File"
 POST projects/:project_id/versions
Creates a new version for an item
 data.attribute.extension.type
"versions:autodesk.core:File" : "versions:autodesk.bim360:File"
BIM 360: Upload a file

9. © Autodesk, Inc. 2017
 BIM 360 Team
 POST projects/:project_id/folders
3-legged
2-legged
 BIM 360 Docs
 POST projects/:project_id/commands
3-legged
2-legged only with x-user-id (as of August/2017)
BIM 360: Create Folder

10. © Autodesk, Inc. 2017© Autodesk, Inc. 2017
Transferring Files

11. © Autodesk, Inc. 2017
After all, what is a transfer between servers?
• Servers don’t know each other > need a server in the middle that knows both
Source Destination
Action

12. © Autodesk, Inc. 2017
Why AWS Lambda?
Benefits of ”server-less” approach
Scalable
Automatically scales your application by running code in response to each trigger
Multiple transfers
Code runs in parallel and processes each trigger individually, scaling precisely with the size of the
workload
On-demand
Runs your code without requiring you to provision servers
Cheaper (for high demanding tasks)
Pay for only the compute time you consume, avoid a big server idle most of the time

13. © Autodesk, Inc. 2017© Autodesk, Inc. 2017
Webapp
1. User selects a file
2. Get the href of the file
Transfer from Autodesk to Storage
3. Check destination folder
4. Create file ”place holder”
5. Prepare source and
destination URLs with
Authorization header
6. Send ”job” to AWS Lambda
7. Lambda download from source,
upload to destination
8. Send ”job complete” notification

14. © Autodesk, Inc. 2017© Autodesk, Inc. 2017
Webapp
1. User selects a file
2. Get the href of the file
Transfer from Storage to Autodesk
3. Check destination folder
4. Create file ”place
holder” (i.e. storage
location)
5. Prepare source and
destination URLs with
Authorization header
6. Send ”job” to AWS Lambda
7. Lambda download from source,
upload to destination
8. Send ”job complete” notification9. Create Version on Autodesk

15. © Autodesk, Inc. 2017© Autodesk, Inc. 2017
What’s next?

16. © Autodesk, Inc. 2017© Autodesk, Inc. 2017
Sample apps
Source: github.com/Autodesk-Forge/bim360appstore-data.management-nodejs-transfer.storage
box
dropbox
egnyte
google
onedrive
bim360 .autodesk.io (BIM 360 AppStore)

17. © Autodesk, Inc. 2017© Autodesk, Inc. 2017
Further reading
• Developer Portal – Documentation
developer.autodesk.com
• Forge Blog
forge.autodesk.com/blog
• Samples at Github
github.com/Autodesk-Forge

18. © Autodesk, Inc. 2017
Thank you!
augusto.goncalves@autodesk.com
augustomaia

19. Autodesk and the Autodesk logo are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders.
Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document.
© 2017 Autodesk. All rights reserved.