Tib Adfiles Release Notes

TIBCO Adapter™ for Files

Release NotesSoftware Release 5.5.0June 2006

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE TIBCO ADAPTER FOR FILES USER’S GUIDE). USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.

TIB, TIBCO, TIBCO Software, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO Adapter, TIBCO Rendezvous, TIBCO Administrator, TIBCO IntegrationManager, TIBCO Designer, TIBCO Hawk, and TIBCO Enterprise Message Service are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

EJB, J2EE, JMS and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.

This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. Please see the readme.txt file for the availability of this software version on a specific operating system platform.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 1999-2006 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

| iii

Contents

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Release 5.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Release 5.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Compatibility and Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Additional Related Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

TIBCO Adapter for Files Release Notes

iv | Contents


| 1

Release Notes

Check the TIBCO Product Support web site at http://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one from the same site. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 8

• Deprecated Features, page 11

• Compatibility and Migration, page 12

• Additional Related Release Notes, page 13

• Closed Issues, page 14

• Known Issues, page 26


2 | Release Notes

New Features

This section lists new features added since the last major release of this product.

Release 5.5.0• Added Platform Support This release adds support for Solaris 10.

• Linux Support Policy The Adapter has adopted the Linux kernel support policy. The following kernels are supported:

— Linux 2.4 kernel:2.4.6 or above, 2.2 glibc: 2.2.4 or above (for example, SuSE 8)

— Linux 2.4 kernel:2.4.18 or above, 2.3 glibc: 2.3.2 or above (for example, Red Hat Advanced Server 3)

— Linux 2.6 kernel:2.6.8 or above, 2.3 glibc: 2.3.3 or above (for example, SuSE 9, Red Hat Advanced Server 4)

• Subscriber’s Reply Message The Adapter’s subscriber service responds with a status message if the data message contains a reply subject. The type of the status message is Rendezvous message.

Release 5.4.0• Added Platform Support This release adds support for AIX 5.2 and 5.3 and

Linux AS 3.0.

• Preserving Undelivered JMS Messages A new check box, Preserve Undelivered, has been added to the Configuration tab of a publication service. This check box determines whether an undelivered JMS message should be preserved in the system queue.

• Location of Progress File You can now specify the location of the progress file directory through the TIBCO Designer. A new field, Progress Directory, has been added to the Processing tab of the publication and the subscription service. This field determines where the progress file is written to. If no directory is specified, the progress file is created in the directory where the adapter was started. This new Feature Applies to both Record and SFT modes and both publication and subscription services.

Release 5.3.1• Support for HP-UX Itanium This release adds support for HP-UX Itanium.


New Features | 3

Release 5.3.0• Support for Business-Event Notifications This release adds support for TIBCO

Business Events.

• Support for RVCMQ Transport This release includes the option for users to specify RVCMQ (Rendezvous Certified Messaging Queue) as a QoS (Quality of Service).

• Support for JMS Message Transport In the simple file transfer mode, the File Adapter now supports JMS message transport in addition to TIBCO Rendezvous message transport.

Release 5.2.0• Storing Tracking IDs If the publisher is re-started while publishing a file, the

associated tracking ID is stored in the progress file. The stored tracking ID will be used by the publisher when re-publishing the file.

This feature is available only in the Simple File Transfer ECM mode.

• Publishing Multiple Files When one trigger publishes multiple files, the first file that is published will use the specified tracking ID. Subsequent files published will use a tracking ID uniquely generated by the adapter.

This feature is available only in the ECM mode.

• Retransmission Delay A new field Retransmission Delay is added to the SFT tab of the publication service. This field is used to specify the number of times the publisher will attempt to publish a message before publishing the error message.

To generate an error message, you need to do the following:

1. Specify the Retransmission Delay.

2. Create a network sink with a role of retransmissionDelay.

This feature is available only in the Strict ECM mode.

• Post Processing Status Flag For the Record Transfer mode, the file adapter appends a status flag (succeeded or failed) to the post processing script at the end of parsing the input file.

As of the release of TIBCO Adapter for Files 5.3.0, TIBCO Business Events has not been released. The above information is provided for convenience purposes only and TIBCO shall, in its sole discretion, determine if and when TIBCO BusinessEvents will be released. For information about this product, contact TIBCO Sales.


4 | Release Notes

For the Simple File Transfer mode (ECM mode only), the argument sequence will now contain the name of the file, arguments specified in the post processing arguments and lastly, the status flag. The status flag is either succeeded or failed.

• Queuing Trigger Messages The adapter handles multiple trigger messages by queuing the received messages by saving them in a trigger file.

This feature is available only when using TIBCO Rendezvous.

• Storing Sequence Numbers In the record transfer mode, the sequence number from the output file is now stored in a progress file. The sequence number can be placed either at the beginning or at the end of the progress file.

When the subscription service is restarted, the next expected sequence number is read from the progress file.

This feature is not available when using the Simple File Transfer-non ECM Mode.

• Error Handling If either the publication service or the subscription service encounters conditions, such as the adapter is unable to the move a file, or a specified folder doesn’t have the requisite permissions, an error message detailing the condition is logged and the adapter continues operation.

• Enhanced Ability to Stop the Adapter In the record transfer mode, to stop the adapter without moving the file from the working directory to the output directory, include the string FAST-EXIT in the exit message.

This feature is only available when using TIBCO Rendezvous transport.

• Using Shortcuts to Specify Directories When specifying folder names, you can now use shortcuts to link to the directories.

For example, you have a directory named complete_dir and a shortcut to it named complete. You can specify complete as your directory instead of complete_dir.

(On Windows only)

• Managing Trigger Files When using the file trigger mode if there are no files for publishing, the trigger file is removed and an error message is displayed only once.

• Added Ability to add UserId Field to Outgoing Messages When the adapter publication service is operating in the timer polling mode, there was no way of including a USERID field in the outgoing messages. Users can now define a global variable to define the user-id which is included in the outgoing message.

The global variable should use the following naming convention:


New Features | 5

<instance name>_<service name>_UserId

For example, if the publication service instance is ReaderA and the service name is PubSrv1, the global variable should be

ReaderA_PubSrv1_UserId

If deploying the adapter using TIBCO Administrator Enterprise Edition

1. Define the global variable using the Global Variables tab.

2. Use the Advanced Editor tab and click the Deployment check box for the newly defined global variable. This makes the global variable value settable from TIBCO Administrator for each deployment.

3. Ensure the adapter properties file contains the new global variable definition.

If deploying the adapter using TIBCO Administrator Repository Edition, update the adapter properties file to include the definition for the global variable.

• Modified Trace Message The trace message for status code AEFA-000062 has changed to: Execute Post Processing script <command string>

Release 5.1.0• Enhanced Error Handling This release of the adapter provides enhanced error

handling. If the error handling feature is used, and the publication service encounters a parsing error in the input file, it creates an xml file that contains the name of the input file and the error details, under the specified error directory.

• Added Platform Support This release of the adapter supports Solaris 9, Red Hat Linux AS 2.1, and Windows Server 2003.

• Support for TIBCO BusinessWorks 5.1.2 The adapter can be used in conjunction with a TIBCO BusinessWorks 5.1.2 process.

• TIBCO BusinessWorks Example A TIBCO BusinessWorks example is provided as part of the adapter installation.

• TIBCO Administrator 5.1.2 Compliance The adapter supports TIBCO Administrator 5.1.2.


6 | Release Notes

Release 5.0.0 • Delayed Acknowledgement for Subscriber Delayed acknowledgment is a

mechanism where an acknowledgement is sent to the publishing application after processing the event.

• Status Messages for Scripts Pre and post-processing scripts now communicate their status to the adapter, which logs the information to a file.

• Support for Dynamically Changing a File Name at Runtime An adapter subscription service is configured at design-time with the name of the output file used to store messages. This output file can be dynamically changed at runtime by sending a message to the service using TIBCO IntegrationManager.

• Support for Multiple Delimiter Characters The adapter publication service can now parse records delimited by multiple characters.

• Support for Custom End Of Line Characters By default, when a file is read a carriage return is assumed to mark the end of a line. You can configure an adapter to use custom end-of-line characters to mark the end of a line, or a combination of custom characters and carriage returns.

• Support for Embedded Delimited Records The adapter can now parse delimited file records that have a repeating sub-structure. Records can also be promoted to the level of a parent; promoted records can be demoted. For details, see Chapter 1, Introduction, in the TIBCO Adapter for Files User’s Guide.

• Enhanced Data Type Validation The adapter performs data validation. If a field contains data that does not conform to the format or is outside the valid range, the entire record is discarded and an error message is logged.

• Support for Handling Date and Time Data As Type Data and Time The adapter handles multiple date and time formats as defined by the Gregorian calendar.

• Change How Read Schema Is Defined Previously, file records were defined independently of read schema. A record was defined, then later linked to the read schema. In this release a read schema is first defined, then its file records are defined under it. Note that file records can no longer be shared, but can be copied to other read schemas.

• Editable Write Schema You can now add or delete fields in write schema records and define formatting information, if necessary, for the new fields.

• Additional Platform Support AIX 5.1 and Red Hat Linux 7.2 are now supported.

• Custom Microagent In addition to the standard microagents that are available with any ActiveEnterprise-compliant adapter, the adapter provides its own microagent. In this release, this microagent provides methods for getting basic processing-related statistics as well as methods for getting and setting some configuration parameters at run time, such as getPollingInterval,


New Features | 7

setPollingInterval, getDocumentDelay, setDocumentDelay, getActivityStatistics, getActivityStatisticsByOperation, getActivityStatisticsBySchema, getActivityStatisticsByServiceName, and ResetActivityStatistics.

• Support for the JMS Transport In previous releases, an adapter service could use only the TIBCO Rendezvous transport. In this release, the JMS (Java Messaging Service) transport is also available. An adapter service that uses the JMS transport can communicate only with the TIBCO Enterprise for JMS server.

• Support for Multi-file Format Projects TIBCO Designer 5.0 now allows you to save adapter projects in multi-file format at design-time. This format is useful if multiple adapter configurations are defined in the same project and worked on by several developers. The adapter configuration files can be managed by a version control system.

• Support for Transferring Files Using this operation mode, the adapter can transfer files among other file adapters.

• Standard Error Management All adapters now use the same mechanism to report errors. Error messages provide more detail, are contextual and can be applied uniformly across adapters. Low-level exception messages like system and TIBCO Rendezvous messages now have appropriate adapter-level information. The error messages descriptions and resolutions are documented in the TIBCO Adapter for Files User’s Guide.

• New Installer The new installer program has three modes available for installation: GUI, console, and silent. The GUI mode presents panels that allow you to make choices about product selection, product location, and so on. The console mode allows you to make installation choices from the command line. The silent mode either installs using the default settings or uses a response file that was saved during an earlier installation.


8 | Release Notes

Changes in Functionality

This section lists changes in functionality since the last major release of this product.

Release 5.5.0• No change in functionality for this release.

Release 5.4.0 • No change in functionality for this release.



Release 5.1.0• Dropped Platform Support Red Hat Linux 7.2 and Sun Solaris 2.6 are no longer

supported.

• Changed TIBCO Hawk Methods The following TIBCO Hawk methods have changed parameters and are now available in the adapter’s class microagent.

— getActivityStatistics()

— getActivityStatisticsByOperation()

— getActivityStatisticsBySchema()

— getActivityStatisticsByService()

— getQueueStatistics()


Changes in Functionality | 9

The following parameters for the above methods are new or have changed (where applicable). In addition, the parameter order for some of the above methods has changed.

— The new output parameter MeasurementInterval displays the time (in seconds) since the last time the adapter was reset, or if never reset, since the adapter started.

— The Total, Success, and Failure output parameters type has changed from string to integer.

— The new output parameter LineIndex is used as an index for the method. Its value is a concatenated string of the Operation and ServiceName parameters separated by a comma.

• TIBCO Rendezvous TX No Longer Supported The TIBCO Rendezvous Transactional quality of service option is no longer supported. The option is still available in the adapter’s palette for backward compatibility with previous adapter releases.

• TIBCO Hawk Class Agent Property The following property has been added to the adapter’s property file: .adfiles.addCustomHawkMethodsToClassMAgent <on/off>. The property is on by default. Setting the property to off disallows adding custom methods to the adapter’s standard microagent.

• Installer Changes The following changes have been made to the installer:

— For adapter installations on Microsoft Windows platforms, all dlls are placed in the lib subdirectory of the adapter installation directory.

— The adapter installation has a new folder called hotfix. The hotfix folder has two sub folders called lib and bin. The hotfix patches will be placed in these sub folders.

— All paths in the tra file will first be prepended with <ADFILES_HOME>/hotfix/lib and <ADFILES_HOME>/hotfix/bin followed by <ADFILES_HOME>/lib and <ADFILES_HOME>/bin.

— TIBCO software can be uninstalled using the TIBCO Installation Manager program.

• Palette GUI Changes The following changes have been made in the palette to the adapter instance configuration tabs:

— Processing tab: The Error Directory field has been added for the Publication Service.

— Advanced tab: The Only publish an identified object, whose associations, if defined, have no errors field has been added, under Publication Semantics, for the Publication Service.


10 | Release Notes

• Palette GUI Changes The following changes have been made in the palette to the adapter instance configuration tabs:

— Configuration tab: Description, Version, and Transformation Plugin fields have been added. Show Advanced Tabs has been renamed to Show All Tabs.

— Startup tab: The Default Session and Metadata Search URL fields have been disabled.

— Monitoring tab: The Default MicroAgent Session field has been disabled. The Has Standard MicroAgent field has been renamed to Enable Standard MicroAgent. The Has Class MicroAgent field has been renamed to Enable Class MicroAgent.

— The General tab is new in this release. The Termination Subject or Topic field is available on the tab.

— The Design Time Adapter tab has been removed.

Release 5.0.0• Installer Changes The adapter installation program no longer includes the

TIBCO Runtime Agent software, which is required by the adapter. The software must be installed prior to installing the adapter.

In previous releases, TIBCO software could be uninstalled using the TIBCO Uninstaller program. In this release, each software component is uninstalled separately by navigating to the _uninst folder and running the Tibuninstall utility.

• Repository Server The repository server is now a component of TIBCO Administrator. Access control to the repository server can be set using TIBCO Administrator.


Deprecated Features | 11

Deprecated Features

This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the equivalent feature.

Release 5.1.0• TIBCO Hawk Methods The following 5.0.1 and earlier TIBCO Hawk methods

available in the adapter’s custom microagent have been deprecated:

— getActivityStatistics()

— getActivityStatisticsByOperation()

— getActivityStatisticsBySchema()

— getActivityStatisticsByService()

— getQueueStatistics()

Equivalent Functionality The above methods are now available in the adapter’s class microagent and have been enhanced (as described in Changes in Functionality on page 8).

If you use TIBCO Designer 5.1 to modify a 5.0 or earlier adapter configuration for use with a 5.0 or earlier run-time adapter, you must use the methods in the custom microagent, not the methods in the class microagent.

Release 5.0.0• Design-time Adapter This feature is no longer supported. In the previous

versions, this feature was used at design time to create schema definitions for files that were placed on remote machines.

Equivalent Functionality In the 5.0.0 release and onwards, to access remote files you can use platform-specific utilities to mount a remote file system or use a copy of the file.


12 | Release Notes

Compatibility and Migration

See TIBCO Runtime Agent Upgrading to Release 5.3 for general information about how the adapter interoperates with previous adapter versions and other TIBCO ActiveEnterprise applications. The guide is part of the TIBCO Runtime Agent documentation set.

Make a backup of the project you are migrating before starting the migration process.


Additional Related Release Notes | 13

Additional Related Release Notes

Adapters are supported by infrastructure products from TIBCO. See the following release notes for additional information about open and closed issues that may affect the adapter.

• TIBCO Designer release notes are available in:

<install-path>\tibco\designer\<version number>\doc\

• TIBCO Runtime Agent release notes are available in:

<install-path>\tibco\tra\<version number>\doc\

• TIBCO Administrator release notes are available in:

<install-path>\tibco\administrator\<version number>\doc\

• TIBCO BusinessWorks release notes are available in:

<install-path>\tibco\bw\<version number>\doc\

• TIBCO Enterprise Message Service release notes are available in: <install-path>\tibco\ems\<version number>\doc\


14 | Release Notes

Closed Issues

This section lists product defects that were closed in the named release.

Closed in Release Defect # Summary

5.5.0 1-6WLJGM The subscription service’s Encoding tab configuration information was not saved if the value in the File System Encoding and File Content Encoding fields were changed to any of the drop down list values from that of a global variable.

This has been fixed.

5.5.0 1-34ESHW In TIBCO Designer, if the delimiter of a delimited record was changed from Other to a positional record, the error: The delimiter must be specified,was displayed.


5.5.0 1-1F1IBW For the adapter publication and subscription services, in the Encoding tab, changing the value of File System Encoding field affected the File Content Encoding field.


5.5.0 1-6X0FLH Incorrect data row was shown in the Sample Line field. In TIBCO Designer’s Positional File Record Configuration tab, when a file was opened using Display Wizard and a row in the file was selected, the row above it was selected internally and shown in the Sample Line field.


5.5.0 1-4K8YFP When a reference was created to a delimited file record or a positional file record using the Link Resource command on the shortcut menu, the reference was created with the error message java.lang.ClassCastException displayed. The reference was lost if the TIBCO Designer was closed.

This has been fixed. The Link Resource command is no longer available with the shortcut menu of a delimited or positional file record.


Closed Issues | 15

5.5.0 1-6U90U1 The Adapter did not support files larger than 2 GB on HP-UX Itanium 64-bit machine.


5.5.0 1-6THWIT The Adapter publication service sent LotEnd as a separate message which followed the last data message.

This has been fixed. To send LotEnd message with the last data message, set the property adfiles.sendLotEndWithDataMsg to TRUE or ON.

5.5.0 1-6QK1UN In TIBCO Designer, if a file schema was renamed, saved, and then the Designer was closed and reopened, the file schema was deleted.


5.5.0 1-6PWTTZ The Adapter instances failed to deploy because TIBCO Runtime Agent minimum version was set incorrectly in the .aar file.


5.4.0 1-5F8IE1 On Linux, the publisher crashed when Document Delay was set.


5.4.0 1-6B1BUH,

1-6B0YUP

In the strict ECM mode, the publisher did not function as expected when processing a zero-byte input file:

• It moved a zero byte file from the input directory to the wip directory.

• It displayed the following error and shut down automatically.

"Error [Adapter] AEFA-000149 Starting offset (0) is

greater than the actual file size!"


5.4.0 1-4ZR9CT In the SFT mode for a Subscription service, the drop down list for Quality of Service in the Transport tab showed Transactional as an option.




16 | Release Notes

5.4.0 1-4Y3S5H For a Subscription service, in the SFT mode, the Close field after time elasped (minutes) and Message Time out (minutes) fields were enabled. The fields remained enabled even if the transport type was changed from JMS to Rendezvous.


5.4.0 1-45X9Q2 The adapter created new FADefaultHawkSessions when the project was validated for deployment.


5.4.0 1-4L439P The Apply button did not get enabled on editing the Pre-registered subscribers field in the publication service and the ECM Subscriber Name field in the subscription service.


5.4.0 1-2T2ZML When a sequence number was chosen to be appended to the subscriber's output file, the TransferResult in the FileTransferEnd event was always "Failed" regardless of the actual file transfer status.


5.4.0 1-2MT4J5 For a subscription service, in the SFT-JMS mode, the functionality for appending sequence numbers to the output file name did not work.


5.4.0 1-2M1349 The pre-processing and post-processing scripts did not return an error code when their execution failed.


5.4.0 1-2EJJFT On UNIX platforms, when a checksum mismatch occurred due to one or more Subscribers going down during a file transfer, the FileTransferEnd event from the Publisher had incorrect values for these fields:

• TransferResult — Success instead of Failure

• SubscriberName — Inappropriate inclusion of the name of the Subscriber that went down




Closed Issues | 17

5.4.0 1-21XSXA When the constant is specified as the last field of the record, the adapter failed to parse the input file.


5.4.0 1-1RXBP2 Moving of records within a Read schema did not get saved. On trying to associate the modified Read schema with a Write schema, in the generated Write schema, the record previously moved remained in the same location as before.


5.4.0 1-1RXBOP When a Read Schema was copied and pasted in another instance and the records in the pasted Read schema were renamed, the record names in the AESchemas folder did not get updated. On trying to associate the pasted Read schema with a Write schema, the Browse window showed the old names.


5.4.0 1-1O7P9T When changing the name of the adapter resource, if the new name contained a hyphen (-), an Invalid Resource Name error message was displayed.


5.4.0 1-1N0LWM The File Schema Position From Header reverted to Begin even after a save operation.


5.4.0 1-1LQSMF When the subscriber was configured with transport type as JMS, the subscriber moved the working file to the output directory on receiving an exit message with <message>=FAST-EXIT.

This has been fixed. The support for using the subject name (Rendezvous) and the destination name (JMS) to determine if an exit message is a FAST-EXIT has been added. You can configure the subject name and the destination name using the General tab of the TIBCO Designer.



18 | Release Notes

5.3.1 1-5B0RWB When an SFT mode subscriber was set to have a sequence number appended to the output file name, the following error message was displayed:

"...Could not open or create the progress file...The

target application specific commands and parameters are

ofstream"


5.3.1 1-42QVKD The SFT publisher did not use the tracking ID provided in the TIBCO Rendezvous polling message. This has been fixed.

5.3.1 1-42QVKU When the RECORD publisher on UNIX did not have read permissions to the input file, it created an empty file in the WIP directory. This has been fixed.

5.3.1 1-4BCWWU If the subscriber failed to overwrite or append the work-in-progress file to the output file, the subscriber sometimes failed to move the work-in-progress file to the error directory. This has been fixed.

Now, the subscriber always moves the work-in-progress file to the error directory if one is specified. A timestamp is also added to the file name. This behavior applies to both Windows and UNIX subscribers and both SFT and RECORD modes.

5.3.1 1-3F4JAP On UNIX, to process a big file, the publisher took approximately 40-50% more time than the 4.2 version of the adapter. The degradation occurred only when many fields defined in the read schema were disabled in the wire schema. This has been fixed.

5.3.1 1-3SPKU1 When the publisher crashed and the check point was restarted, the XML error file showed some of the following problems:

• The file may not contain all the invalid records in the input file.

• Some invalid records may be displayed twice.

• Invalid records may be spread across more than one XML file.

These problems have been fixed.

5.3.1 1-32GVA9 When the "End of Line" property is set to User Defined, the publisher publishes the last record twice. This has been fixed.



Closed Issues | 19

5.3.1 1-2SIQOX The RetryCount in a subscriber's FileTransferAbort EEM event contained junk value. This has been fixed.

5.3.1 1-3IFKK5 The adapter could not be deployed when TRA 5.2.0 and Administrator 5.2.0 were installed. This has been fixed.

5.3.1 1-3WU2GD When an invalid record had a length shorter than the offset of a positional record constant ID field, the following exception was thrown:SDK Error: Cannot initialize string, offset is beyond end of source string.


5.3.1 1-2AU8Q5 The AE Adapter activities were unable to load the File Adapter schemas when the read schemas used container records. This has been fixed.

5.3.1 1-2IJVLB The subscriber crashed when it received an MInstance that contained a MSequence (an array for storing child records) with no object inside. This usually happens when the publisher is BusinessWorks and some of the child records are not present in the data. This has been fixed.

5.3.1 1-29BTXH The publisher continued to process records in the input file even when the transport (for example, JMS server) was down. This has been fixed.

Now, if the transport is down, the publisher simply stops and exits.

5.3.1 1-2AIR0W The following progress file validation has been added:

When the publisher is restarted in the SFT mode, if the calculated starting offset is greater than the actual WIP file size, an error message is displayed and the publisher exits.

5.3.1 1-2QTIG5 In the 'Record Transfer' mode, the subscriber received duplicate messages when the publisher was restarted. This has been fixed.

To avoid duplicate messages, set the TRA variable adfiles.sub.discardDuplicateMessages to ON. Note that the subscriber can only detect and discard duplicate messages if the publisher is also a File Adapter.

5.3.1 1-2I8CSL When the processing script was removed after the adapter was up and running, the adapter logged a "Script successful" message. This has been fixed.



20 | Release Notes

5.3.1 1-2MBJI9 When an RV message trigger was received but no file was found, the publisher did not log a warning message.This has been fixed.

5.3.1 1-2MBJIN In the SFT mode, the publisher and subscriber did not log the progress of the file transfer periodically. This has been fixed.

Now, in the log, the block number published or received is displayed. A new TRA variable, adfiles.logSftProgressEveryNBlocks, allows you to specify the number of blocks after which the progress is to be logged:

adfiles.logSftProgressEveryNBlocks N

where N is an integer.

5.3.1 1-2EJJFD When a 'Delimited' record was changed to a 'Positional' record under the write schema, errors were thrown. This has been fixed.

5.3.1 1-52RRU5 Spaces were accepted in the Trigger File Extension field. This has been fixed.

5.3.1 1-557RW5 The adapter tester could not start on UNIX platforms. For example, on HP Itanium, the following error message was displayed:/usr/lib/hpux32/dld.so: Unable to find library 'libmaverick50.so'


5.3.1 1-273I1J When an adapter instance was renamed using invalid characters, the following error message was displayed:

Name Contains Invalid Characters. invalid_name names must

only have alphanumeric characters and must be at most 80

characters long. Please type in a valid name.

where invalid_name is the name that the user typed.

This has been fixed. The message now reads as follows:

Name Contains Invalid Characters. Instance names must only

have alphanumeric characters and must be at most 80

characters long. Please type in a valid name.

5.3.1 1-1NAKU3 When the Polling Method for the publication service was changed to JMS (topic) Message, clicking Apply threw an exception. This has been fixed.



Closed Issues | 21

5.3.1 1-1NAKUI When you run the example delimitedReader (in the Teak_TafRepoDefault.dat project file) after changing the transport type from Rendezvous to JMS, an exception was thrown. This has been fixed.

5.3.1 1-1LQSKP If the recognition method of a publisher was set to Prefix + Extension and it was restarted while publishing a file, all files were not published. This has been fixed.

5.3.1 1-19YVXS Latin-1 message encoding was not supported for the JMS and TIBCO Rendezvous transports when configured to use the XML message wire format. This has been fixed.

5.3.1 1-1DAA89 On HP-UX platforms, the Adapter Tester did not start although all required information such as the working directory, the adapter executable, the arguments, and the tra file were specified. Instead the following message was displayed:

/usr/lib/dld.sl: can't open shared library:/tsi/build/workspace/suren/TIBFILES/tibfiles-dev/export/h7_110_aCC_Release/l ib/libicuc.sl /usr/lib/dld.sl: No such file or directory.


5.3.1 1-1DJMSX On Solaris platforms, when the adapter was started using the Adapter Tester, the adapter console was blank. No banner, details, or log were displayed in the window. However, the dat file and the tra file were created in the working directory. This has been fixed.

5.3.0 1-23YV91 If the user configured a custom end-point as the closing Subscriber, it reverted to the default Subscriber endpoint, #consumer.FileCloseSubscriber. This has been fixed.

5.3.0 1-239NX9 The subscriber wrote duplicate messages after restart.

Now the MBusiness Doc format uses sequence numbers to prevent duplicate messages. This preventative feature is only effective if the Document Delay parameter is set to 0 (zero).

5.3.0 1-2HU96H The adapter terminated abnormally when it encountered a delimiter character inside a field. This has been fixed.



22 | Release Notes

5.3.0 1-2HU971 When lines with data-format errors immediately followed lines with parsing errors, the lines with data-format errors were not written to the error log file. This has been fixed.

5.3.0 1-1N2GJP Business Document AE classes were not included in export files, including EAR files, for projects that used Business Document data format. This has been fixed.

5.3.0 1-274NW7 When the user tried to save a Publisher configured for JMS transport, and the configuration included an error, the resulting error message referred to RV instead of JMS.

This has been fixed. The message now refers to JMS.

5.3.0 1-23GC81 In Designer, the Type column for records was empty.

This has been fixed. The Type column in the records now indicate the data type of the fields. Data type can be one of the following: string, i1, i2, i4, i8, ui1, ui2, ui4, ui8, r4, r8, datetime, record.

5.3.0 1-E7IYX Users could not specify the order in which the adapter wrote child records to the output file.

A new property, adfiles.toggleChildRecordsOrdering, allows users to toggle the order in which TIBCO Adapter for Files writes child records to the output file.

In the 5.3 release, TIBCO Adapter for Files writes the records from last to first. For example, if you set up the child records as a, b, c, the output file will list them as c, b, a.

Set the value of the adfiles.toggleChildRecordsOrdering property to ON to specify that TIBCO Adapter for Files should write the records from first to last, for example, a, b, c.

Valid values for this property are ON and OFF. The default is OFF.

5.3.0 1-1W0S3H When the File Adapter subscriber (in either Record or simple file transfer mode) was stopped by TIBCO Administrator, the work-in-progress file was moved to the output directory, which resulted in a partial file after the subscriber was re-started. This has been fixed.



Closed Issues | 23

5.3.0 1-2HU97M When a publisher was configured as follows and then restarted, it repeatedly scanned the input directory and took up 100% of the CPU cycle.

• Simple File Transfer Mode

• Explicit Confirmation Mode

• Timer Polling Mode


5.2.0 1-1P0ISL The subscriber sometimes crashed when all of the following conditions existed for the subscriber write schema:

• Derived from a wire schema

• Created by a component other than the File Adapter

• Included a sequence attribute that did not follow the "^child" naming convention.


5.2.0 1-1IYMKQ The File Adapter runtime agent started successfully even when no schema was specified for the subscription service.

Now, if a schema is not specified in the Subscription Service, on startup the file adapter throws the following error and exits:

Startup error. SDK Error: Service contains no schema.

5.1.0 1-HS79Y When an adapter configuration was renamed, the Message Subject field under the Transport tab did not get updated. This has been fixed.

5.1.0 1-KL0H8 When a 4.2 adapter configuration was migrated to 5.0, the global variable JmsProviderUrl was not set and the adapter displayed the following error:

Startup error. SDK Error: Repository Exception : VariableNotFoundExceptionSubstitution Variable JmsProviderUrl not defined.The error occurred on starting the adapter after initialization. The RepositoryURL is backcompat6.dat and the Configuration URL is FileAdapter/FileAdapterConfiguration.




24 | Release Notes

5.1.0 1-KT9K4 When a publication service was renamed, the Subject field under the Transport tab was not refreshed. Additionally, the corresponding Endpoint Reference field was not refreshed. This has been fixed.

5.1.0 1-KT9LQ On HP-UX 11 or 11i, if the adapter configuration used JMS transport with SSL enabled, the following error was displayed:

ERROR: unable to initialize SSL: error=158, message=Not enough random data Startup Error. SDK error: JMS Error: Failed to connect on ssl://localhost:7243: Not enough random data.


5.1.0 1-OOB3M If a schema had been created and associated with a service, the palette displayed an error similar to the following when an attempt was made to move that service to another adapter instance:

The adapter service, PublicationService, contains one or more of the following:1. External schema references2. User-specified user-exit endpoint reference

The service cannot be moved across file adapter configurations unless these references are deleted.


5.1.0 1-OOB3Z Exporting an adapter configuration and then attempting to import it into a new folder did not work, although the adapter displayed the Import Successful message. This has been fixed.

5.1.0 1-OOB4R When a 4.0 adapter configuration was migrated to 5.0, several errors were displayed. For example, one such error that displayed was:

The resource has been locked and does not accept resources.

All these errors have been fixed.

5.0.0 1-FEGVP After creating an empty write schema and renaming it, the write schema reverted to the previous default name. This has been fixed.

5.0.0 1-FEGW2 After renaming an adapter service, if you chose to regenerate endpoints, the endpoint names were changed appropriately but were not refreshed immediately. This has been fixed.



Closed Issues | 25

5.0.0 1-FEGWO Duplicate error messages were displayed when you added a delimited file record with Identifier Type as Field Value and clicked on an item in the project tree before clicking Apply. This has been fixed.

5.0.0 1-FEGXU If a publication service was configured with Life Cycle set to Once Only, Document Delay on, and CheckPoint Restart true, and terminated abnormally, the adapter displayed the message, Working file xxx already exists and exited upon restart. This has been fixed.

5.0.0 1-H1Z8P On HP-UX platforms, a segmentation fault occurred when typing the command ./designer and TIBCO Designer 4.1.3 did not start. This has been fixed.

5.0.0 1-IPK8B The file name in the tracking ID was not consistent with the file being published. This has been fixed.



26 | Release Notes

Known Issues

This section lists issues and provides workarounds where known.

Defect # Summary/Workaround

1-72DQP3 Summary In Record mode, the input data record size must not exceed 256 KB.

Workaround None.

1-2KEPZ9 Summary If the connection to TIBCO EMS server is lost or if the server is down, the Adapter does not try to reconnect to the server.

Workaround

The Adapter can use SDK to reconnect to the TIBCO EMS server. To enable the SDK reconnection feature:

— Set the DefaultJmsTopicSession's, Provider URL property to %%JmsProviderUrl%%,%%JmsProviderUrl%%.

— Set tibco.jmsReconnectCount (the default value is 4) and tibco.jmsReconnectDelay (the default value is 500) if needed.

Note: If you consider the fault tolerance of TIBCO EMS, set the Provider URL to two different EMS daemons: %%JmsProvider1Url%%,%%JmsProvider2Url%%. For more information, refer TIBCO Enterprise Message Service User's Guide, Chapter 13 Fault Tolerance.

1-5XVR6K Summary The adapter does not start if it is deployed in a cluster and it is configured to access a file in a mapped drive. If the mapped drive is changed to a local drive or a cluster shared drive, the adapter starts successfully.

Workaround None.

1-55DO65 Summary If the publisher terminates for some reason and then restarts, upon restart it may create duplicate data in the error XML file.

Workaround None.

1-238MND Summary The adapter is not converting user-defined dates and times properly. For example, the "yyyy/MM/dd, hh:mm:ss:SS a z" format is not converted properly.

Workaround None.


Known Issues | 27

1-26S7JT Summary In the design panel, the context (right-click) menu for adapter instances does not allow cut and paste.

Workaround Use the project panel instead of the design panel. The context (right-click) menu in the project panel does allow cut and paste.

1-26S7K9 Summary The software deletes the ExitSubscriber when users delete a service.

Workaround None.

1-26XZT5 Summary When a user changes the version of an instance to AE Version 4.0, the software warns the user to apply changes even though the Apply button is not enabled.

Workaround The user can ignore this warning.

1-2EJJEX Summary Datetime examples are not working on Solaris platforms.

Workaround None.

1-1JP26D Summary Two dat files are created with similar configurations (default configuration and sequence enabled) but the Location option for modifying the output filename for one is suffix and is prefix for the other. If one subscriber is started and stopped after sequence number, say, 6 and then the second subscriber is started, the second subscriber appends sequence numbers starting with 7.

Workaround None.

1-NV1TD Summary The adapter is unable to handle the single quotation (’) character used for date and time values, and will not process the input file if it encounters a single quotation character. It will display the following error:

2003 Apr 04 17:31:01:138 GMT -8 FileAdapter.reader Error [Adapter] AEFA-000076 Failed to parse the datetime string 2002/07/30, 02:23:34:445 am 'o' clock GMT for the pattern specified yyyy/MM/dd, hh:mm:ss:SSS a ''o'' 'clock' z. Received error code U_ILLEGAL_ARGUMENT_ERROR2003 Apr 04 17:31:01:158 GMT -8 FileAdapter.reader Error [Adapter] AEFA-000074 The line "dt; 2002/07/30, 02:23:34:445 am 'o' clock GMT" contains an invalid field

Workaround Ensure that no single quotation (') character is used in the date and time field.

Defect # Summary/Workaround


28 | Release Notes


Tib Adfiles Release Notes

Documents

Transcript of Tib Adfiles Release Notes