Important note for upgrading LANSA Composer version 2.0 where Hotfix 002 is not applied

Date:30 July 2010
Product/Release:LANSA Composer 2.0
Abstract:Important note if upgrading LANSA Composer version 2.0 and have NOT previously applied Hotfix 002
Submitted By:LANSA Technical Support

Description:

Hotfix 002 for LANSA Composer version 2.0 was supplied with the LANSA Composer installation media for version 2.0. Hotfix 002 for LANSA Composer version 2.0 introduced support for dynamic class loading for the transformation map Java classes.

The effects of this new behaviour included:

  • no need to restart JSM after preparing or deploying maps
  • maps prepared with different versions of MapForce can co-exist
  • no need to rebuild maps following a MapForce upgrade

The following applies to you ONLY if you are upgrading from LANSA Composer version 2.0 to version 3.0 and have NOT previously applied hotfix 002.

This enhanced behaviour is the default behaviour for LANSA Composer version 3.0. If you are upgrading from LANSA Composer version 2.0 and have NOT previously applied Hotfix 002, then you should complete the following steps to move the .jar files for your existing Transformation Maps to their new location. You can do this immediately BEFORE or immediately AFTER performing the upgrade to LANSA Composer version 3.0. (Although the example paths given below are formatted for an IBM i server, these instructions apply equally to a Windows server.)

  • Navigate to the JSM instance folder of the LANSA Integrator installation used by the LANSA Composer server, for example

    \\<iSeries>\IFS\LANSA_licpgmlib\jsm\instance
     
  • In that folder, create a new folder called 'composer', for example

    \\<iSeries>\IFS\LANSA_licpgmlib\jsm\instance\composer
     
  • In the new 'composer' folder, create a new folder and give it the same name as the LANSA partition in which LANSA Composer is installed, for example

    \\<iSeries>\IFS\LANSA_licpgmlib\jsm\instance\composer\LIC
     
  • In the new 'composer\<partition>' folder, create a new folder called 'map', for example

    \\<iSeries>\IFS\LANSA_licpgmlib\jsm\instance\composer\LIC\map
     
    Make sure that the security applying to the new folders is appropriate. For example, on an IBM i server, make sure that the LANSA Composer product owner profile (usually QOTHPRDOWN) owns the new folders and is explicitly granted all data and object authorities to the folders.
     
  • Navigate to the \jar folder in the JSM instance folder, for example

    \\<iSeries>\IFS\LANSA_licpgmlib\jsm\instance\jar
     
  • Identify all the .jar files in the \jar folder that implement Transformation Maps. They have names beginning with 'm', followed by thirty-two alphanumeric characters and the extension '.jar'. For example:

    m0B290A53F13346BAB28871DACB7C36FE.jar
     
  • Move all the identified Transformation Map .jar files to the .\composer\<partition>\map folder created above.
     
  • It is very important NOT to leave any Transformation Map .jar files in the \jar folder. If there are any Transformation Map .jar files in the \jar\pending folder, move them as well.
     
  • You will need to restart the JSM (LANSA Integrator) on the LANSA Composer server before the changes will take effect.