Multiplexing Proxy in redundant and distributed systems

[NikolayLevchenko]

Hi all,

I'm just trying to clarify things in my head...

We have quite a complicated set-up with 3 projects, each one is 2x2 setup. This worked ok in old version (direct comms) but since we are now in version 3.14 we need to go via Multiplexing Proxy.

Help file is somewhat useful for simple examples. My understanding is I am supposed to have smth like this on a server:

------------------------------
[proxy]
proxyPort = [proxyPort]

#Setting up local proxy
server = "hostname:[dataPort]"
server = "hostname:[eventPort]"
------------------------------

And then smth like this on any UI:
------------------------------
event = "hostname:[eventPort]"
data = "hostname:[dataPort]"

mxProxy = "hostname hostname:[proxyPort]"
------------------------------

This way the UI will go to a server via [ProxyPort] and then that proxy will redirect messages to server's [EventPort] and [DataPort]. So far so good.

But then I throw in extra complexity of distributed systems, redundancy, etc. Which means I have in my config file things like (in relevant section):
splitPort = [splitPort]
reduPort =[reduPort]
distPort = [distPort]

Does that mean that all these port have to also be added to the [proxy] section on the server like:
[proxy]
proxyPort = [proxyPort]

#Setting up local proxy
server = "hostname:[dataPort]"
server = "hostname:[eventPort]"
server = "hostname:[splitPort]"
server = "hostname:[reduPort]"
server = "hostname:[distPort]"


I've been trying different combinations and so far found that redundancy and split seem to work even without them being defined under [proxy] section (I have no idea why?). But distributed connections seem top need the definition in [proxy] section.

PS: All machines have firewalls enabled and only WCCILproxy is allowed incoming connection, outgoing connections are not blocked.

[leoknipp]

In a standard setup (Proxy manager on the same machine like the WinCC OA project) the entries are not needed.
During startup the config file is read and the entries from the file (data = ..., event = ..., ...) are used to collect the information for the Proxy manager and the proxy connections.

When using a non standard project setup, e.g. if the Proxy manager is not running on the same host like the WinCC OA project, you have to configure which Proxy manager is used for which project.

When activating the Proxy manager in an already running redundant and/or distributed system you just have to add the Proxy manager to the list of managers. In the config file you have to ensure that the following entry is not set. Otherwise proxy communication is disabled.
mxProxy = "none"

Best Regards
Leopold Knipp
Senior Support Specialist

[NikolayLevchenko]

Hi Leopold, thanks for your help.
I think I made some progress yesterday but I have one more question for now.

What is the best way for me now to see that all comms go through proxy (what connections are established) and nothing talks directly manager-to-manager? Any debugging tools I can use for that?

[leoknipp]

With the debug flag "-report dispatch" you can get the information which connections are established.
This debug flag can be used for the Proxy manager and also other WinCC OA managers.

Best Regards
Leopold Knipp
Senior Support Specialist

[NikolayLevchenko]

Thanks, I'll give it a go