Upgrading FocusOPEN 3.4.7.x to 3.4.8

Introduction

The upgrade from FocusOPEN 3.4.7.x to 3.4.8 should be tested first on a development server (and having made full backups). Windows sysadmin and SQL Server knowledge are required.

Note 1: This upgrade procedure is for 3.4.7.x users only, do not attempt a direct upgrade from an older version to 3.4.8.

To check your current version, enable engineer user mode for your account and view the utilities/settings page in the admin area. The FocusOPEN version will be at the bottom of the page.

Backups & Preparation

A backup of the whole FocusOPEN application folder is recommended with at least the webroot folder being the minimum. It is especially important you make a copy of your configuration settings and original database.

Database

Open the upgrade.cmd batch file and check the connection parameters to your FocusOPEN database and then run the upgrade.cmd script. You need to change three different areas:

set FocusOPENDB_SQLSERVER=(LOCAL)

Swap (LOCAL) for the instance of your local SQL Server.

echo osql -n -E -d FocusOPEN -S %FocusOPENDB_SQLSERVER% -i "348_updates.sql"
osql -n -E -d FocusOPEN -S %FocusOPENDB_SQLSERVER% -i "348_updates.sql"

Swap 'FocusOPEN' for the name of the FocusOPEN database.

If you installed FocusOPEN previously without changing the database name you may only need to change the database connection instance (at the top of the script).

Using SSMS To Upgrade The Database

Alternatively, you can use SQL Server Management Studio to execute the “348_updates.sql” updater script in the the DatabaseSetup\UpgradeScripts folder of the 3.4.8 deployment package.

Upgrade Application Webroot and Change Config Settings

  1. Make a backup copy of your App_Data folder
  2. Make a backup copy of your AuthPlugins folder
  3. Make a backup copy of your Config folder
  4. Make a backup of your web.config file
  5. Make a backup copy of your Brands folder
  6. Copy the webroot folder from the 3.4.7 deployment package over the top of your existing webroot to replace and update your files.
  7. Delete the App_Data and Brands folders
  8. Move the Config, AuthPlugins and web.config folders/files over to a location away from the Webroot - you will need these later
  9. Copy your Config folder back to to the webroot to replace the one from the deployment package.
  10. Copy your Brands folder back to to the webroot to replace the one from the deployment package.
  11. Copy your App_Data folder back to to the webroot to replace the one from the deployment package.
  12. Copy your AuthPlugins folder back to to the webroot to replace the one from the deployment package.
  13. Copy your web.config file back and make the changes described below.

Use a comparison application such as Beyond Compare or WinMerge to identify the sections of the config files to be amended.

Web.config

Add the following keys if not already present

<add key="APIFileFolder" value="##ApplicationDataFolder##\API_File"/>
<add key="APIPersistentDataFolder" value="##ApplicationDataFolder##\API_persistent_data"/>
<add key="APSInstanceToUse" value=""/>
<add key="APSLoadBalanceType" value=""/>
<add key="TemplateCataloguingSupportsPublishing" value="false"/>
<add key="LMAPLStatus" value="false"/>
<add key="EnforceNativeBlankPasswords" value="false"/>
<add key="DefaultShortDescription" value="No description available"/>
<add key="MaximumFileVersions" value="-1"/>
<add key="ImageExtensions" value="gif,jpg,jpeg,png,bmp,tif,tiff"/>
<add key="ThumbnailCustomIdentifierData" value=""/>
<add key="AllowDuplicateAssetsAcrossBrands" value="false"/>
<add key="EnableAPIPersistentDataFileSystemCopies" value="true"/>
<add key="SuppressCategoryCounts" value="false"/>
<add key="CollectionsGuestAccount" value=""/>
<add key="ArbitraryFileDataEnabled" value="false"/>
<add key="ArbitraryFileDataAllowedExtensions" value=""/>
<add key="SavedSearchesStatus" value="false"/>
<add key="EnhancedLightboxStatus" value="false"/>
<add key="BatchImportSimpleMode" value="false"/>
<add key="OptionalNavURL" value=""/>
<add key="OptionalNavURLAnchorText" value=""/>
<add key="OverrideCartBrandLink" value="false"/>
<add key="NoDedicatedUploadURLForUploadUsers" value="false"/>
<add key="HideSearchDDLSearchMetadataInput1Filter" value="false"/>
<add key="NoUploadingDigitalAssets" value="false"/>
<add key="AvailableCatalogueSortHyperlinks" value=""/>
<add key="ShowAscDescSorting" value="false"/>
<add key="DisableCustomSortOnListView" value="true"/>
<add key="DocumentTextFilterDisabledByDefault" value="false"/>
<add key="DocumentTextFilterDisableFeatureEnabled" value="true"/>
<add key="HideFileColumnInListViewSearchResults" value="false"/>
<add key="HideNonCoreSystemMetadataOnAssetForm" value="false"/>
<add key="ShowZoomControl" value="false"/>
<add key="IncludeTotalCountOnAssetExport" value="false"/>

You are recommended to copy the remainder of the 3.4.8 web.config file from below the appsettings node over the top of the existing file, alternatively the following lines from the httphandlers section:

<add verb="*" path="AssetCropPreview.*.ashx" type="FocusOPEN.Website.Components.Handlers.AssetCropPreviewHandler, FocusOPEN.Website" />
<add verb="*" path="APIFile.*.ashx" type="FocusOPEN.Website.Components.Handlers.APIFileHandler, FocusOPEN.Website"/>
APIFilePaths.config

This file should be copied into the config folder (from the deployment package).

APSControlStrings.config

This file should be copied into the config folder (from the deployment package).

StringSettings.config

This file should be copied into the config folder (from the deployment package).

APS

The FocusOPEN 1.5.x APS (distributed with FocusOPEN 3.4.7 earlier) is not compatible with FocusOPEN 3.4.8. Backup the configuration files for the current version (including any plugin changes) and uninstall the old APS, then re-install the new one.

The new APS will generate a watermark on all previews. If you are commercial user, this can be removed by adding a license key which you can obtain from FocusOPEN Software. See Appendix D of the deployment guide for details.

Conclusion

Fully test the new edition, including searching and uploading before making it live. Backups of any production instance are recommended, as well as scheduling a user outage period prior to a production deployment.

 
upgrading-focusopen-3.4.7.x-to-3.4.8/start.txt · Last modified: 2015/05/20 10:45 by admin