How the Asset Manager building block works
The Asset Manager building block is a specialized repository
that allows type-based management of assets. It is a generic framework
that eases application creation, as most things are taken care of
by the Asset Manager building block. This allows you to concentrate
effort on application-specific components. As the first step, you
must register all of the assets used by your correspondence management
application with the Asset Manager building block. Based on the information
collated in the registration step, the Asset Manager building block provides
the following features and functionality to your correspondence management
application:
-
Provides the ability to register event handlers around
pre- and post- CRUD events on any asset.
-
Provides the ability to associate any number of extended
properties with an asset type. The Asset Manager building block
not only saves, retrieves, and deletes these extended properties
(along with asset CRUD), but also allows searching the assets based
on its values. This is a very powerful feature as it can be achieved
at runtime without writing any custom code.
Asset Manager building block components
The following diagram describes the high-level architecture
of the Asset Manager building block.
-
Asset Type Loader
-
This component is responsible for registering asset types and
asset handlers (use to extend asset CRUD and deploy) with the Asset Manager
building block. This component uses a native provider to connect
to Content Services to deploy the various asset types in Content
Services. Type registration is important because it provides metadata
that Content Services stores and uses to understand the asset type.
