DownloadFile by XZX8QW

VIEWS: 6 PAGES: 7

									                                         OPC UA SDK Release 1.01

                                              October 8, 2009

Overview

The 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 separate package.

Build 305 Release Notes

This is a Beta (Development) Build for the UA SDK v1.1.

The major changes include:

The COM DA Proxy and COM DA Wrapper have been tested at the Interoperability Workshop and a
number of fixes have been incorporated.

Some new Quickstarts have been added including:
      An InformationModel Quickstart that implements the Boiler model from the DevCons.
      A SimpleEvent Quickstart that demonstrates the use of vendor defined events.

The Quickstarts are now distributed in a single package called "Quickstarts Source Code" and they
include pre-built executables that can be run immediately.

The Mantis issues that have been fixed in this build can be viewed by setting the "Fixed in Build"
property set to "1.01.305.0"

Build 303 Release Notes

This is a Beta (Development) Build for the UA SDK v1.1.
Build 303.1 adds the ability to create COM proxies by manually entering the URL.

The major changes include:

The COM DA Proxy now passes the DA2.05 and DA3.0 Compliance Tests

Fixed issues affecting communication across firewalls including:
         Added an AlternateBaseAddresses element to the Server configuration;
         Updated the clients to pass the EndpointUrl to the server;
         Added logic in the client to fix potentially incorrect URLs returned by a Server;

Reduced the thread overhead in the server by moving to an asynchronous model.

The Mantis issues that have been fixed in this build can be viewed by setting the "Fixed in Build"
property set to "1.01.303.0"

Build 301 Release Notes

This is a Beta (Development) Build for the UA SDK v1.1.

The major changes include:

The COM DA Quickstart which packages the:
      UA COM Proxy Server with support for DA 2.05a/3.0;
      A NodeManager which wraps COM DA 2.05a servers;
      Managed C++ COM DA client and server samples;

A COM Interop Merge Module which installs the bits used in the Quickstart.

Project directory reorganizations and renaming including:
        UA Configuration Library moved to the Source\Common directory;
        ModelDesigner renamed to ModelCompiler;
        OPC COM DLL Host renamed to UA COM Proxy Server;
        OPC RCWs merged into the COM Interop Library;

A significant number of ANSI C stack internal bug fixes.

The Mantis issues that have been fixed in this build can be viewed by setting the "Fixed in Build"
property set to "1.01.301.0"

Build 300 Release Notes

Note that v1.0 and v1.1 depend on shared files in the "CommonProgramFiles" and
"CommonApplicationData" directories which are upgraded to v1.1 during installation.

All bugs reported on v1.0 are fixed first in v1.1. Users of v1.0 that need particular bug fixes can upgrade
to v1.1, apply the patch to their own code base and/or send a request for a v1.0 patch to the OPC
Foundation.

This release of the SDK supports the released 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.

The Compliance Test Tool (CTT) is under development and will be tested with the v1.1 SDK. Vendors
who wish to ensure that their products pass the CTT when it is released should plan to upgrade to the
v1.1 SDK.


Deliverables
The OPC UA SDK includes the following deliverables:

 Deliverable                             Description
 ANSI C Stack DLL                        A redistributable 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 DLL                          A redistributable library containing the .NET implementation of
                                         the UA Stack. This binary is targeted for any platform that
                                         supports the .NET 3.0 framework.
 ANSI Stack Headers and Libraries        The headers and libraries required to build applications that use
                                         the ANSI C Stack. The libraries support static and dynamic linking.
 .NET Server Toolkit                     A redistributable library containing a basic implementation of a
                                         UA server that can be used to develop application specific UA
                                         servers.
 .NET Client Toolkit                     A redistributable library containing a basic implementation of a
                                         UA client that can be used to develop application specific UA
                                         clients.
 .NET SDK Help files                     The MSDN style help files for the .NET stack and client/server
                                         toolkit libraries.
 Local Discovery Server                  A 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 Constants             The WSDLs, XML Schemas and Numeric Constants defined by the
                                         UA specifications.
 Merge Modules                           Windows Installer compatible Merge Modules which install the
                                         SDK deliverables.
 Quickstarts                             Simple 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 Applications            Fully featured sample applications used for testing.
 Source Code                             The source for stacks, the toolkits and the sample and test
                                         applications.

License and Copyright Information

All binaries and documentation files installed by this package are subject to the term of the "OPC
Redistributables License Version 1.00".
 All source files are subject to one of
OPC Foundation MIT License Version 1.00
OPC Reciprocal Community License ("RCL") Version 1.00
OPC Reciprocal Community Binary License ("RCBL") Version 1.00
The applicable license agreement is declared at the top of each source file.
If a license declaration is not specified 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.
(http://www.openssl.org/). Only users of the ANSI C stack require OpenSSL.
Build Process
Each release of the SDK is assigned a Build Number and a Build Type. The different Build Types are
described in the following table:

 Snapshot    Snapshot builds are only minimally tested and are used to give developers quick access to
             new features and bug 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.
 Testing     Testing builds are put through basic tests to ensure that nothing is broken but have not
             been tested for backward 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 will 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.
 Stable      Stable builds are put through basic tests 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 is already
             distributing products they may wish to use the sample applications to test for compatibility
             problems.
 Final       Final builds are stable builds that have been verified by one or more vendors. Patches
             required to fix issues discovered while testing the stable build are applied but no other
             features 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.
Installers
The SDK is distributed in a number of different packages which are described in the table below:

 Redistributables Setup (x86)                     Installs all of the merge models (prompts user to
                                                  specify whether the development environment should
                                                  be installed).
 Sample Binaries Setup (x86)                      Installs the binaries for the sample and test
                                                  applications.
 Source Code Setup                                Installs the source for .NET and ANSI C stack plus all of
                                                  the test tools.

 AnsiC Stack Source Code Setup                    Installs the source for the ANSI C stack and the ANSI C
                                                  Quickstarts

The following Quickstarts are available with this version of the SDK:
 AnsiC Stack Quickstart Setup (x86)                Installs sample ANSI C and C++ applications that are
                                                   built with the ANSI C SDK

 Quickstart Source Code Setup (x86)                Installs all of the .NET Quickstarts including:
                                                            Data Access
                                                            Alarms and Conditions
                                                            COM Data Access Interoperability
                                                            Simple Events
                                                            Information Model (Boiler)

The following Merge Modules are available with this version of the SDK:

 Local Discovery Server MergeModule (x86)          Installs the Local Discovery Server and the
                                                   Configuration 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.

 OpenSSL 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
                                                   environment is installed by default.
                                                   Setting the UA_DOTNET_SDK or UA_ALL_SDK
                                                   properties will install the development environment.

 COM Interop MergeModule (x86)                     Installs the UA COM Proxy Server which allows COM
                                                   clients to connect to UA servers and the UA COM
                                                   Interop Library which allows UA Servers to wrap COM
                                                   servers.

The Installers will place shared files in the $(CommonProgramFiles)\OPC Foundation\UA\v1.0 directory.

This includes all headers and libraries required to build C/C++ applications.

The .NET assemblies are installed in the $(ProgramFiles)\Reference Assemblies\OPC
Foundation\UA\v1.0.

Source files are installed in the target directory provided when the code is installed.

System Requirements
All of the installers require the .NET 3.0 SP1 runtime.
The Quickstarts and Source Code require Visual Studio 2008 with SP1; however, a Visual Studio 2005
project is available for the .NET Stack and the .NET Client/Server Toolkits.
Redistribution

Vendors that need to redistribute the binaries for their own applications have two options:

    1) Build applications against the binaries signed by the OPC Foundation.

    2) Rebuild the binaries from source and sign them with the vendor’s key.

In both cases vendors shall install copies of the DLLs in a location which is only used by the vendor’s
applications. A vendor SHALL NOT install any binary distributed by the OPC Foundation in a common
location such as the System32 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 updates 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 upgrade applications with DLLs that
they have acquired directly from the OPC Foundation.

Testing

The testing procedures are designed to verify correct behavior and uncover as many problems as
possible are described in the UA SDK 1.00 Testing Report; however, these procedures do NOT cover
every possible path through the code.

Note that the UA SDK is a collection of software libraries which are not intended for use as standalone
applications. Developers who create software that uses the SDK are responsible for fully testing their
applications to ensure that the interaction between their software and the SDK has not uncovered bugs
which could not be found with the test procedures described in this document.

Contributors

The OPC Foundation would like to thank the volunteers who, as members of the Early Adopters Working
Group, contributed to the development of this SDK.

 Christian Zugfil                       ascolab                         http://www.ascolab.com
 Stefan-Helmut Leitner                  ABB                             http://www.abb.com
 Mariusz Postol                         CAS                             http://www.cas.eu
 Alisher Maksumov                       OSIsoft                         http://www.osisoft.com
 Jan Burian, Rudolf Griessl             Iconics, Inc.                   http://www.iconics.com
 John Hoffman                           TimeKeeping Systems Inc.        http://www.guard1.com
 Nathan Pocock                          Software Toolbox, Inc.          http://www.softwaretoolbox.com
Krishna Bandaru          Tata Consulting Services Ltd.   http://www.tcs.com
Mark Timperley           Invensys                        http://www.invensys.com
Alexander Gdalevich      Cognex Corporation              http://www.cognex.com
Craig McMurtry           Microsoft Corporation           http://www.microsoft.com
Yo Funaki                Yokogawa                        http://www.yokogawa.com
Alexander Allmendinger   Allmendinger                    http://www.allmendinger.de
Anuradha Vidyashanka     Honeywell                       http://www.honeywell.com
Tim Fortin               Honeywell                       http://www.honeywell.com
Ravil Nugmanov           Matrikon                        http://www.matrikon.com

								
To top