Remote OPC Connection for HYSYSOPCServer in WXP SP-2

Transcription

1 Remote OPC Connection for HYSYSOPCServer in WXP SP-2 1 de 8 Remote OPC Connection for HYSYSOPCServer in WXP SP-2 Introduction... 1 HYSYSOPCServer configuration for DCOM access... 2 Register the server and do not unregister any more... 2 Change the name in the windows registry from the GUID number to HYSYSOPCServer... 2 Testing With Windows Firewall Deactivated... 3 Configure DCOM... 3 Download an utility to check the status of the Client and Server machines... 5 Checking the HYSYSOPCServer Application... 5 Inspecting the Application with the OCPSecurity Analyzer in the Server PC... 5 Installing an OPCClient for remote connection Testing the remote connection... 7 Testing With the Windows FireWall Activated... 7 First Test. OPCServer Windows Firewall Activated. OPCClient FireWall Deactivated... 7 Second Test. OPCServer Windows Firewall and OPCClient Activated... 7 W XP and users in a workgroup... 7 Introduction HYSYSOPCServer should run in the same computer as the HYSYS application, however, OPCClient connections can be made from other computers to HYSYS via HYSYSOPCserver using DCOM. There are some issues about remote connection in Windows. Windows For this old windows the support of DCOM connections where not supplied, hwever there are a distributable Microsoft kit that should be installed in those computers to get DCOM support (APRXDIST.ZIP) Windows 2000, NT This is the most succesfull installations for OPC Connections. This was the current O.S. when OPC specifications came true. As a result, this is the most easy installation. Windows XP, SP2 In windows XP service pack 2 Microsoft did lot of changes on the windows security package and add a firewall. Because of this all DCOM configuations that before were easy becomes more difficult but not impossible. Users not in a domain, see the specific chapter in this document. There is an OPCFoundation document that describes theconfigurations required to get a connection. It has to be follow up. In the following text there are instructions to get a most simple OPCConnection in remote from a client to a Server machine. We are going to start from deactivation of Windows Firewall because with the SP2 there are many difficulties. When this configuration works for you, you may follow OPCFoundation document that 2007 SimCAE 1

2 Remote OPC Connection for HYSYSOPCServer in WXP SP-2 2 de 8 describes the steps with the FireWall activated. HYSYSOPCServer configuration for DCOM access Register the server and do not unregister any more Everytime the application stars it looks into the HYSYSOPCServer.INI file for the line Registry, if it is ON, then the Server will selfregister, if it is OFF, it will not. Also, when the server is shutting down, it will look for the UnRegistry parameter and if it is ON, it will unregister the server. Because we do have to make modifications to DCOM configuration, we should deactivate the unregistry and do just once the registry operation. So, follow the following steps: 1.- Set Registry = ON and Unregistry= OFF in HYSYSOPCServer.INI file 2.- Run the OPCServer 3.- Shut down the server closing the aplication Maintain for the future this configuration. Change the name in the windows registry from the GUID number to HYSYSOPCServer HYSYSOPCServer is the name registered by his GUID in windows registry, therefore for the OPCENUM utility it will be difficult to identify. So the first thing we should do is change in the register the name of the application back to HYSYSOPCServer. The procedure is as follow: Run the Windows Registry Editor Application, Start RUN REGEDIT.EXE Look for MyPC\HKEY_CLASSES_ROOT\AppID\{EF DB14-11d4-BA6D-0010B56353AE} In Default double click and you have to write HYSYSOPCServer as the name Click right mouse button and add a new string entry and write RunAs. Add Interactive User as value of the entry 2007 SimCAE 2

3 Remote OPC Connection for HYSYSOPCServer in WXP SP-2 3 de 8 Testing With Windows Firewall Deactivated Deactivate Windows Firewall (in both machine) to make sure the Server is visible and can be started from a remote machine. Configure DCOM Run the DCOM Application, Start RUN DCOMCNFG.EXE 2007 SimCAE 3

4 Remote OPC Connection for HYSYSOPCServer in WXP SP-2 4 de 8 Edit Limits for Access and Limits for Launch and Activation For the ANONYMOUS user check the remote box to allow access For the EVERYONE user grant allow all permissions both in launch and Activation and for Access Edit Default Permissions for Access and default Permissions for Launch and Activation. For the EVERYONE user grant allow all permissions both in launch and Activation and for Access For the ANONYMOUS user check the remote box to allow access Allow DCOM in this computer 2007 SimCAE 4

5 Remote OPC Connection for HYSYSOPCServer in WXP SP-2 5 de 8 Check that OPCENUM.EXE application is correctly configured in the Server machine Set the authentication level to NONE Download an utility to check the status of the Client and Server machines One good testing free utility is OPC Security Analyzer from Advosol. You may download it from Install the application in the server and in the client machine Checking the HYSYSOPCServer Application Run HYSYSOPCServer Application, select a simulation, set the integrator and activate frequency updates Inspecting the Application with the OCPSecurity Analyzer in the Server PC Run the OCPSecurity Analyzer application pressing the buttoms 2007 SimCAE 5

6 Remote OPC Connection for HYSYSOPCServer in WXP SP-2 6 de 8 Browse Network Browse OPCServers Select HYSYSOPCServer and Connect DiagnoseServerAccess CreateGroupwithCallBack SelectItemsAndShowData As a result in the main screen you can see the following There is also the possibility of save the text or copy to the ClipBoard and you may send it by to us. If by any reason you cannot see the items probably automatically the application has created another instance of the server and because it is hidden and with no simulation connected there is no way to see any items on it. You can see how many instances are looking to the windows Task Administrator under processes. If there is more than one instance of HYSYSOPCServer, terminate the process with the lowest memory allocation (probably it will be the one with no hysys application connected). Disconnect OPCSecurity application for now 2007 SimCAE 6

7 Remote OPC Connection for HYSYSOPCServer in WXP SP-2 7 de 8 Installing an OPCClient for remote connection. You may use the OCPSecurity application or you may download a free one from the web. Do not use the sample OPCClient sent with HYSYSOPCServer because it is used only or LOCAL access. Some OPCClients are: Testing the remote connection Run the server of your choice. If the settings are OK you should be able to connect and see the OPCItems of the remote HYSYSOPCServer. Testing With the Windows FireWall Activated Download and follow the OCPFoundation document You may use the OCPSecurity application also to follow and test the connections. Remember to follow including: Page 3 Select exception for OPCENUM application in the firewall for the Server Select exception for HYSYSOPCServer application in the firewall for the Server Select exception for any OPCCLient you want to use, like OPCDataSpy or OPCSecurityAnalyer Page 9 Maintain the access permissions to Default for HYSYSOPCServer application. First Test. OPCServer Windows Firewall Activated. OPCClient FireWall Deactivated Do the connection with the Windows firewall deactivated in the server to make sure we can isolate any communication problem. Second Test. OPCServer Windows Firewall and OPCClient Activated This is the final step. If everything is OK, now it is completelly finished. W XP and users in a workgroup This text is extracted from topic forum OPCFoundation If the XP machines are in a workgroup there are more steps to make it work. First, like windows 2000, you match the user names and passwords on each machine, but on XP the passwords must not be left blank or set to "admin". The final step is to alter the default security settings for local accounts: Click on Start/Control Panel/Administrative Tools and open the Local Security Settings window. Expand the tree view and select Security Options in the left hand pane. In the right hand pane, scroll down and select Network Access: Sharing 2007 SimCAE 7

8 Remote OPC Connection for HYSYSOPCServer in WXP SP-2 8 de 8 and security settings for local accounts. Right-mouse click and select Properties. Select Classic - local users authenticate as themselves. The default installation for XP forces remote users to authenicate as Guest. This means that DCOM clients cannot connect to a server running on an XP machine unless the Guest account is enabled and has enough rights to launch the server. You can adjust the settings from the control panel: Find the following: Administrative Tools Local Security Policy Local Policies Security Options Network access: Sharing and security model for local accounts Change this setting to: "Classic - users authenicate as themselves" SimCAE 8