TIBCO iProcess Technology Plug

TIBCO iProcess Technology Plug
TIBCO iProcess® Technology
Plug-ins
Release Notes
Software Release 11.5.0
April 2015
Two-Second Advantage®
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO Designer,
TIBCO Enterprise Message Service, TIBCO Hawk, TIBCO Rendezvous, TIBCO Adapter, TIBCO iProcess
BusinessWorks Connector, TIBCO iProcess, and TIBCO Runtime Agent 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 © 2003-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIBCO iProcess Technology Plug-ins Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other TIBCO iProcess® Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIBCO iProcess User Documentation Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
vi
vi
vi
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xi
xi
xi
xi
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2
3
4
7
7
Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
9
9
9
Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
10
10
10
11
11
Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
12
12
13
13
14
TIBCO iProcess Technology Plug-ins Release Notes
iv
| Contents
Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issues Affecting the iProcess BusinessWorks Server Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issues Affecting the BusinessWorks iProcess Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issues Affecting the EAI POJO Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issues Affecting All iProcess Technology Plug-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
16
18
23
23
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Root User Fails to Install the TIBCO BusinessWorks iProcess Plug-in on AIX . . . . . . . . . . . . . . . . . . . . . . .
Unable to Start a Case of an iProcess Procedure That Is in the Model Status . . . . . . . . . . . . . . . . . . . . . . .
Unable to Configure Details of the Cluster for RAC Database Type in Console Mode . . . . . . . . . . . . . . . . .
Oracle 12c Is Incompatible with TIBCO JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ineffective Conversion of Native Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIBCO JDBC Driver Version 2.x Is Not Supported for Setting Up Oracle Database Connection . . . . . . . . .
Logs for Unregistering EAIJAVA Written to Unreasonable File During Installation . . . . . . . . . . . . . . . . . . . .
One Extra Value Returned to BusinessWorks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installer Not Informing User When JVM Cannot be Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Misleading Error for Long JNDI Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Possible Loop in the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
28
28
28
28
29
29
30
31
31
31
31
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions Affecting the iProcess BusinessWorks Server Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions Affecting the BusinessWorks iProcess Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions Affecting the EAI POJO Plug-in Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions Affecting All iProcess Technology Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32
32
34
34
35
TIBCO iProcess Technology Plug-ins Release Notes
|v
Preface
TIBCO iProcess® Technology Plug-ins includes the following individual plug-ins:
•
TIBCO iProcess® Java Server Plug-in
•
TIBCO iProcess® BusinessWorks™ Server Plug-in
•
TIBCO BusinessWorks™ iProcess® Plug-in
•
TIBCO iProcess® XML Transform Server Plug-in
•
Related Documentation, page vi
•
Typographical Conventions, page viii
•
Connecting with TIBCO Resources, page xi
Topics
TIBCO iProcess Technology Plug-ins Release Notes
vi
| Related Documentation
Related Documentation
This section lists documentation resources for TIBCO iProcess Technology
Plug-ins you may find useful.
TIBCO iProcess Technology Plug-ins Documentation
•
TIBCO iProcess Technology Plug-ins Installation Read this manual for
instructions on site preparation and installation.
•
TIBCO iProcess Technology Plug-ins Release Notes Read the release notes for a
list of new and changed features for TIBCO iProcess Technology Plug-ins.
This document also contains lists of known issues and closed issues for this
release.
If you are installing from physical media, you can find the Release Notes and
Readme in the Docs folder.
If you are installing from a network server, you should ask your network
administrator where the Release Notes and Readme are stored.
Other TIBCO iProcess® Documentation
•
TIBCO iProcess® Java Server Plug-in Documents This plug-in processes the EAI
Java steps.
•
TIBCO iProcess® BusinessWorks™ Server Plug-in Documents This plug-in
provides the communication mechanism that is used for the engine to make
calls TIBCO ActiveMatrix BusinessWorks™.
•
TIBCO iProcess® XML Transform ServerPlug-in Documents This plug-in
performs transformations on XML data. This plug-in was previously available
as part of TIBCO iProcess Conductor.
TIBCO iProcess User Documentation Library
See the following guides for more information concerning TIBCO iProcess
Technology Plug-ins:
•
TIBCO iProcess Java Plug-in User’s Guide This document explains how to
define and use EAI Java steps in your iProcess procedures. EAI Java steps can
be customized to perform the necessary business actions you require in your
procedure (such as calling methods in Enterprise Java Beans or simply
manipulating data via a Java object). The TIBCO iProcess Java Plug-in
software consists of a client plug-in (which is part of the iProcess Workspace
TIBCO iProcess Technology Plug-ins Release Notes
Preface vii
|
Plug-ins), a server plug-in (which is part of the iProcess Technology Plug-ins),
and an SDK.
•
TIBCO iProcess® BusinessWorks™ Connector User’s Guide This document
explains how to use the iProcess BusinessWorks Connector plug-ins, an
efficient and easy to use interface between TIBCO ActiveMatrix
BusinessWorks™ and the iProcess Engine. The iProcess BusinessWorks
Connector consists of a client plug-in (which is part of the iProcess Workspace
Plug-ins), a server plug-in (which is part of the iProcess Technology Plug-ins),
and a BusinessWorks plug-in (which is also part of the iProcess Technology
Plug-ins).
•
TIBCO iProcess® Modeler Integration Techniques This document explains how to
use EAI steps in your procedures to control updates to external systems and
iProcess case data under transaction control.
TIBCO iProcess Technology Plug-ins Release Notes
viii
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention
Use
TIBCO_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.
ENV_HOME
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.
SWDIR
TIBCO iProcess Engine installs into a directory. This directory is referenced in
documentation as SWDIR. The value of SWDIR depends on the operating system.
For example,
on a Windows server (on the C: drive)
if SWDIR is set to the C:\swserver\staffw_nod1 directory, then the full path to
the swutil command is in the C:\swserver\staffw_nod1\bin\swutil
directory.
on a UNIX or Linux server
if SWDIR is set to the /swserver/staffw_nod1 directory, then the full path to the
command is in the /swserver/staffw_nod1/bin/swutil directory or
the $SWDIR/bin/swutil directory.
swutil
Note: On a UNIX or Linux system, the environment variable $SWDIR should be
set to point to the iProcess system directory for the root and swadmin users.
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.
TIBCO iProcess Technology Plug-ins Release Notes
Preface ix
|
Table 1 General Typographical Conventions (Cont’d)
Convention
Use
bold code
Bold code font is used in the following ways:
font
•
In procedures, to indicate what a user types. For example: Type admin.
•
In large code samples, to indicate the parts of the sample that are of
particular interest.
•
In command syntax, to indicate the default parameter for a command. For
example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]
italic font
Key
combinations
Italic font is used in the following ways:
•
To indicate a document title. For example: See TIBCO ActiveMatrix
BusinessWorks Concepts.
•
To introduce new terms For example: A portal page may contain several
portlets. Portlets are mini-applications that run in a portal.
•
To indicate a variable in a command or code syntax that you must replace.
For example: MyCommand PathName
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.
TIBCO iProcess Technology Plug-ins Release Notes
x
| Typographical Conventions
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
{ }
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}
TIBCO iProcess Technology Plug-ins Release Notes
Preface xi
|
Connecting with TIBCO Resources
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and
resident experts. It is a place to share and access the collective experience of the
TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety
of resources. To register, go to http://www.tibcommunity.com.
How to Access TIBCO Documentation
You can access TIBCO documentation here:
https://docs.tibco.com
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, contact
TIBCO Support as follows:
•
For an overview of TIBCO Support, and information about getting started
with TIBCO Support, visit this site:
http://www.tibco.com/services/support
•
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user
name, you can request one.
TIBCO iProcess Technology Plug-ins Release Notes
xii
| Connecting with TIBCO Resources
TIBCO iProcess Technology Plug-ins Release Notes
|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 9
•
Deprecated and Removed Features, page 10
•
Migration and Compatibility, page 12
•
Closed Issues, page 16
•
Known Issues, page 28
•
Restrictions, page 32
TIBCO iProcess Technology Plug-ins Release Notes
2
|
Release Notes
New Features
This section lists features added since the last major release of this product.
Release 11.5.0
The following are new features in this release.
Empty Date Type Fields Are Allowed (IPTP-795)
When defining basic information for an iProcess BusinessWorks step to invoke
BusinessWorks processes from iProcess Engine, you can leave the date type fields
empty.
See TIBCO iProcess BusinessWorks Connector User’s Guide for more details.
Support for TIBCO ActiveMatrix BusinessWorks 5.12 (IPTP-797)
You can install TIBCO BusinessWorks iProcess Plug-in on the machine where
TIBCO ActiveMatrix BusinessWorks 5.12 is installed.
Support for XSLT 2.0 and XPath 2.0 (IPTP-798)
Support for XSLT 2.0 has been introduced in this release. You can use XPath 2.0 in
TIBCO iProcess BusinessWorks Connector to define the field mappings between
the BusinessWorks process definition and the iProcess Engine procedure.
Delayed Release Has Been Enhanced (IPTP-817)
From this release, TIBCO iProcess BusinessWorks Connector can trigger the
stored procedure in the iProcess database to call and
send the error message to the BG process via JMS if the iProcess Complete
Delayed Release activity fails to complete delayed release of an EAI
BusinessWorks step.
SW_DELAYED_RELEASE_ERR
See "Delayed Release" in TIBCO iProcess BusinessWorks Connector User’s Guide for
more details.
Support for Platforms
In this release, support for the following platforms has been added:
•
Red Hat Enterprise Linux Server 5.10 (32-bit and 64-bit)
•
Red Hat Enterprise Linux Advanced Platform 5.10 (32-bit and 64-bit)
TIBCO iProcess Technology Plug-ins Release Notes
New Features 3
|
•
Red Hat Enterprise Linux Server 7.x (64-bit)
Support for Databases
In this release, support for the following databases has been added:
•
SQL Server 2014
•
DB2 Universal Database 10.5
Supported Java Versions
Java Standard Edition 8 is supported in the release.
See TIBCO iProcess Technology Plug-ins Installation guide for details.
Release 11.4.1
Adding the Decimal Symbol Field (IPTP-46)
The Decimal Symbol field has been added to the Advanced tab of the iProcess
Connection shared resource in TIBCO BusinessWorks iProcess Plug-in. You can
specify a character in this field to separate elements of numerical value.
Operating the JMS Administration Utility in Console Mode (IPTP-446)
Commands are available for operating the JMS Administration Utility in console
mode. These commands contain:
jmsadmin password
password, jmsadmin show destinations|providers|ssl,
jmsadmin export XMLFileName, jmsadmin import XMLFileName, jmsadmin test
destination
id|name, and jmsadmin upgrade.
For more information about these commands, see "Chapter 5, Managing Your JMS
Provider" in TIBCO iProcess BusinessWorks Connector User’s Guide.
Setting Up SQL Server Windows Authentication (IPTP-456)
The SQL Server Windows authentication database type is now supported.
For more information about setting up SQL Server Windows authentication, see
TIBCO iProcess Technology Plug-ins Installation.
TIBCO iProcess Technology Plug-ins Release Notes
4
|
Release Notes
Hiding the JMS Provider Details Dialog (IPTP-534)
The JMS Provider Details dialog is no longer displayed after the database
connection configuration is finished if you only select the TIBCO iProcess Java
Server Plug-in feature to be installed in the Features dialog when installing
TIBCO iProcess Technology Plug-ins.
Adding a Configuration File for Authenticating Oracle Database Connection (IPTP-549)
The tnsname.ora file can be used to configure the authentication details of the
Oracle database connection when installing TIBCO iProcess Technology Plug-ins.
For more information about the usage of tnsname.ora file, see "Appendix A,
Installation Data Reference" in TIBCO iProcess Technology Plug-ins Installation.
Support for Platforms
In this release, the following supported platforms are added:
•
Microsoft Windows 8.1 (32-bit and 64-bit)
•
Microsoft Windows Server 2012 R2 (64-bit)
Support for Databases
In this release, a new database is supported:
•
Oracle 12c release 12.1.x
Supported JMS Providers
In this release, the following versions of TIBCO Enterprise Message Service (EMS)
are added as JMS providers:
•
EMS 7.0.1
•
EMS 8.0
Release 11.4.0
Advanced Functions for Triggering Events (IPTP-703)
The following functions are added to improve the trigger event operation in the
case of an iProcess Engine procedure:
•
Resurrect a case if the case is closed.
•
Update data for outstanding work items after processing the triggered event.
TIBCO iProcess Technology Plug-ins Release Notes
New Features 5
|
•
Recalculate deadlines of the main case and sub-cases.
See TIBCO iProcess BusinessWorks Connector User’s Guide for more information.
The Payload of EMS Is Compressed (IPTP-708)
The messages that are sent over EMS for data exchange between TIBCO iProcess
Engine and TIBCO ActiveMatrix BusinessWorks are compressed.
Prioritizing Background Queues (IPTP-716)
You can now set priorities for internal message queues in the iProcess Procedure
Case Management, iProcess Complete Delayed Release, and iProcess Start Case
activities of the iProcess palette when passing messages between iProcess
processes.
See TIBCO iProcess BusinessWorks Connector User’s Guide for more information.
Setting Up Communication with an IPv6 Address (IPTP-729)
When you use JMS to communicate between iProcess Engine and TIBCO
ActiveMatrix BusinessWorks™, you can set up communication using an IPv6
address.
TIBCO iProcess Technology Plug-ins only supports inbound communication at
runtime and outbound communication. In addition, for inbound communication:
•
If you want to use an IPv6 address for an inbound communication at design
time, you must upgrade TIBCO iProcess® Server Objects to a version that is
higher than 11.4.0 after installing TIBCO BusinessWorks iProcess Plug-in and
make sure the upgraded version supports IPv6. Contact TIBCO Support for
details of versions of TIBCO iProcess Server Objects that support IPv6.
Contact TIBCO Support for more information on versions of TIBCO iProcess
Server Objects that supports IPv6.
•
If you use TIBCO iProcess Server Objects as the protocol for the inbound
communication, make sure the Auto Config Date Format checkbox is
unchecked in the Advanced tab of the iProcess Connection activity.
See TIBCO iProcess BusinessWorks Connector User’s Guide for more information.
Support TIBCO Universal Installer for TIBCO BusinessWorks iProcess Plug-in (IPTP-751)
TIBCO universal installer is used for installing TIBCO BusinessWorks iProcess
Plug-in. The installer runs automatically when installing TIBCO iProcess
Technology Plug-in.
TIBCO iProcess Technology Plug-ins Release Notes
6
|
Release Notes
To install TIBCO BusinessWorks iProcess Plug-in, update the values of the
installationRoot and environmentName properties in the
TIBCOUniversalInstaller_bwpluginiprocess_11.4.0.silent file before
installing TIBCO iProcess Technology Plug-in. TIBCO BusinessWorks iProcess
Plug-in must be installed in the same directory where TIBCO Runtime Agent and
TIBCO ActiveMatrix BusinessWorks are installed. For example:
<entry key="installationRoot">C:\tibco</entry>
<entry key="environmentName">TIBCO_HOME</entry>
Support for Platforms
In this release, the following supported platforms are added:
•
Microsoft Windows 8 (32-bit and 64-bit)
•
Microsoft Windows Server 2012 (64-bit)
•
Oracle SPARC Solaris 11 (64-bit)
•
Oracle x86 Solaris 11 (64-bit)
Support for Databases
In this release, the following supported databases are added:
•
DB2 Universal Database 10.1
•
SQL Server 2012
Supported Java Versions
Java Standard Edition 7 is supported in the release.
See the TIBCO iProcess Technology Plug-ins Installation guide for details.
Supported JMS Providers
In this release, TIBCO Enterprise Message Service (EMS) version 7 is supported as
a JMS provider.
TIBCO iProcess Technology Plug-ins Release Notes
New Features 7
|
Release 11.3.1
Application Server Versions
iProcess Technology Plug-ins version 11.3.1 adds support for Oracle WebLogic
version 10.3.4 and JBoss EAP version 5.1 as application servers for the iProcess
Conductor Plug-ins.
Oracle WebLogic was previously known as BEA WebLogic. References to BEA
WebLogic may still remain in the software and documentation.
Support for DB2 Databases
Support for DB2 Universal Database 9.5 and 9.7 has been added in this release.
Support for Platforms
In this release, support for the following platforms has been added:
•
IBM AIX 5.3, 6.1 and 7.1
•
HP-UX on Itanium 11i v2 (B.11.23) and HP-UX on Itanium 11i v3 (B.11.31)
•
Red Hat Enterprise Linux Server 6.x
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.
TIBCO iProcess Technology Plug-ins Release Notes
8
|
Release Notes
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.
Note that Java 5 is not supported for this release of the iProcess Technology
Plug-ins.
TIBCO iProcess Technology Plug-ins Release Notes
Changes in Functionality 9
|
Changes in Functionality
This section lists changes in functionality since the last major release of this
product.
Release 11.5.0
There are no changes in functionality in this release.
Release 11.4.1
There are no changes in functionality in this release.
Release 11.4.0
Database Connection Is Configurable (IPTP-707)
You can configure the database JDBC driver for database connection in the
BWPlugin.properties file.
See TIBCO iProcess BusinessWorks Connector User’s Guide for more information.
Database Type in the iProcess Connection Shared Resource Is Configurable (IPTP-705)
In the iProcess Connection shared resource of the iProcess palette, you can specify
the database type in the Database Type field of the Database Connection tab by
inputting the database type or by setting a predefined global variable.
See TIBCO iProcess BusinessWorks Connector User’s Guide for more information.
Release 11.3.1
There are no changes in functionality in this release.
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.
Note in particular that DB2 databases are not supported at release 11.3.0.
TIBCO iProcess Technology Plug-ins Release Notes
10
|
Release Notes
Deprecated and Removed Features
This section describes any features that have been deprecated or removed since
the last major release of this product.
For deprecated features, if relevant, useful alternative to the deprecated features
are listed. Any use of a deprecated feature should be discontinued as it may be
removed in a future release. You should avoid becoming dependent on
deprecated features and become familiar with the suggested alternative features.
Release 11.5.0
Deprecated Features
No features are deprecated in this release.
Removed Features
•
TIBCO iProcess Conductor Server Plug-ins, including TIBCO iProcess
Conductor Orchestration Server Plug-in and TIBCO iProcess Conductor
Order Server Plug-in are removed from TIBCO iProcess Technology Plug-ins.
•
From this release, TIBCO iProcess Technology Plug-ins is no longer supported
on Microsoft Windows Server 2003.
Release 11.4.1
Deprecated Features
In this release, support for Microsoft Windows Server 2003 is deprecated.
Removed Features
From this version, TIBCO iProcess Technology Plug-ins is no longer supported on
Microsoft Windows XP.
Release 11.4.0
Deprecated Features
No features are deprecated in this release.
TIBCO iProcess Technology Plug-ins Release Notes
Deprecated and Removed Features 11
|
Removed Features
The TIBCO ActiveMatrix BusinessWorks FormBuilder functionality in the
iProcess Palette of the iProcess BusinessWorks Connector is removed.
FormBuilder forms are no longer supported.
Release 11.3.1
From this version, TIBCO iProcess Technology Plug-ins is no longer supported on
WebLogic 9.2.x.
Release 11.3.0
The TIBCO BusinessWorks FormBuilder functionality in the iProcess Palette of
the iProcess BusinessWorks Connector is deprecated. FormBuilder forms will no
longer be supported in future releases.
TIBCO iProcess Technology Plug-ins Release Notes
12
|
Release Notes
Migration and Compatibility
This section explains how to migrate from a previous release to this release.
Release 11.5.0
The table below lists other TIBCO products with which TIBCO iProcess
Technology Plug-ins has direct compatibility requirements. It also lists the
versions of those products that are compatible with this version of TIBCO
iProcess Technology Plug-ins.
Validated versions have been successfully tested by TIBCO for compatibility with
this version of TIBCO iProcess Technology Plug-ins. Compatible versions have
not been formally validated, but have no known incompatibilities with this
version of TIBCO iProcess Technology Plug-ins.
Product
Validated
Version(s)
Compatible
Version(s)
TIBCO iProcess Workspace Plug-ins
Version 11.5.0
None
TIBCO iProcess Workspace (Windows)
Version 11.5.0
and 11.4.2
None
Release 11.4.1
The table below lists other TIBCO products with which TIBCO iProcess
Technology Plug-ins has direct compatibility requirements. It also lists the
versions of those products that are compatible with this version of TIBCO
iProcess Technology Plug-ins.
Validated versions have been successfully tested by TIBCO for compatibility with
this version of TIBCO iProcess Technology Plug-ins. Compatible versions have
not been formally validated, but have no known incompatibilities with this
version of TIBCO iProcess Technology Plug-ins.
Product
Validated
Version(s)
Compatible
Version(s)
TIBCO iProcess Workspace Plug-ins
Version 11.4.1
None
TIBCO iProcess Workspace (Windows)
Version 11.4.1
and 11.4.2
None
TIBCO iProcess Technology Plug-ins Release Notes
Migration and Compatibility 13
|
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 TIBCO iProcess Technology Plug-ins.
•
Later than any of those listed, see the readme file for that product/version to
determine if it is compatible with this version of TIBCO iProcess Technology
Plug-ins. If the readme file does not provide a definitive answer, contact
TIBCO Support for further assistance.
Release 11.4.0
The table below lists other TIBCO products with which the iProcess Technology
Plug-ins has direct compatibility requirements. It also lists 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.
Product
Validated
Version(s)
Compatible
Version(s)
TIBCO iProcess Workspace Plug-ins
Version 11.4.0
None
TIBCO iProcess Workspace (Windows)
Version 11.4.0
None
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, see the readme file for that product/version to
determine if it is compatible with this version of the iProcess Technology
Plug-ins. If the readme file does not provide a definitive answer, contact
TIBCO Support for further assistance.
Release 11.3.1
The table below lists other TIBCO products with which the iProcess Technology
Plug-ins has direct compatibility requirements. It also lists the versions of those
products that are compatible with this version of the iProcess Technology
Plug-ins.
TIBCO iProcess Technology Plug-ins Release Notes
14
|
Release Notes
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.
Product
Validated
Version(s)
Compatible
Version(s)
TIBCO iProcess Workspace Plug-ins
Version 11.3.1
None
TIBCO iProcess Workspace (Windows)
Version 11.3.1
Version 11.1.3
Version 11.3
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 TIBCO iProcess Technology Plug-ins.
•
later than any of those listed, see the readme file for that product/version to
determine if it is compatible with this version of TIBCO iProcess Technology
Plug-ins. If the readme file does not provide a definitive answer, contact
TIBCO Support for further assistance.
Release 11.3.0
The table below lists other TIBCO products with which the iProcess Technology
Plug-ins has direct compatibility requirements. It also lists 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.
Product
Validated
Version(s)
Compatible
Version(s)
TIBCO iProcess Workspace Plug-ins
Version 11.3
None.
TIBCO iProcess Workspace (Windows)
Version 11.3
None.
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.
TIBCO iProcess Technology Plug-ins Release Notes
Migration and Compatibility 15
|
•
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.
TIBCO iProcess Technology Plug-ins Release Notes
16
|
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 16.
•
The second table lists issues that affect only the TIBCO BusinessWorks
iProcess Plug-in. If you do not intend to install this plug-in, you do not need to
read this table. See page 18.
•
The third 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 23.
•
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 Server Plug-in are relevant to all users. See page 23.
Issues Affecting the iProcess BusinessWorks Server Plug-in
This first table lists changes that affect the iProcess BusinessWorks Server Plug-in
only.
Closed in
Release
Defect #
Summary
11.5.0
CR 19357
iProcess fields with the names that included a colon in their
names, such as SW_STARTER:NAME or CUST:POSTCODE, could
not be imported or exported by using iProcess BusinessWorks
Connector. This was because the colon was not a valid character in
the name of an XML element.
Corrected.
11.5.0
CR 19895
The DatabaseConnection tab of the iProcess Connection resource
by default had the Auto Config selected to retrieve the database
configuration from the iProcess Objects Server. In a Windows SQL
Server environment, the database URL was 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.
Corrected.
TIBCO iProcess Technology Plug-ins Release Notes
Closed Issues 17
|
Closed in
Release
Defect #
Summary
11.4.1
IPTP-446
Add support for operating the JMS Administration Utility in
console mode.
Implemented. See Adding a Configuration File for Authenticating
Oracle Database Connection (IPTP-549) on page 4.
11.4.1
IPTP-550 (Parent
IPTP-244)
The TIBCO BusinessWorks iProcess Plug-in resource, iProcess
Service Agent, failed to create an interface definition file if XML
Canon was specified as the repository for the BusinessWorks
project.
Corrected.
11.4.0
IPTP-396
In the JMS Administration Tool, the JMS Provider could not be
added with the same JMS provider name as the predefined one.
Corrected.
TIBCO iProcess Technology Plug-ins Release Notes
18
|
Release Notes
Issues Affecting the BusinessWorks iProcess Plug-in
This table lists changes that affect the BusinessWorks iProcess Plug-in only.
Closed in
Release
Defect
Summary
11.5.0
IPTP-574
When configuring an iProcess Connection shared resource, if you
selected the Auto Config check box and used IPv4 as the inbound
communication address at run time, the connection failed because
the incorrect configuration of the Database URL field which was
performed automatically.
Corrected.
11.5.0
IPTP-795
Empty date type fields are allowed when defining basic information
for an iProcess BusinessWorks step.
Implemented. See Empty Date Type Fields Are Allowed (IPTP-795)
on page 2.
11.5.0
IPTP-797
TIBCO BusinessWorks iProcess Plug-in is supported on TIBCO
ActiveMatrix BusinessWorks 5.12 in this release.
Implemented. See Support for TIBCO ActiveMatrix BusinessWorks
5.12 (IPTP-797) on page 2.
11.5.0
IPTP-798
TIBCO iProcess BusinessWorks Connector adds supports for XSLT
2.0 in this release.
Implemented. See Support for XSLT 2.0 and XPath 2.0 (IPTP-798) on
page 2.
11.5.0
IPTP-803
After upgrading TIBCO iProcess BusinessWorks Connector 11.2.0 to
11.4.1, the projects created in the version of 11.2.0 did not work.
Corrected.
TIBCO iProcess Technology Plug-ins Release Notes
Closed Issues 19
|
Closed in
Release
Defect
Summary
11.5.0
IPTP-812
When continuously running more than 300 BusinessWorks
processes in TIBCO Designer by using TIBCO iProcess
BusinessWorks Connector, if you clicked Window > Show Console
from the menu, the following error message was displayed on the
console:
java.sql.SQLException: ORA-01000: maximum open cursors
exceeded
ORA-01000: maximum open cursors exceeded
ORA-06512: at "SYS.DBMS_AQ", line 169
ORA-06512: at "SWPRO11414.SSOLITE_MSG", line 1094
ORA-06512: at "SWPRO11414.SSOLITE", line 791
ORA-06512: at line 1
Corrected.
11.5.0
IPTP-817
Add asynchronous call in iProcess BusinessWorks Connector to
notify the BG process if performing delayed release of an EAI
BusinessWorks step has failed.
Implemented. See Delayed Release Has Been Enhanced (IPTP-817)
on page 2.
11.5.0
IPTP-839
When starting a case in TIBCO ActiveMatrix BusinessWorks, if the
SW_CP_VALUE field was set to a value between 1 and 999, the value
of the case priority returned to TIBCO iProcess Engine was changed
to 1.
Corrected.
11.5.0
IPTP-840
When configuring database connection for a BusinessWorks process
that was in the Delayed Release mode in an iProcess Connection
shared resource, if you selected the Auto Config check box and set
up a JDBC driver in the BWPlugin.properties file, TIBCO JDBC
driver was used by iProcess Service Agent for the database
connection.
Corrected.
TIBCO iProcess Technology Plug-ins Release Notes
20
|
Release Notes
Closed in
Release
Defect
Summary
11.4.1
IPTP-46
The Decimal Symbol field has been added to the Advanced tab of
the iProcess Connection shared resource in TIBCO BusinessWorks
iProcess Plug-in.
Implemented. See Adding the Decimal Symbol Field (IPTP-46) on
page 3.
11.4.1
IPTP-774
When right-clicking on the iProcess Conncetion shared resource and
choosing What Is This? from the popup menu, the HTTP 404 Not
Found page was displayed.
Corrected.
11.4.0
IPTP-396
In the JMS Administration Tool, the JMS Provider could not be
added with the same JMS provider name as the predefined one.
Corrected.
11.4.0
IPTP-684
An error occurred when communicating between TIBCO iProcess
Engine and TIBCO ActiveMatrix BusinessWorks, if you configured
JMS Administrator with the SSL authentication setting.
Corrected.
11.4.0
IPTP-703
Advanced Functions are added to improve the trigger event
operation in the case of an iProcess Engine procedure.
Implemented. See Advanced Functions for Triggering Events
(IPTP-703) on page 4.
11.4.0
IPTP-705
Make the Database Type field configurable. This field is located in
the Database Connection tab of the iProcess Connection shared
resource.
Implemented. See Database Type in the iProcess Connection Shared
Resource Is Configurable (IPTP-705) on page 9.
11.4.0
IPTP-707
Make database connection manually configurable.
Implemented. See Database Connection Is Configurable (IPTP-707)
on page 9.
11.4.0
IPTP-716
Add internal message queue priorities.
Implemented. See Prioritizing Background Queues (IPTP-716) on
page 5.
TIBCO iProcess Technology Plug-ins Release Notes
Closed Issues 21
|
Closed in
Release
Defect
Summary
11.4.0
IPTP-723
The deadlines of sub-cases were not recalculated when triggering an
event with the Recalculate Deadlines (Main Case and Sub-cases)
checkbox checked. The checkbox is located in the Configuration tab
of the iProcess Procedure Case Management activity.
Corrected.
11.4.0
IPTP-725
In the Configuration tab of the iProcess Procedure Case
Management activity, if you set the trigger event operation with the
Update Pack Data and Recalculate Deadlines checkboxes checked,
the event would be triggered twice.
Corrected.
11.4.0
IPTP-732
An error occurred when starting a case if the value of the
field was set to 1000 using the iProcess palette.
SW_CP_VALUE
Corrected.
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 BusinessWorks 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.
TIBCO iProcess Technology Plug-ins Release Notes
22
|
Release Notes
Closed in
Release
Defect
Summary
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.
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 BusinessWorks
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.
TIBCO iProcess Technology Plug-ins Release Notes
Closed Issues 23
|
Issues Affecting the EAI POJO Plug-in
The following table lists changes that affect the EAI POJO Plug-in only.
Closed in
Release
11.3.0
Defect #
Summary
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.
Issues Affecting All iProcess Technology Plug-ins
The following table lists changes that affect all the iProcess Technology plug-ins.
Closed in
Release
Defect #
Summary
11.5.0
IPTP-397
When uninstalling iProcess Technology Plug-ins, the universal
installer did not remove the $SWDIR/jmslib directory and
mnemonic.properties file.
(Parent
MR 36351)
Corrected.
11.5.0
IPTP-605
Under certain circumstances, it was possible to select the Update
System Path check box when installing TIBCO iProcess Technology
Plug-ins on UNIX platforms, although this option only applied to
Windows.
Corrected.
11.5.0
IPTP-790
The BG processes failed to start if you used EAI Java steps to call
custom Java code to connect to IBM WebSphere.
Corrected.
11.5.0
IPTP-791
When installing iProcess Technology Plug-ins on Linux platforms, if
multiple JAR files were added to the classpath for the provider and the
colon (:) character, rather than the semicolon (;) character, was used as
the separator among the path of the JAR files in the Database
Configuration dialog, the installation failed.
Corrected.
TIBCO iProcess Technology Plug-ins Release Notes
24
|
Release Notes
Closed in
Release
Defect #
Summary
11.5.0
IPTP-802
After upgrading TIBCO iProcess Technology Plug-ins to version 11.4.0
in silent mode, the connection to the database failed when restarting
TIBCO iProcess Engine due to the new encrypted password having
been reset incorrectly.
Corrected.
11.5.0
11.5.0
IPTP-820
(Parent
MR 36047)
The installer logged an error "product bean CreateStartMenu does not
exist" on AIX installations.
IPTP-822
The system path was corrupted by EAI Plug-ins that updated the
system path during installation. This was because the system path was
limited to 1023 characters and if the installer caused this to be
exceeded, the path was concatenated but no errors were reported.
(Parent CR
15926)
Corrected.
Corrected.
11.4.1
IPTP-57
On AIX and Solaris, the _uninsteaijavaplugin folder was left
behind after TIBCO iProcess Java Plug-in was uninstalled from the
machine.
Corrected.
11.4.1
IPTP-456
Add support for setting up SQL Server Windows authentication.
Implemented. See Adding a Configuration File for Authenticating
Oracle Database Connection (IPTP-549) on page 4.
11.4.1
IPTP-534
The JMS Provider Details dialog is no longer displayed after the
database connection configuration is finished.
Implemented. See Hiding the JMS Provider Details Dialog (IPTP-534)
on page 4.
11.4.1
IPTP-549
The tnsname.ora file is available when configuring the authentication
details for the Oracle database connection.
Implemented. See Adding a Configuration File for Authenticating
Oracle Database Connection (IPTP-549) on page 4.
TIBCO iProcess Technology Plug-ins Release Notes
Closed Issues 25
|
Closed in
Release
Defect #
11.4.1
IPTP-764
Summary
Error messages were recorded in the
file, which was
located in the SWDIR/logs directory when upgrading TIBCO iProcess
Technology Plug-ins from version 11.2.0.4 to version 11.3.1.
TIBCOiProcessBusinessWorksPlugInInstall.log
Corrected.
11.4.1
IPTP-772
After upgrading TIBCO iProcess Technology Plug-ins to version 11.4.0
in silent mode, the connection to the database failed when restarting
TIBCO iProcess Engine due to the new encrypted password having
been reset incorrectly.
Corrected.
11.4.1
IPTP-779
The old JAR files used for JDBC drivers, which were located in the
$SWDIR/eaijava/libs/repository/database directory, were not
removed when upgrading TIBCO iProcess Technology Plug-ins from
version 11.2.0 to version 11.4.0.
Corrected.
11.4.0
IPTP-109
All the files in the SWDIR/eaijava/properties directory rather than
only the property files were loaded when starting TIBCO iProcess
Engine and instantiating the JVM.
Corrected.
11.4.0
IPTP-291
When you install TIBCO iProcess Technology Plug-ins, the directory,
SWDIR, is used as the default directory to locate the Java Virtual
Machine (JVM).
Implemented.
11.4.0
IPTP-311
Java version 1.4 is no longer supported.
Implemented.
11.4.0
IPTP-415
In the jmsbinding.properties file, which is located in the SWDIR
directory, the redundant whitespaces in the JMXConfig.binding
property are removed.
Implemented.
11.4.0
IPTP-708
The EMS payload is compressed.
Implemented. See The Payload of EMS Is Compressed (IPTP-708) on
page 5.
TIBCO iProcess Technology Plug-ins Release Notes
26
|
Release Notes
Closed in
Release
Defect #
Summary
11.4.0
IPTP-729
Add support for setting up communication using an IPv6 address.
Implemented. See Setting Up Communication with an IPv6 Address
(IPTP-729) on page 5.
11.4.0
IPTP-731
On IBM AIX 6.1, an error occurred when registering EAIJAVA during
the TIBCO iProcess Technology Plug-ins installation.
Corrected.
11.4.0
IPTP-740
An error occurred when connecting to TIBCO iProcess Engine if the
file was used as the DB2 JDBC driver for database
connection.
db2jcc.jar
Corrected.
11.4.0
IPTP-741
The wording of all the error messages are improved.
Implemented.
11.4.0
IPTP-748
Replace TIBCO BusinessWorks with TIBCO ActiveMatrix
BusinessWorks in the wording of all error messages.
Implemented.
11.4.0
IPTP-751
TIBCO universal installer is used for installing TIBCO BusinessWorks
iProcess Plug-in.
Implemented. See Support TIBCO Universal Installer for TIBCO
BusinessWorks iProcess Plug-in (IPTP-751).
11.3.1
IPTP-790
The BG processes failed to start if you used EAIJAVA steps to call
custom Java code to connect to IBM WebSphere.
Corrected.
11.3.1
IPTP-662
Add support for JAVA 6 on AIX and HP platforms.
Implemented.
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.
TIBCO iProcess Technology Plug-ins Release Notes
Closed Issues 27
|
Closed in
Release
Defect #
Summary
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 BusinessWorks 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.
TIBCO iProcess Technology Plug-ins Release Notes
28
|
Release Notes
Known Issues
This section lists known issues for the current version.
Root User Fails to Install the TIBCO BusinessWorks iProcess Plug-in on AIX
When you run the setupaix setup program as the root user to install the TIBCO
BusinessWorks iProcess Plug-in on the AIX platform, the following error message
is displayed and the installation fails:
Unhandled exception in signal handler. Protected function:
generateDiagnosticFiles
You can use one of the following workarounds to resolve this issue:
•
Run the TIBCOUniversalInstaller-aix.bin setup program as the root user
to install the TIBCO BusinessWorks iProcess Plug-in on the AIX platform.
•
Run the setupaix setup program as the pro user to install the TIBCO
BusinessWorks iProcess Plug-in on the AIX platform.
Unable to Start a Case of an iProcess Procedure That Is in the Model Status
The iProcess Start Case activity contained in the iProcess palette is unable to start
a case of an iProcess procedure that is in the model status.
See "iProcess Start Case" in TIBCO iProcess BusinessWorks Connector User’s Guide
for more details.
Unable to Configure Details of the Cluster for RAC Database Type in Console
Mode
When installing TIBCO iProcess Technology Plug-ins in console mode, if you
select the Oracle Real Application Cluster (RAC) database type, no options are
available to configure details of the cluster.
A workaround for this issue is to install TIBCO iProcess Technology Plug-ins in
GUI mode if the type of the database that iProcess Engine uses is RAC.
Oracle 12c Is Incompatible with TIBCO JDBC Driver
When configuring database connection for a BusinessWorks process in an
iProcess Connection shared resource, if you select JDBC as the connection type
and use TIBCO JDBC driver 1.x as the database driver to connect to the Oracle 12c
database, the connection fails.
TIBCO iProcess Technology Plug-ins Release Notes
Known Issues 29
|
A workaround for this issue is to set the value of the
SQLNET.ALLOWED_LOGON_VERSION parameter in the
oracle/network/admin/sqlnet.ora file to 8 if using TIBCO JDBC driver 1.x or
use the jdbc driver provided by Oracle instead.
Ineffective Conversion of Native Characters
The default setting for the String type values in the
SWDIR/eaijava/pojo.properties file works ineffectively on the conversion
between TIBCO iProcess Engine fields and Java when the values are native
characters, such as Euro symbols, and so on.
A workaround for this issue is to use the native2ascii tool to convert all the native
characters to Unicode-encoded characters before the native characters are used by
the Java runtime environment. Currently, the Java runtime environment only
supports the ISO8859_1 and UTF-8 encoding sets.
The following command is used in the native2ascii converter to convert the native
characters:
native2ascii -encoding
encoding_ name inputfile outputfile
Where:
•
encoding_ name is the name of a specific supported encoding set, including
ISO8859_1 and UTF-8.
•
inputfile is the name of a specific input file in which the native characters are
saved.
•
outputfile is the name of a specific output file in which the conversion result is
put.
TIBCO JDBC Driver Version 2.x Is Not Supported for Setting Up Oracle
Database Connection
When you use the TIBCO JDBC driver
version 2.x that is supplied
with the TIBCO ActiveMatrix BusinessWorks installation to set up a connection
for Oracle 11g and Oracle 12c, starting a case in TIBCO ActiveMatrix
BusinessWorks will be failed.
(tibcosoftwareinc.jdbc.oracle.OracleDriver)
The TIBCO JDBC driver will be used for the database connection in the following
situations:
•
When you select JDBC from the Connection Type list, select the Auto Config
check box in the Database Connection tab of the iProcess Connection shared
resource, and did not specify a JDBC driver in the BWPlugin.properties file.
TIBCO iProcess Technology Plug-ins Release Notes
30
|
Release Notes
•
When you select JDBC from the Connection Type list, uncheck the Auto
Config check box, and type the name of the JDBC driver supplied by TIBCO
in the JDBC Driver field manually in the Database Connection tab of the
iProcess Connection shared resource.
There are two workarounds for this issue:
•
Use the TIBCO JDBC driver version 1.x as a substitute.
To use the TIBCO JDBC driver version 1.x, you need to uninstall the JDBC
driver version 2.x first and then reinstall the JDBC driver version 1.x. For more
information about the installation and uninstall of TIBCO JDBC driver, see
TIBCO Database Drivers Supplement Installation.
•
Use the JDBC driver supplied by Oracle
(oracle.JDBC.driver.OracleDriver (oci)) rather than the JDBC driver that
is supplied with TIBCO ActiveMatrix BusinessWorks installation.
To use the Oracle JDBC Driver, you must obtain it from Oracle and save it in
the TIBCO_HOME\bw\plugins\lib directory. You can take either of the
following ways to use the Oracle JDBC driver:
— Select JDBC from the Connection Type list, check the Auto Config check
box, and set up the Oracle JDBC driver
((oracle.jdbc.driver.OracleDriver (oci)) as the JDBC driver in the
BWPlugin.properties file.
— Select JDBC from the Connection Type list, uncheck the Auto Config
check box, and type the name of the JDBC driver supplied by Oracle in the
JDBC Driver field manually in the Database Connection tab of the
iProcess Connection shared resource.
See the section of ’iProcess Connection’ of "Chapter 6, TIBCO BusinessWorks
iProcess Plug-in Palette" in TIBCO iProcess BusinessWorks Connector User’s
Guide for more information about how to use the JDBC driver supplied by
Oracle.
Logs for Unregistering EAIJAVA Written to Unreasonable File During
Installation
When you install the product or some components of the product, the installer
unregisters EAIJAVA automatically but the logs for unregistering EAIJAVA are
not written to eaireg.log nor eairegerror.log.
If EAIJAVA is not detected on the machine you want to install the product, the
logs indicating unsuccessful unregistering of EAIJAVA are written to
eaiunregerror.log.
TIBCO iProcess Technology Plug-ins Release Notes
Known Issues 31
|
If EAIJAVA is detected on the machine you want to install the product, the logs
indicating successful unregistering of EAIJAVA are written to eaiunreg.log.
One Extra Value Returned to BusinessWorks
When you run cases from TIBCO ActiveMatrix BusinessWorks using TIBCO
BusinessWorks iProcess Plug-in, and enter several values in an array field at
design time, one extra value is sent to TIBCO ActiveMatrix BusinessWorks at
runtime. For example, if you enter a, b in an array field, a,b,b is returned to
BusinessWorks.
Installer Not Informing User When JVM Cannot be Found
The installer terminates at the Verifying JVM check without informing the user of
the cause of the termination.
Misleading Error for Long JNDI Passwords
JNDI 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.
Possible Loop in the Installer
In 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 in
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 in the Features dialog you cannot move from this screen at all,
and must stop the installation manually.
TIBCO iProcess Technology Plug-ins Release Notes
32
|
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 32.
•
The second 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 34.
•
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 Server Plug-in are relevant to all users. See page 35.
Restrictions Affecting the iProcess BusinessWorks Server Plug-in
This table lists restrictions that affect the iProcess BusinessWorks Server Plug-in
only.
Defect #
Summary/Workaround
MR 41537
MR 41550
Summary A known compatibility issue exists between TIBCO iProcess
Technology Plug-ins and TIBCO ActiveMatrix 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 ActiveMatrix BusinessWorks version 5.7.1
3. TIBCO iProcess Technology Plug-ins version 11.2.0
4. TIBCO ActiveMatrix BusinessWorks Hotfix 2 and any subsequent hotfixes
TIBCO iProcess Technology Plug-ins Release Notes
Restrictions 33
|
Defect #
Summary/Workaround
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.NoClassDefFound
No 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.
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.
TIBCO iProcess Technology Plug-ins Release Notes
34
|
Release Notes
Restrictions Affecting the BusinessWorks iProcess Plug-in
This table lists restrictions that affect the BusinessWorks iProcess Plug-in only.
Defect #
Summary/Workaround
IPTP-688
Summary Errors occur when configuring iProcess Connection in
BusinessWorks 5.9.3 while using TIBCO Runtime Agent 5.7.3 on AIX
platforms.
Workaround Replace J9 JVM 1.6.0 SR10 with J9 JVM 1.6.0 SR6 or J9 JVM 1.6.0
SR8 as the Java Runtime environment.
Restrictions Affecting the EAI POJO Plug-in Only
This table lists restrictions that affect all the iProcess Technology plug-ins.
Defect #
Summary/Workaround
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.
TIBCO iProcess Technology Plug-ins Release Notes
Restrictions 35
|
Restrictions Affecting All iProcess Technology Plug-ins
This table lists restrictions that affect all the iProcess Technology plug-ins.
Defect #
Summary/Workaround
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-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/f
rameworkconfig.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/f
rameworkconfig.xml (No such file or directory)]) at
com.installshield.product.actions.XmlTransformer.productException(Unknown
Source)
Workaround None.
TIBCO iProcess Technology Plug-ins Release Notes
36
|
Release Notes
Defect #
Summary/Workaround
MR 36422
Summary When uninstalling the iProcess Technology Plug-ins in console mode,
the following error might 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 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.
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.
TIBCO iProcess Technology Plug-ins Release Notes
Restrictions 37
|
Defect #
Summary/Workaround
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:
Take a copy of the file before you perform the upgrade.
Perform the upgrade.
Manually edit the new log4j.properties file to re-implement your
customizations.
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.
TIBCO iProcess Technology Plug-ins Release Notes
38
|
Release Notes
Defect #
Summary/Workaround
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.
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 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.
TIBCO iProcess Technology Plug-ins Release Notes
Restrictions 39
|
Defect #
Summary/Workaround
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.
TIBCO iProcess Technology Plug-ins Release Notes
40
|
Release Notes
TIBCO iProcess Technology Plug-ins Release Notes
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement