NBWSS message formats
To communicate with WebSocket endpoints, the NetBackup WebSocket Service (NBWSS) uses its own message format with JavaScript Object Notation (JSON). The JSON format allows NBWSS and the applications on the endpoints to keep track of messages by ID and determine their type and subtype.
The messages operate as request and response: each request has an associated response.
The following is an example of an NBWSS connection request:
{
"version": "1.0",
"id": "0CEAB6C2-0BBF-4F60-974D-C1F3EF39B872",
"type": "CONNECT",
"subType": "REQUEST",
"timeStamp": 1444944181,
"payload": {
"token": "qwerrtrtrtrt2234344==="
}
}An example of an application's response:
{
"version": "1.0",
"id": "0CEAB6C2-0BBF-4F60-974D-C1F3EF39B872",
"type": "CONNECT",
"subType": "RESPONSE",
"timeStamp": 1444944191,
"payload": {
"valid": true
}
}Note the following:
The message begins with a left curly bracket ({) and ends with a right curly bracket (}).
The response should have the same value for
"id"as the request.The entries consist of
key:valuepairs that are comma-separated.The message includes a
payload. For messages of typeCONNECTorCOMMAND, the payload contains an object within curly brackets { }. For messages of typeNOTIFICATION, the payload contains an array within square brackets [ ].
Table: NBWSS message fields describes the fields in the NBWSS messages.
Table: NBWSS message fields
Key | Description |
|---|---|
| The version of the message. In this release, the available version is |
| A unique identifier for the message. When NBWSS sends a request message, it generates a UUID and places it in this field. When the application at the endpoint responds with a response message, NBWSS expects the response to contain the same ID as the request message. The ID allows NBWSS to map the request message to the response message. When NBWSS receives a request message, its response message contains the same ID as the request message. The ID allows the endpoint application to map the request to the response if necessary. |
| The message type. The available types are:
|
| The message subtype. The available subtypes are |
| A numeric representation of the UNIX Epoch time (in seconds) when the message was sent. |
| The body of the message. The body varies with the type and subtype of the message. The following topics include further details and examples: See API calls over NBWSS. See NBWSS notifications. |