EPC - 805

Date : 26 March 2007

EPC805 Highlights

EPC805 delivers enhancements and corrections to LANSA Integrator.  The following are some of the most notable items:

Refer to Detailed changes for more information about the changes delivered in this EPC.

ProductLANSA Integrator
Version11 SP4
Pre-Requisite Details Java 1.4
LANSA Integrator installed from CU1 CD (EPC752) or later (iSeries)
LANSA Integrator installed from CU3 CD (EPC772) or later (Windows)
Windows: supported versions of Windows as documented on our web-site.  In particular refer to the web-site for the latest information concerning support for Microsoft Windows Vista.
iSeries: i5/OS or OS/400 at a release level supported by IBM - at time of writing, the earliest supported release was V5R2M0.
Related ProductsLANSA for iSeries and/or Visual LANSA
Full Distribution InV12.0
Special NotesIf you are running custom services (services not provided with the LANSA Integrator product shipment), then you should re-test such services after applying the EPC.  If your custom services do not work after applying the EPC, then you may need to re-compile the .class object for the services.
Document UpdatesAn updated version of the LANSA Integrator Guide is included.

Description

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

Instructions to install the EPC

EPC805 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 EPC805.EXE file from Web site or email.
  2. Unzip (double click) EPC805.EXE. These files will be extracted:

Instructions provided for:

YesLANSA Integrator on iSeries
YesLANSA Integrator on Windows
NoLANSA Integrator on Unix or Linux
YesAdditional Install notes

 

Detailed changes

   EPC805 includes these changes    [Click here to Show table...]

Affected objects

   iSeries and Windows Components:    [Click here to Show table...]

   iSeries only Components:    [Click here to Show table...]

   Windows Only Components:    [Click here to Show table...]

Instructions for installing on iSeries

  1. End the JSM server to be upgraded before installing EPC805.
  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 read only files by using the OS/400 command CHGATR e.g. CHGATR OBJ('/jsm/instance') 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.

    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. EPC805 must be extracted onto a Windows machine then uploaded onto the iSeries server.
    For iSeries shared folders:
  1. If your network file system is not supporting iSeries shared folders, use FTP via TCP/IP and perform the following steps:
  1. Use the 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 EPC805 will be created by this command.
  2. 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.

  1. Use the OS/400 RSTOBJ (restore object) command to restore all objects from library QTEMP into library QTEMP.

For a save file you will use the following command:

RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(EPC805) RSTLIB(QTEMP)
  1. 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.
  2. Install the EPC using the command:

    LOADEPC805 JSMLIB(<jsmlib>) PGMLIB(<LANSA_pgmlib>)

    Where <jsmlib> is the name of the LANSA Integrator JSM library. This is often JSMLIB but it may be different on your system.

    Where <LANSA_pgmlib> is LANSA program library name and is optional.  

  3. Press enter to continue processing.
  4. Save and then delete the backout library (iiiJEPC99 where iii = 1st three letters of your LANSA Integrator library and JEPC99 where 99 = is unique number) 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.

  5. To install the EPC on another LANSA system, sign off and then on again before commencing the next installation.

Additional Install Notes (iSeries)

  1. The STRJSM program should be checked and recompiled. A sample is provided in file QCLSRC.
  2. The exit programs JSMADMEXT, JSMDRTEXT, JSMLSAEXT and JSMPXYEXT should be checked and recompiled. Samples are provided in file QCLSRC.
  3. Please view the Additional Install Notes section in this document for important post-installation/upgrade checks.

Instructions for installing on Windows (including Integrator Desktop Applications)

  1. End the JSM server to be upgraded before installing EPC805.
  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) EPC805w.exe to start the upgrade of LANSA Integrator on Windows.
    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_EPC805.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 RFI installations.
    Then unzip (double click) RFI_EPC805.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.

Additional Install Notes (for Windows Server 2003 only)

In Windows Server 2003, a virtual directory must be created for LANSA Integrator (done automatically for other operating systems). Follow these steps to create it:

  1. In the Installing LANSA on Windows guide, locate the section Create a Virtual Directory for the IIS Plug-in in IIS. Although these steps are for the LANSA for the Web Plugin they can also be used for LANSA Integrator. 
  2. As you follow the steps in the Wizard you will need to replace the directory name and path with your own appropriate for LANSA Integrator.
  3. For Access Permissions select "Read" in addition to "Run scripts" and "Execute".

In Windows Server 2003, a Web Service Extension should be created for Integrator's virtual directory (ie; 'cgi-bin', 'cgi-bin-jsmdirect', etc.) for the user to run any CGI programs. Follow the steps below to set that up.

  1. Open the Internet Information Services Manager from Administrative Tools.
  2. Click 'Web Service Extensions'.
  3. Click 'Add a new Web service extension' from the Tasks in the Web Service Extensions window.
  4. In the 'New Web Service Extension' window, write an appropriate name for 'Extension name' and click the 'Add' button to select the 'Required files' for the extension. From the correct location for your Integrator configuration, select jsmdirect.exe, jsmproxy.exe, and jsmadmin.exe.
  5. Click 'OK'.

In Windows Server 2003, correct permission rights should be allocated to the Integrator's virtual directory for the group 'Users' so that dc_w29.txt and dc_w30.txt files can be changed from Integrator Studio. Follow the steps below to set that up.

  1. Open the Internet Information Services Manager from Administrative Tools.
  2. Select the appropriate virtual directory that has been created for your Integrator configuration (ie; 'cgi-bin', 'cgi-bin-jsmdirect', etc).
  3. Right click on the virtual directory entry, and click on 'Permissions' from the context menu.
  4. Select the group 'Users' from 'Group or user names'.
  5. Allow permission to 'Modify' and 'Write' for the group 'Users'.
  6. Click 'OK'.

Additional Install Notes (iSeries and windows)

  1. When the JSM instance starts it will process the files in the upgrade directory. If the upgrade is successful the JSM instance will restart else the instance will end. Check the file UPGRADE-LOG.txt in the JSM instance directory for upgrade messages.

    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
  2. 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. Use Studio to remove all unassigned sections from property files.

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

© 2007 LANSA