What's new in ITX Advanced V9.0.0.2

IBM® Transformation Extender Advanced (ITXA) V.9.0.0.2 offers new features and UI enhancements.

WTX map type is supported in the Document Extract Service

The WTX map type is supported in the Document Extract Service. To do this, use the ITX SPE adapter setDocSplit command to set the Sender/Receiver/AccepterLookupAlias information for each burst. For command details, see the Data harness function syntax topic on the IBM Transformation Extender 9.0.0. knowledge center.

Note: Only a single WTX map is allowed in your DocExtractMapList option. You cannot specify multiple WTX maps, or mix map types (WTX and SI).
Examples are documented in readme.txt files at the following locations:
  •  itx_install_dir/examples/edifact/docextract/readme.txt
  • itx_install_dir/examples/hipaa/docextract/readme.txt
  • itx_install_dir/examples/x12/docextract/readme.txt

HIPAA error acknowledgement

You can select an option to generate a 997 or 999 acknowledgement only when there are errors, and not generate one when the data passes validation. This is done at the Group level.

REST API enhancement:

You can specify SPEOptions such as ReferenceID on import, export, and delete jobs when a translation map is used. This allows the use of delimiters other than the defaults on auto-envelope maps. When multitenancy is being used, it allows a user with System Administrator privileges to include a ReferenceID.

999 acknowledgement available for HIPAA Type 1 validation

You can select a UI option to generate a 999 acknowledgement when performing HIPAA Type 1 validation. Previously, ony a 997 acknowledgement was available.

Option to skip ST/UNH enveloping

You can configure an outbound envelope to skip ST/UNH enveloping. This allows you to re-use existing WTX maps with the ITXA enveloping function without the need to re-write the map. You create your own ST/SE (X12) or UNH/UNT (EDIFACT) segment, instead of having those segments created automatically during the enveloping process.

This allows WTX map types to add a transaction header/trailer. The Enveloping process adds the group or interchange headers, as appropriate.

Unused parameters removed from UI

The Retain envelope parameter is not used with the X12 ISA and GS envelopes or the EDIFACT UNB and UNG envelopes. It has been removed from the UI.

Base64 encoding

Binary data can be passed in Base64-encoded form on REST API calls. This applies to Import jobs or map data, as well as for input for Envelope/Deenvelope/Transform jobs. Examples of data where you might want to use Base64 encoding include the following:
  • X12 data with BIN segments
  • Flat file data that contains binary information
  • Data where the record delimiters, tab characters, or other whitespace characters are significant
  • Compiled maps

In such cases, you want to make sure that the data processed by ITXA is exactly the same as the original data. If the data is passed without using Base64 encoding, some characters may be changed when the data is converted to JSON or XML and then parsed by ITXA.

The REST APIs look for a special prefix of SIB64ENCODE to denote Base64-encoded data follows.

The SPEOption BASE64_OUTPUT_DOCS designates whether output documents generated by ITXA and returned from the REST APIs will be Base64-encoded or not (for example, by the Transform, Envelope, Deenvelope jobs). Valid values are as follows:
NO
Default. Documents are returned by the server unencoded.
YES
Documents are returned by the server as Base64 encoded and the SIB64ENCODE prefix is prepended.

If using the web services browser, some services automatically encode the data in Base64 automatically. For example, use the Browse button to select a map for the Create Map service encodes the data automatically.

If not using the web services browser, you must encode the data in Base64 and prepend the SIB64ENCODE prefix so that the data is handled correctly by the server.

Create, Read, Update, and Delete services

ITXA provides REST APIs to perform Create, Read, Update, and Delete operations on resources, such as maps and envelopes, that are used in the system. These REST APIs can be invoked directly by using a REST client, or invoked programmatically by using REST client example classes or interactively using the web service browser. The Create, Update, and Delete services operate on a single resource at a time. The Read services can be used to list resources based on a given query. The Create, Update, and Delete services provide an alternative to using an Import or Export operation to create, update, or delete resources.

Refer to the documentation for each service and to the REST API documentation at http://localhost:9080/spe/svc/doc for detailed information on the services.