Product specifications

Integrating OPC Servers into 800xA
464 3BDS011222-510 B
3. Add the 800xA System service account to Launch and Activation
Permissions in DCOM Security and allow Local Launch, Remote Launch,
Local Activation and Remote Activation.
If you do not want to use the 800xA System service account, follow the steps for
Third Party OPC Server Node in another Domain or without Domain.
Third Party OPC Server Node in another Domain or without Domain.
Configure the computer(s) running the third party OPC Server.
1. Create a local account, e.g. OPCuser.
2. Set Identity to This user and select OPCuser created above for the third party
OPC Server.
3. Create a local account with the same name and password as the 800xA System
service account.
4. Add the local account created in step 2 to Access Permissions in DCOM
Security. Allow both Local Access and Remote Access.
5. Add the local account created in step 2 to Launch and Activation
Permissions in DCOM Security. Allow Local Launch, Remote Launch,
Local Activation and Remote Activation.
Configure the Connectivity Server(s):
6. Create a local account with the same name and password as created in Step 3,
on the third party OPC Server node.
For Upload to work it is necessary to configure DCOM security on the computer
running the remote OPC Server. This must be done for the user(s) that should be
able to perform an upload. First you need to configure security according to
Integrating OPC Servers into 800xA on page 463.
Third Party OPC Server Node in the same Domain. Configure the computer(s)
running the third party OPC Server.
1. Add the account(s) that will be used when performing an upload to Access
Permissions in Security for the third party OPC Server. Allow both Local
Access and Remote Access.