|
pure virtual |
Add the put batch item for a KMIP Template.
A successful startRequestMsg function must be called first.
Note, in Put requests the following fields defined in the startRequestMsg( P6KMIP_REQUESTPARAMS params ) call are not allowed: { pMaxResponseSize, pAsynchIndicator, pBatchErrorOption, pBatchOrderOption }. Simply set these fields to NULL in the "params" parameter in the startRequestMsg call.
Put (Section 5.2 KMIP spec), allows the KMIP server to push one of several objects to the client. This call is used to send one of the following wrapped objects: {Template}
params | [ in ] group of parameters specific to the put request |
itemCount | [ in ] the number of entries pointed to by pItemList |
pItemList | [ in ] A template is composed of one or more attributes which can hold any of the defined attributes that can be associated with a registered object (e.g., Object Group), This points to an array of P6KMIP_ATTRIBUTE structures. |
pExtension | [ in ] optional can be NULL, vendor defined extension to the operation |
Success | P6R::eOk | |
Failure | P6R::eNotInitialized | A successful call to intialize() must be made before calling this funciton. |
P6R::eTooSmall | The configured buffer size in pPool is too small to hold the generated message. | |
P6R::eInvalidState | A successful call to startRequestMsg() must be made before calling this function. | |
P6R::eRange | pExtension->encodedExtension.length must be a multiple of 8, since encoded as the Vendor Extension Structure |