WCCOActl in redundant

[alexey.sher]

Hello.

I have a redundant system (two servers)
There is a script which i run via script Manager (WCCOActrl).
Inside one string dpSet("TestDP.int", 123) - it does not work.
But if in settings Manager scripts to write -data "ip_server2" -event "ip_server2", then it works good.
I need the script run when there is no connection with the second server (such as reboots).
Help me to solve this problem. Thank you.

[mkoller]

Solution depends on your setup.
Normally you have a CTRL manager running on EACH of your redundant servers, then each of them will do the dpSet, and the one on the active machine is effectively really setting the value, the other value is discarded.
If your setup has only ONE ctrl manager running on a THIRD machine, then you must start this ctrl manager with the commandline option:
-connectToRedundantHosts
With this option, the ctrl manager has connection to BOTH redu servers.

[alexey.sher]

Thank you so much

[ewoenne]

Hi,

Does this mean on a normal redundant setup (ie with a control manager running on each server) connectToRedundantHosts is not required? I'm a little confused from the help...

[leoknipp]

Yes, in a normal setup running a CTRL manager with the same script on every host the option connectToRedundantHosts is not used.
This option to connect to beth servers is only used in rare cases.

As Martin Koller has written the passive Event Manager is discarding value changes.
If you want to set dp elements by the CTRL script running on the passive server you have to define those dp elementes as "forwarded" dp elements using the config entries fwdDp and/or fwdDpType. The entries are normally defined in the config.redu file for the project.
This can be necessary if a script is providing information related to only one server, e.g. collecting some status or connection information.

Best Regards
Leopold Knipp
Senior Support Specialist

[ewoenne]

Thank you very much!