If you are upgrading LANSA Composer from an earlier version, you must upgrade first to version 7.0 and then to version 8.0. Upgrading directly from versions earlier than 7.0 to version 8.0 is not supported.
Upgrading LANSA Composer will not replace your current version of JTOPEN. This must be done manually.
As with any upgrade, before proceeding with the upgrade, you must make a full backup of the LANSA Composer Windows server installation and the database that it uses. You should also run the LANSA Composer Database Housekeeping task to clean up, maintain, and reorganize the LANSA Composer database.
You should note that the requirement for a 64-bit JVM in version 8.0 is changed from version 5.0, which required a 32-bit JVM. Refer to LANSA Composer Requirements.
| Do not proceed with the upgrade until you have considered the following. |
Custom additions or alterations to the files in the previous version's installation directories will be lost as a result of running the upgrade procedure.
To avoid failure of your LANSA Composer solutions in the upgraded system, you must save custom additions or alterations to the files in the LANSA Composer installation directories so you can re-apply the customizations to the new version 8.0 installation. The easiest way to do this is to make a full copy of the LANSA Composer Server program files tree before beginning the upgrade. For example:
C:\Program Files (x86)\LANSA\LANSA Composer Server
To ensure you can make a complete copy without contention, make sure that the listener and JSM services are stopped before making the copy.
This saved image will ensure that you have a copy of any customized files for easy restoration if required. We recommend making this copy anyway, even if you believe that you have not made any custom additions or alterations to the files in the LANSA Composer installation directories.
The following are examples of the types of customizations and additions that you need to consider:
- LANSA Communications Administrator entries that you may have created to permit your LANSA Composer solutions to communicate with other LANSA applications or other LANSA Composer installations, especially those on separate or remote server systems.
Typically such entries would be associated with LANSA system configurations used in LANSA Composer solutions with the CALL_FUNCTION or COMPOSER_RUN activities.
You can use the LANSA Communications Administrator program to identify any such entries. - Custom LANSA functions that are called by your LANSA Composer solutions using the CALL_FUNCTION activity.
The affected files would usually consist of one or more DLL files in the partition-execute directory (typically .\X_WIN95\X_LANSA\X_LIC\Execute).
(Recommended practice for recent LANSA Composer solutions would be to call such functions in a separate LANSA environment. However, especially in earlier versions of LANSA Composer, you may have developed solutions that used functions deployed to the LANSA Composer installation directories.) - The activity processors for custom activities.
The affected files would usually consist of one or more DLL files in the partition-execute directory (typically .\X_WIN95\X_LANSA\X_LIC\Execute). - Custom LANSA Integrator (JSM) solutions used with LANSA Composer.
Such solutions might include ones built using the LANSA Integrator Studio "binding" wizards (for SOAP server and agent or for XML or JSON bindings).
The affected files would usually consist of one or more JAR files in the Bindings or JAR directories of the LANSA Integrator directory tree (typically .\Integrator\JSMInstance). Such solutions may also necessitate new entries in properties files in the Properties directory. - Changes to internal LANSA, web, and LANSA Integrator (JSM) configuration files. Normally such changes would be made only in exceptional circumstances upon the advice of LANSA Support.
You do not need to identify software patches and hotfixes to prior versions of LANSA Composer that you obtained from LANSA Support as these are, where applicable, included in this version of LANSA Composer. Nor do you need to identify the JAR files for transformation maps as these will automatically be re-deployed to the new installation. MFX files for Transformation Maps executed through MapForce Server are typically not affected, as these are not usually stored in the LANSA Composer installation program directory tree.
When you are ready to proceed with the upgrade, continue with Start the Installation Program.