2. Safe Harbor Statement
Our discussion may include predictions, estimates or other
information that might be considered forward-looking. While
these forward-looking statements represent our current judgment
on what the future holds, they are subject to risks and
uncertainties that could cause actual results to differ materially.
You are cautioned not to place undue reliance on these forward-
looking statements, which reflect our opinions only as of the date
of this presentation. Please keep in mind that we are not
obligating ourselves to revise or publicly release the results of
any revision to these forward- looking statements in light of new
information or future events. Throughout today’s discussion, we
will attempt to present some important factors relating to our
business that may affect our predictions.
CONNECT. TRANSFORM. AUTOMATE.
14. IFC Writing Highlights
Full support for the property and quantity sets
defined in the IFC2x3 and IFC4 specifications
CONNECT. TRANSFORM. AUTOMATE.
34. Add A Web Service
CONNECT. TRANSFORM. AUTOMATE.
35. Add A Web Service
In FME
Options Dialog
Specify How to
Connect To
Your Web
Service
FME will ship
with some
preconfigured
web services
CONNECT. TRANSFORM. AUTOMATE.
36. Add & Use A Named Connection
When running the
workspace backend will
look up the authentication
information based on the
Named Connection.
Only connection name
is stored in the
workspace.
CONNECT. TRANSFORM. AUTOMATE.
37. Update Named Connection
If connection information changes, no need to
open the workspace
No passwords in workspaces!
CONNECT. TRANSFORM. AUTOMATE.
38. FME Server Integration
When publishing the workspace to FME Server map
the named connections used in the workspace to the
appropriate Named Connections on FME Server
CONNECT. TRANSFORM. AUTOMATE.
40. File Storage Web Service Integration
Select Named Connection to indicate where the file(s) are
located
Dialogs will be written to support browsing to files or you
can type a URL
At runtime, file(s) will be downloaded from or uploaded to
specified URL
CONNECT. TRANSFORM. AUTOMATE.
67. Today - FME Server Deployment
FME
FME Server Core
License
Server
Each Engine Machine
has license file pointing
to license server.
License Server file must
be updated each time
engines changes.
Engines connect to
License Server to get
license.
Engine communicates
with Server Core to do
work
Each Engine Machine
has file pointing to
FME Server Core
Big Support Headache
Inconveniencing users!!
68. New FME Server Deployment
FME
FME Server Core
License
Server
Say Goodbye to License
Server.
At connect time Engines
managed by Server Core
Each Engine now only
knows about Server
Core.
Simpler Deployment!
More Flexibility!
69. Benefit 1 – Burst Licensing
FME Server Jobs
License Server Time!
Any number of Engines.
Change number of engines
at any time.
Demand Peak
70. Benefit 2 - FME Desktop Workgroup
FME Desktop
Author and run
spatial data
transformation tasks
FME Workgroup Hub
Share Central
Workspace Repository
FME Server Core
Only
No Engines!!!
71. Benefit 3 – Cloud Management
FME Desktop
Author and run
spatial data
transformation tasks
FME Workgroup Hub
Share Central
Workspace Repository
72.
73. FME Cloud Deployment
FME Cloud –Today
FME Server
Web Layer Queue
Database
•System
•Application
FME Engines
Everything on one instance