Managing Resources

To manage resources like bundles, style sheets or images, use the Resource Manager view, which you can open from the Administration Perspective launch panel. It provides the possibility to manage the following resources for the runtime environment of the administrator the Administration Perspective is started for:

Resource Manager
Figure: The Resource Manager View

Note
Supported characters for filenames are: "a-zA-Z0-9-+=_.,)(&^%$#@!~". The filename should always start with an alphanumeric character.

The section Resources Tree View describes the functionality of the tree view provided for the resources.

Configuration in an EJB Environment without Spring

To enable the usage of the Resource Manager view in an EJB environment without Spring, you need to configure some environment setting for document service usage.

For detailed information on the Document Management Service usage, please refer to the Document Service Integration Guide. Document Service Integration Guide.

The DmsContentServlet assumes that you have a well configured Spring environment, because it needs an instance of the ForkingService. In case you are working in an EJB environment without Spring, you can add and modify respectively the following settings to increase the performance:

  1. In the web.xml file of your Web application modify the DmsContentServlet so that the initialization parameter clientContext is set to ejb:
    <servlet>
        <servlet-name>DmsContentServlet</servlet-name>
        <servlet-class>org.eclipse.stardust.engine.api.web.dms.DmsContentServlet</servlet-class>
        <init-param>
            <param-name>clientContext</param-name>
            <param-value>ejb</param-value>
        </init-param>
    </servlet>
    <servlet-mapping>
        <servlet-name>DmsContentServlet</servlet-name>
        <url-pattern>/dms-content/*</url-pattern>
    </servlet-mapping>
    This is necessary as otherwise the servlet defaults to Spring environment lookup.
  2. In the same way add or modify the FsdContentServlet so that the initialization parameter clientContext is set to ejb:
    <servlet>
      <servlet-name>FsdContentServlet</servlet-name>
      <servlet-class>org.eclipse.stardust.ui.web.viewscommon.docmgmt.FileSystemDocumentServlet</servlet-class>
      <init-param>
        <param-name>clientContext</param-name>
        <param-value>ejb</param-value>
      </init-param>
    </servlet>
    
    <servlet-mapping>
      <servlet-name>FsdContentServlet</servlet-name>
      <url-pattern>/fsd-content/*</url-pattern>
    </servlet-mapping>
    This servlet is required to render images uploaded via activity panels as document metadata.
  3. Add an ejb-local-ref element to the web.xml file of your Web application:
    <ejb-local-ref>
        <ejb-ref-name>ejb/ForkingService</ejb-ref-name>
        <ejb-ref-type>Session</ejb-ref-type>
        <local-home>org.eclipse.stardust.engine.api.ejb2.beans.LocalForkingServiceHome</local-home>
        <local>org.eclipse.stardust.engine.api.ejb2.beans.LocalForkingService</local>
    </ejb-local-ref>
  4. Add the ForkingService to your Web application server specific deployment descriptor. For example to a JBoss specific deployment descriptor jboss-web.xml:
    <ejb-local-ref>
        <ejb-ref-name>ejb/ForkingService</ejb-ref-name>
        <local-jndi-name>org.eclipse.stardust.engine.core.runtime.beans.ForkingService</local-jndi-name>
    </ejb-local-ref>

Resources Tree View

The resource tree view displays all relevant resources. Under the tree nodes, all currently available resources for the tenant are displayed. Documents and folders are sorted alphabetically in the tree. You have the option to create a sub-folder hierarchy.

Rules for Folders and Sub-folders under Artifacts

The folders and sub-folders under artifacts are created automatically. Although an administrator can delete any of these folders, subsequent log-out and log-in operations will recreate these folders automatically. It is not possible to create any sub-folders and files under the artifacts folder directly. However you can upload files and add sub-folders to the existing sub-folders in artifacts.

Artifacts Folder Operations

Apart from creating and uploading a file, you can also backup and load configurations from and to the artifacts folder.

Saving a configuration

You can download a complete configuration by saving it in a zipped file. Right-click on artifacts and select Send to Zip.

Artifacts - Backup Configuration
Figure: Backup Configuration

A download dialog appears depending on your browser type. Choose the option to save the configuration to a zip file. The default name is artifacts.zip. You can rename the zip file as you like.

Please refer to section Sending to ZIP File of chapter Document Operations for details on downloading resources in a zipped file.

Loading a configuration

You can load existing configurations or reload formerly saved configurations from a zipped file.

Right-click on the artifacts folder and select Upload Zip from the menu options.

Artifacts - Load Configuration
Figure: Loading a configuration from a zipped file

Please refer to section Uploading a ZIP File of chapter Document Operations for details on uploading resources from a zipped file.

You can apply the uploaded configuration by setting it in the Portal Configuration part of the Configuration Panel, e.g. by selecting a new uploaded skin.

Skins Folder Structure Rules

Use the following pattern for the Skins folder structure:

Structure of a Skin Folder.
Figure: Structure of a Skin Folder.

Folder Management

You can expand () and collapse () nodes in the tree.

To open the folder menu, right-click on the folder node.

Folder Operations
Figure: Folder Context Menu

The following operations are provided on folders in the Resource Manager view:

For detailed information on the listed folder operations, refer to chapter Document Operations.

Provided File Operations

To open the document menu, right-click on the file node.

File Operations
Figure: Document Context Menu

The following operations are provided on documents in the Resource Manager view:

For detailed information on the listed document operations, refer to chapter Document Operations.