The components of this parameter are defined in Table 175.
Name |
Type |
Description |
||||||||||||||||||||||||||||||||||||
RequestHeader |
structure |
Common parameters for all requests submitted on a Session. |
||||||||||||||||||||||||||||||||||||
authenticationToken |
Session AuthenticationToken |
The secret Session identifier used to verify that the request is associated with the Session. The SessionAuthenticationToken type is defined in 7.36. |
||||||||||||||||||||||||||||||||||||
timestamp |
UtcTime |
The time the Client sent the request. The parameter is only used for diagnostic and logging purposes in the Server. |
||||||||||||||||||||||||||||||||||||
requestHandle |
IntegerId |
A requestHandle associated with the request. This Client defined handle can be used to cancel the request. It is also returned in the response. |
||||||||||||||||||||||||||||||||||||
returnDiagnostics |
UInt32 |
A bit mask that identifies the types of vendor-specific diagnostics to be returned in diagnosticInfo r esponse parameters. The value of this parameter may consist of zero, one or more of the following values. No value indicates that diagnostics are not to be returned.
Each of these values is composed of two components, level and type, as described below. If none are requested, as indicated by a 0 value, or if no diagnostic information was encountered in processing of the request, then diagnostics information is not returned.
Type:
|
||||||||||||||||||||||||||||||||||||
auditEntryId |
String |
An identifier that identifies the Client’s security audit log entry associated with this request. An empty string value means that this parameter is not used. The auditEntryId typically contains who initiated the action and from where it was initiated. The auditEntryId is included in the AuditEvent to allow human readers to correlate an Event with the initiating action. More details of the Audit mechanisms are defined in 6.5 and in OPC 10000-3. |
||||||||||||||||||||||||||||||||||||
timeoutHint |
UInt32 |
This timeout in milliseconds is used in the Client side Communication Stack to set the timeout on a per-call base. For a Server this timeout is only a hint and can be used to cancel long running operations to free resources. If the Server detects a timeout, he can cancel the operation by sending the Service result Bad_Timeout. The Server should wait at minimum the timeout after he received the request before cancelling the operation. The Server shall check the timeoutHint parameter of a Publish request before processing a Publish response. If the request timed out, a Bad_Timeout Service result is sent and another Publish request is used. The value of 0 indicates no timeout. |
||||||||||||||||||||||||||||||||||||
additionalHeader |
Extensible Parameter AdditionalHeader |
If additional header parameters are needed, they shall be passed using the AdditionalParametersType defined in 7.1. Applications that do not understand the header should ignore it. |