Skip to main content
Question

FME Configuration

  • November 13, 2012
  • 3 replies
  • 13 views

Dear Team,

 

 

I have installed the FME server 2012 on 2 servers.

 

 

Now I would like to configure FME core server failure. I did the config changes in process monitor.txt but didn't work.

 

 

Could you please help me out with this /

 

 

Thanks a bunch in advance
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.

3 replies

Forum|alt.badge.img
  • November 14, 2012
Hello,

 

 

Could this be what you're looking for:

 

http://fmepedia.safe.com/articles/How_To/Changing-the-Hostname-and-Web-Server-Port 

Forum|alt.badge.img
  • November 14, 2012
Sorry, the answer wasn't for this post and there is no way to delete it as far as I can see...

davideagle
Contributor
Forum|alt.badge.img+22
  • Contributor
  • November 15, 2012
Hi Gnan - 

 

 

Important parts of processMonitorConfig.txt file for you are:

 

 

 

FAILOVER_SERVER_NAMES=red green blue

 

 

I suggest you list your cores like this (order is important):

 

 

FAILOVER_SERVER_NAMES=core2 core1

 

 

 

Then register all your engines with core1 using the REGISTER_SOCKET parameter here:   # Start FME Engine 1

 

CMDFMEEngine_Jabba="C:/_FME/FME_Server_2012_x86_SP3//Server/fme/FMEEngine.exe" REGISTER_SOCKET core1 7070 "C:/_FME/FME_Server_2012_x86_SP3//Server/fmeEngineConfig_Engine1.txt" -FME_INSTANCE_NAME Engine1|log|attempts=5

 

WAITFMEEngine_Engine1=0

 

 

 

etc… where you need to start as many engines as you have licensed and register all engines with the primary core initially.

 

 

 

When started all FME Engines should register with core1 initially and the engines should be configured to failover to the backup Core (core2) first and then followed by the active core once the primary has been brought back up and the backup is killed off.