0 Introduction

   0.1 Special Thanks

1 Installation

   1.1 Tryout Version
   1.2 The Example Catalog
   1.3 Integration of UMP4 technologies into UMP3 web application
   1.4 Update your UMP web application to run with a newer Cumulus Server installation
   1.5 Cumulus User Management: 'Simple Mode' or 'Advanced Mode'

2 Usage

   2.1 How to publish a Cumulus Catalog with User Management Pro
   2.2 How to create a new user to access the web application
   2.3 User Management Pro User Permissions
   2.4 How to define a search query for UMP
   2.5 How to add a new language to UMP

3 UMP User Management

   3.1 Groups
   3.2 User Name Filter
   3.3 Send Email to Users
   3.4 Modify Single Permission
   3.5 Copy Permissions
   3.6 User List
   3.7 Labels

4 UMP User Permission: Restrict Access to Records / Categories

   4.1 Record Restriction: Restrict Search
   4.2 Record Restriction: Record Filter
   4.3 Record Restriction: Boolean Record Filter
   4.4 Category Restriction: Category Filter
   4.5 Category Restriction: Boolean Category Filter

5 UMP User Permissions

   5.1 Welcome Text
   5.2 First Search and First Search Name
   5.3 Sort Order and Direction
   5.4 QuickSearch Query Fields
   5.5 Control Download Categories
   5.6 Control Email Categories
   5.7 Master Categories
   5.8 Default Record View
   5.9 Localisation
      5.9.1 Localisation of the Web Application
      5.9.2 Localisation of Catalog Names
      5.9.3 Localisation of Category Names
      5.9.4 More Localisations
   5.10 Modify Records and Categories (ICP only)

6 Miscellaneous

   6.1 Cumulus Client Connection
   6.2 Disable 'Save Permissions' on a UMP demo server
   6.3 Filter group/username on UMP_Admin startup
   6.4 Auto Login if only one catalog available
   6.5 Some additional modifications in UMP8

7 Feedback & Support

8 Version History

The User Management Pro Web Application

The User Management Pro is an extension to the Canto Cumulus Web Publisher Pro (WPP) or Internet Client Pro (ICP) Option. This product helps you to restrict the user's access to the categories and records in the Cumulus catalog. With the Web Publisher Pro or Internet Client Pro you can only give access or assign rights to a user for all the records and all the categories in the catalog. With the 'User Management Pro' you can define the access right for every record and every category per User!

The version comes with a multi language web application. The following languages are supported out of the box: 'English', 'German', and 'French'. Additional languages can be added by the Cumulus administrator. Also the Cumulus category lists can have more than one language. The user of the web application can switch between languages at runtime. So with the 'User Management Pro' you can have e.g. an English Cumulus catalog with an English category tree and publish it also in a 'German' and 'French' Web Interface.

For each user the configurable QuickSearch function can search in different catalog fields. The user has a pre-defined sort order and sort direction and can change the sorting by selecting a sort field from a list. This version also makes the Actions Menu configurable for each user. So different users can have different options to convert files before they download them.

You can show or hide different records and categories from each user and also enable or disable the following functions just by one click in the catalog: View Menu, Record Menu, Image Menu, Number of rows and columns, the Sort Menu, QuickSearch, Advanced Search, Record Information, Preview, Collection Basket, Download, Email and Conversion. The download and email functionality can be configured for each user and for each and every single file (!) cataloged.

Remark: it is only possible for the user to open one catalog at a time with the help of the 'User Management Pro'.

Do you need additional functionality in the web application? We develop additional functionality based on your need. Send an email with your feature requests by clicking here.

0.1 Special Thanks

A special thanks to all who have contributed to the development and improvement of the User Management Pro product. Very special thanks to the following people who came up with innovative ideas to improve User Management Pro:

Black Eye Digital, Mr. Bryan Taylor, Dallas, Texas, USA

ThyssenKrupp Marine Systems, Mr. Jörg Klüver, Mr. Michael Specht, Hamburg, Germany

Thank you very much to our Spanish Partner Electronic Publishing Systems S.L. (special thanks to Francisco Villaverde), who localised the software and provided us with the necessary strings. Thank you very much to our French Partner Avista Systems (special thanks to Pierre Saint Michel), who localised the UMP web application.

If you have downloaded your version from the web, unzip the file 'UserManagementPro8.zip'. A folder named 'UserManagementPro8' will be created. Otherwise copy the folder 'UserManagementPro8' from your product CD-ROM onto your harddisk.

UMP8 comes with different web applications that you will find in the 'Installation' folder:

User Management Pro Administration Web Application (UMP8_Admin.war)

The UMP Admin web application can be used by the Cumulus Admin to set the user's permissions used in the UMP web application.

User Management Pro Web Applications ('UMPn_WPPn.war', 'UMPn_ICPn.war')

The UMP web applications are modified Cumulus Web Publisher Pro 3.0/7.0/7.5/8.0 or Cumulus Internet Client Pro 3.0/7.0/7.5/8.0 web applications. Please use the appropriate web application for your WPP/ICP installation:

Copy the UMP web application that belongs to your WPP/ICP installation (e.g. 'UMP8_WPP8') and the 'UMP_Admin.war' file, which you can find in the folder 'Installation', into your Tomcat web application folder ('...myTomcat/webapps'). Tomcat will recognise the new archive files and will unpack them into folders with the corresponding names ('UMP8_WPP8' and 'UMP8_Admin'). Now you can access the new web applications at 'http://myServer:8080/UMP8_WPP8/' or 'http://myServer:8080/UMP8_Admin/' (if your web application server listens to port 8080 (standard setup of Tomcat)). The basic pages are the pages of the Cumulus 'Web Publisher Pro' or 'Internet Client Pro' with the functions of the 'User Management Pro' added.

The User Management Pro web application comes in demo mode. Without a serial number the software will allow access for only 5 minutes and will log you out after this period of time. If you already own a full version of the product or received a serial number with a time limitation, provide the serial number in the UMP Admin web application. You can order a time limited serial number that unlocks the software for 30 days by email here. A serial number for UMP for ICP can also be used with UMP for WPP to unlock the version!

Important remark: When the user accesses the first page of the Cumulus Web Publisher Pro or Internet Client Pro, the web application evaluates the name and version of the web browser. If the browser is not Mozilla Firefox, Internet Explorer (from version 5) or Netscape (from version 6) or Safari under MacOS X, the user is linked to the folder 'Compatible', where he gets the information to update or change his version of the web browser. The pages that support older web browsers are not implemented in UMP8.

Cumulus Java Classes Serial Number

UMP8 uses a Cumulus Client connection to read necessary information out of your Cumulus catalogs. Therefor it is necessary that you have a valid Cumulus Java Classes (CJC) Serial Number installed in your Cumulus installation. If you do not yet have a valid CJC serial installed, add the JC serial as an option serial number to your Cumulus installation. You can do this as usual by using the Cumulus Server Console or by using the Cumulus Remote Admin through your web browser. You will get a new Cumulus Activation Key from Canto that will also unlock the Java Classes.

The Cumulus Java Classes serial numbers are provided by Canto for free. Here are some the serial numbers for the latest Cumulus versions:

UMP only needs the read only access serial number installed to provide full functionality, as it only reads the information from the catalogs but does not make any changes to the catalog. But we recommend to add both serial numbers (read only and read/write) to your installation to be prepared for upcoming Cumulus enhancements. You can find the serial numbers for your current Cumulus version, if it is not in the list above, on the Canto website at http://www.canto.com (> Download&Support).

Connection between UMP and Cumulus Server

UMP (as an addition to WPP or ICP) uses the Cumulus standard IP connections. Cumulus uses the IP port 9287 to communicate from any Cumulus Client (including WPP and ICP) to the Cumulus Server. If you install the UMP web applications (or WPP or ICP) in a Demilitarized Zone (DMZ), please make sure that the IP port 9287 used by Cumulus is open for communication between UMP and Cumulus Server.

WARNING: please make sure that no firewall is blocking the communication between UMP_Admin and the Cumulus Server. Especially if Windows Vista is involved, the communication might be blocked by the internal Vista firewall. Please make sure that the port is open or deactivate the firewall. If the communication is not possible, you will get an error telling you that the 'UMP_UserInformation' field can not be accessed.

Permissions for the Cumulus Admin

Please note that the Cumulus Admin user that you can specify in the Cumulus Server Console has all the available UMP permissions. So for your first testings of UMP, you should login as Cumulus Admin to have all the functionality of the web application available.

1.1 Tryout Version

The 'User Management Pro' software comes in DEMO mode. If you can not provide a serial number, the software is limited to work for 5 minutes until the user is logged out.

The UMP Tryout Version Dialog - you are logged out every 5 minutes

The UMP version shown in the screenshot above is limited to work for 5 minutes until the user is logged out. The user can close the browser and log in again and work for another 5 minutes.

You can request a serial number from info@heymann-consulting.de, that unlocks the software for one month completely. Please provide your Cumulus Serial Number in your email, as the serial number that you will get is calculated based on your Cumulus serial. After adding the serial, the expiration date will be displayed in the demo dialog.

The UMP Tryout Version Dialog showing the expiration date

Please note that the Cumulus Admin user that you can specify in the Cumulus Server Console has all the available UMP permissions. So for your first testings of UMP, you should login as Cumulus Admin to have all the functionality of the web application available.

1.2 The Example Catalog

The Example Catalog that comes with the 'User Management Pro' should help you to understand the functionality of the product. Please install it on your Cumulus Server as usual and publish it to the Web:

1. Open the Cumulus Client and login as Cumulus Administrator.
2. Select the button 'Add...' to specify the example catalog. You can find the example catalog in the 'Installation' folder. The file is named 'ExampleCatalogUMP.ccf'.
3. Publish the catalog to the other Cumulus Clients and on the Web by selecting 'Share Catalog' and 'Publish Catalog to Internet'.
4. To publish the catalog to the guests on the web, open the Cumulus Server Console and add the 'Example Catalog UMP' to the 'Guest'-account.

Remark: the 'User Management Pro' is not a new login mechanism nor does it change the Cumulus way to control user rights! It just adds new user rights and control mechanisms to the UMP web application.

The User Management Pro Example Catalog in the Cumulus Client

1.3 Integration of UMP4 technologies into UMP3 web application

User Management Pro 4 comes with a lot of new functionality in the UMP4_Admin web application. But the new version does only have modifications in the UMP library files and no changes in the web pages, so you can easily use the new technology with your old web application. This is interesting, because might have made a lot of changes to the web application to suite your or your customers needs (changing logos, colors, ...).

The type and number of modification varies depending on the Cumulus Software you are using. There are some more changes to implement if you want to use the UMP3 web application with Cumulus 7, due to changes that Canto implemented in the Cumulus 7 Java Classes.

This is what you have to do to use your current UMP3 web application with the new UMP4 technologies and a Cumulus 6 installation (if you are installing UMP for ICP, please replace '_WPP' by '_ICP' (e.g. 'UMP_WPP' by 'UMP_ICP) in the following description):

0. Make a backup copy of your current UMP folder!

1. Install the UMP4 web application for your Cumulus 6 installation: 'UMP4_WPP' as described in chapter 1 Installation. After Tomcat unpacked the '.war' file into the folder 'UMP4_WPP' you can copy the necessary files from the new folder into your current UMP folder.

2. Copy the Tag Library Description file '/UMP4_WPP/WEB-INF/HC_UserManagementPro.tld' to '/MyUMPFolder/WEB-INF/HC_UserManagementPro3.tld' (please note the 3 in the filename!). You have to replace the old version of the file with the new one!

3. Copy the Library file '/UMP4_WPP/WEB-INF/lib/HC_UserManagementPro.jar' to '/MyUMPFolder/WEB-INF/lib/HC_UserManagementPro3.jar'. (please note the 3 in the filename!). You have to replace the old version of the file with the new one!

4. Restart Apache Tomcat to make the new files available to the Web Application Server.

This is what you have to do to use your current UMP3 web application with the new UMP4 technologies and a Cumulus 7 installation (if you are installing UMP for ICP, please replace '_WPP' by '_ICP' (e.g. 'UMP_WPP' by 'UMP_ICP) in the following description):

0. Make a backup copy of your current UMP folder!

1. Install the UMP4 web application for your Cumulus 7 installation: 'UMP4_WPP7' as described in chapter 1 Installation. After Tomcat unpacked the '.war' file into the folder 'UMP4_WPP7' you can copy the necessary files from the new folder into your current UMP folder.

2. Replace the complete folder 'WEB-INF' in your UMP folder by the 'WEB-INF' folder that you can find inside the 'UMP4_WPP7' folder.

3. Rename the file '/MyUMPFolder/WEB-INF/HC_UserManagementPro.tld' to '/MyUMPFolder/WEB-INF/HC_UserManagementPro3.tld'.

4. Due to the new Tomcat version 5.5.17, you have to add a line to the following pages:

/MyUMPFolder/Standard/RecordViewTitle.jsp'
/MyUMPFolder/Standard/SearchResult_RecordInfo.jsp'
/MyUMPFolder/Standard/HC_UserManagementPro/BeanInfo.jsp'
/MyUMPFolder/Standard/HC_UserManagementPro/Demo.jsp'
/MyUMPFolder/Standard/HC_UserManagementPro/DemoError.jsp'

Add the second line that is missing in the pages above to make them work with Tomcat 5.5.17:

<%@ taglib uri="/WEB-INF/HC_UserManagementPro.tld" prefix="hcu"%>
<jsp:useBean id='HCBean' class='com.hc.beans.HCBean' scope='session'/>

5. Add the collection attribute to the tag 'getCategoryFieldValue' in the pages:
'/MyUMPFolder/Standard/CollBasket_RecordInfo.jsp'
'/MyUMPFolder/Standard/SearchResult_RecordInfo.jsp'
See the new pages in the UMP4_WPP folder to see the difference.

6. Restart Apache Tomcat to make the new files available to the Web Application Server.

1.4 Update your UMP web application to run with a newer Cumulus Server installation

The UMP web application is a modified WPP or ICP web application containing the WPP/ICP technologies. All the Cumulus technology can be found in the 'WebPublisherPro.jar' or 'InternetClientPro.jar' library file inside the 'WEB-INF/lib' directory. These Java Class libraries try to connect to the Cumulus Server version that they have been designed for, so a Cumulus Web Publisher Pro 7.5 web application for example expects a Cumulus 7.5 Server running containing a Cumulus Web Publisher Pro 7.5 license.

E.g. if you try to connect with the UMP4_WPP75 web application, which contains the WPP 7.5 libraries, to a Cumulus 7.6 Server (with WPP 7.6 license) installed, you will get an error message like:

The option "00790" is not correctly licensed on the Cumulus Server.

In this case download the newest version of UMP from the website to see, if a newer version of the UMP web application is available for your Cumulus Server version.

To make your current UMP web application (in this example designed for Cumulus 7.5) work with Cumulus 7.6, you have to replace the 7.5 WPP/ICP technologies with the ones of Cumulus 7.6, that are installed inside the web application named 'Cumulus'. This is what you have to do:

1. Stop your Tomcat web application server.
2. Copy the UMP4_WPP75 web application from your current Tomcat installation to your new Web Publisher Pro 7.6 installation ('webapps' directory) and you should rename it to e.g. 'UMP4_WPP76'.
3. Copy all the library files (*.jar) from Canto's newest web application ‘/Cumulus/WEB-INF/lib’ to ‘/UMP4_WPP76/WEB-INF/lib’. While copying, the new files need to replace all old existing files.
4. Copy all the TAG library files (*.tld) and xml file (*.xml) from ‘/Cumulus/WEB-INF’ to ‘/UMP4_WPP76/WEB-INF’. While copying, the new files need to replace all old existing files.
5. Configure the copied web.xml and log4j.xml files (located in the 'WEB-INF' folder) according to your needs. For details on how to configure these files , see Canto's WPP/ICP documentation 'Editing the Configuration File,' p. 18, and 'Logging,' p. 30.
6 . Start the Web application server again.

For other web application versions, the upgrade procedure is similar to the steps described here.

1.5 Cumulus User Management: 'Simple Mode' or 'Advanced Mode'

Canto Cumulus comes with different implementations of the Cumulus User Management in the Server Console:

1) Users (Simple Mode)
2) Users and Roles (Advanced Mode)

The Users and Roles concept is a feature of the Cumulus Enterprise Edition, or the Cumulus Workgroup Edtion with Cumulus 'Roles & Extended LDAP Support' Module installed. The standard Workgroup Edtion does only allow to configure Users on a one by one basis.

The UMP_Admin web application of User Management Pro 4 (since version 4.5 of UMP_Admin) supports both types of the Cumulus User Management.

When your Cumulus User Management is running in Advanced Mode, UMP_Admin also switches internally to 'Advanced Mode'. You will be informed about the mode on the upper lefthand side of the main page, if your Cumulus Server is running in 'Advanced Mode'.

In the 'Advanced Mode', two new menu items are displayed: 'Users' and 'Roles'. Click on 'Users' to display the list of already created Cumulus Users and all the appropriate functionality for users is available there. Click on 'Roles' to display the list of Cumulus Roles and set the permissions for roles there. To create the users and roles, use the User Management in the Cumulus Server Console as usual.

If Cumulus is running in 'Simple Mode', only users can be configured in the Cumulus User Management and the User Management Pro Admin Tool will also only allow to set the user settings.

This documentation expects that your Cumulus Server is running in Simple Mode (as most of the Cumulus implementations do). This means that all permission that can be set are displayed in one page. If your Cumulus implementation is running in 'Advanced Mode', the permissions discribed in the documentation will be seperated into the ones that can be configured on a users basis and the ones that can be set for roles. The permissions that can be set are exactly the same, whatever mode your Cumulus Server is running in.

The UMP Admin 'Roles Management'

The User Management of UMP uses the Canto Cumulus User Management technology introduced with Cumulus 6, so it is based on the Cumulus '$Users' catalog and the Server Console that comes with the Cumulus product. To store the new permissions introduced in UMP it is necessary to add one text field to the '$Users' catalog. To achieve this, here are the steps to follow:

1. Open the Cumulus Client and open the '$Users' catalog as Cumulus Administrator.
2. Open the Preferences of the '$Users' catalog and add a 'String' field named 'UMP_UserInformation'.

Add the String Field 'UMP_UserInformation' to your '$Users' Catalog

WARNING: Please make sure that you create the String field named 'UMP_UserInformation'. Do NOT create a String field 'Untitled' and rename it lateron to 'UMP_UserInformation', because even after renaming the field, the Cumulus internal name of the field is still 'Untitled'. In that case UMP can not access the field and will give an 'UMP_UserInformation field not available' error!

3. Please make sure that the new field can be edited by the user.

Before you can use your UMP web application, please open the UMP_Admin web application to provide your serial number or (if you do not have a valid serial number) make your initial setup. Open the URL 'http://myServer:8080/UMP_Admin/login.jsp'.

The User Management Pro Admin Web Application Login Page

1. Log into the web application as Cumulus Adminstrator. Only the Cumulus Admin is allowed to use this web application!
2. If you have opened the web application for the first time or you have not saved the initial configuration yet, you will be linked to the 'Initial Configurations' page to specify your serial number and the language that should be used for the UMP web application.

UMP Admin Initial Configuration

3. Please provide the serial number(s) (the Cumulus Serial Number should be read from your Cumulus Server application automatically) and select the language of your web application and click 'Save Configuration' to save your current setup. The software tries to connect to your Cumulus Server to get your Cumulus Serial via IP port 8954.

4. With the help of UMP Admin 4 you are able to send emails to each and every user with a valid configured email address. You can specify your email server configuration in the UMP Admin configuration.

Specify your email configuration before using the email function

Specify your email server attributes and click on 'Save Configuration' to make the new configuration valid.

5. After providing the serial number(s) and email server configuration you will be linked to the list of available users.

UMP Admin List of Users

5. If your version is a tryout version, or a time limited tryout version, you will find this documented on the upper right-hand side of the page.

2.1 How to publish a Cumulus Catalog with User Management Pro

1. Create the Cumulus Catalog and catalog the files that you want to publish on the web.
2. Publish the catalog to the web: Edit>Preferences>Catalog Settings>General>Sharing: 'Share Catalog' and 'Publish Catalog to Internet'.
3. If you would like to localise the name of the catalog, you can specify the localised names in the language configuration files inside the web application folder ('webapps\UMP\WEB-INF\classes'). Find detailed information on this topic here.
4. Open the Cumulus Server Console in the Cumulus Client: File>Administration>Server Console...
5. Select 'User Manager>Users'.
6 . Assign the new Catalog to the appropriate users.
7. Make sure that the user is allowed to Open the catalog.
8 . You can access the catalog using the UMP web application at 'http://yourServer/UMP/'.
9. Open the UMP_Admin web application to verify the UMP permissions for this user in this catalog. If you have not set the permission, the user will only see limited functionality in the web application!

WARNING: Please make sure that you specify the user's permission in the UMP_Admin web application first.

2.2 How to create a new user to access the web application

In this example we would like to create a new user named 'James Dean' and make the UMP Example Catalog available to him.

1. Open the Cumulus Server Console in the Cumulus Client: File>Administration>Server Console...
2. Select 'User Manager>Users'.
3. Create a new user clicking the 'Create...' button and specify the name of the new user 'James Dean'.
4. Specify the catalogs, that the user is allowed to access in the tab 'Catalogs'. You can allow access to all the published catalogs by unchecking the 'Restrict Catalog Access to the Following Catalogs' checkbox. In the screenshot below, only the access to the UMP Example Catalog is allowed.

The user's catalog permissions in the Cumulus Server Console

5. Make sure that the user has (min.) the right to open the catalog. You can specify this right in the 'Permissions' tab for all allowed catalogs or for each single catalog.
6. In the tab 'Server Permissions', you can specify the user's 'Action Permissions', Metadata Templates Permissions' and 'Record Query Permissions' that are used inside the web application.
7. After setting the basic Cumulus user permissions, you can specify the user rights used by the User Management Pro in the UMP Admin web application.
8. Login to the UMP Admin web application at 'http://yourServer/UMP_Admin/' with your Cumulus Admin username and password.
9. Select the name of the user for whome you want to set the rights to open the 'Modify Permissions Page'.

The UMP Admin Modify Permissions Page

10. Specify the user rights in the 'Modify Permissions Page'. You can specify user rights and user settings. The permissions can be specified for 'All Allowed Catalogs' or for each single catalog. Make sure that you have selected the appropriate option before setting the user permissions.

The list of available catalogs

Remark: You can specify the permissions for single users or for a set of users by checking their names in the list of users and clicking the 'Modify Permissions' button.

2.3 User Management Pro User Permissions

The User Management Pro provides a lot of user permissions that can be configured in the 'Modify Permissions Page'. These permissions are explained in the following list:

Permission Name	Explaination
View Menu	5 different views (max.) can be selected from the menu: Thumbnail View, Details View, Record Information, Preview and Slideshow. The View Menu allows the user to switch between the different views. If you hide the View Menu from the user, you have to specify one view that is used as the basic setup.
Image Size Menu	3 different Image Sizes are available in the menu.
Number of Rows and Columns	The number of rows and columns in the Thumbnail View.
Sort Menu	The sort field can be selected from list of sort fields.
Record Menu	All functions can be chosen from the Record Menu displayed in the Thumbnail View.
Category Information	The category information window can be accessed by the user.
Collection Basket	The Collection Basket is shown / hidden from the user. The fields to be searched can be specified in the parameter 'Search Fields'.
Advanced Search	Complex search queries can be defined in the Advanced Search form.
Download	The user is allowed to download files. A category, that restricts the download of files for the user can be specified in the parameter 'Control Download Category'.
Email	The files in the Collection Basket can be sent by email, if the email address of the user is available.
CD Order	The files in the Collection Basket can be ordered by email, if the shipping address of the user is available.
Conversion	The files are converted based on the Cumulus Actions defined for the user.
Language Selection	The language of the web application can be selected from the list of supported languages.
Upload (ICP only)	Allow upload of files to the server.
Welcome Text	The welcome text will be display when the user first enters the web application. You can specify the welcome text in different languages (click here to go to chapter 5.1 for details).
First Search	This first search query will be performed at initial access and reload. Click on 'Select' to select the first search from the list of available search queries (click here to go to chapter 5.2 for details).
First Search Name	The name of the first search will be displayed in the status bar. You can specify the First Search Name in different languages (click here to go to chapter 5.2 for details).
Restrict Search	The search query limits the user's access to the records. Click on 'Select' to select the restriction query from the list of available search queries (click here to go to chapter 4.1 for details).
Restrict Master Categories	Restrict the user's access to the different Category Trees. Click on 'Select' to select the master categories that should be hidden from the user. One master category has to be active, so you can not hide the category tree completely using this feature (click here to go to chapter 5.7 for details).
Default Master Category:	The selected Master Category (Category Tree) will be displayed by default for the user. The available choices are: undefined, All ($All), Categories ($Categories), Sources ($Sources), and Keywords ($Keywords) (click here to go to chapter 5.7 for details).
Default Record View:	The selected Record View will be displayed at startup. The following choices are available: undefined, Thumbnail View, Details View, Record Information, and Preview (click here to go to chapter 5.8 for details).
Search Fields:	The given search fields (delimited by comma) will be used in the QuickSearch function (String and number fields only!) (click here to go to chapter 5.4 for details).
Sort Field:	The records will be sorted by this field (click here to go to chapter 5.3 for details).
Sort Direction:	The sort direction can be 'Ascending' or 'Descending' (click here to go to chapter 5.3 for details).
Control Download Categories:	All assets with these categories assigned can be downloaded by the user. If none of these categories is assigned to the record, the asset can not be dowloaded. If this parameter is empty, the user is allowed to download all the assets in the catalog, if the download permission is set (click here to go to chapter 5.5 for details).
Control Email Categories:	All assets with these categories assigned can be sent by email to the user. If none of these categories is assigned to the record, the asset can not be sent. If this parameter is empty, the user is allowed to email all the assets in the catalog, if the email permission is set (click here to go to chapter 5.6 for details).
Language: Select	The user's language (abbreviation, e.g. 'en_US' for English). Click on 'Select' to select the language from the list of supported languages (click here to go to chapter 5.9 for details).
Restrict Categories:	Specify a boolean Category Field that controls the user's access to categories. Only categories with this value set to 'true' will be displayed in the category tree (click here to go to chapter 4.5 for details).

2.4 How to define a search query for UMP

The User Management Pro uses Cumulus search queries to restrict the access to records in the Cumulus catalog. If a restriction search is defined for the user, only the records found by the query can be accessed by the user. This is how you can define a query in Canto Cumulus and make it valid for the user:

1. Open the Cumulus Client and open the Cumulus catalog.
2. Open the find window ('Collection>Find Records...').
3. Define the search query that you need to restrict the access to records or use for the first search. Example: show only JPEG files to the user.

Configure the search query in the Cumulus Client Find Window

4. Click 'Floppy Symbol>Save...' to save the search query.
5. Specify a name and make sure that you check 'Share Query' to make it available for the use in the Server Console.

Save the Search Query and save it

6. Open the Cumulus Server Console in the Cumulus Client: File>Administration>Server Console...
7. Select 'User Manager>Users'.
8. To restrict the access of user 'James Dean' to only the JPEG files, open the preferences of user 'James Dean' ('Edit...').
9. Select the tab 'Server Permissions' and click 'Record Query Permissions'.

Set the Record Query Permission in the Cumulus Server Console

10. Make the search query 'JPEG Files Only' available to the user by adding it to the 'Restrict Access to' list or uncheck 'Restrict Access to' and check 'View Shared Queries' to make all queries available to the user.
11. After setting the 'Record Query Permissions', you can specify the restriction used by the User Management Pro in the UMP Admin web application.
12 . Login to the UMP Admin web application at 'http://yourServer/UMP_Admin/' with your Cumulus Admin username and password.
13 . Select the name of the user 'James Dean' to open the 'Modify Permissions Page'.
14. Click the 'Select' link next to 'Restrict Search:' to open the 'Select Search Query Page'.

The UMP Admin Search Query Selection Page

IMPORTANT: the list of search queries that is displayed shows all the search queries available on your Cumulus Server. You can select any query from the list, even if the query is not yet assigned to the selected user. A query that is not yet assigned to the user (in the Server Console) can not be used as a restriction query or first search query lateron.

15. Select the search query 'JPEG Files Only'. The text of the query will be displayed in the text box to inform you about the search criteria.
16. Click 'Select' to confirm your choice.
17. Click 'Save Permissions' to save all the permissions set for the user.

The same technology is used for the 'First Search' parameter. Create a search query and assign it to the user like in the example above.

2.5 How to add a new language to UMP

The User Management Pro technology to localise the strings in the web application is open, so the administrator can add more languages to the software.

This is what you have to do to add another language (Spanish in this example) to the UMP web application:

1. Duplicate the English localisation file ('/UMP/WEB-INF/classes/UMP_en_us.properties') and rename the new file using the Java locale naming convention for the language (lowercase letters only): '/UMP/WEB-INF/classes/UMP_es_es.properties'.

2. Translate all the Strings in the localisation file 'UMP_es_es.properties'. You should convert all special characters into their HTML representation to be independant from the server platform and the encoding used. Example: replace 'é' with '&eacute;'.

3. Add the name of the new language to ALL the localisation files (UMP_??_??.properties) of the UMP web application

Add the following line e.g. to the French localisation file '/UMP/WEB-INF/classes/UMP_fr_fr.properties':

Language.Spanish = Espagnol

4. Add the new language as a new option to the language selection menus in the UMP web application:

<option value="es_ES"><hcu:getLocalText key='Language.Spanish'/></option>

UMP web application: '/UMP/Standard/Login.jsp' line 88 and '/UMP/Standard/RecordViewTitle.jsp' line 634.

You can specify the language that should be used in the Login Page by specifying the lang attribute in the URL like this:

http://myServer/UMP/Standard/Login.jsp?lang=es_ES

This will open the Login Page in Spanish, if a Spanish localisation file 'UMP_es_es.properties' is available. The strings in the page will be localised and the language menu will be set accordingly. If no lang attribute is specified, the Login Page tries to detect the current language setup from the Web Browser. It takes the current setup (for example: es-ar = Argentina Spanish) and maps the locale to the supported locales (Spanish es_es). If no matching locale is available, the locale will be set to 'en_US'. Here are the current browser locale mappings defined:

'en-...' to 'en_US'
'de-...' to 'de_DE'
'fr-...' to 'fr_FR'
'es-...' to 'es_ES'
every other Browser locale is mapped to 'en_US'

5. Add a localisation of the Cumulus Fieldnames to your localisation file. See lines 84-111 in the Spanish localisation file '/UMP/WEB-INF/classes/UMP_es_es.properties'.

6. Add a localisation of the Cumulus Queries to your localisation file. See lines 45-49 in the Spanish localisation file '/UMP/WEB-INF/classes/UMP_es_es.properties'.

This is what you have to do to add another language (Spanish in this example) to the UMP_Admin web application:

1. Duplicate the English localisation file ('/UMP_Admin/WEB-INF/classes/UMP_Admin_en.properties') and rename the new file using the Java locale naming convention for the language (lowercase letters only): '/UMP_Admin/WEB-INF/classes/UMP_Admin_es.properties'.

2. Translate all the Strings in the localisation file 'UMP_Admin_es.properties'. You should convert all special characters into their HTML representation to be independant from the server platform and the encoding used. Example: replace 'é' with '&eacute;'.

3. Add the name of the new language to ALL the localisation files (UMP_Admin_??.properties) of the UMP_Admin web application:

Add the following line e.g. to the German localisation file '/UMP_Admin/WEB-INF/classes/UMP_Admin_de.properties' to the Supported Languages section (line 9):

Language.Spanish = Spanisch

4. Add the name of the new language to the localisation files (line 131):

txtSpanish=Spanisch

5. Add the new language to the language selection menus in the UMP_Admin login page:

<OPTION VALUE="es"><umpadmin:getLocalText key='Language.Spanish'/></OPTION>

UMP_Admin web application: '/UMP_Admin/login.jsp' line 63.

6. Add the new language to the language selection menus in the UMP_Admin web application:

<OPTION VALUE="es_ES"><umpadmin:getLocalText key='txtSpanish'/></OPTION>

UMP_Admin web application: '/UMP_Admin/selectLanguage.jsp' line 77.
UMP_Admin web application: '/UMP_Admin/selectConfigLanguage.jsp' line 75.

You can specify the language that should be used in the Login Page by specifying the lang attribute in the URL like this:

http://myServer/UMP_Admin/login.jsp?lang=es

3.1 Groups

User Management Pro 4 implements the definition of groups of users, an important function that is missing in the Cumulus Workgroup Edition. A user can belong to more than one group at a time.

You can select a name of a group from the list of groups to limit the list of users. You can select 'Show All' to show all the defined users. Select 'Not Assigned' if you want to see the users that do not belong to one of the defined groups.

Select a User Group to limit the list of users

Click on '+' or '-' to add a group to or remove a group from the selected user(s). This will lead you to the 'Assign Group' page.

Click on '+' or '-' to add or remove a group from the selected user(s)

You can assign a group name to a list of users or specify a new group name in the 'Assign Group' page:

Assign a group to a list of users

You can assign a group name by selecting it from the list of already existing groups or you can specify a new group name in the 'New group name' text box. Click on 'Assign Group' to save the group setting. The group names are displayed in the list of users.

3.2 User Name Filter

You can filter the list of users by typing the beginning of the user name in the 'Show Users' text box. Click on 'Filter' to only see the users that match the filter name.

Specify a user name to limit the list of users

The list of users above is limited to the user names that start with 'creative'. This is helpful if you do have to manage a long list of users and you do not know the group the users belongs to.

3.3 Send Email to Users

You can send an email to all the selected users in the list by clicking the button 'Send Email'. You can specify the subject and the email body in the 'Send email to' page. You can also send a carbon copy to yourself or a list of users.

The 'Send email to' page also informs about missing email addresses

The email is sent to all email addresses that have been specified in the Cumulus Server Console (field name: E-Mail Address). All the users with an email address specified are marked with an email icon in the list of users. If you have selected users that do not have an email address configured yet, you will get a warning on top of the 'Send email to' page. When clicking the 'Send Email' button, the email will be sent to all the available email addresses.

You can send an email to all the users marked with the email icon

Hold the mouse over the email icon to see the email address configured for the user.

You can verify the email address by positioning the mouse on the email icon

3.4 Modify Single Permission

User Management Pro 4 allows to modify a single permission for a lot of users at the same time. This feature is very helpful if you would like to change permissions for a lot of users after they have been configured, but their permission setup varies and you can not select users with similar permission settings easily.

Select the catalog and the permission to modify a single permission

Select the users and click the 'Modify Single Permission' button to go to the 'Modify Single Permission' page. Select the catalog and permission that you would like to change. The permission setup will be displayed and you can configure it as usual. Click on 'Save Permission' to save the user setting for all the selected users.

Only the selected permission is changed for the selected users, all other permission for these users stay as they are.

3.5 Copy Permissions

You can copy all permission settings of one user for one catalog to a list of other users. Copy the user to the clipboard by selecting the user from the list and clicking the clipboard icon.

Copy the user to the clipboard by selecting the user and clicking the clipboard icon

After putting the user into the clipboard, you can select the users that should get the permissions of the clipboard user and click on the 'Copy Permissions' button to go to the 'Copy Permissions' page:

Copy all permissions from one user to a list of users

Select the catalog and double-check again, if you want to copy the settings as this can not be undone! Click on the 'Copy Permissions' button to copy all the permission settings from the user in the clipboard to all the selected users.

3.6 User List

The 'User List' page helps you to compare the permission settings for the different users. It gives you a good overview over all the permissions set for the selected users.

The list of users provides a good overview over all permissions

Select the name of the catalog from the list. The user permissions are displayed for all selected users in the specified catalog. Click on the permission name link to modify a single permission for all the selected users.

3.7 Labels

Labels can help you to get a better overview over the users in the list of users. You can mark users or sets of users with a label by selecting the users in the list and by clicking the 'Label' icon which you can find next to the 'Users' column title.

Click on the assign label icon the get select the label

The list of predefined labels will be displayed. Select one of the labels to assign it to the selected users or select 'No Label' to remove a label from the selected user settings.

Select the label that you want to assign to the selected users

The label color will be used to mark the users in the list of users.

User Management Pro 4 provides more configuration settings for showing and hiding records and categories to the user. There are three different options of how to hide records from the user:

• a Restriction Search is added to the users search criteria
• based on the Category Assignment
• based on the setting of Boolean Record Fields

There are two different options of how to hide categories from the user:

• based on the Category Assignment
• based on the setting of Boolean Record Fields

The Record and Category Access Permissions

The UMP Admin now provides more flexibility in configuring access rights for the user. Click on the 'Select' link to go to the permission configuration page.

4.1 Record Restriction: Restrict Search

For every user you can define a search query that restricts the access to the records in the catalog. This query is added to every search query that is sent to Cumulus. To make the definition of the search query as easy as possible, UMP uses Cumulus Client queries, that have been saved and published. You can easily define the search query in the Cumulus Client by saving it in the Cumulus Search Window.

To make the definition of the search query as easy as possible, UMP uses Cumulus Client queries, that have been saved and published. You can easily define the search query in the Cumulus Client by saving it in the Cumulus Search Window. Click on the floppy icon in the search window ('Save Query...') to store the query that you have defined in the search window. Give the query file a unique name and publish the query (!) to make it available for the users. Click here to get detailed information on how to create and publish a search query.

Select a search query from the 'Restrict Search' page to restrict the record access

In the example above, a search query with the name 'JPEG Files Only' is assigned to the user, he is limited to only access the JPEG files in the catalog. If there is no 'restrictSearch' query defined for the user, the user has full access to all the records of the catalog. The search query in the query file can be very complex and can consist of a lot of different search criterias combined by 'and' and 'or'.

Select the search query from the list of queries

You can select one of the published Cumulus search queries from the list. The search query text will be displayed to help you identify the correct query.

4.2 Record Restriction: Record Filter

You can limit the access to records by setting categories in the Record Filter permission. The user can only see the records within the selected categories (and its sub-categories). A category is specified by providing the full category path (seperated by ':'). An unlimited number of categories can be listed, seperated by comma.

List the categories to show its records to the user

If the Record Filter permission is empty, all the records are shown to the user. Click on the 'Select' link to go to the 'Select Record Filter' page. You can navigate through the complete category tree of the selected catalog and check the categories that you would like to use as the Record Filter. You can navigate through the category tree by clicking on the category name to go to its sub-categories (if available). On top of the page, you see your location in the category path, you can click on the category name to go to the category directly or click on the catalog name to go to the top of the category tree.

Your current selection will be displayed at the bottom of the page. Remark: this page is only visible if a Cumulus Client connection can be established to the Cumulus Server.

Navigate through the category tree to specify the filter categories

You can also use your filter setup for hiding categories from the user by selecting 'Use Record Filter for filtering categories also'.

4.3 Record Restriction: Boolean Record Filter

You can limit the access to records by setting boolean record fields in the Boolean Record Filter permission. The user can only see the records with the selected boolean fields set to 'true'. An unlimited number(!) of boolean record fields can be listed, seperated by comma.

List the boolean record fields to control the records shown to the user

If the Boolean Record Filter permission is empty, all the records are shown to the user. Click the 'Select' link to go to the 'Select Boolean Record Filter' page. Check the boolean record fields that you would like to use as the Boolean Record Filter. Only the boolean record fields of the selected Cumulus catalog are displayed in the page. Remark: this page is only visible if a Cumulus Client connection can be established to the Cumulus Server.

Select the boolean fields that you want to use as the Boolean Record Filter

Click the 'Select' button to set the Boolean Record Filter setting.

4.4 Category Restriction: Category Filter

You can limit the access to categories by setting categories in the Category Filter permission. The user can only see the selected categories (and its sub-categories). A category is specified by providing the full category path (seperated by ':'). An unlimited number of categories can be listed, seperated by comma.

List the categories that should be visible to the user

If the Category Filter permission is empty, all the categories are shown to the user. Click on the 'Select' link to go to the 'Select Category Filter' page. You can navigate through the complete category tree of the selected catalog and check the categories that you would like to use as the Category Filter. You can navigate through the category tree by clicking on the category name to go to its sub-categories (if available). On top of the page, you see your location in the category path, you can click on the category name to go to the category directly or click on the catalog name to go to the top of the category tree.

Your current selection will be displayed at the bottom of the page. Remark: this page is only visible if a Cumulus Client connection can be established to the Cumulus Server.

Navigate through the category tree to specify the filter categories

You can also use your filter setup for hiding records from the user by selecting 'Use Category Filter for filtering records also'.

4.5 Category Restriction: Boolean Category Filter

You can limit the access to categories by setting boolean category fields in the Boolean Category Filter permission. The user can only see the categories with the selected boolean fields set to 'true'. An unlimited number(!) of boolean category fields can be listed, seperated by comma.

List the boolean category fields to control the categories shown to the user

If the Boolean Category Filter permission is empty, all the categories are shown to the user. Click the 'Select' link to go to the 'Select Boolean Category Filter' page. Check the boolean category fields that you would like to use as the Boolean Category Filter. Only the boolean category fields of the selected Cumulus catalog are displayed in the page. Remark: this page is only visible if a Cumulus Client connection can be established to the Cumulus Server.

Select the boolean fields that you want to use as the Boolean Category Filter

Click the 'Select' button to set the Boolean Record Filter setting.

In the following example a category field named 'PublishCategoryToWeb' is created in the Cumulus Catalog to control the web access to the categories.

Create the Boolean Category Field in your catalog

The initial value of this category field is set to TRUE ('Active'), so every new category will have this value in the field.

If the user shall only see the categories 'marked' with TRUE, it is only necessary to set the field value of the 'Restrict Categories' permission for this user to the boolean field named 'PublishCategoryToWeb'. If the boolean example Category Field 'PublishCategoryToWeb' is not available in the Cumulus Catalog, all the categories are displayed to the user. If the Category Field is available in the Catalog, set the value of the field to FALSE to hide the category from the user. If the field value is set to TRUE or (!) the field value is EMPTY (undefined), the category will be displayed to the user.

Important: the 'User Management Pro' is designed for the use with the Cumulus Workgroup Edition and implements features that are only available in the Enterprise Edition. In the Workgroup Edition it is not possible to search in category fields (Enterprise Edition feature). This is why you have to use Boolean Fields to control the access to categories on the web.

5.1 Welcome Text

When the user accesses the web application for the first time, a welcome text can be displayed. You can configure this text in the permission parameter 'Welcome Text'. The text will be displayed in the UMP web application on the righthand side of the tabs.

The text will also be displayed when the web application is reloaded.

You can specify one welcome text for all languages or specify different strings for each language. If the parameter value is 'Welcome', this text will be displayed independant from the language selected in the web application. If the parameter is '<de_DE>Willkommen</de_DE><en_US>Welcome</en_US><fr_FR>Bienvenue</fr_FR>', the specified strings will be displayed depending on the selected language in the web application.

User Management Pro supports the languages English, German, French and Spanish in one web application. The welcome text and the first search name attributes can be set in a comfortable dialog that supports the one text for all languages or seperate text for each and every language.

Specify one text for all languages or language dependent strings

The different localised strings are seperated by tags from each other in the permission settings.

Localised strings seperated by locale tags

5.2 First Search and First Search Name

When the user accesses the web application for the first time, it is possible to let UMP perform a first search for records that can be different for each user.

To make the definition of the search query as easy as possible, the 'User Management Pro' uses Cumulus Client queries, that have been saved and published. You can easily define the search query in the Cumulus Client by saving it in the Cumulus Search Window. Click on the floppy icon in the search window ('Save Query...') to store the query that you have defined in the search window. Give the query file a unique name and publish the query (!) to make it available for the users. Click here to get detailed information on how to create and publish a search query.

When the user first accesses the web application (or reloads it) this search query is used. If no first search query is defined for the user, a search is performed for all the records that the user is allowed to access. The search query can be very complex and can consist of a lot of different search criterias combined by 'and' and 'or'. If a restriction is defined for the user, the first search query is performed together with the restriction query.

In the middle of the Status Bar UMP will show the last search query text (category name or search text). You can display a search text which tells the user which search was performed. You can configure this text in the parameter 'firstSearchName'. This is how the 'firstSearchName' is displayed in the web application:

You can specify one First Search Name for all languages or specify different strings for each language. If the parameter value is 'All Images', this text will be displayed independent from the language selected in the web application. If the parameter is '<de_DE>Alle Bilder</de_DE><en_US>All Images </en_US><fr_FR>Tous les Images</fr_FR>', the specified strings will be displayed depending on the selected language in the web application.

5.3 Sort Order and Direction

A standard sort order and direction can be configured for the user which is used when he first accesses the web application. You can specify the sort order for the user in the parameters 'Sort Field' and 'Sort Direction' (Ascending or Descending).

If these fields are empty, the standard sort order of the web application is used. You can set the standard sort order of the web application in the file '/UserManagementPro/Standard/RecordView.jsp' in lines 14 and 15. The standard sort order is 'Asset Creation Date Descending' ('newest files first').

If the user is allowed to use the sort menu, he can change the sort order at any time by selecting a different sort field from the list or changing the sort direction by clicking the appropriate button.

Click on the Select link to specify the Sort Field

Just click on the 'Select' link to go to the 'Select Sort Field' page.

Select the Sort Field from the list

Select the sort field from the list of the avaialble sort fields and click on the 'Select' button to set your selection.

To specify the sort direction just click on the appropriate button to set the sort direction:

Click on the arrows to specify 'Ascending' or 'Descending'

5.4 QuickSearch Query Fields

If the user has the right to use the text search function, the text search form is displayed in the web application:

The left search button starts a search in all the records of the catalog. The second button performs a search in the list of current records (search in current collection). In the user category field 'searchFields' you can define the search fields for the user. Important: these fields need to have an index for full text search, because the module performs a contains-search.

Click on the Select link to specify the list of Search Fields

In this example the user can perform a search like: Asset Name contains 'tif' or Categories contains 'tif' or Notes contains 'tif' or Record Name contains 'tif'.

If the 'searchFields' parameter for the user is left empty, the standard search setup is taken. You can specify the standard search parameter in the file '/UserManagementPro/Standard/HC_QuickSearch.jsp' in line 16.

Just click on the 'Select' link to go to the 'Select Search Fields' page.

Select the Search Fields from the list

Check the fields that you would like to use in the Quicksearch function and click on the 'Select' button to set your selection.

5.5 Control Download Categories

You can limit the download of assets by setting a list of categories in the Control Download Categories permission. The user can only download the assets within the selected categories (and its sub-categories). A category is specified by providing the full category path (seperated by ':'). An unlimited number of categories can be listed, seperated by comma.

Click on the Select link to specify the categories that control the download of assets

If the Control Download Categories permission is empty, all the assets can be downloaded by the user. Click on the 'Select' link to go to the 'Select Control Download Categories' page. You can navigate through the complete category tree of the selected catalog and check the categories that you would like to use as the Control Download Categories. You can navigate through the category tree by clicking on the category name to go to its sub-categories (if available). On top of the page, you see your location in the category path, you can click on the category name to go to the category directly or click on the catalog name to go to the top of the category tree.

Your current selection will be displayed at the bottom of the page. Remark: this page is only visible if a Cumulus Client connection can be established to the Cumulus Server.

Navigate through the category tree to specify the Control Download Categories

5.6 Control Email Categories

You can limit the sending of assets by email by setting a list of categories in the Control Email Categories permission. The user can only send the assets within the selected categories (and its sub-categories). A category is specified by providing the full category path (seperated by ':'). An unlimited number of categories can be listed, seperated by comma.

Click on the Select link to specify the categories that control the email assets function

If the Control Email Categories permission is empty, all the assets can be sent by email by the user. Click on the 'Select' link to go to the 'Select Control Email Categories' page. You can navigate through the complete category tree of the selected catalog and check the categories that you would like to use as the Control Email Categories. You can navigate through the category tree by clicking on the category name to go to its sub-categories (if available). On top of the page, you see your location in the category path, you can click on the category name to go to the category directly or click on the catalog name to go to the top of the category tree.

Your current selection will be displayed at the bottom of the page. Remark: this page is only visible if a Cumulus Client connection can be established to the Cumulus Server.

Navigate through the category tree to specify the Control Email Categories

5.7 Master Categories

Canto Cumulus supports so called 'Master Categories'. Each master category is a name for a single category tree. The Workgroup Edition comes with 4 different Master Categories: All, Categories, Keywords and Sources.

UMP supports hiding some of the category trees from the user. You can specify the Master Categories that you want to hide from the user by clicking the 'Restrict Master Categories Select' link. In the 'Restrict Master Categories Page' you can check the Master Categories that should not be accessable by the user. All unchecked Master Categories can be accessed by the user.

The UMP Admin Restrict Master Categories Selection Page

All the checked Master Categories will be listed delimited by comma in the Restrict Master Categories parameter.

If this text field is empty, the user has access to all available Master Categories.

In the parameter 'Default Master Category' you can specify the Master Category that will be displayed by default. In the example above, UMP will switch to the 'Categories' tree when the user accesses the web application.

5.8 Default Record View

The Canto Cumulus Web Publisher Pro and Internet Client Pro support 4 different main views: Thumbnail View, Details View, Record Information and Preview.

In the parameter 'Default Record View' you can specify the Record View that will be displayed by default. In the example above, UMP will switch to the first view available when the user accesses the web application. This is usually the Thumbnail View, but depends on the users View Menu setup.

In the example above the user is not allowed to access the Thumbnail View, therefor UMP will automatically switch to the Details View if the Default Record View parameter is set to 'undefined'.

5.9 Localisation

UMP supports four different languages out of the box: English, German, Spanish and French. It is also prepared for Spanish and you can add your own languages as you like.

5.9.1 Localisation of the Web Application

The basic language of the web application can be defined in the configuration section of the UMP Admin web application.

This is the basic setup for all the users using the web application and is used for the Login Page and web application, if there is not a different language defined for the user. You can use the following values:

en_US = English
de_DE = German
es _ES = Spanish
fr_FR = French

The web application is also prepared for supporting Spanish (you will find a Spanish localisation file in the 'classes'-folder), but Cumulus does not support this language internally and due to the tight integration into Cumulus technologies in all pages.

You can specify different languages for different users in the user attribute 'Language'. This attribute can have the same values listed above. If you have defined your own language, of course you can also use this Locale Identifier as a value here.

If the user is allowed to switch between the languages at runtime (user attribute 'Language Selection'), the language selection menu will be displayed in the web application.

If the user attribute 'language' is empty the basic language from the UMP Admin Configuration is taken.

5.9.2 Localisation of Catalog Names

You can also localise the catalog names shown in the list of available catalogs.

If no translation is available, the original catalog name is displayed. You can specify the localised name of the catalog in the localisation files. Example: translate the 'UMP Example Catalog' in the German web application to 'Bilddatenbank':

1. Open the German localisation file with a text editor: .../UMP/WEB-INF/classes/UMP_de_de.properties'.
2. Add the line 'CatalogName.ExampleCatalogUMP=Bilddatenbank' to the text block of catalog name localisations.
3. Save the file and restart your web application server.

Make sure that there are NO blanks in the original catalog name as shown in the example above.

5.9.3 Localisation of Category Names

The 'User Management Pro' implements a multi-language category list. If the user is allowed to do so, he can switch between the languages at runtime.

The localised Category Names in the Category Information Window

It uses Cumulus Category Fields to hold the category names in the different supported languages. The category field names have to be as follows:

CategoryName_en_US = English category name
CategoryName_de_DE = German category name
CategoryName_fr_FR = French category name
CategoryName_es_ES = Spanish category name

You can define your own language fields in the catalog. E.g. if you want to add Danish to your category list, just add the Cumulus Category Field 'CategoryName_dk_DK' to the catalog.

Add the Category Fields to your Cumulus Catalog

If a field is not available or the field is empty, the value of the field 'Category Name' is displayed as the category name. So if you have got categories in the catalog that do not need to be translated (e.g numbers), just leave the localisation fields empty so the usual Category Name is displayed. In the Example Catalog, the 'Weekly Jobs' in the 'Job Tracking' hierarchy are just numbers, that do not have to be translated. So in this case you do not have to fill the localisation fields, the job numbers are displayed anyway.

If the user is allowed to switch between the languages, it is possible to change the language of the Category List at runtime by selecting the new language in the language selection menu.

The order of the categories in the list is given by the alphabetical order of the categories in the Cumulus Catalog (based on the 'Category Name' field). If you want to have your own order, please use numbers in the category name to create your own 'alphabetical' order. Please keep in mind that these category names do not have to appear on the web, because you can have other category names in the localisation fields.

Canto introduced new master categories with Cumulus 6: $All, $Categories, $Keywords and $Sources. With 'User Management Pro', you can translate these Category names, which confuse most of the users, to something more meaningful.

You can also localise the Master Categories

If you are using the UMP version for ICP and you are allowed to modify categories, it is possible to specify the different catagory names for the different available languages inside the web application. If the Category Fields ('CategoryName_en_US','CategoryName_de_DE','CategoryName_fr_FR') are available in the catalog, they are displayed in the Category Info page.

The localised Category Names in the UMP Web Application for ICP

5.9.4 More Localisations

All the localisation of the web application is done based on the localisation files that can be found in the folder '.../UMP/WEB-INF/classes/'. The files following the usual naming convention:

UMP_en_us.properties = English
UMP_de_de.properties = German
UMP_es_ES.properties = Spanish
UMP_fr_fr.properties = French

You can specify the following types of Strings in the localisation files:

Catalog Names
Action Names
Asset Handling Set Names
Metadata Template Names
Free Strings

Example: to provide an English and German translation for the French Asset Handling Set 'Tous Format' (if you are using a French Cumulus Server), the files hold the following translation information:

UMP_en_us.properties:
AssetHandlingSetName.Tousformats=All Formats

UMP_de_de.properties:
AssetHandlingSetName.Tousformats=Alle Formate

Make sure that there are NO blanks in the names as shown in the example above. You can use whatever character in the translation. The translations are read by the web application using the TAG <hcu:localise key=''>.

5.10 Modify Records and Categories (ICP only)

With the version of UMP for the Internet Client Pro it is possible to modify records and categories in the Cumulus Catalog. All the functionality that is supported by ICP is also available in the UMP web application.

The Record Information in the UMP Web Application for ICP

If you are allowed to modify records (Cumulus Server Console user permission), you can modify the record field values and assign categories to the records in the catalog. UMP shows the category names in the currently selected language. You can also specify the localised category names inside the web application:

The localised Category Names in the UMP Web Application for ICP

6.1 Cumulus Client Connection

The new version provides even more setup dialogs to make it even easier for the Administrator to set the users' permissions. For some of the new functionalities UMP 4 uses a Cumulus Client Connection to read information out of your Cumulus catalogs. If a Client connection can not be established, the functionality is still there, but you might miss some comfort in setting of the permissions.

Cumulus Client Connection Indicator

You will find the information, if a Client Connection is established or not, on the upper left hand side of the users page. A Client Connection can not be established, if

• you are running out of Cumulus Client licenses
• the Java Classes serial number is not installed
• the Cumulus Client port 9287 is blocked by e.g. a firewall

So you want to make sure that your Cumulus Server installation has a valid Cumulus Java Classes serial number installed (and activated by your current Activation Key). The Cumulus Java Classes serial number is provided by Canto for free. Here are some of the serial numbers for the latest Cumulus versions:

UMP 4 only needs the read only access serial number installed to provide full functionality, as it only reads the information from the catalogs but does not make any changes to the catalog. You can find the serial number for your current Cumulus version, if it is not in the list above, on the Canto website at http://www.canto.com (> Download&Support).

6.2 Disable 'Save Permissions' on a UMP demo server

The Cumulus/UMP administrator can enable or disable all functions that modifies the user permissions in the Cumulus $Users catalog. This option is useful for sales partners to set up a User Management Pro demo server.

You can disable all saving functionality in the page '/UMP4_Admin/switch.jsp' in line 21:

session.setAttribute("com.hc.umpadmin.writeEnabled", "true");

Set the value of the attribute to "false" to disable the saving of permissions.

6.3 Filter group/username on UMP_Admin startup

The Cumulus/UMP administrator can set a group filter or a username filter that is used at startup of the UMP_Admin web application. You can specify these filters in the page '/UMP8_Admin/switch.jsp' in line 16/17:

session.setAttribute ("com.hc.umpadmin.groupFilter", "");
session.setAttribute ("com.hc.umpadmin.userFilter", "");

Set the value of the appropriate attribute to the group name or username to show the specified users at startup. You can also preset a username that is put into the clipboard at line 18:

session.setAttribute ("com.hc.umpadmin.clipboard", "");

6.4 Auto Login if only one catalog available

If only one catalog is available to the user, UMP opens the catalog for the user immediately without showing the list of available catalogs for selection. If more than one catalog is available to the user, the list of catalogs is displayed for selection.

6.5 Some additional modifications in UMP8

Permissions for the Cumulus Admin User

Please note that the Cumulus Admin User that you can specify in the Cumulus Server Console has all the available UMP permissions. So for your first testings of UMP, you should login as Cumulus Admin to have all the functionality of the web application available.

User Permission Reload

With the new UMP8 classes the user permissions will be reloaded whenever the RecordView is reloaded. So it is not necessary anymore to close the browser and open a new web browser session to have the new permissions available. Just reload the page set and you will have the configured permissions for the current user.

SelectCatalog3.jsp Login Page for direct login

The web applications come with a new login page ('/Standard/SelectCatalog3.jsp') which performs a direct login into the web application. This is very helpful for testing purposes, as you can have a URL which leads directly into a Cumulus Catalog with appropriate user permissions.

Inside the URL to access the page, you can specify the following attributes:

- user: specify the user name
- password: specify the user password
- catalog: specify the Cumulus Catalog name

Here is an example how to use a URL to connect to the 'Example Catalog UMP' as user 'cumulus':

http://myServer:8080/UMP8_WPP8/Standard/SelectCatalog3.jsp?user=cumulus&password=cumulus&catalog=Example%20Catalog%20UMP

Remark: blanks in attribute values are replaced automatically by '%20' through the web browser.

Your feedback is very much welcome!

Please send all your questions about the product to the email address support@heymann-consulting.de. We try hard to answer your questions quickly and improve our products by implementing functionality based on your feedback.

Remark: we do not offer a telephone hotline for this product. Please send in all your requests by email.

Version 8.0.0 - October 2009

The new version of User Management Pro 8 comes with two new web applications for Cumulus Web Publisher Pro 8 and Internet Client Pro 8.

Here are some of the modifications implemented in this software release:

- Cumulus Simple Mode and Advanced Mode (Users and! Roles) are now supported by the UMP_Admin web application
- Cumulus Admin has now all permissions inside the UMP web app
- Reload and New Session in the web browser will reload all user permissions, so it is not necessary to close the browser and to login again with a different user account
- SelectCatalog3.jsp implements a direkt login technology for testing
- various b ug fixes and modifications that were necessary to work with Cumulus 8
- CSS cleanup

Version 4.0.2 - September 2008

The new version of User Management Pro 4 comes with two new web applications for Cumulus Web Publisher Pro 7.6 and Internet Client Pro 7.6.

Version 4.0.1 - August 2007

The new version of User Management Pro 4 comes with two new web applications for Cumulus Web Publisher Pro 7.5.1 and Internet Client Pro 7.5.1. Please make sure that you are updating your version to the newer release of Cumulus 7.5, as Canto fixed a long list of bugs in the .1 release.

A new Spanish localisation file has been added to the UMP4_Admin web application.

The new version of User Management Pro 4 implements new powerful functionalities to let the Administrator restrict the users access to the Cumulus catalogs. It comes with a brand new UMP Admin web application. The good news for all User Management Pro 3 customers: No changes are necessary for using the new UMP Admin with your current UMP 3 web application! You just have to replace the UMP library file in your current web application by the new one to use the new functionality! So if you have made changes to the UMP3 web application, you do not have to reimplement all these changes in a new web application - just use your modified web application with the new library file.

The new version implements a better support for additional languages. Spanish has been added to the UMP and UMP_Admin web application. Thank you very much to our Spanish Partner Electronic Publishing Systems S.L. (special thanks to Francisco Villaverde), who localised the software and provided us with the necessary strings. The UMP_Admin web application is now also available in French. Thank you very much to our French Partner Avista Systems (special thanks to Pierre Saint Michel), who localised the software and provided us with the necessary strings.

The following changes have been implemented:

1) If a localised string is not found in the localisation files, an error message is displayed like '[***Language.Spanish missing***]'. This should help finding the missing strings in the localisation files.
2) A new language has been added to the web applications (Spanish). The tasks needed to add new languages to the web application have been documented in the chapter 2.5 How to add a new language to UMP.
3) The special characters in the French localisation file '/UMP/WEB-INF/classes/UMP_fr_fr.properties' have been converted to their HTML representation.
4) The Standard Language will now be read from UMP_Admin configuration.
5) Added a block of Strings for the translation of the Cumulus Fields (for sorting and searching) to the Spanish localisation file '/UMP/WEB-INF/classes/UMP_es_es.properties' (lines 82-105). The Sort Field Names of the standard Cumulus languages come out of the Cumulus Catalog, but as Spanish is not one of the standard languages, the field names have to be localised. This block of strings is necessary for all additional 'Non-Cumulus' languages.
6) Added a new TAG 'modifySorting' to the JSP page '/Standard/RecordViewContentHeader.jsp' (lines 18/28). The TAG localises the list of sort fields for NON-Standard Cumulus languages (like Spanish).
7) All special character (like German Umlauts and special French characters) are now converted into their HTML representations in the localisation files in the UMP and UMP_Admin web applications.
8) Changed the language priorities: 1. the language is defined in a URL parameter, 2. if not available, the language is set in the UMP_Admin configuration, 3. if not available, the language is taken from the user's Web Browser, 4. if 3. does not match one of the supported languages, the language is set to English ('en_US').
9) UMP_Admin modifyRoles.jsp: line 51 changed alert('...') to alert("..."). This allows to use the ' character in the 'errNoViewAssigned' error message, which is especially import in French.
10) Added new localisation option for the Cumulus Catalog fields for the non-standard languages. It is now possible to translate the names of the fields in all available languages.
11) Added new localisation option for the stored Cumulus Search Queries to the localisation files. It is now possible to translate the names of the stored Queries that are visible to the user in all available languages.
12) Added translated Strings to the 'NewUser.jsp' page.

To sum up the changes in the web pages, here is the list of files in the web applications that have been changed:

UMP web application:
Login.jsp, RecordViewTitle.jsp, RecordViewContentHeader.jsp, SearchForm.jsp, SearchFormMore.jsp, NewUser.jsp

UMP_Admin web application:
login.jsp, selectLanguage.jsp, selectConfigLanguage.jsp, modifyRoles.jsp

To use the new technology with your User Management Pro 3.0/3.0.1 implementation, please implement the changes described above into the JSP pages. As the JAVA libraries have been changed also, copy the new versions of the files into your web application:

/WEB-INF/HC_UserManagementPro3.tld
/WEB-INF/lib/HC_UserManagementPro3.jar

The new version is a bugfix release of the software for Web Publisher Pro and Internet Client Pro. Please find detailed information about the changes in the web application in the text file 'ChangesUMP301.txt' delivered with the software.

The User Management Pro and the User Management Pro Administration Web Application have been developed for Canto Cumulus 6.6 and Web Publisher Pro and Internet Client Pro version 3.0 shipped since end of July 2005. This is the first version of the Administration web application, but the version number follows the version number of the User Management Pro web application.