Knowledgebase:
How to Migrate from Webmail to Workflow
Posted by Aly Essa, Last modified by Aly Essa on 13 April 2017 10:02 AM

Release Information

As of January 2015, Webmail is discontinued. The latest version of FileCatalyst Webmail (v4.9.6 release date: Feb 24, 2016) only contains critical fixes and updates. The Windows Installer for Webmail has been discontinued starting in version 4.9.6. Until Aug 30th, 2016 only critical updates to Webmail will be released. No updates to Webmail will be offered after Aug. 30th, 2016. All the functionality of Webmail is now included in a product called FileCatalyst Workflow. We encourage everyone to upgrade to Workflow ASAP to remain up-to-date. Please note if after your upgrade your Language File entries do not show, you will need to restart the Tomcat Web Server.

 

Why Upgrade?

First and foremost, starting in Workflow v4.9.6 we now provide an alternative to Java Applets. The list of web browsers that either no longer support or will soon stop supporting Java Applets is growing fast. The new file transfer method that does not require Java Applets is called TransferAgent.

TransferAgent is FileCatalyst’s latest web-based file transfer tool. TransferAgent supports our lightning fast UDP-based file transfer acceleration protocol and smoothly handles large files and complex directory structures for both uploads and downloads. TransferAgent is only available in FileCatalyst Workflow.

Here is a complete list of features only available in FileCatalyst Workflow:

  • TransferAgent for upload and download (no Java applet required).
  • Ability to customize the directories where job files are stored.
  • Ability to start a file transfer and be able to close the web browser while the transfer is still in progress.
  • Advanced LDAP/Active Directory integration using secure proxy search account.
  • PermaLinks to upload forms.
  • Ability to generate XML/JSON/PDF files containing all job information.
  • Ability to customize user fields for Registration, Anonymous, User Edit, and Admin.
  • Users can select FTP or FileCatalyst Server at job submission.

Version History:

http://support.filecatalyst.com/index.php?/Knowledgebase/Article/View/35/13/filecatalyst-webmail-and-workflow-release-notes


Overview

This article describes how to upgrade an existing FileCatalyst Webmail installation to the latest Workflow version. It is assumed that Workflow is deployed on Apache Tomcat.

To ensure a smooth upgrade, our support team can perform a migration from Webmail to Workflow for your server. This upgrade service is part of our professional services package and there are additional fees associated with it. Please contact your FileCatalyst Sales Representative for details.

 

Note:

New License Key:

Upgrading from version 3.x.x to 4.x.x will require a new set of license keys. Please contact your FileCatalyst Sales Representative with a license request string to obtain your new license key. The request string can be found on the Licenses Page. It can be accessed from Modify Configuration and selecting Licenses under System Configuration section.

 

Environment

FileCatalyst Webmail v4.9.5 and earlier.

 

Resolution

Download Update:

You will need the latest WAR file from our website http://download.filecatalyst.com.

Contact your FileCatalyst Sales Representative in order to obtain a username and password. Locate and download the FileCatalyst Workflow application called fcwebworkflow_war.zip.

Migration Instruction

  1. Log in as Super Admin to FileCatalyst Webmail. Click on the About FileCatalyst icon and make a note of the path to your configuration folder. Look for it in the field named Configuration Path.
  2. Stop Tomcat service.
  3. Make a backup copy of the Configuration Folder.
  4. Make a backup of MySQL Database, using a MySQL dump tool, or by any other method that you find convenient.
  5. Backup fcweb.war and /fcweb folder to a location outside of Tomcat. This folder and WAR file are located in /<Tomcat-Home>/webapps/
  6. Delete the fcweb.war and /fcweb folder from /<Tomcat-Home>/webapps/.
  7. Unzip the workflow.war from the fcwebworkflow_war.zip file and place it in /<Tomcat-Home>/webapps/.
  8. Rename workflow.war to fcweb.war, so the path to your application doesn't change in your Web URL.
  9. Delete the /<Tomcat-Home>/work/Catalina directory.
  10. Start Tomcat service. Tomcat will re-deploy the new WAR file and make a new directory /<Tomcat-Home>/webapps/fcweb/ automatically.
  11. Open a web browser of your choice and access FileCatalyst Webmail as usual. If you are on the local machine, go to http://localhost/fcweb or http://localhost:8080/fcweb. (Assuming the Tomcat default port 8080, otherwise substitute an appropriate port)
  12. Log in with username Init with the password aaaaa.
  13. Click on the button for Existing or Custom Configuration folder.
  14. Enter the path you noted in Step 1 from the Configuration Path.
  15. FileCatalyst Workflow will re-initialize and all your previous settings will be imported into the new deployment.
  16. From Modify Configuration select General Settings under System Configuration. Clear the field adjacent to Custom Job ID and Save.
  17. From Modify Configuration select Edit Language File. Select the content and save to a text document. This is to preserve any customization you have made. Select Default English and OK. This will apply the Workflow tags to your deployment. Any previous customization to the language file will need to be reapplied.
  18. From Modify Configuration, select User Data Fields.  Locate the preferredServer line, and select the checkbox under the Show To Admin column.  Press Save.
  19. While in the Modify Configuration sections, navigate to Recipient E-mail. When the context window appears, select **Default Recipient E-mail**. Copy the contents of the current RecipeintEmail_email.txt file into a text editor and save it. Scroll down to the bottom of the page and click Default Recipient E-mail. Once the page reloads hit Save.
  20. From Modify Configuration select Licenses under System Configuration. Add your new Workflow key and delete any other keys above that line. The application will pick up the key in the top most spot and validate against it first. Once your new key is in the top most position hit Save. You will be required to restart Workflow to apply the changes. In the bottom right hand corner of the Modify Configuration page select the link to Restart System.

 

Roll-Back Guide

  1. Stop the Tomcat service.
  2. Delete the /<Tomcat-Home>/webapps/fcweb/ directory.
  3. Delete the /<Tomcat-Home>/webapps/fcweb.war file.
  4. Delete the /<Tomcat-Home>/work/Catalina directory.
  5. Place the backup version of fcweb.war into /<Tomcat-Home>/webapps/ folder.
  6. You can either backup the existing configuration folder or delete it.
  7. Place the previously backup Configuration Folder in the original location.
  8. Start the Tomcat service. Tomcat will redeploy the WAR file and make a new directory /<Tomcat-Home>/webapps/fcweb/ automatically.
  9. Open a web browser of your choice and access FileCatalyst Webmail as usual. If you are on the local machine, go to http://localhost/fcweb or http://localhost:8080/fcweb. (Assuming the Tomcat default port 8080, otherwise substitute an appropriate port)
  10. Log in with username Init with the password aaaaa.
  11. Click on the button for Existing or Custom Configuration folder.
  12. Enter the path you noted in Step 1 from the Configuration Path.
  13. FileCatalyst Workflow will re-initialize and all your previous settings will be imported into the new deployment.