24.3 Upgrading iFolder 3.x

You can upgrade iFolder 3.x on OES 1 to iFolder 3.8.4 on OES 2 SP3. This is a single-server scenario, where the source and target servers reside on the same machine.

24.3.1 Server Upgrade

Ensure that the server-side data is backed up before you perform the upgrade.

You must use the YaST-based Novell iFolder configuration for the in-place upgrade. A YaST upgrade of OES 1 to OES 2 SP3 upgrades the configuration values of the iFolder enterprise server from the 3.x iFolder server to the 3.8 iFolder server.

For details on YaST-based configuration, see Deploying iFolder Server in the Novell iFolder 3.8 Administration Guide.

  1. Install OES 2 SP3 by using YaST. For more information, see Installing iFolder on an Existing OES 2 Linux SP2 Server in the Novell iFolder 3.8 Administration Guide.

  2. Select Use Following Configuration and click Novell iFolder to change the default configuration settings for iFolder.


    If you decide to use default settings, click Next to start Novell iFolder 3 configuration.

    For security reasons, it is recommended that you always change the default iFolder configuration settings.

  3. Follow the YaST on-screen instructions to proceed through the Novell iFolder 3.8 configuration.

    The table in the Configuring the iFolder Enterprise Server in the Novell iFolder 3.8 Administration Guide summarizes the decisions you make.

    NOTE:In an upgrade scenario, the following fields in the YaST UI for iFolder are disabled so you don't need to specify them.

    • Path to the Server Data files

    • Install into Existing iFolder Domain

    • Private URL of Master server

    • Directory Server Address

    • iFolder Admin Password

    • Verify iFolder Admin password

    • LDAP Search Contexts

    • LDAP Naming Attribute

    • Require a secure connection between the LDAP server and the iFolder server

If you have upgraded an iFolder server to OES2 SP3 in a cluster setup, move to common proxy using the move_to_common_proxy.sh script fails. This is because during upgrade, the cluster volumes are not mounted. After upgrade is successful, you must use the following command on the node where iFolder cluster is running:


This will update the Simias.config file with the necessary configuration information required for common proxy framework. In non-cluster setups, this runs automatically as part of post install script.

24.3.2 Client Upgrade

Understanding the Upgrade Process

With the client upgrade, binaries are upgraded with the new version of binaries and the client data is auto-upgraded.

Preparing for the Upgrade

Make sure that you perform the following server-side operations so that the user is notified of the new version of the iFolder client and prompted to accept the client upgrade.

IMPORTANT:You must ensure that the user backs up the Simias store before upgrading the client.

  1. Enter http:\\ IP address of iFolder serverin the browser to go to the OES 2.0 home page.

  2. Download the client RPMs or executables from the OES 2.0 home page.

  3. Place the RPMs under the respective platform directories in the path ifolder_installDirectory/lib/simias/web/update/unix

    The latest client RPMs are installed only if they are present in the given path. The automatic installation happens when the user attempts to connect the 3.x or 3.4.1 client to the iFolder 3.8 server. The names of the platform-specific directories are in the version.config file in the same path. A script file named install-ifolder.sh in the unix directory contains the commands for upgrading the RPMs to the latest version.

    Examples for install-ifolder3.sh are as follows:

    • rpm -Uvh <absolute path of simias rpm>
    • rpm -Uvh <absolute path of ifolder rpm>
    • rpm -Uvh <absolute path of nautilus-ifolder3 rpm>
  4. Modify version.config to include entries for the directory where in the RPMs or the executables are placed.

Upgrade Procedure for the User

  1. Connect the existing client to the server.

    The client automatically prompts the user to accept the client upgrade when he or she attempts to connect an iFolder 3.x or 3.4 1 client to a 3.8 server. For details, refer to Upgrading iFolder 3.x Clients in the Novell iFolder 3.8 Cross-Platform User Guide.

    For instructions on performing a manual upgrade, refer to Manually Upgrading to iFolder 3.8 client on Linux in the Novell iFolder 3.8 Cross-Platform User Guide.