Cascade Server Asset Hierarchy

NEWS & TIPS

  • Site Access Keys
  • Top: Alt+t
    Previous: Alt+,
    Next: Alt+.
    Up: Alt+;
    (Note: use Ctrl on the Mac)

Cascade Server Asset Hierarchy

A little aside concerning IDs and Paths:

Every asset (or administration component) in Cascade Server has an ID. This ID is a 32 digit hexadecimal number used as the UUID (Universally Unique Identifier) for all assets contained within Cascade Server. Any time you see a property ending in "Id", that field will be referring to this number.

Every asset in Cascade Server has a Path. This Path is calculated exactly like calculating a file system Path in any operating system. The system begins with the lowest level folder's name and follows the folder hierarchy by appending a slash and then the next folder's system name until the asset is located. The asset's name is then appended, following a slash. An example of a Path in Cascade Server would be: /intranet/files/logo.gif. The leading slash is optional. Anytime you see a property ending in "Path", that field refers to this construct.

You will notice that most times a relationship will have both an ID and a Path property (for example, parentFolderId and parentFolderPath). This is to provide the writer of the SOAP request with the flexibility to specify a relationship using either the ID or the Path. Generally, this appears inside a <choice> element, so it is valid to only specify either the ID or the Path in order to define the relationship.

Cascade Server has a variety of assets, all of which have various properties able to be edited or specified via an edit or create request. Unless otherwise noted, not specifying a value will lead Cascade Server to use the existing value (when editing) or to assign a default value for that property (when creating), which is the following: for Booleans - false, for Strings - empty/null, and for Numbers - 0.

The Cascade Server Assets are organized in a hierarchical manner for object-oriented purposes. Since most assets share many common fields, it makes sense to define them once in a certain type (for example: folder-contained) rather than to re-define those fields for each different asset.

  1. Home Area Assets »
    The Cascade Server Assets are organized in a hierarchical manner for object-oriented purposes.
    1. Base Asset
      This page describes the Base Asset.
    2. Named Asset
      This page describes the Named Asset.
    3. Folder Contained Asset
      This page describes the Folder Contained Asset.
    4. Stylesheet Asset
      This page describes the Stylesheet asset.
    5. Template Asset
      This page describes the Template asset.
    6. Dublin Aware Asset
      This page describes the Dublin Aware Asset.
    7. Expiring Asset
      This page describes the Expiring Asset.
    8. Symlink
      This page describes the Symlink asset.
    9. Block
      This page describes the Block asset.
    10. Feed Block
      This page describes the Feed Block asset.
    11. Index Block
      This page describes the Index Block asset.
    12. Text Block
      This page describes the Text Block asset.
    13. XHTML Block
      This page describes the XHTML Block asset.
    14. XML Block
      This page describes the XML Block asset.
    15. Publishable Asset
      This page describes the publishable asset.
    16. File
      This page describes the File asset.
    17. Folder
      This page describes the Folder asset.
    18. Page
      This page describes the Page asset.
    19. Reference Asset
      This page describes the reference asset.
  2. Administrative Area Components »
    This section provides a description of each Administrative Area Component as it fits in the Cascade Server asset hierarchy.
    1. Containered Asset
      This page describes the Containered Asset component.
    2. User
      This page describes the User component.
    3. Group
      This page describes the Group component.
    4. Asset Factory
      This page describes the Asset Factory component.
    5. Asset Factory Container
      This page describes the Asset Factory Container component.
    6. Page Configuration Set
      This page describes the Page Configuration Set component.
    7. Page Configuration Set Container
      This page describes the Page Configuration Set Container component.
    8. Structured Data Definition
      This page describes the Structured Data Definition component.
    9. Asset Factory Container
      This page describes the Structured Data Definition Container component.
    10. Metadata Set
      This page describes the Metadata Set component.
    11. Metadata Set Container
      This page describes the Metadata Set Container component.
    12. Publish Set
      This page describes the Publish Set component.
    13. Publish Set Container
      This page describes the Publish Set Container component.
    14. Target
      This page describes the Target component.
    15. Destination
      This page describes the Destination component.
    16. File System Transport
      This page describes the File System Transport component.
    17. FTP Transport
      This page describes the FTP Transport component.
    18. Workflow Definition
      This page describes the Workflow Definition component.
    19. Workflow Definition Container
      This page describes the Workflow Definition Container component.
Last modified on Mon, 05 Nov 2007 11:04:43 -0500
Top / Up / Table of Contents