IBM Support

Release notes for Transformation Extender, V9.0.0.3

Release notes


Abstract

These release notes contain the information required to install and configureTransformation Extender, version 9.0.0.3.

Content

© Copyright IBM Corp 2006, 2016 © Copyright HCLTechnologies Ltd. 2017, 2018


=====================================================================
CONTENTS
=====================================================================

About this release
Installation and configuration
API-specific installation
Adapter-specific installation and configuration
Upgrade and migration
Known limitations, problems, and workarounds
New and changed behavior
Resolved Authorized Program Analysis Reports (APARs)
Command Server notes
Software Development Kit notes
Launcher Studio notes
Contacting customer support
Notices and trademarks





=====================================================================
ABOUT THIS RELEASE
=====================================================================

This release is a full version of the product. Transformation Extender Version 9.0.0.3 can coexist on the same computer with earlier point releases of the product starting from Version 8.1.

IBM Transformation Extender (ITX) was formerly called WebSphere Transformation Extender. Documentation, some interfaces, and some web sites might still refer to it as WebSphere Transformation Extender.

Where to find the software to download
To download the software for Transformation Extender Version 9.0.0.3, go to Fix Central.

For details about supported hardware and software, see the system requirements.

After you install the software for this release, go to Transformation Extender Support downloads to download and install any interim fix releases. For details about interim fixes, go to the Transformation Extender Support portal.

Descriptions of the new features in this release are published as technical support documents linked from the New and changed behavior section of these release notes. Additional Transformation Extender V9.0.0 documentation is available only on the knowledge center. No documentation is installed with the product.

You can link to the latest workarounds for known problems in Version 9.0.0 and later releases from the known problems list.

For answers to frequently asked questions and workarounds for known problems in all Transformation Extender releases, review the tech notes that are on the IBM Support website.

The release notes in this document apply to the IBM Transformation Extender components listed below. There are also sections for notes that apply to specific components.

- Transformation Extender with Command Server
- Transformation Extender with Launcher
- Transformation Extender Launcher Studio
- Transformation Extender Design Studio
- Transformation Extender for Application Programming

The Transformation Extender main release notes page links to the release notes for the following components:

Note: Transformation Extender V9.0.0.3 does not support the Launcher Hypervisor Edition. A Launcher Docker image for Linux platforms is available as an alternative.

WebSphere DataPower support

Transformation Extender support for WebSphere DataPower® aligns with and depends upon specific versions of WebSphere DataPower SOA Appliances. Disregard any references to DataPower-specific features in the Transformation Extender documentation and in the Design Studio if there is no alignment of your version of Transformation Extender with WebSphere DataPower SOA Appliances.

For the current alignment of WebSphere DataPower SOA Appliances with Transformation Extender, see the System requirements for IBM DataPower Gateway appliances. Select a version and a WebSphere DataPower SOA Appliance, then click Supported Software > Integration Middleware. For additional detail, click Supported Software > Development Tools.

You can also review the current alignment of WebSphere DataPower SOA Appliances with Transformation Extender Enterprise Application Packs and Industry Packs.


IBM Runtime Environment, Java Technology Edition


Transformation Extender V9.0.0 installs the operating system-appropriate version of IBM® 64-bit Runtime Environment, Java™ Technology Edition, Version 8 SR 5 FP 10.

Use the installed version of the runtime environment. If you configure Transformation Extender to use a different runtime environment, it must be the same version as the installed runtime environment.

The IBM Runtime Environment, Java Technology Edition is not included with the Transformation Extender for z/OS® product, V9.0.0. Transformation Extender for z/OS customers can download it from z/OS or from Shopz.

About translations
IBM Transformation Extender V9.0.0 products are available in the following languages:
  • Brazilian Portuguese
  • English (United States)
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Russian
  • Simplified Chinese
  • Spanish
  • Traditional Chinese

IBM Transformation Extender products display in English if the IBM representative of a country did not choose to translate them.

For the latest documentation, see the English documentation in the knowledge center on the web and the technical support documents linked from the New and changed behavior section of these release notes.


=====================================================================
INSTALLATION AND CONFIGURATION
=====================================================================

Important: The Transformation Extender, V9.0.0.3 fix pack does not support upgrade installation. To install over an earlier release, backup configuration files, uninstall the existing release, and then install the fix pack.



When you use Transformation Extender with another product, ensure that you satisfy the system requirements of the base product and apply all required fixes to the base product. See the support portal for information about product fixes.


On all Microsoft® Windows® operating systems, ensure that the Transformation Extender installation directory has Write permission for the logged-in user. Write permission is required to run a map.


Installing and uninstalling Transformation Extender products

Use the links below for general information about installing and uninstalling Transformation Extender.


Loading and running the Launcher Docker image

The Docker image of Transformation Extender (TX) Launcher is a Linux Ubuntu-based image that contains a full TX V9.0.0.3 Linux X64 Launcher installation that's ready to run in a Docker container.

It's based on a Linux Ubuntu 14.04 base, with updates to the latest packages. It also contains:
- ksh
- rpm
- curl
- gdb
- strace

All TX environment variables are pre-set. The Launcher runs in the container with a DTX_HOME_DIR location of /opt/ibm/wsdtx.

Systems, maps, and data, as well as configuration files like dtx.ini, reside on the host machine and are mounted in the container for access inside the container.

Load the TX Launcher Docker image by using the Docker load command. For example:

docker load -i docker_image_name.tar.gz

You can then see the image by using the Docker images command. For example:

REPOSITORY TAG IMAGE ID CREATED SIZE
itx-launcher-9.0.0/ubuntu 2.65 32135151118a 1 hour ago 866 MB

To run the TX Launcher image, use the Docker run command. These are some of the parameters you can use to run the image:
  • Use the -it (interactive with a terminal) option if you want or need to be in the container to validate mapped volumes, etc.
  • Use the -h option to name the Docker container's host name. This is important if you are running multiple TX Launcher Docker containers and using Launcher cooperative file listening:
    -h <hostname>
  • The -v option allows files and directories on the host to be mapped inside the container. This is typically how TX systems, maps, and data are visible inside the container. You can use multiple -v options on the Docker run command:
    -v <host-directory>:<container-mount>
    • To override the container's dtx.ini configuration file from /home/config/dtx.ini on the host:
      -v /home/config/dtx.ini:/opt/ibm/wsdtx/config/dtx.ini
    • To map the container's TX systems directory for .msl files with /home/systems:
      -v /home/systems:/opt/ibm/wsdtx/systems
    • Similarly, map the host directories where TX maps are located to container directories where the .msl files point to the maps.
  • For HTTP listener ports, the -p option maps ports within the container to the host. Within the container, all containers can reference the same port, but they must be mapped to different host ports:
    -p <host-port>:<container-port>
    Use multiple -p options to map multiple ports to the host.
  • The following option is required for the strace utility, which assists in debugging Launcher issues:
    --security-opt seccomp:unconfined

The TX Launcher Docker image does not start the Launcher automatically. You can use the --entrypoint option of the Docker run command to specify a command to be executed when the image starts. Note that the container exits when the command specified on the --entrypoint ends. If the specified command requires arguments, put them after the image name at the end of the Docker command.

See the Docker documentation for Docker command and usage details.

Potential issues with glibc component on RHEL V6.7 or RHEL V7.2 systems

As described in Red Hat Linux® Bug 1293976 and Bug 1256285, Red Hat Enterprise Linux V6.7 and V7.2 can include a defective version of the glibc component. The affected versions are glibc-2.12-1.149.el6.x86_64 through glibc-2.12-1.163.el6.x86_64. These versions of glibc can cause unpredictable behavior in Transformation Extender.

Enter the following command to display the version of glibc that is installed on your system:

rpm -qi glibc

If you have an affected version of glibc, correct the issue as described in the bug reports before you run Transformation Extender.



Default installation location
IBM Transformation Extender products are installed in the default location
C:\IBM\WebSphere Transformation Extender 9.0.0

When you upgrade from an earlier release, you can reuse existing references to the original installation path (for example, references in batch, configuration, or initialization files) if the original installation path did not specify a version number. To reuse existing references when you upgrade the product, install the new release in the same path as the earlier release.

For example, suppose you installed Transformation Extender V8.4.1 in the C:\WebSphere Transformation Extender directory. To reuse existing V8.4.1 references after you upgrade to V9.0.0, uninstall V8.4.1 and specify C:\WebSphere Transformation Extender as the installation path when you install V9.0.0.


Design Studio integration with IBM Integration Bus Toolkit
In V9.0.0, Transformation Extender Design Studio integrates with IBM Integration Bus Toolkit without the need to install IBM Transformation Extender for Integration Servers run time on the design-time computer. IBM Integration Bus V10.0.0.2 is the minimum required version.


Installing the example files
The Typical installation of Transformation Extender Design Studio does not install example files. Use the Custom installation option to install the example files.

For example, to install the Transformation Extender example files on Windows operating systems:
  1. During installation of the Transformation Extender Design Studio, click Custom installation in the Setup Type window.
  2. Ensure that Example Files is selected in the Select Components window.

Transformation Extender Design Studio installs the example files in the install_dir\examples folder.


Changing the JVM heap size in Design Studio
Transformation Extender Design Studio sets a default Java® Virtual Machine (JVM) heap size. You can adjust the heap size of the JVM to meet the needs of your installation. To change the heap size, edit the C:\IBM\WebSphere Transformation Extender 9.0.0\DesignStudio\wtx_eclipse\eclipse\eclipse.ini file and change the value of the -Xmx1024m parameter. For example, to set the default heap size to 512 MB, change -Xmx1024m to -Xmx512m.


Installing on Windows operating systems
When you install the Transformation Extender products on a Microsoft Windows operating system, do not specify C:\Program Files in your target installation location because of compatibility issues.

Before using third-party software with Transformation Extender installed on your Windows 7 operating system, check with your vendor to ensure that it is compatible with the operating system.


Overriding the default UTF-8 encoding of XML documents
UTF-8 is the default encoding when an XML document does not explicitly specify the encoding. Use the DTX_SCHEMA_ENCODING Language Environment variable to override the default encoding. The encoding that you specify applies to all input and output cards in a map.
  • In a Launcher environment, the encoding applies to the XML input and output of all maps in the Launcher instance.
  • In an IBM Integration Bus environment, the encoding applies to the XML input and output of all maps in the broker where the variable is set.

Specify the code page and export the DTX_SCHEMA_ENCODING variable. For example:

export DTX_SCHEMA_ENCODING=IBM-1047


Malloc-bucket memory allocation in 64-bit Launcher on AIX systems

An APAR in AIX® V7 and earlier versions can cause memory corruption in processes that use malloc buckets. When malloc buckets are enabled, the memory corruption causes crashes or hangs in random Launcher processes on 64-bit Transformation Extender on AIX systems.

To avoid this memory corruption, Transformation Extender V9.0.0 enables malloc buckets only when the AIX APAR is fixed on the computer where the Launcher is installed, because either:
  • The APAR fix is included in the installed version of AIX
  • The required AIX APAR fixes are installed:
When malloc-bucket memory allocation is enabled, the install_dir /tmp/wtxlauncher.log file logs a message that is similar to:

Malloc buckets set Mon Mar  2 13:51:41 EST 2015 HOME:  /AIX_install_dir

The log file is discarded when AIX restarts.

Configuring the size and number of the Launcher system_name_timestamp.log file
The dtx.ini configuration file can specify the maximum size of the Launcher system_name_timestamp.log file and the maximum number of log files to keep before the oldest log file is deleted. See the Launcher documentation for details about the CircularLogSize and CircularLogFileNum options.



Installation error: uncompress not found
The Transformation Extender installation programs for UNIX® operating systems rely on the UNIX uncompress program. The uncompress program might not be available in some Linux installations. If you encounter the "uncompress: not found" installation error, install the uncompress program.


Configuring UNIX environment variables
The environment variables required to execute a Transformation Extender map or system must be set prior to execution.

You can set the environment variables (PATH, DTX_TMP_DIR, DTX_HOME_DIR, and the appropriate library path variable for your platform) by running the setup program.

After you log on to your computer, execute the setup program in the Transformation Extender installation directory before executing a map or system file (using the Launcher). This sets the required environment variables for this session only. Modify the .profile script to set the environment variables for all sessions.

Note: The following command procedure assumes that your UNIX command line environment is the Korn (ksh) shell.

Run the command as follows:

. /install_dir/setup

where install_dir is the directory where you installed the Transformation Extender products. For example, if /home/itx is the installation directory, run the . /home/itx/setup command.

Note: There must be a space between the initial source operator (.) and the command path.


Soft DATA segment or heap size on UNIX systems
The default setting for the Soft DATA segment or heap size parameter can cause problems on UNIX platforms. The root user must reset the Soft DATA Segment value to a value larger than the default.

Note: On AIX platforms, use IBM's smit (System Management Interface Tool) utility to reset the Soft DATA Segment value.

Set this value one time for each user (not for each session). Choosing the correct value depends on the following factors:
  • Amount of memory available on the machine
  • Size of data being processed
  • Type of processing occurring on the respective data
  • Other major applications that run on the machine

If memory permits, start with the default value and increase it as needed. Use the following command to test the value by temporarily setting the value within your own environment:

ulimit -d <value>

Note: When setting the Soft DATA Segment value, the change takes effect only for the current session.


Required IBM XL C/C++ runtime package maintenance level on AIX

If you use the IBM XL C/C++ runtime package on AIX operating systems, you must install the required IBM XL C/C++ runtime package maintenance level 9.0.0.5 or later. To download the PTF, go to http://www.ibm.com/support/entry/portal/Downloads/Software/Rational/XL_C~C++_for_AIX.


HP-UX product requirements
To run the Launcher on HP-UX platform, consider tuning the kernel parameters for max_thread_proc and maxdsiz. The value of maxdsiz depends on the amount of available memory and the size of the data used by the maps. Set maxdsiz to the largest value possible, based on the available memory.


Patch requirement for Red Hat Enterprise Linux on IBM z systems
On computers that run on Red Hat® Enterprise Linux on IBM z systems, you must install the RHEL 5 Server Update 4. Without this update, the Management Console and Launcher Administration trigger a Java exception error.


Microsoft .NET Framework 4.0 requirement
Transformation Extender requires .NET Framework 4.0 to register an assembly such as dtxInterop.dll.
  1. Download and install .NET Framework 4.0.
  2. To ensure that the current dtxCom.dll is registered:
a. Unregister the current dtxCom.dll:
regsvr32 /u dtxCom.dll

b. Register the V9.0.0 dtxCom.dll:
regsvr32 dtxCom.dll

Now you can use Microsoft .NET Framework 4.0 to register assemblies such as dtxInterop.dll. The regasm utility might require you to run the command prompt with administrator privilege.

Invoke the regasm utility from the Microsoft.NET\Framework directory. For example:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm dtxInterop.dll



To do before opening the Design Studio
By default, Eclipse applications cache plug-ins. In certain circumstances, the default Eclipse behavior might prevent Design Studio from opening, cause Design Studio to be unstable or to exhibit the behavior of an earlier release, or cause the run map process to fail.

To avoid these problems, take one of the following steps before you open the Design Studio application:
  • Clear the cached version of the Design Studio plug-ins by running the cleanextenderstudio.bat file. The cleanextenderstudio.bat file is installed at the root of the install_dir directory.
  • Delete the .metadata folder that is in your workspace, and then reimport the workspace, or switch to a different workspace.

Run the cleanextenderstudio.bat file to clear the cached version of the Design Studio plug-ins under the following circumstances:
  • Your workspace got corrupted.

    In this case, the open process fails when Eclipse attempts to open the Design Studio.
  • You installed a patch provided by the Transformation Extender customer support team that copied files to the wtxstudio directory.

    In this case, when Eclipse attempts to open the Design Studio, it uses the cached versions of the Design Studio plug-ins from the prior release on which this patch was installed, which causes the open Design Studio process to fail.
  • You installed a fix pack release on top of a Transformation Extender 9.0.0 release.

    In this case, when Eclipse attempts to open the Design Studio, it uses the cached versions of the Design Studio plug-ins from the prior release on which this fix pack was installed, which causes the open Design Studio process to fail.


Delete the .metadata folder and reimport the workspace, or switch to a different workspace under the following circumstance:
  • You ran a map that could not be loaded into memory, which caused the map to fail and the Design Studio application to terminate abnormally. When you tried to reopen the application, the open process failed.



=====================================================================
API-SPECIFIC INSTALLATION AND CONFIGURATION
=====================================================================

ITX REST API

The ITX REST API is a .war file that you can deploy in any web server that supports the Servlet 3.0 specification, such as Apache Tomcat. These instructions describe how to deploy to Tomcat, but the instructions can be adjusted for other web servers.

These instructions also describe how to create and run a Docker image that contains the ITX REST API.

See the ITX Programming Interface documentation in the knowledge center and the tutorial installed in install_dir\examples\restapi for details about using the ITX REST API.


Installing the ITX REST API in a web server


Prerequisites:

  • A web server that supports Servlet 3.0 containers, such as Tomcat, Glassfish, or Jetty
  • A Redis server to run maps asynchronously or in fenced mode. If you don't require these functions (for example, to use the API for demo purposes), you can use the ITX REST API without a Redis server.

Configuring the tx-rest.properties configuration file

The tx-rest.properties configuration file is installed in the ITX installation directory (install_dir). Comments in the file explain each property.

At a minimum, set the following properties in the tx-rest.properties file. The directories you specify in the configuration file must be existing directories:

  • map.dirs – one or more directories that contain the compiled map files.
  • catalog.dir – the directory where the map catalog file is to be created
  • work.dir – the directory for temporary files used during map execution
  • redis.host – the host (and port) of the Redis server. By default, this is set to localhost.
  • exec.log.dir – the directory where map execution logs are written


Setting up the web server environment

You need to set environment variables for the API to find the ITX jar and library files.

If you are using Tomcat, you can choose either of the following methods to set up the environment variables:

  • The session that starts Tomcat can invoke the $DTX_HOME_DIR/setup script (or %DTXHOME%/DTXCommon.bat on Windows systems) to set up the ITX environment variables,
  • Specify the environment variables in the setenv.sh file in Tomcat's /bin directory. Create the following entries in $CATALINA_BASE/bin/setenv.sh (create the file if it does not exist). Ensure that DTX_HOME_DIR is set to the directory where ITX is installed.

    export DTX_HOME_DIR="/opt/ibm/wsdtx"
    export CATALINA_OPTS="$CATALINA_OPTS -Djava.library.path=$DTX_HOME_DIR/libs"
    export LD_LIBRARY_PATH="$DTX_HOME_DIR/odbc_drivers/lib:$DTX_HOME_DIR/libs:$DTX_HOME_DIR/GSKit/lib64:$DTX_HOME_DIR/java/bin:$DTX_HOME_DIR/java/bin/classic:/opt/ibm wsdtx/java/lib/amd64:$DTX_HOME_DIR/java/lib/amd64/classic:$LD_LIBRARY_PATH"
    export ODBCINST="$DTX_HOME_DIR/odbc_drivers/odbcinst.ini"
    export ODBCINI="$DTX_HOME_DIR/odbc_drivers/odbc.ini"


Deploying the WAR file

The tx-rest.war file implements the REST API for ITX. It's installed in the $DTX_HOME_DIR/restapi directory. Deploy the .war file like any other web application. In the case of Tomcat, copy the .war file to the Tomcat webapps folder, either manually or through the Tomcat web console (for example http://<server>:8080/manager/html/list).

Depending on how your web server is configured, you might need to restart the server after deploying the application.

The console of the web server displays whether the application started correctly. If the application did not start correctly, search the web server's log file for errors related to the tx-rest application.


Validating deployment

After you deploy the tx-rest application, by default, it runs with a context root of tx-rest.

In a browser specify: http://<server>:8080/tx-rest/. If the tx-rest app is running correctly, it reports version and status information:

{
version: "1.0.0",
status: "OK",
name: "ITX Map REST API",
up_time: "0 days, 0 hours, 0 mins, 25 secs"
}

Swagger documentation

To view the Swagger documentation for the ITX REST APIs, enter the following URL in a browser:

http://<server>:8080/tx-rest/api-docs?url=/tx-rest/swagger.json

You can invoke the APIs directly from the Swagger interface by clicking Try it out under each API definition.

Running in a Docker container

Use these instructions to run the ITX REST API in a Docker container. These instructions apply only to the Linux platform.

To build the Docker image:

1. Install ITX for Application Programming.

2. Enter cd /opt/ibm/wsdtx/restapi/docker

3. Run build_image.sh to build the Docker image. If you want to customize the content of the Docker image (such as by adding components), edit the Dockerfile.

4. To confirm that the image is in the Docker repository, run docker images and look for the "tx-rest" image.

5. Create a directory on the host to hold the map files, the catalog, and the map execution log. The directory can be anywhere on the host file system but must contain the following subdirectories:

mydir

mydir/maps

mydir/catalog

mydir/logs

6. Copy your map files to the /maps directory. You can create subdirectories under the /maps directory.

7. The tx-rest Docker image contains ITX and the tx-rest application installed in Tomcat. A Redis docker image is also required.

To run the Docker images:

  • The following command automatically downloads the Redis docker image from the Docker repository:

    docker run --name tx-rest-redis -d -p 6379:6379 redis

  • In the following command, replace mydir with the path of the directory you created in step 5.
    docker run --name tx-rest -it -d -p 8080:8080 --link tx-rest-redis:redis -v mydir:/tx-rest tx-rest

    If you want to invoke the API on a different port, change the -p command. For example, to use port 4444, change the command to -p 4444:8080.

8. Follow the steps described in Validating deployment to test that the server is running.



=====================================================================
ADAPTER-SPECIFIC INSTALLATION AND CONFIGURATION
=====================================================================

Apache HDFS adapter
Apache Kafka adapter
Aspera adapter
CICS adapter
Connect:Direct adapter
DB/2 adapter
Email adapter
Java-based adapters
JNDI adapter
MIME adapter
ODBC adapter
OpenPGP adapter
Oracle and Oracle AQ adapters
SNMP adapter
Sybase adapter




Apache HDFS adapter
The Apache HDFS adapter is supported with Apache Hadoop v2.9.0 or later.


Apache Kafka adapter
The Apache Kafka adapter is supported with Apache Kafka v0.11.0.0 or later.


Aspera adapter platform support
The Aspera adapter is supported only on the Linux on Intel® platform.


Important: Transformation Extender Connect:Direct adapter is thread unsafe on UNIX® platforms

The Command Server runtime environment ensures threadsafe processing when using the new Connect:Direct adapter. To ensure threadsafe processing when using the Connect:Direct adapter in other Transformation Extender runtime environments on UNIX platforms, follow these design guidelines for your solution implementation:
  • In a Launcher runtime environment, run only one map that uses the Connect:Direct adapter, and set the Max Concurrent Map Instances setting to 1. You still can deploy multiple Launcher processes to achieve parallel execution.
  • In a Transformation Extender for Integration Servers runtime environment, run only one map that uses the Connect:Direct adapter, and disable concurrent instances. You still can deploy multiple IBM Integration Bus execution groups to achieve parallel execution.
  • When using Transformation Extender APIs, run only one map that uses the Connect:Direct adapter, and run only one map instance at a time from the same process.


DB2 adapter
For the DB2 adapter to connect with a DB2 database from a Linux, UNIX, or Microsoft Windows system, install an IBM Data Server Client Package. An IBM Data Server Client Package is available for you to download from the internet for free. Select an IBM Data Server Client Package that includes the CLI driver, which the DB2 adapter uses to connect to a DB2 database. When configuring a database connection for a z/OS or IBM i operating system, you also need a DB2 Connect license. For further information about choosing, installing, and configuring an IBM Data Server Client Package, see the IBM DB2 Database for Linux, UNIX, and Windows knowledge center.

Specify the DB2 adapter from either the map command line, for example, -DBTYPE DB2, or from the Database Interface Designer, for example, in the "Adapter Type" field of the "Database Definition" window.

For more details about using the DB2 adapter, see the related topics in the IBM Transformation Extender knowledge center.

ODBC adapter
The ODBC adapter supports both IBM and DataDirect ODBC drivers. ODBC drivers from other vendors might work, but they are not tested for compatibility with Transformation Extender. Because of this, the ODBC adapter is usually better suited for use with IBM and DataDirect ODBC drivers.

However, when designing a map to connect to a DB2 data source that is located on a Linux®, UNIX®, Microsoft® Windows® or z/OS system, you might prefer to use the DB2 adapter. The DB2 adapter connects to the DB2 database without using an ODBC driver manager and still provides all the functionality that is present in the ODBC adapter.

Specify the ODBC adapter from either the map command line, for example, -DBTYPE ODBC, or from the Database Interface Designer, for example, in the "Adapter Type" field of the "Database Definition" window.

For more details about using the ODBC adapter, see the related topics in the IBM Transformation Extender knowledge center.


Support for DataDirect ODBC drivers

Transformation Extender supports DataDirect ODBC drivers release 7.15 on Windows® systems and on UNIX® systems except for Linux for System z®. See the product documentation for details.



Prerequisite procedures for running ODBC adapters with DataDirect ODBC drivers

To run the ODBC adapters with DataDirect ODBC drivers on Windows or UNIX operating systems, you must:
  1. Install the IBM-branded ODBC drivers on Windows or UNIX.
  2. Configure the ODBC DSN on Windows or configure the odbc.ini file to define the ODBC DSN on UNIX.
  3. Configure Transformation Extender to access the ODBC DSN so that you can run maps on Microsoft Windows or UNIX systems.



ODBC User's Guide:

The ODBC User's Guide is available in HTML format on Microsoft Windows and UNIX systems:

Platform Help directory
Microsoft Windows install_dir\odbc\help\help.htm
UNIX install_dir/odbc_drivers/help/help.htm


Installing and configuring IBM-branded ODBC drivers on Windows

To install the IBM-branded ODBC drivers:
  1. Select Custom installation in the Setup program.
  2. Make sure that the component for the "IBM Transformation Extender Branded ODBC Drivers" is selected in the Select Components window.
  3. Enter the selections in the Setup program.


To configure the ODBC DSN:
  1. Select Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).
  2. Select the System DSN tab, and then click Add.
  3. In the Create New Data Source window, select the Transformation Extender IBM ODBC driver for this release and click Finish.
  4. Enter the appropriate values in the window that opens for the Transformation Extender IBM ODBC driver that you selected.
  5. Select the option that tests the connection from the Transformation Extender IBM ODBC driver to the database server that you previously configured. This step is optional.


Installing and configuring IBM-branded ODBC drivers on UNIX

To install IBM-branded ODBC drivers:

Select the appropriate ODBC driver option to install. Specific Transformation Extender product installations include IBM-branded ODBC drivers for the following operating systems:
  • AIX
  • Linux
  • Solaris
  • HP-UX (Itanium®)

The IBM-branded ODBC drivers are installed on the UNIX operating systems listed above under the odbc_drivers subdirectory of the Transformation Extender installation directory. The readme.txt file in the odbc_drivers subdirectory contains details about the contents of the subdirectory, such as the release notes, configuration information, and instructions about how to access the ODBC driver help system.


To configure the odbc.ini file to define the ODBC DSN:

To define the ODBC DSN, configure the odbc.ini file in the odbc_drivers subdirectory. See the ODBC User's Guide.

You must run the Transformation Extender "setup" script before your maps can use the ODBC settings in the odbc.ini file at run time. For details about how to run the "setup" script, see the Configuring UNIX environment variables section. After you run the script, the ODBC library paths are automatically configured.


Configuring access to the ODBC DSN

To configure Transformation Extender to access the ODBC DSN so that you can run maps that use ODBC adapters on Windows or UNIX:
  1. Start the Database Interface Designer (DID) and create a new database query file or open an existing one. A database query file has a .mdq file extension.
  2. Define a new database. Click Database > New.
  3. For the Database Name setting, enter the name of the database that you are defining.
  4. For the "Adapter > Type" setting, select ODBC.
  5. For the "Data Source > Database Interface Designer" setting, enter or select the ODBC DSN that you specified in the "To configure the ODBC DSN" procedure on Windows.
  6. For the "Data Source > Runtime" setting, enter or select the ODBC DSN that you configured on Windows or UNIX. If the map is run on Windows, enter the ODBC DSN that you configured in the "To configure the ODBC DSN" procedure. If the map is run on UNIX, enter the ODBC DSN that you configured in the "To configure the odbc.ini file to define the ODBC DSN" procedure.
  7. Click OK.
  8. When you define a database card in the Map Designer, reference the Transformation Extender ODBC connection with the following parameters:
Parameters Definition
Database Query File This is the name of the file that you used in step 1.
Database This is the name of the database that you defined in step 3.

When you define a database adapter operation in a map rule through the GET, PUT, or DBLOOKUP functions, you can reference the Transformation Extender ODBC connection with the following command-line options:
  • When you use an MDQ file:
Command-line options Definition
-MDQ <mdq file> <mdq file> is the name of the file that you used in step 1.
-DBNAME<db name> <db name> is the name of the database that you defined in step 3.

  • When you do not use an MDQ file:
Command-line options Definition
-DBTYPE ODBC Specifies the ODBC type of database.
-SOURCE <data source> <data source> is the DSN that you used in the "To configure the ODBC DSN" procedure on Windows, and the "To configure the odbc.ini file to define the ODBC DSN" procedure on UNIX.






Configuring Java-based adapters
To configure the Java-based adapters, modify the CLASSPATH environment variable, either directly or by adding the JAR file entries to the [External Jar Files] section of the dtx.ini file. Alternatively, you can add directories that contain JAR files to the [External Jar Directories] section of the dtx.ini file.

The [External Jar Files] and [External Jar Directories] sections are valid only when the adapter is invoked by the Command Server, Launcher, or a non-Java-based API.

For example:

[External Jar Files]
jar N =c:\mypath\myjar.jar

Note: N represents the next available number when there are multiple JAR entries or JAR directories. Environment variables cannot be used in these entries.

For example:

[External Jar Files]
jar1=c:\J2EE\lib\j2ee.jar
jar2=c:\mypath\myjar.jar

To specify directories that contain the JAR files:

[External Jar Directories]
Dir1=c:\J2EE\lib
Dir2=c:\mypath


You can use CLASSPATH environment variables to locate external JAR modules. For example:
  1. Set environmental variable J2EE_HOME to point to the installed directory.
  2. Update the CLASSPATH environment variable as described below.
  3. Platform CLASSPATH Environment Variable
    Windows %J2EE_HOME%\lib\j2ee.jar
    Solaris $J2EE_HOME/lib/j2ee.jar





SNMP adapter and SNMP Agent software requirements
The SNMP adapter is automatically included with all base editions of Transformation Extender. The SNMP Agent is an optionally installed component of Transformation Extender with Launcher.

To use the SNMP adapter or the SNMP Agent, you must install the Java™ Dynamic Management Kit (JDMK) runtime module available from the OpenDMK project.



Installing CICS adapter when Transformation Extender for Application Programming is not installed
Use this procedure to install the required CICS server-side components when Transformation Extender for Application Programming is not installed on a z/OS system. This procedure is not required on a system where Transformation Extender for Application Programming is installed.

The CICS adapter requires the cicssrvr.loadlib file that is shipped with Transformation Extender and is located in the installation directory. The cicssrvr.loadlib file includes server-side components required to use the CICS adapter to connect to CICS.

To install the cicssrvr.loadlib file:

1) Transfer the cicssrvr.loadlib file in binary mode from the
installation directory on your computer to a z/OS data set with
80-byte fixed-length records (RECFM=FB, LRECL=80,
system-determined blksize).

This means no ASCII-to-EBCDIC translation and no
elimination of carriage-return or line-feed characters.

2) After you have installed the file on z/OS, issue the TSO
RECEIVE command to create a load library from it. At the
"READY" prompt, type the following:

receive inda(‘my.upload’)

The following messages are displayed:

INMR901I Dataset MY.UPLOAD from USER on NODENAME
INMR906A Enter restore parameters or 'DELETE' or 'END' +

3) Type the name of the load library to be created as follows:

da('my.loadlib')

Messages are displayed, indicating that the load library is being created.


4) Define the programs to the CICS region that will be
running the CICS adapter server-side components.

The programs can be defined to CICS by adding the following
statements to the CICS CSD definitions. To update the CSD, use
either the DFHCSDUP CICS batch utility program or use the CEDA
transaction and use the following statements as an example:

DEFINE PROGRAM(DTXC3270)
GROUP(DTXCICS)
DESCRIPTION(3270 BRIDGE EXIT)
LANGUAGE(LE)
DATA(ANY)

DEFINE PROGRAM(DTXCDRIV)
GROUP(DTXCICS)
DESCRIPTION(ADAPTER DRIVER)
LANGUAGE(LE)
DATA(ANY)

5) Add the cicssrvr load library to the DFHRPL concatenation
for the CICS region that will be running the CICS adapter
server-side components.




JNDI adapter
The following indicates the supported JNDI drivers for use with the JNDI adapter:

- COS Naming service provider, 1.2.1 release
- DNS Service Provider, 1.2 release
- File system service provider, 1.2 release
- LDAP service provider, 1.2.4 release
- RMI registry service provider, 1.2.1 release





MIME adapter
The MIME adapter requires the j2ee.jar and mail.jar files, or equivalent jar files that contain the J2EE and "javax.mail" classes. These modules are not shipped with Transformation Extender. After installing the .jar files from an appropriate Java Platform, Enterprise Edition installation, modify the CLASSPATH to include the modules.



Oracle and Oracle AQ adapters
See the Transformation Extender system requirements for the supported database versions.
Support for Oracle databases does not include support for the Oracle Exadata platform.




Sybase adapter

With the Sybase adapter, you can connect to the Sybase Adaptive Server Enterprise (ASE) and Sybase IQ databases. See the Transformation Extender system requirements for the supported database versions. See the Sybase adapter documentation for the list of supported data types.





Email adapter configuration

To use any email adapter, you must update the dtx.ini file on the runtime system.

On a Microsoft Windows system:
1. Edit the install_dir\dtx.ini file. The install_dir is the directory where Transformation Extender is installed.
2. Search for the string [JVM Options], and set option1 as follows:

option1=-Djava.ext.dirs= install_dir\java\lib\ext; install_dir\extjar

On a UNIX system:
1. Edit the install_dir/config/dtx.ini file. The install_dir is the directory where Transformation Extender is installed.
2. Search for the string [JVM Options], and set option1 as follows:

option1=-Djava.ext.dirs= install_dir/java/lib/ext: install_dir/libs/extjar



OpenPGP adapter
In V9.0.0, the OpenPGP adapter is installed as part of the base product.

Downloading the GnuPG libraries for the OpenPGP Adapter
This release of the OpenPGP adapter supports GnuPG V1.4.2 and later for Windows and UNIX® operating systems.

The OpenPGP Adapter uses the Gnu Privacy Guard (GnuPG) third-party product to perform the functionality required by the adapter. To use the OpenPGP Adapter, you must first download and install the GNU PG libraries from the GNU website.
  • For Windows operating systems, the binary images for the GnuPG product are available for download.
  • For UNIX operating systems, you must download and recompile the GnuPG source to generate the binary images.
After you download and install the GnuPG files, use the following instructions to configure the location of the GnuPG (gpg.exe) executable file for the OpenPGP Adapter.

Configuring the gpg.exe file location in the Windows registry

The OpenPGP Adapter requires the following change to the registry for it to determine the location of the GnuPG (gpg.exe) executable file.

To specify the location of the GnuPG gpg.exe file in the registry:
  1. Click Start > Run and enter regedit to launch the Registry Editor.
  2. Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\GNU\GNUPG key.
  3. Right click on the GNUPG key, select New > String Value from the menu, and name the string value gpgProgram.
  4. Double-click gpgProgram to assign a value to it.
  5. In the Value field, enter the full path to the GnuPG gpg.exe file. For example:
    C:\IBM\GNU\GnuPG\gpg.exe
  6. Click OK.
  7. Select File > Exit to exit the Registry Editor.

Configuring the gpg.exe file location on UNIX systems

The Transformation Extender OpenPGP Adapter requires the GPG_PATH environment variable to be set to the directory of the GnuPG gpg executable file. Use either of the following methods to set the GPG_PATH environment variable:
  • Add the setting of this variable to the user login profile, so that it is always set.
  • Add it to the bottom of the setup script that contains all of the environment variables needed by Transformation Extender.

If you use the /usr/local/bin default installation location, add the following line to the setup script:
export GPG_PATH=/usr/local/bin



=====================================================================
UPGRADE AND MIGRATION
=====================================================================

Transformation Extender V9.0.0 supports 64-bit platforms only

Because Transformation Extender V9.0.0 supports 64-bit platforms only, Connect:Direct integration is not supported on the Windows platform.

Changes to anyType XML schema fields prevent older maps from compiling

A fix to the native schema type tree to properly process anyType XML schema fields changed the format of the type tree. Because anyType fields include anyAttribute, additional levels are added to the native schema type tree to handle any attributes that might occur in the data. As a result, maps older than V9.0.0.2 do not compile because the path to these elements changed.

To eliminate the need for remapping, set the new ITX_NS_NOANYTYPE environment variable to TRUE. When enabled, ITX_NS_NOANYTYPE forces the Transformation Extender native schema type tree generator to create the type tree identical to the one before the anyAttribute fix was added.

Running Transformation Extender with locally vs globally installed GSKit

Transformation Extender installs a local version of IBM Global Security Kit (GSKit) in the install_dir /GSKit directory. Local GSKit installation enables Transformation Extender to automatically run its installed version of GSKit without additional software installation or environment configuration.

IBM products that Transformation Extender integrates with might use:
  • A local version of GSKit that is installed by that product
  • A global version of GSKit that is installed by the GSKit installation program.
    When globally installed, the security modules of GSKit are available on a system-wide basis.

To prevent Transformation Extender from using its locally installed version of GSKit, rename the install_dir /GSKit directory. At run time, Transformation Extender searches the platform-specific environment path for the GSKit modules.


64-bit support for EXIT structure of C API
Customers who use the C Exit must rebuild their EXIT library for V9.0.0.


Change to resolution of relative paths for some interfaces that use files as arguments

In earlier releases, Transformation Extender changed from the directory of the currently running process to the map directory before it ran a map.

For example, before running the /home/abc_acct/8413/maps/myoracle.mmc map, Transformation Extender changed from the directory of the currently running process to the /home/abc_acct/8413/maps directory. If the myoracle.mmc map used a relative path to specify files, the path resolves relative to the map directory. In this example, Transformation Extender creates an adapter trace file called m4oracle.mtr in the /home/abc_acct/8413/maps directory if the trace file was defined with any of the following relative paths:
../../8413/maps/m4oracle.mtr  
./m4oracle.mtr
m4oracle.mtr

Transformation Extender V9.0.0 does not change to the map directory before it runs a map. V9.0.0 resolves relative paths by appending the relative path to the directory of the currently running process. The following interfaces are affected by this change:
  • Custom functions that use files as arguments
  • Adapter trace files in IBM Transformation Extender for Integration Servers integrations
  • API implementations that open files after calling a map

For example, the following xmllib functions that can specify files as arguments are affected:

xmllib->XSLTEX( "ipo.in.xml", "ipo.xsl", "transform.log")
  • The first two arguments can be data or a file.
  • The third argument is always a file.

xmllib->XPATHEX( "ipo.in.xml", "./order//item[1]/shipDate", "/ipo:purchaseOrders ", "xpathlog.txt")
  • The first argument can be be data or a file.
  • The fourth argument is always a file.
xmllib->VALIDATEEX( "ipo.in.xml", " http://www.example.com/IPO  ipo.xsd", "numtotext.log"
  • The first argument can be data or a file.
  • The second argument is always a file (optionally prefixed by default name space).
  • The third argument is always a file.

To restore the pre-V9.0.0 behavior so that affected relative paths resolve relative to the map directory, set the environment variable DTX_CHDIR=TRUE. In a multi-threaded environment such as Launcher or Transformation Extender for IBM Integration Bus, all of the maps must run in the same directory to ensure thread safety.

On UNIX systems:

export DTX_CHDIR=TRUE

On Windows systems:

set DTX_CHDIR=TRUE

For best results, use an absolute path for adapter trace files. You can use the GETDIRECTORY function to dynamically build an absolute path.


Native XML schemas with prologs must use XSD as the type of the main input card
When a native XML schema has a prolog, the Type setting of the main input card must be XSD (the root of the XML document). A parser error results when the XML schema has a prolog and the Type setting specifies a sub-element of the root.

As a general practice, use XSD as the Type setting in the main input card of all native XML schemas. The XSD setting parses correctly regardless of whether the schema includes a prolog.

For all Xerces type trees, use Doc XSD as the Type setting of the main input card, regardless of whether the XML document has a prolog. Parsing errors can result if the XML document includes a prolog and you specify a sub-element of Doc XSD as the Type setting of the main input card.


Recompile existing V8.4.1.1 maps that use the Standards Processing Engine adapter

A map that uses the Standards Processing Engine (SPE) adapter to run adapter action commands such as ENVELOPE, DEENVELOPE, and TRANSFORM must be compiled with Transformation Extender V8.4.1.2 or later. To upgrade a map that you developed with Transformation Extender V8.4.1.1, delete the existing  Response.mtx file and recompile the map using the updated Response.xsd file that is included with a later version of Transformation Extender. The schema for the SPE adapter response was updated in V8.4.1.2. A map must use the new version of the Response.xsd file to correctly process the SPE response.



Maps cannot reuse work files from earlier releases
Transformation Extender V8.4.1 and later work files are not compatible with work files from earlier releases. If a map reuses work files that were created with an earlier release, you must delete the work files and run the map to create new work files that are compatible with version 8.4.1 and later.


Custom function memory allocation on Windows systems

Transformation Extender version 8.4 and later releases require custom functions that run on Microsoft Windows systems to use the new mpiMemMalloc and mpiMemRealloc memory management functions to allocate or reallocate the lpDataFromApp buffer.


Migrating maps, type trees, and systems


Maps, type trees, and systems from versions 5.0 and later can be used with V9.0.0 and later. You must regenerate systems. Although it is not always required for running maps from an earlier version, you should reanalyze and save the type trees, and save and recompile the maps; otherwise, the processes must convert the files each time they load the files.

See additional considerations in Maps cannot reuse work files from earlier releases.

  • If you are migrating from V8.0 to V9.0.0, you must run your database triggering scripts in order to successfully run source-triggered database systems. After V9.0.0 is installed on the supported Oracle or SQL Server databases, no earlier release of Transformation Extender can use triggering on that database, because the client and source reference different names.
  • To use the new code page functionality, you must make new selections for the Data Language and National Language type properties in your type trees.

  • If you previously used a non-international version of Transformation Extender (formerly DataStage TX or Mercator), Native has been redefined to be Latin1 instead of ASCII.
  • During installation, if you are prompted to register this version as the default program for opening Transformation Extender file types and you choose "Yes," all Transformation Extender files, such as *.mtt or *.mms, open with this version.

Opening Files from an earlier version
When you save a source file from an earlier version of a Transformation Extender product in the current version, the content and structure of that file is automatically converted to the format for the current version.

After conversion to the current version formats, do not open these files in earlier versions of a Transformation Extender product component. After conversion, the format of the source has changed and there are added features that are not supported in the earlier versions.
  • *.mtt files are converted in memory when the file is opened. The backup *.omt file is created when the file is saved.
  • *.mms files do not need to be converted for the current version.
  • A map created in an earlier version opens in the current version.
  • *.msl files do not need to be regenerated. They are converted dynamically.
  • *.mmc files do not need to be recompiled.
  • *.msd files still work the same way, creating an *.osd when the file is opened.
  • *.mdq files open in the current version.


Preparing maps to run in this version
  • Analyze each type tree file for logic and structure and then save it in the current version of the Type Designer.
  • Regenerate type trees for queries, tables, and stored procedures.
  • For maps that will be executed using a current version of the Command Server or Launcher, build all maps using the equivalent (current) version of the Map Designer.
  • Build and generate the Launcher system (.msl) file or the command file for all systems defined in the current version of the Integration Flow Designer.
  • If you have designed maps that could produce 0 bytes of data to an adapter (this is especially critical for R/3 adapters), you must change the OnSuccess setting to CreateOnContent or use the -XO adapter option.
  • When you open a map that references a custom adapter or an adapter that is no longer supported in version 9.0.0, the Source or Target in the Edit Card window is blank. The map builds successfully, but returns a "Source not available" or "Target not available" message when it executes. The solution is to select an adapter from the list in the Edit Card window.


Performance of maps
If you are migrating from an earlier version, you should be aware of the relative performance of running maps in this version.



=====================================================================
KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS
=====================================================================

For the latest information, see the list of known problems and workarounds.


=====================================================================
NEW AND CHANGED BEHAVIOR
=====================================================================

For an overview of new features in this release, see the What's New information in the knowledge center.


Deprecated functions, components, and platforms
The following functions, components, and platforms are deprecated in V9.0.0 and later:
  • tbcconv utility
Use the API instead.
  • WSDL Classic Importer
  • Solaris SPARC platform
  • HP-UX Itanium platform
  • SLES for x86
  • SLES for z/Series
  • 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

For version 9.0.0 and higher, Windows and Solaris clustering are no longer supported

32-bit platforms are no longer supported

Removed Transformation Extender components:
  • Launcher Agent
  • Secure adapter collection
The OpenPGP adapter is installed with the base product. The S/MIME adapter is removed.

Removed APIs and utilities:
  • CORBA API
  • dtxmapconv utility
  • dtxxmlconv utility
  • MSLDump utility
Removed adapters and adapter functions:
  • CORBA adapter
  • Simple MAPI protocol support (Transformation Extender Email adapter)
  • S/MIME adapter
  • WebSphere Email adapter
  • WebSphere FTP adapter


Disregard any references to these components in the documentation.


=====================================================================
RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARs)
=====================================================================

Review the list of APARs that are resolved in IBM Transformation Extender V9.0.0.3.



=====================================================================
COMMAND SERVER NOTES
=====================================================================

These notes are for the Command Server component of the following products:
- IBM Transformation Extender with Command Server
- IBM Transformation Extender with Launcher
- IBM Transformation Extender Design Studio


Installation information
Because procedures for Command Servers for Windows, HP-UX, AIX, and Solaris platforms might differ slightly, the installation program provides specific instructions to guide you.

The Command Servers for Microsoft Windows are components of the client installation and are installed with the IBM Transformation Extender with Command Server and IBM Transformation Extender with Launcher. These Command Servers are also available as components of the Command Server installation for Windows-based platforms to be installed on your server for runtime purposes.

The HP-UX, AIX, and Solaris Command Servers are components of each platform-specific Command Server server installation for runtime purposes.

The additional Command Servers for z/OS (Batch and CICS) are available on platform-specific media. For system requirements and installation procedures for these Command Servers, see the platform-specific release notes and the Program Directory.


Additional UNIX runtime information
You must manually set the shared library path according to your platform.

Do not execute the setup program if you want to configure the environment variables manually. Instead, use the DTX_TMP_DIR environment variable to set the location of temporary files, as described in the following procedure.

Set location for temporary files (DTX_TMP_DIR)
During map execution, the Command Server creates temporary files for resource handling and for retaining debug information. The default directory for these temporary files is /tmp. To specify a different directory for temporary files, set the DTX_TMP_DIR environment variable. For example:

DTX_TMP_DIR=install_dir/tmp
export DTX_TMP_DIR

If multiple users or groups are to access the Command Server engine, define DTX_TMP_DIR instead of using the default /tmp directory. Define and export the DTX_TMP_DIR variable manually or with the setup script. The directory specified for DTX_TMP_DIR must have permission 777 to provide permission to the user, the group, and all others. Define and export the DTX_TMP_DIR variable before you set the directory permission. To set the permission, run the chmod command:

chmod 777 $DTX_TMP_DIR


Enabling environmental debug information (DTX_DEBUG)
When the DTX_DEBUG environment variable is defined, the Command Server can produce environmental diagnostic information that can be helpful when a problem is encountered during map execution. By default, the DTX_DEBUG environment variable is not defined and environmental diagnostic information is not recorded.

When you define the DTX_DEBUG environment variable, environmental diagnostic information is recorded in a file named dtxinfo.log located in the directory defined by the DTX_TMP_DIR environment variable (or in the /tmp directory, if DTX_TMP_DIR is not defined).


To enable the environmental debug facility, set the DTX_DEBUG environment variable to TRUE. For example:

DTX_DEBUG=TRUE
export DTX_DEBUG

To disable the environmental debug facility, set the DTX_DEBUG environment variable to FALSE. For example:

DTX_DEBUG=FALSE
export DTX_DEBUG

The following is a sample of the information contained in the environmental debug file:

PROCESS_ID: 2309, API_REF: 1
Date/Time: Fri Jul 25 14:30:09.279783 2012
FILE: mercmain.c, line: 714
info: [IBM WebSphere Transformation Extender Product
Version: 0.0]

PROCESS_ID: 2309, API_REF: 1
Date/Time: Fri Jul 25 14:30:09.280252 2012
FILE: mercmain.c, line: 744
info: [IBM WebSphere Transformation Extender RUNNING:
Fri Jul 25 14:30:09 2012]

PROCESS_ID: 2309, API_REF: 1
Date/Time: Fri Jul 25 14:30:09.470357 2012
FILE: mercrun.c, line: 1951
New Map File - Fri Jul 25 14:30:09 2012
[/install_dir/examples/general/map/sinkmap/sinkmap.mmc]


Tracing I/O problems (DebugName and DebugAppend)
You can enable the DebugName and DebugAppend options in the [Connections Manager] section of the dtx.ini file to enable the Command Server to trace I/O-related problems.


Setting shared libraries environment variables
After you install mapping components on UNIX platforms, set the appropriate shared object path environment variable to access the shared libraries. This procedure varies slightly depending on the platform being used.

For example, to set this variable for an IBM AIX platform, enter:

LIBPATH=$LIBPATH: install_dir /libs
export LIBPATH

Note: Because the AIX platform caches shared libraries, if you update a shared library on the disk, you will not be able to see the update. Use the slibclean command as the root user to remove the old shared library from system memory.

To set this variable for an HP-UX platform, enter:

SHLIB_PATH=$SHLIB_PATH: install_dir /libs
export SHLIB_PATH

To set this variable for Solaris platform, enter:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH: install_dir /libs
export LD_LIBRARY_PATH

Note: In these examples, install_dir /libs is the directory where the shared libraries are located.


=====================================================================
SOFTWARE DEVELOPMENT KIT NOTES
=====================================================================
The following Software Development Kit components are automatically included when you install the Design Studio. Any base version of Transformation Extender can be used as the runtime environment with the Software Development Kit:
  • Transformation Extender for Application Programming
  • Transformation Extender with Command Server
  • Transformation Extender for Integration Servers
  • Transformation Extender with Launcher


IBM Transformation Extender for Application Programming Interface requirements

The IBM Transformation Extender Programming Interface consists of C, COM, Java, REST, and RMI APIs.

The required header files, library files, and IDLs for these APIs are located in the following directories:

Files Windows Directory UNIX Directory
Headers install_dir $install_dir/src
Library install_dir $install_dir/libs
IDLs install_dir\idl $install_dir/idl
Schemas install_dir $install_dir/src
JARs install_dir\tools


Linking an application to an alternate ICU library version

This release of IBM Transformation Extender uses ICU version 55.1.0.

A Transformation Extender Application Programming Interface (API) user can link an application to a version of ICU other than ICU V55.1.0 by including the ICU version's lib names in the link line.

For example, to link your application to ICU V3.4.1, use the following link line:

-licuuc341 -licuuc18n341 -licudata341

If you do not want to specify the version numbers in the link line, the ICU team recommends that you start the icu-config script from the $(ICU_INSTALL)/bin/ directory.

To start the icu-config script, include the following code in your makefile:

ICU_LDFLAGS=`$(ICU_INSTALL)/bin/icu-config --ldflags-libsonly`

If you are using ICU V3.4.1, the icu-config script returns the following required link lines:

-licui18n341 -licuuc341 -licudata341



=====================================================================
LAUNCHER STUDIO NOTES
=====================================================================

These notes are for the Launcher Administration, Management Console, and Resource Registry components of the IBM Transformation Extender Launcher Studio.

Resource Registry trace file
Use the [Launcher] logging options in the install_dir \dtx.ini configuration file to set the Resource Registry trace options. The trace file logs encrypted aliases and displays them as masked values.

Configuration requirements in non-Windows environments
To use these products in a non-Windows environments, the X Window server must be running on the local host machine or system. You must set the DISPLAY environment variable and export it.

The DISPLAY environment variable identifies the X Window server that is to display the X Window Transformation Extender GUI client. The syntax might vary depending on the shell version that you are using. To set the DISPLAY environment variable:

export DISPLAY=<display_name>:<server_display[.screen_number]>

  • The DISPLAY environment variable name must be in uppercase letters.
  • The display_name is the IP address or domain name of the local host machine that is to display the X Window Transformation Extender GUI client application.
  • server_display is the number assigned to the X Window server that is to display on the host machine.

Because most local host machines have a maximum of one display monitor, keyboard, and mouse, in most cases, you specify the server_display as :0, and omit the screen_number .

If your system has more than one monitor (display screen) as in multi-headed systems, each monitor is identified by a unique screen number. You specify the screen_number by appending it to the end of the X server_display specification, for example, :0.1. The default screen_number is 0, which refers to the primary screen, and when it is 0, you do not need to specify it; for example, you can specify only the server_display simply as :0.

Example 1:

export DISPLAY=mycomputer.ibm.com:0

Where:
  • mycomputer.ibm.com is the domain name of the local host that is to display the X Window Transformation Extender GUI client application.
  • 0 is the value for the server_display that is assigned to the DISPLAY environment variable.

The host system exports the value to the X Window client so that it will display the X Window Transformation Extender GUI client application on the primary screen of the computer with the mycomputer.ibm.com domain name through the X server assigned as 0.

Example 2:

export DISPLAY=192.168.1.110:0

Where:
  • 192.168.1.110 is the IP address of the local host that is to display the X Window Transformation Extender GUI client application.
  • 0 is the value for the server_display that is assigned to the DISPLAY environment variable.

The host system exports the value to the X Window client so that it will display the X Window Transformation Extender GUI client application on the primary screen of the computer with the 192.168.1.110 IP address through the X server assigned as 0.


Display errors in non-Windows environments
To avoid display errors related to font.properties when starting the Launcher Administration, Management Console, or Resource Registry, ensure that the display X server has access to all fonts used in the font.properties of the Java installation.

On Solaris JVMs, the font.properties consistently refer to fonts that are not included with Exceed. This can sometimes cause problems such as distortions when displaying GUIs. To resolve this problem, a customized font.properties can be placed in your $HOME/lib directory, which will remove references to the problem fonts.


=====================================================================
CONTACTING CUSTOMER SUPPORT
=====================================================================

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


=====================================================================
NOTICES AND TRADEMARKS
=====================================================================
This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.

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, MD-NC119
Armonk, NY 10504-1785
US

HCL
330 Potrero Ave.
Sunnyvale, CA 94085
USA
Attention: Office of the General Counsel


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

HCL
330 Potrero Ave.
Sunnyvale, CA 94085
USA
Attention: Office of the General Counsel


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 jurisdictions 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 websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide 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 Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US

HCL
330 Potrero Ave.
Sunnyvale, CA 94085
USA
Attention: Office of the General Counsel

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.

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.

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 actual people or business enterprises 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. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.


Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered 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.

  • Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
  • 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.
Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following terms and conditions.

Applicability
These terms and conditions are in addition to any terms of use for the IBM website.

Personal use
You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.

Commercial use
You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.

Rights
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy Statement

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 IBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details in the section entitled “Cookies, Web Beacons and Other Technologies,” and the “IBM Software Products and Software-as-a-Service Privacy Statement” at http://www.ibm.com/software/info/product-privacy.


Document information

More support for: Transformation Extender

Software version: 9.0.0.3

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows, z/OS

Reference #: 7051084

Modified date: 11 May 2018


Translate this page: