Vijeo Citect OPC Server

Page 1 of 1

Using Vijeo Citect > Using OPC Server DA2.0 > Vijeo Citect OPC Server

Vijeo Citect OPC Server

When Vijeo Citect is used to monitor and control a plant, data from PLCs is collected and displayed in the Vijeo Citect runtime environment. OPC Clients can access device and tag information from Vijeo Citect through the OPC interface to the OPC Server, which in turn interacts with the CtAPI interface to the Vijeo Citect Runtime, as shown here:

The Vijeo Citect OPC Server can be invoked from an OPC Client on the same machine or on a different machine. When connecting to an OPC Server running on the same machine as the client, use the Citect.OPC connection option. When connecting to an OPC Server running on a remote machine, use the Citect.OPCRemote option. The OPC Server starts automatically when you start the Vijeo Citect runtime environment and does not require configuring.

mk:@MSITStore:C:\Program%20Files\Schneider%20Electric\Vijeo%20Citect%207.20\Bin\CitectSCADA.chm::/CitectSCADAVijeo_Cit... 8/23/2011

Windows Vista and Windows XP SP2

Page 1 of 3

Using Vijeo Citect > Using OPC Server DA2.0 > Configuring Remote Access to the OPC Server > Windows Vista and Windows XP SP2

Windows Vista and Windows XP SP2 This section describes how to configure the OPC Server on Windows Vista and Windows XP Service Pack 2. Note: After configuring your OPC Server, you need to restart the server so that your settings can take effect. To configure the OPC Server: 1. In Windows Control Panel, double-click Security Center, and then click Windows Firewall. 2. Select the Exceptions tab, and then click Add Program. 3. Locate the OPC Servers and clients you want to add as exceptions. You need to add the Microsoft Management Console (used by the DCOM configuration utility, below) and the OPC utility OPCEnum.exe in the Windows/System32 folder. You might have to Browse for other executables installed on the computer to add them as exceptions. Please be aware that only .exe files are added to the exceptions list. For in-process OPC Servers and clients (DLLs and OCXs) you need to add the .exe applications that call them to the list instead. 4. Click OK to save your exceptions. You need to now add TCP port 135 to initiate DCOM communications and allow incoming echo requests. 5. From the Windows Firewall Exceptions tab, click Add Port. 6. In the Name text box type DCOM. 7. In the Port number text box type 135 and select the TCP option. 8. Click OK to save your changes. You have now defined your exceptions, so you can restart your firewall. You are now ready to configure DCOM for your launch, activation, and access permissions. 9. Choose Start | Run. Type dcomcnfg and click OK. The Component Services dialog will appear. 10. In the tree pane, locate and select Computers under Component Services. 11. Right-click My Computer in the pane on the right, and choose Properties from the context menu. 12. Select the Default Properties tab. Make sure the settings are adjusted as follows:
Property Setting

mk:@MSITStore:C:\Program%20Files\Schneider%20Electric\Vijeo%20Citect%207.20\Bin\CitectSCADA.chm::/Windows_XP_SP2.html

8/23/2011

Windows Vista and Windows XP SP2

Page 2 of 3

Enable Distributed COM on this computer Enable COM Internet Services on this computer Default Distributed COM Communication Properties Default Authentication Level Default Impersonation Level Provide additional security for reference tracking

selected not selected

Connect Identify not selected

Click Apply to save your changes. For some OPC servers, setting the Default Authentication Level to "Connect" does not work. If this is the case, try setting this property to "None".
Note:

13. You need to then edit the access permissions. Select the COM Security tab, and click Edit Limits in the Access Permissions section. 14. Use the Access Permission dialog to select Anonymous Logon, and then check Allow for the Remote Access option. This is needed for OPCEnum.exe to function correctly, and for any OPC Servers and clients that set their DCOM authentication level to None in order to allow anonymous connections. If you don't use OPCEnum.exe, you might not need to enable remote access for anonymous users. 15. Click Apply to save your changes. You need to then edit the launch and activation permissions. 16. Select Edit Limits in the Launch and Activation Permissions section of the Default COM Security tab. In the Group or user names list, select Everyone then select every check box in the Allow column. 17. Click OK to save your changes. Finally, you're ready to edit the default permissions for Access and Launch for each user (or group) that participates in OPC communication (for example, "OPC Users"). 18. In the Access Permissions section of the COM Security tab, click Edit Default. Select the necessary users/groups and allow Local Access and Remote Access. Click OK to save your changes. 19. In the Launch and Activation Permissions section of the COM Security tab, click Edit Default. Select the necessary users/groups and allow

mk:@MSITStore:C:\Program%20Files\Schneider%20Electric\Vijeo%20Citect%207.20\Bin\CitectSCADA.chm::/Windows_XP_SP2.html

8/23/2011

Windows Vista and Windows XP SP2

Page 3 of 3

Local Access and Remote Access. Click OK to save your changes. You have now configured your OPC Server. Note: You need to restart this machine so that your settings can take effect. You are now ready to configure your OPC Client.

mk:@MSITStore:C:\Program%20Files\Schneider%20Electric\Vijeo%20Citect%207.20\Bin\CitectSCADA.chm::/Windows_XP_SP2.html

8/23/2011