TIBCO ActiveMatrix Adapter for SAP...TIBCO ActiveMatrix Adapter for SAP Release Notes |iii Contents...

TIBCO ActiveMatrix® Adapter for SAP

Release NotesSoftware Release 6.2.0 March 2012

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE TIBCO ACTIVEMATRIX ADAPTER FOR SAP USER’S GUIDE). USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.

TIB, TIBCO, Information Bus, The Power of Now, TIBCO Rendezvous, TIBCO Designer, TIBCO Adapter, TIBCO InConcert, TIBCO IntegrationManager, TIBCO Administrator, TIBCO Runtime Agent, TIBCO Enterprise Message Service, and TIBCO Hawk are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.

This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. Please see the readme.txt file for the availability of this software version on a specific operating system platform.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 1997-2012 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Terminology and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 6.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 6.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Compatibility and Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

TIBCO ActiveMatrix Adapter for SAP Release Notes

iv |


| 1

Preface

Topics

• Terminology and Acronyms, page 4

• Connecting with TIBCO Resources, page 6


2 | Preface

Typographical Conventions

The following typographical conventions are used in this manual

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco.

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. The directory into which such products are installed is referenced in documentation as ENV_HOME. The value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname


Typographical Conventions | 3

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


4 | Preface

Terminology and Acronyms

Term Definition

ABAP Advanced Business Application Programming is a language in SAP used to write SAP specific code.

ALE/IDoc Application Link Enabling/Intermediate Documents.

API Application Program Interface.

Application Server The server on which the SAP processes run.

BAPI Business API (Functionally equivalent to RFC).

CIF Certified Intermediate Format.

Component A self-contained replaceable functional unit of the adapter that provides a set of interfaces. TIBCO ActiveMatrix Adapter for SAP has two kinds of components; r3Outbound and r3Inbound. r3Outbound encapsulates functionality for outbound communication with the SAP system while r3Inbound encapsulates the functionality for inbound communication with the SAP system.

EDI Electronic Data Interchange.

EMS Enterprise Message Service

Gateway Server A server used to exchange data with the SAP system.

Inbound Instance An adapter configuration listening for messages inbound to the SAP system. Inbound instances transfer messages from the TIBCO environment to SAP.

Interface A functional sub-unit of the adapter that exposes one or more adapter services. For example, the RFCServer interface exposes RFC/BAPI Request-Response Invocation services.

JMS JAVA Messaging Service

MBCS Multi-byte character string.

One Way Invocation protocol

One way invocation protocol allows you to invoke the BAPI/RFC in the SAP system without waiting for a reply from the system.

Outbound Instance An adapter configuration listening for messages outbound from SAP. Outbound instances transfer messages from SAP to the TIBCO environment.


Terminology and Acronyms | 5

RV TIBCO Rendezvous™ protocol; also in certain contexts refers to reliable message quality of service, as opposed to certified message.

RFC The SAP Remote Function Call Interface.

RFC Client A SAP term for any program that can post RFCs/BAPIs/IDocs from an external system into the SAP system.

RVCM TIBCO Rendezvous certified message quality of service.

RFC Server A SAP term for any external program that can accept and process RFCs/BAPIs/IDocs from the SAP system.

RVDQ TIBCO Rendezvous distributed queue.

SAP Native data All SAP data that the adapter interacts with. It consists of RFC data types. This includes IDocs received as RFC tables in an RFC function call.

SSL Secure Sockets Layer.

TID Transaction ID. A globally unique identifier used by transactional RFCs to ensure exactly-once execution of a transaction.

TIDManager Transaction Identifier Manager.

Term Definition


6 | Preface

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO DocumentationAfter you join TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com/TibcoDoc

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibcommunity.com

http://docs.tibco.com/TibcoDoc

http://www.tibco.com/services/support

https://support.tibco.com

| 1

Release Notes

Check the TIBCO Product Support web site at http://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one from the same site. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 5

• Deprecated and Removed Features, page 7

• Compatibility and Migration, page 8

• Closed Issues, page 10

• Known Issues, page 13


2 | Release Notes

New Features

This section lists the new features added since the last major release of this product.

Release 6.2.0• Added Platform Support

Support added for the following platforms:

— AIX 7.1 (POWER)

— Red Hat Linux 5.x (x86_64)

— Red Hat Linux 6.x (x86, x86_64)

— SUSE 10.x, 11 (x86, x86_64)

• The adapter uses SAP JCo 3.0.x libraries for both non-Unicode and Unicode palettes for configuration done using TIBCO Designer.

• (Unicode adapter only) A new property, adr3.rfcBapiReplaceNullFieldsWithSpace, lets the adapter send a space character instead of NULL for the empty fields returned by the SAP system.

• TIBCO Wrapper Generation for SAP is provided that generates wrapper function modules of RFC/BAPI function modules where the table type parameters exist in the function interface. See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for more information.

Release 6.1.0• Added Platform Support

This release of the adapter adds support for the following platforms:

— Microsoft Windows 2008 Server (x86)

— Microsoft Windows 2008 R2 (x86)

— Microsoft Windows 7 (x86)

— SUSE 11 (x86)

— AIX 6.1 (POWER)

— Red Hat Linux 5.x (x86)

• Support for Secure Networks Communications (SNC)


New Features | 3

The Secure Network Communications (SNC) component integrates the adapter with SAP Systems. With SNC, you strengthen the security between the adapter and the SAP system.

See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for more information.

• Support for JMS Compression for the Adapter Publisher

(Unicode adapter only) The property adr3.jmscompress can be used to compress messages while sending messages via the publisher when using JMS transport. See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for more information.

• Added Support for Non Blocking RPC Server

(Unicode adapter only) A new field rfcBapiTimeout has been added in the class RFCCLOSURE. This field is used to specify a value after which the adapter will timeout resulting in server timeout errors. See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for more information.

• Support for JMS Destination Bridges.

You can specify one or more JMS bridges as destinations for the services using JMS transport. The destination can be either a topic or a queue. See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for more information.

• Performance Improvement

Improved performance for the multithreaded adapter when using multiple inbound services configured for a single JMS session.

• Fault Tolerance setup for TIDManager

See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for information setting to the TIDManager in a fault tolerant mode using JMS exclusive queues.

• Memory improvement for larger IDOCs

The adapter now uses memory more efficiently when handling larger IDocs.

See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for information on using the tibco.minstanceimpl property.

• Enhanced error handling for subcriber

(Unicode adapter only)The error messages for handling IDOC errors have been modified to include more information.


4 | Release Notes

Additionally you can configure the adapter to shutdown on receiving an error from the SAP system using the property adr3.stoponsubscribersaperror.

For details see TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment.

• Added Application Support

This release of the adapter adds support for:

— SAP CRM 7 and 2007

— RFCSDK 7.x libraries.

See the TIBCO ActiveMatrix Adapter for SAP readme file for details.

Release 6.0• Support to receive IDocs through qRFC.

This release of the adapter adds support to the outbound unicode adapter to receive IDocs through qRFC.

See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for more information.

To use this feature create a new adapter projects using the unicode version of the adapter. Adapter projects created an earlier version of the adapter cannot be used.

When using QRFC, IDocs should be published from the SAP IDoc qRFC queue in the order they were posted to the queue, provided that the following conditions are met:

— Only one adapter instance publishing from each QRFC queue (multiple Adapter instances could cause the IDocs to be published out of sequence)

— All Publisher services in an adapter instance must publish to the same EMS session.

— Remote TID Manager must be used (not local TID Manager).

— If adapter multithreading is used, all outbound connections must be from the same SAP system and be utilized only for IDoc publication.

• Added Platform Support

This release of the adapter adds support for the HP-UX 11i V3 (Itanium) platform.


Changes in Functionality | 5

Changes in Functionality

This section lists changes in functionality since the last major release of this product.

Release 6.2• For both non-Unicode and Unicode palettes, you can no longer download

using TIBCO Designer RFC/BAPIs containing IMPORT, EXPORT, or CHANGING parameters referring to Table Types or Complex data types. Similarly, if you run a non-Unicode or Unicode adapter against a project created by an earlier adapter release and the schema has references to Table Types or Complex data types, the associated adapter services would be disabled when the adapter starts.

• When using ReadIDocFromFilePlugin you can now have JMS as the transport protocol.

• When using the non-Unicode palette in TIBCO Designer you can no longer connect to an Unicode SAP system.

• Dedicated connections that are part of a connection pool where adr3.maxConnections is greater than one can now be used for inbound transactions to SAP.

• The property adr3.commitid is no longer supported.

• Dropped Platform Support for:

— HP-UX PA-RISC (x86, x86_64) is no longer supported for design-time configuration.

— Red Hat Linux 4.x (x86)

— Microsoft Windows Server 2003 (Enterprise Edition) on x86

— AIX 5.2 on POWER

Release 6.1No change in functionality.

Release 6.0• Dropped Platform Support

— Microsoft Windows 2000 (x86) is no longer supported.


6 | Release Notes

• TIBCO IntegrationManager is no longer supported.


Deprecated and Removed Features | 7

Deprecated and Removed Features

This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features.

This section also lists features that are removed (if any).

Release 6.2

Deprecated Features

No features have been deprecated in this release.

Removed Features

The following features are removed in this release:

• The ActiveMatrix Adapter Service Engine component of TIBCO

ActiveMatrix Adapter for SAP is no longer supported.

Release 6.1No features have been deprecated in this release.

Release 6.0The property adr3.TraceOldMessages has been deprecated.


8 | Release Notes

Compatibility and Migration

This section provides information on the adapter’s compatibility with and its data migration support for other TIBCO applications.

Migration

Migrating from a Non-Unicode SAP System to a Unicode SAP System:

• For correct data conversion, the adapter should be configured in UTF-8 encoded projects.

• Existing 4.x and 5.x projects with ISO8859-1 encoding have to be opened in TIBCO Designer and saved as UTF-8 encoded projects.

• To migrate from a Microsoft Windows platform, update the adr3.locale parameter in the adapter properties file to use a different set of character encoding values. Refer to the Program Internationalization section in TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for details.

Follow the steps below to migrate from a Non-Unicode SAP System to a Unicode SAP System:

1. Open the project in TIBCO Designer.

2. Navigate to the Advanced tab of the ClientConnection as shown below, and select the Is Unicode check box.

This step is not mandatory. The run-time adapter dynamically detects if the target SAP system is Unicode or not. However, this results in a loss of

Make a backup copy of the project before starting the migration process.


Compatibility and Migration | 9

performance during connection time. Select this check box to avoid loss of performance. This is significant particularly for RFC Configurations using the Event-driven Inbound Connection feature.


10 | Release Notes

Closed Issues

This section lists product defects that were closed in the named release

Additionally refer to the TIBCO Adapter SDK Release Notes for closed runtime issues. See Connecting with TIBCO Resources for more information.

Closed in Release Key Summary

6.2.0 ASAP-1068 The ReadIDocfromFilePlugin feature now works as expected when using JMS transport.

6.2.0 ASAP-1086 The value of the LogIdoctoDirectory parameter set in TIBCO Designer is now used during runtime.

6.2.0 ASAP-2067 Adapter subscriber now works as expected when it receives IDocs with 10xcif or 10xbatched mode.

6.2.0 ASAP-2105 If using RFCSDK 7.x, the Request Reply Service now returns exceptions to the calling process.

6.2.0 ASAP-2173 The parameter adr3.preserveFieldBlanks = ON had no effect on Unicode adapters for publishing modes 10xCIF, 10xBatched, and 10xBatchedNL.

6.2.0 ASAP-2248 The adapter was unable to process IDoc files where the Basic IDoc name contained the "/" character.

6.2.0 ASAP-2308 When configuring maxConnections property to 1 in the case of dedicated connections while processing explicit commits from concurrent TIBCO ActiveMatrix BusinessWorks processes, the adapter now returns an error message instead of ending up in state of deadlock.

6.2.0 ASAP-2309, ASAP-2310

If an error occurs and a specific Logical Unit of Work times out the adapter now rolls back the transaction in SAP.

6.2.0 ASAP-2331 Configuration of TID Management using TIBCO Designer can now be saved to a project even though no adapter services have been configured.

6.1.0 ASAP-1211

1-AB32PC

(AIX platforms only) The adapter showed a CPU spike when replying to a BW message when a timeout occurred on the client side for the RPC Server.


Closed Issues | 11

6.1.0 ASAP-1224

1-AP6RZN

The adapter when using multiple threads was not able to handle large data and memory growth was observed.

6.1.0 ASAP-781 Dynamic subjects were not created when using JMS as the transport.

6.1.0 ASAP-646 The trace messages for the subscriber and the publisher did not include the business key.

6.1.0 ASAP-713: Adapter did not handle negative values for the INT4 data type.

6.1.0 ASAP-720 The trace messages for the subscriber and publisher included the incorrect tracking id.

6.1.0 ASAP-888 The adapter terminated when it received an exception for the second time while processing a BAPI/ RFC that has a field of length 30.

6.1.0 ASAP-1162 The adapter would terminate if the RFC had line data type parameters but the error message did not accurately describe the error condition.

The adapter now provides informative error messages during startup.

6.1.0 ASAP-1168 The adapter did not include the tracking info in the log file.

6.1.0 ASAP-1198 (Solaris on x86 only) The unicode version of the adapter terminated when handling errors returned from the SAP system.

6.1.0 ASAP-1098 The value of the commit expiry setting was not saved. The value would change to the default setting.

6.0.0 1-7U5KR7 Custom scalars in custom folders could not be used with AE or RV wire format.

This has been fixed.

6.0.0 1-8JL1ZH The adapter failed to connect to SAP applications when using French as the logon language.


6.0.0 1-8LHVLH Errors were generated when the non-unicode adapter tried to reply to a RFC/BAPI message that contained a slash ('/') character in the parameter name.




12 | Release Notes

6.0.0 1-94WC5R The adapter did not support binary data type.

This has been fixed. The adapter now supports binary data type for the unicode and non-unicode adapters.

6.0.0 1-96HDU3 If a field of type NUMC was not initialized and if the length of the value of the field was less than half the field length, the unused spaces were padded with '#' characters.


6.0.0 1-9DKWGL When an RFC that contained TYPNUM fields in a table parameter was invoked and when the length of the value of the field was less than half of the field length, the return values of TYPNUM fields were set to nil.

This has been fixed. The value is prefixed with zeros.

6.0.0 1-9E5YF9 (Solaris, HP, and HP-Itanium only) The unicode adapter terminated when the last parameter in the table was a fixed field (QUAN, DEC, CURR) and the length of the field was odd.


6.0.0 1-80PG5S You could not save a project after changing the commit expiry parameter to use a global variable.




Known Issues | 13

Known Issues

The table in this section lists product defects known in this release.

Additionally refer to the TIBCO Adapter SDK Release Notes for known runtime issues. See Connecting with TIBCO Resources for more information.

Key Summary/Workaround

ASAP-2388 Summary (HP-UX PA-RISC only) The Discovery Agent does not start up when using the unicode adapter.

Workaround Follow these steps to start the Discovery Agent when using the unicode adapter:

• Make a backup copy of the adr3Discoverer.tra file.

• Edit the adr3Discoverer.tra file and add

%TIB_SDK_DIR%/lib/64 in front of the entry

:%TIB_SDK_DIR%/lib path as shown in the example belowbelow.tibco.env.SHLIB_PATH %CUSTOM_LIB_PATH%:%TIB_ADR3_HOME%/hotfix/lib:%TIB_ADR3_HOME%/lib:%TIB_SDK_DIR%/lib/64:%TIB_SDK_DIR%/lib:%TRA_HOME%/hotfix/lib:%TRA_HOME%/lib:%RV_HOME%/lib:%TPCL_HOME%/lib/64:%TPCL_HOME%/lib:%JVM_LIB_DIR%/hotspot:%JVM_LIB_DIR%

ASAP-2386 Summary The adapter does not support parameters that reference table types or complex/nested data types

Workaround Create a wrapper function module where only simple data types and internal tables are used. If RFC/BAPI contain table type parameters then the TIBCO Wraper Generation for SAP can be used for automatically generating the wrapper function module. See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for more information.

ASAP-2384 Summary The non-unicode version of the adapter does not support String data types.

Workaround Create a wrapper for the RFC/BAPI without the using the String datatype.

ASAP-2357 Summary For inbound transactions with explicit commit (transaction processing), the error messages for log-in failures and unavailable connections are the same.

Workaround None.


14 | Release Notes

ASAP-2351 Summary (10x publication modes only) In case of errors when using the ValidDestination property, information is not logged by the publication service in the file specified by the LogIdoctoDirectory property.

Workaround None.

ASAP-2340 Summary When changing the publication mode from the explodeBatch to explode, the schema associated with the service is incorrect.

Workaround Re-create the adapter service and choose the explode publication mode.

ASAP-2339 Summary When using IDocs of 3.x format and using the explodeBatch publication mode results in errors.

Workaround None.

ASAP-2334 Summary Load balancing with inbound transactions to the SAP system do not worked as expected.

Workaround None.

ASAP-2256 Summary When logging IDocs to a file, the Non-Unicode adapter logs the IDocs in the raw format and the Unicode adapter logs in the XML format.

Workaround None.

ASAP-2066 Summary The .ear file created for a project configured with JMS SSL transport does not include the cert and identity folders.

Workaround Add these folders manually when creating the .ear file from the resource. These folders are available in the Resources tab under Shared Archive.

ASAP-1231 Summary If using different Custom Folders for multiple services, only the first service schema will be included in the .ear file. As a result you see errors such as NodeNotFoundException Node = /tibco/public/class/ae/BBB/basic/IDOCS when the adapter starts up.

Workaround Manually add the missing schemas into the Resource Tab of the .ear file and recreate the .ear file.

ASAP-1066 Summary IDocs sent from the SAP system with packet size greater than 1 are logged incorrectly to the file.

Workaround None.



Known Issues | 15

ASAP-774 Summary The Dynamic Logon feature does not work as expected when using JMS transport.

Workaround Use RV as the transport.

1-UKXC6 Summary (LINUX only) If a request is sent to the adapter for an RFC that is not configured, the adapter exits abnormally.

Workaround None.

1-OU4W1 Summary Moving of adapter instances and services across TIBCO Designer screens is not supported.

Workaround Use the cut and paste feature to move the adapter instances and services across TIBCO Designer screens.

1-MQ8X6 Summary The Dynamic Logon/Logoff feature is not available as an adapter service in TIBCO ActiveMatrix BusinessWorks process configurations.

Workaround Configure a GenericAdapterConfiguration having a Request-Response service with schema pointing to /tibco/public/classes/SAPAdapter40/RFCClient. This service can be used for the Logon and Logoff operations from TIBCO BusinessWorks.

1-8OS3YJ Summary When using JMS as the transport, the Discovery Agent is unable to communicate with the adapter.

Workaround Use RV as the transport.

1-6RRMOR Summary At run-time, the adapter does not support the Remote Function Call (RFC) schema when the RFC name and the structure name are the same.

Workaround

• If using a SAP RFC or BAPI function module, create a wrapper function module and invoke the SAP RFC or BAPI function module inside the ABAP code of wrapper function module.

• If using a custom RFC or BAPI function module, for parameters referring to structures, avoid using the name of the RFC or BAPI as the structure name.

1-5KHTJY Summary The adapter custom datatypes do not get exported with the library builder resource.

Workaround After saving the project, export the resources under the Scalars folder which is located under the ae schema of the AESchemas folder. Import the same whenever the Design-Time Library (DTL) is being used.



16 | Release Notes

1-3YAAP9 Summary The plug-in ReadIDocFromFile cannot read IDoc files that contain non-ISO8859-1 character data written by the Unicode version of the adapter.

Workaround Use TIBCO ActiveMatrix BusinessWorks to read the IDoc file and republish the IDoc.

1-3S2U7V Summary If an adapter instance is configured from a Template with services that do not have schemas associated with them (using the New project from template option), the adapter starts up and exits immediately.

Workaround Make sure the services that the Templates refer to contain at least one schema.

1-1UCNTO Summary In a project, if an IDoc segment name of the Subscriber IDoc schema is the same as that of a Publisher name, the adapter is unable to publish IDocs configured for the Publisher.

Workaround None. Ensure that the IDoc segment name of the Subscriber IDoc schema is not the same as that of the Publisher IDoc segment name.

1-1P7T7U Summary The adapter does not support the SAP data types X, XSTRING, and STRING.

Workaround Use char(n), where n is the length of the datatype that you want to use.

For X data types, change the parameter type from binary.16 to char.16 in the project file



Known Issues | 17

1-19YVXS Summary Latin-1 message encoding is not supported for the JMS and Rendezvous transports when configured to use the XML message wire format.

Workaround To use the XML message wire format, the default message encoding, Latin-1 (ISO8859-1) must be changed to UTF-8. Otherwise, use the Rendezvous transport configured with ActiveEnterprise message wire format. It supports both UTF-8 and Latin-1 message encodings.

The message encoding property is set on the project itself at design-time, and when creating a TIBCO administration domain. The default for both is ISO8859-1.

• To change the message encoding on the project, select the root folder and, under the Project Settings tab, change the value for the TIBCO Message Encoding field. This affects only projects used with Adapter Tester, BusinessWorks Tester and projects exported to local repositories.

• To change the message encoding for the administration domain, edit the repo.encoding property in the administration server's tibcoadmin<domain-name>.tra configuration file, which is located in <install-path>/tibco/administrator/n.n/bin. This affects all projects managed by the administration server.

1-17UIT8 Summary Class references for Publication and Subscription services are broken when a 4.x project is imported into TIBCO Designer.

Workaround Convert the 4.x dat to a multi-file project and then open the multi-file project in TIBCO Designer.



18 | Release Notes


TIBCO ActiveMatrix Adapter for SAP...TIBCO ActiveMatrix Adapter for SAP Release Notes |iii Contents...

Documents

Transcript of TIBCO ActiveMatrix Adapter for SAP...TIBCO ActiveMatrix Adapter for SAP Release Notes |iii Contents...