Features and changes in prior versions.
The release of this document for JText connector version
5.5.x contains the following new features:
- Support for the option to use the MVS FTP SITE commands on MVS datasets is
provided with introduction of a new meta-object property named
MVSSiteCommand.
- Enhancements to handle large Business Objects and to reduce Out-of-memory
errors (for a 1GB RAM configuration) have been implemented. A new
meta-object property LargeObject has been introduced for the
adapter to work in large object mode.
- A new SortFilesOnTimestamp connector specific property has been
added to the Adapter and allows the adapter to pick up event files based on
the modification timestamp.
- Note:
- This version of the JText adapter is not backward compatible with ADK
versions prior to the 4222. It needs ADK 4222 or future versions of the
ADK to function correctly.
Beginning with the 5.4 version, the adapter for JText is no longer
supported on Microsoft Windows NT.
Adapter installation information has been moved from this guide. See
Chapter 2, Installing the JText adapter, for the new location of that information.
The release of this document for JText connector version
5.3.x contains the following new features:
- A new FTPTransferType meta object property has been added to
allow for ASCII and Binary file transfers.
- An additional data parsing method for binary data, FixedBOSize,
has been added to the JText Adapter.
- Support for host file system MVS has been enhanced to provide for time
stamping to avoid duplicate file names.
- A new DataProcessingMode meta object property has been added to
the Adapter to enable the reading and writing of Binary data.
- A new meta object attribute, FTPDataStructure, has been added
to the JText Adapter to provide support for either file or record oriented
data structures on remote MVS platforms.
The adapter can now use WebSphere Application Server as an integration
broker. For further information, see Adapter environment. The adapter now runs on the following
platforms:
- Solaris 7, 8
- AIX 5.x
- HP UX 11.i
Updated in March, 2003. The "CrossWorlds" name is no longer
used to describe an entire system or to modify the names of components or
tools, which are otherwise mostly the same as before. For example
"CrossWorlds System Manager" is now "System Manager," and
"CrossWorlds InterChange Server" is now "WebSphere InterChange
Server."
The release of this document for JText connector version
5.1.x contains the following new or corrected information:
- Documentation of theStagingDir meta-object attribute, which allows the connector to use a
staging directory when writing files. The connector writes files that
represent business objects to a staging directory and then moves them to the
configured output directory so that external processes that might manipulate
files in the output directory do not receive the files before they have been
completely written. For more information, see StagingDir.
- Documentation of the IncludeEndBODelimitermeta-object attribute, which enables the connector to either
include the value specified for the EndBODelimiter attribute when it writes out files, or to leave the value
out of the data stream. For more information, see IncludeEndBODelimiter.
- Documentation of the FTPFileListingFormatmeta-object attribute, which enables the connector to read in
files with format information (such as date and timestamps) that differ
depending on the locale. For more information, see FTPFileListingFormat.
- Documentation of the FTPKeepConnectionOpenmeta-object attribute, which enables the connector to
maintain a persistent connection with an FTP server. For more
information, see FTPKeepConnectionOpen.
- Documentation of the FTPOSPlatformmeta-object attribute, which must be set to the value MVS if
the FTP server with which the connector communicates is running an MVS
platform. For more information, see FTPOSPlatform.
- Documentation of the FTPPollTerminateIfServerDownmeta-object attribute, which allows you to specify whether
the connector terminate when an FTP server it is polling for events is
unavailable. For more information, see FTPPollTerminateIfServerDown.
- Documentation of the FTPRequestTerminateIfServerDownmeta-object attribute, which allows you to specify whether
the connector terminate when performing request processing with an FTP server
that is unavailable. For more information, see FTPRequestTerminateIfServerDown.
- Revision of the information regarding the DataEncodingmeta-object attribute. You can set the attribute to
any Java-supported encoding. For more information, see DataEncoding.
The connector has been internationalized. For more information, see "Processing locale-dependent data" and Appendix A, Standard configuration properties for connectors.
WebSphere Business Integration Adapter for JText includes the connector for
JText. This adapter operates with both the InterChange Server (ICS) and
WebSphere MQ Integrator (WMQI) integration brokers. An integration
broker, which is an application that performs integration of heterogeneous
sets of applications, provides services that include data routing.
This adapter includes:
- An application component specific to JText
- A sample business object, included in the
\connectors\JText\Samples\ directory
- IBM WebSphere Adapter Framework, which consists of:
- Connector Framework
- Development tools (including Business Object Designer and Connector
Configurator)
- APIs (including ODK, JCDK, and CDK)
This manual provides information about using this adapter with both
integration brokers: InterChange Server (ICS) and WebSphere MQ
Integrator (WMQI).
The release of this document for JText connector version
4.4.x contains the following changes:
- Support has been added for configuring the connector to use a remote FTP
file system. See Specifying a remote FTP file system for details.
- Documentation of the deprecated DataHandlerFormatter and the ByNameValue,
ByDelimiter, and BySize formatters has been removed. For documentation
on using these formatters, see the JText connector documentation for the
3.0.0 or 2.0.3 releases of the guide for the
connector.
- Documentation of dynamic child meta-objects has been clarified, and the
manual states that use of the JTextWrapper configuration is being
deprecated.
- Documentation of the BODelimiter meta-object attribute has been
clarified.
- The MO_JText_DHFormatter.txt file has been removed from
the \repository\Jtext directory under the product directory.
IBM WebSphere Business Integration for JText includes the adapter for
e-Mail. This adapter operates with both the InterChange Server and
WebSphere MQ Integrator integration brokers. An integration broker,
which is an application that performs integration of heterogeneous sets of
applications, provides services that include data routing.
This adapter includes:
- An application-specific component specific to e-Mail technology.
- A sample, which is located in \connectors\EMail\samples.
- IBM WebSphere Adapter Framework, which consists of:
- Adapter Framework
- Development tools (including Business Object Designer and Connector
Configurator)
- APIs (including ODK, JCDK, and CDK)
This manual provides instructions about using this adapter with both
integration brokers: InterChange Server and WebSphere MQ
Integrator.
The adapter has been internationalized. For more information, see Processing locale-dependent data and Appendix A, Standard configuration properties for connectors.
The release of this document for JText connector version
4.2.x contains the following new or corrected information:
- Support has been added for dynamic child meta-objects. The
connector can now be configured to use wrapper objects or dynamic child
meta-objects for dynamic file specification. See Using a dynamic child meta-object for details.
- The EventDataHandler and OutputDataHandler
meta-object attributes have been added to allow the connector to directly
invoke data handlers rather than invoke them via the
DataHandlerFormatter. You may use these attributes to directly specify
a data handler in the JText connector meta-object rather than indirectly
within the DataHandlerFormatter's meta-object. See Table 7 for details.
- The new user option None has been added for configuring the
EndBODelimiter meta-object attribute when outputting business
objects to a file without any EndBODelimiter or newline
character. See Table 9 for details.
- The DataEncoding meta-object attribute has been added to allow users to
specify the UTF8 encoding instead of the default UTF7. See Table 7 for details.
The release of the document for JText connector version 4.1.x
contained the following new information:
- The connector's archiving feature has been redesigned.
- The naming convention for formatter meta-objects has changed.
- Important:
- It is recommended that you use only data handlers and not formatters for
business-object processing.
- The CwJTFormatter.jar file is no longer
distributed.
- The format and use of the event.log file has
changed.
- The process of specifying a data handler has been clarified and
corrected.
- The descriptions of event notification and data handler processing have
been clarified and corrected.
- A new section on creating custom meta-objects has been added.
- The sections Problem with event triggering and JText failure handling have been clarified and corrected.
