Asset Manager building block basics

Building block structure

The Asset Manager Building Block 9.5 is used register asset types and support type extension through custom type extension handlers.

The Asset Manager building block provides following features:

the ability to register event handlers around pre- and post-CRUD events on any asset.
the ability to associate any number of extended properties with an asset type.
framework to register and launch the editor UI for a given asset type

The Asset Manager building block includes these components:

Asset Manager building block UI: The Asset Manager building block provides multiple Flex® UI components which can be used and stitched together to create the UI for your solution. The Asset Manager building block UI uses the Assembler services for interacting with the underlying repository, Adobe® LiveCycle® Content Services 9. This component provides the capability to execute pre-configured actions, such as Create, Edit, and Delete on assets. The various assets and their corresponding actions can be configured declaratively and the same will show up on the UI. It also provides advanced search capabilities on the metadata associated with the assets. The Asset Manager building block UI can be configured to launch other user interfaces, on click of respective action buttons.
The editor UIs in the Correspondence Management Solution Accelerator 9.5 solution template are configured to work with relevant Asset Manager building block actions by default. The Asset Manager building block UI component provides a configurable search pod and search result UI based on asset definitions and configurations.
Security: The overall application security is managed and intercepted via a Spring security-based module that connects to Adobe User Management.

Building block structure

The Asset Manager building block components are installed in the following folder: c:\Adobe\Adobe LiveCycle ES2\sa_resources\SA_SDK_9.5\BuildingBlocks\assetmanager\.

Component location	Description
\client\flex\adobe-amg-flex-presentation_rb.swc	Resource bundles SWC for the Asset Manager building block. This SWC file contains bundles for all supported locales and is used as a compile-time dependency for adobe-amg-flex-presentation.swc
\client\flex\adobe-amg-flex-domain-model.swc	Domain library for the Asset Manager building block. It contains various domain classes encapsulating business data and behavior, and can be leveraged to build Flex views with less effort.
\client\flex\adobe-amg-flex-presentation.swc	Presentation SWC for the Asset Manager building block. This SWC contains the presentation logic and the Flex views built atop the Asset Manager Flex domain model.
\client\flex\adobe-amg-flex-presentation_styles.swc	Styles SWC for the Asset Manager building block. This SWC file contains the style sheets and various assets (such as animations, icons, and skins) that are used by the Asset Manager building block.
\client\flex\src\adobe-amg-flex-presentation_rb-src.zip	Zip file that contains the project for resource bundles of Asset Manager building block Flex components.
\client\flex\src\adobe-amg-flex-presentation_styles-src.zip	Zip file that contains the project for the style sheets and various assets (such as animations, icons, and skins) that are used by Asset Manager building block.
\client\flex\src\adobe-amg-flex-presentation-src.zip	Zip file that contains the project for presentation logic and the Flex views that encompass various UI components such as the Search Pod and Search Reults Viewer in the Asset Manager building block.
\client\java\adobe-amg-asset-manager-api	Client jar for the Asset Manager building block.
\services\adobe-amg-assembler.jar	For internal use only.
\services\adobe-amg-asset-manager-impl.jar	For internal use only.
\services\adobe-amg-cms-client-api	For internal use only.
\services\adobe-amg-cms-client-impl	For internal use only.

In addition, a file named cs-provider.amp is copied to the c:\Adobe\Adobe LiveCycle ES2\deploy folder. This is the Content Services provider AMP for the Asset Manager building block interfacing with Content Services for internal use only.