Page 1 of 1
Working with pmon.ctl
Posted: Wed Mar 29, 2017 8:28 am
by tobias_raab
Hi everybody,
I like to start / stop managers using pmon.ctl or just using the tcpOpen / Write / Read commands but I can't make it work.
Using the pmon.ctl functions always results in error messages like variable "gTcpFileDescriptor" not defined or "gTcpFifo", etc..
Am I missing a libary/script containing those globals or am i doing something utterly wrong?
If i do it manually with tcpOpen / write then just nothing happens at all.
Thank you for your help!
Re: Working with pmon.ctl
Posted: Wed Mar 29, 2017 8:38 am
by eivanovic
Hi,
Try to define two variables in your script, although they are not used:
int gTcpFileDescriptor,gTcpFileDescriptor2;
Cheers,
Emanuel
Re: Working with pmon.ctl
Posted: Wed Mar 29, 2017 8:43 am
by eivanovic
sorry... and also:
string gTcpFifo
BR
Emanuel
Re: Working with pmon.ctl
Posted: Wed Mar 29, 2017 8:46 am
by tobias_raab
That was easy
Thank you very much.
Re: Working with pmon.ctl
Posted: Thu Jul 06, 2017 2:42 pm
by chris@blue-catalyst.co.uk
Is it possible to connect to a remote pmon using tcpOpen/tcpWrite in v3.14 with the multiplexing proxy running?
We experience the tcpOpen command timing out when it attempts to connect to the pmon on the remote machine.
Re: Working with pmon.ctl
Posted: Thu Jul 06, 2017 3:30 pm
by leoknipp
The Multiplexing Proxy is used for the encryption of TCP messages between WinCC OA managers, e.g. for a remote UI connected to the Data and Event Manager.
The process monitor WCCILpmon is not using the encryption via the Proxy manager.
Due to security reasons in standard configuration accessing the process monitor from a remote machine is not possible.
You have to enable the access from remote machines before you can communicate with the process monitor.
Information can be found at the following thread
https://portal.etm.at/index.php?option= ... =1598#1645
Best Regards
Leopold Knipp
Senior Support Specialist