Upgrade Plan Notes
These notes refer to the reference numbers in the table in Complete your Upgrade Plan.
Installation Paths Notes
1. New version (5.0)
The new installation path must be different to the existing installation path for the version 4.0 LANSA Composer system. This is very important.
2. Existing version (4.0)
In the Setup the Local Database step you will need to specify the existing installation path down to the partition folder. That is to say, the path will usually end with x_win95\x_lansa\x_lic.
Database Notes
It is very important that you specify the database details during the installation that identify your LANSA Composer version 4.0 database. If you don't know these details, you can find them by opening the file in a text editor, such as notepad.exe. Look for lines similar to the following:
dbid=COMPOSER
dbut=MSSQLS
Disregard any lines that begin with a semi-colon (;) as these are comments and are not effective.
3. DBMS Type
You can determine the existing version 4.0's DBMS (database management system) type by referring to the line beginning in the file described above). It is very important that you specify the same DBMS type for the new version 5.0 installation.
4. Data Source Name
You can determine version 4.0's Data source name by referring to the line beginning in the file described above). It is recommended that you use the same Data source name for the new version 5.0 installation.
5. Server
With the Data Source Name (from point 4), open the DSN in the program to find the name of the database server. It is very important that you specify the same database server for the new version 5.0 installation.
6. Database name
With the Data Source Name, open the DSN in the program (from point 5) to discover the database name. It is very important that you specify the same database name for the new version 5.0 installation.
Web Notes
7. Is the active IIS plug-in installed in the version 4.0 installation path?
Depending on your response to this question, you may need to carry out further steps as described below.
First you must determine the location of your LANSA for the Web IIS plug-in:
a. Start the Internet Information Services (IIS) Manager.
b. Open the ISAPI Filters feature.
c. Locate the ISAPI Filter with the name 'lansaweb'.
- If there is no such ISAPI Filter, then select the option in this item in the Upgrade Plan. No further action is required.
- If there is an ISAPI filter, examine the executable file path associated with it. The path will usually end with something similar to:
If the path is a child of the LANSA Composer Version 4.0 installation path, then go to Is LANSA Composer the Only Web Application being served by the Active IIS Plug-in? to determine which of the options to select.
If the path is not a child of the LANSA Composer Version 4.0 installation, select the option in your Upgrade Plan. No further action is required at this time, however you may need to follow the instructions in Configure IIS to Serve the LANSA Composer Web Components when you have completed the installation.
8. JSM Virtual Folder
You should use the same JSM Virtual Folder name that you used for the LANSA Composer version 4.0 installation. You can determine the existing system's JSM Virtual Folder name by opening the and locating the folder in the web site that refers to the folder in the existing version 4.0 LANSA Composer installation. The default name used by prior LANSA Composer installations was .
Communication Ports Notes
It is recommended that you use the same port numbers that you used for the LANSA Composer version 4.0 installation.
9. Listener port number
If you don't know the listener port number used for the existing installation, you can discover it by opening the file in a text editor, such as notepad.exe. The file can be found in the directory of the existing LANSA Composer Version 4.0 installation path.
10. JSM Server port number
If you don't know the JSM port numbers used for the existing installation, you can discover them by opening the file in a text editor, such as notepad.exe. The file can be found in the directory of the existing LANSA Composer Version 4.0 installation path.
Look for the occurrence (there may be more than one) of a line beginning tcp.port=, and make a note of the port number as the JSM Server port number. If such a line is not present, the default is 4560.
11. JSM Administrator port number
In the file, described in item 10, look for the occurrence (there may be more than one) of a line beginning console.tcp.port=, and make a note of the port number as the JSM Administrator port number. If such a line is not present, the default is 4561.
LANSA Composer Files Location Notes
12. Path (relative to the server)
To determine the path to the LANSA Composer Files location used in the existing version 4.0 installation, firstly determine the network path as described for item 13 below. Then translate that network path to the equivalent local path relative to the server on which LANSA Composer is installed.
13. Network path (relative to client)
To find the network path to the LANSA Composer Files location used in the existing version 4.0 installation, open the LANSA Composer version 4.0 client software, go to , and locate the setting.
14. Path is child of installation path?
If your existing LANSA Composer Files location is NOT a child directory of the LANSA Composer Version 4.0 installation path, then select the option for this item. No further action is required.
If your existing LANSA Composer Files location is a child directory of the LANSA Composer Version 4.0 installation path, then select for this item.
For example, if the existing LANSA Composer version 4.0 is installed at:
and your existing LANSA Composer Files location is at then your answer is .
If , then you have two options to consider:
- Proceed, using the existing LANSA Composer Files location.
When you come to the post-installation task Remove LANSA Composer Version 4.0, you should make sure that you remove all the contents of the Version 4.0 installation directory except the directory that is the LANSA Composer Files location. You should not remove the entire Version 4.0 installation directory as this will remove the LANSA Composer Files location as well.
- Choose a new LANSA Composer File location for the Version 5.0 installation.
We recommend that you choose a location that is not in the (or equivalent) tree.
You may not wish to use a new location if your existing solutions contain hard-coded references to the LANSA Composer Files location or if other applications also use the same folders or files.
15. Customizations
If you have made custom additions or alterations to the files in the version 4.0 installation directories, you should identify them so that you can re-apply the customizations to the new version 5.0 installation. Such changes might include:
- 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 used in LANSA Composer solutions with the CALL_FUNCTION or COMPOSER_RUN activities.
You can use the 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 ).
(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 ).
- 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 or directories of the LANSA Integrator directory tree (typically ). Such solutions may also necessitate new entries in properties files in the 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 version 4.0 that you obtained from LANSA Support as these are, where applicable, included in LANSA Composer version 5.0. Nor do you need to identify the JAR files for transformation maps as these will automatically be re-deployed to the new installation.
16. Licenses
Before proceeding with your upgrade, you must first request new LANSA Composer server licenses. For more information refer to Appendix B. License LANSA Composer.