Specialized Client Objects
A specialized client object provides functionality that is relevant for specific problem domain. It contains, in a sense, pre-packaged pieces of reusable code that the developer would typically need to write, whenever he needs to develop a solution for that problem domain.
In OPC Unified Architecture (OPC UA), the problem domain addressed by the specialized client object is often a selected part of the OPC UA specification.
QuickOPC exposes several useful specialized client objects to you, saving you from having to write unnecessary parts of code.
OPC UA Global Discovery Client
The OPC UA Global Discovery Client is a specialized OPC UA client object for global discovery. In the OPC UA specifications, the functionality covered by this type is described in Part 12: Discovery and Global Services, in the Global Discovery Server section.
The methods allow querying for applications and/or servers, and registering, unregistering or updating application registrations in the GDS.
OPC UA Certificate Management Client
The OPC UA Certificate Management Client is a specialized OPC UA client object providing access to certificate management (CM) information model of an OPC UA Global Discovery Server (GDS). The methods allow getting certificate groups, requesting key pairs or certificate signing and obtaining the results, retrieving trust lists, and more.
QuickOPC can provide even higher level of automation, and additional features that make the certificate management - which is otherwise a traditional pain point in OPC UA - easier. For more information, see Certificate Management, PKI and UA Administration.
OPC UA File Transfer Client, and File Provider Model
The OPC UA specification allows servers to provide file and directories, resembling traditional file systems, as part of their information model, and QuickOPC allows to consume this functionality comfortably. QuickOPC gives you a specialized client object for easy execution all "File Transfer" operations, but not just that. QuickOPC also allows the OPC UA files to be treated as normal .NET streams, so that your code can abstract from details of OPC UA when manipulating file contents. In addition, you can use the File Provider Model, which further generalizes how your application "sees" the elements of the OPC UA file system, making it possible to write programs that are independent of the type of the file system they work with.
Available methods include:
- Obtain information about specific files
- Create, open and close files
- Read data from and write data to files
- Get and set position in the file
- Delete files
- Create and delete directories
- Move or copy files and directories
- List contents of directories
- Finding files, directories, and finding a parent directory
- Finding a file system on a specified OPC UA object
- Determining whether the specified node represents a file or directory