TIBCO iProcess Engine Release Notes

TIBCO iProcess Engine Release Notes
TIBCO iProcess® Engine
(Oracle) for Windows
(Consolidated with TIBCO iProcess® Objects
Server and TIBCO iProcess® Director)
Release Notes
Software Release 11.4.0
July 2013
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 Business Studio, TIBCO
EnterpriseMessage Service, TIBCO Hawk, TIBCO iProcess, TIBCO iProcess Suite, and TIBCO Rendezvous are
either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition
(J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation
in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 2001-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
TIBCO iProcess Engine Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x
x
x
x
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 11.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
15
15
15
15
15
15
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
17
22
29
43
48
54
TIBCO iProcess Engine Release Notes
iv
| Contents
Release 11.1.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Earlier Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIBCO iProcess® Conductor EAI Order Step Should be Preceded by a Transaction Control Step . . . . . . .
Using SWDIR\util\plist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Must Normalize Case Data to View Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Large Number of User Logins May Cause Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading from Earlier Version May Cause Error Messages in Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Name Cannot Contain Certain Characters if Using Access Database . . . . . . . . . . . . . . . . . . . . . . . .
TIBCO iProcess Engine Release Notes
91
91
91
91
91
92
92
|v
Preface
TIBCO iProcess Engine provides the runtime execution environment for business
processes developed using TIBCO Business Studio™, TIBCO iProcess®
Workspace (Windows) and other TIBCO iProcess® Suite components.
Topics
•
Related Documentation, page vi
•
Typographical Conventions, page viii
•
Connecting with TIBCO Resources, page x
TIBCO iProcess Engine Release Notes
vi
| Related Documentation
Related Documentation
This section lists documentation resources you may find useful.
TIBCO iProcess Engine Documentation
The following documents form the TIBCO iProcess® Engine documentation set:
•
TIBCO iProcess Engine Installation Read this manual for instructions on site
preparation and installation.
•
TIBCO iProcess Engine Release Notes Read the release notes for a list of new
and changed features. This document also contains lists of known issues and
closed issues for this release. The appropriate information for TIBCO iProcess
Objects Director and TIBCO iProcess Objects Server release notes are
integrated into appropriate TIBCO iProcess Engine release notes.
•
TIBCO iProcess Suite Documentation This documentation set contains all the
manuals for TIBCO iProcess Engine and other TIBCO products in TIBCO
iProcess® Suite. The manuals for TIBCO iProcess Engine are as follows:
— TIBCO iProcess Engine Architecture Guide
— TIBCO iProcess Engine Administrator’s Guides:
TIBCO iProcess Engine Administrator’s Guide
TIBCO iProcess Objects Director Administrator’s Guide
TIBCO iProcess Objects Server Administrator’s Guide
— TIBCO iProcess Engine Database Administrator's Guides:
TIBCO iProcess Engine (DB2) Administrator's Guide
TIBCO iProcess Engine (Oracle) Administrator's Guide
TIBCO iProcess Engine (SQL) Administrator's Guide
— TIBCO iProcess swutil and swbatch Reference Guide
— TIBCO iProcess Engine System Messages Guide
— TIBCO iProcess User Validation API User's Guide
— LDAPCONF Utility User’s Guide
TIBCO iProcess Engine Release Notes
Preface vii
|
Other TIBCO Product Documentation
You may find it useful to read the documentation for the following TIBCO
products:
•
TIBCO ActiveMatrix BusinessWorks™
•
TIBCO Business Studio™
•
TIBCO Enterprise Message Service™
•
TIBCO Hawk®
•
TIBCO Rendezvous®
TIBCO iProcess Engine Release Notes
viii
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention
Use
SWDIR
TIBCO iProcess Engine installs into a directory. This directory is referenced in
documentation as SWDIR.
For example, if SWDIR is set to C:\swserver\staffw_nod1 on a Windows server
(on the C: drive), then the full path to the swutil command is
C:\swserver\staffw_nod1\bin\swutil.
code font
Code font identifies commands, code examples, filenames, pathnames, and
output displayed in a command window. For example:
Use MyCommand to start the foo process.
bold code
font
Bold code font is used in the following ways:
•
In procedures, to indicate what a user types. For example: Type admin.
•
In large code samples, to indicate the parts of the sample that are of
particular interest.
•
In command syntax, to indicate the default parameter for a command. For
example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]
italic font
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.
TIBCO iProcess Engine Release Notes
Preface ix
|
Table 1 General Typographical Conventions (Cont’d)
Convention
Use
The note icon indicates information that is of special interest or importance, for
example, an additional action required only in certain circumstances.
The tip icon indicates an idea that could be useful, for example, a way to apply
the information provided in the current section to achieve a specific result.
The warning icon indicates the potential for a damaging situation, for example,
data loss or corruption if certain steps are taken or not taken.
Table 2 Syntax Typographical Conventions
Convention
Use
[ ]
An optional item in a command or code syntax.
For example:
MyCommand [optional_parameter] required_parameter
|
A logical OR that separates multiple items of which only one may be chosen.
For example, you can select only one of the following parameters:
MyCommand para1 | param2 | param3
{ }
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 Engine Release Notes
x
| Connecting with TIBCO Resources
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:
http://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 Engine Release Notes
|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
•
New Features, page 2
•
Deprecated Features, page 15
•
Compatibility, page 16
•
Change History, page 17
•
Restrictions, page 74
•
Known Issues, page 84
•
Other Information, page 91
TIBCO iProcess Engine Release Notes
2
|
Release Notes
New Features
This section lists features added since the last major release (11.0) of this product.
Release 11.4.0
The following are new features in this release.
Define how many of the Latest Versions of Procedure Definition to be Cached (IPE-2975)
To define how many of the latest versions of procedure definitions are to be
cached by the iProcess Objects Server processes, you can use the
RESTART_SPO_CACHE_PROC process attribute when restarting or quick starting
iProcess Engine, and use the SPO_CACHE_PROC process attribute when the iProcess
Objects Server process starts normally.
See TIBCO iProcess Engine Administrator's Guide for more information.
Enable Quick Start Mode (IPE-2976)
You can quick start iProcess Engine server processes with quick start mode by
running the following command:
swstart -q
See TIBCO iProcess Engine Administrator's Guide for more information.
Define the Minimum Size of a Work Queue to Cache on a Restart (IPE-2990)
You can control the minimum size of a queue to be cached by a WIS process by
using the RESTART_WIS_CACHE_THRESHOLD process attribute when quick starting
or restarting iProcess Engine.
The RESTART_WIS_CACHE_THRESHOLD attribute will be used only for restart and
quick start.
See TIBCO iProcess Engine Administrator's Guide and TIBCO iProcess Engine
Installation for more information.
Procedure Level Events (IPE-3016)
Procedure level events are introduced with the following functionalities:
— You can define an event, which is triggered just before or after performing
the purge, close, resurrect, suspend, or resume action, from the Events tab
of the Properties dialog. The Event tab contains the following procedure
TIBCO iProcess Engine Release Notes
New Features 3
|
level events: OnBeforePurge, OnBeforeClose, OnAfterClose,
OnBeforeResurrect, OnAfterResurrect, OnBeforeSuspend,
OnAfterSuspend, OnBeforeResume, and OnAfterResume. See TIBCO
iProcess Modeler Procedure Management for more information on the Event
tab.
— You can use the CancelProcEvent expression to cancel the purge, close,
resurrect, suspend, or resume action that is set in the OnBeforeEvent
procedure level events. See TIBCO iProcess Expressions and Functions
Reference Guide for more information.
— You can use swutil and swbatch utilities to purge or close cases without
triggering events. See TIBCO iProcess swutil and swbatch Reference Guide for
more information.
— The SW_PURGE_WITHOUT_EVENT and SW_CLOSE_WITHOUT_EVENT SSOLite
command procedures are added to purge or close cases without triggering
events. See the appropriate TIBCO iProcess Engine (Database) Administrator’s
Guide for more information.
— The definition of procedure events is stored in the proc_event table, and
the information of cases that are interrupted by triggered events when
processing the purge, close, resurrect, suspend, or resume operation is
stored in the case_event table. The case information is recorded in the
case_event table only when the BG process is handling the delayed release
EAI steps, which are defined in the triggered event. See the appropriate
TIBCO iProcess Engine (Database) Administrator’s Guide for more
information.
Set Auto-Purge and Deadlines for Cases (IPE-3019)
You can configure delay auto-purge and deadline for cases in TIBCO iProcess
Engine. The information of the auto-purge delay is recorded in the proc_index
table.
You can create a case deadline for a case to trigger an event after a specified time
period, as well as update and delete a case deadline. The definitions of the case
deadlines are recorded in the proc_deadline table. When a case is started, the
information of the case deadline is saved in the case_deadline_event table.
See TIBCO iProcess Modeler Procedure Management for more information on the
configuration of delay auto-purge and case deadlines, proc_index,
proc_deadline, and case_deadline_event tables.
See TIBCO iProcess Engine (Database) Administrator’s Guide for more information
on the proc_index table.
See TIBCO iProcess Expressions and Functions Reference Guide for more information
on the CreateCaseDeadline, UpdateCaseDeadline, and DeleteCaseDeadline
TIBCO iProcess Engine Release Notes
4
|
Release Notes
functions.
Switch On or Off the Retry Function for Configured Oracle RAC (IPE-3032)
You can control whether to enable the retry function by using the
attribute. The retry function retrieves work items from the
staffo database table for the configured Oracle RAC.
RETRY_OFF_FOR_RAC
See TIBCO iProcess Engine Administrator's Guide for more information.
Test the Event Mechanism Manually (IPE-3052)
You can test the event mechanism manually by using the following command:
swadm evloopback
When Process Sentinel starts, a START event is issued, or a SHUTDOWN event is
issued, the event mechanism is tested automatically.
See TIBCO iProcess Engine Administrator's Guide for more information.
Additional IP Addresses Support (IPE-3055)
IPv6 addresses are supported on Windows and Linux systems.
See TIBCO iProcess Engine Installation Guide for more information on the
configuration.
When communicating with TIBCO iProcess Technology Plug-ins with an IPv6
address, you need to note that TIBCO iProcess Technology Plug-ins only supports
inbound communication at runtime with IPv6 addresses.
•
If you want to use an IPv6 address for 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.
•
If you use TIBCO iProcess Server Objects as the protocol for inbound
communication, make sure the Auto Config Date Format checkbox is
unchecked in the Advanced tab of the iProcess Connection activity.
Release 11.3.1
There are no new features in this release.
TIBCO iProcess Engine Release Notes
New Features 5
|
Release 11.3.0
The following are new features in this release.
Include MailID in Output Messages From IAPJMS (IPE-1602)
MailID has been added to the output messages from IAPJMS so that users can use
this mailID to build a tag for each work item.
See TIBCO iProcess Engine Administrator’s Guide for more information.
Publish Step Description or Extended Step Description (IPE-1603)
The extended step description, along with the step description, can be published
with a minimum length of 48 bytes for the messages which have a type_id equal
to 1, in IAPJMS. You can use the IAPSCHEMA2_1 parameter to enable this feature.
See TIBCO iProcess Engine Administrator’s Guide for more information.
SWBATCH Returns Proper Return Codes When SWBATCH Fails (IPE-2322)
When all the START commands succeed, the return code from SWBATCH is
SW_SUCCESS. If a SWBATCH command fails, SWBATCH will continue to
execute the subsequent commands, and the return code will be the same as that of
the first failure command.
Audit Changes to Case Data (IPE-2258)
When the case data is changed by using iProcess Insight, iProcess Workspace
(Browser), or the setCaseData SSO interface, rather than by the normal step
processing, such changes are logged in the audit trail.
See the TIBCO iProcess Insight documentation for how to change case data in
TIBCO iProcess Insight.
See the TIBCO iProcess Workspace (Browser) documentation for how to change
case data in TIBCO iProcess Workspace (Browser).
See TIBCO iProcess Engine Administrator’s Guide for how to change case data in
TIBCO iProcess Engine.
Reopen Cases via SSOLite Stored Procedures (IPE-1579)
Users can resurrect cases by using the SW_CASEREOPEN SSOLite stored procedure.
See the appropriate TIBCO iProcess Engine Database Administrator’s Guide for more
information.
TIBCO iProcess Engine Release Notes
6
|
Release Notes
Update Terminated Date/Time Display (IPE-1921)
Terminated Date/Time is now stored including Seconds. You can view this value
by using SSO interface or the clients such as iProcess Workspace (Browser).
A New Case Start Interface and Instruction (IPE-1593)
A new case start SAL interface and instruction are introduced when a case is
started by using iProcess Server Objects or iProcess Objects server. When the step
is addressed to the current user, and the step is to be released, the iProcess Objects
server internally uses the new SAL interface. The case start is implemented in one
single SAL interface and with one single CASESTARTRELEASE message passing
to the StartCase interface.
plist -p Identifies Procedure Templates (IPE-2013)
The plist -p command can identify whether the procedure is a template. In the
Flag column returned by the command, flag T indicates that the procedure is a
sub-procedure parameter template, and flag I indicates that the procedure is a
sub-procedure.
See TIBCO iProcess Engine Administrator’s Guide for more information.
Start Case Only If All Necessary Information Is Available (IPE-2191)
When you start a case through iProcess Server Objects JAVA code with both
and aValidateFields set to be true, and do not specify all the
required fields in the first step, the case can not be started and an error is reported.
aReleaseItem
In previous releases, if you did not specify all the required fields in the form, the
step could not be released, but the case was started with an error reported.
A New Case Start Interface and Instruction (IPE-2239)
A new case start SAL interface and instruction are introduced when a case is
started by using iProcess Server Objects or iProcess Objects server. When the step
is addressed to the current user, and the step is to be released, the iProcess Objects
server internally uses the new SAL interface. The case start is implemented in one
single SAL interface and with one single CASESTARTRELEASE message passing
to the StartCase interface.
IMPORT and EXPORT XFR and XPDL Files to a Directory Outside of SWDIR/util (IPE-2257)
The XFR and XPDL files can be imported from and exported to a directory
outside of the SWDIR/util directory.
See TIBCO iProcess swutil and swbatch Reference Guide for more information.
TIBCO iProcess Engine Release Notes
New Features 7
|
Audit Changes to Case Data (IPE-2259)
When you change the case data through iProcess Insight, iProcess Workspace
(Browser), or the setCaseData iProcess Server Objects interface, rather than by
using the normal step processing, such changes are logged in the audit trail.
See TIBCO iProcess Insight documentation for how to change case data in TIBCO
iProcess Insight.
See TIBCO iProcess Workspace (Browser) documentation for how to change case
data in TIBCO iProcess Workspace (Browser).
To audit such changes to case data, you must set the AUDIT_CASEDATA_CHANGED
process attribute. See TIBCO iProcess Engine Administrator’s Guide for how to set
the process attribute.
Enable plist -wvV and plist -wVv (IPE-2321)
The plist -wvV and plist
items returned by the plist
commands are enabled, which return all the
and plist -wV commands.
-wVv
-wv
See TIBCO iProcess Engine Administrator’s Guide for more information.
Installation Is Separated by Roles (IPE-2256)
Installation is separated by roles:
•
Binary Installation (by OS Admin) only copies binaries.
•
DB Installation (by DB Admin) only runs DDL script.
The separation of roles during installation can enhance security in customers’
environments because an OS administrator need not know some sensitive
information (for example, DB user’s credentials and server names) any more. The
separation of roles during installation also facilitates the iProcess Engine upgrade
because you need not install iProcess Engine schemas if you still use the existing
database during the upgrade.
See TIBCO iProcess Engine Installation for more information.
TIBCO iProcess Objects Server Startup Performance Improvements (IPE-2554, IPE-2562)
TIBCO iProcess Objects Server startup performance has been improved
significantly in the following two aspects:
•
TIBCO iProcess Objects Server is started simultaneously with WIS. This
means that it starts sooner in the startup procedure.
•
Users and groups can be loaded at higher speeds.
TIBCO iProcess Engine Release Notes
8
|
Release Notes
Create Log Files in a Rotational Manner (IPE-2613)
The sw_warn, sw_error, swentobjsv, and swentobjUA log files are now created
with the timestamp in the file name to record messages every day if a serious
error occurs. For example:
sw_warn20110831,sw_error20110831,swentobjsv_20110831, and
swentobjUA_20110831.
Log messages were recorded in one single log file titled as sw_warn, sw_error,
swentobjsv, and swentobjsvUA. When errors occur frequently, log files can
quickly become very large. It was not easy to archive old log files which could
lead to the loss of old log files.
See TIBCO iProcess Engine Administrator’s Guide and TIBCO iProcess Objects Server
Administrator’s Guide for more information.
Support Oracle 11g Client Libraries
Support for Oracle 11g client libraries (11.2.0.2) has been added.
HP Itanium platforms still require Oracle 10g client libraries (10.2.0.4). All other
platforms require Oracle 11g client libraries (11.2.0.2).
See TIBCO iProcess Engine Installation for more information.
Pass Complete Arrays Into and out of Sub-procedures (IPE-2535)
Complete arrays can be passed into and out of sub-procedures.
See TIBCO iProcess Modeler Advanced Design for more information.
Prioritizing the Work Performed by Background Processes (IPE-2480)
You can now set priorities for internal message queues when passing messages
between iProcess processes such as from the background and the WISes, or from
SSOLite to the background.
See the appropriate TIBCO iProcess Engine Database Administrator’s Guide for more
information.
Bulk Operations for SSOLite (IPE-2423)
Support for bulk operations has been added by adding the SW_SET_MBOX and
SSOLite procedures.
SW_UNSET_MBOX
See the appropriate TIBCO iProcess Engine Database Administrator’s Guide for more
information.
TIBCO iProcess Engine Release Notes
New Features 9
|
Enable RPC Blocking From iProcess Workspace (Windows) (IPE-2348)
You can now prevent TIBCO iProcess Workspace (Windows) from accessing
iProcess Engine by setting the RPC_BLOCK attribute to 1.
See TIBCO iProcess Engine Administrator’s Guide for more information.
Exact Timestamps for Release Instructions in Audit Trail (IPE-2658)
In previous releases, the timestamps used in the audit_trail table recorded
when the actual RELEASE actions of the instruction were processed.
The timestamps in the audit_trail table now record when the actual RELEASE
actions of the instruction are carried out.
See TIBCO iProcess Engine Administrator’s Guide for more information.
Redirect the Work Items of a Deleted User (IPE-2560)
When a user is deleted, the work items which are currently in the deleted user's
queue can be redirected to the supervisor’s queue, to a user-specified destination,
or to the admin user’s queue. The work items, which arrive at a deleted user after
the user has been deleted, will be delivered to the undelivered queue.
See TIBCO iProcess Engine Administrator’s Guide for more information.
Make Purging Many Cases More Efficient for Oracle (IPE-2596)
Purging many cases can be made more efficient by configuring the
USE_NEXT_MESSAGE_TO_DEQUEUE process attribute.
See TIBCO iProcess Engine Administrator’s Guide for more information.
Map an Attribute Which Contains an Underscore to One Which Doesn’t Have One in LDAP
(IPE-2604)
LDAP does not allow attributes with an underscore. An attribute with an
underscore in iProcess Engine can be mapped to an attribute without an
underscore in LDAP.
See LDAPCONF Utility User’s Guide for more information about how to map an
iProcess Engine attribute to the corresponding LDAP attribute.
TIBCO iProcess Engine Startup Performance Improvements (IPE-2552, IPE-2558, IPE-2563)
TIBCO iProcess Objects Server startup performance has been improved
significantly in the following two aspects:
TIBCO iProcess Engine Release Notes
10
|
Release Notes
•
TIBCO iProcess Objects Server is started simultaneously with WIS. This
means that it starts sooner in the startup procedure.
•
Users and groups can be loaded at higher speeds.
Log Files Directory Is Configurable (IPE-2732)
You can specify the log files directory by adding it in line 19 of the staffpms file
located in the SWDIR/etc directory.
Ensure that the log files directory you specify is available, and has the same
permissions to access it as the original log files directory.
See TIBCO iProcess Engine Administrator’s Guide for more information.
Log Files Directory Is Configurable (IPE-2733)
You can specify the log files directory by adding it in line 19 of the staffpms file
located in the SWDIR\etc directory.
Ensure that the log files directory you specify is available, and has the same
permissions to access it as the original log files directory.
Optionally Migrate Only Live Cases (IPE-2337)
You can choose to migrate only live cases from previous versions to a new version
in one of the following ways:
•
migrate only live cases for deployment from TIBCO Business Studio to TIBCO
iProcess Engine by configuring the RPC_TCP_LI process attribute.
Case migration is not supported by TIBCO Business Studio currently.
See TIBCO iProcess Engine Administrator’s Guide for more information.
•
migrate only live cases from swutil by running the swutil
command.
PROC RELEASE
See TIBCO iProcess swutil and swbatch Reference Guide for more information.
Release 11.1.3
The following is the new feature in this release.
TIBCO iProcess Engine Release Notes
New Features 11
|
Added the STICKY_SAL Attribute (JIRA IPE-2382)
In this release, TIBCO iProcess Objects Director can allocate a user to the TIBCO
iProcess Objects Server that has opened an SAL session for this user. To enable or
disable this function, a new attribute STICKY_SAL has been added to TIBCO
iProcess Objects Director. When the value of STICKY_SAL is set to 1, the function is
enabled; when the value is set to 0, the function is disabled.
When upgrading TIBCO iProcess Objects Director from an earlier version to
version 11.1.3, you will not be able to see the new attribute unless you activate it
by running the following command under the $SWDIR/util/ directory:
swadm set_attribute 1 DIRECTOR 0 STICKY_SAL 1
Release 11.1.2
There are no new features in this release.
Release 11.1.1
The following are new features in this release.
Additional Platform Support - Microsoft Windows
TIBCO iProcess Engine now supports Microsoft Windows 7 Professional.
Added Database Support
This release adds support for Oracle 11g release 11.2.0.1.0 (server) with 10.2.0.4
(client).
Release 11.1.0
The following are new features in this release.
TIBCO iProcess Engine Now Supports UTF-8 (MR 38428)
TIBCO iProcess Engine now supports UTF-8 encoding. This is a choice that you
can specify when you install or upgrade the iProcess Engine.
The advantage of using UTF-8 is that it allows you support multiple regions
within a single character set. For example, an enterprise operating globally could
support data in Chinese, Japanese, Russian and English character sets in the same
database. Work can be partitioned so that an end user working in this installation
will normal see only work in his or her language.
TIBCO iProcess Engine Release Notes
12
|
Release Notes
For more information see TIBCO iProcess Engine Installation and TIBCO iProcess
Architecture Guide.
Option to Configure Use of SSL Support (MR 39108)
When setting up your LDAP connection you can now configure whether or not to
use SSL to secure the link between the iProcess Engine and the LDAP database.
For more information on setting up your LDAP connection, see TIBCO iProcess
LDAPCONF Utility User’s Guide.
swutil IMPORTLIB Extended for XPDL Files (MR 38270)
The swutil IMPORTLIB command line option has been expanded to cater for
XPDL files. The command remains the same as iProcess Engine detects whether
the library has an xfr or xpdl extension. This feature facilitates the scripted
deployment of process created with TIBCO Business Studio.
For more information on swutil, please see the TIBCO iProcess swutil and swbatch
Reference Guide.
Additional Platform Support - Windows
TIBCO iProcess Engine now supports Windows Server 2008 and Windows Server
2008 x64. For more information, see TIBCO iProcess Engine Installation.
Additional Database Support - Oracle
TIBCO iProcess Engine now supports Oracle 10.2.0.4 (client) and 10.2.0.4 or later
(server). It also now supports Oracle 11.1.0.6 or later (server) with a 10.2.0.4 client.
For more information, see TIBCO iProcess Engine Installation.
Extended Information for IAPJMS Messages (MR 40846)
It is now possible to include additional information in messages generated by the
IAPJMS process. A new IAPSCHEMA parameter in the SWDIR\etc\staffcfg file
enables you to control which format to use.
See the TIBCO iProcess Engine Administrator's Guide for setting the IAPSCHEMA
parameter, and see the TIBCO iProcess Architecture Guide for details of the new
extended format.
Include Open and Kept Data in IAPJMS (MR 38272)
When a work item is opened, changed, then requeued, IAPJMS now publishes the
latest data (from the requeued item, rather than from the central case data).
TIBCO iProcess Engine Release Notes
New Features 13
|
TIBCO Business Studio Deployment Through a Firewall (MR 38271)
A TIBCO Business Studio process can now be deployed through a firewall.
Only Upgrade COM+ and RPC When Necessary (MR 38504)
The installer has been enhanced to check the versions of these components and
only update them if necessary.
Allow EMPTYMBOXSLEEP to be Specified in Intervals Less Than One Second (MR 36301)
The EMPTYMBOXSLEEP process attribute has been enhanced so that values up
to (and including) 60 are treated as a measure of the time to sleep in seconds, and
values of greater than 60 are treated as the sleep time in milliseconds.
Configuration of Uncommitted Reads (MR 38267 (Parent MR 36449))
A new process attribute XPC_READ_UNCOMMITTED is provided to allow
configuration of uncommitted reads during an XPC SELECT.
If this is set to 1, XPC is enabled to use uncommitted reads. If set to 0 (which is the
default) uncommitted reads cannot be used.
See the TIBCO iProcess Engine Administrator's Guide for details about setting
process attributes.
New Configuration Flag in staffcfg File to Predict Step Duration (MR 38407 (Parent MR 34440))
A new configuration flag has been added to the staffcfg file to define how
predicted step duration is to be calculated. See TIBCO iProcess Engine
Administrator's Guide for more information.
Ability to Configure Signals (MR 38648 (Parent MR 36109))
You now have the ability to configure signals that threads are blocked from
receiving.
If you wish to enable threads to be blocked from receiving signals then you will
need to modify the $SWDIR/etc/staffpms file, adding the information to line 17
of the file.
For example, to add blocking for the SIGALRM (14) signal the last few lines of the
file will look like this:
QPARAM1\QPARAM2\QPARAM3\QPARAM4\CP_V...
<blank line - unless UVAPI is configured>
<blank line>
TIBCO iProcess Engine Release Notes
14
|
Release Notes
14
If you wish to add more signals to the list they will need to be separated by the '\'
character:
QPARAM1\QPARAM2\QPARAM3\QPARAM4\CP_V...
<blank line - unless UVAPI is configured>
<blank line>
14\13\12\\
For more information on the staffpms file, see TIBCO iProcess Administrator’s
Guide.
Earlier Versions
For details of the new features implemented in earlier versions of the product,
please see the Readme and Release Notes for that particular product release.
TIBCO iProcess Engine Release Notes
Deprecated Features 15
|
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.4.0
No features are deprecated in this release.
Release 11.3.1
No features are deprecated in this release.
Release 11.3.0
No features are deprecated in this release.
Release 11.1.3
No features are deprecated in this release.
Release 11.1.2
The following feature is deprecated in this release:
•
Remove the TIBCO HAWK Installation from the TIBCO iProcess Engine
Installer The TIBCO iProcess Engine installer does not contain the TIBCO
Hawk installation any more.
Release 11.1.1
No features are deprecated in this release.
Release 11.1.0
No features are deprecated in this release.
TIBCO iProcess Engine Release Notes
16
|
Release Notes
Compatibility
In addition to other Version 11 TIBCO iProcess® Suite components, the following
TIBCO products have been successfully tested for compatibility with Version
11.4.0 of TIBCO iProcess Engine.
Product
TIBCO
iProcess®
Version(s)
Decisions Server Plug-in
Version 10.3.0
TIBCO iProcess® Web Services Server Plug-in
Version 11.3.0
TIBCO iProcess® Technology Plug-ins
Version 11.2.0,
11.3.1, 11.4.0
TIBCO iProcess® Server Objects
Version 11.4.0
If you have any queries regarding product compatibility with this version of the
iProcess Engine, contact TIBCO Support for further assistance.
TIBCO iProcess Engine Release Notes
Change History 17
|
Change History
The following JIRA issues and Modification Requests (MRs) have been
implemented since the initial release of TIBCO iProcess Engine.
Release 11.4.0
Defect #
Description
IPE-163
An error occurred when checking permissions of the running users due to the
user name being case-sensitive on Windows systems.
Corrected.
IPE-2975
Add the RESTART_SPO_CACHE_PROC process attribute to define how many of
the latest versions of the procedure definition will be cached by the iProcess
Objects Server processes when restarting or quick starting iProcess Engine.
Add the SPO_CACHE_PROC process attribute to define this behavior when
starting iProcess Engine normally.
Implemented. See Define how many of the Latest Versions of Procedure
Definition to be Cached (IPE-2975) on page 2.
IPE-2976
Add a new option –q to the swstart command for quick starting iProcess
Engine.
Implemented. See Enable Quick Start Mode (IPE-2976) on page 2.
IPE-2990
The RESTART_WIS_CACHE_THRESHOLD process attribute, defining the threshold
number of work items in a work queue, is added to determine whether to
cache all the work items in the work queue when a WIS process restarts or
quick starts.
Implemented. See Define the Minimum Size of a Work Queue to Cache on a
Restart (IPE-2990) on page 2.
IPE-3016
The procedure level event is added to TIBCO iProcess Engine to record
information about cases that are interrupted by triggered events when
processing the purge, close, resurrect, suspend, or resume operation.
Implemented. See Procedure Level Events (IPE-3016) on page 2.
TIBCO iProcess Engine Release Notes
18
|
Release Notes
Defect #
Description
IPE-3017
Changed the default values of the CNUM_SEQ_CACHE and REQID_SEQ_CACHE
process attributes to 5 for the iProcess Objects, and SSOLITE on Oracle.
Changed the default value of the WIS_UPDATE_PERIOD attribute to 20.
Corrected.
IPE-3019
Add support to delay the case auto-purge operation and to set case deadlines.
Implemented. See Set Auto-Purge and Deadlines for Cases (IPE-3019) on
page 3.
IPE-3020
(Parent JIRA
IPE-2978)
IPE-3028
The message priority was not controlled by setting the value of the
field through TIBCO ActiveMatrix BusinessWorks Plug-in.
SW_CP_VALUE
Corrected.
Upgrade Java from version 1.6 to 1.7 on all platforms of TIBCO iProcess
Engine.
Implemented.
IPE-3032
Adds the RETRY_OFF_FOR_RAC attribute to determine whether to enable the
retry function that reviews work items from the staffo database table for the
configured Oracle RAC.
Implemented. See Switch On or Off the Retry Function for Configured Oracle
RAC (IPE-3032) on page 4.
IPE-3036
An error message was logged in the seo_error log when starting TIBCO
iProcess Objects Server after upgrading iProcess Engine to version 11.3.1.
Corrected.
IPE-3038
(Parent JIRA
IPE-2967)
Mapping from the sub-procedure fields to expressions continued after the
"sal_validsh (): session_lock (21248) failed" error occurred, resulting
in incorrect mappings.
Corrected.
IPE-3039
(Parent JIRA
IPE-2981)
Users imported from the LDAP Server could log in through TIBCO iProcess
Workspace (Windows) or TIBCO iProcess Workspace (Browser) with an
incorrect password.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 19
|
Defect #
Description
IPE-3040
The trigger event operation did not work when the case number was greater
than 2147483647.
(Parent JIRA
IPE-3004)
IPE-3041
(Parent JIRA
IPE-3005)
IPE-3042
(Parent JIRA
IPE-3025)
Corrected.
When releasing a script, the CALL function did not work if the scriptname
parameter in the function was not enclosed in double quotation marks.
Corrected.
When using the JumpTo function to jump from main procedures to dynamic
sub-procedures, the "unexpected exception, Message Item not found."
error message was reported.
Corrected.
IPE-3043
(Parent JIRA
IPE-3030)
If the user name of a case had been changed, for example, changing S02460 to
s02460, the original user was inserted into the leavers and redir_defn tables
as a recently deleted user.
Corrected.
IPE-3045
(Parent JIRA
IPE-2974)
When attempting to release a work item, which contained fields with
validations, error messages were generated in the TIBCO iProcess Objects
Server log file.
Corrected.
IPE-3046
(Parent JIRA
IPE-2994)
When creating an XList of work items from a queue by using TIBCO iProcess
Objects (COM) and looping through the XList to lock each work item, after the
first work item was locked and then released, other work items failed to be
locked.
Corrected.
IPE-3050
TIBCO iProcess Engine ran out of case numbers.
(Parent JIRA
IPE-3013)
Corrected.
IPE-3052
Add the swadm EVLOOPBACK command to test event mechanism manually, and
report error messages if events do not work.
Implemented. See Test the Event Mechanism Manually (IPE-3052) on page 4.
IPE-3055
IPv6 addresses are supported on Windows and Linux systems.
Implemented. See Additional IP Addresses Support (IPE-3055) on page 4.
TIBCO iProcess Engine Release Notes
20
|
Release Notes
Defect #
Description
IPE-3072
After cases were migrated to a new procedure version by using the swutil
IMPORT +c command, duplicated work items were displayed in a case when
triggering an event.
(Parent JIRA
IPE-3048)
Corrected.
IPE-3073
Case start was slow after installing TIBCO iProcess Engine 11.3.0_HF-008.
(Parent JIRA
IPE-3053)
Corrected.
IPE-3074
The indexes for the Mbox tables did not include the enq_time index after
upgrading TIBCO iProcess Engine from version 11.1.2 or earlier versions to
11.3.1.
(Parent JIRA
IPE-3051)
Corrected.
IPE-3078
After migrating existing cases of a procedure to a new version, the existing
cases were still in the old version.
Corrected.
IPE-3090
The F3 filter failed to filter work items via Case Data Queue Parameter (CDQP)
if the field held 255 characters, the maximum capacity.
Corrected.
IPE-3096
The MEMATTS sections in the old version and new version of the procedures
did not match after the XFR file was imported by using the SWUTIL command.
Corrected.
IPE-3116
Only iProcess Engine database user (swuser) account is used to connect to
databases.
Implemented.
IPE-3122
(Parent JIRA
IPE-3063)
IPE-3126
(Parent JIRA
IPE-3101)
When the BG process failed to handle the SUBDONE message because of a
deadlock, the BG process did not roll back the affected transaction.
Corrected.
Chinese characters were not retrieved correctly by using iProcess Server
Objects (Java) if they were split by TIBCO iProcess Objects Server.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 21
|
Defect #
Description
IPE-3145
An error occurred when using the output mapping script to assign the
sub-procedure output values to the Date type and Time type fields of the main
procedure.
(Parent JIRA
IPE-3131)
Corrected.
IPE-3155
The archived log files were not deleted as per the LogFileMaxArchives
setting.
Corrected.
IPE-3156
(Parent JIRA
IPE-3144)
The user defined attributes of Group were missing after synchronizing iProcess
user data with the LDAP directory by using the LDAPCONF utility.
Corrected.
IPE-3177
If an error occurred when closing a case, the BG process did not catch the error
nor roll back the transaction.
IPE-3205
Upgrade Tomcat from version 6.0.35 to 7.0.40.
Implemented.
IPE-3209
(Parent JIRA
IPE-3189)
The background (BG) processes crashed because iProcess Engine unexpectedly
released memory addresses twice. Also, a memory leak occurred in the BG
processes.
Corrected.
IPE-3237
(Parent JIRA
IPE-3231)
IPE-3243
(Parent JIRA
IPE-3240)
When you close or purge a case that contains sub-cases, delete certain
audit_trail entries to reduce the number of returned sub-cases.
Implemented.
After importing a new version of a procedure by using the SWUTIL command,
MEMO fields created for the new version of the procedure referenced the same
MEMO ID.
Corrected.
TIBCO iProcess Engine Release Notes
22
|
Release Notes
Release 11.3.1
Defect #
Description
IPE-2008
An sw_warn error message displayed when processing the audit and
PROCCASE messages. This error only occurred when running a procedure,
which contained sub-procedures and Transaction Control steps.
Corrected.
IPE-2762
(Parent JIRA
IPE-1228)
IPE-2770
The BG process did not roll back the affected transaction if a deadlock occurred
when handling sub-cases.
Corrected.
After upgrading TIBCO iProcess Engine from a previous version to 11.3.0,
messages in queues were lost, and additional queues manual-created were not
upgraded.
Corrected.
IPE-2771
Change the data type of the reqid field in the outsanding_addr table from 232
to 264.
Implemented.
IPE-2775
An error occurred when running the swutil
IMPMONITOR
command.
Corrected.
IPE-2776
When the ReqID value was greater than 2 GB, work items were not retrieved.
(Parent JIRA
IPE-1992)
Corrected.
IPE-2788
Add the new salq_list_sfinditem interface to retrieve the work item index,
and to improve the performance of TIBCO iProcess Server Objects operations,
including the lockitem, unlockitem, releaseitem, keepitem, forwarditem, and
undo operations.
(Parent JIRA
IPE-2784)
Implemented.
IPE-2789
(Parent JIRA
IPE-2785)
A new salq_list_sfinditem interface has been added to retrieve the work
item index. It also improves the performance of TIBCO iProcess Server Objects
operations, including the lockitem, unlockitem, releaseitem, keepitem,
forwarditem, and undo operations.
Implemented.
TIBCO iProcess Engine Release Notes
Change History 23
|
Defect #
Description
IPE-2793
Memory usage of the BGPREDICT process grew uncontrollably, which
exhausted system memory.
Corrected.
IPE-2799
When transforming Workflow Standard XML Process Definition Language
(XPDL) into iProcess procedures, duplicated Numeric Object IDs of the user or
EAI steps were created.
Corrected.
IPE-2801
Memory usage of the BGPREDICT process grew uncontrollably, which
exhausted system memory.
Corrected.
IPE-2804
The WQS process crashed when connecting large numbers of RPC calls.
(Parent JIRA
IPE-2787)
Corrected.
IPE-2805
The memory usage of the BGPREDICT process grew uncontrollably.
(Parent JIRA
IPE-2793)
Corrected.
IPE-2807
After upgrading TIBCO iProcess Engine version 11.0.1.7.1 to 11.3.0 in Silent
Mode, the database schema was not upgraded.
Corrected.
IPE-2809
(Parent JIRA
IPE-2798)
IPE-2811
(Parent JIRA
IPE-2786)
Add more logs in the program to trace global user cache in TIBCO iProcess
Engine and iProcess Objects Server.
Implemented.
The +v major.minor option of the swutil EXPORTLIB command did not affect
the version of the reference template if the exported procedure library did not
contain the template.
Implemented.
IPE-2815
The work queues did not self-refresh after upgrading iProcess Engine.
Corrected.
TIBCO iProcess Engine Release Notes
24
|
Release Notes
Defect #
Description
IPE-2816
If a procedure was deleted from TIBCO iProcess Engine and TIBCO iProcess
Objects Server did not refresh the procedure list, when importing a new
procedure with the same name as the previously deleted one, TIBCO iProcess
Objects Server did not receive the new procedure, even though the procedure
list was then refreshed.
(Parent JIRA
IPE-2753)
Corrected.
IPE-2819
The audit trail records were generated when a case was not migrated.
(Parent JIRA
IPE-2764)
Corrected.
IPE-2821
In the BG processes, a memory leak occurred in procedure definition sessions.
(Parent JIRA
IPE-2796)
Corrected.
IPE-2820
Running a process at LogLevel=4 caused the TIBCO iProcess Objects Server
process to crash.
(Parent JIRA
IPE-2813)
Corrected.
IPE-2823
A memory leak occurred in TIBCO iProcess Objects Server when starting cases.
(Parent JIRA
IPE-2795)
Corrected.
IPE-2825
(Parent JIRA
IPE-2810)
IPE-2826
(Parent JIRA
IPE-2818)
IPE-2831
(Parent JIRA
IPE-2531)
The salq_list_sfinditem interface could not unlock work items using the
utility.
swadmin
Corrected.
An error occurred when releasing steps made by TIBCO iProcess Objects
Server contained embedded fields.
Corrected.
When TIBCO iProcess Objects Server communicated with the WIS and WQS
processes using the RPC client in the SAL session, the RPC call was suspended.
Corrected.
IPE-2833
The WIS process failed when processing the PURGE instruction.
(Parent JIRA
IPE-2817)
Corrected.
TIBCO iProcess Engine Release Notes
Change History 25
|
Defect #
Description
IPE-2836
When using the swutil command to import a procedure library, the memo ID
of one of these procedures was not checked.
(Parent JIRA
IPE-2553)
IPE-2837
(Parent JIRA
IPE-2768)
Corrected.
When EAICOM was installed with iProcess Engine, the following error
message was repeatedly logged in the sw_error log file after performing an
LDAP synchronization:
idl_SQL_allocate_connection_from_pool()
idl_SQL_enlist_connection()
Failed (Statement ID - 0) (ORA-24776: cannot start a new
transaction)
Corrected.
IPE-2838
(Parent JIRA
IPE-2766)
IPE-2845
The FIL definition was not enabled in the iProcess Objects Server process,
which resulted in low performance.
Corrected.
Increase the maximum number of procedures from 4096 to 32768.
Implemented.
IPE-2847
Improve the performance of the WIS process.
(Parent JIRA
IPE-1608)
Implemented.
IPE-2850
Improve the performance of the WIS process filtering by configuring the
WIS_FILTER_LOCALE_SENSITIVE parameter. This improvement makes the case
sensitivity for Russian characters configurable.
(Parent JIRA
IPE-2380)
Implemented.
IPE-2851
The performance of the WIS process filtering was low when UTF-8 was not
configured.
Corrected.
IPE-2855
A deadlock occurred when updating the deleted-item list.
Corrected.
TIBCO iProcess Engine Release Notes
26
|
Release Notes
Defect #
Description
IPE-2856
With configured Oracle RAC, the work items was not retrieved in a work
queue using TIBCO iProcess Workspace (Browser) because a delay occurred
between two Oracle RAC instances.
(Parent JIRA
IPE-2839)
Corrected.
IPE-2857
(Parent JIRA
IPE-2849)
IPE-2858
(Parent JIRA
IPE-2853)
IPE-2862
After cases were migrated to a new procedure version, duplicated work items
appeared in a case when triggering an event.
Corrected.
The WIS process used an incorrect lock when refreshing the indexes in the
user’s queue.
Corrected.
Change the length of the wait_id field in the wait_step table to 10.
Implemented.
IPE-2863
Change the data type of case number and case ID in the database tables from
231 to 232.
Implemented.
IPE-2866
If the Event, Transaction Control step, or step is blank, its procedure definition
will not be cached in memory by the SPO process.
Implemented.
IPE-2865
If an Event, Transaction Control step, or step is blank, its procedure definition
is not cached in memory by the BG process.
Implemented.
IPE-2867
Add the line_cache_compact() function to remove redundant or unused
memory when caching procedure definition.
Implemented.
IPE-2869
Change the data type of the wait_id field in the wait_step, wait, sequences,
and seq_val tables to 232.
Implemented.
IPE-2872
TIBCO iProcess Engine did not start on Linux with Oracle client 11.2.0.2 and
Oracle server 11.2.0.3.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 27
|
Defect #
Description
IPE-2873
Mbox logs showed incorrect information.
Corrected.
IPE-2875
Add the SUBCASE_START_AUTOCOMMIT process attribute to allow a Transaction
Control step to be implicitly inserted as the first step for all sub-cases.
Implemented.
IPE-2876
Reduce the memory size of each index when filtering work queues.
Implemented.
IPE-2877
An option has been added to configure whether or not to free up the WIS
session in the WIS memory after the lock, keep, forward, release, undo, or
unlock operation.
Implemented.
IPE-2878
(Parent JIRA
IPE-2868)
IPE-2879
(Parent JIRA
IPE-2835)
IPE-2881
When logging in to TIBCO iProcess Workspace (Browser) with an expired
password, the password expiration warning was not provided.
Corrected.
A configuration flag has been added in the configuration file to specify
whether or not TIBCO iProcess Objects Server caches the EAI step definition.
Implemented.
Upgrade Tomcat from version 5.5.31 to 6.0.35.
Implemented.
IPE-2882
Add the FREE_WIS_SESSION process attribute to configure whether or not to
free up the WIS session in the WIS memory after the lock, keep, forward,
release, undo, or unlock operation.
Implemented.
IPE-2884
If the RPC_BLOCK process attribute was configured to prevent iProcess
Workspace (Windows) from accessing iProcess Engine, spelling errors
displayed in the error message when logging in to TIBCO iProcess Workspace
(Windows) or TIBCO iProcess Administrator.
Corrected.
IPE-2885
iProcess Engine version 11.3.1 is now compatible with Oracle client 11.2.0.3.
Implemented.
TIBCO iProcess Engine Release Notes
28
|
Release Notes
Defect #
Description
IPE-2891
The sw_error.log and sw_warn.log files only record information received on
the current date. When the date changes, if new information needs to be
recorded to the log files, the previously generated sw_error.log and
sw_warn.log files will be archived with the new file names,
sw_errortimestamp.log and sw_warntimestamp.log.
Implemented.
IPE-2892
The swentobjsv log file is now created with the file name: swentobjsv.log. In
the mean time, the previous log file will be archived as
swentobjsv_timestamp.log, where the timestamp variable is the date when that
log is generated.
Implemented.
IPE-2921
Add the Extra debugging logs to detect the reason for the WIS process crash.
Implemented.
IPE-2925
A value was not correctly passed from procedure to sub-procedure when using
TIBCO iProcess Workspace (Windows) to run a case.
Corrected.
IPE-2936
Upgrade Java from version 1.5 to 1.6 on AIX.
Implemented.
IPE-2937
(Parent JIRA
IPE-2927)
TIBCO iProcess Objects Server did not complete the login message, and
returned the value 1 to the password expired message when logging in to
TIBCO iProcess Workspace (Browser) with an expired password.
Corrected.
IPE-2939
(Parent JIRA
IPE-2922)
Add the SHUTDOWN_MIGRATION_MESSAGE process attribute to configure
whether or not to include the audit message in the published Monitor Event
Detail message. The audit message (with activity ID 34), which writes the
procedure migration information.
Implemented.
IPE-2940
Add the MAINCASE_START_SUTOCOMMIT process attribute to allow a Transaction
Control step to be implicitly inserted as the first step for all main cases.
Implemented.
TIBCO iProcess Engine Release Notes
Change History 29
|
Defect #
Description
IPE-2965
When attempting to release a work item, which contained the fields with
validations, error messages were generated in the TIBCO iProcess Objects
Server log file.
Corrected.
Release 11.3.0
Defect #
Description
IPE-1555
TIBCO Business Studio renumbered the steps of an existing procedure in the new
version. As a result, a wait step did not recognize the steps during migration,
causing it to suspend.
MR 43496
Corrected.
IPE-1576
(Parent JIRA
IPE-2319)
The Background (BG) Processes dumped memory with the error Insufficient
Memory.
Corrected.
IPE-1577
The BG Processes dumped memory with the error Insufficient Memory.
(Parent JIRA
IPE-1581)
Corrected.
IPE-1579
User can reopen cases via SSOLite stored procedures.
MR 43545
Implemented. See Reopen Cases via SSOLite Stored Procedures (IPE-1579) on
page 5.
IPE-1593
Introduce an atomic case start interface and instruction.
MR 43571
Implemented. See A New Case Start Interface and Instruction (IPE-1593) on page 6.
IPE-1602
Include MailID in output messages from IAPJMS.
MR 43607
Implemented. See Include MailID in Output Messages From IAPJMS (IPE-1602) on
page 5.
IPE-1603
Publish step description or extended step description.
MR 43610
Implemented. See Publish Step Description or Extended Step Description
(IPE-1603) on page 5.
TIBCO iProcess Engine Release Notes
30
|
Release Notes
Defect #
Description
IPE-1913
Installing TIBCO iProcess Engine failed if SQL Server used the Windows
authentication account.
Corrected.
IPE-1921
MR 41920
Terminated Date/Time on TIBCO iProcess Workspace (Browser) displayed 00
instead of the actual seconds.
Corrected. See Update Terminated Date/Time Display (IPE-1921) on page 6.
IPE-2013
Expand the plist
-p
command to identify procedure templates.
Implemented. See plist -p Identifies Procedure Templates (IPE-2013) on page 6.
IPE-2016
Deploying libraries from TIBCO Business Studio resulted in the creation of the date
31/12/3000 rather than the actual date.
Corrected.
IPE-2191
A case can be started now only if all necessary information is available.
MR 41628
Implemented. See Start Case Only If All Necessary Information Is Available
(IPE-2191) on page 6.
IPE-2236
The Complete Delayed Release activity completed without updating the field data
of the selected procedure.
MR 43524
Corrected.
IPE-2239
MR 43572
A new instruction is introduced where the case start is implemented in one single
SAL interface and with one single CASESTARTRELEASE message passing to the
background.
Implemented. See A New Case Start Interface and Instruction (IPE-2239) on page 6.
IPE-2254
(Parent JIRA
IPE-2263)
Upon deployment from TIBCO Business Studio to TIBCO iProcess Engine, StepIDs
were not maintained correctly. TIBCO iProcess Engine uses the StepID as part of its
processing for processing a number of actions including Waits and Deadlines.
Therefore, if these numbers change, the process does not progress as expected.
Corrected.
IPE-2256
Make installation separated by roles.
Implemented. See Installation Is Separated by Roles (IPE-2256) on page 7.
TIBCO iProcess Engine Release Notes
Change History 31
|
Defect #
Description
IPE-2257
The swutil IMPORT and EXPORT commands are expanded to import and export
XFR files to a directory outside of SWDIR\util.
MR 11523
Implemented. See IMPORT and EXPORT XFR and XPDL Files to a Directory
Outside of SWDIR/util (IPE-2257) on page 6.
IPE-2258
Audit changes to case data.
Implemented. See Audit Changes to Case Data (IPE-2258) on page 5.
IPE-2259
Audit changes to case data.
Implemented. See Audit Changes to Case Data (IPE-2259) on page 7.
IPE-2282
Issuing an event only updated the data in the parent procedure without
propagating the changes to the sub-cases.
Corrected.
IPE-2316
The WIS process crashed because of a buffer overrun.
(Parent JIRA
IPE-2342)
Corrected.
IPE-2321
The plist
-wv
and plist
-wV
commands can be used together.
Implemented. See Enable plist -wvV and plist -wVv (IPE-2321) on page 7.
IPE-2322
The SWBATCH command utility should return proper return codes when a command
fails.
Corrected. See SWBATCH Returns Proper Return Codes When SWBATCH Fails
(IPE-2322) on page 5.
IPE-2337
Provides a user the option of only migrating live cases.
Implemented. See Optionally Migrate Only Live Cases (IPE-2337) on page 10.
IPE-2344
A memory leak occurred when logging into or out of a TIBCO iProcess Objects
Server on a 64-bit operating system.
Corrected.
IPE-2345
A memory leak occurred when logging into or out of a TIBCO iProcess Objects
Server on a 64-bit operating system.
Corrected.
TIBCO iProcess Engine Release Notes
32
|
Release Notes
Defect #
Description
IPE-2347
The case data fields were not returned when an XPDL file was imported using the
SWUTIL IMPORTLIB command.
(Parent JIRA
IPE-2338)
IPE-2348
Corrected.
Add support to enable rpc blocking from iProcess Workspace (Windows).
Implemented. See Enable RPC Blocking From iProcess Workspace (Windows)
(IPE-2348) on page 9.
IPE-2357
(Parent JIRA
IPE-1402)
IPE-2359
(Parent JIRA
IPE-2349)
IPE-2361
(Parent JIRA
IPE-1522)
IPE-2364
(Parent JIRA
IPE-2336)
The migration operation failed when running the post-install script swinitora to
upgrade TIBCO iProcess Engine version 10.6.1 to 11.0.2 or higher.
Corrected.
STAFFIFC.EXE
crashed when running the swutil MOVESYSINFO, swutil
and swutil EVENT commands.
IMPORT,
swutil IMPORTLIB,
Corrected.
When sending an email by the TIBCO iProcess Email Plug-in, the sent
of the mail in the Microsoft Outlook inbox was incorrect.
time
value
Corrected.
The filtering result was incorrect because a Case Data Queue Parameter (CDQP)
was not defined in procedures. It must be defined in procedures and used as a
filtering parameter to filter correctly.
Corrected.
IPE-2366
(Parent JIRA
IPE-2276)
IPE-2386
(Parent JIRA
IPE-2367)
After importing the participation list, Work Queue Server (WQS) crashed when
executing the MOVESYSINFO function.
Corrected.
Caches the user information to improve performance. Doing so prevents repeated
retrievals of the same information from the database, and limits the frequency of
cache updates to only when there is an update to user information.
Implemented.
IPE-2395
(Parent JIRA
IPE-1448)
The Background (BG) processes crashed when processing an instruction followed
by a JumpTo SSOLite stored procedure call.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 33
|
Defect #
Description
IPE-2397
The performance of the WIS filtering was low when UTF-8 was not configured.
(Parent JIRA
IPE-2394)
Corrected.
IPE-2399
Improve the performance of the WIS filtering, make the case sensitivity for Russian
characters configurable.
(Parent JIRA
IPE-2398)
Corrected.
IPE-2407
The BG processes were stuck at EAI
(Parent JIRA
IPE-2268)
Corrected.
IPE-2408
The BG processes were stuck at EAI
(Parent JIRA
IPE-2401)
Corrected.
IPE-2409
EAI Oracle Step failed when inserting more than 4,000 characters into a
(Parent JIRA
IPE-2400)
Corrected.
IPE-2423
Add support for bulk operations to using a different MBOX SET.
mail
steps.
mail
steps.
memo
field.
Implemented. See Bulk Operations for SSOLite (IPE-2423) on page 8.
IPE-2446
(Parent JIRA
IPE-2003)
A memory leak occurred in TIBCO iProcess Objects Server when accessing audit
trail records (including type_id 16) for a main procedure from which the sub cases
had been previously removed.
Corrected.
IPE-2447
(Parent JIRA
IPE-2242)
IPE-2449
(Parent JIRA
IPE-1566)
IPE-2451
(Parent JIRA
IPE-1559)
A memory leak occurred on the TIBCO iProcess Objects Server when the work
items were unlocked.
Corrected.
The &, <, >, ", and \ characters in the XML output of WorkQueueDeltajms interfaces
were incorrectly normalized.
Corrected.
When SW_QPARAMn was changed to the Date type, the result of the filtering
operation was incorrect.
Corrected.
TIBCO iProcess Engine Release Notes
34
|
Release Notes
Defect #
Description
IPE-2453
IAPJMS only published the changed values for OPEN/KEEP events, not all the
values.
(Parent JIRA
IPE-1596)
IPE-2454
(Parent JIRA
IPE-2354)
IPE-2455
(Parent JIRA
IPE-2365)
Corrected.
Some improvements to input validation should be added in the TIBCO iProcess
Engine Server Manager.
Implemented.
When importing the XFR file to TIBCO iProcess Engine, the security information
was corrupted occasionally, and the corrupted security data in the XFR file was not
reset automatically.
Corrected.
IPE-2459
(Parent JIRA
IPE-1606)
When executing the procedure EAI_BW (delayed released) > EAI_SCRIPT >
EAI_BW (delayed released), the second step, EAI_BW (delayed released), was
executed twice.
Corrected.
IPE-2460
(Parent JIRA
IPE-1605)
After resuming a case from the Suspend state, the case did not proceed to the next
step.
Corrected.
IPE-2461
Releasing a case caused TIBCO iProcess Objects Server to suspend.
(Parent JIRA
IPE-1610)
Corrected.
IPE-2462
When changing the password in TIBCO iProcess Engine, the chgpwd process was
stuck and occupied near 100% CPU if the new password violated the Operating
System rules.
(Parent JIRA
IPE-2264)
Corrected.
IPE-2463
(Parent JIRA
IPE-2265)
The RPC_POOL process was suspended when the serverrun function was called in
the script.
Corrected.
IPE-2465
Performance was getting low when filtering the SW_PARAMn field.
(Parent JIRA
IPE-2266)
Corrected.
TIBCO iProcess Engine Release Notes
Change History 35
|
Defect #
Description
IPE-2468
TIBCO iProcess Objects Director needs to allocate a user to the TIBCO iProcess
Objects Server that has opened a SAL session for the user.
(Parent JIRA
IPE-2346)
IPE-2475
(Parent JIRA
IPE-2267)
Implemented.
The performance of the user_cmp() function was very slow when using the UTF-8
supporting system.
Corrected.
IPE-2476
The buffer overran in the LDAP sync code.
(Parent JIRA
IPE-2269)
Corrected.
IPE-2477
When passing the memo array field to a BusinessWorks step, the data was not
correct.
(Parent JIRA
IPE-2270)
IPE-2478
(Parent JIRA
IPE-2271)
IPE-2479
(Parent JIRA
IPE-2272)
IPE-2480
Corrected.
An error occurred in TIBCO iProcess Workspace (Browser) when using the Start
field to filter cases.
Date
Corrected.
Changing password failed when first logging on to TIBCO iProcess Workspace
(Windows).
Corrected.
Add internal message queue priorities.
Implemented. See Prioritizing the Work Performed by Background Processes
(IPE-2480) on page 8.
IPE-2481
(Parent JIRA
IPE-2274)
The cache on demand queues should be uncached after a configurable period of
time if no user was using the queue.
Implemented.
Note: Configure the time (in minutes) after which the queues should be uncached
by adding a WIS_UNCACHE_PERIOD process attribute for the WIS.
IPE-2482
(Parent JIRA
IPE-2275)
IAPJMS did not function correctly when moving an IAPJMS process from a master
machine to a slave machine.
Corrected.
TIBCO iProcess Engine Release Notes
36
|
Release Notes
Defect #
Description
IPE-2483
The WIS process was occasionally crushed because uncached queues in WIS were
not thread-safe.
(Parent JIRA
IPE-2277)
Corrected.
IPE-2484
Background memory leak occurred when invoking the triggerEvent method.
(Parent JIRA
IPE-2279)
Corrected.
IPE-2487
Removes the TIBCO Hawk installation from the TIBCO iProcess Engine installer.
(Parent JIRA
IPE-2261)
Implemented.
IPE-2488
Upgrades Tomcat from version 5.5.20 to 5.5.31.
(Parent JIRA
IPE-2281)
Implemented.
IPE-2489
The Background (BG) processes were suspended after upgrading to TIBCO iProcess
Engine 11.1.2.5.
(Parent JIRA
IPE-2413)
IPE-2490
(Parent JIRA
IPE-2388)
IPE-2493
(Parent JIRA
IPE-2311)
Corrected.
The TIBCO iProcess Engine user could not log in to the TIBCO iProcess Workspace
(Browser) client for the second time.
Corrected.
Adds support for a new parameter (RPCClntIPs) in TIBCO iProcess Objects Server
to define the list of IP addresses to which the RPC client will be bound.
For usage instructions, see TIBCO iProcess Objects Server Release Notes.
Implemented.
IPE-2494
The WIS process lost work item deadlines under certain circumstances.
(Parent JIRA
IPE-2324)
Corrected.
IPE-2496
A problem occurred when adding the first process into the slave node.
(Parent JIRA
IPE-2326)
Corrected.
TIBCO iProcess Engine Release Notes
Change History 37
|
Defect #
Description
IPE-2497
If an EAISQL step failed (for example, when specifying database parameters that
did not exist), cases that should have remained outstanding were terminated.
(Parent JIRA
IPE-2327)
IPE-2499
(Parent JIRA
IPE-2414)
IPE-2500
(Parent JIRA
IPE-2328)
Corrected.
Cases started through SSOLITE were not distributed evenly across the two queues
in the BG MBox Set.
Corrected.
The default method that created read/write locks on Linux favored the threads that
received read locks. This caused threads that tried to get a write lock to be blocked
for a long time, which caused TIBCO iProcess Engine to be unresponsive.
Corrected.
IPE-2505
(Parent JIRA
IPE-2329)
While purging sub-cases, if a deadlock occurred during the process of getting an
audit trail, the Background (BG) processes did not roll back transactions.
Corrected.
IPE-2506
Performance was low when purging multiple cases using the swbatch command.
(Parent JIRA
IPE-2435)
Corrected.
IPE-2509
The Background (BG) Processes were getting suspended in the IAPJMS process
when publishing a message including empty memo fields.
(Parent JIRA
IPE-2330)
IPE-2510
(Parent JIRA
IPE-2437)
Corrected.
When releasing a new version of a procedure and choosing to migrate existing cases
of that procedure to the new version, the following audit trail entry was generated
for each case:
Case migrated from Procedure vFromVersion to vToVersion by UserName
If TIBCO iProcess Engine was configured to publish activity information, a
corresponding Monitor Event Detail (MED) message should be published for each
case, containing this audit message (with ActivityID = 34). However, this message
was not published.
Corrected.
IPE-2511
(Parent JIRA
IPE-2335)
The field values were not updated when a subprocedure started through the GRAFT
step.
Corrected.
TIBCO iProcess Engine Release Notes
38
|
Release Notes
Defect #
Description
IPE-2519
Performance was low when sorting an empty string in TIBCO iProcess Objects
Server.
(Parent JIRA
IPE-2427)
Corrected.
IPE-2520
The escape characters in the Filter Expression were converted incorrectly.
(Parent JIRA
IPE-2428)
Corrected.
IPE-2521
A problem occurred when creating a participant record for a particular user via
TIBCO iProcess Objects Server.
(Parent JIRA
IPE-2417)
Corrected.
IPE-2522
The global variable abandoned_wqs_list was not initialized to NULL.
(Parent JIRA
IPE-2418)
Corrected.
IPE-2525
Adding a user to a group using the makeAWorkItemListJMS method failed, and
could only succeed after TIBCO iProcess Engine was restarted.
(Parent JIRA
IPE-2419)
IPE-2526
(Parent JIRA
IPE-2430)
Corrected.
The sal_frm_findandinit function, which was used to implement the Open
and Open Next Available Work Item functions,
did not filter the work item list before choosing a work item. This causedthe work
item chosen not to be from the most current data if the work item list had been
changed (like someone changed a CDQP value).
First Available Work Item
Corrected.
IPE-2527
(Parent JIRA
IPE-1585)
Including the character \n in the case description caused TIBCO iProcess
Workspace (Windows) to crash and case list requests using TIBCO iProcess
Workspace (Browser) to fail.
Corrected.
IPE-2528
(Parent JIRA
IPE-2431)
When attempting to release a work item, TIBCO iProcess Objects Server returned an
error to the application, stating that a required field was not
specified, even though all required fields were specified.
swItemErrErr
Corrected.
TIBCO iProcess Engine Release Notes
Change History 39
|
Defect #
Description
IPE-2535
Add support to pass complete arrays into and out of sub-proccedures.
Implemented. See Pass Complete Arrays Into and out of Sub-procedures (IPE-2535)
on page 8.
IPE-2539
(Parent JIRA
IPE-2536)
IPE-2547
The swbatch command utility crashed when processing a command file with the
EVENT command.
Corrected.
The Move System Information took a long time to synchronize not only the
modified roles and groups information but unchanged as well.
Corrected.
IPE-2552
Improve the performance of TIBCO iProcess Objects Server when loading user
cache.
Implemented. See TIBCO iProcess Engine Startup Performance Improvements
(IPE-2552, IPE-2558, IPE-2563) on page 9.
IPE-2554
The performance of TIBCO iProcess Objects Server when loading user cache has
been improved.
Implemented. See TIBCO iProcess Objects Server Startup Performance
Improvements (IPE-2554, IPE-2562) on page 7.
IPE-2558
Improve the performance of TIBCO iProcess Objects Server when checking queues.
Implemented. See TIBCO iProcess Engine Startup Performance Improvements
(IPE-2552, IPE-2558, IPE-2563) on page 9.
IPE-2560
Add support to redirect the work items of which the user is deleted.
Implemented. See Redirect the Work Items of a Deleted User (IPE-2560) on page 9.
IPE-2562
The performance of TIBCO iProcess Objects Server when checking queues has been
improved.
Implemented. See TIBCO iProcess Objects Server Startup Performance
Improvements (IPE-2554, IPE-2562) on page 7.
IPE-2563
Improve the performance of TIBCO iProcess Objects Server by moving it up in the
start-up order.
Implemented. See TIBCO iProcess Engine Startup Performance Improvements
(IPE-2552, IPE-2558, IPE-2563) on page 9.
TIBCO iProcess Engine Release Notes
40
|
Release Notes
Defect #
Description
IPE-2581
The swbatch command utility crashed occasionally when running the swbatch
EVENT command with the -e option in the control file.
(Parent JIRA
IPE-2536)
IPE-2596
Corrected.
Make purging many cases more efficient.
Implemented. See Make Purging Many Cases More Efficient for Oracle (IPE-2596)
on page 9.
IPE-2603
(Parent JIRA
IPE-2667)
IPE-2604
The major version and minor version of a procedure were not correctly reflected in
the IAPJMS activity 34 entry when a case was migrated.
Corrected.
Add support to map an attribute which contains an underscore to one which
doesn’t have one in LDAP.
Implemented. See Map an Attribute Which Contains an Underscore to One Which
Doesn’t Have One in LDAP (IPE-2604) on page 9.
IPE-2609
IPE-2654
(Parent JIRA
IPE-2624)
IPE-2613
TIBCO iProcess Engine did not create a mapping of the MEMATTS and FIELDS
sections between the old and new versions when a new version of the procedure
was imported from TIBCO Business Studio, or was imported with the swutil
command utility.
Corrected.
Create log files in a rotational manner on a daily base.
Implemented. See Create Log Files in a Rotational Manner (IPE-2613) on page 8.
IPE-2619
The memo and attach fields for some steps were lost when importing an XPDL file
through TIBCO iProcess Workspace (Windows).
Corrected.
IPE-2658
The timestamps of the release instructions shown in an audit trail were not correct.
Corrected.See Exact Timestamps for Release Instructions in Audit Trail (IPE-2658)
on page 9.
IPE-2664
Performance was low when processing the rebuild function in the program.
(Parent JIRA
IPE-2168)
Corrected.
TIBCO iProcess Engine Release Notes
Change History 41
|
Defect #
Description
IPE-2666
Adds more logs in the program to trace a cached work item.
(Parent JIRA
IPE-2597)
Implemented.
IPE-2667
The major version and minor versions of a procedure were not correctly reflected in
the IAPJMS activity 34 entry when a case was migrated.
(Parent JIRA
IPE-2603)
Corrected.
IPE-2670
IAP messages were not generated because the audit user failed in validation.
(Parent JIRA
IPE-2551)
Corrected.
IPE-2675
Performance was low when rebuilding the work queues list.
(Parent JIRA
IPE-2168)
Corrected.
IPE-2676
The TIBCO iProcess EAI Bridge COM application GetField() method did not
return Japanese characters correctly.
(Parent JIRA
IPE-2620)
IPE-2687
(Parent JIRA
IPE-2559)
Corrected.
When setting IAPSCHEMA to 1 in the staffcfg file, the BG failed to validate the audit
username for the activity and did not roll back the transaction.
Corrected.
IPE-2690
Using an F3 filter on a queue of items caused the RPC call to time out.
(Parent JIRA
IPE-2672)
Corrected.
TIBCO iProcess Engine Release Notes
42
|
Release Notes
Defect #
Description
IPE-2695
Allows a user to configure the Case Description sort criteria in TIBCO iProcess
Workspace (Windows) to be case-sensitive or not.
Implemented.
This configuration can be done at the node level with a new
WIS_SORT_TEXT_CASE_SENSITIVE parameter in iProcess Engine
SWDIR\etc\staffcfg configuration file:
Section: WQS
Initial Value: 0
Units: N/A
Range: 0 (non-case-sensitive sorting) or 1 (case-sensitive sorting)
Description: Sets the sorting type of the Case Description sort criteria to be
case-sensitive or not.
IPE-2698
(Parent JIRA
IPE-2531)
When TIBCO iProcess Objects Server communicated with the WIS and WQS
processes using the RPC client in the SAL session, the RPC calling was suspended.
IPE-2699
To find out the reason why TIBCO iProcess Obejects Server crashed, add some log
messages into the program.
Corrected.
Implemented.
IPE-2727
(Parent JIRA
IPE-487)
Importing a procedure that contained memo fields from an XPDL file using TIBCO
iProcess Workspace (Windows) reallocated all the data of the memo fields, causing
the corruption of data if old cases were migrated.
Corrected.
IPE-2728
(Parent JIRA
IPE-2656)
The JBoss messaging server did not work appropriately when waiting for a failover
to complete. This caused WIS not to be able to receive the receipt of some Work
Queue Delta messages due to timeout, and resulted in the invalid receipt of all the
subsequent messages.
Corrected.
IPE-2729
Cases was terminated unexpectedly because caching procedures failed.
(Parent JIRA
IPE-2599)
Corrected.
TIBCO iProcess Engine Release Notes
Change History 43
|
Defect #
Description
IPE-2732
Make log files directory configurable.
Implemented. See Log Files Directory Is Configurable (IPE-2732) on page 10.
IPE-2733
The Log Files directory is now configurable.
Implemented. See Log Files Directory Is Configurable (IPE-2733) on page 10.
IPE-2735
(Parent JIRA
IPE-2250)
IPE-2736
(Parent JIRA
IPE-2618)
The WISMDB process crashed when using incorrect WIS information obtained as a
result of the RPC time-out.
Corrected.
When performing the JumpTo operation (or jumping from one step to another) in a
procedure that includes withdrawing a transaction control step (TCS), warning
messages were generated by the WISMBD process.
Corrected.
IPE-2744
Add logs into the programs to investigate why 100% CPU is occupied constantly
when using the swdbqd process.
Implemented.
IPE-2747
100% CPU was occupied constantly when using the swdbqd process.
Corrected.
Release 11.1.3
Defect #
Description
IPE-1585
When the character \n was included in the case description, the TIBCO iProcess
Workspace (Windows) client crashed, and also case list requests using the TIBCO
iProcess Workspace (Browser) failed.
MR 43553
Corrected.
IPE-2242
MR 43587
A memory leak occurred on the TIBCO iProcess Objects Server when the work items
were unlocked.
Corrected.
IPE-2324
The WIS process lost work item deadlines under certain circumstances.
(Parent JIRA
IPE-987)
Corrected.
TIBCO iProcess Engine Release Notes
44
|
Release Notes
Defect #
Description
IPE-2325
Process sentinels failed because the WORKER could not start.
(Parent JIRA
IPE-1474)
Corrected.
IPE-2326
A problem occurred when adding the first process into the slave node.
(Parent JIRA
IPE-984)
Corrected.
IPE-2327
If an EAISQL step failed (for example, when specifying database parameters that did
not exist), cases that should have remained outstanding were terminated.
(Parent JIRA
IPE-1982)
IPE-2328
(Parent JIRA
IPE-1297)
Corrected.
The default method that created read/write locks on Linux favored the threads that
received read locks. This caused threads that tried to get a write lock to be blocked
for a long time, which caused TIBCO iProcess Engine to be unresponsive.
Corrected.
IPE-2330
(Parent JIRA
IPE-1898)
IPE-2335
MR 40500
The Background (BG) Processes were getting suspended in the IAPJMS process
when publishing a message including empty memo fields.
Corrected.
The field values were not updated when a sub-procedure started through the GRAFT
step.
Corrected.
IPE-2338
The case data fields were not returned when an XPDL file was imported using the
SWUTIL IMPORTLIB command.
Corrected.
IPE-2342
The WIS process crashed because of a buffer overrun.
(Parent JIRA
IPE-2316)
Corrected.
IPE-2346
TIBCO iProcess Objects Director needs to allocate a user to the TIBCO iProcess
Objects Server that has opened a SAL session for the user.
Implemented.
TIBCO iProcess Engine Release Notes
Change History 45
|
Defect #
Description
IPE-2354
Some improvements to input validation should be added in the TIBCO iProcess
Engine Server Manager.
Implemented.
IPE-2356
(Parent JIRA
IPE-1402)
IPE-2358
(Parent JIRA
IPE-2349)
IPE-2360
(Parent JIRA
IPE-1522)
IPE-2362
(Parent JIRA
IPE-2336)
The migration operation failed when running the post-install script swinitora to
upgrade TIBCO iProcess Engine version 10.6.1 to 11.0.2 or higher.
Corrected.
STAFFIFC.EXE
crashed when running the swutil MOVESYSINFO, swutil
and swutil EVENT commands.
IMPORT,
swutil IMPORTLIB,
Corrected.
When sending an email by the TIBCO iProcess EAI MAIL plug-in, the sent
value of the mail in the Microsoft Outlook inbox was incorrect.
time
Corrected.
The filtering result was incorrect because a Case Data Queue Parameter (CDQP) was
not defined in procedures. It must be defined in procedures AND used as a filtering
parameter to filter correctly.
Corrected.
IPE-2365
(Parent JIRA
IPE-2288)
When importing the XFR file to TIBCO iProcess Engine, the security information was
corrupted occasionally, and the corrupted security data in the XFR file was not reset
automatically.
Corrected.
IPE-2382
When choosing a server to allocate to a user, TIBCO iProcess Objects Director needed
to select a TIBCO iProcess Objects Server that had already opened a SAL session for
the same user. See Added the STICKY_SAL Attribute (JIRA IPE-2382) on page 11.
Implemented.
IPE-2388
The TIBCO iProcess Engine user could not log in to the TIBCO iProcess Workspace
(Browser) client for the second time.
Corrected.
TIBCO iProcess Engine Release Notes
46
|
Release Notes
Defect #
Description
IPE-2389
There were certain issues in the SW_GET_REQUEST_ID and SW_GET_CASE_NUMBER
stored procedures. Specifically, SW_GET_REQUEST_ID incorrectly used the process
attribute CNUM_SEQ_CACHE instead of REQID_SEQ_CACHE, and there was no way to set
CNUM_SEQ_CACHE and REQID_SEQ_CACHE for SSOLite stored procedures.
(Parent JIRA
IPE-1535)
Corrected.
IPE-2390
The Background (BG) processes crashed when processing an instruction followed by
a JumpTo SSOLite stored procedure call.
(Parent JIRA
IPE-1448)
Corrected.
IPE-2393
The upgrade script did not run correctly for TIBCO iProcess Engine 11.1.2.
(Parent JIRA
IPE-2380)
Corrected.
IPE-2394
The performance of the WIS filtering was low when UTF-8 was not configured.
(Parent JIRA
IPE-2369)
Corrected.
IPE-2398
To improve the performance of the WIS filtering, make the case sensitive for Russian
characters configurable.
(Parent JIRA
IPE-2372)
Implemented.
IPE-2400
EAI Oracle Step failed when inserting more than 4,000 characters into a
(Parent JIRA
IPE-1354)
Corrected.
IPE-2401
The Background (BG) processes were stuck at EAI mail steps.
(Parent JIRA
IPE-2252)
Corrected.
IPE-2402
A deadlock occurred in SQL Server 2000, but TIBCO iProcess Engine did not
recognize it as an error.
(Parent JIRA
IPE-1766)
IPE-2413
Memo
field.
Corrected.
The Background (BG) processes were suspended after upgrading to TIBCO iProcess
Engine 11.1.2.5.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 47
|
Defect #
Description
IPE-2414
Works through SSOLITE were not distributed evenly across the two queues in the
BG MBox Set.
Corrected.
IPE-2417
(Parent JIRA
IPE-2391)
A problem occurred when creating a participant record for a particular user via
TIBCO iProcess Objects Server.
Corrected.
IPE-2418
The global variable abandoned_wqs_list was not initialized to NULL.
(Parent JIRA
IPE-2226)
Corrected.
IPE-2419
(Parent JIRA
IPE-2231)
IPE-2427
(Parent JIRA
IPE-2181)
The operation failed when adding a user to a group using the
method until TIBCO iProcess Engine restarted.
makeAWorkItemListJMS
Corrected.
Performance was low when sorting an empty string in TIBCO iProcess Objects
Server.
Corrected.
IPE-2428
The escape characters in the Filter Expression were converted incorrectly.
(Parent JIRA
IPE-2182)
Corrected.
IPE-2430
(Parent JIRA
IPE-2190)
The sal_frm_findandinit function, which was used to implement the Open First
and Open Next Available Work Item functions, had a
filter parameter that could be used to filter the list before choosing a work item. This
filter should be applied even if the end user did not refreshed the list.
Available Work Item
The advantage of this was that if the work item list had changed (like someone
changed a CDQP value), supplying this parameter would ensure that the work item
chosen was from the most current data.
Corrected.
IPE-2431
(Parent JIRA
IPE-2197)
When attempting to release a work item, TIBCO iProcess Objects Server was
returning an swItemErrErr error to the application, stating that a required field was
not specified, even though all required fields were specified.
Corrected.
TIBCO iProcess Engine Release Notes
48
|
Release Notes
Defect #
Description
IPE-2432
When attempting to release a work item, TIBCO iProcess Objects Server was
returning an swItemErrErr error to the application, stating that a required field was
not specified, even though all required fields were specified.
(Parent JIRA
IPE-2200)
Corrected.
IPE-2435
Performance was low when purging multiple cases using the swbatch command.
Corrected.
IPE-2437
When releasing a new version of a procedure and choosing to migrate existing cases
of that procedure to the new version, the following audit trail entry was generated
for each case:
Case migrated from Procedure vFromVersion to vToVersion by UserName
If TIBCO iProcess Engine was configured to publish activity information, a
corresponding Monitor Event Detail (MED) message should be published for each
case, containing this audit message (with ActivityID = 34). However, this message
was not published.
Corrected.
Release 11.1.2
Defect #
Description
IPE-2261
Remove the TIBCO Hawk installation from the TIBCO iProcess Engine installer.
Implemented.
IPE-2263
Upon deployment from TIBCO Business Studio to TIBCO iProcess Engine, StepIDs
were not maintained correctly. TIBCO iProcess Engine uses the StepID as part of its
processing for processing a number of actions including Waits and Deadlines.
Therefore, if these numbers change, the process does not progress as expected.
Corrected.
IPE-2264
When changing the password in TIBCO iProcess Engine, the chgpwd process was
stuck and occupied near 100% CPU if the new password violated the Operating
System rules.
Corrected
TIBCO iProcess Engine Release Notes
Change History 49
|
Defect #
Description
IPE-2265
The RPC_POOL process was suspended when the serverrun function was called in the
script.
Corrected.
IPE-2266
Performance was getting low when filtering the SW_PARAMn field.
Corrected.
IPE-2267
The performance of the user_cmp() function was very slow when using the UTF-8
supporting system.
Corrected.
IPE-2268
Background processes were stuck at EAI
mail
steps.
Corrected.
IPE-2269
The buffer overran in the LDAP sync code.
Corrected.
IPE-2270
When passing the memo array field to a BusinessWorks step, the data was not
correct.
Corrected.
IPE-2271
An error occurred in TIBCO iProcess Workspace (Browser) when using the Start
field to filter cases.
Date
Corrected.
IPE-2272
Changing password failed when first logging on to TIBCO iProcess Workspace
(Windows).
Corrected.
IPE-2273
When using the SWUTIL command to import an XPDL file into TIBCO iProcess
Engine, the Data tab was blank in the Browser.
Corrected.
IPE-2274
The cache on demand queues should be uncached after a configurable period of time
if no user was using the queue.
Implemented.
Note: Configure the time (in minutes) after which the queues should be uncached by
adding a WIS_UNCACHE_PERIOD process attribute for the WIS.
TIBCO iProcess Engine Release Notes
50
|
Release Notes
Defect #
Description
IPE-2275
IAPJMS
did not function correctly when moving an IAPJMS process from a MASTER
machine to a SLAVE machine.
Corrected.
IPE-2276
After importing the participation list, Work Queue Server (WQS) crashed when
executing the MOVESYSINFO function.
Corrected.
IPE-2277
The WIS process was occasionally crushed because uncached queues in WIS were
not thread-safe.
Corrected.
IPE-2279
Background memory leak occurred when invoking the triggerEvent method.
Corrected
IPE-2280
Previously, whenever acquiring user information, TIBCO iProcess Engine needed to
access a database. Now TIBCO iProcess Engine only needs to access the database
once to get user information and cache it.
Implemented.
IPE-2281
Upgrade Tomcat from version 5.5.20 to 5.5.31.
Implemented.
IPE-2311
Add support for a new parameter (RPCClntIPs) in TIBCO iProcess Objects Server to
define the list of IP addresses to which the RPC client will be bound.
For usage instructions, see TIBCO iProcess Objects Server Release Notes.
Implemented.
MR 43253
(Parent
MR 43077)
The performance of the audit trail caching was low.
MR 43254
(Parent
MR 43080)
Application filters within work queues failed to return any results.
MR 43255
(Parent
MR 43165)
TIBCO iProcess Objects Server crashed when parsing the array field.
Corrected
Corrected.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 51
|
Defect #
Description
MR 43284
The output XFR file was corrupted when exporting a sub-procedure template.
Corrected.
MR 43304
(Parent
MR 43000)
TIBCO iProcess Objects Server generated a dump file when the client tried to set the
field data to a value larger than 255.
MR 43307
(Parent
MR 41636)
The TIBCO iProcess Server Objects Director returned the host name of the TIBCO
iProcess Objects Server. There should be a means to have it return the IP address
instead of the host name.
Corrected.
Implemented. A new IDENTIFY_SPO_MACHINE_BY process attribute has been added
for TIBCO iProcess Objects Director that allows you to specify whether the host
name or IP address is to be returned.
The valid values for IDENTIFY_SPO_MACHINE_BY are:
- HOSTNAME: Returns the host name (the default).
- IP: Returns the IP address.
Refer to Chapter 6 in TIBCO iProcess Engine Administrator's Guide for detailed
information about process attributes and how to set them.
MR 43312
(Parent
MR 43166)
Background Memory leak occurred when starting or releasing a case.
MR 43313
(Parent
MR 43143)
An error occurred when using a filter expression with SSO for Java - additional to
MR 42620.
MR 43306
(Parent
MR 43141)
When importing a procedure into TIBCO iProcess Engine, certain values in the
procedure contained ASCII characters that should not be included.
MR 43315
(Parent
MR 32404)
MR 43316
(Parent
MR 42335)
Corrected.
Corrected.
Corrected.
The WQS responded very slowly to clients for a long time when a lot of
records were being updated.
PARTICIPATION
Corrected.
The length of the req_id and casenum fields were not consistent in the TIBCO
iProcess Engine tables and SSOLite.
Corrected.
TIBCO iProcess Engine Release Notes
52
|
Release Notes
Defect #
Description
MR 43293
The memo data was not correct when setting an element of an array to NULL.
Corrected.
MR 43352
(Parent
MR 41904)
BG Instruction processed the eai_oracle step without a package name.
MR 43354
The threads were suspended in WIS because the write lock was not unlocked.
Corrected.
Corrected.
MR 42969
All libraries were displayed in TIBCO Business Studio, although some of them were
restricted by the access control in TIBCO iProcess Workspace.
Corrected.
MR 43436
(Parent
MR 43420)
When starting TIBCO iProcess Objects Server on a UTF-8 enabled system, memory
corruption occurred in some cases, causing TIBCO iProcess Objects Server to
occasionally crash.
Corrected.
MR 42608
The xpc filter did not work on TIBCO iProcess Engine 11.1.0.2.
Corrected.
MR 42768
If a user who was a participant of other queues had been deleted, you still could
create the participant records.
TIBCO iProcess Engine was not stable after importing participants.
Corrected.
MR 16929
If a user who was a participant of other queues was deleted, the participant records
were not deleted.
Corrected.
MR 43499
A memory leak occurred in TIBCO iProcess Objects Server when accessing audit trail
records (including type_id 16) for a main procedure from which the sub cases had
been previously removed.
Corrected.
MR 43444
When using IAPJMS to send messages that contained symbols, some symbols were
not properly converted. For example, the symbol '&' was not changed to '&amp;'.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 53
|
Defect #
Description
MR 43510
(Parent
MR 43500)
When SW_QPARAMn was changed to the Date type, the result of the filtering operation
was incorrect.
MR 43574
(Parent
MR 43541)
The Background (BG) Processes dumped memory with the error Insufficient
Memory.
MR 43576
(Parent
MR 43543)
The Background (BG) Processes dumped memory with the error Insufficient
Memory.
MR 43577
(Parent
MR 43393)
IAPJMS only published the changed values for OPEN/KEEP events, not all the
values.
MR 43633
(Parent
MR 42660)
After resuming a case from the Suspend state, the case did not proceed to the next
step.
MR 43634
(Parent
MR 43562)
When executing the procedure EAI_BW (delayed released) -> EAI_SCRIPT ->
EAI_BW (delayed released), the second step, EAI_BW (delayed released), was
executed twice.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
MR 43585
(Parent
MR 43412)
After upgrading TIBCO iProcess Engine or TIBCO iProcess Workspace (Windows)
from a lower version to version 11.1.1, an error occurred in TIBCO iProcess Engine
script if there was no space between a keyword and parentheses in the script.
Corrected.
MR 43558
(Parent
MR 43133)
An error occurred in TIBCO iProcess Workspace (Browser) when using the Start
field to filter cases.
Date
Corrected.
TIBCO iProcess Engine Release Notes
54
|
Release Notes
Release 11.1.1
Defect #
Description
MR 40451
Users disabled on the LDAP Server could still log in.
Corrected.
MR41687
(Parent
MR 39824)
The log level of the returned code (-4 and
have been set to the INFO level.
-6)
in the lock_item function should
Corrected.
MR 41691
The contents in some Memo fields were lost or interchanged with another case.
(Parent
MR 41468)
Corrected.
MR 42179
If ulimit
(Parent
MR 41801)
Corrected.
MR 41083
The SPO process was suspended because running this process occupied lots of CPU
resources.
-n
was set to UNLIMITED, TIBCO iProcess Engine could not start up.
Corrected.
MR 43046
Numeric filters did not work correctly after TIBCO iProcess Objects Server was
migrated from 10.3 to 11.0.2.
Corrected.
MR 43052
An error occurred in TIBCO iProcess Objects Server when starting a case with the
Composite arrays.
Corrected.
MR 36175
The process was incorrect when adding an extra case into the existing incomplete
Dynamic Sub-Procedure.
Corrected.
MR 37553
Japanese character strings in the EAICOM dialog were corrupted.
Corrected.
MR 37734
The Background (BG) Processes crashed when the username for the
call was SW_NA.
USERATTRIBUTE
Corrected.
TIBCO iProcess Engine Release Notes
Change History 55
|
Defect #
Description
MR 38713
swutil EXPORTLIB
did not change the version of the Dynamic Sub-Procedure
(DSP) parameter template referred by the DSP step and sub-procedure.
Corrected.
MR 38721
When deploying the processes from TIBCO Business Studio, the number of RPA
definitions was not reset after the RPA validation was resolved.
Corrected.
MR 41019
If a work item was locked, it was still visible in the work queue after it was
withdrawn.
Corrected.
MR 41330
The jumpto operation failed when the case was not migrated.
Corrected.
MR 41500
The EMAIL plug-in did not return an error code or status message.
Corrected.
MR 41559
The Case Data Queue Parameters (CDQP) were invisible from the TIBCO iProcess
Engine client.
Corrected.
MR 41654
XSD should be updated to represent the new version of the schema.
Implemented.
MR41685
A work item was still visible after it was withdrawn.
(Parent
MR 39830)
Corrected.
MR 41688
The Work Queue Server (WQS) consumed vast amounts of CPU resources when the
participation information was cached.
(Parent
MR 40426)
MR 41690
(Parent
MR 41017)
Corrected.
When using an Oracle database and trying to make a call to an EAIDB step in a
procedure, the following error message appeared:
EAI call-out failed("EAIORA_ERR-5 - Invalid Step Definition: No
Stored procedure name.
Corrected.
TIBCO iProcess Engine Release Notes
56
|
Release Notes
Defect #
Description
MR 41714
Initially you did not need to get the write lock in the CCacheRec::LockItem()
function to check the lock.
(Parent
MR 41533)
MR 41715
(Parent
MR 41529)
Implemented.
There was a delay between unlocking the item and removing the item from the
index, which caused -11 to be returned if another command tried to lock the item
after it was unlocked but before it was removed from the index.
Corrected.
MR 41716
(Parent
MR 41342)
MR 41717
(Parent
MR 41420)
MR 41983
The Background (BG) Processes did not roll back the transaction when a deadlock
occurred during a case purge.
Corrected.
A mapped memo output parameter in a stored procedure called by the EAI Oracle
Plug-in occasionally caused the background process to crash.
Corrected.
The wildcard filter with the not
equals
operator did not work correctly.
Corrected.
MR 41984
After upgrading TIBCO iProcess Engine from version 11.0.1 to version 11.1.0 using
the Unicode database option, the packages, triggers and views became invalid.
Corrected.
MR 42013
In a clustered environment, it should be possible to use a separate iProcess Engine
resource group with a network name (rather than machine name or cluster name).
Previously, TIBCO iProcess Engine only looked for machine name or cluster name,
which caused problems when subsequently moving the iProcess Engine resource
group.
Corrected.
MR 42117
The cases could not be purged in TIBCO iProcess Engine 11.1.0.
Corrected.
MR 42132
(Parent
MR 41810)
If the command SWUTIL EXPORT [sub-proc name] -E -a -c -e -l
was used to export the xfr file, then Pstaffer.exe crashed.
-x -v -s
Corrected.
TIBCO iProcess Engine Release Notes
-m -r +t
Change History 57
|
Defect #
Description
MR 42159
If a field name began with EXIT_ in the EAI script, the script would exit.
Corrected.
MR 42176
The CUSTAUDIT command did not work in TIBCO iProcess Engine 11.1.0.
(Parent
MR 41799)
Corrected.
MR 42178
TIBCO iProcess Engine 11.1.0 was suspended for more than 30 minutes on Solaris
(SPARC) when issuing swstart -p if ulimit -n was set to UNLIMITED.
(Parent
MR 41800)
MR 42180
(Parent
MR 42042)
Corrected.
Exporting a procedure created in the iProcess Modeler from the command line
exported only the Released version of the procedure, regardless of which version
was specified.
Corrected.
MR 42182
(Parent
MR 41744)
MR 42184
(Parent
MR 41937)
The performance was low if too many SQL statements were involved in the loading
of the DESCRIPTION attributes.
Corrected.
The sub-procedure name was truncated by the SPO if it was retrieved using Java
SSO in a sub-procedure step.
Corrected.
MR 42206
Configuration of UPPER() Use During Case Data Searching:
(Parent
MR 41522)
Doing an uppercase convert on a number could prevent the use of the index during
case data searching. As a result, timeouts were experienced in TIBCO
BusinessWorks Connector (version 10.6).
A new section had been added in staffcfg:
in STAFF
USE_UPPER, 1 ;Whether the column can use an UPPER() clause
Acceptable values are
1; use an UPPER() clause
0; Do not use an UPPER() clause
Corrected.
TIBCO iProcess Engine Release Notes
58
|
Release Notes
Defect #
Description
MR 42298
If TIBCO BusinessWorks put a String larger than 255 characters into a 255 string
field in TIBCO iProcess Engine, the following error message appeared and the
insert operation failed:
ERROR: ORA-01480: trailing null missing from STR bind value
Corrected.
MR 42478
The DSP Step was not withdrawn correctly if the Don't delete work item checkbox
was checked.
Corrected.
MR 42536
The .log extension was added to the sw_error and sw_warn files.
Implemented.
MR 42607
The sal_queues_getqueue_info32 function was slow because getting the queue
information from the participation queue failed in the Work Queue Server (WQS).
Corrected.
MR 42719
(Parent
MR 40805)
MR 42720
(Parent
MR 41143)
MR 42769
The SQLConnect function returned SQL_ERROR when the connection was opened
successfully.
Corrected.
The Background (BG) Processes were slowed down by the IAPJMS process if a
connection to TIBCO EMS was not available.
Corrected.
An error message displayed after using the incorrect username or password was
not appropriate.
Corrected.
MR 40557
The command line utilities (swutil DCSTART, swutil
handle UTF-8 BOM (Byte Order Mark).
EVENT, swbatch)
did not
Corrected.
MR 42276
The sentinel process could not start up on Microsoft Windows 2008 (x86 64-bit).
Corrected.
MR 42337
The command line swutil proc release -M ALL or -m
case versions when you enabled an AQ port range.
Corrected.
TIBCO iProcess Engine Release Notes
ALL
did not upgrade the
Change History 59
|
Defect #
Description
MR 42820
An error occurred when multiple users were trying to connect to TIBCO iProcess
Engine at the same time from TIBCO Business Studio.
(Parent
MR 41976)
MR 42822
(Parent
MR 37946)
Corrected.
A sw_warn error was generated when passing SW_CASENUM as an expression to a
sub-procedure input parameter.
Corrected.
MR 42824
The RPC_POOL process could not successfully cancel the building of the case list.
(Parent
MR 40947)
Corrected.
MR 42860
The swsvrmgr executable program did not reuse the AQ port range slots correctly if
the swsvrmgr processes were terminated abnormally.
(Parent
MR 38032)
MR 42878
Corrected.
When using the swutil IMPORTLIB command to insert a record into the database,
the database reported the following error message:
String or binary data would be truncated.
Corrected.
MR 42879
Wrong umlaut characters were displayed after dragging and dropping work items.
Corrected.
MR 42880
PROC Manager Watcher Ports were incorrect on Solaris (x86).
Corrected.
MR 42888
(Parent
MR 41962)
MR 42889
(Parent
MR 41268)
MR 42890
The WIS failed to get the work item when the reqid value was greater than the
maximum of a 32-bit integer.
Corrected.
The Dynamic Sub-Procedure (DSP) call error handling did not return any error
messages.
Corrected.
The EAIScript could not handle umlauts characters.
Corrected.
TIBCO iProcess Engine Release Notes
60
|
Release Notes
Defect #
Description
MR 42891
The wrong umlaut characters were displayed when opening a work item.
Corrected.
MR 42917
A deadlock occurred in the WIS process under certain circumstances.
(Parent
MR 42582)
Corrected.
MR 42918
Users could not log in after a connection time out because the connection was not
being recreated.
(Parent
MR 42318)
MR 42922
(Parent
MR 42443)
Corrected.
It was not possible to use LDAP for user validation for swadmin. Setting LDAP_UV to
1 worked for other validation, but not for swadmin.
Corrected.
The LDAP_UV process attribute now accepts the following values:
0 - All validation uses the operating system
1 - swadmin uses the operating system; all other validation uses LDAP
2 - All validation uses LDAP
See TIBCO iProcess Engine Administrator's Guide (version 11.1, page 152) and
LDAPCONF Utility User's Guide (version 11.1, page 46) for details of the LDAP_UV
attribute.
MR 42923
(Parent
MR 42521)
The users on the LDAP server were not synchronized with those on TIBCO iProcess
Engine if the description parameter of a user added to TIBCO iProcess Engine was
empty.
Corrected.
MR 42924
The client crashed intermittently.
(Parent
MR 42551)
Corrected.
MR 42934
The permissions for a procedure were changed after the procedure was imported
into TIBCO iProcess Engine.
(Parent
MR 42520)
Corrected.
TIBCO iProcess Engine Release Notes
Change History 61
|
Defect #
Description
MR 42972
EAI SQL crashed on the stored procedure with the datetime field.
Corrected.
MR 41384
Sometimes TIBCO iProcess Workspace Lite failed to start up. The smstart script
should have been updated to start up TIBCO Workspace Lite.
Corrected.
MR 41755
Long LDAP filters caused buffer overruns.
(Parent
MR 41741)
Corrected.
MR 42904
TIBCO iProcess Engine should not support UTF-8 by default during the
installation.
Corrected.
MR 42989
The procedure could not be saved to HTML in the driver’s root directory.
Corrected.
MR 42991
The performance was low when transferring the UTF-8 encoding on the TIBCO
iProcess Engine and TIBCO iProcess Workspace.
Corrected.
MR 43003
Import of an XPDL file created by TIBCO Business Studio failed.
Corrected.
MR 43013
TIBCO iProcess Engine could not start up if the status of SELinux was not set to
during the TIBCO iProcess Engine installation, but changed to enforce
after the installation.
enforce
Corrected.
MR 43015
TIBCO iProcess Workspace (Windows) crashed after the server configuration
changed.
Corrected.
MR 43026
The performance was low when executing the simulate or predictCase function.
Corrected.
MR 43028
A number of cases were stuck in an EAISCRIPT step in the procedure.
Corrected.
TIBCO iProcess Engine Release Notes
62
|
Release Notes
Defect #
Description
MR 42953
The while loop function in the EAI steps did not work correctly.
Corrected.
MR 43001
The IAPJMS process did not connect to JBoss-4.2.1 because the version of the
file did not meet the requirement of JBoss-4.2.1.
log4j.jar
Corrected.
MR 43034
The WIS process crashed because of a memory leak.
Corrected.
MR 43041
If the different values (True or False) of the UseWorkingDays flag were set to
different procedures in TIBCO Business Studio before the procedures were
deployed to TIBCO iProcess Engine, error occurred in the flag settings for those
procedures in TIBCO iProcess Engine after the deployment.
Corrected.
MR 43042
A buffer overrun occurred in the
sw_LDAP_filter_BG
function.
Corrected.
MR 43044
(Parent
MR 42995)
MR 43048
(Parent
MR 42130)
MR 43050
(Parent
MR 42971)
Certain filters did not work correctly on Red Hat Enterprise Linux 4 and AIX 5L
Version 5.3.
Corrected.
If a Case Data Queue Parameter (CDQP) was defined as swNumeric, it failed to
filter on TIBCO iProcess Workspace (Browser).
Corrected.
The Work Queue Server (WQS) crashed when simultaneously trying to get a queue
in a thread and releasing a queue in another thread.
Corrected.
MR 43051
The SPO event did not update the composite fields.
(Parent
MR 42981)
Corrected.
MR 43054
The performance was low when transferring the UTF-8 encoding in TIBCO iProcess
Engine.
(Parent
MR 42988)
Corrected.
TIBCO iProcess Engine Release Notes
Change History 63
|
Defect #
Description
MR 43055
The jumpto operation did not withdraw the active wait steps.
(Parent
MR 42735)
Corrected.
MR 43056
The proEAI_GetData() API failed to return the value of the SW_STEPNAME field.
(Parent
MR 42892)
Corrected.
MR 43083
When running the swutil
EXTCD
command, inconsistent results were returned.
Corrected.
MR 43099
The installed web server service was removed from TIBCO iProcess Engine after
TIBCO iProcess Engine was upgraded to version 11.1.1.
Corrected.
Release 11.1.0
Defect #
Description
MR 41058
When upgrading from i10.0.3.31 to i11.0.0.2, during the part of the upgrade that
runs database scripts, the following error is displayed:
String variable is not large enough for string.
Check the string declarations.
Corrected.
MR 41016
Sometimes when running a case, an event step causes the following error message
in the sw_error file:
unique constraint (PK_PACK_DATA) violated
Corrected.
MR 40639
TIBCO iProcess Workspace (Windows) cannot reconnect to the Work Queue Server
(WQS) after a timeout.
Corrected.
MR 40860
Ask the user in LDAPCONF whether the LDAP provider is Microsoft Active
Directory on Windows.
Implemented.
TIBCO iProcess Engine Release Notes
64
|
Release Notes
Defect #
Description
MR 40846
Add new information for IAPJMS messages.
Implemented. See Extended Information for IAPJMS Messages (MR 40846) on
page 12.
MR 40664
(Parent
MR 38925)
IAPJMS doesn't capture the message when the case is closed if the "auto-purge" flag
is set on the procedure.
MR 40663
(Parent
MR 39006)
A JumpTo failure does not throw an exception in iProcess Server Objects client.
MR 40662
(Parent
MR 38992)
IAP messages are not generated when a null or empty string memo is published.
MR 40644
(Parent
MR 32926)
The PROCMGR (sentinel) process can crash after a WIS process is killed or crashes.
MR 40642
(Parent
MR 39447)
Wait steps sometimes show redundant flows.
MR 40641
(Parent
MR 39867)
If a procedure definition containing a dynamic sub-procedure call is deployed from
TIBCO Business Studio, when the case is closed the work items of the
sub-procedure are not withdrawn.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
MR 40640
(Parent
MR 39234)
The current version of the sw_get_sequence_trans stored procedure does not
- call the disconnect method at the end of the procedure, or
- destroy objects and call the disconnect method when an error is generated.
Corrected.
MR 40616
(Parent
MR 39353)
The statement for caching procedures is failing; The Background (BG) Processes
continue to try to process work but as it is not caching procedures, all instructions
fail.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 65
|
Defect #
Description
MR 40249
The WIS process can crash following performance issues with processing duplicate
REQUEST instructions from the wismbd, if wismbd has to retry.
Corrected.
MR 39417
Process labels deployed or exported from TIBCO Business Studio to iProcess
destination environments cannot exceed 53 characters. If they do, the following
error is displayed upon deployment:
Could not write object record to database
Corrected; process labels are truncated to the correct length upon deployment or
export.
MR 37907
SQL( 163 IDLMEMOEXISTS_SELECT100 ) is executed at a very high frequency.
Corrected. SQL( 163 IDLMEMOEXISTS_SELECT100 ) and
SQL IDLMEMOSELECT_SELECT100 are now cached.
MR 32149
The iProcess Objects process cannot cache users and therefore cannot start if the
user information has been changed more that 32,768 times.
Corrected.
MR 36538
A sub-procedure does not return to a parent procedure if:
- the parent procedure that calls it is migrated to a new version, and
- the previous versions of the parent procedure are deleted
Corrected.
MR 37126
When large numbers of users are logging into the iProcess Server Objects client at
the same time, a timeout exception occurs.
Corrected.
MR 37303
(Parent
MR 36459)
Work queue searches don't work in Russian as it treats them as case sensitive.
MR 38266
(Parent
MR 36268)
IAPJMS publishes activities regardless of transaction completeness.
Corrected.
Corrected.
TIBCO iProcess Engine Release Notes
66
|
Release Notes
Defect #
Description
MR 38267
(Parent
MR 36449)
Allow configuration of uncommitted reads during an XPC SELECT. Currently only
committed reads can be used. This can cause a problem when updates, inserts and
deletes are performed since the SELECT is, by default, blocked on locks.
Implemented. A new process attribute XPC_READ_UNCOMMITTED is provided.
If this is set to 1, XPC is enabled to use uncommitted reads. If set to 0 (which is the
default) uncommitted reads cannot be used.
See the TIBCO iProcess Engine Administrator's Guide for details about setting process
attributes.
MR 38268
TIBCO iProcess Objects Server can take 60+ seconds doing a TriggerEvent due to a
deadlock and timeout.
Corrected.
MR 38270
The swutil IMPORTLIB command line option needs to be expanded to cater for
files.
XPDL
Implemented.
The swutil IMPORTLIB command remains the same as iProcess Engine detects
whether the library has an xfr or xpdl extension.
For more information on swutil, please see the TIBCO iProcess swutil and swbatch
Reference Guide.
MR 38271
Add support for Business Studio to deploy processes through a firewall.
Implemented.
MR 38272
Include Open and Kept data in IAPJMS messages.
Implemented.
MR 38277
(Parent
MR 38129)
Date in email header is inaccurate by one day between 7 PM and 11:59 PM.
MR 38278
(Parent
MR 37411)
The RPC reply buffer can overrun when returning Case Data Queue Parameter
(CDQP) information for work items
MR 38279
(Parent
MR 37677)
Cases started in TIBCO iProcess Engine (Oracle) cannot be listed using the case
administration tool.
Corrected.
Corrected.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 67
|
Defect #
Description
MR 38280
(Parent
MR 36604)
A call of SQLSetConnectAttr could return SQL_SUCCESS_WITH_INFO. This
should be treated as success instead of failure.
MR 38281
(Parent
MR 36775)
The iProcess Objects server crashes on a case_wflddata call if the field length is
exceeded.
MR 38282
(Parent
MR 34507
If an RPCPool server crashes, users cannot login to the system and a timeout error
message is received.
MR 38283
(Parent
MR 38219)
The Background (BG) Processes do not handle deadlocks properly so transactions
are not rolled back and retried.
MR 38284
(Parent
MR 38145)
Repeated login/logout calls cause the number of handles used by iProcess Server
Objects to grow.
MR 38285
(Parent
MR 32660)
If a WIS process is killed that has a client connected to it, when the sentinels restart
they sometimes cannot reget the port previously being used as it is in a timed-wait
state.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
MR 38293
(Parent
MR 36914)
When using SW_PRIORITY for work item filtering, all work items are returned.
MR 38296
(Parent
MR 35779)
The debug function does not support the %f format.
MR 38298
(Parent
MR 36253)
If the available work queue list is sorted by queue description (WQ_SORT_ITEM,1
in the staffcfg file) and if more than one queue has the same description, then when
the queue list is refreshed, only a single queue shows in the list of available queues
for each distinct queue description value.
Corrected.
Corrected.
Corrected.
TIBCO iProcess Engine Release Notes
68
|
Release Notes
Defect #
Description
MR 38303
(Parent
MR 37909)
An IAP Activity 22 (Suspend) fails with a JMS error "Invalid destination syntax" if
IAPJMS_SIMPLETOPIC is set to 0.
MR 38309
Symbols should not be stripped from UNIX executables; this will make crashes
easier to diagnose.
Corrected.
Corrected.
MR 38406
(Parent
MR 33939)
The RPC library (libswrpc.so) implements the get_myaddress() function, which can
cause problems.
MR 38407
(Parent
MR 34440)
A new configuration flag is needed in the staffcfg file to define how predicted step
duration is to be calculated.
Corrected. The get_myaddress() function is no longer used.
Implemented. A new flag has been added to the staffcfg file as follows:
Flag: DYNDEADPRED
Section: STAFF
Default Value: 1
Unit: n/a
Range: 0 or 1
Description: Defines how the predicted step duration is to be calculated.
Tuning:
If the value is 1, then if the 'Use Deadline for Step Duration' flag is set then use the
deadline as the predicted duration, otherwise, use either the configured duration or
the deadline depending on which would elapse first.
For example, if the deadline was set to expire in one hour and the duration was set
to three hours then the deadline would be used for the predicted duration.
Conversely if the deadline was set to expire in three hours and the duration was set
to one hour then the duration would be used for the predicted duration.
If the value is 0, then if the 'Use Deadline for Step Duration' flag is set then use the
deadline as the predicted duration, otherwise use the configured duration for the
predicted duration.
See ’Defining Duration of Procedure Steps’ in the TIBCO iProcess Modeler - Advanced
Design guide for the Use Deadline for Step Duration flag, and see the TIBCO
iProcess Engine Administrator’s Guide for editing the staffcfg file.
TIBCO iProcess Engine Release Notes
Change History 69
|
Defect #
Description
MR 38410
(Parent
MR 35037)
The installation path for TIBCO Rendezvous was changed for some platforms
causing a Known Issue to be raised against iProcess Engine v10.6.2.
Corrected. The paths have now reverted to their original defaults and the Known
Issue no longer applies.
MR 38411
(Parent
MR 35454)
Prediction fails to calculate the correct critical path through a process with parallel
branches.
MR 38412
Oracle client 10.2.0.4 can now be used to install iProcess Engine.
Corrected.
Implemented.
MR 38428
TIBCO iProcess Engine now supports UTF-8. For more information see TIBCO
iProcess Engine Now Supports UTF-8 (MR 38428) on page 11.
MR 38504
When installing or upgrading, the installer installs the latest version of COM+
events and NobleNet RPC modules. However, it does not check to see if the latest
versions are already installed and it automatically re-installs them.
Corrected. The installer now checks the versions currently installed and only
updates them if necessary.
MR 38563
(Parent
MR 35625)
Cannot change the deadline on a GRAFT step using Dynamic Deadlines.
Corrected.
TIBCO iProcess Engine Release Notes
70
|
Release Notes
Defect #
Description
MR 38648
(Parent
MR 36109)
Add the ability to configure signals that threads are blocked from receiving.
Corrected.
If you wish to enable threads to be blocked from receiving signals then you will
need to modify the $SWDIR/etc/staffpms file, adding the information to line 17 of
the file.
For example, to add blocking for the SIGALRM (14) signal the last few lines of the
file will look like this:
QPARAM1\QPARAM2\QPARAM3\QPARAM4\CP_V...
<blank line - unless UVAPI is configured>
<blank line>
14
If you wish to add more signals to the list they will need to be separated by the '\'
character:
QPARAM1\QPARAM2\QPARAM3\QPARAM4\CP_V...
<blank line - unless UVAPI is configured>
<blank line>
14\13\12\\
For more information on the staffpms file, see TIBCO iProcess Administrator’s Guide.
MR 38649
(Parent
MR 37590)
The message "Process Startup failed. Error -1002: '' is not a Staffware user" is
displayed when using swutil IMPORT to import a procedure.
MR 38650
(Parent
MR 37675)
The iProcess Objects Server can't be started after installing and starting iProcess
Engine.
MR 38671
(Parent
MR 37562)
Change optimization flags used on computationally intense modules on Unix to
improve performance.
MR 38684
(Parent
MR 37954)
swutil EXPORTLIB doesn't change the version of the DSP parameter template
referred by the DSP step and sub procedure.
Corrected.
Corrected.
Corrected.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 71
|
Defect #
Description
MR 38685
(Parent
MR 38597)
The sub-procedure name array is lost when using swutil importlib.
MR 38687
If you import two xpdl files at the same time, the two commands will read and
write to the same .imp file. The program should generate a *.imp log file based on
the name of the xpdl file, for example, if you import carpool.xpdl, it should
generate carpool.imp.
Corrected.
Corrected.
MR 38705
(Parent
MR 33153)
The RPCBG does not handle Transaction Control Steps correctly when initiated by a
JUMPTO instruction.
MR 38719
(Parent
MR 38224)
swrpcsvr RPC_POOL can crash if a long running SQL statement is cancelled.
MR 38770
Corrected.
Corrected.
The Background (BG) Processes will automatically lock all sub cases if the "update
pack data" flag is specified. This can lead to unnecessary deadlocks.
Corrected.
MR 38796
(Parent
MR 36341)
Transactional events are not cleared on a rollback, so will be published on next
commit.
MR 38946
(Parent
MR 38654)
Using an F3 filter on a queue of items can produce incorrect Case Data Queue
Parameter (CDQP) values.
MR 39030
(Parent
MR 32539)
WISMBD processes are not un-paused if one WIS is disabled and another WIS is
killed (or crashes) and is restarted by the sentinels.
MR 39031
(Parent
MR 32764)
When a deadline for a workitem expires and the case is suspended, the suspended
workitem is not removed from the queue when the case is unsuspended.
Corrected.
Corrected.
Corrected. The WISMBD processes are now un-paused after all the enabled WIS
processes have restarted.
Corrected.
TIBCO iProcess Engine Release Notes
72
|
Release Notes
Defect #
Description
MR 39068
(Parent
MR 38180)
The paused child processes can't be un-paused after the parent processes are
restarted by the sentinel.
MR 39108
Provide the option to configure whether or not to use SSL support.
Corrected.
Implemented. See Option to Configure Use of SSL Support (MR 39108).
MR 39175
When a password is reset, the iProcess Workspace (Windows) client gives an error
message, rather than the change password dialog.
Corrected.
MR 39823
(Parent
MR 38493)
The procedure description is not updated on procedure import.
MR 40133
An exception message (Bad SAL/FIL function parameter) can be received when the
Work Item list is refreshed after multiple case starts.
Corrected.
Corrected.
MR 40198
Need to provide an option to choose Unicode encoding in the database or not.
Implemented. See TIBCO iProcess Engine Installation for further information.
MR 40248
(Parent
MR 35523)
Errors are occurring due to parameter template procedures being included in the
audit procedure list.
MR 40250
(Parent
MR 39221)
The rpc timeout variable is not set correctly causing the SALRPCTimeout to be
ignored.
MR 40251
(Parent
MR 38082)
When deploying an xpdl module in Business Studio, if the number of input and
output parameters in the sub-procedure parameter template is greater than 32, this
will cause an RPC server coredump in iProcess Engine.
Corrected.
Corrected.
Corrected.
MR 36301
Change the way the EMPTYMBOXSLEEP process attribute is treated in the
SWBGMBX and WISMBD processes. Values up to (and including) 60 are treated as
a measure of the time to sleep in seconds, and values of greater than 60 are treated
as the sleep time in milliseconds.
TIBCO iProcess Engine Release Notes
Change History 73
|
Earlier Versions
For details of the MRs/CRs implemented in earlier versions of the product, please
see the Readme and Release Notes for that particular product release.
TIBCO iProcess Engine Release Notes
74
|
Release Notes
Restrictions
The table in this section lists known restrictions in this release.
Defect #
Summary/Workaround
IPE-3234
Summary On Windows Server 2003, an error occurs when you use TIBCO
iProcess Engine ldapconf command to connect to the LDAP server with IPv6
addresses.
Workaround To connect to the LDAP server, you can use IPv4 addresses on
Windows Server 2003.
IPE-3113
Summary An error occurs when loading XPDL for a procedure library with any
new functionality into iProcess Workspace (Windows), if the procedure library is
saved as XPDL from a later version of TIBCO iPrcoess Engine, and loaded into
an earlier version of TIBCO iProcess Engine.
Workaround TIBCO does not recommend that you import procedures, which
are exported from a later version of TIBCO iProcess Engine, to an earlier version
of TIBCO iProcess Engine.
See TIBCO iProcess swutil and swbatch Reference Guide for more information.
MR 40988
Summary When a procedure is exported to an XPDL file from TIBCO iProcess
Workspace (Windows), no list or table information is included.
Workaround None.
MR 35378
Summary On some platforms, if you are installing iProcess Java Server Plug-in
to use with this version of iProcess Engine, you cannot run the installer with
Java 1.6, you must use an earlier version such as Java 1.5. However, you can use
Java 1.6 at run-time.
Workaround None.
MR 35194
Summary The iProcess Server Manager does not support language translation.
Workaround None.
TIBCO iProcess Engine Release Notes
Restrictions 75
|
Defect #
Summary/Workaround
CR 19850
Summary The LDAPCONF utility enables you to define which LDAP directory
attributes are mapped to which iProcess Engine properties. However, if you
select option 3 (Set Attribute Mappings) from the LDAP main menu, the
SW_DOMAIN and WISCACHE attributes are not displayed.
Workaround Select option 3 from the LDAP main menu and, when prompted,
select the Add option to manually add the SW_DOMAIN and WISCACHE
attributes as LDAP directory attributes. See Chapter 2, "Creating and
Maintaining iProcess User Data in the LDAP Directory" in the LDAPCONF
Utility User’s Guide for more information.
CR 19525
Summary A temporary file is always left behind when installing the iProcess
Engine, whether the installation is successful or not. The location of the file is
defined by the TEMP system variable. The name of the file is _ISTMPn.DIR
where n is a number that increments each time you install the iProcess Engine.
For example, _ISTMP1.DIR, _ISTMP2.DIR and so on.
Workaround Manually delete the temporary file(s) once the iProcess Engine
installation is complete.
CR 19301
Summary Installation fails if the username of the background user starts with a
numeric; for example, 1swpro.
Workaround Define the background user to start with an alphabetic character.
CR 19010
Summary If the WIS process handles an update event (for example, from a
SWDIR\bin\swutil EVENT -p command) while a user has a work item open,
the Case Description and WQ Parameters revert to the values they had prior to
the update when the work item is kept.
Workaround None.
CR 18901
Summary If you have installed the iProcess COM Server Plug-in and an Oracle
failover occurs, iProcess Engine background processes may stop working. An
affected process cannot perform any further work until the iProcess Engine is
restarted, and writes a 1945-Database error message to the
SWDIR\logs\sw_error file every few seconds. For example:
2006/07/04 12:31:45(BGPREDICT:1:7756:1:pro:idl.c:7.145:5825):
1945-Database error: idl_SQL_allocate_connection_from_pool()
idl_SQL_enlist_connection() Failed (Statement ID - 0) (ORA-25402:
transaction must roll back)
Workaround To stop this message being written to the SWDIR\logs\sw_error
file you must stop and restart the iProcess Engine.
This problem is currently under investigation with Oracle.
TIBCO iProcess Engine Release Notes
76
|
Release Notes
Defect #
Summary/Workaround
CR 18799
Summary If lots of MOVESYSINFO operations are being performed by BG
processes, then the other processes that have to recache the user/group
information might fail due to becoming deadlocked.
It is also possible that the caching process might load group membership or
attribute values that don't match the attributes or queues loaded. This is because
the caching process would first load the queues, then the attributes and finally
the attribute values. If a MOVESYSINFO changed the attribute values before
they were loaded then they may not match the attributes that were loaded prior
to the MOVESYSINFO.
Workaround Once all operations have been completed, modify the user/group
area and perform one last MOVESYSINFO.
CR 18631
Summary If you have an outstanding test mail item for an unreleased procedure
and you delete the step from the procedure that the outstanding mail refers to,
the test mail item can no longer be accessed. This is to be expected as the step has
been deleted from the procedure. However, if you then purge the case for this
inaccessible step the case is purged but the item is never removed from the
message queue.
Workaround None.
CR 18614
Summary When a user logs in to the iProcess Workspace (Windows) test queues
are not displayed in Work Queue Manager. This is because the user's personal
work queue (from which the test queues are created) has not been cached yet.
Workaround If a new work item is sent to a test queue this causes the Rebuild
List button to appear. Alternatively, the user can select their personal work
queue and press F5. This also causes the Rebuild List button to appear. Clicking
Rebuild List displays the test queues.
CR 18467
Summary TIMEZONE setting does not correctly handle daylight savings time
on Windows for zones that do not use North American rules.
Workaround None.
CR 17728
Summary The purge process does not successfully purge pack data and memos
for outstanding Delayed Release steps and for failed steps awaiting retry.
Workaround None.
TIBCO iProcess Engine Release Notes
Restrictions 77
|
Defect #
Summary/Workaround
CR 17669
Summary If you use iProcess activity monitoring on an iProcess Engine that uses
a node cluster architecture, and you enable iProcess activity monitoring on the
master node but not on one or more slave nodes, activity monitoring is disabled.
(This is because the slave node settings contradict the master node settings.)
Workaround Make sure that you enable iProcess activity monitoring on both the
master node and on each slave node when you install the iProcess Engine. See
the iProcess Engine Installation Guide for more information about how to do this.
CR 17603
Summary The J2EE standard supports the use of different security credentials
(username and password) for JNDI InitialContext and JMS connections.
However, in this version of the iProcess Engine, you can only define a single
username and password for the IAPJMS process. The process uses these
credentials for both JNDI InitialContext and JMS connections.
Note that the IAPJMSConnect.SecurityPrinciple property defines the
username. The IAPJMSConnect.SecurityCredentials property defines the
password. Both properties are defined in the iapjms.properties file. See Chapter
9, “Administering Activity Monitoring”, in the TIBCO iProcess Engine
Administrator’s Guide for more information.
Workaround None
CR 17518
Summary If the Oracle listener is stopped and then restarted errors can be
generated.
Workaround None
TIBCO iProcess Engine Release Notes
78
|
Release Notes
Defect #
Summary/Workaround
CR 17466
Summary If you are using iProcess activity monitoring, Monitor Event Detail
(MED) messages with ActivityIDs 16, 19, 20, 25, 26 and 28 do not display the
name of the audit user in the <AuditUser> element. Instead, they display
information that depends on the particular message.
For example, when a sub-procedure is started a MED message with ActivityID
= 16 is generated. The <AuditUser> element in this case shows the SubCaseID of
the sub-case that has been started, not the name of the audit user, as shown
below.
<AuditMessage>Sub-Case started from "SUBCALL1"</AuditMessage>
<AuditStep Name="SUBCALL1">
<Description>SUBCALL1</Description>
<AuditDate
Microseconds="545547">2005-08-24T14:57:56</AuditDate>
<AuditUser>:iPEPublication4:SUBPROC:1:201:201</AuditUser>
</AuditStep>
Workaround None. If you require additional information about the contents of
the <AuditUser> element for one of these messages, please contact TIBCO
Support.
CR 16878
Summary Filtering a view of a case via the TIBCO iProcess Objects Server with a
filter expression that uses a ‘?’ or ‘*’ wildcard character to match against
SW_CASEREF causes an error. A ‘SAL System Error’ message is returned to
TIBCO iProcess Objects (COM).
Workaround None
CR 16833
Summary The WIS process occasionally crashes during shutdown of the
iProcess Engine on a machine which is responding slowly due to a very heavy
paging going on at the same time.
Workaround None
CR 16766
Summary Do not use the LDAPCONF ATTRIB command. It is not supported in
this version of the iProcess Engine. (The command returns "error in parameter
list: Unknown option" errors if you do use it.)
Workaround None
TIBCO iProcess Engine Release Notes
Restrictions 79
|
Defect #
Summary/Workaround
CR 15531
Summary Adding a numeric user attribute with decimal places actually creates
an attribute with 24 Characters and no decimal places.
This happens if the attribute is added using the iProcess Administrator or via
SWDIR\bin\swutil USERINFO. For example, if you add a numeric attribute
with length 10.2, it is actually created as a numeric attribute with length 24.0.
Workaround None
CR 15444
Summary During the upgrade process, the iProcess Engine services are deleted
and then re-created. If the Services window is open during this process the
system will not actually delete the service but will mark it for deletion, which
will be performed at the next reboot.
Workaround If this error occurs during upgrade you will need to reboot the
machine and re-run the upgrade process.
CR 15334
Summary When you upgrade from a Version 9 Process Engine the entries in the
at_id column of the audit_trail table are migrated to the audit_usecs column.
at_id values that are greater than 1 million are truncated after upgrade, which
means that the correct ordering of audit trail rows is lost.
This is only an issue when the number rolls over from 6 to 7 digits and the audit
trail items are from the same case and have the same timestamp. If all the
numbers are above 6 digits then all entries are truncated and ordering is
preserved.
Workaround None
CR 15319
Summary If you change the date separator in the SWDIR\etc\staffpms file to a
hyphen (-):
•
when you enter a date field in a form the separators are displayed correctly,
but change to backslash characters (/) when you tab off the field.
•
when you release the form, one or more background processes crash.
Workaround None
CR 15311
Summary The following fields do not appear in the Available Fields list of fields
in the Inputs or Outputs tab for iProcess Engine plug-ins:
•
SW_IP* Fields
•
SW_STEPNAME
•
SW_STEPDESC
Workaround None
TIBCO iProcess Engine Release Notes
80
|
Release Notes
Defect #
Summary/Workaround
CR 14598
Summary When you map sub-procedure output parameters to main procedure
fields, you can define a private Output Mapping script which runs after all
mappings have been performed (for example, to perform additional field
manipulation). These output mapping scripts are ignored when performing case
prediction.
Workaround None
CR 14597
Summary If a memo field is defined as an input or output parameter for a
sub-procedure, it is ignored when performing case prediction - no data is passed
for the field.
Workaround None
CR 14595
Summary If a procedure contains a set of conditions where there is a FALSE
result followed by multiple TRUE results, the iProcess Engine can, when
performing case prediction, incorrectly process the conditions and produce
future work items for both the True and False paths.
Workaround None
CR 14225
Summary When viewing cases, filter criteria that use the ? operator (such as
SW_CASENUM ? "2") or regular expressions using the same character
(SW_CASENUM ? "1234?") will fail.
Workaround Either:
•
Use the equality operator, =, instead; for example, SW_CASENUM = "2", or
•
Use a * wildcard character in the regular expression; for example, "1234*".
This will succeed, but will produce a wider range of results than the ?
character should; any case number that starts with 1234 will match.
TIBCO iProcess Engine Release Notes
Restrictions 81
|
Defect #
Summary/Workaround
CR 12961
Summary The following iProcess Expressions are currently not available to the
iProcess Script Server Plug-in. Therefore, even though you can successfully enter
the expressions in your iProcess Script plug-in definition, they will not be
processed by the iProcess Engine. All of the following expressions will return
SW_NA (except GOTOSTEP, which has its own error code).
•
ATTACHFILENAME
•
CALL
•
CASECLOSE, CASESTART, CUSTAUDIT
•
DBWRITEFIELDS, DDEGETNAME, DDEGETTOPIC, DDEINITIATE,
DDEPOKE, DDETERMALL, DDETERMINATE, DDEXECUTE
•
FILEREQUEST, FORMCONTROL, FORMMAXIMIZE, FORMMINIMIZE,
FORMMOVE, FORMRESTORE, FORMSIZE
•
GETHANDLE, GOTOSTEP
•
MARKFIELDCHANGED, MEMOFILE, MESSAGEBOX
•
READFIELDS
•
SCRIPT
•
SENDKEYS, SERVEREXEC, SERVERRUN
•
TRIGGEREVENT
•
UNIXEXEC, UNIXRUN
•
VLDFILE, VLDFILEX, VLDQUERY
•
WINACTION, WINACTIVATE, WINCLOSE, WINEXIST, WINFIND,
WINMAXIMIZE, WINMESSAGE, WINMINIMIZE, WINMOVE,
WINRESTORE, WINRUN, WINSIZE, WRITEFIELDS
The following iProcess data fields are not available:
•
SW_USER:attribute
•
SW_GROUP:attribute
•
SW_IP_work item priority fields
Workaround None
CR 12037
Summary You should not use any special characters (!, £, &, *, ?, /, etc.) when
naming new groups, roles, lists or tables using SWDIR\bin\swutil.
Workaround None
TIBCO iProcess Engine Release Notes
82
|
Release Notes
Defect #
Summary/Workaround
CR 12023
Summary Do not create attribute names that end in the string _XX, where XX is
a two digit number. This string is reserved for internal use by the iProcess
Engine.
Workaround None
CR 12001
Summary The iProcess Engine’s DNS Host Name must be identical (including
case) to its Computer Name. If these names are different, users will not be able
to log in to this iProcess Engine from the TIBCO iProcess Workspace (Windows).
Workaround To make sure the names are identical:
1. In Control Panel, double-click the System icon. The System Properties
dialog is displayed.
2. On the Network Identification tab, click Properties. The Identification
Changes dialog is displayed.
3. Click More. The DNS Suffix and NetBIOS Computer Name dialog is
displayed.
4. Note the Primary DNS suffix of this computer. If it is not already the same,
change this name to match the NetBIOS computer name.
CR 11428
Summary During the starting or stopping of the iProcess Engine, there can be a
pause of 60 seconds between a process (once shutdown) publishing an event and
all the subscribers receiving it. This makes it look like the system has not fully
shutdown or started up. This is a problem with the COM+ Events system and a
resolution is being sought from Microsoft.
Workaround None
TIBCO iProcess Engine Release Notes
Restrictions 83
|
Defect #
Summary/Workaround
CR 10878
Summary When a case is being processed, the
MAX_SUB_PROCEDURE_DEPTH limit (from the process_attributes table) is
checked when a sub-case is started. If this limit is going to be exceeded, the
sub-procedure should not start. Instead, an error message is written to the
SWDIR\logs\sw_warn file and the next step (at the immediate parent level)
should be started instead.
However, this functionality does not work correctly in this version of the
iProcess Engine. If the MAX_SUB_PROCEDURE_DEPTH limit is reached (not
exceeded):
•
the sub-procedure is not started.
•
the procedure jumps back to the main procedure, and the next step at that
level is started.
•
any data set in any intermediate sub-procedure steps is lost. This means that
any further step processing can contain incorrect case data.
Workaround None
CR 07082
Summary If you set or change the value of the URGENTPRIORITY attribute,
you will need to restart the iProcess Engine before the new value takes effect.
Workaround None
TIBCO iProcess Engine Release Notes
84
|
Release Notes
Known Issues
This section lists known issues in the current release.
Summary
Summary The step_addr column of the predict table displays NOADDR when
a new user is added to TIBCO iProcess Engine.
Workaround Restart TIBCO iProcess Engine.
Summary When importing users without user descriptions in the XFR file
through TIBCO iProcess Administrator, the imported users can not be used to
log into TIBCO iProcess Workspace (Windows).
Workaround When importing users through TIBCO iProcess Administrator,
import users with user descriptions in the XFR file.
Summary TIBCO iProcess Engine fails to be moved to another machine in the
same Microsoft Windows cluster by using Move To option in the Failover
Cluster Administrator.
Workaround Before moving TIBCO iProcess Engine to another machine in the
same Microsoft Windows cluster in the Failover Cluster Administrator, run the
following command at the command prompt:
SWDIR\util\swadm move_server machine_id machine_name
where:
— machine_id is the server identifier of the source server, such as, 1, 2, 3.
— machine_name is the name of the Microsoft Distributed Transaction
Coordinator resource (MSDTC). See "What is MSDTC" in TIBCO iProcess
Engine Architecture Guide for more information.
Summary TIBCO iProcess Engine cannot start when connecting Oracle
database 11.1.0.6 using Oracle client 11.2.0.2.
This is an Oracle defect. Oracle database 11.1.0.6 can result some known issues
for which Oracle has not provided any fix yet.
Workaround Change the database version to required Oracle database versions
for TIBCO iProcess Engine.
For required Oracle versions, see "Table 11 Required Oracle Database and
Client Versions" in iProcess Engine for Windows Installation or iProcess Engine for
UNIX Installation.
TIBCO iProcess Engine Release Notes
Known Issues 85
|
Summary
Summary TIBCO iProcess Engine cannot start when connecting Oracle
database 11.2.0.1 using Oracle client 11.2.0.2.
This is an Oracle defect for which Oracle has not provided any effective fix yet.
See Oracle Documentation 1310859.1 for more information.
Workaround Change the database version to required Oracle database versions
for TIBCO iProcess Engine.
For required Oracle versions, see "Table 11 Required Oracle Database and
Client Versions" in iProcess Engine for Windows Installation or iProcess Engine for
UNIX Installation.
Summary After installing TIBCO iProcess Engine on a Microsoft Windows
platform, an iProcess Engine service user without the local administrator rights
cannot start the iProcess Engine services if User Access Control (UAC) is
enabled on the Microsoft Windows platform.
Workaround Disable User Access Control (UAC) on the Microsoft Windows
platform.
Summary TIBCO iProcess Engine Server Manager cannot work with TIBCO
HAWK (64bit) on the Microsoft Windows platforms.
Workaround Follow these steps:
1. Back up the tomcat and java folders under $SWDIR.
2. Copy the 64bit tomcat and JDK folder to $SWDIR and rename them to
tomcat and java respectively.
3. Copy the ipsvrmgr folder and iProcessReports.war file under the
backed-up tomcat/webapps folder to $SWDIR/tomcat/webapps folder.
4. Delete contents under $SWDIR/tomcat/work.
5. Rename the tomcat6.exe and tomcat6w.exe files under the
$SWDIN/tomcat/bin folder to tomcat5.exe and tomcat5w.exe.
6. Restart TIBCO iProcess Engine.
TIBCO iProcess Engine Release Notes
86
|
Release Notes
Summary
Summary Work items cannot be seen in the work queue when configuring
IAPJMS
for JBoss.
Workaround Follow these steps:
1. Copy $JBOSS_HOME\client\log4j.jar to $SWDIR\jar\thirdpart\
2. Open the $SWDIR\etc\iapjms_classpath.properties configuration file
and replace classpath.internal.log4j=thirdparty/log4j-1.2.8.jar
with classpath.internal.log4j=thirdparty/log4j.jar
3. Restart TIBCO iProcess Engine.
Summary When installing TIBCO iProcess Engine, UTF-8 is not supported by
default.
Workaround Manually set up support for UTF-8 in TIBCO iProcess Engine.
During installing TIBCO iProcess Engine:
— For interactive installation
For a new installation, the default behaviour should be NOT supporting
UTF-8.
For upgrading, if old version supports UTF-8, the default behaviour
should be supporting UTF-8, and it should NOT be editable. If old
version not supports UTF-8, the default behaviour should be NOT
supporting UTF-8, and it should be editable.
— For silent installation:
If it is upgrade and old version supports UTF-8, the behaviour should be
supporting UTF-8 and it should NOT be changed. Otherwise, whether
supporting UTF-8 is up to the value set in the response file.
See TIBCO iProcess Engine Architecture Guide for more details about configuring
your system to support UTF-8.
Summary The PM_AUTO_BOOT parameter should not be set in a cluster of the
TIBCO iProcess Engine nodes.
Workaround Follow these steps to set the PM_AUTO_BOOT parameter and start
the cluster:
1. Set the PM_AUTO_BOOT parameter to 0.
2. Run swstart
-p
to start the sentinels on all nodes.
3. Run swstart to start TIBCO iProcess Engine on any node.
TIBCO iProcess Engine Release Notes
Known Issues 87
|
Summary
Summary TIBCO iProcess Web Services Server Plug-in does not update the
memo field correctly if the database is using UTF-8.
Workaround None.
Summary If you select the option "User must change password at net logon" in
Active Directory, and then sync to iProcess Engine, the user cannot login to
iProcess Engine.
Workaround None.
Summary If you upgrade from a TIBCO iProcess Engine Version 10.5 to a
TIBCO iProcess Engine Version 10.6 or later with a node cluster installation,
your iProcess system will have an extra SWLIB_PATH process attribute.
The SWLIB_PATH process attribute is created when you install the iProcess
Engine (i.e. 0 ALL 0 SWLIB_PATH). In older versions of the iProcess Engine,
one SWLIB_PATH process attribute was created whether your iProcess Engine
installation scenario was a single node or a node cluster.
In the iProcess Engine Version 10.6, a change was implemented that meant that
if you install the iProcess Engine in a node cluster, a SWLIB_PATH process
attribute is created for every node in the cluster (i.e. 1 ALL 0 SWLIB_PATH, 2
ALL 0 SWLIB_PATH and so on). This means that, if you upgrade from an
iProcess Engine Version 10.5 to an iProcess Engine Version 10.6 or later with a
node cluster installation, you will have a SWLIB_PATH process attribute for
your original iProcess Engine installation and a SWLIB_PATH process attribute
for each iProcess Engine in your node cluster. The SWLIB_PATH process
attribute created with your original iProcess Engine installation (i.e. 0 ALL 0
SWLIB_PATH) is not required, but is not removed as part of the upgrade
process. However, it can be removed manually using SWDIR/util/swadm.
Summary The LDAPCONF Utility’s test connection file output option uses
UNIX carriage returns. This makes it difficult to view the output in Notepad.
Workaround Use another text editor, for example, Wordpad.
Summary Services are not removed correctly if the Microsoft Management
Console dialog is open.
If the Microsoft Management Console dialog is open and a service is stopped
and then deleted, the Startup Type of the service can be shown as Disabled.
The service will be removed when the Microsoft Management Console dialog
is closed.
The problem does not occur if you are using command line utilities. This is a
known problem documented in the Microsoft Knowledge Base.
TIBCO iProcess Engine Release Notes
88
|
Release Notes
Summary
Summary Disabling cached logon information in a domain environment.
By default, Windows 2000 caches previous users’ logon information locally.
This ensures that users are able to log on if a domain logon server is
unavailable during subsequent logon attempts. However, this feature could
result in users with invalid passwords still being able to log on to the iProcess
Suite. For example, a user whose password has been changed attempts to
logon to the iProcess Suite with their old password. If the domain controller is
not available to validate the current password but the old password is still
cached locally, the logon attempt will be accepted.
You can prevent this from happening by disabling the cached logon
information feature in Windows 2000. If you do this, a user will not be able to
logon to the iProcess Suite if the domain controller is not available to validate
their password.
For more information about how to disable logon caching, please refer to the
Cached Logon Information article (Article ID: Q172931), available from the
Microsoft Personal Support Centre at:
http://support.microsoft.com/kb/q172931/
Summary Operating system dates later than 31st December 2037 are not
supported.
Although designed to process dates up to the year 3000, the iProcess Suite has
been modified - in the interests of data integrity - to shut down if the system
date exceeds 31st December 2037.
The iProcess Suite uses the time() system call to get the system date and time.
This call returns the system date and time as the number of seconds since
midnight, 1st January 1970 as a signed integer (32-bits). This means that the
time() function (which is commonly referred to as UNIX time) is unable to
return a time beyond 19th January 2038, 03:14:07 UCT.
To protect the integrity of your iProcess installation, the iProcess Engine will
create a file SWDIR\logs\sw_error and shut itself down if the system returns a
date beyond 31 December 2037. You should not use operating system dates
later than this. Potentially, ALL applications that use the time function are at
risk beyond this date.
TIBCO iProcess Engine Release Notes
Known Issues 89
|
Summary
Summary Large Number of User Logins May Cause Problems.
If your client application performs a large number of user logins to the iProcess
Engine, it may experience problems that are a result of running out of TCP
ports, or attempting to connect to a TCP port above 5000. You may see one of
the following problems in the client application or the iProcess Engine:
•
the system hanging or exhibiting unexpected behavior
•
unable to create new connections to the server
•
Event ID 2009 “Number of sessions exceeds 2048” may be written to the
event log
•
the local computer responds with a WSENOBUFS (10055) error
For information about resolving these issues, refer to Microsoft Knowledge
Base articles Q149532 and Q196271. These can be found at:
http://support.microsoft.com.
Summary Invalid data type causes error.
If an incorrect type of data is passed into a field (e.g., text is passed into a
numeric field) when executing the StartCaseEx method, an “Invalid data for
field” error is thrown by the iProcess Engine. Even though invalid data is
passed, the case is still started. Field values in the FieldValues array prior to the
invalid data are correctly assigned to their respective fields; field values in the
FieldValues array after the invalid data are NOT assigned to their respective
fields.
Summary Same user logged on multiple times causes degradation/possible
errors.
The same user logging on multiple times to the same iProcess Engine may
result in performance degradation. The iProcess Engine will allow only one
transaction to be processed at a time for users that are logged on multiple times
to that server, resulting in slower processing
Summary No support for attachments.
There is currently no support for fields of type swAttachment.
Summary Cannot access default attribute values.
The TIBCO iProcess Engine does not store default values for Attributes. Consequently, the Value property of an SWAttribute object does not have any value
when accessed from an SWNode object.
TIBCO iProcess Engine Release Notes
90
|
Release Notes
Summary
Summary Locking work items.
The SAL SDK allows long locking multiple times by the same user name. Consequently, in the iProcess Engine, it is possible to lock the same work item from
a work queue using a different login session if there are two or more clients
logged in as the same user name.
Summary Text field attribute lengths stored in multiples of 24.
All attributes except for text fields are set to a length of 24 if a length is not
specified or if some length (up to 24) is specified. Decimal places are not stored.
For text fields, length is set to 24 if no length is specified. If a length is specified,
the actual length will be the next multiple of 24, up to the maximum length of
255. For example, creating a text field 25 characters long will result in the field
actually being 48 characters long.
Summary Audit filtering limitations on sub-cases.
When specifying an audit filter for a sub-case, or a parent case that contains a
sub-case, the following limitation applies: If your filter criteria does not match
the sub-case started audit entry in the parent case, no audit entries are returned
for the sub-case, regardless of whether the filter criteria matches audit entries
of the sub-case.
The work around for this is to specify the following in your AuditFilterExpr filter expression:
FILTER_FLAGS=[AF_ALL_SUBSTART]
Summary Single numeric values in range filters must have correct decimals.
If you specify single values in a range filter expression, and the field that you
are filtering on is defined as a numeric field with decimal positions, the decimal positions must be included with the single values in the expression and the
single values must be shown in the form of a range.
For example, assume SW_QPARAM2 is defined as a numeric field with two
decimal positions. The following example shows the proper way to specify a
filter expression that includes single values:
SW_QPARAM2=[1-3|5.00-5.00|8-9|18-22|25.00-25.00]
(The single values in the example above are 5.00-5.00 and 25.00-25.00.)
When you specify a range of values (e.g., 1-3), you do not need to include the
decimal positions. In other words, you don’t need to specify “1.00 - 3.00”.
TIBCO iProcess Engine Release Notes
Other Information 91
|
Other Information
TIBCO iProcess® Conductor EAI Order Step Should be Preceded by a
Transaction Control Step
Before invoking the iProcess Conductor Order plug-in for the first time it is
important that the initial transaction for the process in which it is executing is
committed.
If you use an EAI Order step close to the beginning of a procedure or
sub-procedure, you should therefore place a Transaction Control Step
immediately before it.
Using SWDIR\util\plist
You can use the SWDIR\util\plist X option to provide backwards compatibility
with Staffware 2000. For example, using plist -pv does not report counts, but you
can use plist -pvX to specify Staffware 2000 compatibility so that counts are
derived. Enter SWDIR\util\plist at the command line to display a full list of
options.
Must Normalize Case Data to View Cases
When you install the iProcess Engine, there is a check box in the Configuration
window that is used to enable a feature called CaseData Normalization. If you are
using an application developed with iProcess Objects or iProcess Server Objects,
you must enable case data normalization. If it is not enabled, cases will not appear
in the case list.
Case data normalization can be enabled either during the installation, or at a later
time using the Case Data Normalization utility, swnormcd.
For more information about case data normalization and using swnormcd, see
TIBCO iProcess Engine Administrator’s Guide.
Large Number of User Logins May Cause Problems
If your client application performs a large number of user logins to the iProcess
Engine (for example, in a stateless or web environment), it may experience
problems that are a result of running out of TCP ports, or attempting to connect to
a TCP port above 5000. You may see one of the following problems on either the
client or iProcess Engine:
TIBCO iProcess Engine Release Notes
92
|
Release Notes
•
the system suspending or exhibiting unexpected behavior
•
unable to create new connections to the server
•
Event ID 2009 "Number of sessions exceeds 2048" may be written to the event
log
•
the local computer responds with a WSENOBUFS (10055) error
For information about resolving these issues, refer to Microsoft Knowledge Base
articles Q149532 and Q196271. These can be found at:
http://support.microsoft.com.
Upgrading from Earlier Version May Cause Error Messages in Log File
Upgrading from an earlier version of the iProcess Engine to version i10.0 (0.0) or
later may cause error messages similar to the following to appear in the iProcess
Engine log file:
ERROR|error in sal_pver_audlist procname($EMAIL) err(0) curridx(1)
ERROR|error in sal_pver_audlist procname($SYSTEM) err(0)
curridx(1)
ERROR|error in sal_pver_audlist procname(CARPOOL) err(0)
curridx(1)
These messages are a result of the upgrade, but an error has not occurred.
Disregard the messages.
Node Name Cannot Contain Certain Characters if Using Access Database
The iProcess Engine uses the Microsoft Access database to store information
concerning auto forwarding, view-only queues, and anonymous logons. If you
are using any of this functionality, the name of the TIBCO iProcess Engine (node
name) cannot include any of the following characters:
! * = ( ) { } [ ] ; @ \ , ?
If the node name contains any of the listed characters, the iProcess Engine will fail
on startup. This is a result of a limitation in ODBC that does not allow the Access
connect string (which includes the node name) to contain these characters.
TIBCO iProcess Engine 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