1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. IFOLDER 3.8 - DEPLOYMENT
  6. Deployment manual

Novell IFOLDER 3.8 - DEPLOYMENT Deployment Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
AUTHORIZED DOCUMENTATION
Deployment Guide
Novell
®
iFolder
3.8
November 2009
www.novell.com
Novell iFolder 3.8 Deployment Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the IFOLDER 3.8 - DEPLOYMENT and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell IFOLDER 3.8 - DEPLOYMENT

Summary of Contents for Novell IFOLDER 3.8 - DEPLOYMENT

  • Page 1 AUTHORIZED DOCUMENTATION Deployment Guide Novell ® iFolder November 2009 www.novell.com Novell iFolder 3.8 Deployment Guide...
  • Page 2 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.
  • Page 3 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.
  • Page 4 Novell iFolder 3.8 Deployment Guide...

  • Page 5: Table Of Contents

    Contents About This Guide 1 Understanding iFolder Deployment Before You Deploy iFolder ........... . 11 1.1.1 Hardware and Software Requirements .
  • Page 6 Deployment Scenarios ............51 Novell iFolder 3.8 Deployment Guide...
  • Page 7 Novell Web Admin Configuration ........
  • Page 8 Novell iFolder 3.8 Deployment Guide...

  • Page 9: About This Guide

    Please use the User Comments feature at the bottom of each page of the online documentation, or go to Feedback (http://www.novell.com/documentation/feedback.html) and enter your comments there. Documentation Updates For the most recent version of the Novell iFolder 3.8 Deployment Guide, visit the Novell iFolder 3.x Documentation (http://www.novell.com/documentation/ifolder3). About This Guide...
  • Page 10 Novell iManager 2.7 documentation (http://www.novell.com/documentation/imanager27/ treetitl.html) Novell Technical Support (http://www.novell.com/support/) Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.

  • Page 11: Understanding Ifolder Deployment

    Section 1.2, “Using a Deployment Manager,” on page 13 1.1 Before You Deploy iFolder Before you install Novell iFolder, you must plan the setup that is suitable for your enterprise. You should organize the deployment based on your current requirements, the quality of service required, and the projected needs for future growth.

  • Page 12: Security Considerations

    (SAN), and clients. This also includes the network requirements. Server Software Requirements A Novell iFolder server has the following software requirements: ® Novell Open Enterprise Server 2 Linux Support Pack 2 with updated Mono patches from the ® patch channel for SUSE...

  • Page 13: Encryption And Key Recovery

    Agent” “Transferring the Encryption Key” 1.2 Using a Deployment Manager Novell iFolder 3.7 and later versions support auto-account creation through an XML-based response ® file. You can use any deployment manager, such as Novell ZENworks , to distribute the response file along with the client to the user machines.
  • Page 14 Novell iFolder 3.8 Deployment Guide...

  • Page 15: Single-Server Deployment

    Single-Server Deployment A single-server setup consists of a single server with up to one thousand clients simultaneously connected to it. In such a setup, the iFolder server and the database are located on a single Open Enterprise Server (OES) 2 server, and the client workstations are connected to it. This scenario is illustrated in the following figure.

  • Page 16: Ldap Configuration

    10 MB per hour. A single-server setup is ideal in such a scenario. Before you use a single-server setup for this scenario, you must consider the following policies: “Limiting the Number of iFolders Per User” on page 17 Novell iFolder 3.8 Deployment Guide...

  • Page 17: Document Management

    “Disabling Sharing” on page 17 “Setting a Disk Quota” on page 17 Limiting the Number of iFolders Per User In order to maintain the server load at an optimal level, you must limit the number of iFolders that a user can create. Use the Web Admin console to limit the number of iFolders per user in a given iFolder system.
  • Page 18 Novell iFolder 3.8 Deployment Guide...

  • Page 19: Multi-Server (Master-Slave) Deployment

    Multi-Server (Master-Slave) Deployment A multi-server setup consists of multiple servers, which can each have more than a thousand simultaneous connections at any point of time. Multi-server configurations are of two types, master- master and master-slave. This section discusses the master-slave setup, and the master-master setup is discussed in Chapter 4, “Multi-Server (Master-Master) Deployment,”...

  • Page 20: Key Benefits

    5 minutes, which is almost 4 MB per second. Enables users across different geographical locations to share data in a secure manner. Enables Novell iFolder servers across different geographical locations to be integrated with Business Continuity Clusters (BCC) for data replication and high availability.

  • Page 21: Scalability Parameters

    In this case, you can deploy Novell iFolder in a multi-server setup so that the manufacturing divisions can share the plans and other documents in a secure manner. Because the number of units...

  • Page 22: Data Synchronization

    Because the presentation material might need last- minute changes, it needs to be synchronized in real time. In such a scenario, an iFolder multi-server (master-slave) deployment can offer real-time data synchronization capabilities. Novell iFolder 3.8 Deployment Guide...

  • Page 23: Multi-Server (Master-Master) Deployment

    Multi-Server (Master-Master) Deployment A multi-server (master-master) setup consists of multiple domains that are created so that master servers can communicate to each other. A master-master setup is particularly useful for organizations that have multiple independent departments that do not need to communicate with each other.

  • Page 24: Key Benefits

    If a slave is included, see Section 3.3, “Scalability Parameters,” on page 21 Chapter 3, “Multi-Server (Master-Slave) Deployment,” on page 19 Each master server can store up to a terabyte of data. The synchronization interval must be 5 minutes. Novell iFolder 3.8 Deployment Guide...

  • Page 25: Deployment Scenarios

    4.4 Deployment Scenarios A multi-server (master-master) setup is particularly beneficial for enterprises that have multiple lines of businesses spread across different geographical locations. The following sections discuss the deployment scenarios for a multi-sever (master-master) setup: Section 4.4.1, “Functional Grouping,” on page 25 Section 4.4.2, “Specialized Services,”...
  • Page 26 Novell iFolder 3.8 Deployment Guide...

  • Page 27: Master-Slave Deployment For A High Web Access Load

    Master-Slave Deployment for a High Web Access Load In a master-slave deployment with a high Web Access load, the setup consists of a master server, a slave server, and a slave server dedicated to Web Access. In this setup, the iFolder server and the database are typically located on the master and slave servers, and the client workstations are connected to the iFolder server.

  • Page 28: Key Benefits

    The number of hits per second to the Web Access server through a browser is based on the ® ® server processing capability and the network link. A Novell iFolder Web Access server does not limit the number of hits because it runs behind Apache and Apache governs the processing capability.

  • Page 29: Deployment Scenarios

    ® ® presentations to other sales or marketing representatives across the globe. Novell iFolder effectively synchronizes these information units among company representatives so that everyone has access to the latest information.
  • Page 30 Novell iFolder 3.8 Deployment Guide...

  • Page 31: Single-Server Cluster Deployment

    Single-Server Cluster Deployment ® ® Cluster-enabling the Novell iFolder service enables the iFolder server to be highly available at any time. If your organization is deploying only one iFolder server for the iFolder service, you should enable a server cluster. This scenario is illustrated in the following figure.

  • Page 32: Ifolder Configuration

    The number of hits per second to the iFolder server through a browser and thick client is based on the server processing capability and the network link. The Novell iFolder server does not limit the number of hits, because it runs behind Apache and Apache governs the processing capability.
  • Page 33 In this scenario, the server must always be online and the file service must be available at all times. Novell iFolder provides an excellent solution for the user to work on the local copy and to update the central iFolder server with the latest document copy at regular intervals. Because updating the document is delta-based, very little data is transferred across the wire.
  • Page 34 Novell iFolder 3.8 Deployment Guide...

  • Page 35: Multi-Server Master-Slave Deployment In A Cluster

    Multi-Server Master-Slave Deployment in a Cluster In a multi-server cluster scenario, the setup consists of multiple servers with up to 1000 simultaneous connections at a time. The iFolder server and the database are located on a single Open Enterprise Server (OES) 2 server with client workstations connected to it. Multi-Server Cluster Figure 7-1 In a multi-server setup, one master and multiple slaves participate in a single iFolder domain.

  • Page 36: Configuration

    LDAP search context or specify ou=KAR, ou=DL. In the latter case, slaves have a specific search context or group containing users who can exclusively access the slave server and store the data. Novell iFolder 3.8 Deployment Guide...

  • Page 37: Scalability Parameters

    Ensure that each iFolder server has its own eDirectory replicas so that the authentication happens locally instead of walking the eDirectory tree. iFolder supports both secure and non-secure communication with the directory server. You can choose any communication channel that you need. Ensure that the directory server is listening on standard LDAP ports for secure and non-secure channels.
  • Page 38 Novell iFolder 3.8 Deployment Guide...

  • Page 39: Using An Ifolder Master Server As A Load Balancer

    Using an iFolder Master Server as a Load Balancer Organizations that need to distribute an equal number of users across iFolder servers need user load balancing support. User load balancing ensures an equal amount of connections per server and balanced data transfer across servers. Load Balancer Figure 8-1 Organizations that need automatic user management should provision the users soon after iFolder...

  • Page 40: Key Benefits

    Consider an example of an organization that has about 100,000 employees in 10 different locations ® ® within a city and 10 different cities in a country. This organization wants to deploy Novell iFolder for information management (storing, retrieving, and sharing) across cities. You want to make sure that management overhead for the 100,000 users in this scenario does not become excessive.

  • Page 41: Load Balancing

    Consider an organization with multiple branches operating in a city that has a network set up in such a way that the response time across any branch is constant. Given this case, Novell iFolder can be deployed with auto-user provisioning without specifying a particular user group. The iFolder server automatically load-balances the users across the servers.
  • Page 42 Novell iFolder 3.8 Deployment Guide...

  • Page 43: Using Fibre Channel To Deploy Ifolder In A Storage Area Network

    Organizations involved in multi-media invest in SANs for storage scalability and high- performance data transfer rates. Implementing Novell iFolder in this scenario enables users to transfer data to and from different users in a fast and reliable manner. Because iFolder performs a delta synchronization of data, the data transfer is minimized and performance is increased.

  • Page 44: Ifolder Configuration

    The number of hits per second to the iFolder server through a browser and thick client is based ® ® on the server processing capability and the network link. A Novell iFolder server does not limit the number of hits because it runs behind Apache.

  • Page 45: Case 1

    Using this deployment, you can formulate a backup strategy where the administrator doesn’t need to find time to perform a backup, and can recover data in real time. This deployment employs Novell Cluster Services and a high speed SAN with a Fibre Channel controller to provide good response time for the data that is synchronized.
  • Page 46 Novell iFolder 3.8 Deployment Guide...

  • Page 47: Using Xen To Deploy Ifolder As A Virtual Service

    The key benefits of deploying iFolder as a virtual service are as follows: With Novell iFolder configured on a virtual server either in single-server mode or multi-server mode, the capability and capacity of the iFolder server remains the same. Using Xen or any other virtualized environment, each virtual host can be used as an iFolder server consuming a common storage, yet providing load balancing between the hosts.

  • Page 48: Ldap Configuration

    Users transparently get the performance and scalability expected from the physical servers. Novell iFolder deployment in a virtual environment ensures that multiple services run on a single physical resource with a dedicated virtual guest server for each service. Given this, an iFolder multi-server setup can run on a single physical server with multiple virtual hosts.
  • Page 49 Although both the subgroups are part of the same organization and work in the same geography, their iFolder policy needs are different. From the administrative perspective, it is simpler if a master- slave iFolder server is deployed and the employee count is low. For this deployment scenario, the iFolder services can be deployed over Xen to maximize the underlying hardware.
  • Page 50 Novell iFolder 3.8 Deployment Guide...

  • Page 51: Nat-Based Configuration

    NAT-Based Configuration Organizations utilize Network Address Translation (NAT) to secure server access and identity. This helps users access all services through a single public IP address. Section 11.1, “Planning,” on page 51 Section 11.2, “Key Benefits,” on page 51 Section 11.3, “Scalability Parameters,” on page 51 Section 11.4, “Deployment Scenarios,”...
  • Page 52 Web Admin console must be able to work outside the NAT network, because the users might sometimes be in a public domain and might need access to their iFolder data. The Novell iFolder server’s public URL must be set to the router's DNS address, so that Web Access, Web Admin, and the clients can access the iFolder server inside the NAT network from the external network.

  • Page 53: Using Router Port Forwarding And Mod Proxy

    Using Router Port Forwarding and Mod Proxy Your organization does not always need to expose the iFolder data servers to the Internet in order to enable users to access information through the firewall. Instead, you can use a port forwarding mechanism and mod proxy as a means to handle requests from external users without directly exposing the iFolder data servers.

  • Page 54: Mod Proxy

    The figure given below illustrates how mod proxy can act as a gateway to the requests directed from the external network by obtaining the required information from the internal iFolder application server. Mod Proxy Figure 12-2 Novell iFolder 3.8 Deployment Guide...

  • Page 55: Port Forwarding And Mod Proxy

    12.3 Port Forwarding and Mod Proxy Consider an example where myifolder.organization.com/ifolderapp is an internal ifolder application server and external users need to access this server using the URL www.myifolder.organization.com. In this scenario, mod proxy can enable the external users to access the internal iFolder application server by rewriting the external URL <...

  • Page 56: Deployment Scenarios

    URL redirection can be done by Apache supported mod proxy. Mod proxy has multiple configurations. For more information on mod proxy, refer to the mod proxy configuration information at the Apache Module mod proxy Web site (http:// httpd.apache.org/docs/2.0/mod/mod_proxy.html). Novell iFolder 3.8 Deployment Guide...

  • Page 57: Deploying Ifolder Behind Access Manager Or Ichain

    Internet kiosk. Nevertheless, your business must be accessible to employees, customers, and partners, regardless of location or time of day. Novell Access Manager solves this challenge by helping you maximize access without limiting security or control.

  • Page 58: Key Benefits

    Novell iFolder can also be accessed via the SSL-VPN option of Access Manager for a trusted tunnel connection. This setup provides better access control and administration for the administrator to manage the security aspects of an organization.
  • Page 59 In this scenario, the company can install and configure iFolder behind Access Manager to provide stricter access control and security. Novell iFolder is configured to use Access Manager as an access method so that the employees and business partners can use single sign-on as well as a secure connection from the public Internet.
  • Page 60 Novell iFolder 3.8 Deployment Guide...

  • Page 61: Deploying The My Documents Folder As An Ifolder

    Section 14.2.2, “Single Server and Multi-Server,” on page 62 Section 14.2.3, “Novell iFolder Configuration,” on page 62 Section 14.2.4, “Novell Web Admin Configuration,” on page 63 Section 14.2.5, “Web Access Configuration,” on page 64 Section 14.2.6, “Converting the My Documents Folder to an iFolder,” on page 64...

  • Page 62: General

    Section 14.1, “Environments,” on page 61, the method to configure SSL options differs with iFolder versions. iFolder 3.6 does not support SSL communication, so you must use it only in a trusted environment. Novell iFolder 3.7 and later versions do support SSL. SSL Recommendations...

  • Page 63: Novell Web Admin Configuration

    14.2.4 Novell Web Admin Configuration The Web Administration console helps you create policies for the system as a whole or at every user/group level. For iFolder 3.7 and later versions, LDAP groups are supported. “Provisioning” on page 63 “Limiting iFolder Count to One” on page 63 “Sharing iFolders”...

  • Page 64: Web Access Configuration

    Ensure that the size of the iFolder does not grow beyond the limit specified by the administrator. You should avoid storing a large amount of data in an iFolder because data synchronization is evenly distributed among the iFolders on the workstation. Novell iFolder 3.8 Deployment Guide...

This manual is also suitable for:

Ifolder 3.8

Table of Contents