span8
span4
span8
span4
FME Server 2018.1+ has a new system for fault tolerant configuration, for more information please see the Documentationor the Introducing the New 2018.1 Fault Tolerant Architecturearticle.
Can you tell me more about your Active/Passive Fault Tolerance configuration?
The FME Server components to consider when configuring Active/Passive fault tolerance are:
When configuring FME Server for fault tolerance, the Web Application Server, Database Repository and File Repository are separated from the FME Server Processes (Process Monitor, Core and Engines).
Web Application Server
The Web Application Server must detect failure in the FME Server Core and failover to the standby or secondary system.In other words, if a single Java Web Application Server in a cluster failed, it would be recovered instantly by the failover system and operation would continue.FME Server administrators are responsible for providing this portion of the environment, as it requires additional installation and configuration separate from FME Server fault tolerance configuration.
FME Server Core
In the Active/Passive fault tolerance environment, one FME Server is active and the other system is inactive until a failover occurs.A heartbeat between the systems monitors the health of the active system.If a failure is detected or the heartbeat is lost, a failover initiates.Once the failover occurs, the inactive system assumes ownership of jobs from the FME Server Database Repository and processing continues, allowing virtually uninterrupted access to FME Server services.
FME Server Database
The Database Repository, where FME Server stores and retrieves job information, must be configured for replication to guard against hardware failure.By default, FME Server installs a ready-to use-database repository, but when configuring for fault tolerance, a repository is typically used on a separate machine.There arethree possibilities for FME Server database repositories, Oracle, SQL Server and PostgreSQL.Each of these databases has backup and restore capabilitiy to ensure 100% uptime.Some examples of these types of environments are Oracle’s RAC, SQL Server’s AlwaysOn and PostgreSQL’s Cluster configuration.It is the FME Server administrator’s responsibility to ensure the database in use is properly configured for fault tolerance.
FME Server File System
Any flat files that are intended to be shared between the different systems in an Active/Passive configuration should be on a separate machine.它是系统管理员的责任 ensure the file shares are properly configured against hardware failures common to storage devices.
3 Machine Distributed Installation
FME Server Web UI: Error 500: Can't Find Bundle For Base Name (FME Server 2015 or Previous)
An FME Server 2018.1 Installation Scenario
Service log folders don't get created in a distributed setup which causes jobs to fail
Outputting the Log File to a Local Directory in a Distributed Environment
Jobs Remain in Queue After System Failover
Notifications, Subscriptions and Topics not Installed Correctly
Unable to Manage Engines from Web UI
© 2020 Safe Software Inc |Legal