Errata exists for this version of the document.
The Hello Message has the additional fields shown in Table 51.
Table 51 – OPC UA Connection Protocol Hello Message
|
Name |
Data Type |
Description |
|
ProtocolVersion |
UInt32 |
The latest version of the UACP protocol supported by the Client. The Server may reject the Client by returning Bad_ProtocolVersionUnsupported. If the Server accepts the connection is responsible for ensuring that it returns Messages that conform to this version of the protocol. The Server shall always accept versions greater than what it supports. |
|
ReceiveBufferSize |
UInt32 |
The largest MessageChunk that the sender can receive. |
|
SendBufferSize |
UInt32 |
The largest MessageChunk that the sender will send. |
|
MaxMessageSize |
UInt32 |
The maximum size for any response Message. The Server shall abort the Message with a Bad_ResponseTooLarge Error Message if a response Message exceeds this value. The mechanism for aborting Messages is described fully in 6.7.3. The Message size is calculated using the unencrypted Message body. A value of zero indicates that the Client has no limit. |
|
MaxChunkCount |
UInt32 |
The maximum number of chunks in any response Message. The Server shall abort the Message with a Bad_ResponseTooLarge Error Message if a response Message exceeds this value. The mechanism for aborting Messages is described fully in 6.7.3. A value of zero indicates that the Client has no limit. |
|
EndpointUrl |
String |
The URL of the Endpoint which the Client wished to connect to. The encoded value shall be less than 4 096 bytes. Servers shall return a Bad_TcpEndpointUrlInvalid Error Message and close the connection if the length exceeds 4 096 or if it does not recognize the resource identified by the URL. |
The EndpointUrl parameter is used to allow multiple Servers to share the same endpoint on a machine. The process listening (also known as the proxy) on the endpoint would connect to the Server identified by the EndpointUrl and would forward all Messages to the Server via this socket. If one socket closes, then the proxy shall close the other socket.
If the Server does not have sufficient resources to allow the establishment of a new SecureChannel it shall immediately return a Bad_TcpNotEnoughResources Error Message and gracefully close the socket. Client should not overload Servers that return this error by immediately trying to create a new SecureChannel.