|
|
Forward |
User authentication of client machine is required to connect OPC Server with DCOM.
In the general case (System works in work group), user authentication of client machine is completed to prepare the same user account in the both machines.
This user account will connect OPC Server and execute it after logon OPC client machine.
DCOM setting for OPC Client is not necessary in case of using OPC Custom Interface, but it is necessary that "Default Authentication Level" is set "None" or an appropriate setting of security in case of using OPC Automation Interface. And the other settings work for OPC Server machine.
In the application of Windows XP SP2 (Service Pack2), the setting of Windows firewall and the COM security is needed.
Please see here in detail.
Notice
The following contents is intended for users who integrate with TAKEBISHI OPC Server to use smoothly. TAKEBISHI doesn't guarantee the operational results about its setting way and each explanation in this site. We recommend you to verify the function carefully.
|
|
Windows Service Pack |
The following software is required to use DCOM on windows. Refer to WEB site of Microsoft about detail.
| OS |
Service Pack |
| Windows XP |
none |
| Windows 2000 |
none |
| Windows NT |
Service Pack 3 or later |
| Windows ME |
none |
| Windows 98 |
DCOM98 (DCOM98 is in OSR2) |
| Windows 95 |
DCOM95 |
|
|
How to start Component Services |
Logon with user account that have Administrator authority and execute Component Services (DCOM Setting Tool : DCOMCNFG.EXE) from start menu.
|
|
Component Services |
Because "Component Services" starts in Windows XP and Windows 2003, open the property of "My Computer". "Composition Property of DCOM" starts before Windows2000. |
|
Default Property |
Select "default property" tab and check "Enable Distributed COM on this computer". And set authentication level and impersonation level as the dialog box shows above.
# Eliminate "Default Authentication level" in OPC client machine.
|
|
OPC Server Property |
Select property of OPC Server (Example of the screen is "Takebishi MELSEC OPC Server") from "DCOM Config" tree. Before Windows2000, Select the objective OPC Server in applications tab and click "property" button and then you can set the details in each applications.
|
|
OPC Server Property - General |
Select authentication level "connect" in General tab.
|
|
OPC Server Property - Location |
Check the "execute applications on this computer" in Location tab and specify that executive node of OPC Server works on local (your own computer).
|
|
OPC Server Property - Security |
Choose "Customize" in each option button in Security tab.
|
|
OPC Server Property - Launch Permissions |
Click "Edit" button. And add "Everyone" and set "Permission" in all of the four check boxes of "Local Launch", "Remote Launch", "Local Activation", and "Remote Activation".
|
|
OPC Server Property - Access Permissions |
Click "Edit" button. And add "Everyone" and set "Permission" in "Local Access" check box and "Remote Access" check box.
|
|
OPC Server Property - Configuration Permissions |
Click "Edit" button. And confirm that six items of "Administrator", "Administrators", "CREATOR OWNER", "Power Users", "SYSTEM", and "Users" are registered. (Default Setting)
|
|
OPC Server Property - Identity |
Select "The interactive user" in "Identity" tab.
If you select "The interactive user", the screen of OPC Server is automatically displayed when connecting from OPC Client.
If you select "The launching user", user account on server node be able to run OPC Server from external node. But the screen of OPC Server is not displayed.
# When "The launching user" is selected, running instance exists on server node but the window doesn't show up.
# When "The interactive user" is selected, the window shows up on server node but you should use the same account name on server node and client node.
|
|
OPC Server Property - Endpoints |
Select "Default value of system protocols" in the endpoints tab. (Default Setting)
|
|
Sample : Accessing from OPC client node |
Confirm whether it is possible to connect OPC Server by starting OPC Client of product attachment from Client PC.
When inputting the node name to "Server Node" and clicking "Refresh List" button, list of OPC Server installed on a remote node is displayed.
Select "Takebishi.Melsec" and click "OK" button, so OPC Server starts on server node through DCOM remotely.
Client machine can access OPC Server as computer exists on local.
And this dialog shows OPC Test Client attached TAKEBISHI OPC Server.
Refer to the instructions of client software about the way to specifying of client software side.
# Please install "OPC DA Component" included in our OPC Server product CD for client computer.
It will be setup opc automation rapper and related DLL (OPCProxy.dll, OPCComn_ps.dll).
|
|
Top Page
Sample
DCOM Config
Manual/Demo
