Date : 7 August 2006
| Product | LANSA Integrator |
|---|---|
| Version | 11.0 |
| Pre-Requisite Details | Java 1.4 LANSA Integrator installed from CU1 CD (EPC752) or later. CU3 is recommended to be on the Visual LANSA backend. iSeries: V5R1M0 or above |
| Related Products | LANSA for iSeries and/or Visual LANSA |
| Full Distribution In | V12.0 |
| Special Notes | |
| Document Updates | 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, The LANSA documentation is installed with Visual LANSA in the ..\x_win95\x_lansa\execute\eng directory, or if you installed the LANSA documentation (default folder ...\lansadoc\) from the LANSA Windows CD-ROM, then you should manually copy the updated file to these folders. |
EPC778 contains updates to iSeries and Windows components of LANSA Integrator.
The LANSA Integrator Guide has been updated for this EPC.
EPC778 includes software to be installed on an iSeries machine or Windows machine. These instructions describe the installation and use of all delivered items.
| Yes | LANSA Integrator on iSeries |
| Yes | LANSA Integrator on Windows |
| No | LANSA Integrator on Unix or Linux |
| Yes | Additional Install notes |
EPC778 includes these changes:
| 0107698 | Allow to specify log file location for all Integrator CGI programs
JSMAdmin, JSMDirect and JSMProxy can now nominate a logfile location. If no log file location is nominated, then the default is used. The configuration files used to hold the log file location is jsmcgi.cfg. This configuration file lives in the same folder as the executables. The entry "LogFileLocation=" specifies the path for the logfile. Configuration file jsmcgi.cfg: Example 1: LogFileLocation=C:\Temp This example nominates C:\Temp as the log file location. Full name of the JSMDirect log file will be: C:\Temp\jsmdirect.log Example 2: LogFileLocation=Log This example nominates a folder called Log under the JSMDirect install directory as the log file location. Full name of the JSMDirect log file will be something like: C:\Program Files\LANSA\Integrator\JSMCGI\Log\jsmdirect.log |
| 0121936 | OutboundMultiPartHandler not to uppercase name
Previously the OutboundMultiPart content handler of the HTTPService converted the name of the outbound part to uppercase, leading in some cases to incompatibility with partner applications that were sensitive to the case of the name. This fix prevents the handler from converting the name to uppercase. |
| 0121937 | Add check to OutboundNameValueHandler to check for only 2 fields in list
Previously the OutboundNameValueHandler of the HTTPService did not check the number of fields in the working list supplied to the SEND command. This change implements the check such that the command will fail if the supplied working list has more than two fields. NB: It is possible that this change may impact existing applications. |
| 0121938 | Enhance tracing to delete trace files when service closes without errors
For this purpose TRACE(*ERROR) can now be specified on the SERVICE_LOAD command. In addition the TRACE_NAME keyword has been added to the SERVICE_LOAD for finer control of the disposition of generated trace files. New manager.properties entries have also been added to control tracing. |
| 0121979 | PDFSpoolFileService add custom page size and margin
Enhance PAGESIZE keyword by allowing a custom width and height to be specified. Add MARGIN keyword. Default encoding has been changed to Cp850 and Cp943. |
| 0122102 | Trace JVM classpath
The classpath files and directories are now listed in CLASSPATH.TXT file. This facilitates easier and faster diagnosis of problems related to the classpath. |
| 0122119 | Enchance EDIDataSetSQLService mapping to access other parent result sets
Allow binding process to access other parent resulting using the ../ notation |
| 0122146 | JSMProxy needs to handle IBM apache bug - HTTP_REFERER
JSMProxy checks for the REFERER variable first. If not found, then it checks for the more correct HTTP_REFERER variable. JSMProxy will therefore continue to behave correctly if or when the IBM Apache behaviour is changed. |
| 0122185 | Trace inbound and outbound fieldlist
Trace function fields being sent to JSM service and the fields being returned to the function. This facilitates debugging and diagnosis for client applications. |
| 0122266 | Add more MIME body part headers to OutboundMultiPartHandler
The OutboundMultiPart handler of the HTTPService now creates the following extra MIME body part headers: - Content-Type - Content-Transfer-Encoding This provides better interoperability with other applications. |
| 0122267 | Improve excel reading and writing capability in ExcelReadService
Add OPEN and CLOSE commands. add additional keywords to READ and WRITE commands |
| 0122300 | Allow user defined MIME encoding of MulitPart file part
For the OutboundMultiPart handler of the HTTPService, an optional 4th column on the working list can be used to control the encoding of the file contents. The possible options are 8bit or base64, the default is 8bit. |
| 0122307 | Add encoding MS932 to Text, XML and Properties editors
This provides support for JIS Japanese character encoding. |
| 0122332 | Return null if command keyword value is an empty string
The JSMCommand interface will now return null if command keyword value is an empty string where previously it returned an empty string object. This change may be of interest to developers creating their own LANSA Integrator services. It should not affect any existing LANSA Integrator client applications. |
| 0122383 | Add Copy, Move and Paste files feature to LANSA Integrator Studio
This enhancement facilitates copying and moving files within a project and between projects . |
| 0122486 | Add ability to call stored procedures in SQLService
This enhancement adds the CALL keyword to the EXECUTE command of the SQLService for calling stored procedures. |
| 0122558 | Add SOAP server type support for int[...]
By adding support for integer arrays as parameter or return types, this enhancement extends the range of Web services solutions possible with LANSA Integrator. |
| 0122572 | Allow DCXS882X service program to handle no JSMCLTDTA data area
If the JSMCLTDTA data area does not exist, default to LOCALHOST:4560 and JSM prefix. |
| 0122581 | Use Apache Xalan 2.7.0
Modify compile style sheet logic to handle Apache Xalan 2.7.0 changes. NB: Existing style sheets must be recompiled after applying this change. |
| 0122648 | Add support for XMLSpy
Allow project files to be edited using Altova XMLSpy. XMLSpy is a widely-used XML tool that provides features specifically tuned for editing XML and related files. Note: XMLSpy is not included with LANSA Integrator. Customers must acquire XMLSpy separately. Customers who do not have or wish to acquire XMLSpy may continue to use the editor built-in to LANSA Integrator. |
| 0122666 | Add excel sheet protection to ExcelReadService
New keywords on the WRITE command of the ExcelReadService allow client applications to implement sheet protection. |
| 0122667 | Improve Studio Look And Feel
As supplied, this version of LANSA Integrator Studio implements the "plastic" look and feel defined by the JGoodies Looks 1.3.2 package. This provides a look and feel that for most purposes is indistinguishable from native Windows applications. |
| 0122684 | Add copy-namespaces to xsl:copy-of, this is an XSLT 2.0 feature
Enhance XMLEditor format command to use the xsl:copy-of copy-namespaces attribute to copy unused namespaces |
| 0123171 | RFI table class cannot send an RDMLX list - Out of memory error
RDMLX working lists are no longer limited to 9999 entries. Therefore the RFI table class associated with the RFIDataSourceService has been amended not to rely on the list maximum when allocating memory to contain the list. Instead the initial size is set to 1000 and will grow dynamically when entries are added. |
| 0123173 | Change XMLWizard to look like XMLBindWizard
The existing XMLWizard has been changed to have a consistent look and feel to the new XMLBindWizard. |
| 0123174 | Create XMLBindFileService to use code generated by XMLBindWizard
The XMLBindFileService (and its associated XMLBindWizard) is a new service for reading and writing XML files. The XMLBindFileService generates Java code to bind the client application to the XML data. In doing so, it avoids some of the scalability and other issues associated with XSL transformations as used by the existing XMLFileService. The XMLFileService remains fully supported but in most cases new applications should use the XMLBindFileService in preference. |
| 0123175 | Create XMLBindWizard to read and write XML sources
The XMLBindWizard is used to define projects that will read and write XML sources using the new XMLBindFileService. |
| 0123208 | Enhance CSV parser to handle quoted empty value
The CSV parser has been enhanced to hande quoted empty values and to behave the same as Microsoft Excel. This affects: - the HTTPService (InboundSeparatedValue and OutboundSeparatedValue content handlers) - the HTTPInboundSVService - the SVFileService Following this enhancement, CSV parsing behaviour is more standard - however, it continues not to support "\r\n" (carriage return / line feed) embedded inside quoted values. |
| 0123432 | Clear temporary files from SOAP project before build and generate cycle
LANSA Integrator Studio now clears the project compile directory and other build output files before each build and generate cycle for a project. This helps to ensure that any current output is from the immediately preceding build. Customers should not place customer files in the project compile directory. |
| 0123433 | Check classpath for duplicate classes during JSM manager tracing
The new duplicate checking is designed to facilitate more readily identification and diagnosis of apparent LANSA Integrator problems arising from such name conflicts. |
| 0123434 | Add RPG Structure Editor to LANSA Integrator Studio
The new Structure Editor to simplifies creating RPG structure definitions for passing fields and lists between an RPG client application and the JSM. |
| 0123435 | Add support for Cp1388 and Cp935 DBCS EBCDIC Simplied Chinese
LANSA Integrator now supports client applications using these code pages - that is, for data (command strings, fields and lists) passed between the client application and the JSM. Note that Cp935 is a subset of Cp1388 and that the latter is not presently supported by the iSeries JDK 1.4. Therefore Cp1388 is supported only for the subset of characters that are also available in Cp935. |
| 0123471 | Create and use a local temp directory, when using Studio startup argument
Shared Studio Projects To allow users to access shared projects, specify the shared directory as a Studio program argument. Copy or modify an existing Studio short-cut and add the shared directory to the end of the program command. com.lansa.jsf.studio.JSFStudio s:\studio A workspace subdirectory and Studio.xml file will be created in the specified directory. A temp subdirectory used for Drag and Drop operations will be created in the program's current or start in directory on the local drive. By default Studio uses the current directory or Start In directory for its working directory. |
| 0124001 | Add JavaScript support to EDI mapping
Add JavaScript support to EDI mapping to allow the definition of custom processing or formatting for in-coming or out-going EDI values using EDI services with EDI Direct. |
| 0124002 | Improve Stream File support in SOAP Wizard
Allow String and byte array parameters to be able to send and receive content from and to stream files. |
| 0124006 | Ship Apache Rhino JavaScript version 1.6.2
Ship Apache Rhino JavaScript version 1.6.2 (this is to support Javascript in EDI mapping). |
| 0124984 | service.properties resource lookup should be using service name not class name
Use the service name to do the service.properties resource lookup and not the classname. Add extra properites to support backward compatability. |
| 0124985 | Reduce Java object creation in JSM server
Locate areas where object creation is excessive and refactor code to reduce memory usage and improve performance. |
| 0124986 | Add Wrapped Document/Literal support to SOAP Server
The wrapped document/literal style is becoming the preferred option for many new Web service applications. The SOAP Client supported this style previously. Now the SOAP Server supports this style for Web services published using LANSA Integrator. |
| 0124987 | Add SPLIT and BREAK commands to EDICatalogService
The new commands are provided for breaking up large EDI transmissions containing multiple transactions into smaller transaction sets. This is done to improve performance of the EDI services, which can be degraded when used with very large files. |
| 0124988 | Create JMSFileService to send and receive files as messages
Create new JMSFileService to send and receive files as messages through vendor-implementations of the Java Messaging Service (JMS) api. This release supports vendor implementations for MQSeries and SonicMQ. |
| 0124989 | Create additional helper methods for JSM service programmers
Create JSMManager.getTemporaryDirectory and JSMManager.createTemporaryDirectory methods to further support development of custom LANSA Integrator services. |
| 0124990 | Improve XML processing
Improve XML processing by adding additional keywords like DOMSET, DOMSETRESULT to services that process XML content. These enhancements allow DOM reuse and streaming of XML result out to temporary files to reduce memory usage. |
| 0124991 | Improve the updating of LANSA fields and list from FunctionXML results.
Use a SAX approach to receive data into LANSA fields and lists instead of the DOM approach used previously. This has no effect functionally but may reduce memory requirements and improve performance in some cases. |
| 0124992 | Improve performance of EDI processing by changing the format of DataSet XML
Improve performance of EDI processing for EDI/Direct by changing the format of DataSet XML |
| 0125086 | Output upgrade messages to UPGRADE-LOG.TXT
This enhancement changes the upgrading and pending logging from System.out ( STDOUT ) to files in the instance directory. This will make it alot easier to locate the upgrade log. |
| 0125098 | Allow HTTPService to send HTTP head properties
Allow HTTPService outbound content handlers to send HTTP protocol head values. The SET command has been added to the HTTPService to allow user defined HTTP head properties to be sent. |
| 0125141 | XMLWizard - set XSL indent-amount to 0
This enhancement changes the XMLWizard generated XSL indent-amount from 2 to 0. This will reduce the size of the XML data. |
| 0125151 | Add new InboundMultiPartHandler
The InboundMultiPart content handler of the HTTPService can be used to send and receive MIME multipart content. |
| 0125283 | Add FORMAT keyword to MQGET command - JSMMQGET program
Also the MQ BIF service program DCXS883X has been changed to trim the format value. MQGET CCSID(37) FORMAT(MQSTR) |
| 0125415 | Allow XML DTD entity resolver to use dtd.dir resource and also dtd directory
The following additional steps are only done for url's with a file:// protocol. If a dtd.dir property exists then the value directory and url filename are used. If the dtd.dir property does not exist, then if the url file does exist use the current url value else use the instance dtd sub-directory and the url filename. |
| 0125484 | XMLParserService cannot get node text from a < tag/> type node
The GET command of the XMLParserService fails with a NullPointer exception when attempting to retrieve the value of an empty element node in the form <tag/>. In this instance the GET command should return an empty string. |
| 0125486 | Allow means to TRIM node or attribute text return in JSMMSG field
Allow means to TRIM node or attribute text return in JSMMSG field for the XMLParserService. The current text is trimmed both ends, this should be trailed trimmed. Add TRIM keyword support to GET and CHECK commands. NB: Because this enhancement changes the default trim behaviour, it is possible that the behaviour of existing client applications using the XMLParserService could be affected. Users should consider the impact on existing applications and, if necessary, plan changes to explicitly specify the TRIM keyword in order to preserve the current behaviour. |
| 0125488 | XMLParserService should be auto detecting the XML encoding
Most of the XML sources FILE, FTP, POP3 protocol do not identify the encoding of the contents. So the XMLParserService needs to auto-detect the encoding. This frees the client application from having to know in advance and specify the encoding that applies to the XML content. |
| 0125540 | Change the property to do EBCDIC NL to LF conversion for XMLQueueService
This enhancement rationalises two properties concerning NL (new line) to LF (line feed) conversion for the XMLQueueService into a single property in this version. The previous method required two properties and was confusing in its usage and did not offer any advantage of just having a single property boolean to do the conversion or not. For MQ Series, replace: - "mq.put.ebcdic.byte.from=NL" and "mq.put.ebcdic.byte.to=LF" - with the single property "mq.put.ebcdic.nl2lf=true" For iSeries data queues, replace - "dq.put.ebcdic.byte.from=NL" and "dq.put.ebcdic.byte.to=LF" - with the single property "dq.put.ebcdic.nl2lf=true" |
| 0125554 | Allow Studio to be able to receive different levels of trace directory files
Add property to manager.properties "studio.include.trace.directory" to control if child trace directories and files are sent to the LANSA Integrator Studio client. |
| 0125555 | Change the default encoding for inbound HTTP XML content to auto-detect
If no ENCODING keyword and charset attribute then default to auto-detect for XML content. |
| 0125678 | Return single "from address" in response message field for POP3MailService
If the calling application does not provide a working list in which to receive the "from addresses", the POP3MailService will return the first "from address" in response message field. This simplifies client application programming for the most common case. |
| 0125706 | Add support for more IANA encoding
This enhancement extends LANSA Integrator's internationalisation support to keep current with encodings mandated by relevant standards bodies. In particular this affects HTTP, XML and SOAP services. |
| 0125707 | Allow XMLQueueService to receive and send text messages
The XMLQueueService is for sending or receiving XML messages via MQSeries message queues or iSeries data queues. This enhancement extends it to permit sending and receiving plain text messages for simple applications that do not demand the use of XML. |
| 0125784 | Add GET message sent date to POP3MailService
The GET command of the POP3MailService allows a client application to retrieve a mail message or attributes of a mail message from the POP3 server. Previously you could retrieve attributes such as the sender's address, the subject and a list of attachments. With this enhancement, the message sent date can now also be retrieved. |
| 0125785 | Add SERVICE_GET PROPERTY() command to all servcices
Using this new command, LANSA Integrator client applications can directly access service properties for a service they have loaded. As well as accessing service properties known to or used by LANSA Integrator services, client applications can store their own custom properties in the service properties file and use this service command to access their values at run-time. If used in this way, it is the client application's responsibility to adopt a naming standard that avoids any potential name clash with current or future LANSA Integrator service properties. |
| 0125786 | Add BigDecimal, BigInteger, Double and Integer support to SOAP ServerTypes
This new support enables LANSA Integrator SOAPServer service to better serve Web services that conform to specifications created outside the LANSA Integrator SoapWizard. |
| 0125946 | Update 3rdParty jars with latest version
Apache Axis 1.4, iText 1.4 and jxl 2.6.0 This represents updated underlying support for SOAP, PDF and ExcelRead services. The updates include fixes for some known issues in these 3rd party libraries. There is not new functionality exposed through the related LANSA Integrator services, except as specifically noted in other items. |
| 0126010 | Improve ExcelReadService Date cell handling
This enhancement ensures that dates read from Excel files are interpreted according to the local timezone. |
| 0126013 | Improve UserAgent Excel date cell handling
Make default date format yyyy-MM-dd. Use timezone GMT. http://www.andykhan.com/jexcelapi/tutorial.html#dates |
| 0126078 | Improve ExcelReadService and UserAgent excel numeric cell read
ExcelReadService and UserAgent can now read a wide range of formated cells. Numeric cells value are converted a the standard format. -1234.10 |
| 0126080 | SQLService METADATA scale is returning precision value should be returning scale
The working list populated by the METADATA service command of the SQLService should contain column name, type, precision and scale, but the precision was being placed in the scale column. |
| 0126082 | Add SET SQLSTATE keyword support
The SQLSTATE keyword has been added to the SET service command of the SQLServiice. This controls the command response status value being ERROR, WARNING or SQLxxxx. |
| Object Name | Folder | Platform |
|---|---|---|
| jsm.jar | LANSA Integrator Instance jar directory | All |
| jsmas2.jar | LANSA Integrator Instance jar directory | All |
| jsmaxis.jar | LANSA Integrator Instance jar directory - Axis 1.4 | All |
| axis.jar | Component | |
| commons-discovery-0.2.jar | Component | |
| commons-logging-1.0.4.jar | Component | |
| jaxrpc.jar | Component | |
| saaj.jar | Component | |
| wsdl4j-1.5.1.jar | Component | |
| log4j-1.2.8.jar | Component | |
| jsmedimap.jar | LANSA Integrator Instance jar directory | All |
| jsmide.jar | LANSA Integrator Instance jar directory | All |
| jsmjaf.jar | LANSA Integrator Instance jar directory - JAF 1.0.2 update | All |
| jsmmail.jar | LANSA Integrator Instance jar directory - JavaMail 1.3.2 | All |
| mail.jar | Component | |
| jsmnative.jar | LANSA Integrator Instance jar directory | All |
| jsmpdf.jar | LANSA Integrator Instance jar directory - iText 1.4 | All |
| jsmpdfcjk.jar | LANSA Integrator Instance jar directory | All |
| jsmrfi.jar | LANSA Integrator Instance jar directory | All |
| jsmscript.jar | LANSA Integrator Instance jar directory - Rhino 1.6.2 | All |
| jsmservice.jar | LANSA Integrator Instance jar directory | All |
| jsmsoap.jar | LANSA Integrator Instance jar directory | All |
| jsmutil.jar | LANSA Integrator Instance jar directory | All |
| jsmxalan.jar | LANSA Integrator Instance jar directory - Xalan 2.7.0 | All |
| xalan.jar | Component | |
| xercesImpl.jar | Component | |
| xml-apis.jar | Component | |
| jsmxls.jar | LANSA Integrator Instance jar directory - JExcel 2.6.0 | All |
| Object Name | Object Type | Library |
|---|---|---|
| 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 |
| BI@P277 | *PGM | *PGMLIB |
| BI@P278 | *PGM | *PGMLIB |
| BI@P279 | *PGM | *PGMLIB |
| BI@P280 | *PGM | *PGMLIB |
| BI@P281 | *PGM | *PGMLIB |
| BI@P282 | *PGM | *PGMLIB |
| BI@P303 | *PGM | *PGMLIB |
| CHGJSMAUT | *PGM | *JSMLIB |
| CHGJSMDFT | *PGM | *JSMLIB |
| CHGJSMOWN | *PGM | *JSMLIB |
| CLRJSM | *PGM | *JSMLIB |
| CRTJSMSBS | *PGM | *JSMLIB |
| DC@P8700 | *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 |
| JSMLINK | *PGM | *JSMLIB |
| JSMMQDEPTH | *PGM | *JSMLIB |
| JSMMQGET | *PGM | *JSMLIB |
| JSMMQPUT | *PGM | *JSMLIB |
| JSMOWNER | *PGM | *JSMLIB |
| JSMPENDING | *PGM | *JSMLIB |
| JSMPROXY | *PGM | *JSMLIB |
| OPTJSM | *PGM | *JSMLIB |
| RUNJSM | *PGM | *JSMLIB |
| WRKJSM | *PGM | *JSMLIB |
| DCXS882X | *SRVPGM | *PGMLIB |
| DCXS883X | *SRVPGM | *PGMLIB |
| JSMDTAQ | *SRVPGM | *JSMLIB |
| JSMMGRSRV | *SRVPGM | *JSMLIB |
| JSMMSGQ | *SRVPGM | *JSMLIB |
| JSMUSRSPCE | *SRVPGM | *JSMLIB |
| LIBLSSRV | *SRVPGM | *JSMLIB |
| JSM | *MSGF | *JSMLIB |
| JSMMSGF | *MSGF | *JSMLIB |
| JSM | *DSPF | *JSMLIB |
| JSMIFS | *SAVF | IFS Instance objects |
| JSM | *MENU | *JSMLIB |
| DC@D8700 | *FILE | *JSMLIB |
| DC@F47 | *FILE | *PGMLIB |
| DC@F48 | *FILE | *PGMLIB |
| DC@W29 | *FILE | *JSMLIB |
| DC@W29V1 | *FILE | *JSMLIB |
| DC@W29V2 | *FILE | *JSMLIB |
| DC@W30 | *FILE | *JSMLIB |
| DC@W30V1 | *FILE | *JSMLIB |
| JSM | *FILE | *JSMLIB |
| QCLSRC | *FILE | *JSMLIB |
| QCMDSRC | *FILE | *JSMLIB |
| QDDSSRC | *FILE | *JSMLIB |
| QRPGLESRC | *FILE | *JSMLIB |
*JSMLIB = LANSA Integrator Program Library, *PGMLIB = LANSA Program Library
| Object Name | Folder | Platform |
|---|---|---|
| LANSA Integrator Studio | \Integrator\Studio | |
| LANSA Integrator User Agent | \Integrator\UserAgent | |
| LANSA Integrator Remote Function Invocation | \Integrator\RFI | |
| LANSA Integrator on Windows | \Integrator\JSMInstance | |
| \Integrator\JSMCGI | ||
| \Integrator\JSMAdmin |
CHGATR OBJ('/jsm/instance')
ATR(*READONLY) VALUE(*NO) SUBTREE(*ALL)
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.
- in Explorer, map to the shared folder drive
- create a folder named EPC778
- copy unzipped file EPC778 to folder EPC778
- logon to the iSeries and create folder EPC778
- 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 EPC778 : enter command cd EPC778
- to send the downloaded file to the iSeries : enter command put EPC778
- to exit : enter command quit
NOTE: Check the OS/400 system value QFRCCVNRST. If QFRCCVNRST is set to 0, you must use FRCOBJCVN(*YES) on the RSTOBJ command.
For a save file you will use the following command:
RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(EPC778) RSTLIB(QTEMP)
LOADEPC778 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 is optional.
You might want to do a backup of your current independent User Agent install before you start the upgrade process.
You might want to do a backup of your current independent RFI install before you start the upgrade process.
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:
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.
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.
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
#!<studio-project id="00000000-000000"
name="unassigned">
#
# Move these entries to a new or existing studio-project section.
# Delete this unassigned section.
#
#
#!</studio-project>
© 2006 LANSA