EPC - 853

Date : 7 May 2010

EPC853 Highlights

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

  • New Base64FileService
  • Added ClassLoader support to several "project-based" services for dynamic (on-demand) loading of generated Java implementation classes
  • Significant enhancements to PDFDocumentService and PDFSpooledFileService
  • more PDF formatting and functionality features
    • support for AFPDS format spooled files in PDFSpooledFileService
    • SSL support added to email services
  • A range of useability and functional enhancements to LI Studio
  • A range of incremental enhancements to supplied LI services
  • A variety of updates to latest versions of various Java libraries used in LI Studio and LI Service implementations.

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

ProductLANSA Integrator
Version12
Pre-Requisite DetailsJava: 1.4
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 V5R3M0.

The following PTFs must be applied before this EPC is applied:
  1. i5/OS Release / Required PTF
    • V5R3M0 = MF41354
    • V5R3M5 = MF41734
    • V5R4M0 = MF40520
    • V5R4M5 = MF42655
  2. Additional required PTFs for restoring Java programs created on V6R1 or later to an earlier release i5/OS Release / Required PTF
    • V5R3M0 = SI27297
    • V5R4M0 = SI27765
       
LANSA Integrator:

iSeries - installed from CU1 CD (EPC752) or later
Windows - LANSA Integrator V12

Associated LANSA system (if installed):

iSeries - V12 and EPC 851 or later.
Windows – V12
Related ProductsLANSA for iSeries or Visual LANSA
Full Distribution InN/A
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. Once the EPC is applied, you need to ensure that the version of the guide shipped with the EPC is placed in the default LANSA documentation location as installed with Visual LANSA. This default location is ...\x_win95\x_lansa\execute\eng directory. You should manually copy the guide to this folder, replacing the existing version of the LANSA Integrator guide.

Description

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

Instructions to install the EPC

EPC853 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 EPC853.EXE file from Web site or email.
  2. Unzip (double click) EPC853.EXE. These files will be extracted:
    • this document, EPC853.htm
    • EPC853 - iSeries Save file
    • EPC853w.exe - Windows install executable
    • RFI_EPC853.exe - RFI install executable
    • UA_EPC853.exe - Independent User Agent install executable
    • LANSA093.chm - updated version of the LANSA Integrator Guide

Instructions provided for

Detailed changes

CCS id.Description
0136043Add trace.fields and trace.passwords properties to manager.properties

Trace.fields enables tracing of LANSA field values in transport.txt. Trace.passwords enables tracing of command password keyword values, which are normally suprressed. These options provide for deeper diagnostic information when required.
0136045Trace SSL handshake during SSL PORT session

Provides enhanced diagnostic information in the LANSA Intgerator trace files relating to SSL connections.
0136167UserAgent does not use the last line in the .lih file if no CRLF terminator

This has been corrected in this version of LANSA Integrator.
0136347Update 3rd party jar files

Update the following jar files.
jsflook.jar - Version 2.3.0
jsmbcprov.jar - Version 1.4.1
jsmbcmail.jar - Version 1.4.1
jsmbcpg.jar - Version 1.4.1
jsmssh2.jar - Version 1.4.0
jsmpdf.jar - Version 2.1.4
Such updates keep LANSA Integrator services up-to-date with the most recent versions of 3rd party/open source Java libraries used by the services.
0136348Add a trace message to report if the body text list argument is null

This change gives additional diagnostic information for users of the SMTPMailService if body text is not provided.
0136405Add exponent and modulus to PKI information panels

Add RSA exponent and modulus to public key, private key and certificate information windows
0136477Provide new Base64FileService for base-64 encoding and decoding of file content

The Base64FileService provides commands that

1. allow the content of a nominated input file to be base-64 encoded and written to the nominated output file

2. allow the content of a nominated input file to be base-64 decoded and written to the nominated output file
0136563Add a trace active threads feature to JSM

This feature which is activated by the manager.properties trace.threads property traces information about all active threads to the file TRACE-THREADS.CSV in the instance directory.
To cause this tracing event to be done, select the Active services option of Studio or Console.
0136599Enhance Studio find Java compiler and runtime logic

Make Studio Java compile and runtime directory find locations more generic to handle the changed directory name for Java 6.0 Update 10
0136623Add 3D Look & Feel to LANSA Integrator Studio

This provides a more contemporary look and feel.
0136710Check that content handlers implement the expect interfaces

Check that a content handler implements the content hander interfaces and throw an error message instead of a class cast exception. This will improve problem resolution.
0136711Add a default NOOP operation to new SOAPServerWizard projects

The NOOP operation provides bot an example operation and a means to verify basic operation of the service.
0136796Include class name in JSM console exception log messages

This provides for better diagnostic information in the event of an error.
0136824Trace XML TransformerFactory class

Trace XML TransformerFactory class, this will help in problem resolving when a JDK might not be using the Apache Xalan class.
0136852Create the TraceViewer tool to view traces in a tree format

The TraceViewer tool allows service.txt and transport.txt to be viewed in a graphical tree format. The viewer can be accessed directly from LANSA Integrator Studio.
0136882Upgrade JCraft JSch to version 1.42

Such updates keep LANSA Integrator services up-to-date with the most recent versions of 3rd party/open source Java libraries used by the services.
0136899Add Verified Self Signed information to Certificate text view

Additional X509 certificate information is displayed when a certificate is viewed from LANSA Integrator Studio.
0136909Handle missing HTTP Content-Type property

This provides better support for HTTP servers that do not provide this information in the HTTP headers.
0137007Add anchor url support to image and a clickable region anchor element

Provides enhanced functionality for hyper-linked images in PDF documents created with the PDFDocumentService.
0137201Add more tracing and a debug feature to MultiPartStorageService

This provides greater daignostic information for users of this service.
0137216Create HTTPService InboundTextHandler

The InboundText handler can be used to receive text content from a HTTP client program.
0137233Refactor Packed and Zoned decimal formating

Refactor Packed and Zoned decimal formating to handle a wider variety of inputs from Excel documents, SQL databases and CSV data in related services. For example: .00 -.00
0137279Add support for SSL connection to POP3MailService and SMTPMailService

This enables these services to be used with mail servers that require clients to connect using SSL (secure sockets layer) for increased security.
0137447Upgrade Bouncy Castle to version 1.4.5

Such updates keep LANSA Integrator services up-to-date with the most recent versions of 3rd party/open source Java libraries used by the services.
0137448Upgrade JavaMail to version 1.4.3

Such updates keep LANSA Integrator services up-to-date with the most recent versions of 3rd party/open source Java libraries used by the services.
0137449Update iText to version 2.1.7

Such updates keep LANSA Integrator services up-to-date with the most recent versions of 3rd party/open source Java libraries used by the services.
0137534Allow working list fields to be excluded from WRITE cell data operation

A new EXCLUDE keyword to the WRITE command of the ExcelReadService allows specified working list fields to be excluded from the write.
0137681Add SVEXCLUDE keyword to SV services

Add the SVEXCLUDE keyword support to SV services. This allows working list fields to be excluded from the created data.
0137788
0137772
Do not allow HTTP protocol properties to override existing http keywords

If a custom HTTP client program sends user defined HTTP protocol properties, ie Server-Name, this HTTP property value will overide the Server-Name property send by the JSM BIF sent to the JSM service.
0137896Upgrade WS-Security ( 1.5.8 ) and XML-Security ( 1.4.3 ) jar files

Such updates keep LANSA Integrator services up-to-date with the most recent versions of 3rd party/open source Java libraries used by the services.
0137926Enhance XML bind services to load classes from specified jar file

This allows the xmlbinding jar to be placed in any directory. It no longer requires the jar file to be placed in the jar/pending and JSM rebooted
0137962Change PDFSpoolFileService code to handle changes to iText 2.0 and above

iText behaviour has changed and spaces around a new-line character are trimmed, this causes line indenting issues. Also include new encodings for the courier font. *COURIER1 is the same as COURIER and is codepage 1252. *COURIER2 is code page 1250. *COURIER3 is code page 1257.
0138003Enhance XMLParserService to SET node and attribute values

Enhance the XMLParserService to SET node and attribute values. Also allow the STORE command to save the current DOM object. This will allow changes to the DOM to be serialized to a file.
0138075Add socket timeout control to HTTP outbound services

Enhanced the SEND comamd WAIT keyword usage and add a new TIMEOUT keyword.
0138076Add author, subject and date attributes to PDFDocument annotation element

This allows the specified property values to become a part of the generated PDF document and visible to readers of the document.
0138392
0138355
Allow XML encoding to be specified on the WRITE command for XML binding services

%%DONE%%
0138421
0137944
Allow imported PDF pages to be rotated using an affine transform

Enhance the PDFDocumentService import element so imported PDF pages can be rotated using an affine transform
0138422Enhance SV services so decimal values from SQL source are formatted

Some versions of JDK 1.5 and 1.6 BigDecimal class return values in scientific notation instead of standard decimal notation. JDBC drivers using BigDecimal classes to hold column values are returning values in scientific notation. Decimal format logic has been added to convert scientific notation to decimal notation, this formatting is aggressive and trailing zeroes will be removed. Also NUMBERFORMAT support has been added to created SV content from SQL sources.
0138430
0138496
0139021
0139049
0140480
Cannot login to Unix FTP server, getting connection reset error

Some Unix FTP servers or intermediate firewalls cannot handle fragmented data writes.
Send FTP control command using a single socket write.
0138748Add SVROW and SVROWLIMIT support for SV READ command

This allows the programmer to specify the starting row and the number of rows to read from the SV data. SVROWLIMIT keywords support the following option ( *NONE | *LIST | *AVAILABLE | number )
0138959Add the ADD command to the ExelReadService

Provides new capabilities for writing Excel documents, including adding a formula or inserting an image and/or URL or cell hyperlink.
0139297Add Euro IANA encoding support to XML services

Add support for Euro IANA encodings

Cp1140 ebcdic-us-37+euro
Cp1141 ebcdic-de-273+euro
Cp1142 ebcdic-dk-277+euro ebcdic-no-277+euro
Cp1143 ebcdic-fi-278+euro ebcdic-se-278+euro
Cp1144 ebcdic-it-280+euro
Cp1145 ebcdic-es-284+euro
Cp1146 ebcdic-gb-285+euro
Cp1147 ebcdic-fr-297+euro
Cp1148 ebcdic-international-500+euro
Cp1149 ebcdic-is-871+euro
0139613Update XMLSchema to version 1.4.5

Such updates keep LANSA Integrator services up-to-date with the most recent versions of 3rd party/open source Java libraries used by the services.
0139639Allow SOAP Fault message to be saved using the FAULT keyword on the CALL

This provides greater capability for SOAPAgent client programs to handle SOAP faults relating to web-service calls.
0139680XMLSchema Viewer does not display base type and extension elements

The XMLSchema Viewer has been fixed to display base type and extension elements.
0140035Include page sizes when reading PDF document information

The PDFDocument READ command can optionally include PAGE sizes in the document information list.
0140420
0140403
Some FTP server return response code 235 for the PBSZ subcommand

Enhance the code so response code 200 and 235 are accepted as OK for the PBSZ and PROT subcommands. Provides better compatibility with a range of FTP servers.
0140545Allow PDFSpoolFileService to create pages in TIFF format

Add PAGETYPE, PAGES and SCALING keywords to control the type of PDF pages to be created from a spooled file. Use TIFF image pages for AFPS pages.
0140744HTTPINBOUNDQUERYSERVICE creating a query does not work

It was a possible to use the SET QUERY(*LIST) command to create a SQL query at the service end.
This has been fixed and the SET QUERY(*LIST) command now works.
0140802Add HTTP server

LANSA Integrator now provides an intregrated HTTP server which allows serving of static resources and the execution of custom Java classes for dynamic content.
0140807Add OCCURANCE keyword to the ZipService GET command

The OCCURANCE keyword only applies when ENTRY(*READ) and FILE keyword are specified.
By default all occurances of a file are written out.
If you only require the first or only occurance of the file to be written out, then use the keyword value *FIRST.
Using an occurance value of *FIRST improves the access time to read a single file from the archive.
0140808Add new special directories to JSM and Studio

Add new special directories bindings, schema, wsdl and www to JSM and Studio
0140811Enable MQ BIFs to use TERASPACE

%%DONE%%
0140812Change JSMDQGET and JSMDQPUT programs to match IBM data structures changes

The IBM changes are now handled correctly in LANSA Integrator data queue support.
0140813Enhance Studio text editor to read GZIPed compressed content

%%DONE%%
0140814Allow UserAgent work directory to be specified by jsf.workspace command property

%%DONE%%
0140816Improve HTTP key manager tracing

Provides better diagnostic information for easier problem resolution.
0140831
0140828
XMLBindWizard does not use the correct ns prefix when an empty ns uri is present

When an empty default namespace uri is present, the XMLBindWizard does not generate the correct namespace alias. This has been corrected.
0140888Improve null handling in JSON binding service

When a null property was received, a "null" string value was returned. The JSON binding process should have ignored the property with a null value.
0140995Enhance Studio to send project jar files to different folders

Studio project popup menu has a send menu item, this sends the selected file to a particular folder.

Studio has been enhanced to send binding wizard jar files to bindings folder and other jar files to jar pending folder.
0141149Imported PDF pages have an incorrect page rectangle postition

Some PDF pages created by other producst use a non zero page rectangle co-ordinate system.

When importing pages only use the page width and height.
0141185HTTPInboundQueryService needs to have the ability to change ResultSet mode

Some JDBC drivers do not support the ResultSet cursor readonly mode.
Add the RESULTSET(*READONLY|*UPDATEABLE) keyword to the SEND command to allow the ResultSet mode to be changed.
0141195
0141184
Handle JDK changes to BigDecimal class behaviour

From JDK 1.5, the BigDecimal toString method can produce a String value in exponent format.
Add code to convert and format decimal values into normal form
0141287
0141292
SQLService needs to have the ability to change ResultSet mode

Some JDBC drivers do not support the ResultSet cursor readonly mode.
Add the RESULTSET(*READONLY|*UPDATEABLE) keyword to the EXECUTE and META commands to allow the ResultSet mode to be changed.
0141316run clrjsm in batch

Integrator's Clear Trace can now be run in batch mode on Windows.

Batch mode:
clrjsm /batch will execute in batch and clear the trace files and the temp files
clrjsm /batch /trace will execute in batch and clear the trace files only
clrjsm /batch /temp will execute in batch and clear the temp files only
clrjsm /batch /trace /temp will execute in batch and clear the trace files and the temp files

Interactive mode:
clrjsm will default to clear the trace files and the temp files
clrjsm /trace will default to clear the trace files only
clrjsm /temp will default to clear the temp files only
clrjsm /trace /temp will default to clear the trace files and the temp files

Affected objects

Object NameFolderPlatform
jsm.jarLANSA Integrator Instance jar directoryAll
jsmas2.jarLANSA Integrator Instance jar directoryAll
jsmaxis.jarLANSA Integrator Instance jar directory - Axis 1.4 Nov 19 buildAll
jsmbcmail.jarLANSA Integrator Instance jar directory - Bouncy Castle 1.4.5All
jsmbcpg.jarLANSA Integrator Instance jar directory - Bouncy Castle 1.4.5All
jsmbcprov.jarLANSA Integrator Instance jar directory - Bouncy Castle 1.4.5All
jsmcomdisc.jarLANSA Integrator Instance jar directory - Axis commons-discovery 0.4All
jsmcomlog.jarLANSA Integrator Instance jar directory - Axis commons-logging 1.1All
jsmedimap.jarLANSA Integrator Instance jar directoryAll
jsmide.jarLANSA Integrator Instance jar directoryAll
jsmjaf.jarLANSA Integrator Instance jar directory - Java Activation Framework 1.1.1All
jsmjaxrpc.jarLANSA Integrator Instance jar directory - Axis JAXRPC 1.1All
jsmldap.jarLANSA Integrator Instance jar directory - Open LDAP 2008-03-01 buildAll
jsmlog4j.jarLANSA Integrator Instance jar directory - Axis Log4j 1.2.15All
jsmmail.jarLANSA Integrator Instance jar directory - Java Mail 1.4.3All
jsmnative.jarLANSA Integrator Instance jar directoryAll
jsmpdf.jarLANSA Integrator Instance jar directory - iText 2.1.7All
jsmpdfcjk.jarLANSA Integrator Instance jar directory - iText fontsAll
jsmrfi.jarLANSA Integrator Instance jar directoryAll
jsmsaaj.jarLANSA Integrator Instance jar directory - Axis SAAJ 1.2All
jsmscript.jarLANSA Integrator Instance jar directory - Rhino 1.6.7All
jsmserializer.jarLANSA Integrator Instance jar and endorsed directories - Xerces 2.7.0All
jsmservice.jarLANSA Integrator Instance jar directoryAll
jsmsoap.jarLANSA Integrator Instance jar directoryAll
jsmssh2.jarLANSA Integrator Instance jar directory - JSch 1.42All
jsmstax.jarLANSA Integrator Instance jar directory - Woodstox 3.2.4All
jsmstaxapi.jarLANSA Integrator Instance jar directory - Woodstox 1.0.1All
jsmutil.jarLANSA Integrator Instance jar directoryAll
jsmwsaddr.jarLANSA Integrator Instance jar directory - Axis WS-Addressing 1.0All
jsmwsdl4j.jarLANSA Integrator Instance jar directory - Axis WSDL4J 1.6.2All
jsmwssec.jarLANSA Integrator Instance jar directory - Axis WS-Security 1.5.8All
jsmxalan.jarLANSA Integrator Instance jar and endorsed directories - Xalan 2.7.0All
jsmxerces.jarLANSA Integrator Instance jar and endorsed directories - Xerces 2.8.1All
jsmxls.jarLANSA Integrator Instance jar directory - jXL 2.6.8All
jsmxmlapi.jarLANSA Integrator Instance jar and endorsed directories - Xerces 1.3.03All
jsmxmlsec.jarLANSA Integrator Instance jar directory - Axis XML-Security 1.4.3All
Object NameObject TypeLibrary
QCLSRC*PF*JSMLIB
QCMDSRC*PF*JSMLIB
QDDSSRC*PF*JSMLIB
QRPGLESRC*PF*JSMLIB
SFMFILTER*PF*JSMLIB
SFMFILTER1*LF*JSMLIB
SFMFILTER2*LF*JSMLIB
SFMFOLDER*PF*JSMLIB
SFMFOLDER1*LF*JSMLIB
SFMUSER*PF*JSMLIB
SFMUSER1*LF*JSMLIB
SFMUSER2*LF*JSMLIB
DC@D8700*DSPF*JSMLIB
DC@P8700*PGM*JSMLIB
JSM*DSPF*JSMLIB
JSM*MSGF*JSMLIB
JSM*MENU*JSMLIB
JSMMSGF*MSGF*JSMLIB
CHGJSMAUT*PGM*JSMLIB
CHGJSMDFT*PGM*JSMLIB
CHGJSMOWN*PGM*JSMLIB
CLRJSM*PGM*JSMLIB
CRTJSMSBS*PGM*JSMLIB
EDTJSMMGR*PGM*JSMLIB
EDTJSMSRV*PGM*JSMLIB
JSMADMIN*PGM*JSMLIB
JSMAUTH*PGM*JSMLIB
JSMBUILD*PGM*JSMLIB
JSMCHECK*PGM*JSMLIB
JSMCHGJOB*PGM*JSMLIB
JSMCHGUSER*PGM*JSMLIB
JSMCLEAR*PGM*JSMLIB
JSMDIRECT*PGM*JSMLIB
JSMDQGET*PGM*JSMLIB
JSMDQPUT*PGM*JSMLIB
JSMGETENV*PGM*JSMLIB
JSMGETPORT*PGM*JSMLIB
JSMLINK*PGM*JSMLIB
JSMMQDEPTH*PGM*JSMLIB
JSMMQGET*PGM*JSMLIB
JSMMQPUT*PGM*JSMLIB
JSMOWNER*PGM*JSMLIB
JSMPENDING*PGM*JSMLIB
JSMPROXY*PGM*JSMLIB
JSMTRCENV*PGM*JSMLIB
OPTJSM*PGM*JSMLIB
RUNJSM*PGM*JSMLIB
WRKJSM*PGM*JSMLIB
DCXS882X*SRVPGM*JSMLIB
DCXS883X*SRVPGM*JSMLIB
JSMDTAQ*SRVPGM*JSMLIB
JSMMGRSRV*SRVPGM*JSMLIB
JSMMSGQ*SRVPGM*JSMLIB
JSMRPGSRV*SRVPGM*JSMLIB
JSMUSRSPCE*SRVPGM*JSMLIB
LIBLSSRV*SRVPGM*JSMLIB
CHGJSMAUT*CMD*JSMLIB
CHGJSMDFT*CMD*JSMLIB
CHGJSMOWN*CMD*JSMLIB
CLRJSM*CMD*JSMLIB
CRTJSMSBS*CMD*JSMLIB
EDTJSMMGR*CMD*JSMLIB
EDTJSMSRV*CMD*JSMLIB
OPTJSM*CMD*JSMLIB
RUNJSM*CMD*JSMLIB
STRJSM*CMD*JSMLIB
WRKJSM*CMD*JSMLIB
JSMCLTDTA*DTAARA*JSMLIB
JSMDRTDTA*DTAARA*JSMLIB
JSMMGRDTA*DTAARA*JSMLIB

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

Object NameFolder
LANSA Integrator StudioIntegrator\Studio
LANSA Integrator User AgentIntegrator\UserAgent
LANSA Integrator Remote Function InvocationIntegrator\RFI
LANSA Integrator on WindowsIntegrator\JSMInstance
Integrator\JSMCGI
Integrator\JSMAdmin

Install Instructions

  1. Backup all the LANSA Integrator library and ALL the Integrator IFS objects (LANSA_jsmlib/jsm) before applying this EPC (this IFS is backed up by the EPC load program)
  2. End the JSM server to be upgraded before installing EPC853.
  3. 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.
  4. Move the unzipped file EPC853 to an IFS folder on the System i. ( e.g. /LANSA_jsmlib(pgmlib)/tmp/epc853' )
  5. For this EPC use the following options:
    1. Install the EPC from = *IFS
    2. Apply this EPC to = LANSA_INTEGRATOR 
  6. Run the command LOADEPC with the following parameters:

    jsmlib/LOADEPC and press command 4 (F4) to prompt the command (This command also can be run in batch)

    EPC number . . . . . . . . . . . >  853

    Install the EPC from . . . . . . > *IFS
    IFS Path and object name . . . . eg: /LANSA_jsmlib(pgmlib)/tmp/epc853
    Apply this EPC to . . . . . . . > LANSA_INTEGRATOR
    LANSA Integrator library . . . jsmlib
    LANSA program library   . . . pgmlib (This is optional)

  1. End the JSM server to be upgraded before installing EPC853.
  2. Make a backup of the JSM directory from the iSeries. The current JSM directory will also be saved in the backout library.
  3. EPC853 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 EPC853
    • copy unzipped file EPC853 to folder EPC853
  4. 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 EPC853
    • 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 EPC853 : enter command cd EPC853
    • to send the downloaded file to the iSeries : enter command put EPC853
    • to exit : enter command quit
  5. 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 EPC853 will be created by this command.
  6. 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.
  7. 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(EPC853) RSTLIB(QTEMP)
  8. 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.
  9. Install the EPC using the command:

    LOADEPC853 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.
     
  10. Press enter to continue processing.
  11. 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.
  12. To install the EPC on another LANSA system, sign off and then on again before commencing the next installation.

Additional Install Notes (iSeries)

  1. If custom changes are required to the STRJSM program, the changes should be applied and affected source files should be recompiled. A sample is provided in file QCLSRC.
  2. If custom changes are required to the exit programs JSMADMEXT, JSMDRTEXT, JSMLSAEXT and JSMPXYEXT , the changes should be applied and then the affected source files should be recompiled. Samples are provided in file QCLSRC.
  3. Please view the Additional Install Notes section in this document for important post-installation/upgrade checks.
  1. End the JSM server to be upgraded before installing EPC853.
  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) EPC853w.exe to start the upgrade of LANSA Integrator on Windows.
    NOTE: Please view the 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_EPC853.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_EPC853.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'.
  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. The PKI Editor no longer requires the 3rd party jar files from Phaos Technology. Bouncy Castle is now used and these jar files are shipped with Studio.

  4. When using the Studio application, several obsolete directories and files will be renamed or deleted when a project is opened or a wizard is executed.
    The SOAP Wizard, JSON Wixard, XML transformation and binding Wizards will execute remove obsolete project solution files when they are started.

    The following files will be removed from the project solution directory:

        XML_TRACE.TXT
        XML_COMPILE.TXT
        JSON_TRACE.TXT
        JSON_COMPILE.TXT
        SOAP_TRACE.XT
        SOAP_COMPILE.TXT
        SOAP_WSDL.XT

    The following directories will be removed from the project solution directory:

        xsl-compile
        xml-compile
        json-compile
        xsl-source      ( if empty )
        soap-compile  ( if empty )

    If the soap-compile directory exists and contains files, it will be renamed to compile-agent.
    This the safest option to preserve the contents of the soap-compile directory.
    It is standard practice to have only one SOAP project per solution directory.
    If the solution directory is being used for a SOAP server project, then it is ok to delete the soap-agent directory as it is not used and will only contain old SOAP server generated code.

© 2010 LANSA