5.1

mimeType="application/vnd.vmware.vcloud.createBackupParams+xml"
linkHref="{baseUri}vApp/vapp-{resourceId}/action/backup"
href="https://vcloud.example.com/api/admin/extension/service/link/f62e..." />
</QueryResultRecords>
NOTE Link id values are truncated in this example.
Using this information, find the ServiceLinkRecord that represents the service link you want to delete, and
make a DELETE request to that URL.
DELETE https://vcloud.example.com/api/admin/extension/service/link/f62e...
Service-Specific Tasks and Events
An extension service can create Task objects in a vCloud Director organization, and can post events to the
organization's event stream.
Tasks and events are created in the context of an organization. Each task or event is associated with exactly
one user, who must be a system administrator or a member of the organization in which the task or event is
created. Tasks and events can also have an owner, which is a reference to the subject of the task or event (for
example, an object being created or updated by a task).
Task and Event Workflow
vCloud Director native services typically create Task objects to track the progress of asynchronous events.
These objects are returned to clients as Task elements, which can be embedded in a container that represents
an object under construction, or simply returned in Task form.
Tasks are also reported in the organization's event stream. A service can also add its own events to this stream,
in addition to the ones added as a side-effect of creating a task.
Extension services act as vCloud API clients when creating tasks and events, even if those tasks and events are
created to track service-specific objects or operations. After a task is created in vCloud Director, an extension
service can use its AMQP connection to vCloud Director to return a Task as the response, or part of the response,
to a client request.
Localizing Task and Event Message Content
Message strings included in tasks and events can be localized. See “Localization Framework for Extension
Services,” on page 302.
Create or Update a Service-Specific Task
When a user requests an asynchronous operation from an extension service, the service can create a task object
and add it to an organization's tasks list.
Every vCloud Director organization has a tasks list and accepts requests to add a task to the list. When a client
requests an asynchronous operation from a service, the service starts to process the request and also POSTs a
Task element to the organization's tasksList URL. vCloud Director adds information such as an id and
startTime to the Task, places it on the organization's TasksList, creates an event in the organization's event
stream, and returns the Task to the service. The service can then send the Task, as an AMQP message, to
vCloud Director, which sends it as a response to the client that made the original request.
NOTE Because of the diversity of sources from which an extension service can draw references to the User,
Owner, and Organization elements of a Task, it may not always be possible for every client to resolve such
references. For example, if a service creates an object in an organization of which you are not a member, you
will not be able to resolve the reference to the object in the Owner element of the Task.
Chapter 11 vCloud Director Extension Services
VMware, Inc. 291