西門子wincc相關(guān)資料OPC UA SDK 1.00 Readme

1、OPC UA SDK Release 1.00December 1st, 2010OverviewThe OPC UA SDK is a collection of libraries and applications that facilitate the development of UA applications. The UA SDK supports 2 different development environments: .NET and C/C+. A Java version is under development and is distributed as a separ

2、ate package.Release NotesBuild 250.8This release includes the following fixes:Files created in system folders are not removed on uninstall (#1399);Uninstall fails on systems with vl.l of the SDK installed (#1428);WindowCertificateStore.Add does not handle Certificates with Private Keys (#1429);Syste

3、ms that have an older build that cannot be uninstalled can be repaired by installing this build.Build 250.7This release includes the following fixes:Handle leak in ServerBase (#1250);Incorrect StoreName constructed in CreateCertificate (#1251);Build 250.5This release includes the following fixes:Dir

4、ectory based certificate stores are now supported (#1028);The Configuration Tool now has a create certificate dialog (#1029);The Matrix class did not serialize object arrays properly (#972);Checks if a server requires IPv6 before creating a socket (#1030);Certificate Generator tool now part of the v

5、l.O distribution (#1028);This fix is required for any systems that were having problems with Windows certificate stores (usually due to security policies set by the domain controller). The Configuration Tool has a new menu item (Application | Switch to Directory Stores) which will fix an application

6、 after a failed installation by creating a new Certificate and setting the application trust list to:n%CommonApplicationData%OPC FoundationCertificateStoresUA Applications,The tool will prompt the user to select an application configuration file when this menu item is selected.Build 250.3This releas

7、e includes the following fixes:The LDS now has a separate installer (#965);A .NET UA-TCP server would stop accepting new connections (#945);The Transport URIs did not match the specification (#959);The subjectAltName in autogenerated certificates had the wrong OID (#964);The CertificateValidator was

8、 not handling the authorityKeyldentifier correctly (#958);The following are significant known issues which are fixed in vl.l:.NET threading issues cause spurious delays in UA-TCP communication (#804); requests hang rarely when clients send calls from multiple threads (#917);FindServers/GetEndpoints

9、implementations ignore EndpointUrl parameter (#862);Cannot create self-signed certificates on some systems (#918);Only the file versions have be incremented so existing installations can be upgraded by replacing the following assemblies:This build is posted as a Testing build to allow users to ident

10、ify any compatibility issues. If no issues are reported over the next 2 weeks it will be re-labeled as a Stable build. Prior to posting this build has been tested on Windows XP SP3, Vista SP1 and Windows 7.Users compiling the source with VS2008 may encounter a linker error that can be resolved with

11、this hotfix from Micros。代.Build 250.2This release corrects a problem (Mantis #859) that was preventing clients built with the .NET SDK from communicating with servers behind a NAT firewall. The assembly version has not been incremented which means the new DLLs can be used to patch existing applicati

12、ons without rebuilding. The file versions have been incremented to insure installers work correctly.Servers built with the .NET SDK may also need to be patched if clients use to access them via a NAT firewall.Build 250.1This is the first release of the UA SDK.This release of the SDK supports the rel

13、eased versions of Parts 1 through 9 of the UA Specification.Outstanding issues are reported in the OPC Foundation Mantis database.Users that have questions or problems can post questions on the OPC Foundation message board.This is stable release and patches will only be provided for important issues

14、 that do not require significant code changes. Vendors who wish to ensure that they have all available fixes and features should be using the vl.l (Beta) which will also be available on the OPC Foundation website.The Compliance Test Tool (CTT) is under development and will be tested with the vl.l SD

15、K. Vendors who wish to ensure that their products pass the CTT when it is released should plan to upgrade to the vl.l SDK.Build 250.1 fixes incorrect assembly version numbers in Build 250.0.DeliverablesThe OPC UA SDK includes the following deliverables:DeliverableDescriptionANSI C Stack DLLA redistr

16、ibutable library containing the ANSI C implementation of the UA Stack. This binary is built for x86 WIN32 systems and has a dependency on OpenSSL.NET Stack DLLA redistributable library containing the .NET implementation of the UA Stack. This binary is targeted for any platform that supports the .NET

17、 3.0 framework.ANSI Stack Headers and LibrariesThe headers and libraries required to build applications that use the ANSI C Stack. The libraries support static and dynamic linking.NET Server ToolkitA redistributable library containing a basic implementation of a UA server that can be used to develop

18、 application specific UA servers.NET Client ToolkitA redistributable library containing a basic implementation of a UA client that can be used to develop application specific UA clients.NET SDK Help filesThe MSDN style help files for the .NET stack and client/server toolkit libraries.Local Discovery

19、 ServerA redistributable .NET application which is used to discover the UA servers running on a machine. This binary is targeted for any platform that supports the .NET 3.0 framework.WDSL, Schemas and ConstantsThe WSDLs, XML Schemas and Numeric Constants defined by the UA specifications.Merge Module

20、sWindows Installer compatible Merge Modules which install the SDK deliverables.QuickstartsSimple client/server implementations which illustration specific UA features and/or profiles. Developers should start with these examples if they are using the SDK for the first time.Sample and Test Application

21、sFully featured sample applications used for testing.Source CodeThe source for stacks, the toolkits and the sample and test applications.License and Copyright InformationAll binaries and documentation files installed by this package are subject to the term of the OPC Redistributables License Version

22、 LOO.All source files are subject to one ofOPC Foundation MIT License Version LOOOPC Reciprocal Community License (RCL) Version LOOOPC Reciprocal Community Binary License (RCBL) Version 1.00The applicable license agreement is declared at the top of each source file.If a license declaration is not sp

23、ecified in a source file then the file is subject to the OPC Reciprocal Community Binary License (RCBL) Version 1.00.A more detailed overview of the different agreements can be found here.This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit.( :). Only users

24、of the ANSI C stack require OpenSSL.Build ProcessEach release of the SDK is assigned a Build Number and a Build Type. The different Build Types are described in the following table:SnapshotSnapshot builds are only minimally tested and are used to give developers quick access to new features and bug

25、fixes. There may be backward compatibility issues and some features may be broken. Developers should not migrate to a snapshot build unless they need the feature and/or bug fixes.TestingTesting builds are put through basic tests to ensure that nothing is broken but have not been tested for backward

26、compatibility. All Stable and Final builds are posted first as Testing builds which gives developers a chance to check for issues which can be corrected quickly. Any changes will be incorporated into a new revision and posted immediately. If no issues come up the last revision of a Testing build wil

27、l be re-labeled as Stable or Final. Developers are encouraged to look at Testing builds and see if there are issues. Developers should not migrate to Testing builds unless they absolutely need the functionality or are participating in the testing process.StableStable builds are put through basic tes

28、ts to ensure that nothing is broken but have not been tested for backward compatibility. Stable builds are posted to give vendors a chance to verify that it works with existing products. Vendors who have products under development should migrate to stable builds as quickly as possible. If a vendor i

29、s already distributing products they may wish to use the sample applications to test for compatibility problems.FinalFinal builds are stable builds that have been verified by one or more vendors. Patchesrequired to fix issues discovered while testing the stable build are applied but no other feature

30、s are added. Vendors who have products under development should migrate to stable builds as quickly as possible.The version number of all binaries incorporates the SDK version and the build number.InstallersThe SDK is distributed in a number of different packages which are described in the table bel

31、ow:Redistributables Setup (x86)Installs all of the merge models (prompts user to specify whether the development environment should be installed).Source Code SetupInstalls the source for .NET and ANSI C stack plus all of the test tools.AnsiC Stack Source Code SetupInstalls the source for the ANSI C

32、stack.Sample Binaries Setup (x86)Installs the binaries for the sample and test applications.The following Quickstarts are available with this version of the SDK:Alarms and Conditions Quickstart Setup (x86)Installs sample Alarms and Conditions applications.Data Access Quickstart Setup (x86)Installs s

33、ample Data Access applications.AnsiC Stack Quickstart Setup (x86)Installs sample ANSI C and C+ applications that are built with the ANSI C SDKThe following Merge Modules are available with this version of the SDK:Local Discovery Server MergeModule (x86)Installs the Local Discovery Server and the Con

34、figuration Tool.AnsiC Stack MergeModule (x86)Installs the ANSI C stack headers, libraries and the DLLs. The runtime only environment is installed by default.Setting the UA_ANSIC_SDK or UA_ALL_SDK properties will install the development environment.This module requires the OpenSSL Merge Module.OpenSS

35、L MergeModule (x86)Installs the OpenSSL headers, libraries and DLLs. The runtime only environment is installed by default.Setting the UA_OPENSSL_SDK or UA_ALL_SDK properties will install the development environment.NET Stack MergeModule (x86)Installs the UA .NET stack assemblies. The runtime only en

36、vironment is installed by default.Setting the UA_DOTNET_SDK or UA_ALL_SDK properties will install the development environment.The Installers will place shared files in the $(CommonProgramFiles)OPC FoundationUAvl.O directory.This includes all headers and libraries required to build C/C+ applications.

37、The .NET assemblies are installed in the $(ProgramFiles)Reference AssembliesOPC FoundationUAvl.O.Source files are installed in the target directory provided when the code is installed.System RequirementsAll of the installers require the .NET 3.0 SP1 runtime.The Quickstarts and Source Code require Vi

38、sual Studio 2008 with SP1; however, a Visual Studio 2005 project is available for the .NET Stack and the .NET Client/Server Toolkits.RedistributionVendors that need to redistribute the binaries for their own applications have two options:Build applications against the binaries signed by the OPC Foun

39、dation.Rebuild the binaries from source and sign them with the vendors key.In both cases vendors shall install copies of the DLLs in a location which is only used by the vendors applications. A vendor SHALL NOT install any binary distributed by the OPC Foundation in a common location such as the Sys

40、tem32 directory or the GAC. Vendors that require binaries to be installed in common locations SHALL rebuild the binaries from source and sign them. In addition, ANSI C libraries SHALL be renamed to something that identifies the vendor that created the libraries.The OPC Foundation will produce update

41、s to the SDK that incorporate critical bug fixes. These updates will only be available to corporate members. Vendors are expected to verify that these bug fixes are compatible with their applications before providing the updates to their customers. Users of UA products who are also corporate members must never attempt to upgr