tibco activematrix businessworks smartmapper release notes · — oracle 11g r1, 11g r1 rac, 11g r2...

TIBCO ActiveMatrix BusinessWorks™ SmartMapper

Release NotesSoftware Release 5.5June 2011

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 LICENSE.PDF) 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, The Power of Now, TIBCO Adapter, TIBCO ActiveMatrix BusinessWorks, TIBCO Designer, TIBCO Administrator, TIBCO Rendezvous, TIBCO Runtime Agent, TIBCO Hawk, TIBCO Enterprise Message Service, 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. 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 © 1999-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

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

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

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

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 5.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 5.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Platforms available after Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Configuration on Microsoft Windows 32-bit (x86) platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Configuration on Linux/Unix platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

TIBCO ActiveMatrix BusinessWorks SmartMapper Release Notes

iv | Contents


| v

Preface

TIBCO ActiveMatrix BusinessWorks SmartMapper simplifies and enhances the process of setting up, deploying, using, and managing cross-referencing services for data synchronization.

Topics

• Typographical Conventions, page vi

• Connecting with TIBCO Resources, page ix


vi | 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 default 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. An environment home directory is referenced in documentation as ENV_HOME. The default 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: Typeadmin.

• 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 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 | vii

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 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 para1 | param2 | param3

Table 1 General Typographical Conventions (Cont’d)

Convention Use


viii | Preface

{ } 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}

Table 2 Syntax Typographical Conventions (Cont’d)

Convention Use


Connecting with TIBCO Resources | ix

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


x | Preface


| 1

Release Notes

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 username and password. If you do not have a username, 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 5

• Deprecated and Removed Features, page 6

• Migration and Compatibility, page 7

• Closed Issues, page 9

• Known Issues, page 15



2 | Release Notes

New Features

This section lists features added since the last major (5.0.0) release of this product.

Release 5.5.0The following are new features in this release:

• Added Universal Installer Support

• Added Platform Support Support has been added for the following platforms:

— Windows 7 (x86, x86-64)

— Windows server 2008 (x86, x86-64)

— Windows server 2008 R2 (x86-64)

• Added Database Support Support has been added for the following databases:

— Oracle 11G R1, 11G R1 RAC, 11G R2

— MySQL 5.0


• Cache Supported by Association Relationship SmartMapper has two kinds of Relationships, Identity and Association. In this release, cache is supported in both Identity and Association relationships.

• Cache Supported by Dynamic Lookup Cache is also supported by Dynamic Lookup.

Release 5.3.2No new features are introduced in this release.

Release 5.3.1No new features are introduced in this release.



New Features | 3

• Bulk Load Update The Update mode setting was added for the input format set to One Participant Relationship Format. In this mode, lookup is performed based on the primary participant: if no relationship instance is found, a new one will be created; if a lookup returns an existing relationship instance, it will be replaced with the new participant.

• Bulk Extract Filter This filter contains the following values: participantFieldName, where, and orwhere.

Each instance of the extraction filter is mapped to a condition in the SQL WHERE clause (WHERE <column> <operator> <value>).

• Dynamic Lookup, entity based Input format for this lookup is entity based.

• Dynamic Lookup, non-key based queries In this release, the non-key based queries are supported in addition to key-based queries.

• Reload from a database The Reload feature allows the users to import an ER Model, previously synchronized by another user, from a SmartMapper database instance.

• Participant Level Timestamp A participant level timestamp for the relationship-based Bulk Extract activity is now available.

• Support for the SQL Server 2005 has been added.

• Support for the 64-bit mode is added for the following platforms:

— HP-UX on IA-64/Itanium

— HP-UX on PA-RISC

— Solaris 10, 9, and 8 on SPARC

— Solaris 10 on x86

— Linux on x86

— AIX on POWER

All configurations are explained in TIBCO ActiveMatrix BusinessWorks SmartMapper Installation Guide.


• Bulk extract of data The Bulk Extract activity enables the bulk extraction of cross-referencing data for reporting purposes. You can query entity or relationship data by providing an entity name or relationship name.


4 | Release Notes

• Dynamic loading and query The Bulk Load activity allows you to load SmartMapper data and the Dynamic Lookup activity allows you to query SmartMapper data.

• Non-key attributes Non-key attributes are supported. Certain non-key attributes can also be made null.

• Records can be timestamped. Creation and modification timestamps for records can be included in the Dynamic Lookup and Bulk Extract activities.

• The association relationship type has been added for relationships where there are only two participants. The relationship type is set on the Relationship resource.


• Support for TIBCO Enterprise for JMS™ 3.1.2 and higher. TIBCO Enterprise Message Service™ 4.x is also supported.

• Support for DB2 8.1.

Release 5.1.2In this release, TIBCO BusinessWorks SmartMapper does not have new features: however, because of the many enhancements in the TIBCO BusinessWorks 5.1.2 release, BusinessWorks SmartMapper has been enhanced to support this version of TIBCO BusinessWorks. Refer to TIBCO BusinessWorks Release Notes for specific changes.


Changes in Functionality | 5

Changes in Functionality

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

Release 5.5There are no changes in functionality in this release.

Release 5.4The following is a change in functionality in this release:

• Dropping a installer file The installer drops the TIB_smartmappereps-simple_5.3.3_linux2g122_x86.bin file from this release.


6 | Release Notes

Deprecated and Removed Features

This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. 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 equivalent feature.

Release 5.5

Deprecated Features

No features are deprecated in this release.

Removed Features

The following features are removed in this release:

• Deleted Database Support DB2 8.x, SQL Server 2000, and Oracle 9i database are no longer supported from this release.

• Deleted Platforms Support Solaris 8 on SPARC is no longer supported from this release

Release 5.4No features are deprecated or removed in this release.


Migration and Compatibility | 7

Migration and Compatibility

This section explains how to migrate from a previous release to this release.

Release 5.5There are no migration procedures or compatiblity issues in this release.

Release 5.4There are no migration procedures or compatibility issues in this release.

Release 5.3After making the modifications, you will be unable to run BusinessWorks SmartMapper release 5.3. You can however, restore the backup copies made in the next procedure and then run release 5.3.

1. Change directory to install-path\tibco\designer\n.n\bin\.

2. Make a backup copy of the designer.tra file.

3. Using a text editor, open the designer.tra file.

4. In the tibco.env.CUSTOM_CP_EXT property, add the path to the BusinessWorks SmartMapper release 5.1 plug-in. The path must be added at the start of the value.

5. In the tibco.env.CUSTOM_PALETTE_PATH property, add the path to the BusinessWorks SmartMapper release 5.1 plug-in. The path must be added at the start of the value.

6. Save the file.

7. Change directory to install-path\tibco\bw\n.n\bin\.

8. Make a backup copy of the bwengine.tra file.

9. Using a text editor, open the bwengine.tra file.

10. In the tibco.env.CUSTOM_EXT_PREPEND_CP= property, add the path to the BusinessWorks SmartMapper release 5.1 plug-in. The path must be added at the start of the value.

This release only support for the migration from release 5.3.2, and from release 5.4 hotfix01.


8 | Release Notes

11. Save the file.

Release 5.2If you have a 5.2 database, you can upgrade to 5.3 by opening the 5.2 projects and saving them. There is no need to run the migration script.

Release 5.1To upgrade a release 5.1 database for use with release 5.2 or 5.3, you must run a migration script against your database.

After installing release 5.2 or 5.3:

1. Change directory to install-path\tibco\smartmapper\n.n\sql

2. Change directory to your database.

Execute the database-name_migration.sql script against your 5.1 database.

TIBCO BusinessWorks SmartMapper 5.3 /5.2 creates additional metadata fields for audit timestamps. The ER Model objects migrated from the release 5.1 will not have these fields available.

In order to enable audit timestamps for 5.1 objects, users can create a new database instance and sync it using the audit checkbox set at ON. Afterwards, data can be migrated using the BulkExtract and BulkLoad activities.


Closed Issues | 9

Closed Issues

The table in this section list issues that were closed in the named releases.

Closed in Release

Change Request ID Summary

5.5.0 SM-1105 The SmartMapper Wizard did not get the output value when the call was defined in the complex elements under the choice schema.

5.5.0 SM-1106 The input structure of the Wizard was changed after upgrading from TIBCO BusinessWorks SmartMapper 5.3.2 to 5.4.0, which would cause an invalid input data error at runtime.

5.5.0 SM-1111 The SmartMapper Wizard Input tab was unavailable if the input schema contained attributes.

5.4.0 1-8RX3TZ When JNDI lookup was used in the Adapter-Based SmartMapper service of SmartMapper storage, and a process with HTTP Receiver was invoked, the test connection of the transport in the Adapter-Based SmartMapper service failed.

5.4.0 1-8SH27J When JNDI lookup was used in SmartMapper Adapter Repository, the system threw an error in SmartMapper Admin Plugin.

5.4.0 1-9UIIKX The cache function only worked for the lookup activity and only if the relationship used was one-to-one.

5.4.0 1-A5CZS1 The SmartMapper Wizard activity did not pick up the correct values from SmartMapper DataBase.

5.4.0 1-A6XM8H Cache did not work for the SmartMapper Wizard when using the JDBC-Based service.

5.4.0 1-AFQAKP The SmartMapper Wizard activity did not resolve a CHOICE element.

5.4.0 1-AOTXNH Dynamic lookup did not support Cache.

5.4.0 1-AMMC19 Pepsico expected 4000 calls per second with Wizard Lookup.

5.3.1 1-84N2ZE TIBCO BusinessWorks SmartMapper Adapter only had error logs and did not have debugging logs. Debugging logs can now be found in the TIBCO_HOME/smartmapper/n.n/logs directory.


10 | Release Notes

5.3.1 1-85CGJX TIBCO BusinessWorks SmartMapper only worked with the default TIBCO RendezVous port for TIBCO Hawk.

5.3.1 1-8JGQ40 SQL Server domain authentication was not compatible with SmartMapper.

5.3.1 1-7DDGMN After the Bulk Load activity had been applied and the mode had been set to Update, the warning message Duplicate Record Exists did not display when the same record was inserted twice.

5.3.1 1-7XTW3H Changed Schema in JDBC-based service (Oracle) did not synchronize correctly if the option Audit had been checked while synchronizing for the first time.

5.3.1 1-8UKEU2 When using the TIBCO Administrator SmartMapper plug-in in Microsoft Internet Explorer, the Participant drop-down list items did not display if the attribute entity name began with gt_ or gt.

5.3.1 1-7Y5RVH Java runtime memory was not adjustable in the adsmartmapper.tra file. The system threw a Java heap space exception when more than 100,000 records were inserted under the adapter mode.

5.3.1 1-8MDWGA Incorrect list of participants displayed for a relationship in TIBCO Administrator when an ER (Entity-Relationship) model link was clicked for the first time.

5.3.1 1-8T1HRD The system threw a 'runtime time out' error when there was no input for the wizard activity.

5.3.1 1-8BTMER An 'operation timed out' error was thrown on the second iteration of the Bulk Extract Utility of TIBCO BusinessWorks SmartMapper with Adapter repository.

5.3.1 1-807TCK The Wizard activity did not display xref-elements in the Input tab correctly.

5.3.1 1-6Y39AL The Batch Size field in the Advanced tab determines the size of the batches sent by the SmartMapper Wizard for the Adapter-Based BusinessWorks SmartMapper Service. If the Batch Size field is set to 0, an error similar to the following appears:

BW-SMARTMAPPER-100014 : Wizard Operation Exception: com.tibco.solution.xref.XRefException: Failed to create mappings.

Closed in Release



Closed Issues | 11

5.3.1 1-8ONKP8 If a relationship contained many participants, the DynamicLookup activity did not close the cursors and threw a "Max open cursors exceeded" exception.

5.3.1 1-8DZPY6 When using the local deployment model, the "Parent parameter may not be null" exception was thrown when attempting to access ER models from TIBCO Administrator.

5.3.1 1-8MEYGG BusinessWorks SmartMapper lookups in TIBCO Administrator threw the "Lookup on empty keys values are not permitted" error when Silk support was enabled in TIBCO Administrator by adding the java.property.WFC.SILK_SUPPORT_ENABLED=true property to tibcoadmin_<domainname>.tra.

5.3.1 1-8FEXBF The Dynamic lookup activity failed with an error ORA-01000: maximum open cursors exceeded after entity lookup was performed several times.

5.3.1 1-8GP2Y3 The activity "Dynamic delete" threw an exception "maximum open cursors exceeded" while trying to delete entities. This happened with both JDBC and Adapter repositories.

Note: BulkExtract activity, when configured for Subset based extraction, will give "Object has been Closed" error in cases when the extraction process takes longer than 5 minutes and the connection times out.

This problem can be worked around by setting the following java property in designer.tra (or adsmartmapper.tra for the Enterprise version):java.property.com.tibco.solution.sm.agedTimeout 3600000

5.3.1 1-8FH9IC The activity "Delete Relationship Instance" was throwing an exception "java.lang.RuntimeException: no entryid" when the following conditions were met:

• Cache was enabled

• An update was done to one of the entities in the relationship instance just before the deletion was attempted.

5.3.1 1-8EI651 When Global Variables were used, the ER model was unable to connect to the EMS server (while using the Smart Mapper Adapter) or to the database (when using the JDBC based connection).

Closed in Release



12 | Release Notes

5.3.1 1-8D8L87 While doing a batch delete with the Dynamic Delete activity some rows were not removed from the map/relationship table.

5.3.1 1-8DOL2I Performance would degrade and memory usage would increase until the MAX HEAP SIZE limit was reached in TIBCO Designer when a large number of input and output participants were configured in the Smart Mapper Wizard.

5.3.1 1-885JR7 A java.lang.NullPointerException exception would result when clicking the SmartMapper 5.3.0 link in TIBCO Administrator.

5.3.1 1-7ZRZ6V The SmartMapper wizard activity ignored the nillable attribute and threw an error when an element was nill or when minOccurs='0'. Even though an element was defined as optional (minOccurs='0'), the wizard activity still expected the element to be present. The same schema and input data worked with the Mapper activity in TIBCO BusinessWorks.

Note: Previously mapped Nillable elements will appear red in SmartMapper Wizard activity input tab. Use "Mapper Check and Repair" feature of BW Mapper to fix these mapping.

5.3.0 1-7VXI4N The error java.lang.ArrayIndexOutOfBoundsException was thrown while trying to create new mapping with TIBCO Administrator.

5.3.0 1-7VWSZR BusinessWorks SmartMapper Wizard was not able to display a schema properly when minOccurs or choice attributes were used in this schema.

5.3.0 1-7B9G7P BusinessWorks SmartMapper Adapter responses were not picked up from temporary queues.

5.3.0 1-7B0PJT When there were non-key fields in an entity, the cache was not updated even when that entity was updated.

5.3.0 1-7AOY62 BusinessWorks SmartMapper was not caching data properly.

5.3.0 1-7ALXII The Bulk Extract activity and Adapter Repository with caching enabled were throwing a null-pointer exception even when there was data in the database.

5.3.0 1-7A953J The Bulk Extract activity was throwing a null-pointer exception if a user would try to extract from an empty database.

Closed in Release



Closed Issues | 13

5.3.0 1-7A6QHO Relationships within a folder were not working for the activities Bulk Load and Dynamic Lookup.

5.3.0 1-78NG87 ER Model Synchronization did not work when adding a new participant to an existing relationship.

5.3.0 1-77WA8L There was a failure in the relationship related activity ([tibcosoftwareinc][Oracle JDBC Driver]Invalid parameter binding(s).)

5.3.0 1-77OCSL When trying to access ER models, the following exception was thrown:(java.lang.IllegalArgumentException: Parent parameter may not be null)

5.3.0 1-7607RZ BusinessWorks SmartMapper did not support local deployments. When a customer would use local deployment and try to deploy BusinessWorks SmartMapper, the ER model was not deployed in TIBCO Administrator.

5.3.0 1-75X5A0 Support for Oracle RAC was added.

5.3.0 1-717JTA During load balancing, the BulkLoad activity would report a timeout error if two adapters were running in the same distributed queue mode and one of the adapters would go down while the Bulk Load was running.

5.2.0 1-6G8XZD The user was not able to create one-to-many mappings in TIBCO Administrator™.

5.2.0 1-7347LZ The uninstall procedure malfunctioned because the 'TIBuninstaller.bin' file was missing under the 'install-path/tibco/smartmapper/5.2/_uninst' directory on the HP-UNIX platform.

5.2.0 1-1CVXY5 When synchronizing the ER model with a Microsoft SQL Server database and copying and pasting the SQL generated into Microsoft SQL Query Analyzer, the following error message appeared:

'CREATE PROCEDURE' must be the first statement in a query batch.

Closed in Release



14 | Release Notes

5.2.0 1-712F1P When using TIBCO BusinessWorks SmartMapper with TIBCO BusinessWorks 5.2, if a SmartMapper activity had a non activity related error, the error would be reported under the activity’s Error Output and Output tabs.

5.1.3 1-1SYT75 Fixed a problem in which the Wizard would hang when multiple maintain mappings referenced the same entity.

5.1.3 1-2108DO Fixed an Add new entries problem related to maintaining mapping for one to many relationships in the Wizard.

5.1.3 1-2108EQ Fixed a log file format problem that caused the Administrator UI to display an error.

5.1.3 1-22DPJQ Fixed a problem related to BusinessWorks SmartMapper Enterprise Server state notification to Administrator during startup.

5.1.3 1-1CZ1X8 When using the adapter-based SmartMapper service, adapter errors were not propagated to the Administrator client libraries. Therefore, adapter errors did not display to users.

Closed in Release



Known Issues | 15

Known Issues

The table in this section lists known issues in this release.

Change Request ID Summary/Workaround

1-AVRA9J Summary The SmartMapper icon of the previous version is still shown in TIBCO Administrator after installing TIBCO BusinessWorks SmartMapper 5.4.0.

Workaround Complete the following steps to manually remove the previous SmartMapper icon:1

1. Open the TIBCO Administrator Window.

2. Expand Application Management > All Service Instances in the left pane.

3. Select a service instance named XXXXXX - TIBCO Administrator.

4. Check the SmartMapper Admin PlugIns/5.3.x under the Plug-Ins tab.

5. click the Remove button.

1-AUO2NU Summary An invalid input data error occurs when using the SmartMapper wizard to create a complex schema using an all type sub-element as a child of another element.

Workaround None.

1-AUO2NB Summary A NPE occurs when using the SmartMapper wizard to create a complex schema using an all or sequence type sub-element as a child of the choice element.

Workaround None.

1-AUEORV Summary No uninstaller executable file is available on the HP-UX with PA-RISC platform.

Workaround Use the following command to uninstall TIBCO BusinessWorks SmartMapper on the HP-UX platform:java -cp path to uninstaller.jar run

1-AT9MA5 Summary For the Identity relationship, the cache cannot get the changes caused by the SmartMapper wizard from the database.

Workaround None.


16 | Release Notes

1-8XT2K9 Summary TIBCO BusinessWorks SmartMapper cannot perform the Failing Over function in Oracle RAC (Real Application Clusters).

Workaround The user needs to use Oracle’s own driver, which is the OCI (Oracle Call Interface) driver. An example is given in the Appendix on page 17.

1-8YK5BX Summary In the TIBCO BusinessWorks SmartMapper 5.3.1 running environment, if a project is created in BusinessWorks SmartMapper 5.3.0 and has the SmartMapper Adapter Configuration property, BusinessWorks SmartMapper Adapter will only work with the default TIBCO Rendezvous port for TIBCO Hawk.

Workaround The SmartMapper Adapter configuration property has to be deleted and recreated in BusinessWorks SmartMapper 5.3.1.

1-8YQ55N Summary A connection error and time out error are given when the Synch ER Model w/DB button is clicked while using TIBCO BusinessWorks SmartMapper 5.3.1 with TIBCO Runtime Agent 5.5.0 This issue occurs when DB2 9.2 is on the Linux platform.

Workaround Upgrade the current version to TIBCO Runtime Agent 5.5.2 or greater or replace the Tldb2.jar file under the TIBCO_HOME/tpcl/n.n/jdbc directory.

1-8YH28L Summary The file xrefplugin.jar from TIBCO BusinessWorks SmartMapper hotfix 1 to 6 is not automatically removed after the uninstallation of BusinessWorks SmartMapper 5.3.0.

Workaround Manually delete the file xrefplugin.jar under the TIBCO_HOME/bw/n.n/lib/palettes directory from BusinessWorks SmartMapper hotfix 1 to 6.

1-7Y0ORM Summary Entity-based Dynamic Lookup and filter-based Bulk Extract activities throw runtime errors for DB2 when integer type key fields are used for lookup.

Workaround Add a double quote to all numerical type data (For example, "100").

1-732O8Y Summary When pasting an Association relationship , the relationship type changes to Identity.

Workaround Select the pasted relationship and change the relationship type to Association. Click Apply.

Change Request ID Summary/Workaround


Appendix | 17

Appendix

An workaround example for the known issue 1-8XT2K9 (Oracle OCI Driver Example Usage in TIBCO BusinessWorks SmartMapper 5.3.1) is listed below.

Platforms available after Verification• Microsoft Windows 32-bit (x86)

• Sun (SPARC 64-bit)—Solaris 10 on SPARC

• HP (HP-UX 64-bit)—HP-UX on IA-64/Itanium

• Linux (x86) 32 bit—Kernel 2.4.6 or greater/glibc 2.2.2 or greater

• Linux (x86) 64-bit

• AIX 5.3—AIX on POWER (64-bit)

Configuration on Microsoft Windows 32-bit (x86) platform1. Install the Oracle 11g client.

2. Copy the JAR file (ojdbc5.jar, for Oracle 11g) from Oracle JDBC (Java Database Connectivity) to the tibco/tpcl/5.5/jdbc directory.

3. Add the following code to the tnsnames.ora file:RAC_DB =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.65.31)(PORT = 1521))


)

(CONNECT_DATA =

(SERVICE_NAME = isqa)

(LOAD_BALANCE = ON)

(FAILOVER = ON)

(FAILOVER_MODE = (TYPE = SELECT)

(METHOD = BASIC)

(RETRIES = 20)

(DELAY = 10)

)


18 | Release Notes

)

)

4. Change the JDBC (Java Database Connectivity) class of the TIBCO BusinessWorks SmartMapper to oracle.jdbc.driver.OracleDriver and set the URL to jdbc:oracle:oci:@RAC_DB in the JDBC configuration.

5. Append %PATH% to tibco.env.PATH in the tibcoadmin_<DomainName>.tra file.

Configuration on Linux/Unix platforms1. Install the Oracle client (the Adminsitrator Type).

2. Set the PATH parameter for Oracle variables in the PROFILE or BASH-PROFILE file. The example is as shown as below:

PATH=$PATH:$HOME/bin

export ORACLE_BASE=/home/isqa/app/isqa

export ORACLE_HOME=$ORACLE_BASE/product/11.1.0/client_1

export LD_LIBRARY_PATH=$ORACLE_HOME/lib

PATH=$ORACLE_HOME/lib:$ORACLE_HOME/bin:$PATH

export PATH

unset USERNAME

Note: Set the PATH parameter as export LD_LIBRARY_PATH=$ORACLE_HOME/lib32 instead in Solaris 10.

3. Copy the JAR file (the file is called ojdbc14.jar in Oracle 10g and ojdbc5.jar in Oracle 11g ) from Oracle JDBC to the <tibco-home>/tpcl/5.5/jdbc directory.

4. Add the following code to the tnsnames.ora file.RAC_DB =

(DESCRIPTION =

(ADDRESS_LIST =



)

(CONNECT_DATA =

(SERVICE_NAME = isqa)

(LOAD_BALANCE = ON)

(FAILOVER = ON)

(FAILOVER_MODE = (TYPE = SELECT)

(METHOD = BASIC)


Appendix | 19

(RETRIES = 20)

(DELAY = 10)

)

)

)

Change the JDBC (Java Database Connectivity) class of the TIBCO BusinessWorks SmartMapper to oracle.jdbc.driver.OracleDriver and set the URL to jdbc:oracle:oci:@RAC_DB in the JDBC configuration.

5. Add %PSP%%LD_LIBRARY_PATH% at the end of the tibco.env.LD_LIBRARY_PATH property in the designer.tra file in the <Tibco-HOME>/desinger/n.n/bin directory.

Note:

• Add %RV_HOME%/lib/64 to <SHLIB_PATH> in the designer.tra file for HP-UNIX on IA64

• Add /oracle/OraHome_1/lib32 to <LIBPATH> in the designer.tra file for AIX53 64

• Append %LD_LIBRARY_PATH%%PSP%/home/oracle/app/oracle/product/11.1.0/cl

ient_1/lib to <tibco.env.LD_LIBRARY_PATH> in the designer.tra file on LINUX 64

6. Modify the adsmartmapper.tra file in <smartmapper-home>/5.3/bin as follows:

• Add tibco.env.ORACLE_HOME=/home/isqa/app/isqa/product/11.1.0/client

_1 as a common variable

• Append %PSP%%ORACLE_HOME%/lib to tibco.env.LD_LIBRARY_PATH

• Add tibco.env.ORACLE_HOME=/home/oracle/app/oracle/product/11.1.0/cl

ient_1 in the adsmartmapper.tra file and Append %LD_LIBRARY_PATH%%PSP%%ORACLE_HOME%/lib to <tibco.env.LD_LIBRARY_PATH> in the adsmartmapper.tra file for LINUX 64 (TIB_smartmappereps-simple_5.3.1_linux24gl23_x86.bin)

For more information on the Oracle installation on Linux and packages required on each platform, refer to the link below:http://www.oracle.com/technology/tech/linux/install/index.html


20 | Release Notes


tibco activematrix businessworks smartmapper release notes · — oracle 11g r1, 11g r1 rac, 11g r2...

Documents