Upgrading FocusOPEN 3.4.5.x to 3.4.6

Introduction

The upgrade from FocusOPEN 3.4.5.x to 3.4.6 should not be deployed to a production instance without testing it first on a development server (and making full backups).

Windows system administration and SQL Server knowledge are required. If you do not have these skills, you are advised to request priority support assistance from the My Account area. You must have a Commercial licence to be able to access our support plans, alternatively, use the forum to request assistance from the FocusOPEN community.

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

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

Backup your FocusOPEN installation.

You are advised to use the sandbox deployment guide to make a backup of your current FocusOPEN installation (with all assets and users), upgrade that and then take your old 3.4.5.x edition off-line and re-point the domain to the new 3.4.6 deployment.

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 "346_updates.sql"
osql -n -E -d FocusOPEN -S %FocusOPENDB_SQLSERVER% -i "346_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 “346_updates.sql” updater script in the the DatabaseSetup\UpgradeScripts folder of the 3.4.6 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.6 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 web.config file back and make the changes described below.

Some users may find a comparison application such as Beyond Compare or WinMerge to be useful to manage the process of identifying the sections of the config file to be amended.

Web.config

Add the following keys if not already present

<add key="AddToCartReminderMessage" value="Restricted: you must request permission to use this asset by adding it to your cart" />
<add key="AutoUpdateExpiryOnAssetFileReplacement" value="false"/>
<add key="NewlineReplacementChar" value=""/>
<add key="AutoSelectedPrimaryGroup" value="0"/>
<add key="UsePDFToTextForPDFTextExtraction" value="true"/>
<add key="HideGroupMetadataDropDownViewSelector" value="false"/>

The following key has been added to the controls section of web.config

<add tagPrefix="app" src="~/Controls/Admin/BatchActions/AssetListBatchActions.ascx" tagName="AssetListBatchActions" />

Some further changes to the following existing keys are recommended:

This will force the upload control to use a faster maximum upload of 10MB per second.

<neatUpload xmlns="http://www.brettle.com/neatupload/config/2008" useHttpModule="true" maxNormalRequestLength="4097151" maxRequestLength="4097151" maxUploadRate="10000" defaultStateStoreProvider="InProcUploadStateStoreProvider">

Increases the maximum number of assets that can be deleted without a password prompt.

<add key="MaxBulkDeleteAllowed" value="500" />

Stops the asset type as well as title from being copied across in template cataloguing operations

<add key="TemplateCataloguingFieldsToExclude" value="Title,AssetType"/>

You can normally use the web.config file from the deployment package and copy it over the top of your old one - although you may lose any settings modifications you have made. Consult the deployment guide for a full explanation of the new settings.

AdminNavigation.config

The AdminNavigation.config file hass been updated with new features to allow the batch modification of users and some other adjustments. Unless you have changed this on an existing installation, you can usually copy the files wholesale from the deployment package over the top.

Brand CSS Changes

The asset detail pop-up window has been made wider to accommodate the new widescreen video preview plug-in.

In Styles.css the following changes need to be applied.

}
.DetailsWrapper
{
	margin-bottom: 0;
	margin-left: auto;
	margin-right: auto;
	margin-top: 0;
	text-align: left;
	/* width: 700px; */
	/* Increased width - Apr 2013 */
	width: 800px;
}
.DetailsThbPanel
{
	background-color: #FFFFFF;
	border: 1px solid #EAEAEA;
	/*height: 470px;*/
	/* width: 360px; */
	/* Increased width - Apr 2013 */
	width: 430px;
}

Since the brands folder is usually set aside when upgrading, the above will need to be made manually to every brand.

Finishing Up and Testing

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.

If you have difficulties with the upgrade, try a fresh deployment of 3.4.6 and see if that is successful.

 
upgrading-focusopen-3.4.5.x-to-3.4.6/start.txt · Last modified: 2014/05/26 17:05 by admin