Upgrade to version 1.5 from version 1.4

Build 1501 on 14/Nov/2017  This topic last edited on: 10/Jun/2016, at 16:47

Steps for upgrading an existing Tark4/Gn4 installation to version 1.5 from version 1.4

Click to toggle expandGeneral warnings and information

•If you want to use error reporting over Tera mail server, add configuration to the GlobalConfig, as explained in Auto-reporting of GN4 system exceptions, paragraph "In version 1.5 or newer".

•If you want to add IMAP support for notifications, see Enabling IMAP server in ServerConfig.

•There are changes in thumbnails generation. Look here for details: Configuring page thumbnails in 1.5 or newer.
Click to toggle expandModify customized configuration files and add-ins

Use a merge utility to see all changes and additions to the standard configuration files, against those you customized.

This is the list of new files in version 1.5, list extracted comparing the 1.5 and 1.4 versions of the editorial_installconfig, it is strongly recommended to do the same check against you current install or upgrade configuration:

Data files (to be imported using cmd4 import)

<DataFile>Data\configScope.xml</DataFile>

<DataFile>Data\notifyDests.xml</DataFile>

<DataFile>Data\GN4\printTemplate_PSFile.xml</DataFile>

<DataFile>Data\GN4\printQueue_PSFile.xml</DataFile>

<DataFile>Data\GN4\printConfigs.xml</DataFile>

New Config files (to be imported using cmd4 config)

<ConfigFile>Global\wf_CopyUserConfig.xml</ConfigFile>

<ConfigFile>Global\GN4_Tark4_Common\wf_CreatePreviewThumbnailDocumentIds.xml</ConfigFile>

<ConfigFile>Global\GN4_Tark4_Common\wf_CreatePreviewThumbnailImageIds.xml</ConfigFile>

<ConfigFile>Global\GN4_Tark4_Common\wf_Import_Tark.xml</ConfigFile>

<ConfigFile>Global\GN4_Tark4_Common\wf_Split.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_ArchiveZip.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_ArticleNew.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_GeneratePS.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_PSFile.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_sendAssetsToNewsroom.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_sendAssetsToNewsroomInteractive.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_sendEventsToNewsroom.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_sendEventsToNewsroomInteractive.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Default.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Filed.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Page Closed.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\feed_AdobeTask.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\search_AdobeTasks.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\wf_AdobeAddProductToTask.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\wf_InDesignUploadJumpLayout.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\wf_AdobeCopyExtDoc.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\gnpcInt_WebParts_configScope.xml</ConfigFile>

<ConfigFile>Global\MobileApp\search_MobileAppTasks.xml</ConfigFile>

<ConfigFile>Global\MobileApp\wf_MobileAppAddProductToTask.xml</ConfigFile>

New Icon files (to be imported using cmd4 icon)

Import all the icons listed in tark or editorial installconfig, as many are new, and some already existing were modified.

As we added the support for 64-bit client software, replace your custom projects with the standard custom projects. Before replacing projects, make a list of all references you've added to your custom projects, and port them to the replaced project.

•The ArticleSaveAs script in Article.vb 1.5.1524 and 1.4.1524 requires the objectUI ArticleSaveAs to exist in ted4_Config.xml and changes in NewArticle objectUI. Standard configurations updated. UPDATE YOUR CUSTOM TED4_CONFIG.XML FILE ACCORDINGLY.

•Schema paths in configuration files could be incorrectly specified by using a dot operator on a non-referencing attribute, e.g. [archiveObject.publicationDate.name] where archiveObject.publicationDate does not reference another object. These invalid paths are now captured and will throw an exception that will stop the application starting. An occurrence of this has been removed from the standard configurations ([archiveObject.publicationDate.name]), ensure that you don't have any in other configurations by test running the applications after updating the configuration.

•Added new enumeration values for the folderKind attribute of folders and folderObject (computed). Specifically it is possible to mark a folder as of "Contacts" kind, so that searches on folder can be filtered by folders, acting as "Contact lists". Portal and client configurations use the new search field. You need to edit the contacts folder properties and set the folder kind to "contact", and then recompute the contacts object, and reindex them:

ocmd4 recompute -conditions gn4:contact -srvname Main -username xxx -password yyy

ocmd4 index -conditions gn4:contact -srvname Main -username xxx -password yyy

ocmd4 commitindex -srvname Main -username xxx -password yyy
Click to toggle expandUpgrade the database by running the srv4 dbupdate

If you maintain an editorial or tark4 update or installconfig, you can at the same time import the new/modified config/data/icon/strings files using the:

 srv4 dbupdate -config [configfile] -nocompute

Otherwise, run the:

 srv4 dbupdate -s [master schema file] -d "" -nocompute
Click to toggle expandImport the config/data/icon files

If you do not maintain an update or install config file, you will have to manually import all the updated and new files: see "New files in version 1.5" for the list of new files.

1.Locate the files you customized in the version 1.4 and compare them with the files supplied with the version 1.5. Do all needed adjustments to keep your changes and add what’s new/changed.

2.Import using the appropriate command (import, config, icon, strings) :

othe new files;

othe files you compared and modified;

oall the other files listed in the released installconfig (that we may have modified from 1.4 to 1.5).

The files import order is important, see the released installconfig for the proper order.
Click to toggle expandCheck the WinClientResources file

The following style is required by builds 1.5.1585.0 or later:

<Style x:Key="SysTextElementHighlightStyle" 

  TargetType="{x:Type TextElement}">

  <Setter Property="FontWeight" Value="Bold"/>

  <Setter Property="Foreground" Value="Red"/>

</Style>

Please ensure that you have reimported WinClientResources when using 1.5.