TIBCO iProcess Engine (DB2) for UNIX and Linux Release Notes

TIBCO iProcess Engine (DB2) for UNIX and Linux Release Notes
TIBCO iProcess® Engine
(DB2) for UNIX and Linux
Release Notes
Software Release 11.3.0
October 2011
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO iProcess, TIBCO iProcess Suite, TIBCO
Enterprise Message Service, TIBCO FormBuilder, and TIBCO General Interface are either registered trademarks
or trademarks of TIBCO Software Inc. in the United States and/or other countries.
EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 1999-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
viii
viii
viii
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Release 11.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Release 11.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
21
21
21
21
21
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
23
35
39
45
55
65
69
70
75
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
TIBCO iProcess Engine Release Notes
iv
| Contents
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIBCO iProcess® Conductor EAI Order Step Should be Preceded by a Transaction Control Step . . . . . . .
Clearing the sw_subscription_list Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using $SWDIR/util/plist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product Re-branding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIBCO iProcess Engine Release Notes
90
90
90
91
91
|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
•
Typographical Conventions, page vi
•
Connecting with TIBCO Resources, page viii
TIBCO iProcess Engine Release Notes
vi
| 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:\swerver\staffw_nod1 on a Windows server
(on the C: drive), then the full path to the swutil command is
C:\swerver\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 vii
|
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
viii
| Connecting with TIBCO Resources
Connecting with TIBCO Resources
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and
resident experts, a place to share and access the collective experience of the
TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety
of resources. To register, go to http://www.tibcommunity.com.
How to Access All TIBCO Documentation
After you join TIBCOmmunity, you can access the documentation for all
supported product versions here:
http://docs.tibco.com/TibcoDoc
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, please
contact TIBCO Support as follows.
•
For an overview of TIBCO Support, and information about getting started
with TIBCO Support, visit this site:
http://www.tibco.com/services/support
•
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user
name, you can request one.
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 21
•
Compatibility, page 22
•
Change History, page 23
•
Restrictions, page 76
•
Known Issues, page 85
•
Other Information, page 90
TIBCO iProcess Engine Release Notes
2
|
Release Notes
New Features
This section lists features added since the last major release (11.0.0) of this
product.
Release 11.3.0
The following are new features in this release.
Include MailID in Output Messages From IAPJMS (IPE-1602)
MailID is added to the output messages from IAPJMS so that users can use this
mailID to build a tag for each work item.
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.
To enable this feature, complete the following steps:
1. Open the staffcfg file in the SWDIR\etc directory.
2. Change the IAPSCHEMA2_1 parameter value to 1.
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 via 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 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).
TIBCO iProcess Engine Release Notes
New Features 3
|
To audit such changes to case data, you must first set the
AUDIT_CASEDATA_CHANGED attribute to 1 by running swadm
set_attribute 1 SPO 0 AUDIT_CASEDATA_CHANGED 1.
A new audit message "133: Case data changed by USER" is generated to record
such changes to case data.
Reopen Cases via SSO Lite Stored Procedures (IPE-1579)
Users can resurrect cases via the SSO Lite stored procedures.
To resurrect cases in DB2, run the following command in the database client tool:
call sw_casereopen('proc_name', 'user_id','step_name',case_num);
where:
•
proc_name is the name of the procedure that you want to resurrect.
•
user_id is the name of the iProcess user who is resurrecting the cases.
•
step_name is the name of the case step that you want to resurrect.
•
case_num is the number of the cases that you want to resurrect.
Update Terminated Date/Time Display (IPE-1921)
Terminated Date/Time is now stored including Seconds. It can be viewed via the
SSO interface, or viewed in 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 via SSO 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.
The CASESTARTRELEASE message is sent directly from the iProcess Objects
Server to BG. BG processes the case start and immediately performs the actions
for the first step. By doing so, the load on WIS is reduced because the case start no
longer involves WIS at all.
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, flag I indicates that the procedure is a
sub-procedure.
TIBCO iProcess Engine Release Notes
4
|
Release Notes
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.
To import a procedure (for example, carpool.xfr) from a directory outside of
SWDIR\util (for example, c:\\), run the following command:
SWDIR\bin\swutil IMPORT c:\\carpool.xfr
where the .xfr file format is mandatory to make it work.
To export a procedure (for example, carpool.xfr) to a directory outside of
SWDIR\util (for example, c:\\), run the following command:
SWDIR\bin\swutil EMPORT carpool c:\\
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
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, server names, etc. ) 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 upgrade.
See TIBCO iProcess Engine Installation for more information.
Create Log Files in a Rotational Manner (IPE-2613)
Log files, with the timestamp in the file name, are now created every day to record
the sw_warn, sw_error, swentobjsv, and swentobjsvUA messages separately. For
example: sw_warn20110831,sw_error20110831,swentobjsv20110831, and
swentobjsvUA20110831.
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.
TIBCO iProcess Engine Release Notes
New Features 5
|
Pass Complete Arrays Into and out of Sub-procedures (IPE-2535)
Complete arrays can be passed into and out of sub-procedures. The following
example shows how to pass complete arrays into and out of sub-procedures.
To pass complete arrays into and out of sub-procedures, do as follows:
1. Prepare the MAINA main procedure embedded with the SUBNA
sub-procedure:
— the steps of MAINA and SUBNA are defined with Array fields, for
example, TEX, INT, NUM, DAT, TIM, MEM , and COM.
— the steps of MAINA and SUBNA are defined with the SW_GEN_IDX field.
— the input and output mappings for case data are defined.
See TIBCO iProcess Modeler Advanced Design for more information.
2. Open the main procedure in TIBCO iProcess Modeler, double-click the
sub-procedure to open the Sub-Procedure Call Definition dialog.
3. Click the Input tab, and click the Pass Array field of the items (for example,
TEXIN, MEMIN) to select Pass Array.
4. Click the Output tab, and click the Pass Array field of the items (for example,
TEXOUT, MEMOUT) to select Pass Array, as shown in Figure 1.
TIBCO iProcess Engine Release Notes
6
|
Release Notes
Figure 1 Select Pass Array in Sub-Procedure Call Definition Dialog
5. Click the OK button to exit the Sub-Procedure Call Definition dialog.
6. Click the Case Start button, and fill in the Case Start dialog. Click the Start
button to start the case.
7. In the Form: dialog, type values for the Array fields, as shown in Table 3.
Table 3 Array Field Inputs from Main Procedure to Sub-procedure
SW_GEN_IDX
TEX Field
MEM Field
0
a1
q1
1
a2
q2
2
a3
q3
Figure 2 shows the Form: dialog when entering 2 in the SW_GEN_IDX field.
TIBCO iProcess Engine Release Notes
New Features 7
|
Figure 2 Inputs of the Main Procedure
Click the Release button to continue the case.
8. Double-click the work item in the list to check the case data passed into the
sub-procedure, as shown in the Figure 3.
Figure 3 Results of Passing Complete Array into Sub-procedure
The complete arrays are passed into the sub-procedure.
TIBCO iProcess Engine Release Notes
8
|
Release Notes
Type 1 in the SW_GEN_IDX field, the TEX field value changes to a2, and the
MEM field value changes to q2. Type 2 in the SW_GEN_IDX field, the TEX
field value changes to a3, and the MEM field value changes to q3.
9. Update the Array fields values, as shown in Table 4.
Table 4 Array Field Inputs from Sub-Procedure to Main Procedure
SW_GEN_IDX
TEX Field
MEM Field
0
sa1
sq1
1
sa2
sq2
2
sa3
sq3
Click the Release button to pass the arrays from the sub-procedure to the
main procedure.
10. Double-click the work item in the list to check the case data passed into the
main procedure, as shown in the Figure 4.
Figure 4 Results of Passing Complete Array into Main Procedure
The complete arrays are passed into the main procedure.
TIBCO iProcess Engine Release Notes
New Features 9
|
Type 1 in the SW_GEN_IDX field, the TEX field value changes to sa2, and the
MEM field value changes to sq2. Type 2 in the SW_GEN_IDX field, the TEX
field value changes to sa3, and the MEM field value changes to sq3.
When a single field in a sub-procedure is mapped to an array field in a main
procedure and you select Pass Array in the Output tab, the field in the
sub-procedure returns nothing to the array field in the main procedure. This is
because selecting Pass Array causes the non-array data to be discarded.
If you select Pass Array in the Output tab for a dynamic sub-call, the last returned
array will overwrite all the previous arrays returned from the sub-procedure.
This feature is also supported in TIBCO Business Studio - BPM Edition 3.5.2 with
TIBCO Business Studio - iProcess Add-in 3.5.0. See TIBCO Business Studio - BPM
Edition documentation and TIBCO Business Studio - iProcess Add-in
documentation for more information.
Prioritizing the Work Performed by Background Processes (IPE-2480)
You can now set priorities ranging from 1 to 999 (where 1 is the highest priority)
for internal message queues when passing messages between iProcess processes
such as from the background and the WISes, or from SSO Lite to the background.
Its default value is 50.
The messages with higher internal message queue priorities are processed earlier
than those with lower priorities, and the message with the highest priority will
automatically be the next message processed, even if there is a backlog in the
queue.
If the internal message queue priorities are not set, the messages will be processed
in the order of SW_CP_ VALUE or SW_IP_VALUE when using iProcess
Workspace (Windows) to process work items.
For example, if a case sets its value for SW_CP_ VALUE to 25, then all the
messages for that case being sent around the system will have a value of 25, and
automatically be processed before any messages with the default value 50. The
value of SW_IP_VALUE is only valid while a work item is in a queue. If priority
escalation is enabled, SW_IP_VALUE can increase while in the queue. When a
work item is released if SW_IP_VALUE has changed, it will be used to set the
priority for the release from the queue (but only once for that operation). After
that, the case priority SW_CP_VALUE will then continue to be used. To propagate
that value to subsequent messages, a release script which copies the value of
SW_IP_VALUE into the field SW_CP_VALUE can keep the case running at the
new priority level.
TIBCO iProcess Engine Release Notes
10
|
Release Notes
See TIBCO iProcess Modeler - Advanced Design for more information about SW_CP_
VALUE or SW_IP_VALUE.
If the internal message queue priorities are set, the messages will be processed in
the order of message queue priorities no matter the work item priority.
To set the internal message queue priorities, do as follows:
•
From SSO LITE, run the following commands:
— run SW_SET_PRIORITY to set the internal message queue priorities. For
example: CALL swpro.sw_set_priority(90);
— run SW_UNSET_PRIORITY to restore the default message queue priorities.
•
•
From SWBATCH, run the following commands:
—
START [-r|-u|-m|-vX.Y|-sN] [-c] [-e|-a[D] datafile] [-P
priority] <node|-> <procname> <stepname|-> <casedesc>
—
EVENT [-e[p][r|R]|-a[D][p][r|R] datafile] [-P priority]
<node|-> <procname> [-]<casenum> <eventname>
—
CLOSE [-P priority] <node|-> <procname> <caselist>
—
PURGE [-P priority] <node|-> <procname>
<caselist|ALL_CASES|dd_mm_yyyy>
From Utilities, run the following commands:
—
CSTART [-r|-u|-m|-vX.Y|-sN] [-c] [-V] [short procedure name]
[case description] [start step] [-P priority]
—
DCSTART [-r|-u|-m|-vX.Y|-sN] [-c] [-V] [short procedure name]
[case description] [data file] [start step] [-P priority]
—
EVENT [-hostnode] procedure-name [R]case-number event-name
[data-file] [-[p][r|R]] [-P priority]
—
RESEND procname queuename[@nodename]|ALL_QUEUES
[casenum|ALL_CASES [stepname|ALL_STEPS]] [-y] [-P priority]
—
PURGE procname <ALL_CASES|case_list|DD_MM_YYYY> [-y] [-P
priority]
—
CLOSE procname <case_list> [-y] [-P priority]
Bulk Operations for SSO Lite (IPE-2423)
Support for bulk operations has been added by adding the SW_SET_MBOX and
SW_UNSET_MBOX procedures.
The SW_SET_MBOX procedure can tell SSO Lite to use a different MBOX SET for
bulk purges or bulk case starts, and can still use the other MBOX SET for normal
operations such as delayed releases.
The SW_UNSET_MBOX procedure can be called to restore using the default
MBOX SET for all operations.
The following example shows how to set another MBOX SET for bulk operations:
TIBCO iProcess Engine Release Notes
New Features 11
|
1. Create the swpro.sw_db_bgqueue_3 and swpro.sw_db_bgqueue_4 queue
tables in the database.
2. Run SWDIR\util\swadm
add_queue BGMBOX3 Local
0003:swpro.sw_db_bgqueue_3
to add the BGMBOX3 queue to the IQL
Queue Table.
3. Run SWDIR\util\swadm
add_queue BGMBOX4 Local
0003:swpro.sw_db_bgqueue_4to
add the BGMBOX4 queue to the IQL
Queue Table.
4. Run SWDIR\util\swadm
SET to the mbox_set table.
add_mboxset BGMBSETB Local
5. Run SWDIR\util\swadm
MBOXID.
show_mboxsets v
6. Run SWDIR\util\swadm
show_queues
7. Run SWDIR\util\swadm
the queues to MBOX.
add_queue_to_mboxset MBOXID queueID
to add a MBOX
to view the BGMBSETB
to view the queueID.
to add
8. Call swpro.SW_SET_MBOX to set to use another MBOX SET for bulk cases start.
9. Call swpro.SW_CASESTART to start the bulk cases.
10. Call swpro.SW_UNSET_MBOX to restore using the default MBOX SET.
Enable RPC Blocking From iProcess Workspace (Windows) (IPE-2348)
iProcess Workspace (Windows) can be prevented from accessing iProcess Engine
by setting the RPC_BLOCK attribute to 1.
To set the RPC_BLOCK attribute to 1, from a command line window, run
SWDIR\util\swadm SET_ATTRIBUTES 0 ALL 0 RPC_BLOCK 1.
To enable iProcess Workspace (Windows) to access iProcess Engine, run one of the
following commands from a command line window:
•
SWDIR\util\swadm
SET_ATTRIBUTES 0 ALL 0 RPC_BLOCK 0
•
SWDIR\util\swadm
DELETE SET_ATTRIBUTES 0 ALL 0 RPC_BLOCK
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 was processed.
In this release, the timestamps in the AUDIT_TRAIL table record when the actual
RELEASE actions of the instruction are carried out.
TIBCO iProcess Engine Release Notes
12
|
Release Notes
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 to a deleted user after
the user has been deleted, will be delivered to the undelivered queue.
The following two process attributes are introduced to redirect the deleted user’s
work items:
•
BG_LEAVER_SUPER_AS_DEST
•
BG_LEAVER_DESTINATION
BG_LEAVER_SUPER_AS_DEST
The default value of the BG_LEAVER_SUPER_AS_DEST attribute is 1.
When the BG_LEAVER_SUPER_AS_DEST attribute is set to 1, the deleted user’s
work items are redirected to the first supervisor’s queue.
When the BG_LEAVER_SUPER_AS_DEST attribute is set to 0, the deleted user’s
work items are redirected to the destination queue specified by
BG_LEAVER_DESTINATION.
BG_LEAVER_DESTINATION
When the BG_LEAVER_SUPER_AS_DEST attribute is set to 0, and the
BG_LEAVER_DESTINATION is set to a destination (for example, user_test), the
deleted user’s work items are redirected to the user_test’s queue.
When the BG_LEAVER_SUPER_AS_DEST attribute is set to 0, and the
BG_LEAVER_DESTINATION is not set, the deleted user’s work items are
redirected to the admin user’s queue.
How to redirect the deleted user’s work items
To redirect the deleted user’s work items to the first supervisor’s queue:
1. Set the BG_LEAVER_SUPER_AS_DEST attribute to 1 by running the
following command:
SWDIR\util\swadm
set_attribute 1 BG 0 BG_LEAVER_SUPER_AS_DEST 1
To redirect the deleted user’s work items to the user-specified queue (for example,
user_test):
1. Set the BG_LEAVER_SUPER_AS_DEST attribute to 0 by running the
following command:
SWDIR\util\swadm
TIBCO iProcess Engine Release Notes
set_attribute 1 BG 0 BG_LEAVER_SUPER_AS_DEST 0
New Features 13
|
2. Set the BG_LEAVER_DESTINATION attribute to a by running the following
command:
SWDIR\util\swadm
user_test
set_attribute 1 BG 0 BG_LEAVER_DESTINATION
To redirect the deleted user’s work items to the admin user’s queue:
1. Set the BG_LEAVER_SUPER_AS_DEST attribute to 0 by running the
following command:
SWDIR\util\swadm
set_attribute 1 BG 0 BG_LEAVER_SUPER_AS_DEST 0
When a user is deleted, an entry is inserted into the leavers table, and a
corresponding entry is also inserted into the redir_defn table. These records will
be removed automatically when the following conditions are met:
•
All the work items of the deleted user are redirected.
•
The period specified by WQS_LEAVER_PERIOD expires.
Note: WQS_LEAVER_PERIOD is set by minutes and its default value is 60.
•
Perform a movesysinfo request or iProcess Engine is shut down.
Note: When iProcess Engine starts up, the timestamp column for all records in
the leavers table are updated to the current time.
If the records in the leavers table and the redir_defin table are not removed, they
will be removed when the deleted user is added into iProcess Engine again.
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.
iProcess Engine Startup Performance Improvements (IPE-2552, IPE-2558, IPE-2563)
iProcess Engine startup performance has been significantly improved due to the
iProcess Objects Server startup performance improvements, as shown in the
following two aspects:
•
iProcess Objects Server is started with WIS together, moving up in the startup
order.
•
higher speed to load users and groups.
TIBCO iProcess Engine Release Notes
14
|
Release Notes
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 that 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 running the following command:
swadm set_attribute 1 RPC_TCP_LI 1 MIGRATE_LIVE_CASES 1
Case migration is not supported by TIBCO Business Studio currently.
•
migrate only live cases from swutil by running the following command:
swutil PROC RELEASE
procname version comment
Release 11.1.3
There are no new features in this release.
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 - IBM AIX
TIBCO iProcess Engine now supports IBM AIX 6.1.
TIBCO iProcess Engine Release Notes
-m LIVE
New Features 15
|
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.
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 - Red Hat Linux
TIBCO iProcess Engine now supports Red Hat Enterprise Linux versions 5.x AS
and 5.x ES. For more information, see TIBCO iProcess Engine Installation.
Additional Database Support - DB2
TIBCO iProcess Engine now supports DB2 Universal Database 9.5. For more
information, see TIBCO iProcess Engine Installation.
TIBCO iProcess Engine Release Notes
16
|
Release Notes
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 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.
TIBCO iProcess Engine Release Notes
New Features 17
|
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>
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.
TIBCO iProcess Engine Release Notes
18
|
Release Notes
Release 11.0.2
The following are new features in this release.
Batching of RPC Calls (MR 37966)
A new process attribute RPC_SVR_CONTROL has been introduced to allow the
batching together of RPC calls. For further information on process attributes, see
the TIBCO iProcess Administrator’s Guide.
Batching of New Item Requests (MR 38005)
A new process attribute WIS_NEW_ITEM_BATCH_SIZE has been introduced to
batch up new item requests in the WIS so more can be done for a single write lock.
For further information on process attributes, see the TIBCO iProcess
Administrator’s Guide.
Disable Priority Escalation in the WIS Process (MR 38011)
A new process attribute WIS_USE_PRIORITY_ESCALATION has been
introduced to enable the disabling of priority escalation in the WIS process. For
further information on process attributes, see the TIBCO iProcess Administrator’s
Guide.
Configure RPC Call Stats Within WQS Process (MR 38050)
A new process attribute WQS_GATHER_RPC_STATS has been introduced to
allow the gathering of RPC call stats within the WQS process to be configurable.
For further information on process attributes, see the TIBCO iProcess
Administrator’s Guide.
TIBCO iProcess Engine Release Notes
New Features 19
|
Release 11.0.0
The following are new features in this release.
New User Validation Utility for LDAP (MR 33198)
LDAP is now provided with an integral User Validation utility, so that you do not
have to write any code to use an existing LDAP provider as the user validation
mechanism for the TIBCO iProcess Engine.
See LDAPCONF Utility User’s Guide for more information.
Work Queue Delta Publication via JMS (MR 32636)
Work Queue deltas can now be published to a JMS topic, using the existing
IAPJMS process. For more information, see the TIBCO iProcess Engine
Administrator's Guide and the TIBCO iProcess Engine Architecture Guide.
Workspace (Browser) User Settings (MR 32557)
It is now possible to save user settings from the iProcess Workspace (Browser) on
the iProcess Engine server, rather than just storing them on the browser machine.
This enables a user to keep the same settings when working on any machine. See
the TIBCO iProcess Engine (DB2) Administrator’s Guide for details.
Message Formats (MR 32436)
The format of sw_error and sw_warn messages has been enhanced to include:
- Milliseconds in the timestamp
- Case number and step number where appropriate
See "Format of Message Descriptions" in the TIBCO iProcess Engine System
Messages Guide.
Advanced Queue Management (MR 32435)
New functionality has been introduced to improve the handling of message
queues, enabling you to count the messages in a given queue, display header or
detail information, delete messages or move them from one queue to another. You
can now use the iProcess Server Manager to administer message queues.
The swadm_show_messages command has been enhanced, and the following
swadm commands have been added:
swadm count_messages
swadm detail_message
TIBCO iProcess Engine Release Notes
20
|
Release Notes
swadm move_messages
swadm delete_messages
New programming interfaces for integration with TIBCO Hawk have also been
provided.
For further details see the TIBCO iProcess Engine Administrator's Guide.
New SSOLITE stored procedure (MR 32241)
A new SSOLite stored procedure has been introduced.
SW_EVENT_UPDATE_PACK is the same as the existing SW_EVENT procedure
but has an option to refresh the data for any outstanding work items. See the
"SSOLITE Stored Procedures” appendix in the TIBCO iProcess Engine (DB2)
Administrator’s Guide.
Supported Java Versions
The iProcess Engine version 11 is delivered with Java Version 1.5 and has also
been tested against Java Version 1.6. See the appropriate TIBCO iProcess Engine
Installation guide for details.
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 21
|
Deprecated Features
This section describes deprecated features and lists equivalent features that
accomplish the same result, if relevant. Any use of a deprecated feature should be
discontinued as it may be removed in a future release. You should avoid
becoming dependent on deprecated features and become familiar with the
equivalent feature.
Release 11.3.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.
Release 11.0.0
No features are deprecated in this release.
TIBCO iProcess Engine Release Notes
22
|
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.3.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 10.6.1
TIBCO iProcess® Technology Plug-ins
Version 11.2.0
If you have any queries regarding product compatibility with this version of the
iProcess Engine, please contact TIBCO Support for further assistance.
TIBCO iProcess Engine Release Notes
Change History 23
|
Change History
The following Modification Requests (MRs) have been implemented since the
initial release of TIBCO iProcess Engine.
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 SSO Lite stored procedures.
MR 43545
Implemented. See Reopen Cases via SSO Lite Stored Procedures (IPE-1579) on
page 3.
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 3.
IPE-1602
Include MailID in output messages from IAPJMS.
MR 43607
Implemented. See Include MailID in Output Messages From IAPJMS (IPE-1602) on
page 2.
IPE-1603
Publish step description or extended step description.
MR 43610
Implemented. See Publish Step Description or Extended Step Description
(IPE-1603) on page 2.
TIBCO iProcess Engine Release Notes
24
|
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 3.
IPE-2013
Expand the plist
-p
command to identify procedure templates.
Implemented. See plist -p Identifies Procedure Templates (IPE-2013) on page 3.
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-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 4.
IPE-2257
MR 11523
The swutil IMPORT and EXPORT commands are expanded to import and export
XFR files to a directory outside of SWDIR\util.
Implemented. See IMPORT and EXPORT XFR and XPDL Files to a Directory
Outside of SWDIR\util (IPE-2257) on page 4.
IPE-2258
Audit changes to case data.
Implemented. See Audit Changes to Case Data (IPE-2258) on page 2.
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.
TIBCO iProcess Engine Release Notes
Change History 25
|
Defect #
Description
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 4.
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 2.
IPE-2337
Provides a user the option of only migrating live cases.
Implemented. See Optionally Migrate Only Live Cases (IPE-2337) on page 14.
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-2347
(Parent JIRA
IPE-2338)
IPE-2348
The case data fields were not returned when an XPDL file was imported using the
SWUTIL IMPORTLIB command.
Corrected.
Add support to enable rpc blocking from iProcess Workspace (Windows).
Implemented. See Enable RPC Blocking From iProcess Workspace (Windows)
(IPE-2348) on page 11.
IPE-2357
(Parent JIRA
IPE-1402)
IPE-2359
(Parent JIRA
IPE-2349)
IPE-2361
(Parent JIRA
IPE-1522)
IPE-2363
(Parent JIRA
IPE-2002)
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 Data tab was blank in TIBCO iProcess Workspace (Browser), when using the
command to import an XPDL file into TIBCO iProcess Engine.
SWUTIL
Corrected.
TIBCO iProcess Engine Release Notes
26
|
Release Notes
Defect #
Description
IPE-2364
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.
(Parent JIRA
IPE-2336)
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.
IPE-2396
The upgrade script did not run correctly for TIBCO iProcess Engine 11.1.2.
(Parent JIRA
IPE-2393)
Corrected.
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.
TIBCO iProcess Engine Release Notes
mail
steps.
mail
steps.
Change History 27
|
Defect #
Description
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.
memo
field.
Implemented. See Bulk Operations for SSO Lite (IPE-2423) on page 10.
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)
IPE-2453
(Parent JIRA
IPE-1596)
IPE-2454
(Parent JIRA
IPE-2354)
IPE-2455
(Parent JIRA
IPE-2365)
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.
IAPJMS only published the changed values for OPEN/KEEP events, not all the
values.
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.
TIBCO iProcess Engine Release Notes
28
|
Release Notes
Defect #
Description
IPE-2459
When executing the procedure EAI_BW (delayed released) > EAI_SCRIPT >
EAI_BW (delayed released), the second step, EAI_BW (delayed released), was
executed twice.
(Parent JIRA
IPE-1606)
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.
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.
TIBCO iProcess Engine Release Notes
Change History 29
|
Defect #
Description
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
Date field to filter cases.
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 9.
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)
IPE-2483
(Parent JIRA
IPE-2277)
IAPJMS did not function correctly when moving an IAPJMS process from a master
machine to a slave machine.
Corrected.
The WIS process was occasionally crushed because uncached queues in WIS were
not thread-safe.
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.
TIBCO iProcess Engine Release Notes
30
|
Release Notes
Defect #
Description
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.
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.
TIBCO iProcess Engine Release Notes
Change History 31
|
Defect #
Description
IPE-2505
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.
(Parent JIRA
IPE-2329)
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)
IPE-2535
The field values were not updated when a subprocedure started through the GRAFT
step.
Corrected.
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 5.
IPE-2547
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 iProcess Engine Startup Performance Improvements (IPE-2552,
IPE-2558, IPE-2563) on page 13.
TIBCO iProcess Engine Release Notes
32
|
Release Notes
Defect #
Description
IPE-2558
Improve the performance of TIBCO iProcess Objects Server when checking queues.
Implemented. See iProcess Engine Startup Performance Improvements (IPE-2552,
IPE-2558, IPE-2563) on page 13.
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 12.
IPE-2563
Improve the performance of TIBCO iProcess Objects Server by moving it up in the
start-up order.
Implemented. See iProcess Engine Startup Performance Improvements (IPE-2552,
IPE-2558, IPE-2563) on page 13.
IPE-2581
(Parent JIRA
IPE-2536)
IPE-2603
(Parent JIRA
IPE-2667)
IPE-2604
The swbatch command utility crashed occasionally when running the swbatch
EVENT command with the -e option in the control file.
Corrected.
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 13.
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 4.
IPE-2619
The memo and attach fields for some steps were lost when importing an XPDL file
through TIBCO iProcess Workspace (Windows).
Corrected.
TIBCO iProcess Engine Release Notes
Change History 33
|
Defect #
Description
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 11.
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-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
34
|
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 35
|
Defect #
Description
IPE-2732
Make log files directory configurable.
Implemented. See Log Files Directory Is Configurable (IPE-2732) on page 14.
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-2242
A memory leak occurred on the TIBCO iProcess Objects Server when the work items
were unlocked.
MR 43587
Corrected.
IPE-2324
The WIS process lost work item deadlines under certain circumstances.
(Parent JIRA
IPE-987)
Corrected.
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.
TIBCO iProcess Engine Release Notes
36
|
Release Notes
Defect #
Description
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.
IPE-2354
Some improvements to input validation should be added in the TIBCO iProcess
Engine Server Manager.
Implemented.
IPE-2356
(Parent JIRA
IPE-1402)
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.
TIBCO iProcess Engine Release Notes
Change History 37
|
Defect #
Description
IPE-2358
STAFFIFC.EXE
(Parent JIRA
IPE-2349)
IPE-2360
(Parent JIRA
IPE-1522)
IPE-2362
(Parent JIRA
IPE-2336)
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-2388
The TIBCO iProcess Engine user could not log in to the TIBCO iProcess Workspace
(Browser) client for the second time.
Corrected.
IPE-2389
(Parent JIRA
IPE-1535)
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.
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.
TIBCO iProcess Engine Release Notes
38
|
Release Notes
Defect #
Description
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.
IPE-2414
Works through SSOLITE were not distributed evenly across the two queues in the
BG MBox Set.
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.
TIBCO iProcess Engine Release Notes
Change History 39
|
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
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.
TIBCO iProcess Engine Release Notes
40
|
Release Notes
Defect #
IPE-2271
Description
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.
IPE-2275
did not function correctly when moving an IAPJMS process from a MASTER
machine to a SLAVE machine.
IAPJMS
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.
TIBCO iProcess Engine Release Notes
Change History 41
|
Defect #
Description
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 43564
(Parent
MR 43442)
After importing the participation list, Work Queue Server (WQS) crashed when
executing the MOVESYSINFO function.
Corrected.
MR 43603
(Parent
MR 43497)
When using the SWUTIL command to import an XPDL file into TIBCO iProcess
Engine, the Data tab was blank in the Browser.
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.
MR 43284
The output XFR file was corrupted when exporting a sub-procedure template.
Corrected.
Corrected
Corrected.
Corrected.
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.
Corrected.
TIBCO iProcess Engine Release Notes
42
|
Release Notes
Defect #
Description
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.
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)
Corrected.
Corrected.
Corrected.
The WQS responded very slowly to clients for a long time when a lot of
records were being updated.
PARTICIPATION
Corrected.
MR 43316
(Parent
MR 42335)
The length of the req_id and casenum fields were not consistent in the TIBCO
iProcess Engine tables and SSOLite.
MR 43293
The memo data was not correct when setting an element of an array to NULL.
Corrected.
Corrected.
MR 43352
(Parent
MR 41904)
BG Instruction processed the eai_oracle step without a package name.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 43
|
Defect #
Description
MR 43354
The threads were suspended in WIS because the write lock was not unlocked.
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 39198
Searching cases using the sw_starteddate parameter did not work properly on
DB2.
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
44
|
Release Notes
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 43518
Performance was getting low when filtering the SW_PARAMn field.
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
Date field to filter cases.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 45
|
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 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.
MR 38713
did not change the version of the Dynamic Sub-Procedure
(DSP) parameter template referred by the DSP step and sub-procedure.
swutil EXPORTLIB
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.
TIBCO iProcess Engine Release Notes
46
|
Release Notes
Defect #
Description
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.
MR 41657
The RPC processes (RPC_UDP_LI, RPC_POOL, and RPC_TCP_LI) crashed on the
following platforms:
•
Red Hat Enterprise Linux 4 (x64)
•
Red Hat Enterprise Linux 5 (x64)
Corrected.
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 41714
(Parent
MR 41533)
Corrected.
Initially you did not need to get the write lock in the CCacheRec::LockItem()
function to check the lock.
Implemented.
TIBCO iProcess Engine Release Notes
Change History 47
|
Defect #
Description
MR 41715
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.
(Parent
MR 41529)
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 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
If the command SWUTIL EXPORT [sub-proc name] -E -a -c -e -l
was used to export the xfr file, then Pstaffer.exe crashed.
-m -r +t
-x -v -s
(Parent
MR 41810)
Corrected.
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.
TIBCO iProcess Engine Release Notes
48
|
Release Notes
Defect #
Description
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.
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 42405
A problem occurred when running the swinstall script in a directory other than
the one where the installation files were located.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 49
|
Defect #
Description
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 42639
Validated TIBCO iProcess Engine on Red Hat 5.x with SELinux enabled.
Implemented.
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.
ALL
did not upgrade the
Corrected.
TIBCO iProcess Engine Release Notes
50
|
Release Notes
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 42861
Corrected.
When installing TIBCO iProcess Engine 11.1.0 on LinuxRHEL5, the following error
message appeared:
The version of the OS you are running (
LinuxRHEL5 2.6.18-128.el5PAE ) is
not a validated platform
Corrected.
MR 42878
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)
The WIS failed to get the work item when the reqid value was greater than the
maximum of a 32-bit integer.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 51
|
Defect #
Description
MR 42889
The Dynamic Sub-Procedure (DSP) call error handling did not return any error
messages.
(Parent
MR 41268)
MR 42890
Corrected.
The EAIScript could not handle umlauts characters.
Corrected.
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)
Corrected.
MR 42920
The performance of TIBCO iProcess Engine was low on Solaris 10 (x86).
(Parent
MR 42131)
Corrected.
MR 42922
(Parent
MR 42443)
It was not possible to use LDAP for user validation for swadmin. Setting LDAP_UV to
worked for other validation, but not for swadmin.
1
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.
TIBCO iProcess Engine Release Notes
52
|
Release Notes
Defect #
Description
MR 42923
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.
(Parent
MR 42521)
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)
MR 42972
Corrected.
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.
TIBCO iProcess Engine Release Notes
Change History 53
|
Defect #
Description
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 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.
MR 32656
On Unix, SPO could not perform the password lookup function on the remote node
because the wrong RPC host was used.
Corrected.
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)
Certain filters did not work correctly on Red Hat Enterprise Linux 4 and AIX 5L
Version 5.3.
Corrected.
TIBCO iProcess Engine Release Notes
54
|
Release Notes
Defect #
Description
MR 43048
If a Case Data Queue Parameter (CDQP) was defined as swNumeric, it failed to
filter on TIBCO iProcess Workspace (Browser).
(Parent
MR 42130)
MR 43050
(Parent
MR 42971)
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.
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 43072
TIBCO iProcess Engine crashed when loading data from the proc_defn table.
(Parent
MR 41503)
Corrected.
MR 43083
When running the swutil
Corrected.
TIBCO iProcess Engine Release Notes
EXTCD
command, inconsistent results were returned.
Change History 55
|
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 41037
Cannot change password in TIBCO iProcess Workspace (Windows) when
connected to the TIBCO iProcess Engine running on Red Hat Enterprise Linux
version 5.2.
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.
MR 40846
Add new information for IAPJMS messages.
Implemented. See Extended Information for IAPJMS Messages (MR 40846) on
page 16.
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.
Corrected.
Corrected.
TIBCO iProcess Engine Release Notes
56
|
Release Notes
Defect #
Description
MR 40662
(Parent
MR 38992)
IAP messages are not generated when a null or empty string memo is published.
MR 40645
(Parent
MR 39504)
The sal_refresh_login function does not work.
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.
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.
MR 40249
The WIS process can crash following performance issues with processing duplicate
REQUEST instructions from the wismbd, if wismbd has to retry.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 57
|
Defect #
Description
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
58
|
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 38280
(Parent
MR 36604)
A call of SQLSetConnectAttr could return SQL_SUCCESS_WITH_INFO. This
should be treated as success instead of failure.
Corrected.
Corrected.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 59
|
Defect #
Description
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.
MR 38293
(Parent
MR 36914)
When using SW_PRIORITY for work item filtering, all work items are returned.
MR 38295
(Parent
MR 36663)
The WIS can fail to add a new workitem to a queue if DB2 is shutdown and
restarted while the WIS is left running.
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.
Corrected.
TIBCO iProcess Engine Release Notes
60
|
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 61
|
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 15.
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
62
|
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 63
|
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
64
|
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 65
|
Release 11.0.2
Defect #
Description
MR 37696
Changes made to improve performance of WIS process.
MR 37825
(Parent
MR 37780)
Enable the FIL's procedure definition cache (PDC) in the iProcess Objects Server.
The PDC is used on startup but is shut down when startup is completed.
MR 37826
(Parent
MR 36774)
If two items are released via the Action Processor using a single ReleaseItems call,
and one item includes a memo field, the second item fails to be released and the
iProcess Objects Server crashes.
Implemented. The PDC is now shut down only when the iProcess Objects Server
process is disabled.
Corrected.
MR 37840
Change to use the native compilers, cc and aCC, on HP-UX 11 to improve
performance.
Implemented.
MR 37966
Modify RPC layer to use an interrupt socket and allow the batching together of RPC
calls.
Implemented. A new process attribute RPC_SVR_CONTROL has been introduced.
Permissible values in the form B[,<batch size>] are default, 0 or <n>, where <n> is
the number of items to be batched. The default value is 20. For example,
B = Set batch size to default (20)
B,0 = Turn off batching of RPC calls
B,10 = Set batch size to 10
Using this attribute reduces the overhead in processing RPC calls individually. Any
slight overhead in waiting for 20 (or the number specified) to be batched should not
be noticeable.
TIBCO iProcess Engine Release Notes
66
|
Release Notes
Defect #
Description
MR 38005
Batch up new item requests in the WIS so more can be done for a single write lock.
Implemented. A new process attribute WIS_NEW_ITEM_BATCH_SIZE has been
introduced.
Permissible values are 0 or <n>, with the default being 0, and where <n> is the
number of items to be batched to a maximum value of 500000.
0 = batching is not used.
<n> = batching is used.
If you have batching turned on and fewer items than the batch size value number of
items come into the queue, then the update thread, when it next wakes up, will
process any items batched up. Or, if another RPC request comes in to add a new
item that takes the batch size over the configured value, then all items will be
processed.
Using this attribute means that incoming items from the WISMDB are batched up
before the index is updated (similar to pre 10.3 versions). This reduces the load on
the system, but does mean that new items take longer to appear in the queue (by at
most the WIS_REFRESH_INDEX period of time).
MR 38011
Enable the disabling of priority escalation use in the WIS process.
Implemented. A new process attribute WIS_USE_PRIORITY_ESCALATION has
been introduced.
Permissible values are 0 or 1, with the default being 1.
0 = priority ageing will no longer be processed. Every item that is displayed
will use the default priority as set in the staffcfg file. Changes to priority fields
will not affect the current priority value of a work item.
1 = priority ageing will still function.
This attribute can be turned off for a small performance and CPU benefit. However,
you should only do this if you are not using the Priority escalation feature as
switching it off will prevent the priority value being automatically decremented. Be
careful to ensure you are not using this feature before disabling it.
MR 38104
(Parent
MR 37071)
The RPC_TCP_LI process hangs if the process being deployed contains document
section lines longer than 512 characters in the iProcess Modeler section.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 67
|
Defect #
Description
MR 38050
The gathering of RPC call stats within the WQS process should be configurable.
Implemented. A new process attribute WQS_GATHER_RPC_STATS has been
introduced.
Permissible values are 0 or 1, with the default being 0.
0 = RPC stats gathering is turned off.
1 = RPC stats gathering is turned on.
When the attribute is turned off and then on again, any previously gathered stats
are not retained.
To use the attribute, turn on R=2 debug on the WQS process, set the process
attribute and the stats will be seen in the debug log.
TIBCO recommend that this attribute be turned off unless you specifically require
these stats.
MR 38402
(Parent
MR 16771)
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 38455
Re-integration of MRs designed to improve the performance of the WIS and/or
WQS processes.
Implemented.
MR 38492
(Parent
MR 37326)
There is a memory leak in procmgr worker.
MR 38493
The procedure description is not updated on procedure import.
Corrected.
Corrected.
MR 38499
(Parent
MR 35523)
Errors are occurring due to parameter template procedures being included in the
audit procedure list.
MR 38848
The sub-procedure name array is lost when using swutil importlib.
Corrected.
Corrected.
TIBCO iProcess Engine Release Notes
68
|
Release Notes
Defect #
Description
MR 38849
swutil EXPORTLIB doesn't change the version of the DSP parameter template
referred by the DSP step and sub procedure.
Corrected.
MR 38851
The Background (BG) Processes did not handle deadlocks properly so transactions
are not rolled back and retried.
Corrected.
MR 38852
Database errors that occur when handling sub-cases should be propagated up to
make transactions fail.
Corrected.
MR 38853
The BG process will automatically lock all sub cases if the "update pack data" flag is
specified. This can lead to unnecessary deadlocks.
Corrected.
MR 38911
The Hawk microagent methods getmessageheader and getmessage detail don’t
work.
Corrected.
MR 39055
fixperms can fail to set file permissions and hence runcmd permissions do not get
added to the rootscript after a non-root install if the runcmd file is owned by pro.
Corrected.
MR 39092
The version of jre should be upgraded to version 1.6.0_12 where possible.
Implemented. See TIBCO iProcess Engine Installation for specific version
information.
MR 39299
(Parent
MR 39269)
plist -w can terminate prematurely if next deadline is not initialized in WQS shared
memory.
MR 39456
TIBCO EMS is no longer distributed with TIBCO iProcess Engine.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 69
|
Release 11.0.1
Defect #
Description
MR 36105
WIS process can crash while caching queues if work items have more than 500 bytes
of Case Data Queue Parameter (CDQP) data.
Corrected.
MR 35993
The iProcess Engine background gives an error when trying to purge cases.
Corrected.
MR 35987
Thread locking problem found in WIS process when accessing Case Data Queue
Parameter (CDQP) field values.
Corrected.
MR 35915
Case fails to run for a dynamic sub-procedure when deployed or exported from
TIBCO Business Studio™.
Corrected.
MR 35842
Deploying an independent Sub-Process Task that references a sub-process in a
different xpdl package loses the sub-process reference in iProcess.
Corrected.
MR 35836
Update the version of TIBCO Rendezvous to 8.1.1 and TIBCO Hawk to 4.8.1.
Implemented.
TIBCO iProcess Engine Release Notes
70
|
Release Notes
Release 11.0.0
Defect #
Description
MR 35178
When running silent install on a UNIX server, the install stops if it is not a validated
platform and an error message is received.
Corrected. The install will now skip the platform validation and display a
non-interactive warning message.
MR 35148
When upgrading on a UNIX server the upgrade fails to get the current swentobjsv
version.
Corrected.
MR 34681
If an iProcess Objects process crashes, it can cause the process sentinels to hang.
Corrected.
MR 34671
(Parent
MR 33387)
Cannot call TIBCO Rendezvous from iProcess Java Plug-in steps.
MR 34627
Update the version of TIBCO EMS to 4.4.3, TIBCO Rendezvous to 8.1.0 and TIBCO
Hawk to 4.8.0.
Corrected.
Implemented.
MR 34622
Serverrun should export DB2 environment variables to the process that it is running
so that it can access DB2.
Corrected.
MR 34520
LDAP entries that have invalid menu names are being synchronized to iProcess
Engine when they should be ignored.
Corrected.
MR 34476
If you create a silent install script and then run swinstall <script> the install
completes but the iProcess Objects server and directory are not installed. No seo
directory is created, hence iProcess Objects cannot run when the server starts.
Corrected
MR 34451
An invalid year (prior to 1900) in a script causes the BG process to hang.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 71
|
Defect #
Description
MR 34404
If you have a date or time field with a value of SW_NA, it will be corrupted when
passed from a sub-procedure to the main procedure.
Corrected.
MR 34340
Expression syntax checking is failing in some areas, specifically assignment of
variable type values to numeric fields or numeric values to variable type fields.
Corrected.
MR 34226
Cannot deploy a process with Dynamic Sub-Procedure Step or Graft Step that either
has no input mappings OR has no output mappings.
Corrected.
MR 34152
(Parent
MR 32557)
MR 34142
Add support for saving user settings from the iProcess Workspace (Browser) on the
iProcess Engine.
Implemented. See Workspace (Browser) User Settings (MR 32557) on page 19 for
more information.
Jumpto with a specific sub-procedure step is not working. Also, dynamic
sub-procedure is not started when EVENT updates the data (and sub procedure
does not exist).
Corrected.
MR 33970
newmon debug message files need to be in SWDIR/bin as well as SWDIR/util for
swentobjsv/SPO (q1newmon.msg & x1newmon.msg).
Corrected.
MR 33941
Enhance deployment SDK versioning of I/O template to allow templates to be
independently deployed.
Implemented.
MR 33877
(Parent
MR 32995)
When upgrading to an iProcess Engine Version v11.0 the server_minvers table is not
updated. This means a $SWDIR/util/plist -n returns the wrong values.
MR 33864
"Save as XPDL" omits Roles when there is also a user associated with the User Step.
Corrected.
Corrected.
MR 33838
iProcess Objects can crash with a memory allocation error.
Corrected.
TIBCO iProcess Engine Release Notes
72
|
Release Notes
Defect #
Description
MR 33806
(Parent
MR 33791)
If you attempt to withdraw an EAIORCH type step, then the BG will fail to process
the transaction.
MR 33652
Build iProcess Engine version 11.0 with TIBCO EMS version 4.4.2.
Corrected.
Implemented.
MR 33388
(Parent
MR 33406)
When setting up a connection to IAP from the BG process, the IP is set to 0 rather
than the correct IP of the machine hosting the IAPJMS process.
MR 33385
(Parent
MR 33102)
In a clustered system, shutting down one node at a time using, for example,
"swsvrmgr shutdown 1" or "swsvrmgr shutdown 2", does not work.
MR 33384
(Parent
MR 33082)
"swsvrmgr start 1 bg" will timeout if some of the BG processes are already running.
MR 33382
(Parent
MR 33082)
Cannot shutdown iProcess Objects processes on master node if iProcess Objects is
running on a slave node.
MR 33381
(Parent
MR 33028)
Generate sw_warn message when limit of number of WQS sessions is being
approached.
MR 33380
(Parent
MR 32638)
ioctl call from get_myaddress can fail on HP causing RPC processes to crash.
Corrected.
Corrected.
Corrected.
Corrected.
Implemented. The default threshold is 70% of the limit (which can be configured
using the WQS_SESSION_THRESHOLD process attribute which should be set to
the percentage, for example, "70"). 5 equally spaced further thresholds are created at
which warnings are generated. So for example if the threshold is set to 50 then
warnings are generated whenever the number of sessions rises above 50%, 60%,
70%, 80% or 90%. An sw_error message is generated when the limit is reached. The
maximum threshold that can be set is 95% and the minimum is 1% - if the threshold
is set outside this range no warnings will be generated.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 73
|
Defect #
Description
MR 33378
(Parent
MR 32424)
The SAL user cache can consume large amounts of memory causing errors when it
runs out of memory.
MR 33375
(Parent
MR 33175)
SAL refresh one queue optimization only works for own queue
(sal_queue_getqueue_info32() with negative index).
MR 33296
When installing iProcess Engine, values are not being kept when you select 'Back'
and 'Next'.
Corrected.
Corrected.
Corrected.
MR 33198
There is a requirement to provide integrated UVAPI to LDAP, to enable the use of
existing LDAP entries as the user validation mechanism without having to write
additional code.
Implemented. See LDAPCONF Utility User’s Guide for more information.
MR 33182
If you login to iProcess Workspace (Browser) with an expired password it isn't
detected and logs you in.
Corrected. Expired passwords are now detected.
MR 33126
Need to enhance password checking to allow new (and more secure) encryption
methods to be used.
Implemented
MR 33049
Enhance deployment SDK to provide versioning of I/O template.
Implemented.
MR 33010
Extend the iProcess eMail Plug-In to include support for the configuration of more
than one SMTP server.
Implemented. See TIBCO iProcess Email Plug-in User’s Guide for more information.
MR 33004
(Parent
MR 32486)
The TIBCO iProcess Java Plug-in fails to start because the iProcess Engine is
installed with the wrong version of Java.
MR 33002
(Parent
MR 32375)
Cannot install server if user running install has a '-' in name.
Corrected.
Corrected.
TIBCO iProcess Engine Release Notes
74
|
Release Notes
Defect #
Description
MR 32953
(Parent
MR 32214)
Using a combination of Cache on Demand and EVENT -p can cause problems.
MR 32684
(Parent
MR 17750)
On DB2, the SSOLite stored procedure SW_SUSPEND is missing a call to
SW_INIT_TABLES.
MR 32636
Need the ability to publish Work Queue deltas to a JMS topic.
Corrected.
Corrected.
Implemented. See Work Queue Delta Publication via JMS (MR 32636) on page 19 for
more information.
MR 32603
It is not possible to deploy a process to iProcess Engine as a Web Service Service
Task, yet you can when exporting to XPDL and import via iProcess Modeler.
Corrected.
MR 32562
(Parent
MR 32561)
If a work item is locked and the pack data is changed (through an event for
example) and an attempt is made to forward the item then iProcess Objects and/or
the iProcess Client (Windows) will crash.
Corrected.
MR 32557
Add support for saving user settings from the iProcess Workspace (Browser) on the
iProcess Engine.
Implemented. See Workspace (Browser) User Settings (MR 32557) on page 19 for
more information.
MR 32462
If a field is set to SW_NA by a script, the field is blanked but not set to SW_NA.
Corrected.
MR 32436
Add microseconds, case number, step name and procedure name information in
sw_error or sw_warn file.
Implemented. See Message Formats (MR 32436) on page 19 for more information.
MR 32435
Need to improve the handling of message queues, to provide ability to count the
messages in a given queue, display header or detail information, delete messages or
move them from one queue to another. See Advanced Queue Management
(MR 32435) on page 19 for more information.
Implemented.
TIBCO iProcess Engine Release Notes
Change History 75
|
Defect #
Description
MR 32241
Extend ssolite procedures to include the EVENT -p option. See TIBCO iProcess
Engine (DB2) Administrator’s Guide for more information.
Implemented. See Workspace (Browser) User Settings (MR 32557) on page 19 for
more information.
MR 32153
XPDL generated from iProcess Modeler which has a process with sub-procedure
calls doesn't save the sub-procedure name.
Corrected.
MR 31205
None of the system / user attribute fields are output by WRITEFIELDS when run
from iProcess Workspace (Windows). All the field values are left blank.
Corrected.
MR 26628
Recalculating deadlines using swutil EVENT does not work.
Corrected.
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
76
|
Release Notes
Restrictions
The table in this section lists known restrictions in this release.
Defect #
Summary/Workaround
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.
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 19520
This applies to the iProcess Engine (DB2) for Linux only
Summary When Setup reaches the Database Connection and Account Details
dialog, the password information for the database users is automatically filled
in. However, the dialog uses the default passwords, not the passwords that have
been set for the database users on the operating system.
Workaround You should reset these passwords to be the same as the passwords
set for the database users on the operating system.
TIBCO iProcess Engine Release Notes
Restrictions 77
|
Defect #
Summary/Workaround
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 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.
TIBCO iProcess Engine Release Notes
78
|
Release Notes
Defect #
Summary/Workaround
CR 18361
Summary Performance on AIX systems can be very slow when opening cases
from a queue.
Workaround If the SERVERRUN function is being used frequently in one or
many procedures, the $SWDIR/lib/fil.so file should be "pinned" into the AIX
Shared Memory, by ensuring that all users have read and execute permissions
on the file. To do this, use the command
chmod 555 $SWDIR/lib/fil.so
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.
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 17662
Summary If you use the same debug flag setting (1 to enable debug, 0 to disable
it) on consecutive calls to the SSOLite sw_set_debug() stored procedure, the call
returns an unclear error. The error message does not state that the call is trying to
set debug to the state that it is already in.
For example, if you call sw_set_debug(1) once to set debugging, the call
correctly returns 0 (success). If your next call to sw_set_debug() is also
sw_set_debug(1), the following error is returned:
SQL0601N The name of the object to be created is identical to
the existing name "SESSION.SSOLITE_DEBUG_DATA" of type
"DECLARED TEMPORARY TABLE".
SQLSTATE=42710
Similarly, if you call sw_set_debug(0) once to disable debugging, the call
correctly returns 0 (success). If your next call to sw_set_debug() is also
sw_set_debug(0), the following error is returned:
SQL0204N "SESSION.SSOLITE_DEBUG_DATA" is an undefined name.
SQLSTATE=42704
Workaround If you call sw_set_debug(1) and then call sw_set_debug(0), or
vice-versa, the calls behave correctly and return 0 (success).
TIBCO iProcess Engine Release Notes
Restrictions 79
|
Defect #
Summary/Workaround
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 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.
TIBCO iProcess Engine Release Notes
80
|
Release Notes
Defect #
Summary/Workaround
CR 16946
Summary The iProcess Engine uses the SHMKEY_ID process attribute value
when building the UNIX shared memory key that is allocated when the WQS
process is started. If a shared memory conflict occurs, resulting in the WQS
process being unable to start, you can change the SHMKEY_ID value to resolve
the problem.
However, changing the value of the SHMKEY_ID process attribute has no effect
in this version of the iProcess Engine. You cannot use SHMKEY_ID to resolve
shared memory conflicts.
Workaround See CR 16945 on page 80 for more information about alternative
ways of resolving shared memory conflicts.
CR 16945
Summary If the WQS process (or other iProcess Engine process) cannot obtain a
shared memory segment when the iProcess Engine attempts to start, startup
fails. Error messages 1974 and 1975 are written to the $SWDIR/logs/sw_error file
- for example:
2005/02/15 16:51:48(WQS:1:18218:1:swadmin:/wqsindex.c:7.21:566):
1974-Failed to get shared memory handle for WQSINDEX
2005/02/15 16:51:48(WQS:1:18218:1:swadmin:/wqsindex.c:7.21:677):
1975-WQS initialize failed, connected to shared memory for
Workaround For more information about how to resolve this problem, please
refer to the description of these errors in the iProcess Engine System Messages
Guide. Note that:
•
You can force the iProcess Engine to obtain a new shared memory key when
it starts up. To do this:
a. Move the /var/tmp/nodename directory (where nodename is the
nodename of this iProcess Engine) to another location on the same
physical partition of the file system - for example,
/var/tmp/old/nodename.
b. Restart the iProcess Engine. The iProcess Engine should obtain a
different shared memory key, allowing it to start successfully.
•
If you set debugging for the WQS process, the shmget call returns error code
22.
•
Changing the value of the SHMKEY_ID process attribute has no effect in this
iProcess Engine version. This is because of a current restriction in the
product - see CR 16946 on page 80 for more information.
TIBCO iProcess Engine Release Notes
Restrictions 81
|
Defect #
Summary/Workaround
CR 16924
Summary If the LD_LIBRARY_PATH environment variable contains Oracle
libraries as well as DB2 libraries, and the Oracle libraries are listed first, the
iProcess Engine will try to use the Oracle libraries instead of the DB2 ones. The
iProcess Engine will therefore fail to start on DB2.
Workaround To avoid this problem, make sure that the DB2 libraries are listed in
front of the Oracle libraries in LD_LIBRARY_PATH before you start the iProcess
Engine.
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
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 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
82
|
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 83
|
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
84
|
Release Notes
Defect #
Summary/Workaround
CR 12024
Summary Groups and attributes with names greater than 24 characters in length
will be ignored.
Workaround None
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 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
Known Issues 85
|
Known Issues
This section lists known issues in the current release.
Summary
Summary On SUSE Linux Enterprise 11, RPC portmapper service is started by
rpcbind by default, which causes TIBCO iProcess Engine to fail to start.
Workaround Switch to portmap to start RPC services by following these steps:
1. Run
/etc/init.d/rpcbind stop
to stop RPC services.
2. Get the portmap RPM installation file from SUSE Linux Enterprise 11
installation disk and install portmap.
3. Run /etc/init.d/portmap
start
to start RPC services.
Then, the iProcess Engine can start successfully.
Summary After installing TIBCO iProcess Engine on Red Hat 5 and enabling
for JBoss 4.2.1, the IAPJMS process fails to start up.
Workaround Follow these steps:
IAPJMS
1. Change the classpath.JBoss.base parameter in the
iapjms_classpath.properties file.
For example: classpath.JBoss.base=jbossall-client.jar
2. Restart TIBCO iProcess Engine.
Summary If IAPJMS has been configured for Weblogic 10.3 when installing
TIBCO iProcess Engine on Red Hat 5, the IAPJMS process is suspended after
starting TIBCO iProcess Engine.
Workaround Follow these steps:
1. Copy the wlfullclient.jar file to $WEBLOGIC_HOME/jar.
2. Modify the configuration for Weblogic in the
iapjms_classpath.properties file.
For example:
classpath.basedir.WL=$WEBLOGIC_HOME/jar
classpath.WL.base=wlfullclient.jar
3. Restart TIBCO iProcess Engine.
TIBCO iProcess Engine Release Notes
86
|
Release Notes
Summary
Summary After installing the Technology Plug-ins, the BG process cannot start
up while starting TIBCO iProcess Engine.
Workaround Follow these steps:
1. Modify the set_attributes.sh file.
Add $SWDIR/libs into the process attribute SWLIB_PATH for BG,
and PRCBG, and make sure $SWDIR/libs appears before
BGPREDICT,
/usr/lib.
For example:
/staffware/installations/staffw_nod1/util/swadm set_attribute
0 BG
0 SWLIB_PATH
/staffware/installations/staffw_nod1/libs:/staffware/installa
tions/staffw_nod1/java/bin/classic:/staffware/installations/s
taffw_nod1/java/bin:/usr/lib
/staffware/installations/staffw_nod1/util/swadm set_attribute
0 BGPREDICT 0 SWLIB_PATH
/staffware/installations/staffw_nod1/libs:/staffware/installa
tions/staffw_nod1/java/bin/classic:/staffware/installations/s
taffw_nod1/java/bin:/usr/lib
/staffware/installations/staffw_nod1/util/swadm set_attribute
0 RPCBG
0 SWLIB_PATH
/staffware/installations/staffw_nod1/libs:/staffware/installa
tions/staffw_nod1/java/bin/classic:/staffware/installations/s
taffw_nod1/java/bin:/usr/lib
2. Restart TIBCO iProcess Engine.
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.
TIBCO iProcess Engine Release Notes
Known Issues 87
|
Summary
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
88
|
Release Notes
Summary
Summary When installing TIBCO iProcess Engine on Linux Red Hat 5 with an
IBM DB2 database, an error occurs after setting SELinux to the enforcing status.
Workaround Manually set permission to the following files:
- libdb2.so.1
- libdb2.so.1
- libdb2osse.so.1
- libimf.so
For example:
- chcon -t texrel_shlib_t /usr/lib/libdb2.so.1
- chcon -t texrel_shlib_t /$DB2PATH/lib32/libdb2.so.1
- chcon -t texrel_shlib_t /$DB2PATH/lib32/libdb2osse.so.1
- chcon -t texrel_shlib_t /$DB2PATH/lib32/libimf.so
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.
TIBCO iProcess Engine Release Notes
Known Issues 89
|
Summary
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 Process failures occur when you use DB2 to validate passwords via
the TIBCO iProcess User Validation API.
If you are using the TIBCO iProcess User Validation API to validate passwords
against a DB2 database, iProcess Engine processes may crash on exit. If this
occurs, you will need to update your DB2 installation to incorporate a fix for
problem reference APAR IY75560.
TIBCO understand that this fix is expected to be available in FP11 for DB2.
However, you must contact IBM for accurate information about how to obtain
this fix.
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
90
|
Release Notes
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.
Clearing the sw_subscription_list Table
If you use the operating system kill command to terminate the (worker and
watcher) process sentinel processes, or if the iProcess Engine crashes, rows may
be left in the sw_subscription_list database table. This table is used by the
iProcess Engine event daemon (which is provided by the watcher process sentinel
process).
The following utilities use events, and use the sw_subscription_list database
table to determine whether or not they should initialize a connection to the event
daemon:
•
$SWDIR/bin/swutil (pstaffer and staffifc)
•
$SWDIR/util/swadm,
•
$SWDIR/util/swcdata
•
$SWDIR/util/sweaireg
If you try to use one of these utilities while the iProcess Engine is not running and
while the sw_subscription_list database table is not empty, the utility will
attempt to create an RPC connection to the watcher process. Because the watcher
process is not running:
•
the utility will hang and then timeout, and
•
error messages with message identifier 1903 may be written to the
$SWDIR/logs/sw_warn or $SWDIR/logs/sw_error file. For example:
Failed to connect to the RPC Event Daemon after n attempts.
SWRPCEV RPC Program Not Registered.
TIBCO iProcess Engine Release Notes
Other Information 91
|
To avoid this problem, you should manually clear the contents of the
sw_subscription_list database table before trying to use one of these utilities or
restarting the iProcess Engine.
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.
Product Re-branding
Further product re-branding was carried out in the 10.6.0 release, as follows:
•
TIBCO Staffware Process Suite™ was renamed TIBCO iProcess Suite™
•
TIBCO iProcess® Client (Windows) was renamed TIBCO iProcess® Workspace
(Windows)
•
TIBCO iProcess® Client (Browser) was renamed TIBCO iProcess® Workspace
(Browser)
The term "Staffware" was replaced by "iProcess".
You may still see references to Staffware and to the old product names within the
software and in some documentation.
TIBCO iProcess Engine Release Notes
92
|
Release Notes
TIBCO iProcess Engine Release Notes
TIBCO iProcess® Objects Server
for UNIX
Release Notes
Software Release 11.3.0
October 2011
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO iProcess, TIBCO iProcess Suite, TIBCO
Enterprise Message Service, TIBCO FormBuilder, and TIBCO General Interface are either registered trademarks
or trademarks of TIBCO Software Inc. in the United States and/or other countries.
EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 1999-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
viii
viii
viii
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2
3
3
3
4
4
4
4
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
TIBCO iProcess Server Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Number of File Descriptors per Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading from Earlier Version May Cause Error Messages in Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Must Normalize Case Data to View Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
8
8
Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
TIBCO iProcess Objects Server Release Notes
iv
| Contents
TIBCO iProcess Objects Server Release Notes
|v
Preface
TIBCO iProcess Objects Server receives requests for services or data from a client
application developed with either TIBCO iProcess Objects (COM, Java, or C++) or
TIBCO iProcess Server Objects (Java or .NET). It processes the request, then
makes the appropriate call to a TIBCO iProcess Engine to initiate the desired
service or obtain the desired information.
Topics
•
Typographical Conventions, page vi
•
Connecting with TIBCO Resources, page viii
TIBCO iProcess Objects Server Release Notes
vi
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention
Use
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.
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.
TIBCO iProcess Objects Server Release Notes
Preface vii
|
Table 1 General Typographical Conventions (Cont’d)
Convention
Use
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 Objects Server Release Notes
viii
| Connecting with TIBCO Resources
Connecting with TIBCO Resources
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and
resident experts, a place to share and access the collective experience of the
TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety
of resources. To register, go to http://www.tibcommunity.com.
How to Access All TIBCO Documentation
After you join TIBCOmmunity, you can access the documentation for all
supported product versions here:
http://docs.tibco.com/TibcoDoc
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, please
contact TIBCO Support as follows.
•
For an overview of TIBCO Support, and information about getting started
with TIBCO Support, visit this site:
http://www.tibco.com/services/support
•
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user
name, you can request one.
TIBCO iProcess Objects Server 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
•
Compatibility, page 6
•
Other Information, page 7
•
Closed Issues, page 9
•
Restrictions, page 16
•
Known Issues, page 17
TIBCO iProcess Objects Server Release Notes
2
|
Release Notes
New Features
This section lists features added since the last major (11.0.0) release of this
product.
Earlier Versions
For details of the changes implemented in earlier versions of the product, see the
readme file and release notes for that particular product release.
Release 11.3.0
The following are new features in this release:
Start Case Only If All Necessary Information Is Available (IPE-2191)
When users start a case via SSO java code with both aReleaseItem and
aValidateFields set to be true, and do not fill in all the required fields in the first
step, the case can’t be started and an error is reported.
In previous releases, if you did not fill in all the required fields in the form, the
step could not be released, but the case was started with an error reported.
Audit Changes to Case Data (IPE-2259)
When the case data is changed via 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 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 first set the
AUDIT_CASEDATA_CHANGED attribute to 1 by running swadm
set_attribute 1 SPO 0 AUDIT_CASEDATA_CHANGED 1.
A new audit message "133: Case data changed by USER" is generated to record
such changes to case data.
TIBCO iProcess Objects Server Release Notes
New Features 3
|
A New Case Start Interface and Instruction (IPE-2239)
A new case start SAL interface and instruction are introduced when a case is
started via SSO 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.
The CASESTARTRELEASE message is sent directly from the SPO server to BG.
BG processes the case start and immediately performs the actions for the first
step. By doing so, the load on WIS is reduced because the case start no longer
involves WIS at all.
iProcess Objects Server Startup Performance Improvements (IPE-2554, IPE-2562)
iProcess Objects Server startup performance has been improved significantly in
the following two aspects:
•
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-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 that has the same
permissions to access it as the original log files directory.
Release 11.1.3
There are no new features in this release.
Release 11.1.2
There are no new features in this release.
Release 11.1.1
There are no new features in this release.
TIBCO iProcess Objects Server Release Notes
4
|
Release Notes
Release 11.1.0
There are no new features in this release.
Release 11.0.2
Solaris on x86 and x64 Systems Now Supported (MR 39282)
TIBCO iProcess Objects Server can now be used on x86 and x64 machines running
Solaris v10.
Release 11.0.1
SAL Session Wait Timeout Configuration Parameter Added (MR 35652)
A new SALWaitTimeout configuration parameter has been added to the server's
file. This new parameter specifies, in milliseconds, the amount
of time the server will wait for an SAL session to become free before returning an
error to the client. The default value for SALWaitTimeout is 60000 milliseconds (60
seconds).
swentobjsv.cfg
If the server times out waiting for the SAL session to return, it returns an
ER_ACQUIRE error (-158 - "error acquiring a user's mutex and SAL session") to
the client. It also writes the following to the log file:
"process_msg: acquire_user (user) timed out (-158)"
where process_msg is the name of the function where the timeout occurred, and
user is the name of the user that timed out trying to get an SAL session.
Release 11.0.0
Work Queue Deltas via a Subscription to a JMS Topic Support Added (MR 33057)
Client applications can now obtain work queue deltas via a subscription to a JMS
topic. This functionality was added to iProcess Server Objects in MR 33058.
The iProcess Objects Server has been updated to support this new functionality
on clients.
TIBCO iProcess Objects Server Release Notes
New Features 5
|
User Preference Support Added (MR 32557)
Client applications can now set, receive, and delete user preference data as a text
string in the iProcess Engine database. This functionality was added to iProcess
Server Objects in MR 32433.
iProcess Objects Server has been updated to support this new functionality on
clients.
TIBCO iProcess Objects Server Release Notes
6
|
Release Notes
Compatibility
TIBCO iProcess Server Objects
Only TIBCO iProcess Server Objects version 11.x can be used with this release.
TIBCO iProcess Objects Server Release Notes
Other Information 7
|
Other Information
Number of File Descriptors per Process
The TIBCO iProcess Engine must be started with a sufficient number of available
file descriptors per process based upon the number of users. This is specified in
the iProcess Objects Server using the NumFiles configuration parameter.
It is very difficult to know exactly how many files per user will be needed for the
iProcess Objects Server since this number will vary depending on a number of
factors that are unique to each site’s procedures and transactions. The number of
files could be as low as 4 files per user, but would not likely go above 12 files per
user in a standard configuration. In addition, the iProcess Objects Server will use
up to an additional 50 files independent of the number of users. Based on 1,000
users, the iProcess Objects Server would open somewhere from 4,050 to 10,150
files.
When the iProcess Objects Server is started, it attempts to set the number of files
from the default number to the maximum number allowed. The default value can
be displayed with the ulimit -n or ulimit -Sn commands ("S" indicating the
"soft" or default limit). The maximum value can be displayed with the ulimit
-Hn command ("H" indicating the "hard" or maximum limit).
The following formula can be used as a guideline to determine the number of file
descriptors you need:
(12 * Number of users) + 100
For a default configuration, the default number of users is 1024, which means the
upper file limit should be 12388 ((12 * 1024) + 100).
The TIBCO iProcess Engine must be started by the background user (which
defaults to "pro") , but only the superuser ("root") can increase the maximum
ulimits. If the current per process maximum file limit is less than the number
needed, either the number of open files per process will have to be raised for the
entire system, or the root user can start a shell, increase the file limits for that shell,
and then "su" to the background user. (The name of the background user is listed
on the second line of the $SWDIR/swdefs file.)
It is highly recommended that the file limit be set as high as possible since the
iProcess Objects Server will immediately exit if there are no more file descriptors
available. Running the command ulimit -n unlimited will set the file limit to
the operating system design limits. This command will only be successful if the
system limits allow this.
TIBCO iProcess Objects Server Release Notes
8
|
Release Notes
Upgrading from Earlier Version May Cause Error Messages in Log File
Upgrading from an earlier version of the iProcess Objects Server to version i10.0
(0.0) or later may cause error messages similar to the following to appear in the
iProcess Objects Server 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.
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.
TIBCO iProcess Objects Server Release Notes
Closed Issues 9
|
Closed Issues
The table in this section lists issues that were closed in the named releases.
Closed in
Release
MR #
Summary
11.3.0
IPE-2733
The Log Files directory is now configurable.
Implemented. See Log Files Directory Is Configurable (IPE-2733) on
page 3.
11.3.0
11.3.0
IPE-2697
(Parent JIRA
IPE-2168)
Performance was low when processing the rebuild function in TIBCO
iProcess Objects Server.
IPE-2669
TIBCO iProcess Objects Server was suspended due to thread lock
issues.
(Parent JIRA
IPE-2557)
11.3.0
IPE-2562
Corrected.
Corrected.
The performance of TIBCO iProcess Objects Server when checking
queues has been improved.
Implemented. See iProcess Objects Server Startup Performance
Improvements (IPE-2554, IPE-2562) on page 3.
11.3.0
IPE-2554
The performance of TIBCO iProcess Objects Server when loading user
cache has been improved.
Implemented. See iProcess Objects Server Startup Performance
Improvements (IPE-2554, IPE-2562) on page 3.
11.3.0
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.
11.3.0
IPE-2524
(Parent JIRA
IPE-2434)
After a new procedure was imported, TIBCO iProcess Objects Server
did not find it.
Corrected.
TIBCO iProcess Objects Server Release Notes
10
|
Release Notes
Closed in
Release
MR #
Summary
11.3.0
IPE-2523
When attempting to release a work item, TIBCO iProcess Objects
Server returned an swItemErrErr error to the application, stating that
a required field was not specified, even though all required fields were
specified.
(Parent JIRA
IPE-2433)
Corrected.
11.3.0
IPE-2520
(Parent JIRA
IPE-2428)
11.3.0
IPE-2519
(Parent JIRA
IPE-2427)
11.3.0
11.3.0
The escape characters in the Filter Expression were converted
incorrectly.
Corrected.
Performance was low when sorting an empty string in TIBCO iProcess
Objects Server.
Corrected.
IPE-2518
The global variable abandoned_wqs_list was not initialized to NULL.
(Parent JIRA
IPE-2421)
Corrected.
IPE-2517
(Parent JIRA
IPE-2420)
The operation for adding a user to a group using the
method failed until TIBCO iProcess Engine
restarted.
makeAWorkItemListJMS
Corrected.
11.3.0
11.3.0
IPE-2516
TIBCO iProcess Objects Server was suspended.
(Parent JIRA
IPE-1575)
Corrected.
IPE-2513
Adds a new parameter (RPCClntIPs) for use in the swentobjsv.cfg
file to define the list of IP addresses to which the RPC client will be
bound.
(Parent JIRA
IPE-2283)
Usage:
If there is only one network interface used for RPC client, it is
unnecessary to specify this parameter.
If necessary, specify a list of IP addresses, separated by commas.
For example,
RPCClntIPs = 192.168.65.122,192.168.65.119,192.168.65.120
Implemented.
TIBCO iProcess Objects Server Release Notes
Closed Issues 11
|
Closed in
Release
MR #
Summary
11.3.0
IPE-2468
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 an SAL session for the same user.
(Parent
JIRA
IPE-2346)
11.3.0
IPE-2345
Implemented.
A memory leak occurred when logging into or out of a TIBCO iProcess
Objects Server on a 64-bit operating system.
Corrected.
11.3.0
IPE-2259
When the case data is changed by a feature in iProcess Insight or
iProcess Workspace (Browser), such changes are now logged in the
audit trail.
Implemented. See Audit Changes to Case Data (IPE-2259) on page 2.
11.3.0
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 3.
11.3.0
11.1.3
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 2.
IPE-2434
After a new procedure was imported, TIBCO iProcess Objects Server
did not find it.
(Parent JIRA
IPE-2150)
11.1.3
IPE-2433
(Parent JIRA
IPE-2208)
Corrected.
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 Objects Server Release Notes
12
|
Release Notes
Closed in
Release
MR #
Summary
11.1.3
IPE-2430
The sal_frm_findandinit function, which was used to implement
the Open First Available Work Item 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.
(Parent JIRA
IPE-2190)
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.
11.1.3
IPE-2428
(Parent JIRA
IPE-2182)
11.1.3
IPE-2427
(Parent JIRA
IPE-2181)
11.1.3
11.1.3
The escape characters in the Filter Expression were converted
incorrectly.
Corrected.
Performance was low when sorting an empty string in TIBCO iProcess
Objects Server.
Corrected.
IPE-2421
The global variable abandoned_wqs_list was not initialized to NULL.
(Parent JIRA
IPE-2235)
Corrected.
IPE-2420
(Parent JIRA
IPE-2183)
The operation for adding a user to a group using the
method failed until TIBCO iProcess Engine
restarted.
makeAWorkItemListJMS
Corrected.
11.1.3
IPE-1585
MR 43553
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.
Corrected.
TIBCO iProcess Objects Server Release Notes
Closed Issues 13
|
Closed in
Release
MR #
Summary
11.1.2
IPE-2283
Add a new parameter (RPCClntIPs) for use in the swentobjsv.cfg file
to define the list of IP addresses to which the RPC client will be bound.
(Parent JIRA
IPE-2243)
Usage:
If there is only one network interface used for RPC client, it is
unnecessary to specify this parameter.
If necessary, specify a list of IP addresses, separated by comma.
For example,
RPCClntIPs = 192.168.65.122,192.168.65.119,192.168.65.120
Implemented.
11.1.1
MR 43046
Numeric filters did not work correctly after TIBCO iProcess Objects
Server was migrated from 10.3 to 11.0.2.
Corrected.
11.1.1
MR 43052
An error occurred in TIBCO iProcess Objects Server when starting a
case with the Composite arrays.
Corrected.
11.1.0
MR 39954
The TCP port number is not being properly written to the
file.
swentobjsv.log
Corrected.
11.0.2
MR 39282
The iProcess Objects Server needs to be updated to run on Solaris 10 on
x86 and x64 platforms.
Implemented. See Solaris on x86 and x64 Systems Now Supported (MR
39282) on page 4.
11.0.1
MR 35652
There should be a means of specifying a period of time that the server
will wait for the SAL session to become free before timing out.
Implemented. See SAL Session Wait Timeout Configuration Parameter
Added (MR 35652) on page 4.
TIBCO iProcess Objects Server Release Notes
14
|
Release Notes
Closed in
Release
MR #
Summary
11.0.0
MR 34684
There is a timing issue in the startup code that causes the event that is
published by the iProcess Objects Server to indicate that the server is
still initializing when it is actually started. A similar problem occurs
when shutting down — the process status indicates the iProcess
Objects Server is still running instead of shutting down.
Corrected.
11.0.0
MR 33227
Not all case data is returned for work items when they span multiple
versions of procedures, and there is a difference in fields between the
versions.
Corrected.
11.0.0
MR 33124
[Linux only] The OSProvider and Platform properties on the client are
returning values that contain the text “Redhat”.
Corrected. Both of these properties now return the more generic
“Linux”.
11.0.0
MR 33057
Support needs to be added for the new “Work Queue Deltas Via a
Subscription to a JMS Topic” functionality available on the TIBCO
iProcess Server Objects.
Implemented. See Work Queue Deltas via a Subscription to a JMS
Topic Support Added (MR 33057) on page 4.
11.0.0
MR 32557
Support needs to be added for the new “User Preference” functionality
available on the TIBCO iProcess Server Objects.
Implemented. See User Preference Support Added (MR 32557) on
page 5.
TIBCO iProcess Objects Server Release Notes
Closed Issues 15
|
Closed in
Release
MR #
Summary
11.0.0
MR 30580
[HP-UX only] On HP-UX systems, the amount of virtual address space
that can be used for data is one quadrant, which limits the process size
to less than 1 gigabyte (GB). This needs to be increased.
Corrected. The TIBCO iProcess Objects Server has been modified to
combine two quadrants of address space, which increases the amount
of data space to 1.6 GB or more, depending on how the system is
configured (the two combined quadrants are shared with other system
information, which prevents the entire 2 GB from being used as data
space -— consult your HP documentation for more information).
To make use of this MR, you must also do the following:
— Ensure that the “maxdsize” kernel parameter is set to 2 GB. (The
“sam” program is used to set kernel parameters.)
— Check the “ulimit -d” for the user. It also needs to be set to 2 GB.
TIBCO iProcess Objects Server Release Notes
16
|
Release Notes
Restrictions
The table in this section lists restrictions in this release. These restrictions will be
fixed in a later release under the change request number listed.
Change
Request #
Summary
12580
Summary Embedded memos not returned in markings list
If a field that has been placed on a form is embedded and of type swMemo,
it is not returned in the list of markings in the Markings property when the
work item is locked. (Note that if the allMarkings parameter is set to True
when the work item is locked, embedded swMemo fields are returned in the
Markings property.)
14605
Summary Case prediction always uses default precedence in sub-procedures
When predicting or simulating cases with the PredictCase or SimulateCase
methods, the default sub-procedure precedence (released) is always used in
sub-procedures.
14650
Summary Sub-case memo fields set to SW_NA
If you attempt to set the value of memo fields that are defined in sub-procedures via the SetState, JumpTo, or TriggerEvent methods, the value is set to
SW_NA. Main case memo fields are set correctly with these methods.
39781
Summary If you execute spodirector -v or ./swentobjsv -v on Solaris X86, it
displays:
: i11.0(2.0) - Solaris/SPARC [3.1.3]
instead of Solaris/X86
TIBCO iProcess Objects Server Release Notes
Known Issues 17
|
Known Issues
The table in this section lists known issues in this release. Known issues are
problems that are not scheduled to be resolved in a later release.
Known Issues
Summary [HP only] Some special characters (e.g., '£', '¬', etc.) can cause
problems in client applications when using an HP iProcess Objects Server.
The workaround for this issue is to avoid using special characters in user
names, group names, procedure names, step names, and node names.
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 Objects Server. 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 Objects Server
may result in performance degradation. The iProcess Objects Server 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.
Summary Locking work items
The SAL SDK allows long locking multiple times by the same user name.
Consequently, in the iProcess Objects Server, 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.
TIBCO iProcess Objects Server Release Notes
18
|
Release Notes
Known Issues
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 Objects Server Release Notes
TIBCO iProcess® Objects Director
for UNIX
Release Notes
Software Release 11.3.0
October 2011
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO iProcess, TIBCO iProcess Suite, TIBCO
Enterprise Message Service, TIBCO FormBuilder, and TIBCO General Interface are either registered trademarks
or trademarks of TIBCO Software Inc. in the United States and/or other countries.
EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 1999-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Release 11.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Release 11.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Release 11.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
TIBCO iProcess Server Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
TIBCO iProcess Objects Director Release Notes
iv
| Contents
TIBCO iProcess Objects Director Release Notes
|v
Preface
TIBCO iProcess Objects Director is a standalone program that maintains a list of
TIBCO iProcess Objects Servers configured in a node cluster. When a client needs
access to a TIBCO iProcess Objects Server, it first establishes a connection to the
TIBCO iProcess Objects Director. TIBCO iProcess Objects Director then decides
which TIBCO iProcess Objects Server the client should connect to using the "pick
method".
Topics
•
Typographical Conventions, page vi
•
Connecting with TIBCO Resources, page viii
TIBCO iProcess Objects Director Release Notes
vi
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention
Use
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.
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.
TIBCO iProcess Objects Director Release Notes
Preface vii
|
Table 1 General Typographical Conventions (Cont’d)
Convention
Use
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 Objects Director Release Notes
viii
| Connecting with TIBCO Resources
Connecting with TIBCO Resources
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and
resident experts, a place to share and access the collective experience of the
TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety
of resources. To register, go to http://www.tibcommunity.com.
How to Access All TIBCO Documentation
After you join TIBCOmmunity, you can access the documentation for all
supported product versions here:
http://docs.tibco.com/TibcoDoc
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, please
contact TIBCO Support as follows.
•
For an overview of TIBCO Support, and information about getting started
with TIBCO Support, visit this site:
http://www.tibco.com/services/support
•
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user
name, you can request one.
TIBCO iProcess Objects Director 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
•
Compatibility, page 4
•
Closed Issues, page 5
TIBCO iProcess Objects Director Release Notes
2
|
Release Notes
New Features
This section lists features added since the last major (11.0.0) release of this
product.
Earlier Versions
For details of the changes implemented in earlier versions of the product, please
see the Readme and Release Notes for that particular product release.
Release 11.3.0
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.
Release 11.1.3
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.
TIBCO iProcess Objects Director Release Notes
New Features 3
|
Release 11.1.1
There are no new features in this release.
Release 11.1.0
This release of the iProcess Engine is only for the purpose of bringing the version
number in line with the version number of the TIBCO iProcess Engine — there are
no new features.
Release 11.0.2
Solaris on x86 and x64 Systems Now Supported (39283)
The iProcess Engine can now be used on x86 and x64 machines running Solaris
v10.
Release 11.0.1
This is a service release of the iProcess Engine — there are no new features nor
MRs in this release.
Release 11.0.0
There are no new features in this release of the iProcess Engine. For information
about the closed MRs in this release, see Closed Issues on page 5.
TIBCO iProcess Objects Director Release Notes
4
|
Release Notes
Compatibility
TIBCO iProcess Server Objects
Only TIBCO iProcess Server Objects version 11.x can be used with this release.
TIBCO iProcess Objects Director Release Notes
Closed Issues 5
|
Closed Issues
The table in this section lists issues that were closed in the named releases.
Closed in
Release
MR #
Summary
11.3.0
IPE-2733
The Log Files directory is now configurable.
Implemented. See Log Files Directory Is Configurable (IPE-2733) on
page 2.
11.3.0
IPE-2468
(Parent
JIRA
IPE-2346)
11.1.3
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 an SAL session for the same user.
Implemented.
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 an SAL session for the same user.
Implemented.
11.1.2
n/a
There were no MRs closed against TIBCO iProcess Engine in this release.
11.1.1
38862
TIBCO iProcess Objects Director crashed when trying to sort more than
10,000 items in a queue.
Corrected.
11.1.0
n/a
There were no MRs closed against TIBCO iProcess Engine in this release.
11.0.2
39283
The iProcess Engine needs to be updated to run on Solaris 10 on x86 and
x64 systems.
Implemented. See Solaris on x86 and x64 Systems Now Supported
(39283) on page 3.
11.0.1
n/a
There were no MRs closed against TIBCO iProcess Engine in this release.
11.0.0
33146
[Linux only] The name “Redhat” appears in the log file when running on
SUSE Linux.
Corrected. The name “Redhat” has been replaced with the more generic
“Linux”.
TIBCO iProcess Objects Director Release Notes
6
|
Release Notes
TIBCO iProcess Objects Director 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