EPC - 739

Date : 5 Jan 2005

Description

EPC739 contains updates to iSeries and Windows components of LANSA Integrator.

The LANSA Integrator Guide has been updated for this EPC.

View Installation instructions

EPC739 includes these changes:

EPC739 supersedes EPC737, EPC722, EPC716, EPC695 and EPC665 which included these changes:

List of affected objects

iSeries and Windows Components:

iSeries only Components:

*JSMLIB = LANSA Integrator Program Library, *PGMLIB = LANSA Program Library

Windows only Components:

Instructions provided for:

Instructions to install the EPC 

EPC739 includes software to be installed on an iSeries machine or Windows machine. These instructions describe the installation and use of all delivered items. 

1. Download EPC739.EXE file from Web site or email.
2. Unzip (double click) EPC739.EXE. These files will be extracted:
   • this document, EPC739.htm
   • EPC739 - iSeries Save file
   • LI_EPC739.exe - Windows install executable
   • UA_EPC739.exe - Independent User Agent install executable
   • RFI_EPC739.exe - RFI install executable
   • LANSA093.chm - updated version of the LANSA Integrator Guide
   • itmpl400 - iSeries import save file
   • itmplwin - Windows LIMPORT zip file

Instructions for installing on iSeries

1. End the JSM server to be upgraded before installing EPC739.
2. The upgrade process will not be able to replace files that have the READONLY attribute set on. Ensure the JSM instance jar directory has no readonly files by using the OS/400 command CHGATR e.g. CHGATR OBJ('/jsm/instance/jar') ATR(*READONLY) VALUE(*NO) SUBTREE(*ALL)
3. Make a backup of the JSM directory from the iSeries. The current JSM directory will also be saved in the backout library DC@EC739.

   Note that the LANSA supplied source files QCLSRC, QCMDSRC, QDDSSRC and QRPGLESRC are replaced by this EPC.

   Note that if you have added or updated any entries in the studio project <studio-project id="20000000-000000" name="lansa"> section of any of the property files these will be removed during the upgrade. It is suggested that you place your own entries in a separate studio project section prior to upgrade.  

4. EPC739 must be extracted onto a Windows machine then uploaded onto the iSeries server.

For iSeries shared folders:

• in Explorer, map to the shared folder drive
• create a folder named EPC739
• copy unzipped file EPC739 to folder EPC739

5. If your network file system is not supporting iSeries shared folders, use FTP via TCP/IP and perform the following steps:

• logon to the iSeries and create folder EPC739
• open a DOS session on the PC
• change to the directory where the downloaded and unzipped files are located
• sign on to FTP site - FTP XXXXXXXX (where XXXXXXXX is the name of iSeries system or TCP/IP address)
• enter your iSeries user id and password
• to send as a binary file : enter command bin
• change to QDLS file system : enter command cd /QDLS
• change to the folder EPC739 : enter command cd EPC739
• to send the downloaded file to the iSeries : enter command put EPC739
• to exit : enter command quit

6. Use XFLRTOSAVF command to convert the folder to a save file format (LANSA program library must be on your library list) - press F4 for command details. Save file EPC739 will be created by this command.
7. Sign on as a user profile that is QSECOFR, part of the QSECOFR group, or, has *ALLOBJ and *SECADM special authorities.

NOTE: Check the OS/400 system value QFRCCVNRST. If QFRCCVNRST is set to 0, you must use FRCOBJCVN(*YES) on the RSTOBJ command.

8. Use the OS/400 RSTOBJ (restore object) command to restore all objects from library DC@EC739 into library QTEMP.

For a save file you will use the following command:
RSTOBJ OBJ(*ALL) SAVLIB(DC@EC739) DEV(*SAVF) SAVF(EPC739) RSTLIB(QTEMP)

9. Display your current library list. If QTEMP is not shown, then add it to your library list using the ADDLIBLE (add library list entry) command.
10. Install the EPC using the command:
    
    LOADEPC739 JSMLIB(<jsmlib>)
    Where <jsmlib> is the name of the LANSA Integrator JSM library. This is often JSMLIB but it may be different on your system.
    
11. After entering the library name, press enter. The LANSA Integrator instance path, LANSA object owner and LANSA program library will be displayed. Leave these defaults.
12. Press enter to continue processing.
13. Save and then delete the backout library (LANSAEC739) created by the install. The contents of the library may be used to back out this EPC and return your system to its previous state.
14. To install the EPC on another LANSA system, sign off and then on again before commencing the next installation.

Instructions for installing on Windows (including Integrator Desktop Applications)

1. End the JSM server to be upgraded before installing EPC739.
2. Make a backup of the Integrator directory from Windows.
   Note that if you have added or updated any entries in the studio project <studio-project id="20000000-000000" name="lansa"> section of any of the property files these will be removed during the upgrade. It is suggested that you place your own entries in a separate studio project section prior to upgrade.  
3. Unzip (double click) LI_EPC739.exe to start the upgrade of LANSA Integrator on Windows. 

   The first time LI_EPC739.exe is run it will create a folder called Integrator_PreEPC739 on the same level as the Integrator folder. This will act as a backup of the current Integrator install. Existing objects for previous tools can then be restored to the new Studio structure. Note that if the folder Integrator_PreEPC739 already exists no backup is made. 

   NOTE: Please view the 'Additional Install Notes' section in this document for important post-installation/upgrade checks.

4. If upgrading an independent User Agent install, uninstall the existing User Agent first. This can be done in one of 2 ways: 
      1. Remove it using Add/Remove programs from the control panel. 
      2. Start the install (see below) and it will automatically prompt you to remove any existing User Agent installations.
   Then unzip (double click) UA_EPC739.exe to start the installation of the User Agent.

   You might want to do a backup of your current independent User Agent install before you start the upgrade process.

5. If upgrading an independent RFI install, uninstall the existing RFI first. This can be done in one of 2 ways: 
      1. Remove it using Add/Remove programs from the control panel. 
      2. Start the install (see below) and it will automatically prompt you to remove any existing User Agent installations.
   Then unzip (double click) RFI_EPC739.exe to start the installation of RFI.

   You might want to do a backup of your current independent RFI install before you start the upgrade process.

6. This EPC provides a new documentation file LANSA093.chm. Please be sure that you update all copies of LANSA093.chm on your system or server. For example, if you installed the LANSA documentation (default folder ...\lansadoc\) from the LANSA Encyclopedia CD-ROM, then you should manually copy the updated file to this folder.

Optional Install of Integrator Templates (previously provided with EPC716)

1. You may optionally import two new templates JSMSKEL and BBJSMCMD and RDML function SET218B. These are provided for use in the updated Integrator tutorials in the shipped Integrator Guide. 
2. Instructions for installing on iSeries:

   Upload itmpl400 file onto the iSeries server as for point 3. in the Instructions for installing on iSeries.
   Use XFLRTOSAVF command to create a save file.
   Import this save file into the required LANSA system and partition.

3. Instructions for installing on Windows:

   Unzip itmplwin.zip into a directory
   Import from this directory  into the required Visual LANSA system and partition.

    

Additional Install Notes (not required if EPC695 previously installed)

1. The STRJSM program should be checked and recompiled as there is now an additional parameter TIMEZONE, which is passed to the RUNJSM program. If using the STRJSM command, the time zone defaults to a value of *DEFAULT. The default time zone is defined in the JSMMGRDTA data area. If the default value is blank then time zone GMT is used. A custom time zone such as GMT+10:00 does not include daylight savings time. The STRJSM command used in any CL source should be checked for the additional parameter.
2. If User Exit programs JSMADMEXT, JSMDRTEXT, JSMLSAEXT and JSMPXYEXT are used they should be checked and recompiled. Samples are provided in file QCLSRC.
3. When the JSM instance starts it will process the files in the upgrade directory and then end. Check standard output for upgrade messages. 
   On the iSeries platform the output will be in a spool file in JSM output queue.
   On the Windows platform the output will be in the file STDOUT.TXT in the instance directory.
   

   An example of the upgrade messages (not complete) :

   Upgrade JSM instance : /jsm/instance
   -
   Upgrade properties file : manager.properties
   Properties file upgraded
   -
   Upgrade properties file : service.properties
   Properties file upgraded
   -
   -
   Upgrade properties file : XMLQueueService.properties
   Properties file upgraded
   -
   Upgrade completed

   Remove upgrade files
   -
   Delete file : /devjsm/instance/upgrade/mailcap.txt
   -
   Delete file : /devjsm/instance/upgrade/integrator-feature.txt
   -
   -
   Delete upgrade directory
   -
   Removal completed

4. After installing/upgrading LANSA Integrator, you may need to delete all the obsolete jar files manually.   The upgrade will attempt to delete the obsolete jar files itself, however locks on files may prevent these files from being removed. As a result you should verify that the following jar files do not exist in your JAR folder.

5. After the upgrade has completed it is important to review the files and make some manual adjustments.

   All the properties files will contain Integrator Studio sections.
   
   The manager.properties file has also been shipped with a "user-override" section, it is recommended to add your modifications to this
   section.

   #!<studio-project id="20030101-000000" name="user-override">
   #
   tcp.port=4560
   tcp.backlog=20
   tcp.interface=*all
   #
   console.tcp.port=4561
   console.tcp.backlog=5
   console.tcp.interface=*all
   #
   # trace.manager=*yes
   # trace.client.address=*all
   #
   #!</studio-project>

   All the properties files will contain an "unassigned" section. This section contains lines that did not belong to a section.
   Review the unassigned section for possible configuration entries. Normally this section just contains # comments and the whole section can be deleted.

   #!<studio-project id="00000000-000000" name="unassigned">
   #
   # Move these entries to a new or existing studio-project section.
   # Delete this unassigned section.
   #
   #
   #!</studio-project>

   After reviewing the files, start the JSM instance again and the instance will be ready.

6. PKI Editor
   The PKI Editor is available for use when using the secure mime feature when sending and receiving e-mails using the SMTP mail, POP3 mail and EDI-INT (AS2) services. This is only available if the secure mime jar files are installed. These jar files are not shipped with LANSA Integrator as these files relate to Public Key encryption which must be purchased separately from Phaos Technology Corporation to support secure mime (SMIME). In particular, the software that needs to be purchased is:
   • Phaos Security Engine
   • Phaos CMS
   • Phaos S/MIME 

   Please refer to the Phaos Technology Corporation Web site for more information.

© 2004 LANSA