Release notes for IBM Transformation Extender Advanced Version 9.0.0.9

• ITXA now supports ITX version 10.0.0.0.
• You can now select the outbound X12 ISA11 Repetition Separator delimiter in the user interface. When the ISA12 Interchange Control Version Number mandates that the ISA11 parameter is the Interchange Control Standards Identifier (for version 00401 and below), Repetition Separator is displayed as a text box with the character value.
• Control numbers that use database sequences can now be tracked and displayed in the user interface. Previously, the value of a database sequence could not be displayed. This control number display enhancement is disabled by default. To enable this feature, you need to set this property in customer_overrides.properties as follows:
  
  enveloping.useControlNumberSequenceTracker=YES
  
  To display database sequence values, you must enable (turn on) the tracker, and data using the envelope must be processed by ITXA. The control numbers are tracked using the transaction register table in the database. By default, the tracker runs every 5 minutes to flush the tracked values from memory to the transaction register table. You can adjust the default time period by using this property:
  
  enveloping.controlNumberSequenceTrackerInterval=300000
  
  NOTE: In the above example, 300000 is value of 5 minutes in milliseconds.
• You now experience improved performance when pending acknowledgments are updated to Overdue status. Also, you can delete pending acknowledgments by using an API method, a REST API function, or an option in SPESample.
   

  To take advantage of increased performance when pending acknowledgments are updated to overdue status, set the following options when using any of the three methods:

  NEED_PENDING_ACK_REPORT=NO
  NEED_PENDING_ACK_CORRELATIONS=NO

  
  When you set these two options to NO, it informs the overdue acknowledgment service that only a database update is needed, which triggers optimized queries and updates.
   

  SPESample has been amended to allow the checkPendingAckStatus API to be used an option.

  The new API that can be used to delete acknowledgments is deletePendingAcknowledgments.

[Where to find the software to download]

To download the software for IBM Transformation Extender Advanced Version 9.0.0.9, go to Fix Central.

[Documentation]

Online documentation is provided for the product in the IBM Knowledge Center.

Translated documentation
Based upon country requests, the online product documentation has been translated from the original English (United States) version into various native languages.

See the Knowledge Center in English for the most recent documentation.

Inquiries about translating documents into specific languages should be directed to an IBM representative of the respective country.

Back to top

=====================================================================
2. INSTALLATION AND CONFIGURATION
====================================================================

[Installation prerequisites]

IBM Transformation Extender Advanced (ITXA) Version 9.0.0.9 requires IBM Transformation Extender Version 10.0.0.0 or higher.

You can install IBM Transformation Extender Advanced (ITXA) Version 9.0.0.9 on any supported version of the Linux, UNIX, or Windows operating system. See the Detailed System Requirements for Transformation Extender Advanced.

If installing IBM Transformation Extender (ITX) Version 9.0 or later common components for use with ITXA on Solaris, be aware that ITX requires the compatibility/ucb package. Solaris 11 systems might not include the package by default. (Earlier versions of Solaris do include the package.) See the Known Limitations section for more information.

To enable ITX to recognize the ITXA server components, install ITX Version 10.0.0.0 or higher prior to installing or upgrading ITXA server components. Alternately, if you prefer to install the ITXA server components before ITX, follow the procedure under "ITX does not recognize ITXA" in Section 4.

[Windows and UNIX Installation]

To install products, see the installation procedure in the IBM Knowledge Center.

[Uninstall]

To uninstall products, see the uninstallation procedure in the IBM Knowledge Center.

Back to top

=====================================================================
3. UPGRADE AND MIGRATION
=====================================================================

[Before you upgrade your installation]

Copy the files that are listed below to a local backup folder. These files are normally backed up by the upgrade process, but if you customized these files, it is recommended that you also make a manual backup in the event that an error occurs during the upgrade.

spe_install_dir/customer_overrides.properties
spe_install_dir/dbprops.cfg
spe_install_dir/packs.properties
spe_install_dir/speiib.properties
spe_install_dir/tpuiserver/usr/servers/defaultServer/jvm.options
spe_install_dir/tpuiserver/usr/servers/defaultServer/server.xml

[Upgrade]

Reminder: Make sure that all applications that use ITXA are shut down before you begin the upgrade, including the ITXA Derby database, the Trading Partner User Interface, and any host applications such as B2Bi and IIB.

To upgrade from IBM Transformation Extender Advanced Version 9.0 through 9.0.0.8 to Version 9.0.0.9, use the IBM Installation Manager update option.
 

[After you upgrade]

1. Redeploy any packs that you installed by using the spedeploy-packs script.
   - Only updated packs need to be redeployed. For example, if you install ITX 9.0.0.9 you must also deploy version 10.0.0 of the EDI and Healthcare packs. The other pack (Financial Services) does not need to be redeployed because no changes or updates were made to it. If you did not deploy or redeploy any packs after the upgrade, you must regenerate the pack configuration files and update the database by executing the spedeploy-packs -j nojar -d nowtx command.

- If your pack version is not one of the versions that is supported by ITXA 9.0.0.9, install the supported version of the pack on your Windows design time system and create a new resource file for the pack using the appropriate speresource-pack script. Then, redeploy the new pack resource file using the spedeploy-packs script.

NOTE: There are two options to create and deploy the Pack for Healthcare. You can either:
- Use the Windows design time system to create a resource bundle for the Pack for Healthcare, then deploy the resource bundle to your runtime system.
- Or, you can deploy the pre-built resource bundle (for all platforms) directly to your runtime system. This option allows you to skip the steps to install the pack on your Windows design time system and create the resource bundle. However, you will still need to install the pack on your Windows design time system in order to use the type trees, edit examples, and perform other design time tasks.

1. Check the files listed below, and merge any customized entries from the backup copies as needed. Typically the customer_overrides.properties file contains customized entries that need to be merged back in, especially if ITXA is used with B2Bi or IBM Control Center. Depending on your configuration, other files may also have customized settings that need to be merged back in.
   
   spe_install_dir/customer_overrides.properties
   spe_install_dir/dbprops.cfg
   spe_install_dir/packs.properties
   spe_install_dir/speiib.properties
   spe_install_dir/tpuiserver/usr/servers/defaultServer/jvm.options
   spe_install_dir/tpuiserver/usr/servers/defaultServer/server.xml
2. To upgrade your database, establish a connection to the database and run the spedbupgrade command. Note: This instruction applies any database changes that are needed for ITXA 9.0.0.9.
3. If you are using ITXA with B2Bi, check your dynamic classpath in B2Bi to make sure all the jar files from the <SPE_INSTALL_DIR>/jars directory are included. Be especially careful with jar files that include version numbers, since these jar names may change from one ITXA fix level to the next.

[Pack upgrade]

There was no pack upgrade for ITXA Version 9.0.0.9.

Back to top

=====================================================================
4. KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS
=====================================================================

[Error message received when running WebSphere Transformation Extender outbound transactions on instance of Solaris 11]

Issue: When running WebSphere Transformation Extender outbound transactions on an instance of Solaris 11, this message is received:

librpcsoc.so.1: open failed: No such file or directory

Note that the file libdstxjpi.so is present under the specified path, WTXInstallDir/libs.

Cause: WebSphere Transformation Extender requires the compatibility/ucb package. Solaris 11 systems might not include the package by default. Earlier versions of Solaris do include the package.

Workaround: To install the compatibility package, follow the procedure in the troubleshooting technote WebSphere Transformation Extender returns "librpcsoc.so.1: open failed: No such file or directory" error on Solaris 11 systems.

[IBM Transformation Extender does not recognize ITXA after a subsequent IBM Transformation Extender installation]

Issue: A customer installs IBM Transformation Extender after ITXA has been installed, and IBM Transformation Extender does not recognize ITXA.

Background: When ITXA is installed, it checks if IBM Transformation Extender is installed. If IBM Transformation Extender is installed, ITXA updates the IBM Transformation Extender dtx.ini file.

If a customer installs IBM Transformation Extender after SPE has been installed, the dtx.ini file does not contain the location of the prior ITXA installation.

Workaround:

1. Manually update the IBM Transformation Extender itx_install_dir/config/dtx.ini file by appending the following lines:

[SPE]
SPE_INSTALL_DIR=C:/IBM/Standards Processing Engine 9.0.0

2. Edit the spewtxenv script in the spe_install_dir/bin directory. Change this line to set DTXHOME to the WTX install directory:

%INSTALLREPLACEMENTSTRING%

• (Windows operating system) The spewtxenv.bat script specifies the ITX installation. Example:

set DTXHOME=C:\IBM\TransformationExtender_10.0.0

• (Linux and UNIX operating systems) The spewtxenv.sh script specifies the ITX installation. Example:

DTXHOME="/itx_install_dir"; export DTXHOME

3. Create the directory link so the ITXA User Interface can find the required ITX files:

• Change directory to the spe_install_dir/tpuiserver/usr/servers/defaultServer/lib directory.
• Remove the empty wtx directory.
• Create the wtx link as follows, where "/path/to/wtx" is the ITX install directory:

Windows: mklink /d wtx \path\to\wtx
UNIX: ln -sf /path/to/wtx/libs wtx


[Some characters are not available for use in naming a resource]

Issue: The following characters are reserved by the Trading Partner UI, and therefore should not be used when naming a resource: "|" (pipe), "^" (caret), and ":" (colon).

Workaround: Avoid the use of these characters when naming resources.


[Known issues in non-English versions of ITXA documentation]

See the English version of the ITXA documentation for the most recent documentation.

[Labels not translated]

In the French version of the documentation, the text appears in English for two graphics:

• "Figure 1: Sample deployment" in the Planning section
• "Figure 1: Standards Processing Engine architecture" in the Overview section

Each graphic is fully described in its accompanying translated text.

Back to top

====================================================================
5. NEW AND CHANGED BEHAVIOR
====================================================================

This is a summary of the new features and changed behaviors in Version 9.0.0.9:

• ITXA now supports ITX version 10.0.0.0.
• You can now select the outbound X12 ISA11 Repetition Separator delimiter in the user interface. When the ISA12 Interchange Control Version Number mandates that the ISA11 parameter is the Interchange Control Standards Identifier (for version 00401 and below), Repetition Separator is displayed as a text box with the character value.
• Control numbers that use database sequences can now be tracked and displayed in the user interface. Previously, the value of a database sequence could not be displayed. This control number display enhancement is disabled by default. To enable this feature, you need to set this property in customer_overrides.properties as follows:
  
  enveloping.useControlNumberSequenceTracker=YES
  
  To display database sequence values, you must enable (turn on) the tracker, and data using the envelope must be processed by ITXA. The control numbers are tracked using the transaction register table in the database. By default, the tracker runs every 5 minutes to flush the tracked values from memory to the transaction register table. You can adjust the default time period by using this property:
  
  enveloping.controlNumberSequenceTrackerInterval=300000
  
  NOTE: In the above example, 300000 is value of 5 minutes in milliseconds.
• You now experience improved performance when pending acknowledgments are updated to Overdue status. Also, you can delete pending acknowledgments by using an API method, a REST API function, or an option in SPESample.
   

  To take advantage of increased performance when pending acknowledgments are updated to overdue status, set the following options when using any of the three methods:

  NEED_PENDING_ACK_REPORT=NO
  NEED_PENDING_ACK_CORRELATIONS=NO

  
  When you set these two options to NO, it informs the overdue acknowledgment service that only a database update is needed, which triggers optimized queries and updates.
   

  SPESample has been amended to allow the checkPendingAckStatus API to be used an option.

  The new API that can be used to delete acknowledgments is deletePendingAcknowledgments.

Deprecated functions, components, and platforms

Per IBM policy, these operating systems are still supported with this release of the product, but they will be withdrawn from support in a future release.

The following functions, components, and platforms are deprecated in ITXA Version 9.0 and later:

• Solaris SPARC platform
• HP-UX Itanium platform
• Red Hat Enterprise Linux (RHEL) 6 and 7 for POWER System-Big Endian
• SUSE Linux Enterprise Server (SLES) 11 and 12 for POWER System-Big Endian

Removed functions, components, and platforms

32-bit platforms are not supported as of ITXA Version 9.0.0.x.

Back to top

=====================================================================
6. Resolved Authorized Program Analysis Reports (APARs)
=====================================================================

See the APARs that are resolved for ITXA Version 9.0.0.9 in the Fix List.

Back to top

=====================================================================
7. CONTACTING CUSTOMER SUPPORT
=====================================================================

Contact Customer Support at 1-800-IBM-SERV, or go to the IBM Support Portal.

Back to top

=====================================================================
8. NOTICES AND TRADEMARKS
=====================================================================

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. The materials at those web sites are not part of the materials for this IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
577 Airport Blvd., Suite 800
Burlingame, CA 94010
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or
any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

[Programming interface information]
Programming interface information, if provided, is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

[Privacy Policy Considerations]
IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.

For more information about the use of various technologies, including cookies, for these purposes, see the IBM Privacy Policy, the IBM Online Privacy Statement section entitled "Cookies, Web Beacons and Other Technologies," and the IBM Software Products and Software-as-a-Service Privacy Statement.

[Trademarks and service marks]
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.

Other product and service names might be trademarks of IBM or other companies.


This product includes software developed by the Eclipse Project
(http://www.eclipse.org/).

Back to top