Release Notes for IBM Transformation Extender, V10.0.2.0

1. Install Design Server:
   a. Download the *.tar.gz file to any Linux OS.
   b. gunzip the *.tar.gz file
   c. tar -xvf the *.tar file
   d. Run ./install.sh script file
   e. Run ./start.sh
2. To interact with the container tx-client run the following from the Linux prompt:
   docker exec -it tx-client /bin/bash
3. cd ssl-certificates/self-signed
4. vi server-crt.cnf and change localhost to the hostname being used for the docker install of Design Server.
5. vi server-crt.ext and change localhost to the hostname being  used for the docker install of Design Server.
6. Under directory ssl-certificates/self-signed verify the script file, genselfsigned.sh.
7. chmod +x genselfsigned.sh to allow execution of the script.
8. Execute:
   . ./genselfsigned.sh
9. You are prompted several times to provide a password phrase. Make sure the password phrase is complex for greater security.
10. Exit from the tx-client container.
11. Stops all four containers (mongodb, redis, tx-client and tx-server) by using the command:
    ./stop.sh
12. Start all four containers (mongodb, redis, tx-client and tx-server) by using the command:
    ./start.sh
13. Open a browser to import the certificate.
14. In the Chrome browser, click on the vertical ellipsis and select Settings.
15. Under Settings, click Advanced.
16. Under Privacy and security select Manage certificates the Certificates window opens.
17. Under the certificates window click Import to install the certificate. When the certificate installs it is displayed under the Authorities tab.

Install the runtime and monitoring server
NOTE: Before using third-party software with IBM Transformation Extender, check with your vendor to ensure that the software is compatible with the operating system.

To install Runtime and Monitoring on Windows systems
On Microsoft® Windows® systems, download and run the executable file. On Windows systems, IBM Transformation Extender products are installed in the following default directory:
C:\IBM\TransformationExtender_n.n.n 
When you install IBM Transformation Extender products on a Microsoft Windows operating system, do not specify C:\Program Files as your target installation location because of compatibility issues.
 

To install Runtime and Monitoring on Linux, zLinux and AIX systems:
A single Linux® and AIX installation provides the Command Server, Launcher, IBM Transformation Extender API and monitoring tools. The supported UNIX® shells are ksh and bash.

. ./setup
Use the dtxcmdsv execution command to run a map with the Command Server.

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

Silent installation records responses during the interactive installation of one Windows system to reuse in the unattended installation of another Windows system.

=====================================================================
IBM APP CONNECT ENTERPRISE (ACE) NOTES
=====================================================================

Prior to IBM App Connect Enterprise (ACE) 11, the IBM Transformation Extender resource registry configuration file was set by the mqsichangeproperties command. As this version of IBM Transformation Extender supports ACE 11, that mechanism is no longer supported by ACE. Instead, perform the following manual steps:

NOTE:  For these steps, the following should be replaced with their actual values:

<MQSI_WORKPATH> The ACE environment variable set by mqsiprofile

<NODE> The integration node (broker) name

<SERVER> The server (execution group) name

Example:
UserDefinedPlugins:
  ComIbmWTXManager:
    resourceConfigFile: C:\IBM\TransformationExtender_n.n.n\resourceconfig.mrc

1. Start an IBM App Connect Enterprise command session.
   
   If  the Welcome to ACE-11 banner displays, a success is indicated. Confirm the success by performing step 2 of this procedure.
   
   If the Welcome banner does not display, a failure is indicated. Confirm the failure by performing step 2 of this procedure.
    
2. If the command session from above, change directory to %MQSI_WORKPATH%\common\profiles and run the dtxwmqi1000_64.cmd script from the command prompt.
    
3. If you see output of the system environment with a list of environment variables the process succeeded.
   
   If you see the errors The input line is too long  and  The syntax of the command is incorrect  You must @rem one or more adapter entries in setTXjarsForACE.cmd to shorten the CLASSPATH, and retest with a new ACE command session.

1.  Open IBM App Connect Enterprise, V11.0.0.4.
2.  Click Help > Install New Software
3.  Click Add.
4.  Click Local.
5.  Browse to <install_dir>\Design Studio\wtx_repo
6.  Click OK.
7.  Select Group items by category.
8.  Select ITX for IBM App Connect Enterprise from the list of categories.
9.  Click Next.
10.  Accept the  new license, then click Finish.

• APAR PH19804 - INCORRECT MAP CARD OR FLOW TERMINAL IS OVERRIDDEN WHEN USING THE TX REST API
• APAR PH19822 - CHANGES TO MAP ARE NOT SEEN AFTER REDEPLOYING

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

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

Apache HDFS adapter
Apache Kafka adapter
Aspera adapter

CICS adapter
Connect:Direct adapter
DB2 adapter
Email adapter
Java-based adapters
JNDI adapter
MIME adapter

OData adapter
ODBC adapter
OpenPGP adapter
Oracle and Oracle AQ adapters

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
The Aspera adapter is supported only on the Linux on Intel® platform.

• 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 an Integration Server runtime environment, run only one map that uses the Connect:Direct adapter, and disable concurrent instances. You still can deploy multiple IBM App Connect Enterprise execution groups to achieve parallel execution.
• When using IBM 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.

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 online documentation .

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

On a Microsoft Windows system:

Before you use the ODBC adapter, you must install the ODBC driver for your specific database. 

For details about using the ODBC adapter, see the online documentation.

Follow these steps to install and configure the ODBC adapter on Windows systems:

1. Install the latest ODBC Driver for your specific database.
2. Go to Administrative Tools and select: ODBC Data Sources (64-bit)
3. Select: Start > Settings > Control Panel > System and Security> Administrative Tools > Data Sources (ODBC)
4. Select the System DSN tab, and click Add.
5. In the Create New Data Source window, select the ODBC driver and click Finish.

1. Install the ODBC driver for your specific database.

2. Edit the $DTX_HOME_DIR/unixODBC/etc/odbc.ini file with the following contents. As an example, for MS SQL Server, use your libmsodbcsql version and location on the "Driver=" entry.
   
   NOTE: The odbc.ini file is an example.  Refer to your ODBC driver vendor for parameter details.
   
   NOTE: The name that you assign to the data source name is what you will use for the ODBC Adapter -SOURCE command.
   
        [<data source name>]
        Driver=<full path to driver library>
        Description=<Optional>
        Trace=NO
        Server=<ipaddress, or hostname>
        Port=<port number>
        Database=<database name>

3. Edit the $DTX_HOME_DIR/unixODBC/etc/odbcinst.ini file with the following contents:
    [<data source name>]
    Driver=<full path to driver library>
    Description=<Optional>
   UsageCount=1
   
   NOTE: In product versions later than 9.0.0.x, the following lines in the $DTX_HOME_DIR/unixODBC folder are part of the setup scrip, and do not need to be manually added:
   
   export LD_LIBRARY_PATH=$DTX_HOME_DIR/unixODBC/linux/lib:$LD_LIBRARY_PATH
   export ODBCINI=$DTX_HOME_DIR/unixODBC/etc/odbc.ini
   export ODBCSYSINI=$DTX_HOME_DIR/unixODBC/etc

4. Run the  . ./setup script from the root installation location.

5. Run the following command to test the connection:
      isql -v <data source name> <userid> <password>

In V10.0.0 and later, 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.

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

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

 

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

• 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 IBM 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 IBM 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 IBM 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 IBM Transformation Extender GUI client application.
• 0 is the value for the server_display that is assigned to the DISPLAY environment variable.

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

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.

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.