Integration Toolkit Manual Upgrade Steps v2.2

Upgrade Procedure Steps

Upgrading an existing instance of PIT 1.0 to the latest version requires the following manual and automated steps:

1. Save existing copies of the following Integration Toolkit customizable stubs/modules:
   • IIFWDCUST
   • IIRTNCUST (Including any duplicated instances of this module that might have been created in the field)
2. Save existing copies of the following Integration Toolkit data files:
   • IICONFIGP
   • IIMACROS
   • IIFWDMSGQ
   • IIFWDERRQ
   • IIDICGRP
   • IIDICREF
   • IIDICTNRY
   • IITRAN
   • IIMACDAT
3. DO NOT SAVE existing copies of the following Integration Toolkit files - new versions of these "static" data files will be delivered by the ASDU and you must use the new versions:
   • TSTRTYP
   • TSTRPUB
   • TSXELEM
   • TSXATTR
   • TSXTAG
4. Use the ASDU to install the Integration Toolkit v2.2 product as described in the Integration Toolkit installation pageas if it was a standard fresh installation. The ASDU will ask for your OMNI libraries, where the toolkit will then be installed.
5. Copy the data from each of the toolkit files saved in a previous step into their equivalent empty files installed for v2.2.
   NOTE: the file record formats have not been changed for v2.2.
   NOTE: A new callable macro template refresh API (IIMACRFSH) may be used to retrieve and locally store all the customers forward and return macro template definitions in the PIT macro database tables (ie. IIMACROS, IIDICREF, IIDICTNRY, IIDICGRP). It is recommended that this API be called to restore (refresh) the local macro template defintions rather than copying (restoring) the data from the corresponding macro files saved in the previous step.
6. Examine the two "new" v2.2 versions of the installed customizable stubs in your OMNI deliverable source library in file IIRPGSRC. Re-apply any custom logic from the older versions saved in a previous step, as described below:  
   • IIFWDCUST - This module has not changed for v2.2 - you can safely overlay or directly use earlier saved versions of this module.
   • IIRTNCUST - This module has not changed for v2.2 - you can safely overlay or directly use earlier saved versions of this module.