diff options
| author | Ulf Lamping <ulf.lamping@web.de> | 2007-05-14 13:58:54 +0000 |
|---|---|---|
| committer | Ulf Lamping <ulf.lamping@web.de> | 2007-05-14 13:58:54 +0000 |
| commit | dd8feca5149d02330925f12ab269f869b4e4c360 (patch) | |
| tree | 3abc54efcdcee8aaadf040b68ffb36c6b9f1c4f4 /plugins/opcua/README | |
| parent | 013332de7f8fe9f4093d83521be8bfcfa7d17e76 (diff) | |
from Gerhard Gappmeier (ascolab):
new dissector for OPCUA protocol
svn path=/trunk/; revision=21760
Diffstat (limited to 'plugins/opcua/README')
| -rw-r--r-- | plugins/opcua/README | 58 |
1 files changed, 58 insertions, 0 deletions
diff --git a/plugins/opcua/README b/plugins/opcua/README new file mode 100644 index 0000000000..40646bdf3d --- /dev/null +++ b/plugins/opcua/README @@ -0,0 +1,58 @@ +OpcUa Plugin:
+=============
+
+This plugin implements the dissection of the OpcUa Binary Protocol.
+Author: Gerhard Gappmeier
+ ascolab GmbH
+ http://www.ascolab.com
+
+Overview:
+=========
+
+OpcUa (OPC Unified Architecture) is a vendor and platform independent
+protocol for automation technology. It is the successor of the
+COM/DCOM based specifications OPC DA, OPC Alarm & Events, OPC HDA, etc.
+It unifies all this technologies into a single protocol.
+
+The specification describes abstract services that are independent
+of the underlying protocol. For now there exist protocol mappings
+to a Binary TCP based protocol and a SOAP based Webservice.
+Also a hybrid version will be available where the Binary messages are transported
+by a single webservice command called "Invoke".
+
+More information about the technology you can find on
+http://www.ascolab.com/index.php?file=ua&lang=en.
+
+Protocol Mappings:
+==================
+
+Binary (TCP): The fastest and most flexible version (small footprint, no XML and SOAP necessary)
+ can easily be tunneled (SSH, IPSEC, etc.), redirected, ...
+SOAP version: Easy to implement with verious tools like .Net, JAVA, gSOAP, etc.
+ Better to communicate through firewalls via HTTP.
+SOAP with Binary Attchment: Combines the advantages of both.
+ The messages are encoded as Binary, and transported via SOAP as binary
+ attachment.
+
+The OPC Foundation offers a free Opc Ua stack implementation in ANSI C
+for all members. This stack implements the binary protocol as well
+as the SOAP version. It's easily portable to different kinds of operating
+systems from embedded devices to servers.
+This makes it easy to implement Opc Ua applications based on this stack
+and it is expected that the binary protocol will be the most used
+protocol.
+Nevertheless it's free to everbody to implement an own stack according
+to the specification. An own implementation of the SOAP version
+should be easy with the various SOAP toolkits.
+
+For more information see http://www.opcfoundation.org
+
+Known limitations:
+==================
+
+* In this version the security layer contains only dummy data.
+ The plugin decodes the transport layer, skips the security dummy data
+ and decodes the application layer.
+ Security implementation will follow when it has been implemented in the
+ Opc Ua stack.
+
|