The ResultFileType provides a description of a file that is part of a result of a program manager run. It is formally defined in Table 64.
Table 64 – ResultFileType Definition
Attribute |
Value |
||||
BrowseName |
ResultFileType |
||||
IsAbstract |
False |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of 0:BaseObjectType defined in OPC 10000-5 |
|||||
0:HasComponent |
Object |
File |
|
FileType |
O |
0:HasProperty |
Variable |
MimeType |
0:String |
0:PropertyType |
M |
0:HasProperty |
Variable |
Name |
0:String |
0:PropertyType |
M |
0:HasProperty |
Variable |
URL |
0:String |
0:PropertyType |
O |
Conformance Units |
|||||
LADS ResultFileType |
|||||
|
File is the OPC UA Node of the file with the method for downloading the file.
MimeType is the MIME type of the file.
Name is the name that describes the file. The name may be different from the filename on the filesystem.
URL is a URL from which the file can be downloaded.
Note: This specification allows for transferring the result file using either the native OPC UA FileType or a different protocol. For example, the URL property can be used with a second protocol (e.g., FTP). The advantage of the OPC UA method is that all information can be provided using a single protocol. No secondary access management and security implementation is needed. For Brownfield applications where a second protocol exists, this second protocol can be used to reduce the implementation effort.