This documentation is for WSO2 ES version 2.0.0. View documentation for the latest release.
Creating the Shell of an Asset Extension - Enterprise Store 2.0.0 - WSO2 Documentation
||
Skip to end of metadata
Go to start of metadata

Follow the instructions below to create the shell of an asset extension, which is the folder structure of an asset extension:

For more information on asset extensions, see Introduction to Asset Extensions.

  1. Create an asset type. If you are extending a default asset type in ES, skip this step.

  2. Create an asset extension folder structure in the asset directory. For more information, see Asset Extension Components. The assets directory of the Publisher and Store asset extension are as follows:

    ES ComponentDirectory
    Publisher<ES_HOME>/repository/deployment/server/jaggeryapps/publisher/extensions/assets/<ASSET_TYPE_NAME>
    Store<ES_HOME>/repository/deployment/server/jaggeryapps/store/extensions/assets/<ASSET_TYPE_NAME>

    The <ASSET_TYPE_NAME> should always correspond to an asset type that exists in ES, which has a corresponding RXT definition in the registry.

    An asset extension directory will contain the following elements:

    • A themes directory with one or more themes (Optional).
    • An asset.js file (Optional).
    • pages directory (Optional).
    • An apis directory (Optional).

    Example:
    The following screenshot explains the general folder structure of an asset extension, where the name of the asset type is servicex.
  3. Restart the ES server, so that ES evaluates the changes in the asset.js file.
  4. Customize the newly created shell of the asset extension. For more information, see Working with Asset Extensions.
  • No labels