Managing Resources

To manage resources like bundles, style sheets or images, use the Resource Management view. It provides the possibility to manage the following resources for the runtime environment of the administrator the Administration Perspective is started for:

• Bundles - manages bundles loaded by the Web and application tier.
• Contents - manages markups (Facelets, HTML) and resources like images, JavaScript or style sheets loaded by the Web tier.
• Skins - manages resources containing specific skins loaded by the Web tier.

Figure: The Resource Management 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 Management 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. You have the possibility 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

You can backup and load configurations from and to the artifacts folder.

• Backup Configuration
• Load Configuration

Backup Configuration

You can download a complete configuration using the Backup Configuration option and save it in a zipped file. Right-click on artifacts and select Backup Configuration.

Figure: Backup Configuration

The download dialog appears. Click the Download button to start the download.

Figure: Download configuration confirmation

The configuration files are saved in a zipped file. The default name is artifacts.zip, which can be changed in the according File download dialog.

Load Configuration

To load existing configurations or reload formerly saved configurations, use the Load Configuration option.

Right-click on the artifacts folder and select Load Configuration from the menu options.

Figure: Load Configuration

Note: This operation removes any existing content from the artifacts folder and cannot be undone once confirmed.

A confirmation dialog opens to confirm that the existing files and folders can be overwritten.

Figure: Load Configuration confirmation

The File Upload dialog opens where you can browse to the configuration zip file to be uploaded. In case the file is not valid, an error message appears and the operation is interrupted.

You can apply the uploaded configuration by setting it in the Portal Configuration 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:

• Use one folder for each skin with the skin name.
• This folder should contain only one style sheet file (css).
• Sub-folders in the skin folder are only for dependencies of the style sheet file, e.g. images.
• Note that sub-folders will not be searched for other css files.

Figure: Structure of a Skin Folder.

Folder Management

You can select, expand and collapse nodes in the tree view.

Figure: Collapsing Nodes

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

Figure: Folder Context Menu

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

• Renaming folders
• Deleting folders
• Creating sub-folders
• Creating documents
• Uploading documents
• Refreshing folders
• Setting security

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.

Figure: Document Context Menu

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

• Renaming documents
• Deleting documents
• Refreshing documents
• Versioning documents
• Downloading documents
• Uploading new file versions
• Setting security

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