TIBCO ActiveMatrix Adapter for SAP · SAP products, including SAP ECC 6.0 re leases and SAP...

Two-Second Adv

TIBCO ActiveMatrix® Adapter for

SAP

Release NotesSoftware Release 7.2.0February 2016

antage®

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 LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. 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.TIBCO, Two-Second Advantage, TIBCO Hawk, TIBCO Rendezvous, TIBCO Runtime Agent, TIBCO ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO Designer, TIBCO ActiveMatrix Service Gateway, TIBCO BusinessEvents, TIBCO BusinessConnect, and TIBCO BusinessConnect Trading Community Management are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and 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. SEE THE README 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 © 1999-2016 TIBCO Software Inc. All rights reserved.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTIBCO ActiveMatrix Adapter for SAP Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viThird-Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiHow to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

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

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Migrating from 6.2.x/7.x.0 to 7.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Migrating from 6.1.0 and Earlier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

TIBCO ActiveMatrix Adapter for SAP Release Notes

iv | Contents


| v

Preface

TIBCO ActiveMatrix® Adapter for SAP is used as a bidirectional gateway between SAP applications and applications configured for the TIBCO environment.

The adapter can remotely connect and operate with SAP systems running on OS platforms not supported by the adapter.

Topics

• Related Documentation, page vi

• Typographical Conventions, page ix

• Connecting with TIBCO Resources, page xii

TIBCO ActiveMatrix Adapter for SAP Installation

vi | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO ActiveMatrix Adapter for SAP DocumentationThe following documents form the TIBCO ActiveMatrix Adapter for SAP documentation set:

• TIBCO ActiveMatrix Adapter for SAP Concepts Read this manual for terminology and concepts of the product. The other manuals in the documentation set assume you are familiar with the information in this manual.

• TIBCO ActiveMatrix Adapter for SAP Installation Read this manual for instructions on site preparation and installation.

• TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment Read this manual for instructions on how to create, configure, and deploy adapter projects.

• TIBCO ActiveMatrix Adapter for SAP Examples Read this manual to work through the examples provided with the adapter.

• TIBCO ActiveMatrix Adapter for SAP Release Notes Read the release notes for a list of new and changed features. This document also contains lists of known issues and closed issues for this release.

• TIBCO ActiveMatrix® Adapter for SAP (TIBCO Business Studio™) Documentation Read this documentation for instructions on how to install, configure and deploy the adapter in TIBCO ActiveMatrix BusinessWorks™ 6.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:

Table 1 TIBCO Products (Sheet 1 of 2)

TIBCO Product Description

TIBCO ActiveMatrix BusinessWorks This product provides an integration platform that enables companies to rapidly integrate systems and automate business processes.


Preface | vii

Third-Party DocumentationYou may also find it useful to read the documentation on the following websites:

• http://help.sap.com

This website is the SAP Help Portal where you can find documentation on all SAP products, including SAP ECC 6.0 releases and SAP NetWeaver. In order for TIBCO ActiveMatrix Adapter for SAP to exchange data with SAP systems,

TIBCO ActiveMatrix Adapter for SAP (TIBCO Business Studio)

This product provides a design-time environment to configure adapter configurations and TIDManager configurations in TIBCO Business Studio™.

TIBCO® Adapter SDK This product provides a class library that helps developers implement an adapter with minimal effort.

TIBCO Administrator™ This product provides capabilities for managing users, monitoring machines, and deploying and managing applications that use TIBCO products.

TIBCO Business Studio This product provides capabilities that help business analysts document business processes, solution engineers implement business processes, and SOA developers create composite applications.

TIBCO Designer™ This product provides a graphical user interface to create TIBCO ActiveMatrix BusinessWorks process definitions, or create or modify TIBCO Adapter configurations.

TIBCO Enterprise Message Service™ This product sends messages from your applications in a format that conforms to the Java Messaging Service (JMS) specification.

TIBCO Hawk® This product is for monitoring and managing distributed applications and systems throughout the enterprise.

TIBCO Rendezvous® This product uses messages to enable distributed application programs to communicate across a wide variety of hardware platforms and programming languages.

TIBCO Runtime Agent™ This product is a bundle of TIBCO software and third-party software that is required to run many TIBCO applications such as TIBCO ActiveMatrix BusinessWorks, TIBCO Adapters, and so on.

Table 1 TIBCO Products (Sheet 2 of 2)

TIBCO Product Description


http://help.sap.com

viii | Related Documentation

you must make configuration in the SAP system to allow for communication and the exchange of messages to take place. This website offers detailed information on such configuration required.

• http://service.sap.com/instguides

This website is provided by the SAP Support Portal and contains documentation on installations and upgrades. The documentation available contains information on components that can be used along with TIBCO ActiveMatrix Adapter for SAP, and the installation of the Secure Network Communications (SNC) libraries where security is required between the adapter and SAP systems.

• http://service.sap.com/connectors

This website provides information on the different types of SAP Connectors available. TIBCO ActiveMatrix Adapter for SAP is based on the SAP Java Connector libraries. You can download the latest versions of these libraries from this website. For more information on the SAP JCo libraries and configuration related to these libraries, see the available documentation from this website.


http://service.sap.com/connectors

http://service.sap.com/instguides

Preface | ix

Typographical Conventions

The following typographical conventions are used in this manual.

Table 2 General Typographical Conventions

Convention Use

ENV_NAME

TIBCO_HOME

TIBCO products are installed into an installation environment. A product installed into an installation environment does not access components in other installation environments. Incompatible products and multiple instances of the same product must be installed into different installation environments.

An installation environment consists of the following properties:

• Name Identifies the installation environment. This name is referenced in documentation as ENV_NAME. The default value is TIBCO_HOME.

• Directory The folder into which the product is installed. This folder is referenced in documentation as TIBCO_HOME.

TIB_ADR3_HOME TIBCO ActiveMatrix Adapter for SAP is installed into a directory within a TIBCO_HOME directory. This directory is referenced in documentation as TIB_ADR3_HOME. The default value of TIB_ADR3_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco\adapter\adr3\ReleaseNumber.

TIB_DESIGNER_HOME TIBCO Designer is installed into a directory within a TIBCO_HOME directory. This directory is referenced in documentation as TIB_DESIGNER_HOME. The default value of TIB_DESIGNER_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco\designer\ReleaseNumber.

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].


x | Typographical Conventions

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix Adapter for SAP 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.

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 2 General Typographical Conventions (Cont’d)

Convention Use


Preface | xi

Table 3 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand param1 | param2 | param3

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}


xii | Connecting with TIBCO Resources

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is 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 TIBCO DocumentationDocumentation for this and other TIBCO products is available on the TIBCO Documentation site:

https://docs.tibco.com

Documentation on the TIBCO Documentation site is updated more frequently than any documentation that might be included with the product. To ensure that you are accessing the latest available help topics, please visit us at https://docs.tibco.com.

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, 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.tibco.com/services/support


http://www.tibcommunity.com


| 1

Release Notes

This document includes release notes for TIBCO ActiveMatrix Adapter for SAP, Software Release 7.2.0.

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

Topics

• New Features, page 2

• Changes in Functionality, page 3

• Deprecated and Removed Features, page 4

• Migration and Compatibility, page 5

• Closed Issues, page 6

• Known Issues, page 8



2 | Release Notes

New Features

The following new features have been added to version 7.2.0 of TIBCO ActiveMatrix Adapter for SAP.

Support for Connection Properties

For Request-Response Invocation Service that uses the RV or EMS transports, or for Publication Service that uses the EMS transport, the following connection properties are available:

• SAPJCO_RFCDESTINATION

• SAPJCO_CLIENT

• SAPJCO_CPICCONVID

• SAPJCO_HOST

• SAPJCO_SYSID

• SAPJCO_USER

Support for Schema Management

When upgrading an existing ActiveMatrix BusinessWorks project, the SAP schemas can be refreshed in the original directory by adding java.property.adr3.schemapath.fixed = true to the TIBCO Designer TRA file and restarting TIBCO Designer.

Support for New Platforms

This release supports Microsoft Windows Server 2008 R2 SP1, 2008 SP1, 2008 SP2, and Red Hat Enterprise Linux 7.x.


Changes in Functionality | 3

Changes in Functionality

The following are changes in functionality in version 7.2.0 of TIBCO ActiveMatrix Adapter for SAP.

IDocFormat Publish Mode

The IDocFormat publish mode supports the raw IDoc format.

Outbound RFC/BAPI Error Delivery

When invoking an Outbound RFC/BAPI with the Request/Reply invocation protocol, if an error occurs, the error returned back to the adapter is forwarded to the SAP system.

New Trace Messages

The following trace messages are newly added for Outbound IDocs when the packet size is greater than one:

• AER3-970041

• AER3-970042

• AER3-970043

• AER3-970044

Inbound TID Management

When invoking an Inbound RFC/BAPI with the One Way invocation protocol, if the TID attribute in the RFCCLOSURE class is not populated with an actual value, TID management can be ignored.

If Inbound TID management is active and no valid value is provided for the TID attribute, the warn trace message, AER3-000501, is displayed.


4 | Release Notes

Deprecated and Removed Features

The following tables list any features that have been deprecated or removed for version 7.2.0 of TIBCO ActiveMatrix Adapter for SAP.

For deprecated features, if relevant, useful alternatives to the deprecated features are listed. Any use of a deprecated feature should be discontinued as it might be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features.

Deprecated Features

Removed Features

Affected Component Description Deprecated in Release

Publication Service and Subscription Service

The None mode for the Publication and the Subscription Services is deprecated.

You can use IDocFormat mode instead.

7.1.0

Affected Component Description Deprecated in Release

Removed in Release

Publication Service and Subscription Service

The Rendezvous Message wire format is removed.

None 7.2.0

Publication Service, Subscription Service, Request-Response Invocation Service, and Request-Response Service

The following attributes in the RECCLOSURE class are removed: GUID, packetSize, bUseCache, bMore, bClearCache, cacheDirection, maxRowCount, currentRowCount.

None 7.2.0


Migration and Compatibility | 5

Migration and Compatibility

The following are instructions on how to migrate from a previous release to version 7.2.0 of TIBCO ActiveMatrix Adapter for SAP.

This section provides information about compatibility of the adapter and its data migration support for other TIBCO applications.

The configuration in earlier release, that is not supported in version 7.2.0, is ignored during migration and not used by the adapter.

The following migration processes are specific to the projects in TIBCO Designer.

For how to migrate a project in TIBCO Business Studio, see the TIBCO ActiveMatrix Adapter for SAP (TIBCO Business Studio) documentation.

Migrating from 6.2.x/7.x.0 to 7.2.0When you migrate projects to this release from version 6.2.x or 7.x.0, note the following points:

• TIBCO ActiveMatrix Adapter for SAP 7.2.0 can co-exist in the same TIBCO Administrator domain as TIBCO ActiveMatrix Adapter for SAP 6.2.x or 7.x.0, where the domain can either be ISO8859-1 or UTF-8.

• Migrate existing projects using the command-line migration tool or TIBCO Designer. It is good practice to use the command-line migration tool for migrating existing projects. For more information, see “Migrating an Adapter Project” in TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment.

Migrating from 6.1.0 and EarlierWhen you migrate projects from a release earlier than 6.2.0, first you have to migrate the projects to the 6.2.1 or 7.x.0 release.

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


6 | Release Notes

Closed Issues

The table lists closed issues in version 7.2.0 of TIBCO ActiveMatrix Adapter for SAP.

Table 4 Closed Issues (Sheet 1 of 2)

Key Summary/Workaround

ASAP-4060 When the maximum number of the SAP connection in the client connection and the thread number of Subscription Service were both greater than one, the TID and IDocNum attributes were incorrect in the IDoc confirmation message.

ASAP-3984 When a transaction contained multiple IDocs, the adapter only logged the first IDoc number.

ASAP-3912 The adapter did not support client connections with the Macedonian language.

ASAP-3898 When configuring the Message Report feature for Subscription Service, if the value of the threadCount property in this service was greater than one, the business key returned to TIBCO ActiveMatrix BusinessWorks was incorrect.

ASAP-3893 Subscription Service sending IDocs to the SAP system did not always confirm the transaction. When the transaction was unconfirmed, the unconfirmed entry was stored in the SAP table, ARFCRSTATE.

ASAP-3875 When the schema had been changed in the SAP system, if you refreshed the schema in the adapter, the latest schema was downloaded to a new folder named with the release version of SAP Kernel.

ASAP-3874 When downloading an RFC or BAPI schema referencing a nested structure, if multiple child structures of the nested structure used the same data type, the schema could not be downloaded successfully.

ASAP-3794 When using a Basic IDoc name containing the forward slash (/) located in a position other than the first position, the adapter could not find the publisher. When using an Extended IDoc name containing the forward slash (/), the adapter could not find the publisher.

ASAP-3733 When using the auto commit feature, if the interface contained a TABLE parameter referencing a structure starting with the name BAPIRET, the adapter can not invoke the RFC or BAPI correctly.

ASAP-3704 An Subscription Service error occurred when specifying the CRETIM field of the IDoc with a invalid value.


Closed Issues | 7

ASAP-2969 When using the command-line migration tool to migrate a project to TIBCO ActiveMatrix Adapter for SAP 7.1.0, the product classes were not migrated.

ASAP-2816 When running the Inbound adapter on a Red Hat Enterprise Linux Server 6.x, if the transport type of the adapter service was Rendezvous, the adapter crashed.

ASAP-2772 When refreshing the RFC/BAPI schema, if the corresponding adapter service has been configured with the One Way invocation protocol, the protocol is changed to Request/Reply.

ASAP-2053 When updating the schemas of an adapter service to a different release version, the reference of the endpoint used by the service was not updated.

Table 4 Closed Issues (Sheet 2 of 2)



8 | Release Notes

Known Issues

The table lists known issues in version 7.2.0 of TIBCO ActiveMatrix Adapter for SAP.

Table 5 Known Issues (Sheet 1 of 3)


ASAP-4011 Summary: When invoking Request-Response Service or Request-Response Invocation Service, if the RFC/BAPI contains a table type and the line type of the table type is also a table type, an runtime error occurs.

Workaround: Put the table type into a structure and use the structure as the line type.

ASAP-3671 Summary: When invoking Request-Response Invocation Service, if an RFC/BAPI contains an IMPORT, EXPORT, or CHANGING parameter where part of the schema refers to a table type and the corresponding line type refers to a data element, domain, or predefined data element, an exception occurs.

Workaround: Use the adr3.saprepository TRA properties. See details about the properties, see “Adapter Properties Files” in TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment.

ASAP-3659 Summary: The Outbound bgRFC of type T does not work.

Workaround: Use the tRFC or the qRFC instead.

ASAP-3562 Summary: The valid durable name of the JMS topic subscriber endpoint at run time is not the one specified at design time, but the one generated by the SDK adapter.

Workaround: None.

ASAP-3007 Summary: For Inbound services, the qRFC property, qCount, does not work.

Workaround: The SAP system assigns the qCount property when the message is received. Ensure that the message is sent to the adapter in the required order and that the number of threads per Inbound adapter service is one.


Known Issues | 9

ASAP-2895 Summary: If you start the adapter when the network connection is broken or the connection to the SAP system is unavailable, the adapter takes considerable time to reconnect to the SAP system.

Workaround:

• For an Outbound adapter, specify the maxRetryInterval property with a larger value.

• For an Inbound adapter, specify the maxAttempts property with a larger value.

ASAP-2894 Summary: The support for Decfloat16 and Decfloat34 is up to 15 characters and 31 characters respectively.

Workaround: None.

ASAP-2877 Summary: The time when the next server connection check takes place provide by the adapter does not reflect the actual time.

Workaround: None.

ASAP-2840 Summary: An error occurs when using the migration tool to migrate mutiple projects by using the -projectdir option.

Workaround: Migrate each project separately by using the -projectfile option.

ASAP-2801 Summary: When using the qRFC protocol to invoke an RFC transaction in an Outbound adapter service, if a message is published subsequently, the following properties are not populated in the RFCClosure class:

• bQueue

• qName

• qCount

Workaround: None.

ASAP-2732 Summary: When using Rendezvous transport between Request-Response Invocation Service and Request-Response Service in a ActiveMatrix BusinessWorks 5 process, if the schema of the operation contains a reference to the Binary data type, the corresponding request data from the adapter service is empty and a deserialization error occurs in the process.

Workaround: This issue is related to the TIBCO Rendezvous issue RV-3103. For details about the resolution, see LBN1-EWOQBG on the TIBCO Support website.




10 | Release Notes

ASAP-2492 Summary: When using the SAP transaction SM59 to test the connection between the SAP system and the Outbound adapter, the testing is not displayed in the adapter log.

Workaround: Ensure that the adapter has been started by checking the results of executing the SAP transaction SM59.

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

Workaround: Add these folders manually when creating the EAR file from the resource. These folders are available in the Resources tab of the Share Archive folder.




Date post:	14-Apr-2020
Category:	Documents
Upload:	others
View:	14 times
Download:	0 times

TIBCO ActiveMatrix Adapter for SAP · SAP products, including SAP ECC 6.0 re leases and SAP...

Documents