6.0.1

Table Of Contents
To ensure the contents of a subscribed library are up-to-date, the subscribed library automatically
synchronizes to the source published library on regular intervals. You can also manually synchronize
subscribed libraries.
You can use the option to download content from the source published library immediately or only when
needed to manage your storage space.
Synchronization of a subscribed library that is set with the option to download all the contents of the
published library immediately, synchronizes both the item metadata and the item contents. During the
synchronisation the library items that are new for the subscribed library are fully downloaded to the storage
location of the subscribed library.
Synchronization of a subscribed library that is set with the option to download contents only when needed
synchronizes only the metadata for the library items from the published library, and does not download the
contents of the items. This saves storage space. If you need to use a library item you need to synchronize
that item. After you are done using the item, you can delete the item contents to free space on the storage.
For subscribed libraries that are set with the option to download contents only when needed, synchronizing
the subscribed library downloads only the metadata of all the items in the source published library, while
synchronizing a library item downloads the full content of that item to your storage.
If you use a subscribed library, you can only utilize the content, but cannot contribute with content. Only the
administrator of the published library can manage the templates and files.
Table 41. Source Objects to Which You Can Subscribe By Creating a Subscribed Library in The
vSphere Web Client .
Source Object
Create a subscribed library in the
vSphere Web Client by using the
option to Download all library
content immediately
Create a subscribed library in the
vSphere Web Client by using the
option to Download library content
only when needed
A library running in a vCenter Server
6.0 instance.
Supported Supported
A catalog running in a vCloud
Director 5.5 instance.
Supported Not supported
A third-party library. Supported for third-party libraries
that require authentication, if the
username of the third-party library is
vcsp. If the username of the source
third-party library is different than
vcsp, you can subscribe to it by using
VMware vCloud Suite API.
Supported for third-party libraries that
require authentication, if the username
of the third-party library is vcsp. If the
username of the source third-party
library is different than vcsp, you can
subscribe to it by using VMware
vCloud Suite API.
Libraries store content on a file system or a datastore. To ensure optimal performance, use file systems for
libraries that are published, and use datastores for local and subscribed libraries.
This chapter includes the following topics:
n
“Create a Library,” on page 73
n
“Synchronize a Subscribed Library,” on page 74
n
“Edit the Settings of a Local Library,” on page 74
n
“Edit the Settings of a Subscribed Library,” on page 75
n
“Delete a Content Library,” on page 76
n
“Hierarchical Inheritance of Permissions for Content Libraries,” on page 76
n
“Sample User Role for Working with Content Libraries,” on page 78
n
“Populating Libraries with Content,” on page 78
n
“Working with Items in a Library,” on page 81
vSphere Virtual Machine Administration
72 VMware, Inc.