Configure the opc server(s), Installing processlinx, Preparing the client’s user accounts – Rockwell Automation 1757-PROCESSLINX ProcessLinx OPC Server to Server Software User Manual User Manual

Page 11

Advertising
background image

Publication 1757-UM002B-EN-P - January 2003

Setup Procedures 1-3

Configure the OPC Server(s)

Before ProcessLinx can work properly in runtime, each OPC Server must be
installed and configured correctly. Follow the installation procedure and setup
specified with the documentation for the external OPC Server. A TCP/IP
connection must also exist between the NT ProcessLogix node and any
remote node running an external OPC server for which you wish ProcessLinx
to connect with. Refer to Using DCOM OPC Servers on page 7-1 to setup
and configure remote OPC servers.

Installing ProcessLinx

Do the following to install the ProcessLinx software:

1. Insert the ProcessLinx CD.

2. Select Start

Run.

3. Enter D(CDROM drive letter):setup.exe.

4. Accept the License Agreement.

5. Follow the rest of the dialog boxes to install ProcessLinx in the default

locations.

6. To complete the installation, insert the floppy disk with the License

Activation.

7. Follow the instructions for moving the License Activation to the PC.

ProcessLinx installation is complete.

Preparing the Client’s User
Accounts

The easiest way to avoid DCOM security problems is to have the same user
account and password on all machines, DCOM security is bypassed. It is
possible however, to allow a remote OPC Client to access the PLX OPC
Server when the correct permissions are specified. This requires user and
group privileges and DCOMCFG settings to be set appropriately. This is not a
trivial undertaking and most people (including network administrators) have
no idea how to do it properly.

Most of the time OPC is set up with user accounts on the Client machine and
Server machine having the same name and password. This is not specific to
ProcessLinx. It is a Microsoft DCOM issue. OPC is written using COM so it
has inherited all the DCOM flaws.

ProcessLinx is not dependent on a specific version of ProcessLogix. It works
the same in R320 as it does in R500. Refer to your Microsoft documentation
on how to add user accounts.

Both the ProcessLogix Client and the Server must have both the MNGR and

Advertising