Cumulus Sites 8.6. Administrator Guide

Transcription

1 Cumulus Sites 8.6 Administrator Guide

2 Copyright 2012, Canto GmbH. All rights reserved. Canto, the Canto logo, the Cumulus logo, and Cumulus are registered trademarks of Canto, registered in the U.S. and other countries. Apple, Mac, Macintosh and QuickTime are registered trademarks of Apple Computer, Inc., registered in the U.S. and other countries. Microsoft, Windows, Windows Vista, and Windows NT are either trademarks or registered trademarks of the Microsoft Corporation in the U.S. and other countries. Other third-party product and company names mentioned in this document are trademarks or registered trademarks of their respective holders. Feedback? Tell us what you think about this manual. We welcome all of your comments and suggestions. Please comments to or via fax at CU-STA-861-MN-Z-2

3 3 Table of Contents Cumulus Sites 5 Overview How Cumulus Sites Works This Guide Overview: Adapting Sites to your Needs Essential Configuration Modifying the Look and Feel How to Configure Cumulus Sites Opening the Sites Configurator Configuring Cumulus Sites Downloading and Previewing Assets How to Customize Cumulus Sites The Customization Concept Basic Customization Tasks Themes: Customizing the Look and Feel Advanced Customization Cumulus Administration Tasks for Sites Before Publishing Catalog Publishing User Access Options for Downloading Prior to Public Access Tracking and Logging Tracking Usage Logging Video Support Appendix 39 Troubleshooting Users cannot Connect to Cumulus Sites Users cannot Open Collections Links Language of the User Inface Differs Asset Download and Preview not Possible Use of the FileSharing.info File with UNIX or Mac OS X Installations Index 43

4 4 CUMULUS SITES ADMINISTRATOR GUIDE

5 Cumulus Sites is the ideal Option to publish and market your digital assets on dynamically generated Web pages to the Internet. Users with a standard Web browser can comfortably search for cataloged assets, collect them into a collection basket and download them converted as required. Appropriate access rights are granted with the integration of the Cumulus user management. Configuring and customizing Cumulus Sites is easy and does not require any programming knowledge. Corporate branding is easily done, themes are supported, and content and layout changes can be made from within Cumulus. For more advanced changes, use CSS and JSP to make Sites perfect for your needs. This guide describes how to configure Cumulus Sites, how to use Sites to publish and distribute media assets over the Internet, and how to take advantage of its advanced features. Cumulus Sites

6 6 CUMULUS SITES ADMINISTRATOR GUIDE Overview Cumulus Sites is based on JSP- and Java -Technology. It supports Web 2.0 and uses Ajax (Asynchronous JavaScript and XML) which is a Web development technique for creating interactive web applications. Ajax enables the exchange of small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user makes a change. It increase a web page's interactivity, speed and usability. Cumulus Sites is installed on a web application server and communicates with your Cumulus Server via TCP/IP. It allows instant access over Java Server Pages (JSP) to Cumulus catalogs, which also applies to searching for digital assets. Catalogs published on the Web can be the same catalogs that are accessed by you or a member of your workgroup, so any changes made locally are immediately reflected on the Web. The web application server can be operated on the same machine on which the Cumulus Server is installed, or on another remote machine accessible through a TCP/IP connection. As with all Web server solutions, this configuration requires an appropriate Internet connection if you want your external visitors to have 24- hour access. Sites comes with a state-of-the-art design out of the box. The layout of catalogs as well as the searching and indication forms can be customized to suit any corporate design by changing the JSP pages included in the scope of delivery with high-level HTML editors. An adaptation and integration into your workflow is easy to realize. Customizable download possibilities enable Website visitors to choose a preferred method of asset delivery when accessing the assets. Sites will provide the data according to the user access rights configured in the user management of your Cumulus edition your data is secure at all times. Sites is the ideal solution to publish and market all digital assets to the Web. You do not need additional Cumulus Client licenses for visitors entering Websites based on Sites, as long as they have read-only access. However, Sites can be configured to allow write access to catalogs. In this case, Sites users can edit metadata and/or catalog and upload new assets, according to their permissions as specified in the Cumulus User Manager. If Sites is configured for write access, a Cumulus Client license is required for every user connected to Sites. NOTE: Even with write access generally enabled, the Cumulus Administrator can inhibit write access for certain users by means of the Force Read Only Catalog Access for Client Groups. The Force Read Only Catalog Access option overrides any individual user permissions and enables access to Websites based on Sites without the need of a Cumulus Client license. For details, refer to the Cumulus Administrator Guide.

7 CUMULUS SITES OVERVIEW 7 (Right top) Sites looks great after installation, but simple tweaks (below) can be performed without a single line of code. (Right bottom) Personal collections are easy to manage and use for file sharing. How Cumulus Sites Works Sites allows a Web designer to build a Website based on Java Server Pages (JSP) and JavaServlet technology. You can find more information on this technology and the handling of JSP pages on Oracle s Website: technetwork/java/index.html The Sites web application consists of a set of JSPX pages, a Cumulus tag library and a JavaBean. The tag library offers a set of custom tags that can be used in JSPX pages to add functionality on the server side to quickly build complex Websites without ever using the Java programming language. The JavaBean is a convenient way to store HTTP request parameters in a JSPX page. Cumulus Sites consists of the following components: the web application (including the JSPX pages) the Cumulus Java Classes Combining these components makes it possible for Web visitors to access your catalogs and assets. You can even continue to use and edit your catalogs while they are published, as changes made are immediately reflected online and your Web users will see them at the same time. In general, the language of the Sites user interface depends on the language of the employed Web browser. Sites tries to support the language the Web browser uses while requesting. If a specific language is not available, English is used by default. Alternatively, the Sites administrator can specify a default language to be used by the Sites user interface. If there are user interface elements that have no source for the specified language (e.g. field names, buttons etc), these elements will be displayed in English. By default, users can select a different Sites user interface language via the language chooser icons on the bottom of the page. The display of language chooser icons can be restricted by Sites administrator.

8 8 CUMULUS SITES ADMINISTRATOR GUIDE This Guide This manual describes how to configure and customize Cumulus Sites. Configuration essentially affects the functionality of Cumulus Sites. Customization, on the other hand, affects the appearance of Cumulus Sites, its look and feel. Before you publish any catalogs with Sites, you should read the section Cumulus Administration Tasks for Sites Before Publishing, starting on page 33, which summarizes the administration tasks to be performed with the Cumulus Client application. The manual concludes with some hints on troubleshooting. Additional documentation The installation, activation and initial configuration of Cumulus Sites is described in the Cumulus Web Solutions 8.6 Installation and Getting Started Guide. How to use a Cumulus Sites out-of-the-box installation with a Web browser is described in the Cumulus Sites Quick Reference manual. Furthermore, there is the HTML-based Cumulus Sites technical documentation which provides information on advanced customization of Cumulus Sites. It is installed together with Sites. Overview: Adapting Sites to your Needs Adapting Cumulus Sites to your needs is performed via the Sites Configurator. The Sites Configurator offers a graphical user interface for easy configuration. It is part of the Web Server Console which is installed along with Cumulus Sites by default. Basic customization tasks such as adapting logo, welcome and contact page to your corporate branding is easily done, too.just replace the corresponding images and text sections. The look and feel of Cumulus Sites can be easily modified using Cumulus view sets or preconfigured themes while more advanced changes can be performed via CSS. Advanced customization that requires structural changes is performed via JSP/JSPX. Normally, Sites uses the same language as the browser. However, if the browser uses a language not supported by Sites, the default language for Sites is English. Alternatively, the Sites administrator can specify a default language to be used by Sites regardless of the language of the browser. Whether users are allowed to change the language, the Record View Set and / or the theme depends on the settings defined via the Sites Configurator.

9 CUMULUS SITES OVERVIEW: ADAPTING SITES TO YOUR NEEDS Configure and Customize 1 Customize by replacing images 2 Configure via the Sites Configurator: Enable or disable the function and the display of the respective link. 3 Contents: configure via Sites Configurator Layout: customize via style sheet 4 Basic layout: customize via style sheet 5 Record layout: configure via Sites Configurator by specifying Record View Sets Essential Configuration The essential configuration for Sites is performed via the Sites Configurator from within the Cumulus Web Server Console. Here you set up Sites to run with your Cumulus Server installation, you define which catalogs are accessible via Sites, which search and sort criteria are offered. You name a default theme, a default Record View Set, a default Category View Set and, if applicable, language-specific Record View Sets for the display of records, and you list which templates are available for printing and which asset actions for download. The Record View Sets as well as the Print Templates and the Asset Actions are defined as usual within the Cumulus Client application. Selected Cumulus Asset Actions provided for download in Sites Selected Cumulus Print Template provided for printing from within in Sites TIP: Separators in Info Window and Info View If you use Record View Sets with separators, each field beneath a separator will show its field name in the Sites Info window and Info View. Via the Sites Configurator, you also specify the user access. You decide whether any website visitor needs an own Cumulus user account and if not which user account is used for such visitors. In addition to that, you specify the technical users Cumulus user accounts used for specific functions. The appropriate access permissions are granted with the integration of the Cumulus user management. The catalogs, templates and asset actions listed in the Sites Configura-

10 10 CUMULUS SITES ADMINISTRATOR GUIDE tor are always a superset. Depending on individual permissions a user might only get a subset. And note that the User settings of a user are also utilized, e.g the fields employed for searching via the search field are those defined for Quicksearch. Basic layout decisions are also made via the Sites Configurator. In addition to the selection of a Record View Set you can decide on using a theme for a customized graphical appearance. Themes are great for selecting different designs, colors etc. perfect if you don t need or want structural customization. Main collection page in classic layout (left) and configured to use the preconfigured dark & orange theme (below). Main collection page in classic layout with different Record View Set (left). This figure shows examples for different layouts

11 CUMULUS SITES OVERVIEW: ADAPTING SITES TO YOUR NEEDS 11 Recommendations for Public Use In addition to the essential configuration required for Sites, it is highly recommended to decide on the following configuration options before public use: Welcome page with login request displayed or not. If no welcome page is to be displayed: Login / Late login User permissions (especially for the guest user when late login possible) Adapt text Theme Switcher: displayed or not Language Switcher: displayed or not Record View Set(s): one or selection of Recommended: Create one or more Record View Sets especially for Sites Sorting criteria, sorting direction Categories and Filter pane: displayed or not Catalogs/Categories: which should be available Filter conditions: which should be available

12 12 CUMULUS SITES ADMINISTRATOR GUIDE The available download options are specified via Assets Actions. The available print options are specified via Print Templates. Modifying the Look and Feel NOTE: User s permissions can restrict access to actions and templates. For details see Configuring Cumulus Sites, p. 16. To modify the look and feel of your Sites installation, you can easily change the Records View Sets, the icons and images, the style sheets or employ a theme that changes the color scheme. For structural changes you need to modify the JSP and JSPX pages. What Welcome text / Contact info: How Login Page: yes or no Text of login and contact info page: edit a properties file (for details see Adjusting Text Sections, p. 31). Image swaps: Easy replacing, just size restrictions matter Display of Files View Sets: In-Cumulus edits, consistency with other clients OR create special Record View Set for Sites

13 CUMULUS SITES OVERVIEW: ADAPTING SITES TO YOUR NEEDS 13 What How Icon / Image Swaps: Easy quick fix changes, just size restrictions matter Style Sheets (CSS): Fine-tune icon / image swaps, change colors, more JSP, JSPX: Complete structural changes

14 14 CUMULUS SITES ADMINISTRATOR GUIDE How to Configure Cumulus Sites The appearance of Cumulus Sites can be easily modified using layout options within Cumulus. Basic configurations are performed with the Sites Configurator which is apart of the Cumulus Web Server Console. Advanced changes can be defined via CSS and JSP. While Sites is extremely flexible and completely customizable, it can as well be used out-of-the-box with only a minimum amount of configuration including basic decisions on functionality and layout. Opening the Sites Configurator Sites configuration tasks are performed with the Sites Configurator, a part of the Cumulus Web Server Console which is by default installed together with Sites or the Cumulus Web Solutions, respectively. NOTE: In order to work with the Sites Configurator, the user/administrator must have the Sites Administrator permission. For details on how to grant permissions, refer to the Cumulus Administrator Guide. To open the Sites Configurator: 1. Open a Web browser and enter the address of the Web Server console into the address field: <servername or IP address>:8080/serverconsole The Web Server Console login window is displayed. 2. Enter the name or the IP address of the Cumulus Server you want to administrate. 3. Enter the name and the password of the Cumulus Administrator or the user who has the permissions to perform the required administrative tasks. 4. Optionally, select a different language. 5. Click Login. The Web Server Console page is loaded.

15 CUMULUS SITES HOW TO CONFIGURE CUMULUS SITES Double-click Sites Configurator. A list with the configuration files of all available Sites installations inside the same web application server is displayed. 7. Double-click the file that belongs to the Sites installation that you want to edit, or select that file and click Load. The Sites Configurator is displayed, showing a row of tabs for different configuration options. The following sections describe the configuration options tab by tab. NOTE: Via the Add button, you can add more Sites configuration files to this list, as long as they are located on the same machine as the web application server.

16 16 CUMULUS SITES ADMINISTRATOR GUIDE Configuring Cumulus Sites The following sections describe how Cumulus Sites is configured via the various tabs of the Sites Configurator. The Server Tab This tab contains the information required by the Cumulus Server that serves the Cumulus Sites web application. Use this tab to define: Server Address IP address or DNS resolvable name of the machine running the Cumulus Server. Required Value! Write Access If activated, Write Access is enabled (depending on the users s specific permissions); if not activated, Write Access is disabled (regardless of a user s permissions). NOTE: If write access is enabled, a Cumulus Client license is required for every connected Sites user whether the users individual user permissions allow write access or not. However, even then it is possible to give certain users a read only access that costs no license by means of a Client Group. Just define an appropriate Client Group and activate the Force Read Only Catalog Access option for the respective user or role. For details, refer to the Cumulus Administrator Guide. Login Mode Drop-down list to select a login mode. Require Login Any website visitor must log in and therefore needs a Cumulus user account. Connecting to Sites opens a Welcome page with login prompt only. Late Login Website visitors are initially treated as guest users and can log in with their user name and password anytime later. Connecting to Sites opens the main page offering login possibility on top. A Cumulus user account and password must be specified for the guest user (see below).

17 CUMULUS SITES HOW TO CONFIGURE CUMULUS SITES 17 Guest User for Late Login Drop-down list to select the Cumulus user used for web visitors that are not logged in. If left empty, the default Cumulus Guest user account is used. Guest Password for Late Login The password for the Guest User account. Leave empty, if no password is required for the Guest User account. NOTE: All Passwords are stored encrypted! Direct URL User Drop-down list to select the (technical) user that is used to login to the Cumulus Server, when a direct URL is opened. Direct URL Password The password for the Direct URL User account. Leave empty, if no password is required for the Direct URL User account Admin User Drop-down list to select the (technical) user that resets passwords and creates user accounts. As this user must perform administrative tasks, appropriate permissions are required for this user: This user also is the one whose settings are employed for the landing page of the Send Collection Links (PIN) therefore this user should have access to all catalogs configured for Web Access and to all shared collections. TIP: Employ Live Filtering You can apply Live Filtering for this user in order to increase security, thus preventing anybody to send Collection Links that provide access to more files than you actually want anyone externally to see. Admin Password The password for the Admin User account. Leave empty, if no password is required for the Admin User account. NOTE: Direct URL User, Admin User and, if desired, Guest User, must be created via the Cumulus User Administration and must have appropriate permissions. For details, see Special User Accounts For Sites, p. 35 List of catalogs to be available for Sites users. In order to be available in Sites, a catalog must be opened by the Cumulus Server and Web Access must be allowed in its Catalog Settings. NOTE: Only the catalogs specified in this section will be displayed with Sites! Catalog Name Name of the Cumulus catalog. Root Category Name of the category to be displayed as the topmost level. Sites will only show records being assigned to that category or below. If no root category is specified, the whole category tree is displayed. TIP: Category hierarchy especially for Sites You can create a simple category hierarchy especially for Sites (making use of related categories) and define its topmost category as entry level for Sites. Edit Opens a window to specify the root category for the selected catalog. Add Opens a window with a drop-down list to select a catalog to be added to Sites.

18 18 CUMULUS SITES ADMINISTRATOR GUIDE The Layout Tab This tab contains different sections for the definitions of layout options for Sites. Use this tab to configure the appearance and functionality of Sites Record View Set Category View Set Design This section is for specifying Record View Set options. Default Record View Set Drop-down list to select the shared Record View Set to be used as default Additionally, you can assign specific Record View Sets to individual users or roles. Click Add to select a user or role and assign a Record View Set. The user or role is displayed in the User/Role list, together with the assigned View Set. You can modify such users or roles and remove them from the list using the according buttons. This section is for specifying Category View Set options. Default Category View Set Drop-down list to select the shared Category View Set to be used as default Additionally, you can assign specific Category View Sets to individual users or roles. Click Add to select a user or role and assign a Record View Set. The user or role is displayed in the User/Role list, together with the assigned View Set. You can modify such users or roles and remove them from the list using the according buttons. This section is for specifying several options that influence the appearance of Sites. Theme Available Themes Drop-down list to select a theme to used by Sites as default.

19 CUMULUS SITES HOW TO CONFIGURE CUMULUS SITES 19 Show Theme Switcher Activate or deactivate the checkbox to show or hide the theme switcher. which allows Sites users to select a different theme from the list of available themes. Slider Settings Settings defining the initial size of thumbnails, as well as the minimum and the maximum size they can be adjusted to via the slider. Left Section Configuration You can specify the width of the categories and filter column displayed on the left side of the Sites window. Furthermore, you can specify whether the category tree and the filter tree are displayed at all, and whether or not they are initially collapsed. Info Window This section is for adapting the appearance and functionality of the Information window. Enable If this checkbox is not activated, the Info window is not available to the Sites user and the corresponding icon is not displayed. Left section width (pixel) Specify the width of the left section of the Info window in pixel. Additionally, you can define the Field name column width: either activate Fixed and specify the desired width in pixel, or select Adapts to the longest field name to adapt the width automatically. NOTE: Field names are displayed only if the currently selected Record View Set contains separators. If the Record View Set does not contain separators, the Field name column width settings are ignored. For details on how to add separators to a view, refer to the Cumulus Client User guide.

20 20 CUMULUS SITES ADMINISTRATOR GUIDE Right section width (pixel) Specify the width of the right section of the Info window in pixel. Thumbnail size (pixel) Specify the size of the thumbnail that is displayed in the Info window in pixel. You can specify the width of the right and the left part of the Info window and the size of the thumbnail (in pixel). Display Social Network Icons If activated, icons providing links to social networks are displayed, allowing the user to share the record with selected social networks. Related files If activated, the related files list is displayed in the info window Find similar files If activated, a clickable list of all categories the file is assigned to is displayed. If Show as tag cloud is activated additionally, these categories are displayed as tag cloud. Enable annotations If activated, the annotation section is displayed. If Collapse annotations is activated additionally, the annotation section is collapsed initially. NOTE: Whether annotations are actually displayed or not depends on the permissions of the user. Enable tooltips If activated, a tooltip with further information is displayed when the mouse pointer rests on the thumbnail. You can define the size (in pixel) and the type of the tooltip (zoom, one column layout, or two column layout with thumbnail on the left side). Preview Window Thumbnail View This section is for adapting the appearance and functionality of the Preview window. Enable If this checkbox is not activated, the Preview window is not available to the Sites user and the corresponding icon is not displayed. You can specify the size of the preview image (in pixel). Enable annotations If activated, the annotation icon and the annotation section are displayed. If Collapse annotations is activated additionally, the annotation section is initially not visible. Enable discussion If activated, the discussion icon and the discussion section are displayed. If Collapse discussions is activated additionally, the discussion section is initially not visible. This section is for adapting the appearance and functionality of the Thumbnail view. Enable If this checkbox is not activated, the Thumbnail view is not available to the Sites user and the corresponding icon is not displayed. If thumbnail is clicked Drop-down list to select what happens when the user clicks a thumbnail: either the Preview window is displayed, or the Information window, or nothing at all. Enable tooltips if activated, a tooltip with further information is displayed when the mouse pointer rests on the thumbnail. You can define the size (in pixel) and the type of the tooltip (zoom, one column layout, or two column layout with thumbnail on the left side).

21 CUMULUS SITES HOW TO CONFIGURE CUMULUS SITES 21 Report View Collection Basket This section is for adapting the appearance and functionality of the Report view. Enable If this checkbox is not activated, the Report view is not available to the Sites user and the corresponding icon is not displayed. If thumbnail is clicked Drop-down list to select what happens when the user clicks a thumbnail: either the Preview window is displayed, or the Information window, or nothing at all. Enable tooltips if activated, a tooltip with further information is displayed when the mouse pointer rests on the thumbnail. You can define the size (in pixel) and the type of the tooltip (zoom, one column layout, or two column layout with thumbnail on the left side). This section is for adapting the appearance and functionality of the Collection Basket. Enable Add Page to Basket If activated, all records displayed on the current page can be added to the collection basket at once. Enable Add Collection to Basket If activated, all records in the current collection can be added to the collection basket at once. NOTE: This can result in a very large collection basket. Enable Send Collection Link If activated, the Send Collection Link function is enabled. Enable Show Base URL Chooser If activated, the Sites user can choose a base URL. Enable All Options If activated, all possible permissions are granted to the recipient by default; the Sites user can deactivate each of these permissions before sending. If deactivated, no permission is granted to the recipient by default; the Sites user must decide which permission(s) to be granted before sending the link. Enable Custom From Address If activated, you can specify a from address to be used with a sent Collection Link, or enable the Sites users to specify a from address themselves. If not activated, the address of the respective Sites user is used by default. Editable If activated, the Sites users may specify a from address themselves. Default From Address Specify the from address to be used instead of the address of the respective user, e.g. your company s address.

22 22 CUMULUS SITES ADMINISTRATOR GUIDE The Language Tab This tab contains options for language settings in Sites. Use this tab to configure: Initial Language Drop-down list to select the (initial) language for Sites: either according to the settings of the browser, or select a specific language. Show language Switcher If activated, the sites user can choose a different language using the language switcher icon. The list displays all languages the Sites user is allowed to select from. You can add more languages if desired; you can remove languages and modify the settings of any listed language using the according buttons. Modifying a language comprises changing the icon which represents the language in the language switcher, as well as specifying general and role/user specific Record View Sets and Category View Sets to be used with that language. The Account Management Tab This tab contains options for the creation of new (Cumulus) users via Sites. Use this tab to configure:

23 CUMULUS SITES HOW TO CONFIGURE CUMULUS SITES 23 Allow creation of new user accounts If activated, new users can sign up for using Sites. A Create Account button will be displayed. Template account for new users Drop-down list to select a template account to be used for new users. TIP: When preparing this template user account with the User Manager, you may want to consider setting the login to not active so that any newly requested account must be activated manually. Furthermore, it might be a good idea to mark user accounts that were created via Sites, e.g. by keeping a note in the Description field of the template user. Notify about new user accounts address of the user/administrator to be informed of users added via Sites account requests The list contains all fields a web visitor is offered to fill in when requesting a user account. If the respective checkbox is activated, the field is mandatory. You can add more fields to or remove fields from the table using the according buttons. Reset Password If activated, the user can reset his/her password. A Reset Password button will be displayed to the Sites user. Mail sender for reset password The address used for answering password reset requests. The Sort, Search & Filter Tab This tab contains different sections for the configuration of sort, search and filter options in Sites. Sorting This section is for specifying sorting options. Initial Sorting If activated, records displayed in Sites are initially sorted. Sorting Drop-down list to select a sorting criterion Direction Drop-down list to select the sorting order Configured Sorting fields List of record fields available as sorting criteria for the main collection and the collection basket. You can add more fields to, or remove fields from the list using the according buttons. Only fields that are activated for sorting in the Catalog Settings are offered here.

24 24 CUMULUS SITES ADMINISTRATOR GUIDE Searching Filtering This section is for specifying searching options. Configured Searching Fields List of record fields available for advanced search. These fields are displayed if the Sites user clicks on the plus sign under Filter Conditions. You can add more fields to, or remove fields from the list using the according buttons. Only fields that are activated for searching in the Catalog Settings are offered here. This section is for specifying filtering options. Configured Filtering Fields List of record fields available as filter bar entries in Sites with their existing values displayed. You can add more fields to, or remove fields from the list using the according buttons. NOTE: Employing filters influences the performance. The more filters are employed, the more load for the Cumulus Server. The Download & Print Tab This tab contains sections for the selection of Asset Actions and Print Templates available when items are downloaded from Sites. Asset Actions Print Templates This section is for specifying asset action options. The list displays asset actions that can be applied when assets are downloaded by Sites user. If the list is empty, all actions available to a user can be applied when downloading assets via Sites. If you add asset actions to this list, the user can only select from these asset actions. You can add asset actions to, or remove from the list, and you can modify asset actions. See below. This section is for specifying print template options. The list displays print templates that ca be applied when PDFs are created for download.

25 CUMULUS SITES HOW TO CONFIGURE CUMULUS SITES 25 If the list is empty, all print templates available to a user can be applied. If you add print templates to this list, the user can only select from these print templates. You can add print templates to, or remove from the list, and you can modify print templates. See below. NOTE: The following applies to both sections, Asset Actions and Print Templates: With asset actions or print templates, the following properties can be specified: Icon Icon to be displayed for the action or template only if this action/ print template is one of the first four available for a user (only first four are denoted by icons). Display Name Key There are several ways to provide a display name for an Asset Action/Print Template: If no value is given, the name of the Asset Action/Print Template (as defined via the Cumulus Client Preference dialog) is displayed if provided, in the selected browser language or the default language. If you enter a name as value, this name will be displayed for all languages If you enter a key that is included in the sitescustomer.properties file, the according text will be displayed if provided, in the selected browser language or the default language Description Key There are several ways to provide a description for an Asset Action/Print Template: If no value is given, the description saved with the Asset Action/Print Template (via the Cumulus Client Preference dialog) is displayed if provided, in the selected browser language or the default language. If you enter a description as value, this description will be displayed for all languages If you enter a key that is included in the sitescustomer.properties file, the according text will be displayed if provided, in the selected browser language or the default language. The Servlet Tab This tab contains different sections for the configuration of the servlets which execute pre-transfer asset actions. These pre-transfer actions are performed on thumbnails, assets and previews before they are published to the web. Pre-transfer actions allow you for example to have image assets (or their previews or thumbnails) watermarked or converted to gray scale images before they are transferred to the users web browser.

26 26 CUMULUS SITES ADMINISTRATOR GUIDE If an error occurs while performing one of the actions, a Cumulus logo image will be transferred instead of the respective asset, preview or thumbnail. Thumbnail Servlet Asset Servlet Preview Servlet This section is for specifying options for the Thumbnail Servlet. Default Pre-Transfer Asset Action Drop-down list to select an action to be performed on the thumbnail of an asset before the thumbnail is transferred to the user s web browser. Asset Actions to be processed before items are published to the web List of actions to be performed for users with specific permissions before the thumbnail is transferred. Click Add to select a permission and the asset action to be performed for all users with the respective permission. The names of the permission and the selected asset action are added to the list. You can modify and remove previously added permissions using the according buttons. Direct URL max. size (pixel) Maximum size allowed for thumbnail display via URL. For security reasons specify the maximum value required by your users needs. This section is for specifying options for the Asset Servlet. Default Pre-Transfer Asset Action Drop-down list to select an action to be performed on an asset before it is transferred to the user s web browser. Asset Actions to be processed before items are published to the web List of actions to be performed for users with specific permissions before the asset is transferred. Click Add to select a permission and the asset action to be performed for all users with the respective permission. The names of the permission and the selected asset action are added to the list. You can modify and remove previously added permissions using the according buttons. This section is for specifying options for the Preview Servlet. Default Pre-Transfer Asset Action Drop-down list to select an action to be performed on the preview of an asset before the preview is transferred to the user s web browser. Asset Actions to be processed before items are published to the web List of actions to be performed for users with specific permissions before the pre-

27 CUMULUS SITES HOW TO CONFIGURE CUMULUS SITES 27 view is transferred. Click Add to select a permission and the asset action to be performed for all users with the respective permission. The names of the permission and the selected asset action are added to the list. You can modify and remove previously added permissions using the according buttons. Use Thumbnail If activated, thumbnails are displayed when previews are requested and all settings for preview caching are ignored. This option is most useful when catalogs are configured to capture high-resolution thumbnails when cataloging assets or updating records. It is also helpful when previews are requested for file formats for which Sites is unable to generate previews, such as InDesign and PowerPoint files. Use Preview If activated, previews (i.e. JPEG images) are displayed which can be cached to improve performance. Use cache If activated, the previews are cached according to the following settings: Quality The image quality of the cached preview images, where 1 denotes the lowest quality (smaller file size) and 10 the highest (larger file size). Default value is 8 which provides the best compromise between quality and file size. Imagesize (pixel) The size of the bounding box (in pixel) for the previews stored in the cache. The default value is 2048 pixels. The aspect ratio of images is always maintained. NOTE: The size in which the cached preview image is displayed depends on the size defined for the bounding box as well as on the size defined by the logged-in user s preference settings for Preview View. Always the smaller of both values is taken. Max. entries Maximum number of preview images permitted in the cache folder (default: 100). When this number is reached, the cached preview image not accessed for the longest amount of time is replaced with each new preview request. If set to 0, the number of entries is unlimited. Max size on disk (MB) Maximum hard disk space (MB) available to the cache folder (default: 200 MB). When this value is reached, the cached preview image not accessed for the longest amount of time is replaced with each new preview request. If set to 0, the amount of hard disk space that can be used by the cache is unlimited. You can loosely estimate the disc space required for your cache folder by multiplying your maximum count value by the file size of a typical asset preview from your catalogs, stored at your chosen quality setting, at the size of your bounding box. Cache directory Path to the directory to be used for caching NOTE: You can either define the amount of entries or the available hard disk space, or you can define both. If both are defined, the limit reached first will initiate replacing the entry not accessed for the longest amount of time with a new one. Stopping and restarting the web application or the web application server does not empty the cache! Direct URL max. size (pixel) Maximum size allowed for preview display via URL. For security reasons specify the maximum value required by your users needs.

28 28 CUMULUS SITES ADMINISTRATOR GUIDE The Customizations Tab This tab contains the customizations available with your Sites installation. To use a customization, you must activate the respective check box. NOTE: Keep in mind that the customizations listed here are not Cumulus Sites standard functions. Though they are tested and work well in Sites 8.6, Canto can not guarantee that they will be supported in future releases. Keep also in mind that some of these customizations need additional preconditions to be fulfilled. For example, if you want to offer a terms & conditions page, or custom category landing pages, you have to prepare such pages in advance. The History Tab This tab displays a list of former versions of the Sites configuration. A new entry is added each time you save changes made with the Sites Configurator. While saving, you can add a description of your changes which might be helpful in order to keep track of them. You can load an old configuration and make it current again, and you can delete old configurations. Downloading and Previewing Assets To enable Sites to fulfill download or preview requests for assets, these assets have to be either stored on the machine running the Sites web application, or the Cumulus Server must have access to these assets. With Sites or the Cumulus Server running under UNIX or Mac OS X, the assets can only be accessed if the FileSharing.info file is adapted to your Cumulus configuration. (See Use of the FileSharing.info File with UNIX or Mac OS X Installations, p. 40, for details.)

29 CUMULUS SITES HOW TO CUSTOMIZE CUMULUS SITES 29 How to Customize Cumulus Sites The Customization Concept Sites can be used out-of-the-box but is also extremely flexible and completely customizable using high-level HTML editors. The JSPX pages in the scope of delivery can be modified and enhanced on HTML, CSS and Java level. Cumulus custom tags makes your work much easier. Customization for Cumulus Sites can be performed on different levels. Customizations concerning the layout (images, icons, style sheets) are stored as subfolders of the themes folder. Each of these subfolders provides an entry in the list of themes the Sites users can choose from with the theme switcher provided that the theme switcher is set to be visible via the Sites Configurator. This makes changing the layout of Sites really easy. Customizations concerning structural aspects, which are performed via modified JSP and JSPX pages, are stored as subfolders of the customizations folder and are copied to temporary folders of your web application server once the web application server is started. This concept makes updates easy and allows for different customizations sources. Sites out-of the box folder structure. Inside the customizations and themes folders you can create any number of subfolders containing your customized files. Inside the customizations folder you may as well use Zip files containing the customized files. In any case, the structure of the subfolders or Zip files containing customized files must resemble the subfolder structure of the respective original folders. Additionally, Canto provides some examples for customized functional additions that can be enabled or disable via the Sites Configurator. See The Customizations Tab, p. 28, for details.

30 30 CUMULUS SITES ADMINISTRATOR GUIDE IMPORTANT! Do not touch the original folders! The original folders as they are delivered by Canto guarantee that all files Cumulus Sites needs are provided. So don t change any file, nor the subfolder structure. To have multiple folders or Zip files in the customizations folder allows you to use multiple customization approaches, e.g. modules from Canto partners that provide additional functionality. Once the web application server is started, the folders are copied and the Zip files are unpacked to temporary folders of your web application server in the following sequence: the folder original inside the customizations folder (to make sure all required files are there) all other folders/zip files inside the customizations folder (to provide all your customizations) Customizations Process at Tomcat Start Copied to live area in order: (1) original, then (2) user folders (order varies by operating system) IMPORTANT! You can have as many subfolders or Zip files inside the customizations folder as best fit your needs, but make sure no file is contained twice or more times (last copied would win). However, this rule does not apply to XSLT files used for advanced customization tasks (see Advanced Customization, p. 33), because XSLT files are not copied but used to alter the original file. NOTE: After changing any CSS or JSPX files it is strongly recommended to empty the cache of your Web browser before testing your customizations, as many Web browsers keep CSS and JSPX files in their caches for quite a long time.

31 CUMULUS SITES HOW TO CUSTOMIZE CUMULUS SITES 31 Basic Customization Tasks Adapting Cumulus Sites to your company s corporate identity, is a simple case of adjusting some text, replacing images and adapting the main style sheet. Customized Welcome page in the classic layout (left) and using the preconfigured dark & orange theme (right). Adjusting Text Sections The text of the welcome and contacts pages is stored in a Java properties file that can be edited with any editor applicable. Applicable editors are e.g. the Resource Bundle Manager (can be downloaded for free from the ICU website: or the prbeditor (for immediate use available under: The properties file is named sitescustomer.properties and stored in a bundles folder inside the WEB-INF of the web application, e.g. under: C:\Program Files\Canto\Cumulus Sites\apache-tomcat \webapps\Sites\WEB- INF\classes\resources\bundles The properties file supports multiple languages and is provided as a resource bundle which is a group of property files with the same base class name. The base class name is always *.properties and contains the English strings. As Cumu-

32 32 CUMULUS SITES ADMINISTRATOR GUIDE lus is localized to German, French, Spanish, Japanese, and Korean by default, each resource bundle contains the additional language files. An additional language file can be identified by an underline and the two letter ISO 639 language code appended to its name, e.g.: *.properties, *_de.properties, *_fr.properties, and *_ja.properties. Edit the sitescustomer.properties resource bundle according to your needs. Resource keys starting with contact refer to the Contacts page and those starting with login to the Welcome page. NOTE: You can leave keys empty at will, if you do not want to have the respective text displayed. However, do not delete any key! Themes: Customizing the Look and Feel In addition to applying configured Record View Sets you can modify the layout of Sites by means of themes which contain different sets of images, icons or style sheets. Sites provides two themes by default, original and darkorange. The respective files are stored in folders of the same name within the themes folder. To provide your own theme(s), duplicate either the original folder or the darkorange folder, give it an appropriate name and modify the content to your needs. Which theme is displayed initially when a user connects to Sites is defined in the configuration file (original by default). You can also define whether a theme switcher is displayed in Sites, thus allowing users to switch between available themes. Replacing Images and Icons Images are kept in the images folder of each theme. Exchange existing images with different images of the same name, format and proportions. If the format and the proportions of the replaced file and the new file are different, the style sheet has to be adjusted. Examples To replace the logo: create a PNG file of your logo and name it logo.png file, then copy this image file to the images folder of your customization folder. To replace the images displayed on the Contacts page: create JPEG files of the images and name them contact_b.jpg (image on the left) or contact_sf.jpg (image on the right), then copy the image files to the images folder of your customization folder. Style Sheets As the provided JSPX pages use style sheets, changing colors and fonts is very easy. Editing style sheets requires only basic HTML knowledge. Just open the corresponding CSS file (located in the styles folder of your themes folder) and adapt the font size, font family or color parameters to your needs. Canto provides two main style sheets: theme.css, defining the colors

33 CUMULUS SITES CUMULUS ADMINISTRATION TASKS FOR SITES BEFORE PUBLISHING 33 Advanced Customization structure.css, defining all the rest oft the page elements as well as the alignment of the elements on the page There are additional style sheets for specific object types: ie7.css for the MS Internet Explorer 7 jstabbedpane.css used by all Web browsers for displaying tabs (e.g. Asset Reference tabs) datepicker.css containing the layout for the date picker Canto recommends to only customize the theme.css style sheet to adjust the colors, and the structure.css style sheet to adjust the layout of Sites to you needs. Canto provides JSPX pages that you can use as they come or modify them to suit your needs. Customized JSPX pages are also kept in a separate folder which will be copied during runtime. To customize existing JSPX page you can also apply XSLT style sheets. For more information on customizing JSPX pages, see the HTML based Sites technical documentation that you can find in the DocumentationSites folder in the Cumulus Sites installation folder. The Cumulus tag library contains custom tags that can be used in JSPX pages to add functionality on the server side to quickly build complex Websites without ever using the Java programming language. If you use Java to access the lowlevel Cumulus Java Classes Objects, you need to be a member of the Cumulus Developer Program. If you are interested, contact: cdp@canto.com Cumulus Administration Tasks for Sites Before Publishing Catalog Publishing In addition to the configurations and customizations you made some administrative tasks are necessary or recommended that have to be performed using the Cumulus Client application. The following sections describe what you have to consider performing these tasks. Required is that you provide catalogs, optionally you can: Create special Sites user (late login, template user for login request Create special users for special functions Create special Record View Set(s) Create special Asset Actions for downloading Create special Print Templates You should follow certain guidelines in order to ensure smooth access to the catalogs you publish on the Internet. Cumulus Sites can publish as many catalogs at one time as the memory permits. To be published on the Internet, a catalog must have the Share Catalog and Allow Web Access options activated in its preferences (in the Cumulus Client, select Edit > Preferences > Catalog Settings). This options can also be set in the Catalog Access dialog. Catalog publishing services are available as soon as you start your web application server software. A catalog and can be accessed by Web visitors via Sites, if it is included in the list of available catalogs in the Catalog Access dialog, its Share Catalog and Allow Web Access options are activated, and it is included in the Catalogs list on the Server Tab of the Sites configurator.

34 34 CUMULUS SITES ADMINISTRATOR GUIDE NOTE: In order to have the catalogs available to users, they have to be assigned to the users. For details on how to do this, see the User Manager chapter of your Cumulus Edition s Administrator Guide. Publishing Catalogs to the Internet To publish individual catalogs on the Internet: 1. Install Cumulus Sites components as described above. 2. From any Cumulus Client, log on to the Cumulus Server as Cumulus Administrator. 3. Each catalog you plan to publish on the Internet has to be included in the list Catalog Access (File > Open Catalog). If the desired catalog is not included you have to add it to the list. 4. For each catalog, enable the Share Catalog and Allow Web Access options in the Catalog Access window. Click OK. 5. Add an entry for the catalog to the catalog table in the Sites configurator. (See The Server Tab, p. 16.) 6. Launch your Web browser and enter the following path: server address]/sites e.g.: Depending on your configuration (late login possible or not) the welcome page or the main collection page is displayed. Under Categories you will find a list of those catalogs (or their categories defined as rootcategory ) that were assigned to the user employing the User Manager application of your Cumulus Edition. NOTE: Catalogs Missing? Sites will provide access only to the catalogs for which a user has the appropriate permissions. The catalogs configured via the Sites Configurator are a superset. For example, if 5 catalogs are listed there and guest users only have permission to access to 2 of these catalogs, then the other catalogs are ignored. Always check whether a catalog is accessible for a user and also check whether the Allow Web Access option is activated. Searching and Field Indexing The Sites search field can offer type-ahead search also called incremental search or find as you type (FAYT): As the user types into the search field, a list of matching words appears in a drop-down list. This list is limited to 20 items by default and is sorted according to the frequency of occurrence of the words. With Sites these matching words are taken from the contents of string fields that are activated for Word-Searching. To enable type-ahead search, you have to activate the Index for Word-Searching option of those string fields offered to users as Quicksearch fields. The option belongs to the Indexing properties of a field defined in the Catalog Settings. NOTE: If you have defined any access restrictions, e.g. via Live Filtering, note that type-ahead search is not aware of access permissions and therefore shows all matching words available in a catalog s index. User Access The user access is managed by the User Manager of your Cumulus edition. As soon as a user has been forced to log in rather than having free access, the user

35 CUMULUS SITES CUMULUS ADMINISTRATION TASKS FOR SITES BEFORE PUBLISHING 35 login name is available to Sites. Cumulus then uses this name to check the Cumulus permission settings for catalog and sets access and asset transfer privileges. IMPORTANT! Never log in to the Sites web application as Cumulus Administrator! For user access of Sites, keep the following in mind for a user s description in the User Manager: If the Address field does not contain a valid address, the user cannot make use of any of the Sites s functions and cannot reset the password. These are the Application Permissions that are important for Sites users: Open Catalog required for opening the catalog(s) Transfer Assets required for the display of previews if asset is under version control and/or server/client-transfer is necessary Download Assets required for downloading assets Assets Special User Accounts For Sites Some special user accounts are requested by the Sites configuration file. Canto recommends you to create special user accounts for Sites. Have the following in mind when creating them with the Cumulus User manager (Server Console > User Manager): Guest User The Cumulus user whose settings are used for web visitors that are not logged in Direct URL User The (technical) user that is used to login to the Cumulus Server, when a direct URL is opened. Recommended permissions are: Open Catalog, View Item for records, and TransferAsset Admin User The (technical) user that resets passwords and creates user accounts. In addition this user is employed to perform all administrative tasks. Required permissions for this user are: Administrator Permissions (at least User Administrator) Open Catalog required for opening the catalog(s) View Item for records required to get the thumbnails displayed $Transfer Asset required if the record s asset is under version control and/ or server/client-transfer is necessary NOTE: The adminuser user s settings are employed for the landing page of the Send Collection Links (PIN) therefore this user should have access to all catalogs published on the Internet and to all shared collections. Source User Template user account for new users. Any existing user can be selected as Template User via the Sites Configurator. TIP: When setting up the template user account consider setting the login to not active so any newly requested account must be activated manually. But then, remember to inform the new users once their accounts are activated. Furthermore, it might be a good idea to mark user accounts that were created via Sites, e.g. by keeping a note in the Description field of the template user.

36 36 CUMULUS SITES ADMINISTRATOR GUIDE Options for Downloading Prior to Public Access The options for downloading the collection basket are provided as Cumulus Actions. Your Web users can select a Cumulus Action for downloading the entire collection basket. Cumulus Actions are defined in the Preferences dialog of the Cumulus Client application. When defining a Cumulus Action for downloading be aware of the following differences: Show Dialog Option With Sites the Show Dialog option for Cumulus Actions will not be interpreted. For Internet users no dialogs will be displayed and the pre-configured values will be used to perform the Action. If no pre-configured values are set, the factory defaults will be used. Processing/Packing Be aware that Sites offers as Zip commands for downloading as default. Either you don t include the ZIP AssetProcessor in your Actions or you deactivate the as Zip commands of Sites Delivering With Sites the selected delivering module for an Action is ignored. The delivering is always download. Asset Handling Set With Sites, we strongly recommend you to select specific Asset Handling Sets for Actions and to select shared ones which are available for your Sites users. Fore more information on Cumulus Actions, see the section Cumulus Actions in the Cumulus Client User Guide. Before you let any users work with your Sites configuration, access each page to improve access time as each JSPX page has to be compiled. The compiled JSPX pages are stored in the temporary folders of your web application server; e.g.: tomcat...\work\catalina\localhost\cumulus\org\apache\jsp\ng You should delete these folders after the modification of any of the JSPX pages and after the de-installation of Sites.

37 CUMULUS SITES TRACKING AND LOGGING 37 Tracking and Logging Tracking Usage Cumulus Sites offers flexible tracking and logging facilities. Cumulus can generate reports based on catalog statistics (number of previews, print outs, mail to, etc.) and reports based on Cumulus Server activity, such as successful and failed search results, client connection rates, and more. Tracking options available for reports generated by Cumulus. If your Cumulus Server is set up for tracking, it works for Cumulus Sites as well. For more information, see the Cumulus Administrator Guide, section Report Manager. Logging Sites also offers very flexible logging facilities that allow you to collect various log messages and write them to different destinations. You can log events such as downloads of an asset and previews of an asset and you can also track custom tag usage and JSPX page generation for debugging. The logging facilities of Sites are based on the log4j library of the Apache Software Foundation. You can configure the output of all log messages by modifying the log4j.xml file (found in the subfolder WEB-INF of the Sites folder inside the webapps folder of your web application server folder). NOTE: In the pre-installed log4j.xml file, all log files are specified by relative path names. This way they are created relative to the directory that your web application server is started from. To make sure the log files are always created in the desired directory, you should change all log file paths in log4j.xml to absolute path names.

38 38 CUMULUS SITES ADMINISTRATOR GUIDE NOTE: Absolute Path Names under Windows! log4j uses the backslash as an escape sequence. That s why you should either use slashes or a double backslash for absolute path names in the log4j.xml file. Example: To define "C:\logs\cumulus.log" as a log file, enter <param name="file" value="c:/logs/cumulus.log" /> OR <param name="file" value="c:\\logs\\cumulus.log" /> For details on the configuration of log files, see the Sites technical documentation. Video Support Cumulus Sites out of the box supports the Video/FLV container format. As Cumulus Sites runs a Flash video object to play the files by default, the supported video and audio codecs are limited by the codecs that Flash supports. Other container formats can be supported, but they require configurations and need to be extensively tested. This means that the file format of the video to be cataloged has to be Video/FLV. So that Cumulus can identify the file during the cataloging process and can correctly set the value for the record field File Format Identifier. This field is interpreted by Cumulus Sites to provide the ability of playing movies.

39 This appendix offers troubleshooting information helping you to quickly solve common problems. Appendix

40 40 CUMULUS SITES ADMINISTRATOR GUIDE Troubleshooting This section contains frequently asked questions and their possible solutions. Users cannot Connect to Cumulus Sites Other users cannot open the Sites web page using the correct URL. What can I do? Add the port number (default 8080) to the exceptions list of the firewall of the machine running the web application server. Users cannot Open Collections Links Users cannot open collection links send via Sites. What can be the reason? Check the URL whether an unresolvable internal address is used or an incorrect external address. Note that the address a user has employed for connecting to Sites is used for creating collection links. Language of the User Inface Differs My Sites installation is English but the user interface is displayed in German. By default, the language of the Sites user interface depends on the language of the employed Web browser. Sites tries to support the language the Web browser uses while requesting. If a specific language is not available, English is used by default. Beyond that, Sites can be configured to use a certain language for the user interface, either initially or always. Whether you are able to change the language of the Sites user interface on the fly by using the language chooser icons at the bottom of the web page depends on the settings made by the Sites administrator. Asset Download and Preview not Possible How is the Cumulus Server able to access an asset and which settings are required? There are two possible reasons for most problems: permission problem: The user under which the Cumulus Server is running might not have read permission for these assets. Check for the right permissions. wrong entries in the FileSharing.info file: The Cumulus Server is not able to create correct UNIX asset references due to wrong entries in the FileSharing.info file. Check the FileSharing.info file. (For details, see below.) Use of the FileSharing.info File with UNIX or Mac OS X Installations What is the FileSharing.info for? If a user wants to preview or download an asset via the Internet, Cumulus Sites or the Cumulus Server must have access to the actual asset. To do this Cumulus reads the stored asset reference and uses it to find the asset. This is also called resolving an asset reference. If assets have been cataloged by Mac OS or Windows Clients, their asset references cannot be resolved by Cumulus under UNIX or Mac OS X. So Cumulus needs to create UNIX asset references based upon the Mac OS or Windows file system asset references. This is done by employing a special file that contains information on how a Windows or Mac OS asset reference should

41 APPENDIX TROUBLESHOOTING 41 be transferred to a corresponding UNIX reference. This special file is named File- Sharing.info. The information stored in this file must be adapted to your Cumulus configuration. You can have a separate FileSharing.info file for your Cumulus Sites installation. If a FileSharing.info file is not available with your Cumulus Sites installation, the FileSharing.info file of your Cumulus Server installation is used. The FileSharing.info file for your Cumulus Server installation can be edited with a utility provided by the Remote Admin module of the Server Console. If you want a separate FileSharing.info file for your Cumulus Sites installation, this file must be adapted manually to your Cumulus configuration. For example: The file picture.jpg is stored on a UNIX or Mac OS X file server and can be accessed by Windows via the following path: \\FILESERVERWINNAME\WINVOLUMEONSERVER\images\ by Mac OS via the following path: *:FILESERVERMACNAME:MACVOLUMEONSERVER:images: Under UNIX or Mac OS X this file is stored under: /shares/volume/images/ The Filesharing. info needs the following information to create the correct UNIX asset reference based upon the given Windows asset references: [Windows] # Begin of the Windows section Server Name = FILESERVERWINNAME Volume Path = /shares/volume Volume Name = WINVOLUMEONSERVER The Filesharing. info needs the following information to create the correct UNIX asset reference based upon the given Mac OS asset references: [Macintosh] # Begin of the Macintosh section Server Name = FILESERVERMACNAME Volume Path = /shares/volume Volume Name = MACVOLUMEONSERVER Make sure that you enter the exact server names and volume names (case sensitive) as you see them from the appropriate platform (in the Chooser on Mac OS and Explorer on Windows). Never enter the UNIX server name. NOTE: If HELIOS EtherShare is installed on the machine that runs the Cumulus Server, you do not need to update the Macintosh section settings of the File- Sharing.info file manually. Cumulus does this automatically. If you have also installed PCShare, you do not need to update the Windows section settings manually.

42 42 CUMULUS SITES ADMINISTRATOR GUIDE

43 43 Index A Access improve access time 36 user 34 C Catalogs publishing to Internet with Sites 34 Configuring Sites 14 Copyright 2 Cumulus Actions 36 Customizing 29 concept on 29 Contacts page 31 easy tasks 31 replacing images and icons 32 replacing logo 32 style sheets 33 Welcome page 31 D Downloading, options for 36 F FAQ s 40 File Sharing information 40 L Language of user interface 7 Logging 37 P Permissions for users 35 Previews using record thumbnail 27 Publishing catalogs on Internet 33 Publishing catalogs with Sites overview 33 publishing to Internet 34 S Sites configuring 14 customizing 29 logging 37 overview 6 publishing catalogs to Internet 33 Sites Configurator opening 14 T Themes 8, 29, 32 Tracking usage 37 Troubleshooting 40 U User access 34 creating account function 23 important permissions 35 User data required for functions 35 O Overview Adapting Sites To your Needs 8 Cumulus Sites 6