IBM Support

Release notes for IBM Transformation Extender Pack for SAP Applications V10.2.0.0

Release Notes


Abstract

This document provides information about the release of the IBM Transformation Extender Pack for SAP Applications V10.2.0.0

Content

IBM Transformation Extender Pack for SAP Applications, V10.2.0.0 release notes.

© Copyright IBM Corporation 2006, 2016. All Rights Reserved.
© Copyright HCL Technologies Ltd, 2017, 2021. All Rights Reserved.

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

1. About this release
2. Installation for Linux design environment
3. Installation for Windows design environment
4. Manual installation of the packs for SAP applications v10.2.0.0 onto ITX v10.1.2
5. Manual installation of the packs for SAP applications v10.2.0.0 onto ITX v11.0.0
6. Design server examples
7. Known Issue and Workaround 
8. Resolved Authorized Program Analysis Reports (APARs)
9. Contacting customer support
10. Notices and trademarks

 


=====================================================================
1. ABOUT THIS RELEASE
=====================================================================

These release notes provide information about the Pack for SAP Applications for users of these IBM Transformation Extender products:

  • Design Server
  • Design Studio
  • Runtime and Monitoring  

WHAT'S NEW IN THIS RELEASE
  • SAP S/4 HANA Adapter
  • SAP S/4 HANA Examples
  • X509CERT option to support Secure Network Communications
  • Module installers for SAP adapters in ITX 10.1.1 

DOCUMENTATION
The documentation for this release is provided in the IBM Transformation Extender online documentation.
SAP Applications latest 10.2.0 documentation is available in the 10.1.1 online documentation, see What's new in Packs V10.2.0 for more details. 
Translated documentation

The online documentation is provided in these languages:

  • English (United States)
  • French
For the latest product information, see the English version in the IBM Transformation Extender online documentation.

To display translated content in the online documentation:

  1. Open the online documentation. A typical URL to the documentation is shown below:
    https://www.ibm.com/support/knowledgecenter/SSVSD8_n.n.n/com.ibm.websphere.dtx.welcome.doc/kc_welcome_nnn.html
  2. Edit the URL to include the desired language code immediately after "/knowledgecenter":
    https://www.ibm.com/support/knowledgecenter/<language code>/SSVSD8_n.n.n/com.ibm.websphere.dtx.welcome.doc/kc_welcome_nnn.html
  3. As an example, enter language code "/fr" to display French content.
  4. Remove the "/<language code>"  to return to the English display.


=====================================================================
2. INSTALLATION FOR LINUX DESIGN ENVIRONMENT
=====================================================================

WHERE TO FIND THE SOFTWARE TO DOWNLOAD

To download the software for this version of the IBM Sterling Transformation Extender Pack for SAP Applications, go to Passport Advantage. This location will direct you to the Passport Advantage (PA) and Passport Advantage Express (PAE) overview page. Passport Advantage (PA) and Passport Advantage Express (PAE) are comprehensive IBM programs by which Clients may order Eligible Products. Customers can search PA and PAE for the following part numbers to download files for windows install and Red Hat OpenShift which include the project files used with the Design Server and certified containers.

Part numbers for SAP Applications 10.2.0.0, search:

  • Windows install - G04NVML
  • Red Hat OpenShift - G04TFEN

The install file is one of the following, depending on which IBM Transformation Extender Core version is in use:

  • itxsap_1020_1000_linux.zip 

  • itxsap_1020_1003_linux.zip 

  • itxsap_1020_1010_linux.zip 

  • itxsap_1020_1011_linux.zip 

These zip files contain:

  • itxsap_10.2.0.0_linux.tar
  • itxsap_10.2.0.0_libs.tar
  • itxsap_10.2.0.0_libs.zip
  • SAP_pack_examples_unix.zip
  • PEPPOL_example_unix.zip (for ITX 10.0.3 and later)

INSTALLING THE PACK ON LINUX

Follow these steps to install the Pack for SAP Applications on Linux:
  1. Create a temp directory called sap.
    Example:
    /home/user/itx10/sap
  2. FTP (in binary mode) the itx_sap_10.2.0.0_linux.tar to the sap directory defined in step 1.
  3. Untar the file.
    Example:
    $ tar -xvf itx_sap_10.2.0.0_linux.tar
  4. Obtain the following user provided libraries from SAP JCo 3.1.4 or later:
    libsapjco3.so
    sapjco3.jar
         a.  For Design Server, copy these files into the folder defined by ITX_ADDITIONAL_LIBS in tx-server.env from your Design Server installation.  By default this is /opt/txlibs.
         b.  For Runtime and Monitoring, copy these files into $DTX_HOME_DIR/libs.
  5. Main installation:
    a.  For Design Server:
    For ITX v10.1.0 and earlier, Execute the install script:
    Run the install_sap_ds.sh script. For ITX v10.1.1, copy the .zip files from the modules directory into the folder defined by TX_MODULES_DIR in tx-server.env from your Design Server installation. By default, this is /opt/txmodules.  Then restart tx-server.
     b.  For Runtime and Monitoring:
     For a native installation run the install_sap_rt.sh script.
     For a docker installation, run the install_sap_rt_docker.sh script.   
INSTALLING THE PACK TO RUNTIME AND MONITORING ON UNIX (OPTIONAL)
FTP (in binary mode) the itxsap_10.2.0.0_libs.tar to the <install_dir>/tmp directory.
  1. Unzip the file to the install_dir/libs directory.
    Example:
    $ tar -xvf itxsap_10.2.0.0_libs.tar -C $DTX_HOME_DIR/libs/
  2. Obtain the following user provided libraries from SAP JCo 3.1.4 or later and copy to the <install_dir>/libs directory:
    libsapjco3.so
    sapjco3.jar

  3. In the adapters.xml file, located in $DTX_HOME_DIR/config, in the Runtime and Monitoring installation, the following lines need to be present and not commented out.
    As shipped:
            <!-- <M4Adapter name="JBAPI" alias="JBAPI" id="160" type="app" class="com/ibm/websphere/dtx/m4r3bapi"/> -->
            <!-- <M4Adapter name="JALE" alias="JALE" id="161" type="app" class="com/ibm/websphere/dtx/m4r3ale"/> -->
    For the Pack for SAP , the following lines must read as shown below:
        <M4Adapter name="JBAPI" alias="JBAPI" id="160" type="app" class="com/ibm/websphere/dtx/m4r3bapi"/>
        <M4Adapter name="JALE" alias="JALE" id="161" type="app" class="com/ibm/websphere/dtx/m4r3ale"/>

UNINSTALLING THE PACK
Follow these steps to uninstall the pack from Windows systems:

  1. Click Control Panel > Add/Remove Programs.
  2. Select the pack that you want to remove.
  3. Click Change/Remove and follow the prompts.

=====================================================================
3. INSTALLATION FOR WINDOWS DESIGN ENVIRONMENT
=====================================================================

WHERE TO FIND THE SOFTWARE TO DOWNLOAD

The Pack for SAP Applications can be obtained from Passport Advantage.
 

BEFORE YOU INSTALL THE PACK

Installation prerequisites:
Before you install the pack, you must install one of the following versions of Transformation Extender:

  • 9.0.0.4
  • 10.0.0.0
  • 10.0.3.0
  • 10.1.0.0 or later
  • 10.1.1.0

If you are installing “Design Studio” and/or “Runtime and Monitoring” with Design Server, make sure those are fully installed before installing the Pack for SAP Applications.  If you install Design Server after installing the Pack for SAP Applications, you will need to re-install the Pack for SAP Applications.

Default installation path
On Microsoft Windows systems, the default install location is one of:

  • C:\IBM\WebSphere Transformation Extender 9.0.0
  • C:\IBM\TransformationExtender_10.0.0
  • C:\IBM\TransformationExtender_10.0.3
  • C:\IBM\TransformationExtender_10.1.0
  • C:\IBM\TransformationExtender_10.1.1

INSTALLING THE PACK ON WINDOWS

Follow these steps to install the Pack for SAP Applications on Windows:

  1. Obtain the product image from Passport Advantage.
  2. Run one of the following commands specific to your ITX core version:
    itxsap_1020_900.exe
    itxsap_1020_1000.exe
    itxsap_1020_1003.exe
    itxsap_1020_1010.exe
    itxsap_1020_1011.exe
  3. The third-party SAP JCo files must be obtained from SAP.  Obtain the following user provided libraries from SAP JCo 3.1.4 (or later) for 64-bit Windows:
    sapjco3.dll
    sapjco3.jar
  4. Copy these SAP JCo files to both the <install_dir> and the <install_dir>\saplibs directory.
  5. For Windows Design Server on ITX 10.1.1, copy the .zip files from <install_dir>\sapmodules to the folder defined by TX_MODULES_DIR in <install_dir>\DesignServer\tx-server-env.bat.  By default, this is C:\IBM\txmodules.
INSTALLING THE PACK ON LINUX OR UNIX RUNTIME (OPTIONAL)
Third party SAP JCo files (.jar and .so files) must be obtained from SAP.
Follow these steps to install the Pack for SAP Applications on Linux or UNIX:
 
  1. Copy the following SAP JCo, files to the install_dir/libs directory:
    sapjco3.jar
     libsapjco3.so
If you prefer, you can complete these steps after installation:
  1. Install the Pack for SAP Applications on Windows, as described above.
  2. Copy the file sap_pack_libs.tar from the Windows <install_dir> to the Linux or UNIX machine where it will be installed.
  3. Extract the sap_pack_libs.tar file into the Linux or UNIX <install_dir>/libs dir.
    Example:
    $ tar -xvf sap_pack_libs.tar -C $DTX_HOME_DIR/libs/
  4. In the adapters.xml file, located in $DTX_HOME_DIR/config, in the Runtime and Monitoring installation, the following lines need to be present and not commented out.
    As shipped:

    <!-- <M4Adapter name="JBAPI" alias="JBAPI" id="160" type="app" class="com/ibm/websphere/dtx/m4r3bapi"/> -->
            <!-- <M4Adapter name="JALE" alias="JALE" id="161" type="app" class="com/ibm/websphere/dtx/m4r3ale"/> -->
     

    For the Pack for SAP Applications, the following lines must read as shown below:
        <M4Adapter name="JBAPI" alias="JBAPI" id="160" type="app" class="com/ibm/websphere/dtx/m4r3bapi"/>
        <M4Adapter name="JALE" alias="JALE" id="161" type="app" class="com/ibm/websphere/dtx/m4r3ale"/>
     

DESIGN STUDIO EXAMPLES
The SAP examples can be found in <install_dir>\examples\sap and can be used in Design Studio.

UNINSTALLING THE PACK
Follow these steps to uninstall the pack from Windows systems:
  1. Click Control Panel > Programs > Programs and Features.
  2. Select the pack that you want to remove.
  3. Click Uninstall and follow the prompts.
To uninstall the pack on Linux, or UNIX, delete the following files:
  • $DTX_HOME_DIR/libs/dssap.jar
  • $DTX_HOME_DIR/libs/m4r3ale.jar
  • $DTX_HOME_DIR/libs/m4r3bapi.jar
  • $DTX_HOME_DIR/libs/p4saphana.jar (if present)
  • $DTX_HOME_DIR/libs/sapjco3.jar
  • $DTX_HOME_DIR/libs/libsapjco3.so
 Comment out the entries in $DTX_HOME_DIR/config for the JALE and JBAPI adapters.

==============================================================================
4. MANUAL INSTALLATION OF THE PACK FOR SAP APPLICATIONS V10.2.0.0 ONTO ITX v10.1.2
==============================================================================

Follow these steps to install the Pack for SAP 10.2.0.0 manually onto ITX  v10.1.2:

  1. Install the ITX v10.1.1 Design Studio.
  2. Install Pack for SAP 10.2.0.0 on ITX v10.1.1.
  3. Install the ITX v10.1.2 Design Studio.
  4. Copy the following files from C:\IBM\TransformationExtender_10.1.1 to C:\IBM\TransformationExtender_10.1.2: 
    • dssap.jar 
    • m4r3ale.jar
    • m4r3bapi.jar
  5. Copy the files sapjco3.dll and sapjco3.jar from SAP JCo 3.1.6 or later to both C:\IBM\TransformationExtender_10.1.2 and C:\IBM\TransformationExtender_10.1.2\saplibs (create this directory if it doesn't exist).
  6. Edit the adapters.xml file to uncomment lines for JBAPI and JALE. Navigate to C:\IBM\TransformationExtender_10.1.2\adapters.xml to uncomment lines for JBAPI and JALE.
  7. Install SAP importers to Design Studio.
  8. Run ITX v10.1.2 Design Studio.
  9. Go to Help > Install New Software…
  10. Type or select a site in "Work with" and click “Add…”.
    Once you click “Add…”, Add Repository window opens.
  11. Click on “Local…” and navigate to C:\IBM\TransformationExtender_10.1.1\DesignStudio\wtx_repo\itxsapstudio. The Location field contains file:/C:/IBM/TransformationExtender_10.1.1/DesignStudio/wtx_repo/itxsapstudio/ and click “OK”.
  12. Uncheck “Group items by category” and select “ITX SAP Pack Importers Feature” and Click “Next”.
  13. Select the terms of the license agreements and click “Finish”. The Security Warning window opens. 
  14. Click “OK” on the Security Warning.
  15. After installing, import SAP BAPI. The Error window opens with the error message “Error when loading importer with the reason”.
  16. Click “OK” and proceed. This error is not significant and the BAPI importer will function as designed. Maps using the JALE and JBAPI adapters will run with no problems.

==============================================================================
5. MANUAL INSTALLATION OF THE PACK FOR SAP APPLICATIONS V10.2.0.0 ONTO ITX v11.0.0
==============================================================================
 

Follow these steps to install the Pack for SAP 10.2.0.0 manually onto ITX  v11.0.0:

  1. Install the ITX v10.1.1 Design Studio.
  2. Install Pack for SAP 10.2.0.0 on ITX v10.1.1.
  3. Install the ITX v11.0.0 Design Studio.
  4. Copy the following files from C:\IBM\TransformationExtender_10.1.1 to C:\Program Files\ibm\TransformationExtender_11.0.0: 
    • dssap.jar 
    • m4r3ale.jar
    • m4r3bapi.jar
  5. Copy the files sapjco3.dll and sapjco3.jar from SAP JCo 3.1.6 to both C:\Program Files\ibm\TransformationExtender_11.0.0 and C:\Program Files\ibm\TransformationExtender_11.0.0\saplibs (create this directory if it doesn't exist).
  6. Edit the adapters.xml file to uncomment lines for JBAPI and JALE. Navigate to C:\Program Files\ibm\TransformationExtender_11.0.0\adapters.xml to uncomment lines for JBAPI and JALE.
  7. Install SAP importers to Design Studio.
  8. Run ITX v11 Design Studio.
  9. Go to Help > Install New Software…
  10. Type or select a site in "Work with" and click “Add…”.
    Once you click “Add…”, Add Repository window opens.
  11. Click on “Local…” and navigate to C:\IBM\TransformationExtender_10.1.1\DesignStudio\wtx_repo\itxsapstudio. The Location field contains file:/C:/IBM/TransformationExtender_10.1.1/DesignStudio/wtx_repo/itxsapstudio/ and click “OK”.
  12. Uncheck “Group items by category” and select “ITX SAP Pack Importers Feature” and Click “Next”.
  13. Select the terms of the license agreements and click “Finish”. The Security Warning window opens. 
  14. Click “OK” on the Security Warning.
  15. After installing, import SAP BAPI. The Error window opens with the error message “Error when loading importer with the reason”.
  16. Click “OK”and proceed. This error is not significant and the BAPI importer will function as designed. Maps using the JALE and JBAPI adapters will run with no problems.

=====================================================================
6. DESIGN SERVER EXAMPLES
=====================================================================

IMPORTING THE  EXAMPLE PROJECTS INTO DESIGN SERVER

The examples are available in zip files which can be imported as a project into Design Server.

If you are using a Linux Design Server, use the files from within itxsap_1020_<core_version>_linux.zip:
  • SAP_pack_examples_unix.zip
  • PEPPOL_example_unix.zip
If you are using a Windows Design Server, complete the Windows installation and use the files from <install_dir>/examples/sap:
 
  • SAP_pack_examples_windows.zip
  • PEPPOL_example_windows.zip
The SAP_pack_examples_<platform>.zip file contains ALE, DXOB, BAPI, and EDI examples. For ITX v10.1.1, it also includes SAP S/4 HANA examples.
The PEPPOL_example_<platform>.zip file contains the PEPPOL examples. This is only available for ITX v10.0.3 and later.
Use these instructions to import the sample projects into Design Server:
NOTE: You must have Administrator privileges to import projects.
NOTE: To preserve the project description that is shipped with the pack, do not enter any additional information description during the project import.
  1. Login to the Design Server.
  2. In the Design Server click the Import Project icon.
  3. In the Import Project dialog, click browse and select a zip file described above.
  4. Click the Import button to import the project.

RUNNING THE ALE EXAMPLE ON DESIGN SERVER

There are two scenarios included:
  • Inbound map to post data to an SAP system.
  • The map LegacyToInboundJALE is used to post data inbound to an SAP system. The data is mapped from an input card which reads legacy data for customers. This map uses the schema debmas03, which represents the customer master IDoc object debmas03.
To run this scenario:
Open the LegacyToInboundJALE map.
  1. Edit the settings of output card IDOC_ALE.  In the Edit Target window, select the Connection tab to change the Command Line, where you will see “-c 800 -u user -p password -h hostname -s 00 -tv -ar3”.  Update the -c, -u, -p, -h, and -s parameters for the adapter commands specific to your SAP installation. Click Next, Next, and OK to save the settings.
  2. Save, build and run the LegacyToInboundJALE map.
  3. Check the IDoc in the SAP system to view its status.
Outbound map to receive data from an SAP system
The map JALEOutboundToLegacy:
This map receives data from an SAP system and maps it to a legacy file. It uses the start method for ALE  communication. This map also uses the debmas03 schema.
 
  1. Open the JALEOutboundToLegacy map.
  2. Edit the settings of input card ALE_Data.  In the Edit Source window, select the Connection tab to change the Command Line, where you will see -a example.rp5 -g gatewayhost -x 3300 -tv -ar3”.  Update the -a, -g, and -x parameters for the adapter commands specific to your SAP installation. Click Next, Next, and OK to save the settings.
  3. Save, build and run the JALEOutboundToLegacy map.
  4. Send an IDoc from your SAP system, and it will be received by this map.

RUNNING THE DXOB EXAMPLE ON THE DESIGN SERVER

In this example, the legacy data is used to map to the data format for a DXOB structure. The DX object used for this example is the Customer Master (0050).
How to run the example:
  1. Open the LegacyToDX0050 map.
  2. Build and run the LegacyToDX0050 map.
  3. From the Map Diagram-Result window, hover over the LegToDXOB map and choose View Data to view the output file (leg_dxob.txt).

RUNNING THE BAPI EXAMPLE ON THE DESIGN SERVER
This directory contains sample files to be used for the integration with SAP ERP using the Pack for SAP JBAPI adapter.
In this example, the JBAPI adapter is used to call a BAPI in the SAP system.  The data returned by the BAPI is passed to a second map using the RUN function.
The BAPI schema used in this example is BAPI_CUSTOMER_GETDETAIL, generated for the BAPI function BAPI_CUSTOMER_GETDETAIL
The bapi_example folder contains two maps. The map, xSingleStyle, has the BAPI structure as well as a second output card, which makes the actual BAPI call. The second map, xBapiInput, is used to map the data returned from the BAPI call.
How to run the example:
  1. Open the xBapiInput example map in the Map Designer.
  2. Build the xBapiInput map.
  3. Open the xSingleStyle example map in the Map Designer.
  4. Modify the BAPI card to have the Importing Parameter CUSTOMERNO refer to a valid customer number.
  5. Modify the xBapi card, to have the GET make a valid call. The connection parameters in the default command line "-h host -s 00 -u user -p password -c 800 -t" need to be changed to reflect the SAP system  to be called.
  6. If the bapi_creditor_getdetail type tree has been changed according to a different SAP ERP version, additional fields might need to be mapped.
  7. Build the xSingleStyle map.
  8. Run the xSingleStyle map.
  9. From the Results tab of the Map Diagram window, click the ‘select activity’ icon next to the xBapi map and choose View Data to view

RUNNING THE EDI EXAMPLE ON THE DESIGN SERVER

The EDI example directory includes two subdirectories:

The 850_to_Orders05 directory contains an example map with an EDI 850 input and ORDERS05 IDoc output.

The invoice02_to_810 directory contains an example map with an INVOIC02 IDoc input and EDI 810 output.

How to run the 850_to_Orders map in the Design Server:

  1. Open the 850_to_Orders map in the EDI\850_to_orders05 directory.
  2. Build and run the 850_to_Orders map.
  3. Right click the output1 target and choose View Data to view the output file.

How to run the InvoicePackets map in the Design Server:

  1. Open the InvoicePackets map in the EDI\invoice02_to_810 directory.
  2. Build and run the InvoicePackets map.
  3. Right click the 810Invoice target and choose View Data to view the output file.
RUNNING THE S4 HANA EXAMPLE ON DESIGN SERVER

These examples require an account on SAP.com with access to the SAP API Business Hub. This account gives you an API Key, a 32-digit alphanumeric code.

  1. From the Design Server home screen, choose Deploy > Configuration Variables.
  2. Add a new variable with name “SAPAPIKEY” and value of your API Key.
  3. Open the SAP_pack_examples project imported earlier.
  4. Note that these examples use pre-defined Connections and Actions objects.  The Connections use Base Headers of “apikey=%SAPAPIKEY%”, using the Configuration Variable defined in step 2.

Test the API_CUSTOMER_MATERIAL_SRV API (OData V2: https://sandbox.api.sap.com/s4hanacloud/sap/opu/odata/sap/API_CUSTOMER_MATERIAL_SRV/):

  1. Open the CustomerMaterial map in the S4HANA/customer directory.
  2. Build and run the CustomerMaterial map. This map is associated with the API_CUSTOMER_MATERIAL_SRV Connection and A_CustomerMaterial action.
  3. Right click the output1 target and choose View Data to view the output file. 

Test the API_PLANNED_ORDERS API (OData V2: https://sandbox.api.sap.com/s4hanacloud/sap/opu/odata/sap/API_PLANNED_ORDERS/):

  1. Open the PlannedOrder map in the S4HANA/orders directory.
  2. Build and run the PlannedOrder map. This map is associated with the API_PLANNED_ORDERS Connection and A_PlannedOrder action.
  3. Right click the output1 target and choose View Data to view the output file.
  4. The PlanedOrder_GET map demonstrates using a GET rule with an SAPHANA command line instead of a Connection and Action. 
Test the Bank API (OData V4: https://api.sap.com/api/BANK_0002/)
  1. Open the Bank map in the S4HANA/bank directory.
  2. Build and run the Bank map. This map is associated with the Bank 0002 Connection and Bank_Source action.
  3. Right click the output1 target and choose View Data to view the output file.
  4. The Bank_GET map demonstrates using a GET rule with an SAPHANA command line instead of a Connection and Action.
RUNNING THE PEPPOL EXAMPLE ON DESIGN SERVER

The PEPPOL example is available in the PEPPOL_example_<platform>.zip file, which is imported as a project into the Design Server.

If you are using a Linux Design Server, use the file PEPPOL_example_unix.zip from within  itxsap_1020_<core_version>_linux.zip.

If you are using a Windows Design Server, complete the Windows installation and use the file <install_dir>/examples/sap/PEPPOL_example_windows.zip.

Follow these steps to run the PEPPOL examples:
 
For PEPPOL to SAP:
  1. Open the map: from_ubl_invoice.
  2. Build and run the map.
  3. From the Results tab, click the More options (vertical ellipse) icon and choose View Data.
 For SAP to PEPPOL:
  1. Open the map: to_ubl_invoice.
  2. Build and run the map.
  3. From the Results tab, click the More options (vertical ellipse) icon and choose View Data.

=====================================================================
7. KNOWN ISSUE AND WORKAROUND
===================================================================== 

When using Design Server on Windows with a Configuration Variable (for example %SAPAPIKEY% in the examples), and you run a map, you may get "An unexpected error occurred".

If the server log contains an error "java.nio.file.NoSuchFileException: C:\IBM\TransformationExtender_10.1.1\configvar.mkf", as a workaround: copy <install_dir>\DesignServer\configvar.mkf to <install_dir>\configvar.mkf

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

For a list of APARs that are fixed in this version of the product, see the fix list.

When using the SAP S/4 HANA adapter with OData V4, apply patch APAR PH42049 (m4odata.jar). Contact customer support for more information

=====================================================================
9. CONTACTING CUSTOMER SUPPORT
=====================================================================

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

=====================================================================
10. NOTICES AND TRADEMARKS
=====================================================================

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

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

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

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

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

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

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

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

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

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

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

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

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

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

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

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

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

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

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

COPYRIGHT LICENSE:

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

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

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

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

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

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

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

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

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

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

Trademarks and service marks
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml .

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSPVY6A","label":"IBM Sterling Transformation Extender Pack for SAP Applications"},"ARM Category":[{"code":"a8m0z000000bmMnAAI","label":"Pack for SAP Applications"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF055","label":"zLinux"}],"Version":"10.2.0"}]

Document Information

Modified date:
05 August 2024

UID

ibm16516444

Page Feedback