2009 Ing. Punzenberger COPA-DATA GmbH. All rights reserved.

Transcription

1

2 2009 Ing. Punzenberger COPA-DATA GmbH All rights reserved. Distribution and/or reproduction of this document or parts thereof in any form are permitted solely with the written permission of the company COPA-DATA. The technical data contained herein has been provided solely for informational purposes and is not legally binding. Subject to change, technical or otherwise. ii

3 1. Welcome to COPA-DATA help zenon at the terminal server General Mode of operation of terminal servers Remote Desktop vs. Terminal Server The advantages The disadvantages The control system General mode of operation Required settings... 7 iii

4 If you miss any information in this help chapter or have any suggestions for additions, please feel free to contact us via If you have concrete questions relating to your project, please feel free to contact the support team via If you realize that you need additional licenses or modules, please feel free to contact the sales team via 1

5 2

6 The control system can also be used in combination with a terminal server solution. Terminal servers are available from Windows resp. Citryx. All test with the control system have been done with the Windows terminal server. Info Keep in mind that the name of the terminal client is dissolved. If you are using a firewall, make sure that corresponding ports are enabled. Terminal servers allow to start several separated shell (desktop) instances on one computer (the host computer). If a terminal client connects to the server, it own user interface is assigned to it, which only it sees. All programs started on the client run on the terminal server. Only the screen information (graphical data) is sent to the client via the network. You can imagine this like a monitor cable lengthened by the network. Only a small program runs on the client, which displays the graphical data sent from the server. No other software is running on the client. So the memory and ressources needed on the client are very low. So they are called thin clients. Another advantage of the client: The client can be realized completely idependent from the operating system, because only graphical information is displayed on it. So there are terminal server clients for Windows XP, Windows CE, Linux, Unix, etc. The only difference to remote desktop programs like PC Anywhere, VNC, Remote Desktop, etc. is the following: With remote desktop programs all connected clients always use one and the same desktop. If 3

7 e.g. one user starts a program, all see the same program, the same mouse cursor, the same keyboard input, etc. With terminal server solutions each connected station has its own desktop - an own instance. Only it sees, what happens there. Mouse actions and keyboard inputs only affect this one instance. But this also means, that a program can be started in each instance. E.g. the MS Editor can be started in each instance. The program (the EXE) then runs several times on the terminal server. Only one computer (the server) has to be maintained. Clients can use very cheap hardware/software and do not habe to be very high-performance. Clients can have different operating systems (Windows 2000/XP, Windows CE, Linux, Unix, etc.). Because of the fact, that all started programs of all instances run on one PC (the server), the following problems might occus: The server has to have sufficient computing power for all started programs. The server has to have sufficient RAM for all started programs. All interfaces have to be shared, e.g. network adapters, COM ports, parallel ports. The network load gets accordingly high, as the data of the programs as well as the graphical data for the clients have to be sent via the network. All started programs use the same file system and the same files. For Word e.g. this means, that the frames e.g. normal.dot are being written to by all started Word instances at the same time. 4

8 5

9 Since version 5.21 SP3 the zenon Runtime can also run on the terminal server. The Editor cannot run on the terminal server. Only one zenon client can run on the terminal server. A server and also a single-user system are not possible. A. Runtime Server B. Terminal Server and n-fold Runtime Client C. n Terminal Clients (only graphical display) 6

10 As the zenon Runtime is started several times as a client on the terminal server, two settings have to be defined, so that the described solution works: 1. In the zenon6.ini the following entry has to be added on the Terminal Server. On the Runtime server no settings are needed. [TERMINAL] CLIENT=1 1: The Runtime can be started several times, all settings for the terminal server operation are automatically set by the Runtime. 0: The Runtime can only be started once. Operation on the terminal server is not possible. (Default) 2. The network service (zennetsrv.exe) has to be registered as standard COM server and not as a service. For this the program has to be started with the option -regsrv from the command line. Example: C:/Program Files/COPA-DATA/zenon650/zenNetSrv.exe -regsrv separately. Since version 6.21, this is a default setting. This means you do not have to consider it 3. The transport service (zensyssrv.exe) must be registered and started as a Windows service, not as a standard EXE file. For this the program has to be started with the option -service from the command line. Example: C:/Program Files/COPA-DATA/zenon650/zenSysSrv.exe -service You can then start the service via the Windows service manager. The service will be started automatically during every computer restart. Please consider that the startup tool and also the setup program always register the transport service as a standard EXE. Therefore, you have to reregister the transport service as a Windows service after every execution of the startup tool and after every reinstallation. 4. All users must have write access to the Runtime folder. You must give full access to the Runtime folder and all subfolders to all Windows users (Everyone) in the Windows Explorer. Read more about the definition of the Runtime folder in the chapter File structure (main.chm::/12437.htm) 7