FME Server Administration: Customization and Monitoring

Introduction

This guide provides administrators with options to configure FME Flow to improve performance, enhance security, and streamline data management.
 

Logging

FME Flow has extensive logging. To help get started with logging it would be please look at the series FME Flow Debugging Toolbox

System Events

FME Flow is able to publish messages about significant events related to administrative tasks as a System Event. These can then be sent to administrators through email or trigger another action in Automations.

System Email

An External SMTP Email Server can be set up as a system email server, which can be used in System Events and Password Resets.

Reset Password

Users can be given the option to automatically reset their passwords, but the user email must be set on the user account, and a system email must also be configured.

System Cleanup

System Cleanup is a feature that allows you to remove these unwanted files and free up space on your server. This can help improve the performance of FME Flow and can be critical on busy systems where logs can build up quickly.

Broadcast Messages

You can broadcast messages to users to notify them of maintenance or other changes and disruptions.

Dashboards

FME Flow's Dashboards feature allows you to create out-of-the-box or custom web pages that display information and metrics about your FME Flow workflows and resources. This can include information such as the status of running or completed workflows, metrics on resource usage, and statistics on the data being processed. For details and ideas on custom dashboards, please see Monitoring FME Flow Job Activity using the REST API.

Shared Resources 

In some cases, you might want to include a common network directory for users to easily access a network file share. You can create and manage connections to your own network resources and Amazon Web Services (AWS) S3 buckets. For more information, see Creating and Managing Resource Connections. If you choose a network resource, access is based on the Service Account running the core, engine, and web application.

Database and Web Connections

Database and Web Connections are a way to safely manage and store connections on FME Desktop and FME Flow.

• Managing Database Connections
• Troubleshooting Web Connections on FME Flow

Third-party Licensing and Workspace Dependencies

To use Esri-related formats (ArcSDE Geodb, File Geodb, Personal Geodb), Esri software must be installed and licensed on the same machine as your FME Flow Engine Service. For more information, please see Using FME Flow with Esri ArcGIS Software. 

Once FME Flow is installed, depending on the components in use within your workspaces, other provisions may be required on FME Flow. Some common examples include: 

• Python Modules
• Custom Coordinate Systems
• Packages
• Format Dependencies e.g. JDBC Drivers 
  • Note: This information is available in the ‘Quick Facts’ on the format help page, and if a dependency is missing, there should be a clear error in the translation log when it is run on FME Flow.

What's Next?

Return to the Getting Started with FME Flow Administration tutorial start page and review any resources that may have been missed. 

Review the FME Flow Troubleshooting Guide if you have encountered any issues during installation and setup. 

If you are still experiencing issues having reviewed the relevant materials, please search for your issue or post your question to the FME Community Q&A.

If you have encountered a bug or defect with FME Flow, please report a problem to Safe Software Support. For tips on creating an FME Flow Support case, see How to Create a Great FME Flow Support Case.