Skip to main content
Solved

Express Installation vs Distributed Installation

  • July 27, 2017
  • 2 replies
  • 22 views

deanhowell
Influencer
Forum|alt.badge.img+24

Apart from being able to connect to Oracle or SQL Server, is there any major difference between the express and distributed installation for FME Server

Best answer by davideagle

Express uses all of the default components and lays them down, so database (Postgres) and web application server (TomCat) it also sets up FME Server as a system user. In the Distributed installer you have much more granular control, so you can connect to an existing Postgres instance and use an existing TomCat or swap out these components for something else, like Oracle and Weblogic... you can also define a specific user to run the service as. So plenty of subtle adjustments that make the distributed approach more flexible if you're looking at having more control over fault tolerance or say putting different components on different machines. See here for more.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

f.kemminje
Contributor
Forum|alt.badge.img+11
  • Contributor
  • 189 replies
  • July 27, 2017

No major difference


davideagle
Contributor
Forum|alt.badge.img+22
  • Contributor
  • 578 replies
  • Best Answer
  • July 27, 2017

Express uses all of the default components and lays them down, so database (Postgres) and web application server (TomCat) it also sets up FME Server as a system user. In the Distributed installer you have much more granular control, so you can connect to an existing Postgres instance and use an existing TomCat or swap out these components for something else, like Oracle and Weblogic... you can also define a specific user to run the service as. So plenty of subtle adjustments that make the distributed approach more flexible if you're looking at having more control over fault tolerance or say putting different components on different machines. See here for more.