Page History
...
| UI Button | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Anchor | ||||
|---|---|---|---|---|
|
| URL in Reference AMS | /new_client/{id} |
|---|---|
| HTTP Method | POST |
BMC notifies AMS of all new clients and this interface is used for that purpose. The intention is that AMS in responds to the notification immediately and then queries what ever systems it needs to in order to decide what kind of job specification needs to be sent, if any. The intention is that this notification contains the minimum amount of information which enables AMS to query for more information, request an asset report or to reset or shutdown the client. An example of the message that is sent:
...
Job Specification Validation
| URL in Reference AMS | /client/{id}/jobspec |
|---|---|
| HTTP Method | POST |
Once AMS has sent job specification for any given client, BMC passes it on to the Drive Eraser instance. Drive Eraser validates it and BMC informs AMS on it's validity. This interface receives that information. To the extent that it was invalid, both BMC and Drive Eraser will remove the session and start over. AMS will then be informed of the new session as described in the chapter New Client. An example of the message:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
{
"job_spec": {
"id": "c44ed942-fab6-4dfe-8b5a-81265e68a8dd",
"status": "NOT_VALID",
"message": "I am a reason of failure"
}
} |
Asset Report
| URL in Reference AMS | /client/{id}/asset_report |
|---|---|
| HTTP Method | POST |
Once AMS has requested BMC to fetch an asset report, it is delivered to this interface. An example message:
...
The XML report is encoded with BASE64.
Session Finished
| URL in Reference AMS | /client/{id}/finished |
|---|---|
| HTTP Method | POST |
Once session has finished, AMS is notified with this interface. Session is considered finished when
...