The upgrade from FocusOPEN 3.3.7.x to 3.3.9.5 is extensive and introduces many new features and facilities. Because of this, the upgrade process is more involved than previous editions. You must have reasonable working Windows system administration knowledge and a grasp of SQL Server to complete the upgrade. If you lack these skills, you are recommended to request priority support assistance via the My Account area or contact form.

Note 1: This upgrade procedure is not suitable for pre 3.3.7.2 users. Ensure you have carried the upgrade to 3.3.7.2 before attempting this upgrade. If upgrading from 3.3.7.1, ensure you have made the hotfix upgrade to 3.3.7.2 first.

Note 2: This upgrade should not be used with FocusOPEN 3.3.9.2 beta.

Note 3: The new APS is incompatible with old editions of FocusOPEN. If you want to keep previous editions of FocusOPEN running without upgrading them, they must be held on a separate server.

Before proceeding, it is recommended you make a complete backup of the whole FocusOPEN folder (including webroot, data and other folders). Also, backup your FocusOPEN SQL Server database. If you install FocusOPEN to a virtual machine and your chosen virtualisation technology supports it, you are recommended to make a snapshot of the current 3.3.7.x FocusOPEN instance.

Ensure that all current APS jobs have completed processing and that all users have been asked to log out of FocusOPEN.

1. Note: the new APS is not compatible with any previous versions of FocusOPEN and you cannot have 2 instances on the same server.
2. Uninstall the existing APS service using the Windows control panel add/remove programs and features option.
3. Install the new APS from the APS installer in the 3.3.9.5 deployment package.
4. Start the APS service and check it set to start automatically (use the delayed start option is available).

Using SQL Server Management Studio, run the “Upgrade 3.3.7.2 to 3.3.9.5.SQL” updater script in the in the DatabaseSetup\UpgradeScripts folder of the 3.3.9.5 deployment package over the FocusOPEN database.

1. Make a backup copy of your config folder, especially appsettings.config and also web.config in the webroot.
2. Copy the webroot folder from the 3.3.9.5 deployment package into your existing webroot.
3. Either copy your existing web.config and appsettings.config files and make the changes shown below or manually transfer any custom settings from the old (copied) files to the new version.
4. If using the former option, add these lines to the web.config file (after the LightboxManager.MaxNumberCCEmails) setting.

<add key="NumberOfMetadataFields" value="50" />
<add key="MaxBulkDeleteAllowed" value="100" /> 
<add key="PasswordResetEnabled" value="true" />
<add key="MaxSelectableMetadataDepth" value="10" />
<add key="PluginsPath" value="~/Plugins/" /> 
<add key="RegisterUserRequiresKnownEmailFormat" value="InternalUsers" /> 
<add key="APIRestrictAccounts" value="" /> 
<add key="APIObeyIPAddressRestrictions" value="true" /> <add key="OverrideCallbackUrl" value="" />

Also add the following web handler references under Asset Files

<add verb="*" path="AssetBitmapGroup.*.*.ashx" type="FocusOPEN.Website.Components.Handlers.AssetBitmapGroupHandler, FocusOPEN.Website" />

And the following new references:

<!--Callbacks -->
<add verb="*" path="ProcessingCallback.ashx" type="FocusOPEN.Website.Components.Handlers.ProcessingCallbackHandler, FocusOPEN.Website" validate="false" />
<add verb="*" path="BitmapProcessingCallback.ashx" type="FocusOPEN.Website.Components.Handlers.BitmapProcessingCallbackHandler, FocusOPEN.Website" validate="false" />

If in doubt, you can usually use the web.config file from the 3.3.9.5 deployment package.

Add the following key to appsettings.config in the config folder:

<add key="ScriptsPath" value="~/Scripts"/> <add key="APILogFolder" value=""/>

Changes have been made to some of the other configuration files such as AdminNavigation.xml so ensure you have up to date editions of these files also or you may not be able to access all features properly.

Add a new folder: “AssetBitmapGroups” as a sub-folder of your data folder. Verify that this has permissions set to 'Everyone' full control (or use the IIS_WPG account on a production server if you prefer).

Once you have completed the upgrade procedure, you are recommended to restart IIS and ensure basic functions still work like logging in, uploading and cataloguing.