Appendix Test all settings in a laboratory environment before changing the production machine This documentation deals with COM components that should comunicate with each other. There are tree different types of COM -Servers known, depending on their operational environment. INPROG- Server The COM-Server runs in the memory area of the Client, the Server is a DLL and runs local on the same machine and in the same process.
LOCAL-Server The COM Server runs in it's own memory area, the Server is a EXE and runs local on the same machine, but in it's own process REMOTE-Server The COM Server runs in it's own memory area, the Server is a EXE and runs remotely on a different machine and (of course) in it's own process as the Client The communication between Client and Server process followes the rules of COM. Whenever the Client is located on one machine and the Server on an other, DCOM (Distributed COM) comes into place. The function calls between Client and Server process are checked for correct security by the operating system.
The security settings for DCOM have NOTHING to do with sharing folders between two machines or network shares across a network. When it comes to DCOM-Security we talk about "inter process communication", in other words: the right to start or access a certain component. To keep configuration simple it is assumed that two machines have the same operating system installed, are both in the same Workgroup and have the same user accounts (same person/PWD actually logged on). On the Server Machine an OPC Server is located and on the Client Machine an OPC Client was installed.
8.2.1 Prerequisites 8.2.1.1 Operating System Depending on the operating system of the OPC-Server and OPC-Client computer, the user accounts which are used for communication will be identified differently. TS6120 66 Version: 1.2.0