EPC - 802

Date : 26 February 2007

EPC802 Highlights

EPC802 delivers enhancements and corrections primarily to the shipped set of LANSA for the Web weblets. 

EPC802 is the first stage in a series of updates that improve the performance of LANSA's Web Application Modules (WAMs).

A core set of weblets, including the grid, standard layouts and default visualizations, has been revamped or replaced. The performance of all of these new or amended weblets has been greatly improved. 

WARNING!

EPC 802 introduces improvements in the way CSS stylesheets and JavaScript files are handled. If your WAM layouts use the LANSA supplied std_style and std_script weblets, then you should experience no problems after installing this EPC. If you have created your own style and script weblets that do not call the standard weblets, then you may have problems after installing this EPC. In this case, you should make the modifications detailed below before applying this EPC.  

Script

Std_script.xsl has changed in a number of ways.  It loads a new JavaScript file (std_script_v2.js) as well as the original (std_script.js) and it generates a number of JavaScript variables that are used by other weblets to improve performance.

If your custom script weblet currently calls std_script, then you will get this new functionality automatically. If it doesn’t, then it is likely that you have implemented the original std_script functionality yourself. We recommend that you remove this code and replace it with a call to the script template in std_script:


   <xsl:import href="std_script.xsl" />

   <xsl:template name="my_script">
      <xsl:call-template name="script">
         <xsl:with-param name="javascript_files"/>
         <xsl:with-param name="trap_script_errors"/>
      </xsl:call-template>
            
      <!-- Custom script functionality here -->
   </xsl:template>


Notice the new javascript_files property. If the purpose of your custom script weblet is to load some extra JavaScript files, you may be able to use this new property and avoid the need for the custom weblet. See the documentation for more details.

Be careful with the template name. If you named the template of your custom weblet “script”, then you will need to rename it to avoid an infinite loop. You will then need to update your layouts to make sure they call the new name (otherwise they will call “script” in std_script.xsl bypassing your custom code).

Style

The std_style.css/std_style_base.css mechanism used prior to EPC802 is no longer used. This mechanism allowed for localization by placing all the required styles in std_style_base.css and locale specific styles in std_style.css. Std_style.css also contained an @import instruction to load std_style_base.css. Locale specific versions of std_style.css (such as std_style_jpn.css) could be created, each one importing std_style_base.css and then adding it’s locale specific styles.

The new mechanism consists of a single std_style.css file which the style weblet always loads first and a locale specific overlay (std_style_jpn.css) which the style weblet then loads is required. In other words, instead of linking CSS files together with @import instructions, the style weblet takes care of loading the CSS files required in the right order.

The new std_style_v2.xsl weblet extends this mechanism further providing a number of properties for specifying extra CSS files to load. The std_style weblet is deprecated but has been modified internally to map the old properties into the new mechanism, ensuring backwards compatibility.

If you have created your own CSS file and supplied it to the std_style weblet via the relative_css_link_filename property, then your application should continue to work without problem after installing this EPC. If you have created a custom style weblet that does not call std_style.xsl, then you may experience problems after installing this EPC.

As with the script weblet, it is likely that you have implemented the original std_style functionality yourself. We recommend that you remove this code and replace it with a call to the style template in std_style_v2.xsl:

   <xsl:template name="my_style">
      <xsl:call-template name="style">
         <xsl:param name="theme_css_filename"/>
         <xsl:param name="css_files"/>
      </xsl:call-template>

      <!-- Custom style functionality here -->
   </xsl:template>

Be careful with the template name. If you named the template of your custom weblet “style” then you will need to rename it to avoid an infinite loop. You will then need to update your layouts to make sure they call the new name (otherwise they will call “style” in std_style_v2.xsl bypassing your custom code).

Product Visual LANSA and LANSA for iSeries
Version 11.3
Pre-Requisite Details EPC800
Related Products LANSA for the Web
Full Distribution In Next Cumulative EPC or next version
Special Notes Requires EPC801 for WAM development and IIS web serving.

All Version 11.3 Visual LANSA EPCs include updates that must be applied to Windows and iSeries systems (Independent Visual LANSA development environments only require the Windows updates). Failure to upgrade both sides of a development environment will render the Host Monitor and Super Server applications inoperable. Attempting to use the Host Monitor and Super Server applications without having applied the EPC to both sides of a development environment will generate an EPC mismatch error.

Make a full backup of your LANSA environment on each platform to which this EPC will be applied.

Compatibility Notes To avoid object versioning issues on any target LANSA runtime environment after applying this EPC to your LANSA development environment (Windows and iSeries), you must also apply this EPC to the target LANSA runtime environment before deploying any objects built and compiled at this EPC level. This ensures that all required runtime routines are present in the target runtime environment to support any new or altered facilities introduced by the EPC. Failure to apply this EPC to such target environments before deploying any objects built and compiled at this EPC level will produce unpredictable results at runtime.
iSeries Specific Special Notes The iSeries instructions are expedited procedures that assume a sound knowledge of OS/400.

You should use a user profile that is QSECOFR, part of the QSECOFR group, or, has *ALLOBJ and *SECADM special authorities.

You must end the web server and run the LANSA for the Web cleanup program before applying this EPC.

You must end the Listener and Host Monitor if active.

You must end the LANSA Integrator server if it has been used with the LANSA system to be updated.

User Actions Import the standard weblets into your Web enabled RDMLX partitions: 
  • On Windows, the imports will be automatically performed if the database is started. If your database is not started, the imports will not complete and must be performed manually using *Limport from the \lansa\imports directories listed in the Windows Components list of Affected Objects. On completion, check your EPC log in Help -> Product Information to see if the imports have completed.
  • On iSeries, import the WEBLETS export save file found in the LANSA program library

If you will be serving very large lists using LANSA for the Web, you need to set appropriate timeouts accordingly:

  1. Response timeout (LANSA for the Web Administrator - Data/Application server configuration)
  2. IBM HTTP server (powered by Apache) TimeOut directive.
Document Updates Updates to these guides are provided:
  • lansa012.chm Visual LANSA User Guide
  • lansa087.chm Web Application Modules (WAMs)
The guides updated by EPC are only placed in the default LANSA documentation location as installed with Visual LANSA. This default location is ...\x_win95\x_lansa\execute\eng directory. If you installed the LANSA documentation (default folder ...\lansadoc\) from the LANSA Windows CD-ROM, you should manually copy the updated guides to those folders.
Hotfixes

The following Hotfixes will be replaced by this EPC:

Windows:
iSeries:
If you have applied a hotfix to your environment that is not listed above, contact your local LANSA vendor for instructions before applying the EPC.

Instructions to install the EPC

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

  1. Download EPC802.EXE file from the Web site or email.
  2. Unzip (double click) EPC802.EXE. These files will be extracted:

Instructions provided for:

Yes LANSA for iSeries
YesiSeries Web Server (multi-tier)
Yes Visual LANSA

 

Detailed changes

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

Affected objects

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

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

Install Instructions

Instructions for installing on iSeries

  1. These instructions have been abridged for experienced LANSA users. If you need further assistance to install the EPC, full instructions are available in the Technical Resources of the LANSA website, www.lansa.com.
  2. Recommend a backup be done of all the LANSA folders, system libraries and ALL the LANSA IFS objects (LANSA_pgmlib/x_lansa) before applying this EPC
  3. You need exclusive use of the LANSA system before applying the EPC. To check for active users refer to Appendix C How to check for Active Users in the LANSA Online documentation for instructions.
  4. End the Listener, Host Monitor and web server for the LANSA system and run the LANSA for the Web cleanup program.
  5. Move the unzipped file EPC802 to a shared folders on the iSeries.
  6. Use the XFLRTOSAVF command to convert the folder to a save file (LANSA program library must be on your library list) - press F4 for command details. A save file will be created by this command.
  7. You now have a save file.
  8. Sign on as a user profile that is QSECOFR, part of the QSECOFR group, or, has *ALLOBJ and *SECADM special authorities.
  9. Use the RSTOBJ command to restore all objects from library QTEMP into library QTEMP, eg.
    RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(<save file name>) RSTLIB(QTEMP)
  10. Display your current library list. If QTEMP is not shown, add it to your library list by using the ADDLIBLE (add library list entry) command.
  11. Install the EPC using the command:
    LOADEPC802 PGMLIB(<pgmlib>) COMLIB(<comlib>)
    <pgmlib> is the name of the LANSA program library, often DC@PGMLIB but it may be different on your system.
    <comlib> is the name of the LANSA Communications library, often DC@COMLIB but it may different on your system.
  12. Save and then delete the backout library (iiiEPCnn where iii = 1st three characters of the LANSA pgm library and nn is sequence number) created by the install. The contents of the library may be used to backout this EPC and return your system to its previous state.
  13. Sign off and then on again before commencing the next installation, eg:
  14. Import the standard weblets into your RDMLX partitions from the save file found in the LANSA program library.

  15. The import job TSPDEF will be submitted by this EPC load 

Special Instructions for users of iSeries web server (multi-tier)

To apply EPC802 on the Web Server tier of your LANSA for the Web system, follow these steps:

  1. End the web server and run the LANSA for the Web cleanup program. Refer to 13.5.6 Clean Up Systems in the LANSA Online documentation for cleanup instructions.
  2. If you haven't installed or upgraded LANSA for the Web on the Web Server, do so before proceeding with step 2.
  3. Restore the EPC objects into QTEMP (Perform the same steps you used to restore the objects in your LANSA for the Web application/data server system).
  4. 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.
  5. Install the EPC for the Web Server by using the command:

    LOADE802MT ADMLIB(<adminlib>) COMLIB(<comlib>)
    where <admin> is the name of the LANSA for Web Administration library.
    where <comlib> is the name of the LANSA Com/Share library. This is often DC@COMLIB but it may different on your system
  6. Press enter to continue processing.
  7. Save, and then delete, the backout library (iiiEPCMBnn where iii = 1st three characters of the LANSA pgm library and nn is sequence number) created by the install. The contents of this library may be used to backout this EPC and return your system to its previous state.
  8. Sign off and sign on again if you want to run the configuration program.

Instructions for installing on Windows

  1. Recommend that a backup be done of all LANSA folders and your LANSA database before applying this EPC.
  2. Stop using the LANSA development environment and stop all currently executing LANSA applications.
  3. Double-click on EPC802w.exe.
  4. Select the "Setup" button or "Cancel" if you do not want to proceed.
  5. If you have multiple configurations installed, Select the configuration to which the EPC is to be applied.
  6. If you are prompted to reboot your pc - please reboot.
  7. To view details of the installed EPCs:
    1. sign into LANSA
    2. view the Help menu
    3. Product Information option
    4. then select the Installation Details tab
    5. expand the Installation/ EPC Summary
    6. review the last entries

© 2007 LANSA