span8
span4
span8
span4
The FME Server product is comprised of several different components that can be configured partially through text configuration files.Since these components are based on different technologies, the syntax for their configuration files is also somewhat different.This article will cover a sample configuration file of each type you are likely to encounter, and explain the differences.Important differences to notice:
These are a custom format used by the FME Server Core and related Safe Software-created services.This includes files in the
directory, such asfmeServerConfig.txt,fmeCommonConfig.txt, and fmeEngineConfig.exe.
Basic format
DIRECTIVE=value
Path specification
FME_INCLUDE_FILE=C:/apps/FMEServer/Server/fmeCommonConfig.txt
Comments
# This text is a comment
The FME Web Application Server is Tomcat-based, and so its configuration files are standard Tomcat XML configuration files.An example is the server.xml file.
.
Basic Format
Path specification
keystorefile="C:\Program Files\FMEServer\Utilities\tomcat\.keystore" keystorepass="secretpassword" />
Comments
Java Web Application Properties
In addition to the general XML configuration files, each individual web application (fmeserver, fmerest, fmedatadownload etc.) also has an individual configuration file.These are located in
\Utilities\tomcat\webapps\
\WEB-INF\conf\propertiesFile.properties
.
Basic Format
DIRECTIVE=value
Path Specification
RESOURCE_PATH=C:/ProgramData/Safe Software/FME Server/Resources
Comments
# This text is a comment
thub.nodes.view.add-new-comment
Navigation
Related Articles
3 Machine Distributed Installation
Service log folders don't get created in a distributed setup which causes jobs to fail
FME Server: Recommended Installation Scenarios
Using IIS and ARR as a reverse proxy
ServletExec and FME Server (2012)
End Client Sessions when Tomcat Restarts
FME Server Web UI: Error 500: Can't Find Bundle For Base Name (FME Server 2015 or Previous)
Web Interface anonymous user account
FME Server Cannot Run Jobs - Underscore in Host Name
Service Properties Are Unavailable when Uploading Workspace to FME Server
© 2020 Safe Software Inc |Legal
- Anonymous
- Sign in
- Create
- New Question
- New Article
- New Idea
- Spaces
- 3D (and BIM)
- Attribute Handling
- Automations (FME Server)
- CAD
- Cloud
- Coordinate Systems
- Custom Transformers
- Database
- Dynamic Workspaces
- FME Cloud API
- FME Cloud Administration
- FME Cloud Getting Started
- FME Desktop 3rd Party Integrations
- FME Desktop Administration
- FME Desktop Administration & Configuration
- FME Desktop Development
- FME Desktop Getting Started
- FME Desktop Installation
- FME Desktop Licensing
- FME Desktop Plug-In SDK
- FME Desktop Workbench Scripting
- FME Server 3rd Party Integrations
- FME Server Administration
- FME Server Administration & Configuration
- FME Server Development
- FME Server Getting Started
- FME Server Installation
- FME Server Licensing
- Fanouts
- Ideas FME Cloud
- Ideas FME Desktop: Data Inspector
- Ideas FME Desktop: Formats & Systems
- Ideas FME Desktop: Transformers
- Ideas FME Desktop: Workbench
- Ideas FME Server
- Indoor Mapping
- KML
- Lists
- PDF
- Performance Tuning
- Point Cloud
- Published Parameters
- Raster
- Real-Time
- Running Multiple Workspaces
- Tabular
- Troubleshooting Techniques
- Vector / GIS
- Web
- Workflow Design
- XML / GML
- Zip Files
- *FME Desktop
- *FME Server
- *FME Cloud
- *Other
- Explore
- Topics
- Questions
- Articles
- Ideas
- Users
- Badges