Filr1 Inst

www.novell.
com/documentation
Installation and Configuration Guide

Novell Filr 1.0
April 30, 2013
Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically
disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any
person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right
to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of
such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade
laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or
classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S.
export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use
deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade
Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software. Novell assumes
no responsibility for your failure to obtain any necessary export approvals.
Copyright 2013 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc.
1800 South Novell Place
Provo, UT 84606
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see the Novell
Documentation Web page (http://www.novell.com/documentation).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/trademarks/
tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
Contents
About This Guide
1 Overview and Planning

1.1
1.2
1.3
1.4
1.5
What Is Novell Filr? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1.1
Filr Applications and Appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1.2
Filr Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.3
Filr Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1.4
Using Novell Filr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Filr System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.1
Filr Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.2
Filr User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.3
Mobile App Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.4
Desktop Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.5
File Viewer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2.6
Linux File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Planning a Multi-Server (Clustered) Filr Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.1
Components of a Clustered Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.2
Filr Clustering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Planning the File Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4.1
Distributing Different Data Types to Different Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Recommended Hardware Configurations Based on System Performance . . . . . . . . . . . . . . . . . . . . 17
1.5.1
Net Folder Indexing and Synchronization Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.5.2
Resource Allocations for the Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.5.3
Small Installation Vs. Large Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 Installing the Filr Appliance and Configuring the Operating System

2.1
2.2
21
Installing the Filr Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Installing Separate Appliances for a Large Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.1
Installing the Search Index Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.2
Installing the MySQL Database Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3 Configuring Filr for the First Time

3.1
3.2
33
Small Deployment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Large Deployment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4 Configuring and Maintaining the Filr Appliance

4.1
4.2
4.3
4.4
37
Changing Configuration Options for the Filr Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.2.1
Changing the Network Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.2.2
Port Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.3.1
Understanding Database Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.3.2
Changing Database Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.3.3
Database Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.3.4
Database Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.3.5
Database Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Contents
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
5 Configuring and Maintaining the Search Index Appliance
55
6 Configuring and Maintaining the MySQL Database Appliance
57
7 Configuring and Maintaining the Novell Appliance
61
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
Changing Administrative Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Changing Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Changing Time Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Replacing the Self-Signed Digital Certificate for an Official Certificate . . . . . . . . . . . . . . . . . . . . . . . 62
7.4.1
Using the Digital Certificate Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.4.2
Using an Existing Certificate and Key Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
7.4.3
Activating the Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Changing the Ganglia Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Changing System Services Configuration (SSH, Filr, Jetty, Postfix, and FAMT). . . . . . . . . . . . . . . . 65
7.6.1
Starting, Stopping, or Restarting System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.6.2
Making System Services Automatic or Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
7.6.3
Downloading Log Files for System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Viewing the Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Shutting Down and Restarting the Novell Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
8 Setting Up the Filr Site
69
9 Updating Filr
71
9.1
9.2
Changing Your Search Index Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.5.1
Understanding Indexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.5.2
Changing Search Index Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.5.3
Running the Search Index As Its Own Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.5.4
Running Multiple Search Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Changing Clustering Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Changing Reverse Proxy Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.7.1
Understanding Reverse Proxy and NetIQ Access Manager . . . . . . . . . . . . . . . . . . . . . . . . 46
4.7.2
Understanding How Port Redirection Affects Reverse Proxy Settings . . . . . . . . . . . . . . . . 47
4.7.3
Changing Reverse Proxy Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Changing Outbound Email Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.8.1
Understanding Outbound Email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.8.2
Changing Outbound Email Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.8.3
Outbound Email Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.8.4
Outbound Email Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.8.5
Outbound Email Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Changing Configuration Settings for Requests and Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Changing the Java JDK Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Changing WebDAV Authentication Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.11.1 Understanding WebDAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.11.2 Changing the WebDAV Authentication Configuration Settings . . . . . . . . . . . . . . . . . . . . . . 52
4.11.3 Choosing the WebDAV Authentication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Viewing and Updating the Filr License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Updating the Filr Appliance and the Search Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Novell Filr 1.0 Installation and Configuration Guide
Part I Appendixes
75
A Troubleshooting the Filr System
77
A.1
A.2
Using VACONFIG to Modify Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Accessing Filr Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
B Third-Party Materials
B.1
B.2
B.3
B.4
B.5
B.6
B.7
B.8
B.9
B.10
79
Oracle Outside In Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

ANTLR 3 License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Colt License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Dom4j License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
iCal4j License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
ICU4J license (ICU4J 1.3.1 and later) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
JAXEN License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Jung . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
ASM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Firebug Lite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Contents
About This Guide

The Novell Filr 1.0 Installation Guide covers the installation and configuration of Novell Filr. The guide
is divided into the following sections:
Chapter 1, Overview and Planning, on page 9
Chapter 2, Installing the Filr Appliance and Configuring the Operating System, on page 21
Chapter 3, Configuring Filr for the First Time, on page 33
Chapter 4, Configuring and Maintaining the Filr Appliance, on page 37
Chapter 5, Configuring and Maintaining the Search Index Appliance, on page 55
Chapter 6, Configuring and Maintaining the MySQL Database Appliance, on page 57
Chapter 7, Configuring and Maintaining the Novell Appliance, on page 61
Chapter 8, Setting Up the Filr Site, on page 69
Chapter 9, Updating Filr, on page 71
Part I, Appendixes, on page 75
Audience
This guide is intended for Novell Filr administrators.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation.
Documentation Updates
For the most recent version of this manual, visit the Novell Filr 1.0 Documentation Web site (http://
www.novell.com/documentation/novell-filr1).
Additional Documentation
You can find more information in the Novell Filr documentation, which is accessible from the Novell
Filr 1.0 Documentation Web site (http://www.novell.com/documentation/novell-filr1).
To access the Novell Filr User Guide from within Filr, click the Help icon (question mark).
About This Guide
Overview and Planning
This section provides overview information that is useful to you as you install Novell Filr. For more
in-depth overview material, see Filr Overview in the Novell Filr 1 How Filr WorksOverview Guide.
Section 1.1, What Is Novell Filr?, on page 9
Section 1.2, Filr System Requirements, on page 13
Section 1.3, Planning a Multi-Server (Clustered) Filr Configuration, on page 15
Section 1.4, Planning the File Repository, on page 16
Section 1.5, Recommended Hardware Configurations Based on System Performance, on
page 17
1.1
What Is Novell Filr?

Novell Filr is an enterprise file management tool designed to share files by leveraging your security
infrastructure, both internally as well as externally. Filr gives you access to corporate files (including
files that are located on mapped drives) and lets you access them from a mobile app on a mobile
device, from a desktop application on your workstation, or from a Web browser.
Section 1.1.1, Filr Applications and Appliances, on page 9
Section 1.1.2, Filr Components, on page 10
Section 1.1.3, Filr Storage, on page 11
Section 1.1.4, Using Novell Filr, on page 12
1.1.1
Filr Applications and Appliances

It is important to distinguish between Filr applications and appliances.
Applications on page 9
Appliances on page 10
Applications
Filr applications are client interfaces that allow users to access the Filr software. There are three Filr
applications:
Web application
See the Filr Web Application User Guide (http://www.novell.com/documentation/novell-filr1/
filr1_user/data/bookinfo.html) for information about how to use the Filr Web application.
After installing Filr, you can log in to the Web application. Review the information in Site
Setup in the Novell Filr 1.0 Administration Guide for information about how you can configure
your Filr site.
Desktop application
See the Filr Desktop for Windows Quick Start (http://www.novell.com/documentation/novellfilr1/filr1_qs_desktop/data/filr1_qs_desktop.html) and the Filr Desktop for Mac Quick Start
(http://www.novell.com/documentation/novell-filr1/filr1_qs_desktopmac/data/
filr1_qs_desktop.html) for information about how to use the desktop application.
Before the desktop application can be available to users, you need to configure it for your Filr
site, as described in Configuring the Filr Desktop Application to Access Files in the Novell Filr
1.0 Administration Guide.
Mobile app
See the Filr Mobile Quick Start (http://www.novell.com/documentation/novell-filr1/
filr1_qs_mobile/data/filr1_qs_mobile.html) for information about how to download and use the
mobile app.
Appliances
Appliances are prepackaged software bundles designed to reduce installation and configuration
overhead. Components that make up a Filr site can be deployed either as a single appliance for small
installations or as multiple appliances for larger installations. Filr appliances run as virtual machines
within a VMware environment. For more information about the individual Filr components, see
Section 1.1.2, Filr Components, on page 10.
1.1.2
Filr Components
A Novell Filr site consists of three major components. In very small deployments, each of these
components is part of the Filr appliance. In large deployments, the software, the database, and the
search index run as separate appliances.
Filr Software on page 10
Filr Database on page 10
Search Index on page 11
Filr Software
The Filr software is a customized version of Apache Tomcat. This software provides the Web-based
functionality you use as you access the Filr site through your Web browser.
This component is either part of the Filr appliance along with the other components, or it is the standalone component of the Filr appliance to enhance performance. For more information, see Chapter 2,
Installing the Filr Appliance and Configuring the Operating System, on page 21.
Filr Database
The Filr database is a MySQL database that is used for storing information about the Filr site and its
users:
Structural information about folders and files
Identification information about folders and files (for example, titles, descriptions, dates of
creation/modification, and users associated with creation/modification)
User profile information (for example, full name, phone number, and email address)
10
The Filr database disk space requirements are relatively modest, because the database is not used for
storing files.
This component can either be installed as part of the Filr appliance or it can be installed as a separate
appliance to enhance performance. For more information, see Chapter 2, Installing the Filr
Appliance and Configuring the Operating System, on page 21.
Search Index
The search index is a high-performance Java search engine built with Lucene technology. The search
index contains pointers to the actual data stored in the Filr file repository. The index enables the
search engine to perform very fast searches through large quantities of Filr data.
This component can either be installed as part of the Filr appliance or it can be installed as a separate
appliance to enhance performance. For more information, see Chapter 2, Installing the Filr
Appliance and Configuring the Operating System, on page 21.
1.1.3
Filr Storage
Data for the Filr system is stored in the following three areas:
MySQL Database on page 11
Data Storage for the Appliance on page 11
Configuration Data for the Appliance on page 11
MySQL Database
The MySQL database is used to store MySQL data files, including tablespace data files, tablespace log
files, and binary log files. It is also used to store comments on files and folders.
The MySQL database can be part of the all-in-one appliance (small installation), can be configured as
a separate appliance (large installation), or you can leverage an existing MySQL database.
Data Storage for the Appliance

When you set up Filr (either as a single appliance in a small installation or as separate appliances for
a large installation), you configure data to reside either on a hard disk or on a remote NFS.
The following kinds of data are stored for each appliance on the hard disk or remote NFS:
All appliances: Web application certificates for Jetty and Tomcat and the Ganglia RRD database.
Filr appliance: Data for the Filr appliance (located in the /Cachefilestore and /conf, /extension,
/filerepository, /temp direcotries).
Search index appliance: Data for the Lucene search index appliance.
MySQL database appliance: Data for the MySQL database appliance.
Configuration Data for the Appliance

Configuration information for each appliance is stored on the appliance itself, and can be exported
during and update process and then re-imported.
For more information, see Chapter 9, Updating Filr, on page 71.
11
1.1.4
Using Novell Filr

Novell Filr lets you work with files in important ways:
Access: Access the files you need in multiple ways, including from a Web browser, from your
desktop, or from a mobile device.
For more information, see Accessing Novell Filr in the Novell Filr 1.0 Web Application User
Guide.
Share: Share files with your co-workers and grant them specific rights to the files. For example,
you can share a file with User A with Read-Only access, then share the same file with User B
with Edit access.
You can easily see what has been shared with you and what you have shared.
For more information, see Sharing Files and Folders in the Novell Filr 1.0 Web Application User
Guide.
Collaborate: Make comments on a file, then all users with access can see your comments and
make comments of their own.
For more information, see Commenting on a File in the Novell Filr 1.0 Web Application User
Guide.
Filr allows you to access, share, and collaborate on files that are in two key locations:
Files in Net Folders on page 12
My Files on page 12
Files in Net Folders

Novell Filr gives you easy access to folders and files on your corporate file system. Corporate files can
be files on your home drive, files on a mapped drive, or files on a remote server. Filr gives you
seamless access to these files, regardless of their location. The corporate files that you have access to
are defined by your Filr administrator.
In Filr, you access these corporate files by clicking Net Folders in the masthead. For more information
about Net Folders, see the Novell Filr 1.0 Web Application User Guide.
My Files
Users can upload files directly to the Filr site for personal use or to promote collaboration. Users can
create folders to better organize files. For more information about how to upload files, see Adding
Files to a Folder in the Novell Filr 1.0 Web Application User Guide.
Files and folders that are located in a users My Files area are visible only to that user by default.
Users can make files and folders available to others by sharing them, as described in Sharing Files
and Folders in the Novell Filr 1.0 Web Application User Guide.
Unlike files in the Net Folders area, files in My Files do not exist on an external server, but rather on
the Filr server itself. Users can access these files by clicking My Files in the masthead.
12
1.2
Filr System Requirements

You, as a Novell Filr site administrator, must ensure that your system meets Filr system
requirements, so that your Filr site can be set up successfully. After your Filr site is set up, you must
ensure that users browsers and office applications meet Filr user requirements, so that users can
access the Filr site successfully.
Section 1.2.1, Filr Server Requirements, on page 13
Section 1.2.2, Filr User Requirements, on page 14
Section 1.2.3, Mobile App Requirements, on page 14
Section 1.2.4, Desktop Application Requirements, on page 14
Section 1.2.5, File Viewer Information, on page 15
Section 1.2.6, Linux File System, on page 15
For the latest system requirements details, see the Novell Filr 1.0 Readme (http://www.novell.com/
documentation/beta/novell-filr1/filr1_readme_novell/data/filr1_readme_novell.html).
1.2.1
Filr Server Requirements

a VMware ESXi (or ESX) 4.1.x, or VMware ESXi (or ESX) 5.x host server for hosting the Filr
appliance.
A VMware vSphere client 4.x or VMware vSphere client 5.x for accessing the host server and
appliance for initial configuration.
A minimum of 12 GB of RAM and 100 GB of disk space on the host server for a small Filr
installation. For a large Filr installation, a minimum of 8 GB of RAM and 100 GB of disk space for
the Filr appliance, 4 GB of RAM and 25 GB of disk space for each Lucene index server appliance,
and 4 GB of RAM and 100 GB of disk space for the MySQL database appliance.
A workstation (Windows, Mac, or Linux) capable of running one of the supported browsers.
Mozilla Firefox 9, Mozilla Firefox 10, Microsoft Internet Explorer 8, or Microsoft Internet
Explorer 9 for configuring and managing the appliance after the initial setup.
IP address information for assigning to the Filr appliance, including:
Static IP address
Network mask
Gateway IP address
DNS host name associated with the IP address
IP address of a DNS server
IP address or DNS name of the same NTP server that your target OES servers use (optional)
Any combination of the following file servers (You can configure Net Folders in Filr to access
files on these file servers. File servers are not required when you use Filr for files in the My Files
area):
One or more Windows 2003 R2 or Windows 2008 R2 file servers with one or more Windows
Shares as data targets for the Filr virtual appliance
One or more OES 2 SP3 or OES 11 or later file servers with one or more NSS volumes as
data targets for the Filr virtual appliance
One or more NetWare 6.5.8 and later file servers with one or more NSS volumes as data
targets for the Filr virtual appliance (must be using eDirectory 8.8 as the directory service)
13
A directory service: (Not mandatory for simple testing)

Linux: Novell eDirectory 8.8 or later, plus the latest Support Pack
For information about eDirectory, see the Novell eDirectory 8.8 Documentation Web site
(http://www.novell.com/documentation/edir88).
Windows: Microsoft Active Directory, plus the latest Service Pack, or Novell eDirectory 8.8
or later, plus the latest Support Pack
For information about Active Directory, see Windows Server 2003 Active Directory (http://
www.microsoft.com/windowsserver2003/technologies/directory/activedirectory) or
Windows Server 2008 Active Directory (http://www.microsoft.com/windowsserver2008/en/
us/active-directory.aspx).
1.2.2
Filr User Requirements

Web browser (for accessing Filr through a browser on your user workstation):
Linux: Mozilla Firefox 3 or later; Google Chrome (latest version)
Windows: Microsoft Internet Explorer 7 or later (must not have the Google Chrome Frame
plug-in installed); Mozilla Firefox 3 or later; Google Chrome (latest version)
Mac: Safari 4 or later; Mozilla Firefox 3 or later
Office applications (for editing documents on your workstation, as described in Editing Files
with Edit-in-Place in the Novell Filr 1.0 Web Application User Guide):
Linux: OpenOffice.org/LibreOffice 3.1.1 or later
Windows: Microsoft Office 2007 or later; OpenOffice.org/LibreOffice 3.1.1 or later
Mac: OpenOffice.org/LibreOffice 3.1.1 or later
NOTE: OpenOffice and LibreOffice are used synonymously throughout the Novell Filr
documentation. Functionality and issues that apply to OpenOffice also apply to LibreOffice.
1.2.3
Mobile App Requirements

The Novell Filr mobile app is supported on the following mobile devices:
iPhone (the native application is available in the iTunes Store)
Android (the native application is available in the Google Play App Store and in the Amazon
Appstore for Android)
For more information about the Filr mobile app, see the Novell Filr Mobile App Quick Start (http://
www.novell.com/documentation/beta/novell-filr1/filr1_qs_mobile/data/filr1_qs_mobile.html).
1.2.4
Desktop Application Requirements

The Filr desktop application is supported on the following client operating systems:
Windows XP and later.
Mac OS X 10.7 and later.
For more information about the Filr desktop application, see the Novell Filr Desktop Application for
Windows Quick Start (http://www.novell.com/documentation/novell-filr1/filr1_qs_desktop/data/
filr1_qs_desktop.html) or Novell Filr Desktop Application for Mac Quick Start (http://
www.novell.com/documentation/novell-filr1/filr1_qs_desktopmac/data/filr1_qs_desktop.html).
14
1.2.5
File Viewer Information

In Novell Filr, file viewing capabilities are provided by Oracle Outside In viewer technology. See
Oracle Outside In Technology 8.3 Supported Formats (http://www.oracle.com/us/026956.pdf) for a
list of the supported file formats. See Oracle Outside In Technology (http://www.oracle.com/
technologies/embedded/outside-in.html) for background information about the Oracle viewer
technology included in Filr.
The file viewers also support data indexing by the search index.
1.2.6
Linux File System

Filr supports the following file systems on Linux: ext3, btrfs, and xfs.
1.3
Planning a Multi-Server (Clustered) Filr Configuration

Section 1.3.1, Components of a Clustered Environment, on page 15
Section 1.3.2, Filr Clustering, on page 15
1.3.1
Components of a Clustered Environment

In a large installation, the Filr components can be deployed as separate appliances.
Filr Appliance: You can run multiple instances of the Filr appliance, which allows the Filr system to
handle more users. For information about installing multiple Filr appliances, see Section 2.1,
Installing the Filr Appliance, on page 21.
Lucene Index Server Appliance: You can run multiple instances of the Lucene index server
appliance (no more than two is recommended), which provides fault tolerance or backup in the event
that one index server fails. Load balancing is not supported between index servers. For information
about installing multiple Lucene index server appliances, see Section 2.2.1, Installing the Search
Index Appliance, on page 25.
MySQL Database Appliance: You can run only one instance of the MySQL database appliance. For
information about installing a MySQL database appliance, see Section 2.2.2, Installing the MySQL
Database Appliance, on page 28.
For information about possible configuration setups and how many users are appropriate for each
setup, see Section 1.5, Recommended Hardware Configurations Based on System Performance, on
page 17.
1.3.2
Filr Clustering
Filr clustering involves two or more Filr VAs sharing the same NFS data storage location (/vashare).
Basic steps for setting up Filr clustering are included in Figure 1-1.
15
Figure 1-1 Clustered Filr VAs
Installing
Admin
NFS Server
1. Access an NFS Server.
Shared
Storage
Remote NFS Directory

2. Export a Directory.
(NFS ready for Remote Mounting)
3. Deploy a Filr VA
4. Specify (mount) the remote NFS
directory as /vashare.
Filr
Filr
Filr
Filr
5. Access the Filr Appliance Administration

Console and click Clustering.
vaadmin
6. Enable Clustering on each Filr VA.
7. Specify each Filr VA in the cluster.
192.168.1.110:11211 192.168.111:11211 19
For more information about clustering, see Changing Clustering Configuration Settings in the Novell
Filr Installation and Configuration Guide.
1.4
Planning the File Repository

Section 1.4.1, Distributing Different Data Types to Different Locations, on page 16
1.4.1
Distributing Different Data Types to Different Locations

The location for the Novell Filr file repository is /vastorage/filr.
The data files not stored in the Filr database are divided into several functional areas:
Simple file repository: A large consumer of disk space.
All attachment files are stored in the file repository.
Archive store: A large consumer of disk space.
When files are deleted, files are retained in the archive store in order to meet compliance and
archival goals. After files have been archived, they are inaccessible from the Filr site. Files that
accumulate in the archive store must be manually deleted as needed to manage the disk space
occupied by the archive store.
Cache store: Consumes less disk space than the file repository.
16
Information derived from the attachments, such as thumbnails, HTML renderings, scaled
images, and word lists for indexing are stored in the cache store.
Lucene index: Takes only a fraction of the space consumed by the file repository.
The Lucene index contains only pointers to the actual data stored in the file repository. The index
enables the Lucene search engine to perform very fast searches through large quantities of data.
1.5
Recommended Hardware Configurations Based on System

Performance
Because of the wide variety of content you can store in Filr and the load any given user might put on
the system, the recommendations given in this section are only guidelines.
The following sections represent configuration changes that you can make to your Filr installation
that affect the amount of users and data that the system can support.
Section 1.5.1, Net Folder Indexing and Synchronization Settings, on page 17
Section 1.5.2, Resource Allocations for the Appliance, on page 17
Section 1.5.3, Small Installation Vs. Large Installation, on page 17
1.5.1
Net Folder Indexing and Synchronization Settings

How you plan to index and synchronize data in Net Folders can affect how much data the Filr system
can support.
Performing a full synchronization every hour puts more load on the system than performing an
initial full synchronization, then using only Just-in-Time synchronization. (For more information, see
Planning Synchronization in the Novell Filr 1.0 Administration Guide.)
Whether you want to index file content also affects the amount of load that is placed on the system.
If you plan to perform a full synchronization and index for Net Folders in your Filr system, ensure
that these processes have taken place before users attempt to access the system.
1.5.2
Resource Allocations for the Appliance

Increasing memory and CPU resources for an appliance can sometimes be more favorable than
adding another appliance. You might need to adjust CPU and Memory settings for each appliance
before you can determine the optimal setting for your environment.
1.5.3
Small Installation Vs. Large Installation

IMPORTANT: You cannot upgrade your Filr system from a small installation to a large installation.
Likewise, you cannot upgrade from a large installation to a clustered installation if shared storage
has not already been configured. If your Filr system has the potential to grow, you should install Filr
in a large installation and create shared storage (as described in Step 20 in Section 2.1, Installing the
Filr Appliance, on page 21). Doing so ensures that you can scale your system in the future if the need
arises by adding additional Filr appliances
17
The following sections describe guidelines for deploying either a small or large Filr installation.
Small Installation on page 18
Large Installation on page 18
Small Installation
A small installation, where all Filr components are running on a single Filr appliance, is suitable for
systems with:
No more than 300 active users (users who regularly access the Filr system from any of the Filr
clients)
No more than 2,500 folders in Net Folders
No more than 50,000 files in Net Folders
Large Installation
A large installation, where each Filr component is running as a separate appliance, is recommended
for systems with any of the following:
More than 300 active users (users who regularly access the Filr system from any of the Filr
clients)
More than 2,500 folders
More than 50,000 files
When you set up a large installation, ensure that you create a shared storage location (as described in
Step 20 in Section 2.1, Installing the Filr Appliance, on page 21). Doing so makes it possible to move
to a clustered installation in the future, where there are multiple Filr appliances and Lucene index
search appliances.
A basic large installation consists of a Filr appliance, a Lucene index appliance, and a MySQL
database appliance.
A clustered installation consists of multiple Filr appliances, multiple Lucene index server appliances,
and a single MySQL database appliance.
18
Advantages of a Clustered Installation

In a clustered installation, you can have multiple Filr appliances and multiple Lucene search index
appliances.
Provides scalability
As more users begin using the system and more data is added, you can add more Filr appliances
to accommodate the load. You can also add a second Lucene search index appliance, which can
help improve scalability.
Provides fault tolerance
In the event that one Filr appliance goes down, other Filr appliances are there to maintain the
system. This is also true with the Lucene search index appliance. It is optimal for your Filr
system to have two Lucene search index appliances.
19
20
Installing the Filr Appliance and

Configuring the Operating System
The following sections describe how to download and install the Filr software, MySQL database, and
search index software, either as a single appliance for a small installation, or as separate appliances
for a large installation.
NOTE: Before you download and install the Filr appliance, the MySQL database appliance, and the
search index appliance, ensure that:
The server requirements in Section 1.2.1, Filr Server Requirements, on page 13 have been met
You have read and understand Chapter 1, Overview and Planning, on page 9
Section 2.1, Installing the Filr Appliance, on page 21
Section 2.2, Installing Separate Appliances for a Large Installation, on page 25
2.1
Installing the Filr Appliance

IMPORTANT: Filr appliance installation is the same for large (multiple appliance) and small (all-inone appliance) installations.
This section describes how to install the Filr appliance, which includes the Filr software, the MySQL
database, and the search index. For a small installation with limited system resources, you can install
only this appliance. For a large installation, you need to install one or more Filr appliances (this
section describes how to install the Filr appliance), then install separate appliances for the MySQL
database and the search index, as described in Section 2.2, Installing Separate Appliances for a Large
Installation, on page 25.
1 Download the Filr software (Filr.x86_64-version.ovf.zip) to your management
workstation.
You can access the file from the Novell Downloads page (http://download.novell.com).
2 Extract the Filr.x86_64-version.ovf.zip file on your management workstation so that the
Filr-version file folder appears.
3 In the vSphere client, click File > Deploy OVF Template.
4 Browse to and select the .ovf file in the Filr-version file folder.
5 Click Next.
6 Click Next again.
7 In the Name field, rename the Filr appliance to a name of your choosing, then click Next.
8 Click Next to accept the default for the disk format.
9 Click Finish.
Installing the Filr Appliance and Configuring the Operating System
21
10 Create a separate VMware hard disk for the appliance. This is the location where you will store
your Filr files (files that are located in users My Files area). If you do not create a separate
VMware hard disk as described here, you cannot update to a new version of Filr.
10a In the vSphere client, right-click the virtual machine that you just created for which you
want to create secondary storage, then click Edit Settings.

The Virtual Machine Properties page is displayed.
10b On the Hardware tab, click Add.
The Add Hardware dialog box is displayed.

10c Select Hard Disk, then click Next.
10d Leave Create a new virtual disk selected, then click Next.
10e In the Disk Size field, specify the amount of hard disk space that you want to allocate. Novell
recommends a minimum of 100 GB.

10f In the Disk Provisioning section, select either Thick Provision Eager Zeroed or Support clustering
features such as Fault Tolerance, depending on the VMware version that you are running.
10g In the Location section, select Specify a datastore or datastore cluster, then click Browse.
10h Select a datastore, then click OK.
10i Click Next.
10j In the Virtual Device Node section, select SCSI (1:0) from the drop-down list.
10k In the Mode section, select Independent, then select Persistent, then click Next.
10l Click Finish.
11 Increase the amount of memory that VMware allocates for the Filr appliance.
The default of 8 GB is the recommended minimum amount of memory for a large deployment.
Novell also recommends 2 CPUs. At least half of the memory should be dedicated to the Java
heap.
For an all-in-one deployment, you should increase the default to at least 12 GB of memory (with
8 GB of memory being dedicated to the Java heap) and 4 CPUs.
11a In the Virtual Machine Properties window, select Memory, then increase the setting to a
suitable size for your environment.

IMPORTANT: When you increase or decrease server memory for the Filr appliance or the
search index appliance, you should also modify the Java heap size, as described in
Section 4.10, Changing the Java JDK Configuration Settings, on page 51 and Chapter 5,
Configuring and Maintaining the Search Index Appliance, on page 55.
You cannot do this until after the appliance is installed.
11b Click OK to exit the Virtual Machine Properties window.
12 Power on the appliance (virtual machine).
IMPORTANT: Do not power on the appliance until you have created a separate VMware hard
disk for the appliance, as described in Step 10.
13 Click the Console tab. After the appliance starts, select your preferred keyboard layout in the
Keyboard Language drop-down, then accept the license agreement.

You can change the language the license agreement is displayed in from the License Language
drop-down.
22
14 Specify the following network information:
Root password and confirmation: The root password for your Filr appliance.
Vaadmin password and confirmation: The preferred user to use when logging in to the
appliance.
Hostname: The fully qualified DNS host name associated with the appliances IP address. For
example, myFilr.mynetwork.example.com.
IP Address: The static IP address for the appliance. For example, 172.17.2.3.
Network Mask: The network mask associated with the appliances IP address. For example,
255.255.255.0.
Gateway: The IP address of the gateway on the subnet where your Filr virtual appliance is
located. For example, 172.17.2.254.
DNS Servers: The IP address of a primary DNS server for your network. For example,
172.17.1.1.
NTP Server: The IP address or DNS name of the reliable external Network Time Protocol (NTP)
server your OES server uses. For example, time.example.com.
Region: Your local region.
Time Zone: Your local time zone.
The time zone of your Filr server should match the time zone of all file servers that Filr will point
to via Net Folders.
NOTE: If after installation you are not able to access the appliance and you need to change any
of these settings, you can use the VACONFIG utility from the Filr command prompt. For more
information about how to access the VACONFIG utility, see Section A.1, Using VACONFIG to
Modify Network Information, on page 77.
15 Click Next.
23
16 Select the data storage location. This is the location (/vastorage) where information specific to
the appliance is stored and is used when the appliance is upgraded. Each appliance has its own
/vastorage location.
Hard Disk (recommended): This option is recommended for both small and large
deployment scenarios. You must assign a hard disk to the virtual machine before you
choose this option. If you have not already assigned a hard disk, click Power Off Virtual
Machine, modify the virtual machine settings to add a hard disk, then power on the virtual
machine. If you created a secondary VMware hard disk for this appliance as described in
Step 10, select this option.
Remote NFS: Use a remote NFS location only in a large deployment scenario, where you
plan to configure all Filr servers (Filr, Filr Search, and MySQL) as separate virtual machines.
You must export the remote directory before you choose this option. Not applicable for a
small installation where you plan to install all components as a single appliance.
For more information about the type of data that is stored here, see Data Storage for the
Appliance on page 11.
17 Click Next.
18 (Conditional) If you selected Hard Disk in Step 16, specify the following options, then click Next:
Hard Drive: Select the hard drive you are using.

If you created a secondary VMware hard disk for this appliance as described in Step 10, it is
automatically detected and sdb is displayed as the hard drive. Accept the defaults for the other
options on this page and skip to Step 21.
Use an existing partition: Select this option to use an existing partition.
Create a new partition: Select this option to create a new partition.
Partition size: Specify the partition size.
Filesystem type: Specify the type of file system.
19 (Conditional) If you selected Remote NFS in Step 16, specify the following options:
NFS Server Hostname: Specify the host name of the NFS server.
Remote Directory: Specify the path to the remote directory. As a best practice, use vastorage as
the name for the directory on the remote NFS server. For a clustered environment (where you
have a separate mount point on the NFS server for each Filr appliance), you should give each
vastorage directory a unique name that represents each Filr appliance. For example,
vastorageA, vastorageB.
20 Select whether you want to configure shared storage for a clustered environment. This storage (/
vashare) is shared storage among all of the Filr appliances in the cluster. There is only one /
vashare storage location that is used by all Filr appliances in the cluster.
If your Filr system has the potential to grow, you should configure shared storage with your
initial Filr installation. Doing so ensures that you can scale your system in the future if the need
arises by adding additional Filr appliances.
Do Not Configure Shared Storage: Select this option if you do not plan to run Filr in a
clustered environment. This is suitable for a small installation where you plan to install all
components as a single appliance. This is also suitable for a large installation where you
plan to install only one Filr appliance. However, if you plan to grow your Filr system in the
future, you should not select this option. Skip to Step 22.
Remote NFS: (Recommended) Select this option if you plan to set up a clustered
environment with multiple Filr appliances. You must export the remote directory before
you choose this option. Also, set the rw and no_root_squash options on the remote
directory.
24
For more information about possible configurations when running Filr in a clustered
environment, see Section 1.5, Recommended Hardware Configurations Based on System
Performance, on page 17.
21 (Conditional) If you are configuring Filr for a clustered environment:
21a Click Next.
21b Specify the following options:
Remote Directory: Specify the path to the remote directory. As a best practice, use vashare
as the name for this directory on the remote NFS server.
22 Click Configure.
A message saying that the installation was successful is displayed.

23 If you are performing a small installation with all components running on a single appliance,
continue with the configuration of the appliance, as described in Chapter 3, Configuring Filr
for the First Time, on page 33.
or
If you are performing a large installation, continue with Section 2.2, Installing Separate
Appliances for a Large Installation, on page 25.
or
If you are performing a clustered installation, install another Filr appliance as described in this
section (Section 2.1, Installing the Filr Appliance, on page 21) until you have installed your
desired number of Filr appliances, then continue with Section 2.2, Installing Separate
Appliances for a Large Installation, on page 25.
2.2
Installing Separate Appliances for a Large Installation

In a large installation, the Filr software, the MySQL database, and the search index can each run as a
separate appliance.
Running the Filr software, the MySQL database, and the search index as separate appliances allows
each component to have access to more server memory, disk space, and CPU resources. There can be
multiple Filr appliances, multiple search index appliances, and multiple database appliances.
You should have already installed the Filr appliance, as described in Section 2.1, Installing the Filr
Appliance, on page 21. The following sections describe how to install the search index appliance
and the MySQL database appliance.
You must configure the MySQL database appliance to change the database administrator password
before you configure the Filr appliance for the first time.
Section 2.2.1, Installing the Search Index Appliance, on page 25
Section 2.2.2, Installing the MySQL Database Appliance, on page 28
2.2.1
Installing the Search Index Appliance

1 Download the Lucene search index software (Filrsearch-version.ovf.zip) to your
management workstation.
2 Extract the Filrsearch-version.ovf.zip file on your management workstation until the
Filrsearch-version file folder appears.
25

4 Browse to and select the .ovf file in the Filrsearch-version file folder.
5 Click Next.
6 Click Next again.
9 Click Finish.
10 Create a separate VMware hard disk for the appliance. If you do not create a separate VMware
hard disk as described here, you cannot update to a new version of the appliance.


10d Leave Create a new virtual disk selected, then click Next.
10e Specify the amount of hard disk space that you want to allocate. Novell recommends a
minimum of 25 GB.
10i Click Next.
10l Click Finish.
11 Increase the amount of memory that VMware allocates for the appliance.
The default is 4 GB. This default is appropriate for a system that has a few hundred to 1,000
users. You should increase this if your user count exceeds 1,000. Novell also recommends 2
CPUs.
11a In the Virtual Machine Properties window, select Memory, then increase the setting to a

12 Power on the appliance.
IMPORTANT: If you are planning to use a separate VMware hard disk to store your Filr files,
do not power on the appliance until you have created the hard disk, as described in Step 10.
26

drop-down.
Root password and confirmation: The root password for your Search Index appliance.
appliance.
255.255.255.0.
Gateway: The IP address of the gateway on the subnet where your Filr virtual appliance is
172.17.1.1.
of these settings, you can use the VACONFIG utility from the command prompt. For more
15 Click Next.
deployment scenarios. You should have already assigned a hard disk to the virtual machine
before you choose this option, as described in Step 10. If you have not already assigned a
hard disk, click Power Off Virtual Machine, modify the virtual machine settings to add a hard
disk, then power on the virtual machine.
Remote NFS: Do not select this option when installing the search index appliance. The
search index appliance is not supported with Remote NFS. If you plan to have multiple
Lucene index servers, understand that load balancing is not supported between index
servers. Rather, the purpose of having multiple Lucene index servers is to provide fault
tolerance or backup in the event that one index server fails.
17 Click Next.
18 (Conditional) If you selected Hard Disk in Step 16, specify the following options:
27
Filesystem type: Specify the type of file system. If you are sharing this file system between
multiple appliances (in a clustered environment), you must select ocfs2 as the file system type
when using a hard disk as the data storage location.
Remote Directory: Specify the path to the remote directory.
20 Click Configure.
The appliance might take a few minutes to install. When the installation is complete, you see a
message telling you that the appliance is now ready to configure.
21 (Optional) Create a cluster of Lucene index server appliances (no more than two is
recommended). Having multiple Lucene index server appliances provides fault tolerance or
backup in the event that one index server fails.
21a Install another Lucene index server appliance, as described in this section (Section 2.2.1,
Installing the Search Index Appliance, on page 25).

21b Log in to the Filr appliance administration and configure Lucene for High Availability, as
described in Section 4.5, Changing Your Search Index Configuration, on page 44.
22 Set a password for the search index appliance. You can also change other configuration options
for the search index appliance.

For information about how to change the search index appliance password and other
configuration options, see Chapter 5, Configuring and Maintaining the Search Index
Appliance, on page 55.
23 Continue with installing the database appliance, as described in Section 2.2.2, Installing the
MySQL Database Appliance, on page 28.
2.2.2
Installing the MySQL Database Appliance

If you already have a MySQL database server that you want the Filr appliance to use, you can skip
this section and continue with Chapter 3, Configuring Filr for the First Time, on page 33.
To install the MySQL database appliance:
1 Download the MySQL database software (MySQL.x86_64-version.ovf.zip) to your
management workstation.
2 Extract the MySQL.x86_64-version.ovf.zip file on your management workstation until the
MySQL-version file folder appears.
4 Browse to and select the .ovf file in the MySQL-version file folder.
5 Click Next.
6 Click Next again.
28

9 Click Finish.
10 Identify the location where you want to store your Filr files. This can be an NFS mount point or a
VMware hard disk.

If you choose to have a VMware hard disk, continue with Step 11. (Recommended)
If you choose to have an NFS mount point, continue with Step 12. You will make this
selection during the initial configuration of the appliance.
11 Create a separate VMware hard disk for the appliance.


11d Specify the amount of hard disk space that you want to allocate. Novell recommends a
minimum of 100 GB. But this might be more for your environment.
11e Leave Create a new virtual disk selected, then click Next.
11i Click Next.
11l Click Finish.
12 Increase the amount of memory that VMware allocates for the appliance.
The default is 4 GB. This default is appropriate for a system that has a few hundred to a
thousand users. Novell also recommends 2 CPUs.
12a In the Virtual Machine Properties window, select Memory, then increase this setting to a

13 Power on the appliance.
IMPORTANT: If you are planning to use a separate VMware hard disk to store your Filr files,
do not power on the appliance until you have created the hard disk, as described in Step 11.
29
drop-down.
Root password and confirmation: The root password for your database appliance.
appliance.
255.255.255.0.
Gateway: The IP address of the gateway on the subnet where your database appliance is
172.17.1.1.
of these settings, you can use the VACONFIG utility from the Filr command prompt. For more
16 Click Next.
deployment scenarios. You should have already assigned a hard disk to the virtual machine
before you choose this option, as described in Step 11. If you didnt, power off this virtual
machine, modify the virtual machine settings to add a hard disk, then power on the virtual
machine.
Remote NFS: Use a remote NFS location only in a large deployment scenario, where you
plan to configure all Filr servers (Filr, Filr Search, and MySQL) as separate virtual machines.
You must export the remote directory before you choose this option. Also, set the rw and
no_root_squash options on the remote directory.
18 Click Next.
19 (Conditional) If you selected Hard Disk in Step 17, specify the following options:

30

Filesystem type: Specify the type of file system.
NFS Server Hostname: Specify the hostname of the NFS server.

Remote Directory: Specify the path to the remote directory.
21 Click Configure.
The appliance might take a few minutes to install. When the installation is complete, you see a
message telling you that the appliance is now ready to configure.
22 Configure the MySQL database appliance to change the database administrator password, as
described in Chapter 6, Configuring and Maintaining the MySQL Database Appliance, on

page 57.
IMPORTANT: You must do this before you configure the Filr appliance for the first time.
23 Continue with Chapter 3, Configuring Filr for the First Time, on page 33.
31
32
Configuring Filr for the First Time
After you install the Novell Filr appliance and configure the network settings as described in Part 2,
Installing the Filr Appliance and Configuring the Operating System, on page 21, you are ready to
configure the Filr appliance for the first time. This configuration process uses a quick wizard that gets
your Filr system up and running. You can then make further configuration decisions, as described in
Chapter 4, Configuring and Maintaining the Filr Appliance, on page 37.
During initial configuration, you can configure Filr for a small or large organization. The
configuration you choose depends on the number of users that access the system. You should have
already chosen your type of deployment during installation. For more information, see Section 1.5,
Recommended Hardware Configurations Based on System Performance, on page 17.
In a small deployment, the Filr application, MySQL database, and search index all run within the
same virtual appliance. In a large deployment, the Filr application, MySQL database, and search
index run as separate virtual appliances.
Section 3.1, Small Deployment Configuration, on page 33
Section 3.2, Large Deployment Configuration, on page 35
3.1
Small Deployment Configuration

To configure the Filr appliance for a small organization:
1 After you have installed the Novell Filr appliance, as described in Section 2.1, Installing the Filr
Appliance, on page 21, navigate to the following URL:

https://ip_address:9443
Use the IP address or DNS name of the server that you specified during the appliance
installation.
2 Log in to the appliance using the vaadmin user and the password that you set.
The Novell Filr Appliance landing page is displayed.
33
3 Click the Filr Server Configuration icon.
The Filr Server Configuration Wizard is displayed.

4 Select Small Deployment, then click Next.
5 On the Database page, specify and confirm the password for the MySQL administrator.
If you need to change this password at a later time, you must use the native MySQL tools to do
so.
6 Click Next.
7 In the Default Locale field, select the default locale for your Filr site. This is the language and
locale that Filr uses when users first log in to the Filr site.
Users can change the individual locale after they log in by modifying the user profile, as
described in Modifying Your Profile in the Novell Filr 1.0 Web Application User Guide.
Some aspects of the Filr interface, such as group names and the login page, are always displayed
in the default language, regardless of individual user settings. For more information, see
Understanding the Filr Site Default Language in the Novell Filr 1.0 Administration Guide.
8 Click Finish.
After the configuration is complete, a summary is displayed.

This configuration summary contains information such as network, database, and so forth. You
can modify these configuration settings at any time from the Configuration column on the left
side of this page.
For information about each configuration option, see Chapter 4, Configuring and Maintaining
the Filr Appliance, on page 37.
9 Continue with Chapter 8, Setting Up the Filr Site, on page 69 to make your site ready for user
access.
34
3.2
Large Deployment Configuration

When you configure Filr for the first time for a large organization, you configure the Filr appliance to
point to the MySQL database appliance and the search index appliance that you previously installed
(see Section 2.2, Installing Separate Appliances for a Large Installation, on page 25 for installation
information).
IMPORTANT: Ensure that you have installed the search index appliance and the MySQL database
appliance before configuring the Filr appliance. The search index appliance and the MySQL database
appliance must be running when you configure the Filr appliance.
1 After you have installed the Novell Filr appliance, as described in Chapter 2, Installing the Filr
Appliance and Configuring the Operating System, on page 21, navigate to the following URL:
installation.
2 Log in to the appliance using the root user and the password that you set.
The Filr Server Configuration Wizard is displayed.

4 Select Large Deployment, then click Next.
5 Specify the following configuration options for the MySQL database:
Database Type: This is a MySQL database. No other database type can be used.
35
Host Name: The host name or IP address of the appliance where the MySQL database is
running.
Port: The port that is used to access the appliance where the MySQL database is running.
Database Name: The name of the MySQL database.
User Name: The administrative username used to access the MySQL database. The default
username is filr.
Password: The administrative password used to access the MySQL database. This is the
password that you set when configuring the MySQL appliance, as described in Chapter 6,
Configuring and Maintaining the MySQL Database Appliance, on page 57.
This is separate from the root password that you set for appliance access in Step 15 of
Section 2.2.2, Installing the MySQL Database Appliance, on page 28.
6 Click Next
7 Specify the following configuration options for the search index:
Host Name: The host name of the appliance where the search index is running. You must
specify the host name; the IP address cannot be used.
RMI Port: The port that is used to access the appliance where the Lucene search index server is
running.
Do not change this setting unless your network uses a different RMI port number.
Lucene User Name: The username for your Lucene search index. By default, the username is
lucene service. You can keep this name or change it to a name that you choose.
Lucene User Password: Specify a password for your Lucene search index. This can be any
password that you choose.
8 Click Next.
9 In the Default Locale field, select the default locale for your Filr site. This is the language and
locale that Filr uses when users first log in to the Filr site.
Users can change the individual locale after they log in by modifying the user profile, as
described in Modifying Your Profile in the Novell Filr 1.0 Web Application User Guide.
Some aspects of the Filr interface, such as group names and the login page, are always displayed
in the default language, regardless of individual user settings. For more information, see
Understanding the Filr Site Default Language in the Novell Filr 1.0 Administration Guide.
10 Click Finish.
After the configuration is complete, a summary is displayed.

This configuration summary contains information such as network, database, and so forth. You
can modify these configuration settings at any time from the Configuration column on the left
side of this page.
For information about each configuration option, see Chapter 4, Configuring and Maintaining
the Filr Appliance, on page 37.
11 Continue with Chapter 8, Setting Up the Filr Site, on page 69 to make your site ready for user
access.
36
Configuring and Maintaining the Filr

Appliance
Before you perform any of the procedures in this section, you must do the initial configuration of the
Filr appliance, as described in Chapter 3, Configuring Filr for the First Time, on page 33.
If you chose a small deployment, all vital configuration options to get the Filr system up and running
were chosen for you during the initial configuration. You can change those options as discussed in
this section.
If you chose a large deployment, most configuration options were chosen for you. You chose other
configuration options during the initial configuration. You can change those options as discussed in
this section. However, configuration options that are specific to the MySQL database appliance and
the search index appliance must be reconfigured as described in Chapter 5, Configuring and
Maintaining the Search Index Appliance, on page 55 and Chapter 6, Configuring and Maintaining
the MySQL Database Appliance, on page 57.
Section 4.1, Changing Configuration Options for the Filr Appliance, on page 37 in this chapter
describes how to modify configuration options for the Filr appliance. Other sections in this chapter
provide additional information for each configuration option.
Section 4.1, Changing Configuration Options for the Filr Appliance, on page 37
Section 4.2, Network Configuration, on page 39
Section 4.3, Database Configuration, on page 41
Section 4.4, Language, on page 43
Section 4.5, Changing Your Search Index Configuration, on page 44
Section 4.6, Changing Clustering Configuration Settings, on page 45
Section 4.7, Changing Reverse Proxy Configuration Settings, on page 46
Section 4.8, Changing Outbound Email Configuration Settings, on page 48
Section 4.9, Changing Configuration Settings for Requests and Connections, on page 51
Section 4.10, Changing the Java JDK Configuration Settings, on page 51
Section 4.11, Changing WebDAV Authentication Configuration Settings, on page 51
Section 4.12, Viewing and Updating the Filr License, on page 53
4.1
Changing Configuration Options for the Filr Appliance

1 Ensure that you have deployed the Novell Filr Appliance, as described in Chapter 3,
Configuring Filr for the First Time, on page 33.

2 Navigate to the following URL:
Replace ip_address with the IP address of your Filr appliance.
Configuring and Maintaining the Filr Appliance
37
3 Sign in to the Filr appliance using the root user and the default password that you specified
during the appliance installation.

The Configuration page is displayed.

5 In the Configuration column on the left side of the page, select the setting that you want to
configure.
The following configuration options are available. Click each option below for detailed
information.
Network
Database
Search Appliance
Clustering
Reverse Proxy
Outbound Email
Requests and Connections
Java JDK
WebDAV Authentication
License
6 Make any configuration changes, then click OK.
7 Click Reconfigure Filr Server for your changes to take effect.
38
NOTE: This stops and restarts your Filr server. Because this results in server downtime, you
should restart the server at off-peak hours.
4.2
Network Configuration
Section 4.2.1, Changing the Network Configuration Settings, on page 39
Section 4.2.2, Port Numbers, on page 40
4.2.1
Changing the Network Configuration Settings

The default port that is configured when you install the Filr appliance is 8443. After the initial
configuration of the Filr appliance (as described in Chapter 3, Configuring Filr for the First Time,
on page 33) you can make any necessary network changes.
To modify network configuration options:
1 Follow the steps in Section 4.1, Changing Configuration Options for the Filr Appliance, on
page 37.
You can modify the following configuration options:
Port Redirection: Select this option to have Filr automatically redirect from ports 80 or 443
(which are the standard ports for Web browsers) to ports 8080 and 8443 (which are the default
ports that Filr listens on). Enabling port redirection in this way allows users to specify the Filr
site URL without including the port number. If port redirection is not enabled, users must
include the port number in the site URL when accessing the Filr site.
IMPORTANT: When port redirection is enabled, ensure that the reverse proxy ports are set to
80 for the HTTP port and to 443 for the secure HTTP port. If they are not, URLs that are sent with
Filr email notifications will continue to have the default port (8443) in them.
For information about how to change the reverse proxy ports, see Section 4.7, Changing
Reverse Proxy Configuration Settings, on page 46.
HTTP Port: The default HTTP port is 8080. As a best practice, do not change this from the
default port.
Select Enabled if you want to enable the HTTP port. By default, only the Secure HTTP port is
enabled.
Select Force Secure Connection to force users to connect to Filr over a secure connection (HTTPS).
See Section 4.2.2, Port Numbers, on page 40 for more information about port numbers in Filr.
Secure HTTP Port: The default secure HTTP port for Filr is 8443. As a best practice, do not
change this from the default.
See Section 4.2.2, Port Numbers, on page 40 for more information about port numbers in Filr.
Session Timeout: By default, if a users Novell Filr session is idle for four hours (240 minutes),
Filr logs the idle user out. For increased convenience to Filr users, you can make the session
timeout interval longer. For increased security for your Filr site, you can make the session
timeout shorter.
Keystore File: Leave this field blank.
39
4.2.2
Port Numbers
Table 4-1 lists the ports that you need to take into consideration when setting up Filr. Figure 4-1 is a
graphical representation of how the ports are used in a Filr deployment.
As a best practice, do not change any port numbers from the default ports.
Table 4-1 Filr Port Numbers
Port Numbers
Description
80, 443
Standard Web server ports

For more information, see HTTP Port: on page 39,
Secure HTTP Port: on page 39 and HTTP/HTTPS
Ports When You Use NetIQ Access Manager with Filr
on page 41.
8080, 8443
Default Tomcat ports for the Filr appliance

When you install Filr, Tomcat is installed along with the
Filr software. Filr uses Tomcat as a stand-alone Web
server for delivering data to Filr users in their Web
browsers. For more information about Tomcat, see the
Apache Tomcat Web site (http://tomcat.apache.org).
For more information, see HTTP Port: on page 39,
Secure HTTP Port: on page 39 and HTTP/HTTPS
Ports When You Use NetIQ Access Manager with Filr
on page 41.
8005
Default shutdown port

For an explanation of the shutdown port, see Tomcat Shutdown Port (http://www.wellho.net/mouth/
837_Tomcat-Shutdown-port.html).
8009
Default AJP port

For an explanation of the Apache JServ Protocol port,
see The AJP Connector (http://tomcat.apache.org/
tomcat-6.0-doc/config/ajp.html).
40
22
SSH port for the appliance
9443
Jetty port for the appliance
1199
Lucene RMI registry port
1188
Lucene server port
3306
MySQL outbound port
25, 465
SMTP and SMTPS outbound ports
524/tcp
Access OES server over NCP
137/tcp, 137/udp, 138/udp, 139/tcp, 445/tcp
Access OES server over CIFS
11211
Used for memcached caching in an appliance cluster
636
Secure LDAP port
389
Non-secure LDAP port
Figure 4-1 Filr Port Usage
524
389/636
NetWare
136
137
138
139
445
389/636
OES
w
Windows
22
8443
9443
80
443
Personal Devices,
Workstations,
Browsers
25
(465/587)
Mail
L4 Switch
Filr
Protocol Key
REST
NCP
CIFS
System Protocols
22
3306
9443
MySQL
22
1188
1199
9443
Search
HTTP/HTTPS Ports When You Use NetIQ Access Manager with Filr
If you are fronting Filr with NetIQ Access Manager, ensure that you have configured the HTTP/
HTTPS ports.
Configuring Filr in this way configures NetIQ Access Manager to access Filr over port 80, which is
the standard port.
Port Configuration
Use the following port configuration when NetIQ Access Manager is fronting your Filr system on
Linux:
HTTP Port: 80
Secure HTTP Port: 443
You need to make these configuration settings in the Reverse Proxy section. For more information, see
Section 4.7, Changing Reverse Proxy Configuration Settings, on page 46.
4.3
Database Configuration
Section 4.3.1, Understanding Database Configuration, on page 42
Section 4.3.2, Changing Database Configuration Settings, on page 42
Section 4.3.3, Database Type, on page 42
Section 4.3.4, Database Location, on page 43
Section 4.3.5, Database Credentials, on page 43
41
4.3.1
Understanding Database Configuration

Novell Filr database disk space requirements are relatively modest. Files that are imported into Filr
are saved in the Filr file repository.
The Filr database is primarily used for storing the following information:
Structural information about folders and files
Identification information about folders and files (for example, titles, descriptions, dates of
creation/modification, and users associated with creation/modification)
User profile information (for example, full name, phone number, and email address)
4.3.2
Changing Database Configuration Settings

Changing the Database Configuration Settings for a Small Installation on page 42
Changing the Database Configuration Settings for a Large Installation on page 42
Changing the Database Configuration Settings for a Small Installation

page 37.
Database Type: Filr uses a MySQL database. You cannot use another type of database.
Host Name or IP Address: Host name or IP address of the MySQL appliance if MySQL is not
running on the Filr appliance.
Port: The JDBC URL also includes the port number on which Filr can communicate with the
database server. The default port number for MySQL is 3306. Use this port number unless it is
already in use by another process on the database server.
Username: The username for your MySQL database. For more information, see Section 4.3.5,
Database Credentials, on page 43.
Password: The password for your MySQL database. For more information, see Section 4.3.5,
Database Credentials, on page 43.
Changing the Database Configuration Settings for a Large Installation

If your Filr site is configured for a large installation (your MySQL database is a stand-alone
appliance), you modify the configuration settings as described in Chapter 6, Configuring and
Maintaining the MySQL Database Appliance, on page 57.
4.3.3
Database Type
Filr uses a MySQL database. This is the only supported database for Filr 1.0.
42
4.3.4
Database Location
When you install a single virtual appliance for a small installation, all components are on the same
appliance. This is the preferable location for a small installation. The default database name is filr.
4.3.5
Database Server
Default Location
MySQL
/vastorage/mysql
Database Credentials
The MySQL database defaults to root for the administrative username.
IMPORTANT: The MySQL root username is not the same as the Linux root user on a Linux
appliance.
4.4
Language
The Novell Filr installation program runs in English only. When you install the Filr software, you can
choose to have the primary language of the Filr site to be any of the following languages:
Chinese-Simplified
Chinese Traditional
Czech
Danish
Dutch
English
French
German
Hungarian
Italian
Japanese
Polish
Portuguese
Russian
Spanish
Swedish
Some languages have an additional distinction by locale (the country where the language is spoken).
The language you select during installation establishes the language of the global text that displays in
locations where all Filr users see it, such as in the Workspace tree when you click the Workspace tree
icon :
43
The language you select also establishes the default interface language and locale for creating new
user profiles.
4.5
Changing Your Search Index Configuration

Section 4.5.1, Understanding Indexing, on page 44
Section 4.5.2, Changing Search Index Configuration Settings, on page 44
Section 4.5.3, Running the Search Index As Its Own Appliance, on page 45
Section 4.5.4, Running Multiple Search Indexes, on page 45
4.5.1
Understanding Indexing
The search index is responsible for indexing all data on the Filr site so that Filr users can easily use
the Search feature to retrieve the information that they need. Text posted in file metadata (such as a
file description) is easy to index, because the formatting is simple. However, text within a file itself
arrives in many different file formats, many of which require conversion before the text in the files
can be indexed. Therefore, the search index is dependent on the available file conversion technology
in order to perform its indexing function. For information about the file viewers that Filr uses, see
Section 1.2.5, File Viewer Information, on page 15.
The search index provides additional services on your Filr site in addition to indexing. In fact, you
cannot access your Filr site if the search index is not running. For this reason, Novell Filr provides
multi-server configuration options.
4.5.2
Changing Search Index Configuration Settings

page 37.
Configuration Type: For a small installation, the default is Local.
For a large installation with only one separate Lucene index server appliance, the default is
Server.
For a large installation with multiple Lucene index server appliances, you must change the
configuration type from the default of Server to High Availability, then click Add to add the
information for each Lucene index appliance.
1. Change the configuration type from the default of Server to High Availability.
2. Click Add, specify the information for the first Lucene index appliance, then click OK.
3. Click Add, specify the information for the second Lucene index appliance, then click
OK.
Description: (This option is visible only when Configuration Type is set to High Availability.)
Specify a short description for the Lucene appliance.
44
Host Name or IP Address: This is localhost if your Configuration Type is Local. If your
Configuration Type is Server or High Availability, use this field to specify the host name or IP
address of the appliance where the search indexes are running. (If your Configuration Type is
High Availability, click Add to configure multiple search indexes.)
RMI Port: When the search index is running as its own appliance, it communicates with
Filr by using the RMI (Remote Method Invocation (http://java.sun.com/javase/technologies/
core/basic/rmi/index.jsp)) port. (Default 1199). In a clustered environment where you are
running multiple search index servers, ensure that the each Lucene index server is running
on the same ports.
Lucene User Name: (This option is visible only when Configuration Type is set to Server or
High Availability.) The name of the Lucene user.
Lucene User Password: (This option is visible only when Configuration Type is set to Server
or High Availability.) The password for the Lucene user.
2 Click OK.
If your Filr site is configured for a large installation (your search index is a stand-alone appliance),
you can make additional configuration settings for your Lucene search index appliance as described
in Chapter 5, Configuring and Maintaining the Search Index Appliance, on page 55.
4.5.3
Running the Search Index As Its Own Appliance

If the search index requires more memory, disk space, or CPU resources than are available on the
Novell Filr appliance, you can move it to a remote appliance. For instructions, see Section 2.2,
Installing Separate Appliances for a Large Installation, on page 25.
4.5.4
Running Multiple Search Indexes

Because the availability of the index is critical to the functioning of the Novell Filr site, you can install
multiple search indexes as multiple appliances to provide high availability. For instructions, see
Section 2.2.1, Installing the Search Index Appliance, on page 25.
4.6
Changing Clustering Configuration Settings

page 37.
Enable Clustered Environment: Select this option to enable clustering.
Host: This represents the reverse proxy or L4 device that fronts the Filr Virtual Appliance.
This is the host name that is used to build the URL which the browser will use to access the filr
clustered system.
It is common across all the Filr Virtual Appliances.
JVM Route: If you plan to use Apache as the reverse proxy, add a JVM route for each filr
Appliance in the Cluster. Otherwise, you can leave the JVM Route field empty. The purpose of
this field is to uniquely identify each Filr Appliance to Apache.
45
In the JVM Route field, specify worker1. On the second Filr node, in the JVM Route field, specify
worker2, and so forth for each Filr node, incrementing the JVM Route setting. Each Tomcat
instance should have a unique JVM Route setting.
worker1, worker2, and so forth are the default names for the matching values used for the
reverse proxy configuration. For example, if you have set up Apache or IIS as a reverse proxy,
these are the default values. The JVM Route setting in the Filr installer must match these values.
Hibernate Caching Provider: memcache is the only option available when configuring Filr in a
clustered environment.
For more information about Memcache caching, see Memcached (http://memcached.org/).
Server Addresses: Each Filr server in the cluster must list all of the Filr servers in the cluster,
with each server separated by a space. The default port for memcached is 11211. For example,
ipaddress1:11211 ipaddress2:11211 ipaddress3:11211
The server addresses listed here are all nodes within the Filr cluster. Changes made to one Filr
node are immediately visible in other Filr nodes. Ensure that all Filr appliances in the cluster are
pointing to the same NTP time source. Failure to do so can significantly degrade overall system
performance.
NOTE: This stops and restarts your Filr server. As this results in server downtime, you should
restart the server at off-peak hours.
4.7
Changing Reverse Proxy Configuration Settings

Section 4.7.1, Understanding Reverse Proxy and NetIQ Access Manager, on page 46
Section 4.7.2, Understanding How Port Redirection Affects Reverse Proxy Settings, on page 47
Section 4.7.3, Changing Reverse Proxy Configuration Settings, on page 47
You might need to modify the reverse proxy configuration settings for your Filr appliance for either
of the following reasons:
When you configure a reverse proxy server, such as NetIQ Access Manager
For more information about this scenario, see Section 4.7.1, Understanding Reverse Proxy and
NetIQ Access Manager, on page 46.
If you have enabled port redirection in your network settings page (as described in Section 4.2.1,
Changing the Network Configuration Settings, on page 39)
For more information about this scenario, see Section 4.7.2, Understanding How Port
Redirection Affects Reverse Proxy Settings, on page 47.
4.7.1
Understanding Reverse Proxy and NetIQ Access Manager

NetIQ Access Manager provides secure single sign-on access to your Novell Filr site by functioning
as a reverse proxy server. Access Manager 3.1 SP1 IR1 is required for use with Novell Filr. You can
download the required version of Access Manager from Novell Downloads (http://
download.novell.com).
For background information about setting up NetIQ Access Manager 3.1, see the Access Manager 3.1
Documentation Web site (http://www.novell.com/documentation/novellaccessmanager31). For
instructions specific to Filr, see Configuring a Protected Resource for a Novell Filr Server in the
Novell Filr 1.0 Administration Guide.
46
After you have configured NetIQ Access Manager, you must configure your Filr site with the IP
address of one or more Access Gateway servers and with the logout URL. When you configure the
Filr site to use the Access Gateway, the IP addresses that you specify are the only locations from
which the Filr site accepts logins. The logout URL is the location where users find themselves when
they log out of the Filr site.
When you enable the Access Gateway for use with your Filr site, all Filr users must log in through the
Access Gateway. It is not possible to set up the Filr site so that some users log in through the Access
Gateway and some do not.
4.7.2
Understanding How Port Redirection Affects Reverse Proxy Settings

If you have enabled port redirection in your network settings page (as described in Section 4.2.1,
Changing the Network Configuration Settings, on page 39), you need to verify that the reverse
proxy ports match what the Filr server expects. The reverse proxy HTTP port should be set to 80, and
the reverse proxy secure HTTP port should be set to 443. If the reverse proxy ports are not correct,
links that are sent from Filr in email notifications are incorrect, and users are not able to access Filr.
This issue is described in Email Notification URLs Are Not Working in Troubleshooting the Filr
System in the Novell Filr 1.0 Administration Guide.
4.7.3
Changing Reverse Proxy Configuration Settings

page 37.
Host: The host name is used to build some of the URLs that are sent in notifications. It should
reflect the host used to access the Filr system from any user (either an internal or external user).
If Access Manager is being used to front Filr, specify the NAM published DNS name for Filr
application in the Host field.
Reverse Proxy HTTP Port: Select Enabled if you want to use a non-secure port for the reverse
proxy. Specify the port number that you want to use. You must use port 80 if you have enabled
port redirection in your network settings page.
Reverse Proxy Secure HTTP Port: Specify the port number that you want to use for the secure
reverse proxy HTTP port. You must use port 443 if you have enabled port redirection in your
network settings page. (Port redirection allows users to access the Filr site without specifying the
port number in the URL. For information about port redirection, see Section 4.2, Network
Configuration, on page 39.)
Enable Access Gateway: Select this option to enable the reverse proxy Access Gateway.
Access Gateway address(es): Specify the IP address of the Access Gateway that is used for the
connection to the Filr server. You must specify the IP address; host names are not supported.
If the Access Gateway is part of a cluster, add the IP address for each cluster member. Wildcards
such as 164.99.*.* are allowed.
When you specify specific IP addresses in this option, Filr logins are allowed only from the
specified addresses. Also, if Authorization header credentials are not present or are incorrect,
the user is prompted for login using Basic Authentication.
Logout URL: Specify the URL of the published DNS name of the reverse proxy that you have
specified for the ESP, plus /AGLogout.
You can find the domain used for the ESP by editing the LAG/MAG cluster configuration, then
clicking Reverse Proxy / Authentication.
47
For example, if the published DNS name of the proxy service that you have specified for the ESP
is esp.yoursite.com, specify the following URL:
https://esp.yoursite.com/AGLogout
2 Click OK, then click Reconfigure Filr Server for your changes to take effect.
4.8
Changing Outbound Email Configuration Settings

Section 4.8.1, Understanding Outbound Email, on page 48
Section 4.8.2, Changing Outbound Email Configuration Settings, on page 48
Section 4.8.3, Outbound Email Protocol, on page 49
Section 4.8.4, Outbound Email Host, on page 49
Section 4.8.5, Outbound Email Authentication, on page 50
4.8.1
Understanding Outbound Email

Your Novell Filr site can be configured to send outbound email through an existing email system.
Email from the Filr site is useful for the following activities:
Filr users can subscribe to email notifications, so that they automatically receive a message
whenever content of interest changes. For more information, see Subscribing to a Folder or
File in Getting Informed in the Novell Filr 1.0 Web Application User Guide.
Filr users can configure folders that they own to send email notifications to other users. For more
information, see Configuring Folders to Send Email Notifications to Other Users in the Novell
Filr 1.0 Web Application User Guide.
After installation, outbound email can be disabled and enabled again on the Filr site, as described in
Configuring Email Integration in Site Setup in the Novell Filr 1.0 Administration Guide. However,
you must configure outbound email in the Filr appliance.
4.8.2
Changing Outbound Email Configuration Settings

page 37.
Use Local Postfix Mail Server: Select this option to use the Postfix mail server, which is the
default mail system included with Filr. To use another mail system (such as GroupWise),
deselect this option, then specify the appropriate information for the protocol, host, and port of
the mail system that you want to use.
Protocol: Select the type of protocol your email system uses. For more information, see
Section 4.8.3, Outbound Email Protocol, on page 49.
Host: Specify the hostname of your SMTP mail server. For more information, see Section 4.8.4,
Outbound Email Host, on page 49.
Port: The port through which Filr can connect to the SMTP mail server. The default SMTP port of
25 is typically appropriate, unless the SMTP mail server requires port 465 or 587 for SMTPS
connections.
48
Time Zone: Select the time zone that you want Filr to use when sending email messages. When
the Filr site sends email notifications for scheduled events, the messages are time-stamped
according to the time zone you specify here during installation. This setting allows you to use a
time zone for email notifications that is different from the time zone where the server is located.
For more information, see Section 4.8.4, Outbound Email Host, on page 49.
Username: Specify an email address to be used when sending outbound email. Many SMTP
mail hosts require a valid email address before they establish the SMTP connection. For more
information, see Section 4.8.5, Outbound Email Authentication, on page 50.
Password: Specify a password for the username. Some email systems also require a password.
Some do not. If authentication is required, you should also provide a password. For more
information, see Section 4.8.5, Outbound Email Authentication, on page 50.
Authentication required: Select this option to require authentication.
Allow sending email to all users: Deselect this option to prevent users from sending email to
the All Users group.
By default, the Filr site allows Filr users to send messages to all Filr users by using the All Users
group on the Filr site. On a very large Filr site, this generates a very large number of email
messages. If desired, you can prevent messages from being sent to the All Users group.
Connection Timeout (in seconds): Specify the amount of time before the connection times out.
NOTE: This stops and restarts your Filr server. As this results in server downtime, you should
restart the server at off-peak hours.
4.8.3
Outbound Email Protocol

Email systems communicate by using SMTP (Simple Mail Transfer Protocol). You need to determine
whether the email system that you want your Filr site to communicate with is using SMTP or SMTPS
(secure SMTP).
For GroupWise, you can check how the Internet Agent is configured:
1 In ConsoleOne, browse to and right-click the Internet Agent object, then click Properties.
2 Click GroupWise > Network Address.
In the SMTP field, if the SSL column displays Disabled, GroupWise is using SMTP. If the SSL
column displays Enabled, GroupWise is using SMTPS.
3 Click Cancel to close the Network Address page.
If the email system requires SMTPS, see Securing Email Transfer in Site Security in the Novell Filr
1.0 Administration Guide.
4.8.4
Outbound Email Host

In order to send messages to your email system, Filr needs to know the host name of your SMTP mail
server.
The default SMTP port of 25 is typically appropriate, unless the SMTP mail server requires port 465
or 587 for SMTPS connections.
If you are using GroupWise, this is the host name of a server where the Internet Agent is running.
GroupWise always uses port 25, even when SSL is enabled.
49
When the Filr site sends email notifications for scheduled events, the messages are time-stamped
according to the time zone you specify here during installation. This setting allows you to use a time
zone for email notifications that is different from the time zone where the server is located. The time
zone list is grouped first by continent or region, optionally by country or state, and lastly by city.
Some common selections for United States time zones are:
4.8.5
Time Zone
Continent/City
Pacific Time
America/Los Angeles
Mountain Time
America/Denver
Central Time
America/Chicago
Eastern Time
America/New York
Outbound Email Authentication

Many SMTP mail hosts require a valid email address before they establish the SMTP connection.
Some email systems can construct a valid email address if you specify only a valid username; other
email systems require that you specify the full email address for successful authentication. You
should provide a username (email address) to ensure a successful connection. Email notifications
from the Filr system are sent using this email address in the From field.
Some email systems also require a password. If authentication is required, you should also provide a
password.
Consider the following tips when using GroupWise or Exchange:
GroupWise on page 50
Exchange on page 50
GroupWise
If you are using Novell GroupWise, the GroupWise Internet Agent does not require authentication in
order to receive inbound messages. However, the /forceinboundauth startup switch is available for
use in the Internet Agent startup file (gwia.cfg) to configure the Internet Agent to refuse SMTP
connections where a valid email username and password are not provided. The Internet Agent can
accept just the username or the full email address.
Exchange
If you are using Microsoft Exchange and you set up the outbound email server to require
authentication (by selecting the option Authentication Required), Exchange must be configured to
allow the From address to be different from the user who is configured for Exchange authentication.
The Exchange permission that you need to add is ms-Exch-SMTP-Accept-Any-Sender.
This is required because Exchange, by default, enforces that the From address of outbound emails
match the exchange user who you configured for authentication, and many emails that are sent from
Filr use the From address of the Filr user who is performing an action.
50
4.9
Changing Configuration Settings for Requests and

Connections
You can configure the number of client requests and database connections that Filr is able to support.
If you have an extremely large Filr site and you need to make numerous client requests and database
connections, you might see improved performance by increasing these settings.
page 37.
Max Threads: The maximum number of simultaneous client request threads that Filr is able to
support. The default is 200 threads.
Max Active: The maximum number of database connections that can be allocated from this pool
at the same time.
Max Idle: The maximum number of database connections that can be idle in this pool at the
same time. The default is 20 connections.
4.10
Changing the Java JDK Configuration Settings

page 37.
Java Home: Displays the path to the JavaHome variable. This cannot be changed.
JVM Heap Size: The default JVM heap size is 2 GB. You can increase or decrease this value as
needed.
The JVM heap size must end with g or m, and it cannot contain fractional values. For example, if
you want your JVM heap size to be 1.5 GB, you must specify 1536m.
4.11
Changing WebDAV Authentication Configuration Settings

Section 4.11.1, Understanding WebDAV, on page 52
Section 4.11.2, Changing the WebDAV Authentication Configuration Settings, on page 52
Section 4.11.3, Choosing the WebDAV Authentication Method, on page 52
51
4.11.1
Understanding WebDAV
WebDAV is a standard collaborative editing and file management protocol. Novell Filr relies on the
WebDAV protocol for Edit-in-Place to use tools such as OpenOffice and Microsoft Office to edit
documents on the Filr site.
IMPORTANT: When Filr users are running Windows 7 as the client operating system, various issues
can be introduced because of WebDAV limitations in Windows 7. If your Filr users are using the
Windows 7 operating system, see Configuring Filr to Support WebDAV on Windows 7 in the
Novell Filr 1.0 Administration Guide.
4.11.2
Changing the WebDAV Authentication Configuration Settings

page 37.
WebDAV authentication method: Select either Basic or Digest. The WebDAV authentication
method determines how user credentials are passed from Filr to the WebDAV server. For more
information, see Section 4.11.3, Choosing the WebDAV Authentication Method, on page 52.
4.11.3
Choosing the WebDAV Authentication Method

The WebDAV authentication method determines how user credentials are passed from Filr to the
WebDAV server. Filr supports two types of WebDAV authentication methods:
Choosing Basic Authentication on page 52
Choosing Digest Authentication on page 52
Choosing Basic Authentication

Basic authentication encodes the username and password with the Base64 algorithm. The Base64encoded string is unsafe if transmitted over HTTP, and therefore should be combined with SSL/TLC
(HTTPS).
Digest authentication is the default. Do not select Basic authentication unless there is a specific reason
for doing so.
Choosing Digest Authentication

Digest authentication applies MD5 cryptographic, one-way hashing with nonce values to a password
before sending it over the network. This option is safer than Basic authentication when used over
HTTP.
Select this type of authentication when client users are using Windows 7 as their operating system
and Microsoft Office as their text editor.
52
4.12
Viewing and Updating the Filr License

You can view information about your current Filr license, as well as update your Filr license.
Filr ships with a 90-day evaluation license. You need to update this license to a full product license.
IMPORTANT: If you are running Filr in a clustered environment, you must update the license for
each Filr appliance in the cluster.
The database and search index appliances do not require a license.
page 37.
On the License page, the Current License Information section displays information about your
current Filr license, including the date it was issued and the number of days from the issue date
that the license is valid.
2 To update your Filr license:
2a In the Update License section, browse to and select a new valid license-key.xml file that
you have previously downloaded to your workstation.

You can obtain a new valid license key from the Novell Customer Center (NCC) (http://
www.novell.com/customercenter/).
2b Reconfigure the Filr server by clicking the Reconfigure Filr Server button that appears in the
Configuration column.
53
54
Configuring and Maintaining the Search

Index Appliance
This section describes how to change additional configuration options for the search index appliance
for a large deployment. If your search index is configured on the same appliance as your Filr
application, you make configuration changes on the Filr appliance, as described in Chapter 4,
Configuring and Maintaining the Filr Appliance, on page 37.
1 After installing the search index appliance, as described in Section 2.2.1, Installing the Search
Index Appliance, on page 25, navigate to the following URL:

Replace ip_address with the IP address of your Filr appliance.

2 Sign in to the Filr appliance. The default username is root, and the default password is the
password that you specified during installation.

The Novell Filr Search Appliance landing page is displayed.
3 Click the Filr Search Configuration icon.
The Filr Search Configuration Wizard is displayed.
Configuring and Maintaining the Search Index Appliance
55
4 (Conditional) If this is the first time you have accessed the Filr search appliance, you must:
4a Select New or Upgrade, depending on whether this is a new installation or an upgrade from
a previous installation.
4b Specify a password for the default Lucene service user, then click Finish.
IMPORTANT: In a clustered environment where you are running multiple search index
servers, ensure that the password is the same for each search index server.
The password for the Lucene service user is now set.
The Search Settings page is displayed.
5 On the Search Settings page, refer to the on-screen instructions for information about the fields
that you can modify.

6 Click Submit after you have made the desired modifications for your search settings.
7 (Conditional) If this is the first time you have configured the Search Index appliance:
7a Ensure that you have configured the MySQL database appliance, as described in Chapter 6,
Configuring and Maintaining the MySQL Database Appliance, on page 57.

7b Configure the Filr appliance, as described in Chapter 3, Configuring Filr for the First
Time, on page 33.

The MySQL database appliance and the Search Index appliance must already be installed
and configured before you can configure the Filr appliance for the first time.
56
Configuring and Maintaining the MySQL

Database Appliance
This section describes how to change configuration options for the MySQL database appliance for a
large deployment, including how to change the credentials for the MySQL database.
If you already have a MySQL database server that you want the Filr appliance to use, you can use it
and skip this section.
IMPORTANT: In a production environment, it is a best practice to change the credentials for the
MySQL database when the MySQL database is running as a separate appliance. If you do not change
the credentials, you at least need to change the root password for the MySQL database.
If your MySQL database is configured on the same appliance as your Filr application, you make
configuration changes on the Filr appliance, as described in Chapter 4, Configuring and
Maintaining the Filr Appliance, on page 37.
1 After installing the database appliance, as described in Section 2.2.2, Installing the MySQL
Database Appliance, on page 28, navigate to the following URL:

Replace ip_address with the IP address of your database appliance.

2 Sign in to the database appliance. The default username is root, and the default password is the
password that you specified during installation.

The Novell MySQL Appliance landing page is displayed.
3 Click the phpMyAdmin icon, then click Go to log in to phpMyAdmin.
Configuring and Maintaining the MySQL Database Appliance
57
4 Log in to the phpMyAdmin tool as the root user. (The default password for the root user is
root. You will be instructed to change the default password in a future step.)
5 (Recommended) Create a new Filr user to administer the MySQL database:
5a At the top of the page, click Users.
5b Click Add user.
5c In the User name field, specify filr as the new user.
5d In the Host field, select Use text field in the drop-down list, then specify the IP address or
host name of the Filr application server.

5e In the Password field, specify a new password for the user, then confirm it in the Re-type
field.
5f In the Database for user section, select Create database with same name and grant all privileges.
5g Click Add user. Note the username and password of this user. This is the user you will use to
access the MySQL database when you configure the Filr appliance.
You can now administer the Filr MySQL database by using this new user.
6 (Recommended) Change your MySQL root password if you have not done so already:
6a At the top of the page, click Users.
6b In the Users Overview table, locate the root user with % in the Host column, then click Edit
Privileges for that user in the Action column.
58
6c Scroll to the Change password section. In the Password field, specify your password, then
confirm it in the Re-type field.

6d Click Go.
7 Make any other configuration changes.
8 (Conditional) If this is the first time you have configured the MySQL database appliance:
8a Ensure that you have configured the search index appliance, as described in Chapter 5,

8b Configure the Filr appliance, as described in Chapter 3, Configuring Filr for the First
Time, on page 33.

The MySQL database appliance and the Search Index appliance must already be installed
and configured before you can configure the Filr appliance for the first time.
Configuring and Maintaining the MySQL Database Appliance
59
60
Configuring and Maintaining the Novell

Appliance
The Novell Appliance is the operating system that the Filr application runs on. You might need to
change certain configuration settings for the Novell Appliance, such as administrative passwords to
the appliance, network settings, and certificate settings.
Section 7.1, Changing Administrative Passwords, on page 61
Section 7.2, Changing Network Settings, on page 61
Section 7.3, Changing Time Configuration, on page 62
Section 7.4, Replacing the Self-Signed Digital Certificate for an Official Certificate, on page 62
Section 7.5, Changing the Ganglia Configuration, on page 64
Section 7.6, Changing System Services Configuration (SSH, Filr, Jetty, Postfix, and FAMT), on
page 65
Section 7.7, Viewing the Firewall Configuration, on page 66
Section 7.8, Shutting Down and Restarting the Novell Appliance, on page 66
7.1
Changing Administrative Passwords

1 Log in to the Novell appliance at https://server_url:9443, then click the Appliance Configuration
icon.
2 Click Administrative Passwords.

3 Specify new passwords for the root and vaadmin administrators.
If you are changing the root password, you must first specify the current root password.
4 Click Save.
7.2
Changing Network Settings

icon.
Configuring and Maintaining the Novell Appliance
61
2 Click Network.
3 As necessary, change the IP and DNS configuration settings for your Novell appliance.
4 Click Save.
7.3
Changing Time Configuration

icon.
2 Click Time.
3 As necessary, change the following time configuration options:
NTP Server: Specify the NTP server that you want to use for time synchronization.
Region: Select the region where your Novell Appliance is located.
Time Zone: Select the time zone where your Novell Appliance is located.
4 Click Save.
7.4
Replacing the Self-Signed Digital Certificate for an Official

Certificate
The Novell Appliance ships with a self-signed digital certificate. Instead of using this self-signed
certificate, you should use a trusted server certificate that is signed by a trusted certificate authority
(CA) such as VeriSign or Equifax.
The certificate works for both the Novell Appliance and the Filr software (ports 9443 and 8443). You
do not need to update your certificate when you update the Filr software.
Complete the following sections to change the digital certificate for your Novell Appliance. You can
use the digital certificate tool to create your own certificate and then have it signed by a CA, or you
can use an existing certificate and key pair if you have one that you want to use.
Section 7.4.1, Using the Digital Certificate Tool, on page 63
Section 7.4.2, Using an Existing Certificate and Key Pair, on page 64
Section 7.4.3, Activating the Certificate, on page 64
62
7.4.1
Using the Digital Certificate Tool

Creating a New Self-Signed Certificate on page 63
Getting Your Certificate Officially Signed on page 63
Creating a New Self-Signed Certificate

icon.
2 Click Digital Certificates.

3 In the Key Store drop-down list, ensure that Web Application Certificates is selected.
4 Click File > New Certificate (Key Pair), then specify the following information:
Alias: Specify a name that you want to use to identify and manage this certificate.
Validity (days): Specify how long you want the certificate to remain valid.
Key Algorithm: Select either RSA or DSA.
Key Size: Select the desired key size.
Signature Algorithm: Select the desired signature algorithm.
Common Name (CN): This must match the server name in the URL in order for browsers to
accept the certificate for SSL communication.
Organizational Unit (OU): (Optional) Small organization name, such as a department or
division. For example, Purchasing.
Organization (O): (Optional) Large organization name. For example, Novell, Inc.
City or Lacality (L): (Optional) City name. For example, Provo.
State or Province (ST): (Optional) State or province name. For example, Utah.
Two-letter Country Code (C): (Optional) Two-letter country code. For example, US
5 Click OK to create the certificate.
After the certificate is created, it is self-signed.

6 Make the certificate official, as described in Getting Your Certificate Officially Signed on
page 63.
Getting Your Certificate Officially Signed

1 On the Digital Certificates page, select the certificate that you just created, then click File >
Certificate Requests > Generate CSR.

2 Complete the process of emailing your digital certificate to a certificate authority (CA), such as
Verisign.
The CA takes your Certificate Signing Request (CSR) and generates an official certificate based
on the information in the CSR. The CA then mails the new certificate and certificate chain back
to you.
63
3 After you have received the official certificate and certificate chain from the CA:
3a Revisit the Digital Certificates page by clicking Digital Certificates from the Novell
Appliance.
3b Click File > Import > Trusted Certificate. Browse to the trusted certificate chain that you
received from the CA, then click OK.

3c Select the self-signed certificate, then click File > Certification Request > Import CA Reply.
3d Browse to and upload the official certificate to be used to update the certificate information.
On the Digital Certificates page, the name in the Issuer column for your certificate changes
to the name of the CA that stamped your certificate.
4 Activate the certificate, as described in Section 7.4.3, Activating the Certificate, on page 64.
7.4.2
Using an Existing Certificate and Key Pair

When you use an existing certificate and key pair, use a .P12 key pair format.
1 Go to the Digital Certificates page by clicking Digital Certificates from the Novell Appliance.
2 Click File > Import > Trusted Certificate. Browse to and select your existing certificate, then click
OK.
3 Click File > Import > Trusted Certificate. Browse to your existing certificate chain for the certificate
that you selected in Step 2, then click OK.

4 Click File > Import > Key Pair, then browse to and select your .P12 key pair file, specify your
password if needed, then click OK.

5 Continue with Section 7.4.3, Activating the Certificate, on page 64.
7.4.3
Activating the Certificate

1 On the Digital Certificates page, select the certificate that you want to make active, then click Set
as Active, then click Yes.

2 Verify that the certificate and the certificate chain were created correctly by selecting the
certificate, then clicking View Info.
7.5
Changing the Ganglia Configuration

Ganglia is a scalable, distributed monitoring system that allows you to gather important information
about your Filr system.
icon.
2 Click Ganglia Configuration.

3 As necessary, change the following Ganglia configuration options:
64
Enable the Web interface to run on this machine: Select this option to allow the Ganglia Web
Interface to run on the same machine as the Filr appliance.
If you already have a monitoring system that you plan to use for Filr, you can disable Ganglia
monitoring by deselecting this option and the following option.
Enable Ganglia Monitoring: Select this option to enable Ganglia to monitor the Novell
Appliance.
Multicast Mode: Select this option to send monitoring information to multiple destinations.
Unicast Mode: Select this option to send monitoring information to a single destination.
Publish to: Specify the URL where Ganglia sends monitoring information when it is running in
Unicast mode.
NOTE: You must use the IP address rather than the DNS name when specifying the URL in the
Publish to field.
4 Click Save.
For more information about how to use Ganglia monitoring with Filr, see Monitoring Filr
Performance with Ganglia in the Novell Filr 1.0 Administration Guide.
7.6
Changing System Services Configuration (SSH, Filr, Jetty,

Postfix, and FAMT)
System services include: SSH, Novell Filr, Jetty, Postfix, and Novell FAMT. This section describes the
kinds of actions you can perform in regards to these services.
icon.
2 Click System Services.

3 You can perform various actions for system services.
Section 7.6.1, Starting, Stopping, or Restarting System Services, on page 65

Section 7.6.2, Making System Services Automatic or Manual, on page 66
Section 7.6.3, Downloading Log Files for System Services, on page 66
7.6.1
Starting, Stopping, or Restarting System Services

You might want to start, stop, or restart a service. For example, you can start SSH so that you can
remote into the appliance without using a VMware client.
1 Select the service that you want to start, stop, or restart.
2 Click Action, then click Start, Stop, or Restart.
3 Click Close to exit System Services.
65
7.6.2
Making System Services Automatic or Manual

1 Select the service that you want to make automatic or manual.
2 Click Action, then click Set as Automatic, or Set as Manual.
7.6.3
Downloading Log Files for System Services

1 In the Log Files column of the table, click the download link for the service for which you want to
view log files.

The following files are available for each service:
SSH: N/A
Novell Filr: catalina.out (Filr appliance)
The catalina.out file reports all timestamps in UTC/GMT.
Jetty: jetty.stderrout.log (Filr, Search, and MySQL database appliances)
Postfix: mail (Filr appliance)
Novell FAMT: famtd.log (Filr appliance)
Search: indexserver.out (Search appliance)
MySQL: mysqld.log (MySQL database appliance)
7.7
Viewing the Firewall Configuration

You can view your current firewall configuration directly from the Filr appliance:
icon.
2 Click Firewall.
Port numbers are listed with the current status of each port number. This page is not editable,
but is for informational purposes.
For more information about port numbers in Filr, see Section 4.2.2, Port Numbers, on page 40.
7.8
Shutting Down and Restarting the Novell Appliance

You might need to shut down or restart the Novell appliance for maintenance.
icon.
66
2 Click Reboot or Shutdown.
67
68
Setting Up the Filr Site
After you have installed and started Novell Filr, there are administrative tasks to perform before your
Filr site is ready for users to log in and start using Filr efficiently. Filr ships with most settings
disabled by default, so you as the Filr administrator must enable each piece of functionality. This
ensures that your data is not unknowingly exposed to users who do not normally have access to
certain information. For example, users cannot share files until you give them the ability to do so.
Refer to the following sections of the Novell Filr 1.0 Administration Guide as you finish setting up your
Filr site.
Setting Up User Access to the Filr Site (Specifically, see Synchronizing Users and Groups
from an LDAP Directory or Creating a New Local User)
Configuring Email Integration
Setting Up Sharing
Setting Up Personal Storage
Setting Up Net Folders
Allowing Access to the Filr Site through Novell Access Manager
Configuring Mobile Device Access to the Filr Site
Configuring the Filr Desktop Application to Access Files
Configuring Filr to Support WebDAV on Windows 7
Managing a Multiple-Language Filr Site
Setting Up the Filr Site
69
70
Updating Filr
This section describes how to update the Filr, search index, and database appliances.
You cannot update from a small installation (Filr software, database, and search index running as a
single appliance) to a large installation (Filr software, database, and search index running as separate
appliances).
Section 9.1, Prerequisites, on page 71
Section 9.2, Updating the Filr Appliance and the Search Appliance, on page 71
9.1
Prerequisites
In order to successfully update the Filr or search appliance, the data storage location must be on a
data disk, not the system disk. This is the VMware hard disk that you created in Chapter 2,
Installing the Filr Appliance and Configuring the Operating System, on page 21. (For more
information about the type of data that is stored in the data storage location, see Section 1.1.3, Filr
Storage, on page 11.)
When you point the new appliance to the previous appliance data storage location, the new
appliance detects that you intend to do an upgrade. The Filr appliance carries forward the
appropriate configuration data from the old appliance.
9.2
Updating the Filr Appliance and the Search Appliance

The method of updating is the same for the Filr appliance and the search appliance.
The data location for the original appliance that you are upgrading from must be independent of the
appliance on a separate VMware hard disk, as discussed in Section 9.1, Prerequisites, on page 71.
1 Download the new Filr software (Filr.x86_64-version.ovf.tar.gz) to your management
workstation.
2 Extract the Filr.x86_64-version.ovf.tar.gz file on your management workstation until the
Filr-version file folder appears.
You cannot use WinZip to extract the files. If you are extracting on a Windows platform, use 7Zip.
4 Browse to and select the .ovf file in the Filr-version file folder.
5 Click Next, then click Yes to ignore the warning that appears.
6 Click Next.
9 Click Finish.
Updating Filr
71
10 Shut down the Filr appliance you are upgrading.
IMPORTANT: In a large deployment, always bring down Filr first and the search appliance
second. When restarting, reverse the order.
When you shut down the appliance, use the Shutdown button from the Novell Appliance
Configuration screen (as described in Section 7.8, Shutting Down and Restarting the Novell
Appliance, on page 66), or use the init 0 command from the appliance console when you are
logged in as root.
11 Before you power on the new appliance, point it to the VMware data disk that your previous
appliance used. For example, for ESX 5.x:



11d Select Use an existing virtual disk, then click Next.
11e Next to the Disk File Path field, click Browse, then browse to and select the datastore or
datastore cluster that you selected for the appliance that you are updating from.
11f Click Open.
11g Click Next.
11h In the Virtual Device Node section, select SCSI (1:0) from the drop-down list.
11i In the Mode section, select Independent, select Persistent, then click Next.
11j Click Finish.
11k Click OK.
WARNING: If for any reason you need to delete the new or the previous appliance, you
must unlink (remove) the disk. Otherwise, the disk is deleted. Having the disk linked to the
original or to the new appliance does not provide the expected safety. In other words, if the
disk is linked to multiple appliances, and you delete one of them, the disk is deleted despite
the remaining link.
12 Power on the appliance (virtual machine).
13 Click the Console tab. After the appliance starts, accept the license agreement.
14 Specify the same configuration information that you did when installing the original appliance.
If you entered incorrect configuration information, you can log in as root and use the
VACONFIG utility. For more information about how to access the VACONFIG utility, see
Section A.1, Using VACONFIG to Modify Network Information, on page 77.
15 Click Next.
16 Select the data storage location that you used when installing the original appliance.
17 Click Next.
18 (Filr only) If you configured Filr for a clustered environment, you must select Remote NFS:
72
For more information about possible configurations when running Filr in a clustered
environment, see Section 1.5, Recommended Hardware Configurations Based on System
Performance, on page 17.
19 Click Next.
20 Click Configure.
A message saying that the installation was successful is displayed.

21 In a browser, navigate to the following URL:
installation.
22 Log in to the appliance using the vaadmin user and the password that you set.
The Filr Configuration Wizard is displayed.

24 Click Finish to upgrade the appliance.
NOTE: Rather than upgrading your search appliance, you can install a new search appliance and
subsequently re-index your data. Upgrading your search appliance doesnt require re-indexing your
data.
Updating Filr
73
74
Appendixes
I
Appendix A, Troubleshooting the Filr System, on page 77

Appendix B, Third-Party Materials, on page 79
Appendixes
75
76
Troubleshooting the Filr System
Section A.1, Using VACONFIG to Modify Network Information, on page 77

Section A.2, Accessing Filr Log Files, on page 77
A.1
Using VACONFIG to Modify Network Information

The easiest way to update the configuration information for the appliance (such as the IP address,
hostname, and so forth) after Filr is already installed is to use the VACONFIG utility from the
appliance command prompt:
1 In the vSphere client, select the Filr appliance, then click the Console tab.
2 From the command prompt, log in to the appliance.
3 Type vaconfig, then press Enter.
4 In the VACONFIG utility, select Configure, then press Enter.
5 Press the Tab key until the IP address is selected, then modify the IP address as desired.
6 Select Next, then press Enter.
A.2
Accessing Filr Log Files

You can access log files for: Filr, Jetty, Postfix, and Novell FAMT.
icon.
2 Click System Services.

3 In the Log Files column of the table, click the download link for the service for which you want to
view log files.

The following files are available for each service:
Novell Filr: catalina.out (Filr appliance)
Jetty: jetty.stderrout.log (Filr, Search, and MySQL database appliances)
Postfix: mail (Filr appliance)
Novell FAMT: famtd.log (Filr appliance)
Search: indexserver.out (Search appliance)
Troubleshooting the Filr System
77
MySQL: mysqld.log (MySQL database appliance)

78
Section B.1, Oracle Outside In Technology, on page 79

Section B.2, ANTLR 3 License, on page 79
Section B.3, Colt License Agreement, on page 80
Section B.4, Dom4j License, on page 80
Section B.5, iCal4j License, on page 81
Section B.6, ICU4J license (ICU4J 1.3.1 and later), on page 82
Section B.7, JAXEN License, on page 82
Section B.8, Jung, on page 83
Section B.9, ASM, on page 84
Section B.10, Firebug Lite, on page 84
B.1
Oracle Outside In Technology

Oracle shall inform you of any notices and other instructions that are related to third party
components (including open source software) that are included in a program and/or hardware and
that Oracle is required to distribute with such programs and/or hardware. These notices and other
instructions shall be provided to you in at least one of the following ways, at Oracles sole discretion:
(a) automatically installed with the programs or in the installation details; (b) in the program
documentation; (c) in the readme files or notice files; or (d) via a supplemental list. You shall comply
with all instructions related to third party software components (including open source software). If
you reproduce the programs, operating system and/or integrated software, you shall reproduce all
third party notices in an appropriate location in the reproduction and/or in its related documentation
and include any associated source code (to the extent such source code is provided by Oracle), as
required by the applicable notices or as otherwise directed by Oracle.
PDF documents with complete information about the use of Oracle technology in Filr are located in
the following directory on the Filr server:
/opt/novell/filr/stellent-converter
B.2
ANTLR 3 License
Copyright (c) 2003-2008, Terence Parr
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met
Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.
79
Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
Neither the name of the author nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
B.3
Colt License Agreement

Packages cern.colt*, cern.jet*, cern.clhep
Copyright (c) 1999 CERN - European Organization for Nuclear Research.
Permission to use, copy, modify, distribute and sell this software and its documentation for any
purpose is hereby granted without fee, provided that the above copyright notice appear in all
copies and that both that copyright notice and this permission notice appear in supporting
documentation. CERN makes no representations about the suitability of this software for any
purpose. It is provided as is without expressed or implied warranty.
Packages hep.aida.*
Written by Pavel Binko, Dino Ferrero Merlino, Wolfgang Hoschek, Tony Johnson, Andreas
Pfeiffer, and others. Check the FreeHEP home page for more info. Permission to use and/or
redistribute this work is granted under the terms of the LGPL License, with the exception that
any usage related to military applications is expressly forbidden. The software and
documentation made available under the terms of this license are provided with no warranty.
B.4
Dom4j License
Copyright 2001-2005 (C) MetaStuff, Ltd. All Rights Reserved.
Redistribution and use of this software and associated documentation (Software), with or without
modification, are permitted provided that the following conditions are met:
1. 1.Redistributions of source code must retain copyright statements and notices. Redistributions
must also contain a copy of this document.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions
distribution.
3. The name DOM4J must not be used to endorse or promote products derived from this
Software without prior written permission of MetaStuff, Ltd. For written permission, please
contact dom4j-info@metastuff.com.
80
4. The name DOM4J must not be used to endorse or promote products derived from this
Software without prior written permission of MetaStuff, Ltd. For written permission, please
contact dom4j-info@metastuff.com.
5. Products derived from this Software may not be called DOM4J nor may DOM4J appear in
their names without prior written permission of MetaStuff, Ltd. DOM4J is a registered
trademark of MetaStuff, Ltd.
6. Due credit should be given to the DOM4J Project (http://www.dom4j.org).
THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND CONTRIBUTORS AS IS' AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Copyright 2001-2005 (C) MetaStuff, Ltd. All Rights Reserved.
B.5
iCal4j License
Copyright (c) 2008, Ben Fortuna
provided that the following conditions are met:
distribution.
Neither the name of Ben Fortuna nor the names of any other contributors may be used to
endorse or promote products derived from this software without specific prior written
permission.
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
81
B.6
ICU4J license (ICU4J 1.3.1 and later)

COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1995-2001 International Business Machines Corporation and others
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of the Software and that both the
above copyright notice(s) and this permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY
RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising or
otherwise to promote the sale, use or other dealings in this Software without prior written
authorization of the copyright holder.
B.7
JAXEN License
Copyright (C) 2000-2002 Bob McWhirter & James Strachan.
1. Redistributions of source code must retain the above copyright notice, this list of conditions, and
2. Redistributions in binary form must reproduce the above copyright notice, this list of
conditions, and the disclaimer that follows these conditions in the documentation and/or other
materials provided with the distribution.
3. The name Jaxen must not be used to endorse or promote products derived from this
software without prior written permission. For written permission, please contact
license@jaxen.org.
4. Products derived from this software may not be called Jaxen, nor may Jaxen appear in their
name, without prior written permission from the Jaxen Project Management (pm@jaxen.org).
In addition, we request (but do not require) that you include in the end-user documentation
provided with the redistribution and/or in the software itself an acknowledgement equivalent to the
following:
This product includes software developed by the Jaxen Project (http://www.jaxen.org).
82
Alternatively, the acknowledgment may be graphical using the logos available at http://
www.jaxen.org.
THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
Jaxen AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Jaxen
Project and was originally created by bob mcwhirter (bob@werken.com) and James Strachan
(jstrachan@apache.org). For more information on the Jaxen Project, please see http://www.jaxen.org.
B.8
Jung
THE JUNG LICENSE
Copyright (c) 2003-2004, Regents of the University of California and the JUNG Project
distribution.
Neither the name of the University of California nor the names of its contributors may be used to
permission.
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
83
B.9
ASM
Copyright (c) 2000-2005, INRIA, France Telecom
distribution.
Neither the name of the copyright holders nor the names of its contributors may be used to
permission.
B.10
Firebug Lite
Copyright (c) 2006-2007, Joe Hewitt
distribution.
Neither the name of the copyright holders nor the names of its contributors may be used to
permission.
84

85
86

Filr1 Inst

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Filr1 Inst

Uploaded by

Copyright:

Available Formats

www.novell.

Installation and Configuration Guide

1 Overview and Planning

What Is Novell Filr? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Installing the Filr Appliance and Configuring the Operating System

Installing the Filr Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 Configuring Filr for the First Time

Small Deployment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4 Configuring and Maintaining the Filr Appliance

Changing Configuration Options for the Filr Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5 Configuring and Maintaining the Search Index Appliance

6 Configuring and Maintaining the MySQL Database Appliance

7 Configuring and Maintaining the Novell Appliance

Changing Administrative Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

8 Setting Up the Filr Site

Changing Your Search Index Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Novell Filr 1.0 Installation and Configuration Guide

A Troubleshooting the Filr System

Using VACONFIG to Modify Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Oracle Outside In Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Novell Filr 1.0 Installation and Configuration Guide

About This Guide

About This Guide

Novell Filr 1.0 Installation and Configuration Guide

Overview and Planning

What Is Novell Filr?

Filr Applications and Appliances

Overview and Planning

Novell Filr 1.0 Installation and Configuration Guide

Data Storage for the Appliance

Configuration Data for the Appliance

Overview and Planning

Using Novell Filr

Files in Net Folders

Novell Filr 1.0 Installation and Configuration Guide

Filr System Requirements

Filr Server Requirements

Overview and Planning

A directory service: (Not mandatory for simple testing)

Filr User Requirements

Mobile App Requirements

Desktop Application Requirements

Novell Filr 1.0 Installation and Configuration Guide

File Viewer Information

Linux File System

Planning a Multi-Server (Clustered) Filr Configuration

Components of a Clustered Environment

Overview and Planning

Figure 1-1 Clustered Filr VAs

1. Access an NFS Server.

Remote NFS Directory

(NFS ready for Remote Mounting)

5. Access the Filr Appliance Administration

6. Enable Clustering on each Filr VA.

7. Specify each Filr VA in the cluster.

Planning the File Repository

Distributing Different Data Types to Different Locations

Novell Filr 1.0 Installation and Configuration Guide

Recommended Hardware Configurations Based on System

Net Folder Indexing and Synchronization Settings

Resource Allocations for the Appliance

Small Installation Vs. Large Installation

Overview and Planning

Novell Filr 1.0 Installation and Configuration Guide