TIBCO iProcess Technology Plug-ins Release Notes...iProcess Technology Plug-ins version 11 .0...

TIBCO iProcess® Technology Plug-ins

Release NotesSoftware Release 11.3.0December 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 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.TIB, TIBCO, Information Bus, The Power of Now, TIBCO Adapter, TIBCO iProcess BusinessWorks Connector, TIBCO iProcess 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 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 © 2005-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

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

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 11.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 11.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 11.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 11.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 11.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 11.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 11.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 11.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 11.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 11.1 and Release 11.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Issues Affecting the iProcess BusinessWorks Server Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Issues Affecting the iProcess Conductor Server Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Issues Affecting the BusinessWorks iProcess Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Issues Affecting the EAI POJO Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Issues Affecting all iProcess Technology Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22iProcess Connection Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Installer Not Informing User When JVM Cannot be Found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Misleading Error for Long JNDI Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Runtime Errors with SQL Server 2005 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22A Possible Loop in the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23XPath Expressions in Numeric Fields Are Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

TIBCO iProcess Technology Plug-ins Release Notes

iv | Contents

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Restrictions Affecting the iProcess BusinessWorks Server Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Restrictions Affecting the iProcess Conductor Server Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Restrictions Affecting the BusinessWorks iProcess Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Restrictions Affecting the EAI POJO Plug-in Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Restrictions Affecting all iProcess Technology Plug-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31


| 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. You must have a valid maintenance or support contract to use this site.

Topics

• Introduction, page 2

• New Features, page 3

• Changes in Functionality, page 6

• Deprecated Features, page 7

• Migration and Compatibility, page 8

• Closed Issues, page 10

• Known Issues, page 22

• Restrictions, page 24


http://support.tibco.com

2 | Release Notes

Introduction

The iProcess® Technology Plug-ins provides a single assembly-based installer for the following plug-ins. Some of these plug-ins were available as separate products in earlier releases:

• TIBCO iProcess® Java Server Plug-in - This plug-in enables the iProcess Engine to process EAI Java steps that have been added to an iProcess procedure.

• TIBCO iProcess® BusinessWorks™ Server Plug-in - This plug-in provides the communication mechanism that allows the iProcess Engine to make calls to TIBCO BusinessWorks.

• TIBCO BusinessWorks™ iProcess® Plug-in - This plug-in provides a set of resources that allow a TIBCO BusinessWorks process definition to communicate with the TIBCO iProcess Engine. This plug-in was previously available together with the iProcess BusinessWorks Server Plug-in as part of the TIBCO iProcess BusinessWorks Connector.

• TIBCO iProcess® Conductor Server Plug-ins (Order and Orchestration) - These plug-ins were previously available as part of the TIBCO iProcess Conductor. The Orchestration plug-in processes the messages you define in the Orchestration steps in your iProcess procedures. The Order plug-in provides an interface that notifies the TIBCO iProcess Conductor of the status of the order and enables you to update order data from the TIBCO iProcess Conductor in the TIBCO iProcess Engine and vice versa.

• TIBCO iProcess® XML Transform Server Plug-in - This plug-in performs transformations on XML data. This plug-in was previously available as part of the TIBCO iProcess Conductor.

Client-side components for these plug-ins are now supplied as the companion product, TIBCO iProcess® Workspace Plug-ins.


New Features | 3

New Features

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

Release 11.3.0

Support SSL Connection to EMS (IPTP-552)

Support is provided for SSL authentication on connections between iProcess Technology Plug-ins and TIBCO Enterprise Message Service (EMS). See the TIBCO iProcess Technology Plug-ins Installation guide and the TIBCO iProcess BusinessWorks Connector User’s Guide for details.

XML Step Definitions (IPTP-595 (MR 42980))

The XML step definitions for iProcess BusinessWorks Connector invocations are cached, and you can edit the cache size.

Installing Database Drivers

In previous releases, database drivers were provided as part of the TIBCO iProcess Technology Plug-ins product. From version 11.3.0, database drivers are no longer provided and must be installed separately.

Supported Java Versions

The iProcess Technology Plug-ins version 11.3.0 is delivered with Java Standard Edition 6. See the TIBCO iProcess Technology Plug-ins Installation guide for details.

Release 11.2.0

UTF-8 Support (MR 40127)

The installer has been enhanced to support UTF-8 encoding, in line with changes to the rest of the iProcess suite.

Note that Java 5 is not supported for this release of the iProcess Technology Plug-ins.


4 | Release Notes

iProcess Conductor Support (MR 38720)

Internal changes to support the clustering capabilities of iProcess Conductor 11.1.0. This is now expanded to support JBoss as well as WebLogic.

Release 11.1.0

iProcess Conductor Support (MR 39820, MR 39840)

Internal changes to support the clustering capabilities of iProcess Conductor 11.1.0. This is supported in a WebLogic/Solaris environment only.

Release 11.0.1

Sun x86 Platform Supported

This release adds support for the Sun x86 platform.

Release 11.0

Supported Java Versions

The iProcess Technology Plug-ins version 11 is delivered with Java Standard Edition 5 and has also been tested with Java Standard Edition 6. See the TIBCO iProcess Technology Plug-ins Installation guide for details.

JNDI Password Encryption (MR 35914, MR 35920, MR 35593)

JNDI passwords for JMS providers are now encrypted by default, both in the database and when you export your JMS configuration using the JMS Administration Tool. See the TIBCO iProcess Technology Plug-ins Installation guide and the TIBCO iProcess BusinessWorks Connector User’s Guide for details.

Database Pooling (MR 34020)

Both the TIBCO iProcess BusinessWorks Connector and the TIBCO iProcess Java Plug-in have been enhanced so that you can configure the database pooling. See the TIBCO iProcess BusinessWorks Connector User’s Guide and the TIBCO iProcess Java Plug-in User’s Guide for details.

Note that Java 1.4 is not supported for this release of the iProcess Technology Plug-ins.


New Features | 5

Application Server Versions

iProcess Technology Plug-ins version 11.0 supports Oracle WebLogic version 9.2.1.0, JBoss version 4.2.1, and JBoss EAP version 4.3 as application servers for the iProcess Conductor Plug-ins.

Earlier VersionsFor details of the new features implemented in earlier versions of the product, please see the Readme and Release Notes for that particular product release.

Earlier versions of WebLogic and JBoss are no longer supported.

Oracle WebLogic was previously known as BEA WebLogic. References to BEA WebLogic may still remain in the software and documentation.


6 | Release Notes

Changes in Functionality

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

Release 11.3.0 The platforms and databases supported in release 11.3.0 are strictly limited to those specified in the readme.txt file.

Release 11.0.1

TIBCO Enterprise Message Server (EMS)

TIBCO Enterprise Message Server (EMS) client libraries are no longer distributed with the TIBCO iProcess Technology Plug-ins. TIBCO EMS must be purchased and installed separately.

Release 11.0

Java Examples

Many changes, both cosmetic and functional, have been made to the Java examples, JavaDoc and supplied Java source code in this release.

Note in particular that DB2 databases are not supported at release 11.3.0.


Deprecated Features | 7

Deprecated 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 11.3.0The TIBCO BusinessWorks FormBuilder functionality in the iProcess Palette of the iProcess BusinessWorks Connector is deprecated. FormBuilder forms will no longer supported in future releases.

Release 11.2.0None.

Release 11.1.0From this version, TIBCO iProcess Technology Plug-ins is no longer supported on Windows Server 2000.

Release 11.0.1None.

Release 11.0None.


8 | Release Notes

Migration and Compatibility

Release 11.3.0The table below lists other TIBCO products with which the iProcess Technology Plug-ins has direct compatibility requirements, and the versions of those products that are compatible with this version of the iProcess Technology Plug-ins.

Validated versions have been successfully tested by TIBCO for compatibility with this version of the iProcess Technology Plug-ins. Compatible versions have not been formally validated, but have no known incompatibilities with this version of the iProcess Technology Plug-ins.

If you are currently using a version of one of these products that is:

• earlier than any of those listed, you must upgrade to a compatible version before using this version of the iProcess Technology Plug-ins.

• later than any of those listed, please refer to the Readme for that product/version to determine if it is compatible with this version of the iProcess Technology Plug-ins. If the Readme does not provide a definitive answer, please contact TIBCO Support for further assistance.

Release 11.2The table below lists other TIBCO products with which the iProcess Technology Plug-ins has direct compatibility requirements, and the versions of those products that are compatible with this version of the iProcess Technology Plug-ins.

Product Validated Version(s)

Compatible Version(s)

TIBCO iProcess Workspace Plug-ins Version 11.3 None.

TIBCO iProcess Workspace (Windows) Version 11.3 None.


Migration and Compatibility | 9


If you are currently using a version of one of these products that is:

• earlier than any of those listed, you must upgrade to a compatible version before using this version of the iProcess Technology Plug-ins.

• later than any of those listed, please refer to the Readme for that product/version to determine if it is compatible with this version of the iProcess Technology Plug-ins. If the Readme does not provide a definitive answer, please contact TIBCO Support for further assistance.

Release 11.1 and Release 11.0 The table below lists other TIBCO products with which the iProcess Technology Plug-ins has direct compatibility requirements, and the versions of those products that are compatible with this version of the iProcess Technology Plug-ins.





TIBCO iProcess Workspace (Windows) Version 11.1 11.0.x10.5.x10.6.x




TIBCO iProcess Workspace (Windows) Version 11.0 10.5.x10.6.x


10 | Release Notes

Closed Issues

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

• The first table lists issues that affect only the iProcess BusinessWorks Server Plug-in. If you do not intend to install that plug-in, you do not need to read this table. See page 10.

• The second table lists issues that affect only the iProcess Conductor Plug-ins. If you do not intend to install those plug-ins, you do not need to read this table. See page 13.

• The third table lists issues that affect only the BusinessWorks iProcess Plug-in. If you do not intend to install this plug-in, you do not need to read this table. See page 14.

• The fourth table lists issues that affect only the EAI POJO plug-in. If you do not intend to use this plug-in, you do not need to read this table. See page 17.

• The last table lists issues that affect all the iProcess Technology plug-ins. Since the iProcess BusinessWorks Server Plug-in is dependent on the iProcess Java Server Plug-in - that is, if you install the iProcess Business Server Works Plug-in, you must also install the iProcess Java Server Plug-in - issues that affect the iProcess Java Plug-in are relevant to all users. See page 18.

Issues Affecting the iProcess BusinessWorks Server Plug-inThis first table lists changes that affect the iProcess BusinessWorks Server Plug-in only.

Closed in Release Defect # Summary

11.0.1 MR 38229 (Parent MR 37763)

Attempting to convert a BWC Date to an iProcess Date when the date is actually a zero length string causes a fatal error.

Corrected.

11.0.1 MR 36785 When iProcess makes a BusinessWorks call and returns a minus number in exponent form, that input is not converted correctly.

Corrected.


Closed Issues | 11

11.0 MR 36166 If you try to edit an iProcess BusinessWorks step that uses a Live Link to BusinessWorks, and the iProcess Service Agent is down, the request to edit hangs for 30 seconds.

Corrected. The default timeout is now 5 seconds, and this value is configurable in case your installation requires a different timeout period - for example, if the Service Agent is typically unable to respond within 5 seconds.

The following property has been added to the SWDIR\eaijava\properties\bw\jms.properties file:

eaijava.service_agent_timeout_ms=5000

If you require a different value, edit this property to give the required timeout (in milliseconds). If this property is not specified, the default value of 5000 (5 seconds) is used.

See the chapter "Invoking BusinessWorks from the iProcess Engine" in the TIBCO iProcess BusinessWorks Connector User’s Guide for further information on iProcess BusinessWorks steps. See the section "Timeout Handling in the iProcess BusinessWorks Connector" in the same manual for the SWDIR\eaijava\properties\bw\jms.properties file.

11.0 MR 35977 The iProcess BusinessWorks Plug-in MBean interfaces are incompatible with TIBCO Business Studio™ Version 3.0.

Corrected.

11.0 MR 35941 Enhance the JMS Administration Tool to be able to generate the schema upgrade script in standalone console mode, without iProcess Engine running.

Implemented. See "Configuring JNDI Password Encryption (Upgrade Only)" in the TIBCO iProcess Technology Plug-ins Installation guide for further details.

11.0 MR 35920 When upgrading to version 11.0, an SQL script must be run after installation to upgrade the schema.

Implemented. See "Configuring JNDI Password Encryption (Upgrade Only)" in the TIBCO iProcess Technology Plug-ins Installation guide for further details.



12 | Release Notes

11.0 MR 35914(original MR 35728)

The JNDI password should be encrypted by default both in the database and when exported.

Corrected. The JNDI password for iProcess BusinessWorks JMS providers is now encrypted in the database, and in the JMS export file. The interfaces between the iProcess Technology Plug-ins and iProcess Workspace Plug-ins have been modified accordingly.

11.0 MR 35656 When an iProcess BusinessWorks step is edited in the iProcess BusinessWorks Server Plug-in, the JMS timeout Configuration tab is disabled.

Corrected.

11.0 MR 35593 When exporting JMS data using the JMS Administration Tool, the JNDI Password should be encrypted by default.

Implemented. The JNDI Password is now encrypted by default. See the section "Exporting JMS Provider Configuration Information" in the TIBCO iProcess BusinessWorks Connector User’s Guide for further information.

11.0 MR 31900 When importing a JMS provider file, the message displayed refers to Staffware procedures. It should instead refer to iProcess procedures.

See "Importing JMS Provider Configuration Information" in the TIBCO iProcess Business Works Connector User’s Guide for further information.

Corrected

11.0 MR 32278 JMS sendRequest function in the BusinessWorks Connector needs tidying up to ensure connections are freed. See MR 32259.

Corrected.

11.0 MR 32508 The iProcess BusinessWorks Client Plug-in cannot connect to the iProcess BusinessWorks Server Plug-in through a firewall. This is because an operating system allocated ephemeral port is used during the connection, making it impossible to enable the port on the firewall.

Corrected. Both the JNDI port and RMI port used for communication are now configurable. This allows firewall administrators to open these ports to allow communication.



Closed Issues | 13

Issues Affecting the iProcess Conductor Server Plug-insThis table lists changes that affect the iProcess Conductor Server Plug-ins only.

Closed in Release Defect Summary

11.2.0 MR 40638 (Parent MR 40617)

An "Update order line" EAI call-out failed due to IncorrectVersionException on the iProcess Conductor server side.

Corrected.

11.2.0 MR 38720 Support iProcess Conductor clustering under JBoss EAP.

Implemented. Note that the server configuration must be specified as All or Production, not Default.

11.1.0 MR 39840 Minor internal code changes to the iProcess Conductor plug-in libraries.

11.0 MR 36323 EAIOrder not allowing Spanish characters to be displayed properly.

Corrected.

11.0 MR 36178 Permit XML Transform to map XPATHs resolving to null.

Implemented. If an XML Transform step executes an XPATH expression that evaluates to null (that is, the XML element does not exist) no action is now taken.

11.0 MR 35927 The user documentation should indicate which XPath functions are not supported by XML Transform steps.

Corrected. See Appendix B, "Unsupported XPath Functions in the XML Transform Plug-in", in the TIBCO iProcess Conductor Implementation guide.

11.0 MR 35712 Support the iProcess Conductor Plug-ins on AIX and Linux systems.

Implemented.


14 | Release Notes

Issues Affecting the BusinessWorks iProcess Plug-inThis table lists changes that affect the BusinessWorks iProcess Plug-in only.


11.3.0 IPTP-600(MR 43134)

Improve the caching of step definitions in order to improve performance and reduce CPU load.

Implemented.

11.3.0 IPTP-595(MR 42980)

The XML step definitions for EAI Business Works invocations should be cached in order to improve performance and reduce CPU load.

Implemented. The cache.properties file enables you to specify whether XML data is cached, and if caching is used, to specify the cache size of the XML data. See "Post-Installation Tasks" in TIBCO iProcess Technology Plug-ins Installation for further details.

11.3.0 IPTP-551 When starting cases from TIBCO BusinessWorks using TIBCO BusinessWorks iProcess Plug-in, an error occurred if the length of the Requisition ID exceeded 32 bits.

Corrected.

11.3.0 IPTP-547 When using multiple connection factories in the endpoints, the incorrect factory was used in EAI steps, because the key mapped to the connection in the cache was not enough information to uniquely identify the connection required.

Corrected.

11.3.0 IPTP-533(MR 40399)

When mapping the output of a POJO (String) into an iProcess Memo field, the process failed at runtime as a consequence of the validation of field lengths. Memos did not have a length (-1) and the check failed with a fatal error.

Corrected.

11.3.0 IPTP-497(MR 40755)

Include the datetime.properties file in iProcess Technology Plug-ins to prevent unnecessary warning messages being sent to the logs when iProcess Engine sends date/time information to TIBCO BusinessWorks.

Implemented.


Closed Issues | 15

11.3.0 MR 43632 Modify the JMS connection behavior when communicating with TIBCO BusinessWorks, to reduce the number of connection requests.

Implemented.

11.3.0 MR 43501 Duplicate JMS provider names are not permitted with respect to a TIBCO BusinessWorks step. Modify the JMS Administrator to permit a duplicate JMS provider to be created so that, for example, for the same JMS endpoint two different sets of credentials can be used. The second and subsequent duplicate provider names are automatically suffixed with a unique identifier. A check is made to ensure the overall record is unique when creating a new provider, however this check is not enforced when modifying an existing provider.

Implemented. See the JMS Provider field in "Administering JMS Providers and Destinations" in the TIBCO iProcess Business Works Connector User’s Guide for further information.

11.3.0 MR 43341 Attempting to confirm a message that had expired while using EMS 4.4+ resulted in an exception. This was not the case in previous versions of EMS.

The iProcess Service Agent should ignore the exception and release the connection back to the connection pool.

Corrected.

11.2.0 MR 40359 The "Modify Case Data" operation of the iProcess Procedure Case Management activity and the iProcess Start Case Activity does not update memo fields correctly when importing from an iProcess database using UTF-8 encoding.

Corrected.

11.0.1 MR 39009 Case Management activity is missing the advanced option 'Include Procedure System Fields in Input'.

Corrected.

11.0.1 MR 39032 The iProcess Service Agent generated WSDL causes an error when using the validate option in Business Studio.

Corrected.



16 | Release Notes

11.0 MR 36245 The error reported by the BusinessWorks iProcess Plug-in if no sub-procedures with the required status can be found is incorrect.

Corrected. New error messages have been introduced specifying that sub-procedures, rather than main procedures, of the appropriate status cannot be found. See the appendix "BusinessWorks iProcess Plug-in Error Codes" in the TIBCO iProcess Business Works Connector User’s Guide for further information.

11.0 MR 35699 If the case number input to the iProcess Get Case Number activity is invalid, or the sub procedure case instance has not been processed, a null pointer exception is generated.

Corrected. If the case number input is invalid (because it does not exist, or for any other reason cannot be processed) a value of 0 is now returned. See the description of this activity in the TIBCO iProcess Business Works Connector User’s Guide for further information.

11.0 MR 34031 Some features of the plug-in are only supported on particular versions of iProcess Engine. When trying to invoke one of these features against some versions of iProcess Engine, the version comparison logic is incorrect and features that should be supported are not available.

Fixed.

11.0 MR 33870 Occasionally duplicate Delayed Release IDs were detected in the Delayed Release activity, which caused steps in the iProcess Engine to remain in an unreleased state. The only work around was by setting the Max Connections in the iProcess Connection Shared Resource equal to 1.

Fixed.

11.0 MR 33014 Changes to the JMS ReceiverConfiguration Class in BusinessWorks 5.6 break compatibility with the BusinessWorks iProcess Plug-in.

Fixed. BusinessWorks iProcess Plug-in now supports BusinessWorks 5.6.



Closed Issues | 17

Issues Affecting the EAI POJO Plug-inThe following table lists changes that affect the EAI POJO Plug-in only.

11.0 MR 32328 BusinessWorks Connector calls to iProcess do not support different date formats.

Corrected. Although different date formats are supported in the BusinessWorks iProcess Plug-in, the date format is embedded in the BusinessWorks process definition for each activity. This makes updating a BusinessWorks process to use a different date format difficult.

In the iProcess Connection Shared Resource, a new Advanced tab is now available which enables you to specify the date format.

See the "TIBCO BusinessWorks iProcess Plug-in Palette" chapter of the TIBCO iProcess BusinessWorks Connector User’s Guide for details.



11.3.0 IPTP-533 (Parent MR 40399)

When mapping the output of a POJO (String) into an iProcess Memo field, the process failed at runtime as a consequence of the validation of field lengths. Memos did not have a length (-1) and the check failed with a fatal error.

Corrected.

11.0 MR 33944 Case fails when an empty value is passed to a method of simple type char.

Corrected. Empty input fields are assigned appropriate values. See the section "Configuring POJO in TIBCO Business Studio" in the TIBCO Business Studio iProcess Developer's Guide.


18 | Release Notes

Issues Affecting all iProcess Technology Plug-insThe following table lists changes that affect all the iProcess Technology plug-ins.


11.3.0 IPTP-624 Remove from the installer the option to select a DB2 database.

Implemented.

11.3.0 IPTP-604(Parent MR 40376)

An error was generated when passing an integer value to an integer array element.

Corrected.

11.3.0 IPTP-552 Enhance iProcess Technology Plug-ins to support SSL authentication to EMS.

Implemented. See the "Managing Your JMS Provider" chapter of the TIBCO iProcess Business Works Connector User’s Guide for further information.

11.3.0 IPTP-418 If you run the iProcess Technology Plug-ins installer with the re-install or reconfigure options selected, the JMS provider and destination information in the database sequence tables is lost.

Corrected. Running the installer in re-install mode correctly re-creates the database tables whilst preserving any JMS data.

The behavior still exists when running the installer in reconfigure mode. If the tables need re-creating, select the re-install rather than reconfigure option in the installer.

11.3.0 MR 43341 Attempting to confirm a message that had expired while using EMS4.4+ resulted in an exception. This was not the case in previous versions of EMS. The iProcess Service Agent should ignore the exception and release the connection back to the connection pool.

Corrected

11.2.0 MR 41132 The TIBCO iProcess Technology Plug-ins installer should support WebLogic 10.3.

Implemented.

11.2.0 MR 40127 Support Unicode UTF-8 character encoding.

Implemented


Closed Issues | 19

11.1.0 MR 39820 Minor internal code changes to the iProcess Java plug-in libraries.

11.0.1 MR 39208 Port TIBCO iProcess Technology Plug-ins to Sun x86 Solaris 10.

11.0.1 MR 39408 TIBCO Enterprise Message Server (EMS) client libraries are no longer bundled with TIBCO iProcess Technology Plug-ins.

11.0.1 MR 36791 Enhance jdbc connection logic so that broken pipe exceptions are handled by allocating a fresh socket connection.

Corrected. Connections in the db pool are now validated according to attributes defined in $SWDIR/eaijava/jmx/config.xml.

11.0 MR 36440 If iProcess Technology Plug-ins is installed on a machine with multiple network cards where each network card is configured on a different network subnet, TIBCO Business Studio can fail to connect to the deployment server when deploying a process containing a BusinessWorks EAI step and/or iProcess Workspace Plug-ins can fail to connect to the JMX service when defining or editing a BusinessWorks EAI step. This is because the client machine (Business Studio and/or Workspace Plug-ins) will only be able to see one of the network cards (the one in the same network subnet as itself), but the JMX proxy stub that is returned to the client can arbitrarily be supplied with the network address of another card, which is of course unreachable by the Business Studio and/or Workspace Plug-ins machine.

Corrected. The file jmxbinding.properties is supplied on the distribution set under the top level folder /network. In order to use the new functionality the file must be copied to SWDIR/eaijava.

The file as supplied sets the property JMXConfig.binding to 127.0.0.1. With this value the default (compatible) behavior is used as though the new functionality has not been applied. This is also the case if the file is not present, or is present but contains no value for JMXConfig.binding.

Alternative values for the property are either

— 0.0.0.0 in which case all network cards on the server are enumerated and the IP addresses are returned to the client (Business Studio/Workspace Plug-ins) when connecting, or

— a list of one or more specific IP addresses that are exclamation mark separated (for example, 192.168.0.1!192.168.1.1) that will be returned to the client when connecting.



20 | Release Notes

11.0 MR 36394 Need to be able to encrypt the database password, for use in the response file for a silent install, without using the GUI.

Implemented.

11.0 MR 35781 When in debug mode the log files continuously grow even though no cases are being processed.

Corrected. Some routinely repeating entries no longer display at Debug level.

11.0 MR 35758 There are various issues with the supplied JavaDocs.

Corrected.

11.0 MR 35696(Original MR 34157)

Support SSOLite functions SW_SET_QUEUE and SW_UNSET_QUEUE on database connections.

Implemented. See the TIBCO iProcess Java Plug-in User’s Guide for further details.

11.0 MR 35548 The COUNT function is not supported in xpaths.

Corrected.

11.0 MR 34020 Enhance Generic Pooling of DB Connections and allow DBPoolMBean to administer pool parameters.

Implemented. See the TIBCO iProcess Java Plug-in User’s Guide and the TIBCO iProcess BusinessWorks Connector User’s Guide for further details.

11.0 MR 34161 Update third-party libraries to new versions.

Implemented.

11.0 MR 34219 The creation of the DB pool in the iProcess Java Plug-in is deferred until a Delayed Release requires processing. It is possible for a change in pool attributes to be missed if the change occurs before the pool is created.

Corrected.

11.0 MR 33998 Expose the SSO Lite Stored Procedure Functionality to direct calls to a specific MBox in the Java wrapper API.

Implemented. See the TIBCO iProcess Java Plug-in User’s Guide and the TIBCO iProcess BusinessWorks Connector User’s Guide for further details.



Closed Issues | 21

Earlier VersionsFor details of the MRs/CRs implemented in earlier versions of the product, please see the Readme and Release Notes for that particular product release.

11.0 MR 33571 In some scenarios, the JNI call to getOutputFieldsAsString() receives a RuntimeException because output fields are deliberately null.

Corrected. Prior to Java 6 this exception was benign but to defend against this, the code is enhanced so that the runtime exception will not be propagated back to the native layer (which would otherwise cause the JVM to terminate and in turn would terminate the iProcess Background).

11.0 MR 33561 To improve performance, determine JVM platform encoding and compare with specified file.encoding, and only translate messages using the encode/decode methods when necessary.

Implemented.

11.0 MR 33524 The JMX polling interval sleepPeriod is too short (at 15000ms) for systems with multiple BG processes, consuming resources as processes poll for a response every 15 seconds.

Corrected. The default remains 15000ms but if this needs to be increased, you can manually create a SWDIR/eaijava/jmx/config.properties file specifying a higher value. See the "Troubleshooting" section in TIBCO iProcess Technology Plug-ins Installation for further details.

11.0 MR 32259

(Parent MR 31449)

Large numbers of socket connections to the JMS provider are being left open instead of being closed by iProcess Java garbage collection.

Corrected. Defensive code has been added to close the socket connections explicitly to ensure any resources outside the JVM are freed.



22 | Release Notes

Known Issues

This section lists known issues for the current version.

iProcess Connection Database InformationAn incompatibility with the current version of TIBCO BusinessWorks means that the information on the Database Connection tab of an iProcess Connection resource must be entered manually. This information must be based on the JDBC driver installed when TIBCO BusinessWorks was installed. See the section ’iProcess Connection’ in the TIBCO iProcess BusinessWorks Connector User’s Guide for more information about this resource, and see the documentation supplied with your JDBC driver for information on what data to enter.

Installer Not Informing User When JVM Cannot be FoundThe installer terminates at the Verifying JVM check without informing the user of the cause of the termination.

Misleading Error for Long JNDI PasswordsJNDI passwords are limited to 1 KByte in length. If a JNDI password longer than the maximum 1 KByte is used, an "Invalid Endpoint Name: Endpoint already exists" error is displayed, instead of an error indicating that the password size limit has been reached.

See the section "Adding a New JMS Provider" in the TIBCO iProcess BusinessWorks Connector User’s Guide for details of the JNDI Password field.

Runtime Errors with SQL Server 2005 SP2If you are performing a new installation of iProcess Technology Plug-ins under SQL Server 2005 with Service Pack 2, or upgrading to Service Pack 2, you may encounter an error at runtime. When you use the BusinessWorks iProcess Plug-in from TIBCO Designer and execute a Start Case on the iProcess Engine, an SQL Server error message is generated warning you to enable OLE using the Server Surface Area Configuration utility.

See TIBCO iProcess Technology Plug-ins Installation for further details.


Known Issues | 23

A Possible Loop in the InstallerIn certain circumstances it is possible to create a loop in the iProcess Technology Plug-ins installer.

If an existing version of one or more plug-ins is already installed and you intend to upgrade the existing installation, but accidentally select New Installation at the Installation Mode dialog instead, an error message is generated.

You are informed that it is not possible to perform a new installation over a previous version, and you are prompted either to select another component to install, or to remove the existing version. The Features dialog is displayed, enabling you to select another component. However, you cannot navigate back to the Installation Mode dialog to correct your original error, and if all components are already selected on the Features dialog you cannot move from this screen at all, and must stop the installation manually.

XPath Expressions in Numeric Fields Are Not SupportedIf you define a numeric field that maps to an XPath expression then the iProcess BusinessWorks Connector fails to call the BusinessWorks process.

This is because the iProcess BusinessWorks Connector uses XPath 1.0 and scientific notation is not supported in XPath 1.0. It is supported in XPath 2.0. Xalan implements the XPath 1.0 specification, so trying to perform arithmetic operations on values does not work.

A workaround for this problem is to perform the addition within TIBCO BusinessWorks. This evaluates the expression correctly, and you can then send the result back to iProcess.


24 | Release Notes

Restrictions

This section lists restrictions for the current version.

• The first table lists restrictions that affect only the iProcess BusinessWorks Server Plug-in. If you do not intend to install that plug-in, you do not need to read this table. See page 24.

• The second table lists restrictions that affect only the iProcess Conductor Server Plug-ins. If you do not intend to install those plug-ins, you do not need to read this table. See page 27.

• The third table lists restrictions that affect only the BusinessWorks iProcess Plug-in. If you do not intend to install this plug-in, you do not need to read this table. See page 28.

• The last table lists restrictions that affect all the iProcess Technology plug-ins. Since the iProcess BusinessWorks Server Plug-in is dependent on the iProcess Java Server Plug-in - that is, if you install the iProcess BusinessWorks Server Plug-in, you must also install the iProcess Java Server Plug-in - issues that affect the iProcess Java Plug-in are relevant to all users. See page 31.

Restrictions Affecting the iProcess BusinessWorks Server Plug-inThis table lists restrictions that affect the iProcess BusinessWorks Server Plug-in only.

Defect # Summary/Workaround

IPTP-396 Summary If you try to add a JMS provider using the URL of an existing provider, a message is displayed stating that the JMS endpoint already exists, when it should say that the provider already exists.

Workaround None.


Restrictions | 25

MR 41537MR 41550

Summary A known compatibility issue exists between TIBCO iProcess Technology Plug-ins and TIBCO BusinessWorks version 5.7.1. The iProcess Connection resource may fail to connect from a BusinessWorks project.

Workaround Contact TIBCO support for details; a hotfix to BusinessWorks may be required. When you have received this, it may be necessary to install the components in the following sequence:

1. TIBCO Runtime Agent version 5.6.0 or 5.6.1

2. TIBCO BusinessWorks version 5.7.1

3. TIBCO iProcess Technology Plug-ins version 11.2.0

4. TIBCO BusinessWorks Hotfix 2 and any subsequent hotfixes

MR 36287 Summary After deploying a Formflow process it is possible for the release of a step to fail with either of the following errors reported:

Java.lang.NoClassDefFoundNo icud36.dll in the java.library.path

Workaround Ensure that the Tomcat instance to which the Formflow process has been deployed has access to a valid version of the iProcess Server Objects client libraries.

Do this by either copying them to the shared folder in the Tomcat directory or add the path to the java.library.path in the Tomcat start up script.

MR 36047 Summary The installer logs an error "product bean CreateStartMenu does not exist" on AIX installations.

Workaround None. This error can be safely ignored.

MR 35674 Summary An iProcess BusinessWorks step cannot import a schema using the interface file introspection method if the interface file (.wsdl file) contains double-byte characters such as Japanese schema names.

Workaround Use the Live Link to BusinessWorks introspection method. The iProcess BusinessWorks step can then import the Japanese schema correctly.



26 | Release Notes

CR 19895 Summary The DatabaseConnection tab of the iProcess Connection resource by default has Auto Config checked to retrieve the database configuration from the iProcess Objects Server. In a Windows SQL Server environment the database URL is populated by the ODBC data source name - not the name of the SQL Server database. In this environment the Database Connection must be manually configured.

Workaround Ensure that the ODBC Data Source has the same name as the iProcess SQL Server database.

CR 19357 Summary iProcess fields with a colon in their names, such as SW_STARTER:NAME or CUST:POSTCODE, cannot be imported or exported using the BusinessWorks Connector plug-ins. This is because the colon is not a valid character in XML element names.

Workaround None.

CR 18744 Summary The Test button in the JMS Administration Utility dialog is unexpectedly disabled. This is because JMS provider and destination data is not available until an IMPORT or a REFRESH on LiveLink is carried out.

Workaround Do a REFRESH on LiveLink or re-import the WSDL.

CR 19253 Summary If the iProcess Decisions Server Plug-in v.10.3 is installed, an iProcess procedure that calls a BusinessWorks process may fail with a message indicating "Error inside execute method of Java object". This is because installing iProcess Decisions creates a difference in the classloading order.

Workaround Re-install the iProcess Decisions .jar files into SWDIR/eaijava/libs/repository/user.



Restrictions | 27

Restrictions Affecting the iProcess Conductor Server Plug-insThis table lists restrictions that affect the iProcess Conductor Server Plug-ins only.


CR 1-72O2UG Summary In certain scenarios fatal exceptions are not being handled by the Order Plug-in.This includes exceptions thrown during order or order line state changes. Under these circumstances, the exception is not written to the iProcess client audit trail and the case will continue to completion, even when the exception handling is set to Fail Step on XML Exception.

Workaround Please check the eaijava logs for order state change/order line state change exceptions.


28 | Release Notes

Restrictions Affecting the BusinessWorks iProcess Plug-inThis table lists restrictions that affect the BusinessWorks iProcess Plug-in only.


(No ID) Summary When you install the BusinessWorks iProcess Plug-in into a 64-bit TIBCO Runtime Agent (TRA), the plug-in fails because it requires a 64-bit SSO JNI library and the installer provides only a 32-bit library.

Workaround Replace the 32-bit library with the 64-bit library (on Windows it is three libraries) from the appropriate SSO Java release. The procedure is as follows:

On UNIX:

1. Obtain from TIBCO Support the correct SSO Java release for the version of the plug-in and the platform type.

2. Extract the install software to a temporary directory.

3. Go to the temporary directory and locate the lib64 directory. This directory contains the 64-bit library libssoJNI.so.

4. Copy the libssoJNI library from the lib64 directory and overwrite the file under $TIBCO_HOME/bw/plugins/lib.

On Windows:

1. Obtain from TIBCO Support the correct SSO Java release for the version of the plug-in and the platform type.

2. Install the software to a temporary directory.

3. Go to the temporary install and locate the x64 directory. This directory contains the following 64-bit libraries:

— ssoJNI.dll

— icudt36.dll

— icuuc36.dll

4. Copy these libraries from the x64 directory and overwrite the files under TIBCO_HOME\bw\plugins\bin.

IPTP-637 Summary . Although DB2 databases are not supported in iProcess Technology Plug-ins version 11.3.0, it is still possible to select DB2 in an iProcess Connection resource in the BusinessWorks iProcess Plug-in.

Workaround Do not select DB2.


Restrictions | 29

IPTP-622 Summary If a BusinessWorks project contains an iProcess Service Agent that references an iProcess Connection resource, the connection information must be correct (that is, must match the iProcess Engine) or a message may be generated saying that the Service Agent cannot be found. This error can occur even when calling a process that does not use the iProcess Connection.

Workaround Ensure that all connection information is correct. In particular, remember to use the Test Connection button on the iProcess Connection resource to check the connection.

IPTP-607 Summary When you click the iProcess Forms Documentation icon displayed on the Start menu under BusinessWorks, a ’Missing Shortcut’ message is displayed.

Workaround None. iProcess Forms Documentation is not available.

IPTP-574 Summary Depending on whether the version of BusinessWorks being used has the Data Direct JDBC drivers included, the automatic configuration of an iProcess Connection may not work.

Workaround Manually configure the fields on the Database Connection tab of the iProcess Connection resource in the BusinessWorks iProcess Plug-in, using data for the JDBC driver installed for BusinessWorks. See "iProcess Connection" in the TIBCO iProcess BusinessWorks Connector User’s Guide for details of these fields.

MR 36197 Summary: On HP-UX systems, installation of the TIBCO BusinessWorks iProcess Plug-in appears to complete successfully. However the file Tibuninstall.bin necessary for uninstallation is missing from the /_uninst directory.

Workaround: To uninstall, type the following:

$ cd <PRODUCT_HOME>/_uninst$ java -cp uninstaller.jar run



30 | Release Notes

Restrictions Affecting the EAI POJO Plug-in OnlyThis table lists restrictions that affect all the iProcess Technology plug-ins.

MR 31167 Summary If you upgrade from Version 10.3.4 of the BusinessWorks iProcess Plug-in (part of the Version 10.3.4 TIBCO iProcess BusinessWorks Connector), some Version 10.3.4 documents are incorrectly left on the system.

The following Version 11.n documents are installed in the $TIBCO_HOME\bw\plugins\iprocess\doc\ip\pdf directory:

• TIBCO BusinessWorks iProcess Plug-in Release Notes, Version 11.n. (tib_bwip_plugin_release_notes.pdf)

• TIBCO iProcess BusinessWorks Connector User’s Guide, Version 11.n (tib_ip_bw_connector_user_guide.pdf)

• TIBCO iProcess Technology Plug-ins Installation, Version 11.n (tib_ip_technology_plugins_installation_guide.pdf)

The following Version 10.3.4 documents are incorrectly also left in the same directory:

• TIBCO iProcess BusinessWorks Connector Installation Guide, Version 10.3.4 (tib_ip_bw_connector_installation_guide.pdf)

• TIBCO iProcess BusinessWorks Connector Release Notes, Version 10.3.4 (tib_ip_bw_connector_release_notes.pdf)

In addition:

• the Version 11.n readme (readme.txt) is installed in the TIBCO_HOME\bw\plugins\iprocess directory.

• the Version 10.3.4 readme (readme_tib_ip_bw_connector.txt) is incorrectly left in the TIBCO_HOME\bw\plugins\iprocess\doc directory.

Workaround None.



MR 31847 Summary: Date arrays are failing to map correctly at run time. if you map the response value using a specific array index value and that index does not exist at run time, then an error will occur. For example, mapping RV[4] when only elements 0 to 3 exist is not permitted.

Workaround: None.


Restrictions | 31

Restrictions Affecting all iProcess Technology Plug-ins This table lists restrictions that affect all the iProcess Technology plug-ins.


IPTP-641 Summary The keyboard may lock when installing on a Linux system that uses a SCIM (Smart Common Input Method) front end.

Workaround Follow these steps:

1. Open the ~/.scim/config file in a text editor.

2. Find the line:

/FrontEnd/X11/Dynamic = value

(If the .scim/config file is not present on your system, create it and add the line referred to.)

3. Change value from the default false to true.

4. Logout and login again. SCIM will still be enabled and working. The keyboard does not lock and you can continue with installation.

IPTP-621 Summary When you modify JMS information using the JMS Administration utility, spurious warning messages relating to missing cache keys and to AliasControlDAO may appear in the eai-warn.log and eaijavaidentifier.log files.

Workaround Ignore these messages.

IPTP-613 Summary When you run the iProcess Technology Plug-ins version 11.3 the version number of the iProcess Conductor plug-ins is given as 11.2 for a fresh installation, but as 11.3 for a re-installation.

Workaround None. These plug-ins are actually delivered as version 11.2, and have not changed at iProcess Technology Plug-ins version 11.3.

IPTP-605 Summary Under certain circumstances, it is possible to select the Update System Path checkbox when installing on UNIX, although this option applies only to Windows.

Workaround None. However, the behavior has no adverse consequences.

IPTP-456 Summary Database connection fails when using SQL Server with Windows authentication.

Workaround None.


32 | Release Notes

IPTP-609 Summary Installing iProcess Technology Plug-ins fails if you specify a port number that is already used by another iProcess Technology Plug-ins installation.

Workaround Ensure that all port numbers specified when installing the product are not currently in use.

IPTP-606 Summary When you uninstall iProcess Technology Plug-ins the log.txt file may show errors although the uninstall was successful. Examples of these errors are as follows:

(Nov 18, 2011 3:44:17 PM), Uninstall, com.installshield.product.actions.XmlTransformer, err, ProductException: (error code = 601; message="err"; additional data = [XML transformation failure: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: /export/home/staffwar/installations/w2239ora/uninstall/../eaiframework/frameworkconfig.xml (No such file or directory)])

STACK_TRACE: 25

ProductException: (error code = 601; message="err"; additional data = [XML transformation failure: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: /export/home/staffwar/installations/w2239ora/uninstall/../eaiframework/frameworkconfig.xml (No such file or directory)]) at com.installshield.product.actions.XmlTransformer.productException(Unknown Source)

Workaround None.

MR 36429 Summary If you have iProcess Java Server Plug-in, iProcess Conductor Server Plug-in and iProcess XML Transform Plug-in installed and then at a later date add iProcess BusinessWorks Server Plug-in by choosing New Installation, the resulting configuration is incorrect.

Workaround: Perform the installation a second time choosing Re-install/Repair/Upgrade An Existing Installation and the problem is corrected.



Restrictions | 33

MR 36422 Summary When uninstalling the iProcess Technology Plug-ins in Console mode the following error may be displayed:

$SWDIR\uninstall\..\eaiframework\frameworkconfig.xml (The system cannot find the path specified)

In GUI and Silent modes the error is logged but not displayed.

This error is benign and the uninstallation completes successfully.

Workaround: None.

MR 36410 Summary Uninstalling the iProcess Conductor Server Plug-in leaving behind the iProcess BusinessWorks Server Plug-in and iProcess Java Server Plug-in, leaves the classloader.properties and mnemonic.properties in their original state. This has no adverse effects at run-time.

Workaround: None.

MR 36351 Summary When uninstalling iProcess Technology Plug-ins, uninstall is not removing the $SWDIR/jmslib directory and mnemonic.properties file.

Workaround: None.

MR 36294 Summary On UNIX platforms the rendering of some fields is cropped.

Workaround: None.

MR 36233 Summary This version of iProcess Technology Plug-ins for HP-UX (PA-RISC) does not work with Java 1.6.

Workaround: None.

MR 36177 Summary: On some UNIX systems, the iProcess Technology Plug-ins installer cannot find the iProcess node or the JBoss Home directory, so installation fails.

This is caused by including \u in the prompt PS1. Normally \u would cause the username to be displayed, but some command shells interpret it as indicating a Unicode sequence.

Workaround: Modify the PS1 prompt to not include \u.

MR 36136 Summary: When an array is passed to a BusinessWorks process and returned, the last field may be copied twice, resulting in an extra element being added.

Workaround: None.



34 | Release Notes

MR 35843 Summary On DB2 systems, calling the SW_SET_QUEUE stored procedure followed by the SW_DELAYED_RELEASE stored procedure causes the delayed release to fail.

Workaround Call SW_DELAYED_RELEASE without explicitly calling SW_SET_QUEUE.

MR 35785 Summary After selecting the option to upgrade the iProcess Technology Plug-ins, a warning message is displayed asking, "Are you sure you want to reset the installation files back to their original versions?" This message is incorrect.

Workaround Answer "Yes" to continue with the upgrade.

MR 31950 Summary: If you are using the iProcess Technology Plug-ins with iProcess Engine version 10.5.0 on a Solaris 8 or Solaris 9 system, the EAI Java Plug-in fails, and causes the BG processes to fail, on startup.

Workaround: Add:

export LD_PRELOAD=/usr/lib/libthread.so

to the env.sh file. A warning message indicating "open failed: illegal insecure pathname" is displayed when the process sentinels start, but the plug-in starts.

MR 31942 Summary: If you specify on the Destination dialog of the installer that the EAI Java Server plug-in should be installed on an iProcess node different from that specified by the $SWDIR environment variable, it is in fact installed on, and registered to, the node specified by $SWDIR and not the node required.

Workaround: Ensure that the $SWDIR environment variable is either not set, or is set correctly, before you start the installation. See the iProcess Engine installation documentation for information on setting this variable.

MR 31105 Summary: When you upgrade to this version, any customizations made to the log4j.properties file are lost. The existing file is overwritten with default values.

Workaround: If you have made any customizations to the log4j.properties file that you wish to retain after upgrade:

1. Take a copy of the file before you perform the upgrade.

2. Perform the upgrade.

Manually edit the new log4j.properties file to re-implement your customizations.



Restrictions | 35

MR 31099 Summary: When you run Setup and you are either:

• upgrading to this version, or

• re-installing this version (with the Modify Existing Installation button selected),

the Audit User Name and Audit Message fields display the default values for a new installation (respectively, swadmin and EAI Java), rather than the actual current system values.

Workaround: None.

CR 19379 Summary: If a step implementing a Withdraw function is configured to produce an exception (for example, for test purposes) using the example code supplied for Withdraw, the step is withdrawn but continues to write to the Java debug log as if still waiting for the withdrawal.

Workaround: None. Note that Withdraw is not supported for EAI BusinessWorks steps.

CR 19274 Summary: Log messages are not enabled for internationalization, but are English only. (All other text is enabled for internationalization.)

Workaround: None.

CR 18405 Summary: When uninstalling iProcess Technology Plug-ins, a directory can be left behind.

Workaround: The directory may be deleted manually.

CR 18371 Summary: During installation, on the Database Configuration screen, the Instance field is available only when Oracle has been selected as the database. It cannot be used to select one of multiple SQL Server instances.

Workaround: If you have multiple SQL Server instances, find out the port number used by the SQL instance to which you wish to connect, and specify it in the Port field.

CR 18291 Summary: If you install both the iProcess Java Server Plug-in and the iProcess Java Client Plug-in on the same machine, and you have the installation program update the PATH environment variable with the location of the Java JVM, it updates the PATH twice.

Workaround: None.



36 | Release Notes

CR 18104 Summary: On UNIX systems, the EAI Java log files are not automatically deleted when the iProcess Engine starts up. (This problem does not affect Windows systems.)

Workaround: Manually delete the EAI Java log files when the iProcess Engine starts up.

CR 17869 Summary: If you use the same iProcess array field for both input and output, a FatalPluginException is generated.

Workaround: Define a different iProcess array field for input and output.

CR 15926 Summary The system path can become corrupted by EAI Plug-ins that update the system path during installation. This is because the system path is limited to 1023 characters and if the installer causes this to be exceeded, the path is concatenated but no error is reported.

Workaround None.

CR 15285 Summary When a Java Object is called from an EAI Java step that contains the following line:

System.exit(0);

the background process that is handling the EAI Java step is terminated.

Workaround None.

CR 15093 Summary The << and >> buttons in the Inputs and Outputs tabs indicate that they support hot keys. However, the hot keys currently do not work.

Workaround None.

CR 15088 Summary During installation, the JRE Details text box does not currently provide a hot key for the text box where you specify the location of the jvm.dll file.

Workaround None.

CR 15046 Summary The EAI Java Server installation program does not set any permissions on the directories that are installed. Refer to the TIBCO iProcess Java Plug-in: User’s Guide for more information.

Workaround None.



Date post:	07-Jul-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

TIBCO iProcess Technology Plug-ins Release Notes...iProcess Technology Plug-ins version 11 .0...

Documents