QDX5.4 upgrade

Uma.

We have used the same migration process for various upgrades and altough we don’t have many of the FRL/Xlate sites (most of our sites use TCL script translations) we have migrated from 3.5.5 to 5.4 issue free.

While we have this scripted, we perfom the following.

save (we use tar) a copy of the various ‘key’ files/directories in our 3.5.5; and

create a site in 5.4 (hcisiteinit); and

install the ‘tar’ file; and

Use the supplied 5.4 routines to verify format, tables and xlates; and

compile pdls; and

tclindex the tclprocs; and

load, verify and save the NetConfig file (we actually process this).

Our ‘key’ files are: NetConfig NetConfig.disabled tclprocs Xlate Tables formats local .monitorAllSite.cfg Alerts bin

The NetConfig script just ensures that all NetConfig files use the same bitmaps and other ‘standard’ configurations and replaces old with new root paths.

I hope this helps

Hi, in reading the installation documentation for 5.4, i thought it stated that to upgrade to 5.4, the site had to be at a minimum of 3.8.1p. However, from your post it seems like you were able to go directly from 3.5.5 to 5.4. Is this correct? If so how did you accomplish.

William.

When we migrated from 3.5.5 to 5.4,we followed our ‘normal’ migration procedure above.

In its simplest form:

Create  a new site in 5.4; and

Copy the NetConfig from 3.5.5;

Edit and Save.

We have used this for a number of migrations.  

We currently have production on 3.5.5 (testing in 5.4 ready for migration) and test on 5.4, having migrated from 5.2.1 (migrated from 3.5.5).

We have the majority of our translation code in TCL and only 10 sites that share (Unix links) Xlate, Tables and formats.

Our testing involves sending a weeks worth of production messages and verifying that the output of the ‘new’ is identical to the output of the ‘old’ and that there are no errors in the sites.