Parallel FactoryTalk Linx Gateway services

Create two FactoryTalk Linx Gateway services with the same configuration on two server computers. The client must then manage the operation to ensure data is delivered. The following table lists a couple of ways for the client to manage the interactions with the two servers.
Approach
Operation
Benefits/challenges
One server at a time
The client connects to one server. If the connection is lost, it will connect to the second server.
Benefit:
  • Only one value to manage
Challenge:
  • Slow recovery after an active server shuts down
Dual servers with only one active
The client connects to both servers. Data is requested from both servers. The data from one server is active and the other inactive. When the server that was active fails, the client activates the data items from the second server.
Benefit:
  • Only one value to manage
  • Faster recovery
Challenge:
  • Recovery delay to activate data from remaining server
Dual servers both active
The client connects to both servers. Data is requested from both servers. Both servers actively deliver data. The client may use both or choose to discard one of the values.
Benefit:
  • No recovery delay
Challenge:
  • Client must process twice as much data
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal