Release Notes (SQL Server) for Windows

Release Notes (SQL Server) for Windows
TIBCO iProcess® Engine
(SQL) for Windows
(Consolidated with TIBCO iProcess® Objects
Server and TIBCO iProcess® Director)
Release Notes
Software Release 11.6.0
January 2016
Two-Second Advantage®
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Business Studio, TIBCO
Enterprise Message Service, TIBCO Hawk, TIBCO iProcess, TIBCO iProcess Suite, and TIBCO Rendezvous are
either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition
(J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation
in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 1994-2016 TIBCO Software Inc. All rights reserved.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
TIBCO iProcess Engine Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x
x
x
x
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2
2
6
8
Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
12
12
13
13
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release 11.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
17
24
31
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the iProcess Engine Against a SQL Server Instance That Uses “Windows Only” Authentication.
Using SWDIR\util\plist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Must Normalize Case Data to View Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Large Number of User Logins May Cause Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading from Earlier Version May Cause Error Messages in Log File . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
48
50
50
50
51
TIBCO iProcess Engine Release Notes
iv
| Contents
TIBCO iProcess Engine Release Notes
|v
Preface
TIBCO iProcess® Engine provides the runtime execution environment for
business processes developed using TIBCO Business Studio™, TIBCO iProcess®
Workspace (Windows) and other TIBCO iProcess® Suite components.
Topics
•
Related Documentation, page vi
•
Typographical Conventions, page viii
•
Connecting with TIBCO Resources, page x
TIBCO iProcess Engine Release Notes
vi
| Related Documentation
Related Documentation
This section lists documentation resources you may find useful.
TIBCO iProcess Engine Documentation
The following documents form the TIBCO iProcess Engine documentation set:
•
TIBCO iProcess Engine Installation Read this manual for instructions on site
preparation and installation.
•
TIBCO iProcess Engine Release Notes Read the release notes for a list of new
and changed features. This document also contains lists of known issues and
closed issues for this release. The appropriate information for TIBCO iProcess
Objects Director and TIBCO iProcess Objects Server release notes are
integrated into appropriate TIBCO iProcess Engine release notes.
•
TIBCO iProcess Suite Documentation This documentation set contains all the
manuals for TIBCO iProcess Engine and other TIBCO products in TIBCO
iProcess® Suite. The manuals for TIBCO iProcess Engine are as follows:
— TIBCO iProcess Engine Architecture Guide
— TIBCO iProcess Engine Administrator’s Guides:
TIBCO iProcess Engine Administrator’s Guide
TIBCO iProcess Objects Director Administrator’s Guide
TIBCO iProcess Objects Server Administrator’s Guide
— TIBCO iProcess Engine Database Administrator's Guides:
TIBCO iProcess Engine (DB2) Administrator's Guide
TIBCO iProcess Engine (Oracle) Administrator's Guide
TIBCO iProcess Engine (SQL) Administrator's Guide
— TIBCO iProcess swutil and swbatch Reference Guide
— TIBCO iProcess Engine System Messages Guide
— TIBCO iProcess User Validation API User's Guide
— LDAPCONF Utility User’s Guide
TIBCO iProcess Engine Release Notes
Preface vii
|
Other TIBCO Product Documentation
You may find it useful to read the documentation for the following TIBCO
products:
•
TIBCO ActiveMatrix BusinessWorks™
•
TIBCO Business Studio™
•
TIBCO Enterprise Message Service™
•
TIBCO Hawk®
•
TIBCO Rendezvous®
TIBCO iProcess Engine Release Notes
viii
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention
Use
SWDIR
TIBCO iProcess Engine installs into a directory. This directory is referenced in
documentation as SWDIR.
For example, if SWDIR is set to C:\swserver\staffw_nod1 on a Windows server
(on the C: drive), then the full path to the swutil command is
C:\swserver\staffw_nod1\bin\swutil.
code font
Code font identifies commands, code examples, filenames, pathnames, and
output displayed in a command window. For example:
Use MyCommand to start the foo process.
bold code
font
Bold code font is used in the following ways:
•
In procedures, to indicate what a user types. For example: Type admin.
•
In large code samples, to indicate the parts of the sample that are of
particular interest.
•
In command syntax, to indicate the default parameter for a command. For
example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]
italic font
Key
combinations
Italic font is used in the following ways:
•
To indicate a document title. For example: See TIBCO ActiveMatrix
BusinessWorks Concepts.
•
To introduce new terms. For example: A portal page may contain several
portlets. Portlets are mini-applications that run in a portal.
•
To indicate a variable in a command or code syntax that you must replace.
For example: MyCommand PathName
Key name separated by a plus sign indicate keys pressed simultaneously. For
example: Ctrl+C.
Key names separated by a comma and space indicate keys pressed one after the
other. For example: Esc, Ctrl+Q.
TIBCO iProcess Engine Release Notes
Preface ix
|
Table 1 General Typographical Conventions (Cont’d)
Convention
Use
The note icon indicates information that is of special interest or importance, for
example, an additional action required only in certain circumstances.
The tip icon indicates an idea that could be useful, for example, a way to apply
the information provided in the current section to achieve a specific result.
The warning icon indicates the potential for a damaging situation, for example,
data loss or corruption if certain steps are taken or not taken.
Table 2 Syntax Typographical Conventions
Convention
Use
[ ]
An optional item in a command or code syntax.
For example:
MyCommand [optional_parameter] required_parameter
|
A logical OR that separates multiple items of which only one may be chosen.
For example, you can select only one of the following parameters:
MyCommand para1 | param2 | param3
{ }
A logical group of items in a command. Other syntax notations may appear
within each logical group.
For example, the following command requires two parameters, which can be
either the pair param1 and param2, or the pair param3 and param4.
MyCommand {param1 param2} | {param3 param4}
In the next example, the command requires two parameters. The first parameter
can be either param1 or param2 and the second can be either param3 or param4:
MyCommand {param1 | param2} {param3 | param4}
In the next example, the command can accept either two or three parameters.
The first parameter must be param1. You can optionally include param2 as the
second parameter. And the last parameter is either param3 or param4.
MyCommand param1 [param2] {param3 | param4}
TIBCO iProcess Engine Release Notes
x
| Connecting with TIBCO Resources
Connecting with TIBCO Resources
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and
resident experts. It is a place to share and access the collective experience of the
TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety
of resources. To register, go to http://www.tibcommunity.com.
How to Access TIBCO Documentation
Documentation for this and other TIBCO products is available on the TIBCO
Documentation site:
https://docs.tibco.com
Documentation on the TIBCO Documentation site is updated more frequently
than any documentation that might be included with the product. To ensure that
you are accessing the latest available help topics, please visit us at
https://docs.tibco.com.
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, contact
TIBCO Support as follows:
•
For an overview of TIBCO Support, and information about getting started
with TIBCO Support, visit this site:
http://www.tibco.com/services/support
•
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user
name, you can request one.
TIBCO iProcess 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 and Removed Features, page 12
•
Compatibility, page 14
•
Change History, page 15
•
Restrictions, page 37
•
Known Issues, page 43
•
Other Information, page 48
TIBCO iProcess Engine Release Notes
2
|
Release Notes
New Features
This section lists features added since the version 11.4.0 of this product.
Release 11.6.0
The following are new features in this release.
Support for System Platform
From this release, Microsoft Windows 10 (64-bit) is supported.
Support for Database
From this release, SQL Server 2016 is supported.
Supported for Java Version
From this release, Java Standard Edition 8 is supported.
See TIBCO iProcess Engine Installation guide for details.
Release 11.5.0
The following are new features in this release.
System Events Management (IPE-3416)
The following new functions have been added to manage system events:
•
Enable System Events Logging
When installing TIBCO iProcess Engine, you can use the Enable System
Event Logging configuration option in the Configuration dialog to specify
whether or not you want to log system events information.
See "Configuration Dialog" in TIBCO iProcess Engine Installation for more
details about how to use this configuration option.
TIBCO iProcess Engine Release Notes
New Features 3
|
The following tables are created to store information about system events
logging:
—
system_event:
the table is used to store basic information about system
events.
—
system_event_conf: the table is used to store system events configuration
information.
•
Audit System Events
You can use the SYSTEM_EVENT_LOGGIN process attribute to specify whether to
audit system events after installing or upgrading to TIBCO iProcess Engine
11.5.0.
See "Activity Monitoring and Work Queue Delta Configuration" in TIBCO
iProcess Engine Administrator's Guide for more details.
•
Publish System Events
You can use the PUBLISH_SYS_EVENT_METHOD process attribute to specify
whether or not you want to publish system events. Before publishing a system
event, ensure that the system event has been audited.
You can publish a system event by using Windows Event Viewer, TIBCO
Hawk Agent, or the IAPJMS process.
— If you choose to publish a system event using TIBCO Hawk Agent, you can
use the SE_WORKER_PORTNO process attribute to specify a port number of
the socket that is used for communications between the processes that
audit the system events and the "worker" process. The "worker" process
finally sends the events information to TIBCO Hawk Agent.
— If you choose to publish a system event using the IAPJMS process, you can
use the SEJMS_TOPICNAME attribute to specify the JMS topic name for the
JMS destination that is used to publish the system event.
See "Activity Monitoring and Work Queue Delta Configuration" in TIBCO
iProcess Engine Administrator's Guide for more details.
•
Query System Events Information
You can use the plist -e command to query information about a single or
multiple system events.
See "System Event Information" in TIBCO iProcess Engine Administrator's Guide
for more details.
•
Turn Off System Events
You can delete information about a single or multiple system events or clear
information about system events ahead of a specified date from the iProcess
database using the swadm delete_system_event command.
TIBCO iProcess Engine Release Notes
4
|
Release Notes
See "Removing System Events Information from the iProcess Database" in
TIBCO iProcess Engine Administrator's Guide for more details.
•
Import and Export System Events Configuration
You can import a system event configuration file into TIBCO iProcess Engine
by using the swutil IMPEVENTCONF command and export configuration
information of a system event from TIBCO iProcess Engine to a command line
by using the swutil EXPEVENTCONF command.
See TIBCO iProcess swutil and swbatch Reference Guide for more details about
how to use these commands.
Optimize SQL Statements Execution (IPE-3455)
You can use the sqloptim file, which is located in the SWDIR/etc directory, to
optimize SQL statements execution in the database.
See "SWDIR\etc\sqloptim" in TIBCO iProcess Engine Administrator's Guide for
more details.
Reduce Login Time (IPE-3468)
The average time for a user to log in to a TIBCO iProcess Engine node is now
identical no matter how many user groups and users have been created in this
TIBCO iProcess Engine node if other system conditions remain unchanged.
For example, the average time for the user to log in to an iProcess Engine node
with 500 users registered is the same as the average time for the user to log in to
the same iProcess Engine node with 15000 users registered if other system
conditions remain the same.
Unlock Work Items (IPE-3472)
You can use the MN_UNLOCKER process attribute to specify which iProcess users
can have permission to unlock work items.
See "Process Management Configuration" in TIBCO iProcess Engine Administrator's
Guide for more details.
WRITELOG Function Introduced ( IPE-3473)
You can use the WRITELOG function to wri te messages to a log file to trace and
debug iProcess scripts issues.
See "Log Functions" in TIBCO iProcess Expressions and Functions Reference Guide for
more details.
TIBCO iProcess Engine Release Notes
New Features 5
|
Define the Maximum Size of Log Files (IPE-3476)
You can use the maxsize parameter in the DEBUG process attribute to define the
maximum size of log files, except the sw_error, sw_warn, SWEntObjSvXX.log,
and spodirectorXX.log files.
When the log files reach the maximum size, if the onfull parameter in the DEBUG
process is set to save, the log files are archived.
The default value of the maxsize parameter is 20 GB, and the default value of the
onfull parameter is save.
See "Monitoring Log files" in TIBCO iProcess Engine Administrator's Guide for more
details.
Define the Maximum Size of the sw_warn and sw_error Log Files (IPE-3477)
You can use the WARN_ERROR_LOG_SIZE process attribute to define the maximum
size of the sw_warn and sw_error log files. The default value of the
WARN_ERROR_LOG_SIZE process attribute is 2 GB.
See TIBCO iProcess Engine Administrator's Guide for more details.
Work Items Are Unique to Users (IPE-3480)
Add requestid as the unique identifier for each work item so that each work
item can only be locked by one user.
Change Field Data Type (IPE-3513)
The IMAGE field data type in the pm_objects, proc_defn, and user_setting
tables in the database has been changed to VARBINARY (MAX).
From TIBCO iProcess Engine 11.5.0, all the new case memo data is stored in the
and pack_nmemo tables and the data type is VARBINARY (MAX).
nmemo
Before using an application to call the SW_ADD_PACK_MEMO procedure to define an
item of pack memo data to be passed to iProcess, you have to change the
SW_ADD_PACK_MEMO procedure because the data type of the memo_data field is
changed from IMAGE to VARBINARY (MAX). See "SW_ADD_PACK_MEMO" in
TIBCO iProcess Engine (SQL) Administrator's Guide for more details.
You can migrate the old case memo data from the memo and pack_memo tables to
the nmemo and pack_nmemo tables in one of the following ways:
•
Using the Migrate live cases or Migrate all cases option in the Upgrade or
New Install Dialog when upgrading TIBCO iProcess Engine to 11.5. See
TIBCO iProcess Engine for Windows Installation for more details.
TIBCO iProcess Engine Release Notes
6
|
Release Notes
•
Using the swutil MIGRATEMEMOS ALL_CASES|LIVE_CASES|casenumrange
command after upgrading TIBCO iProcess Engine to 11.5. See "Migrating Old
Case Memo Data" in TIBCO iProcess swutil and swbatch Reference Guide for
more details.
It might take a long time to complete the migration procedure. The time
consumption depends on the volume of the memos in the pack_memo and memo
tables.
Delayed Release Has Been Enhanced (IPE-3536)
The following features have been introduced to enhance the delayed release
function:
•
Add the SW_DELAYED_RELEASE_ERR stored procedure in the iProcess database.
TIBCO iProcess BusinessWorks Connector can trigger the
SW_DELAYED_RELEASE_ERR stored procedure to call and send the error
message to the BG process if the iProcess Complete Delayed Release activity
fails to complete delayed release of an EAI BusinessWorks step.
See "Delayed Release" in TIBCO iProcess BusinessWorks Connector User’s Guide
for more details.
•
Add the following system-define message in audit trail to trace the error
message when performing delayed release of an EAI BusinessWorks step has
failed:
StepDescription EAI delayed-release failed (error code (failure_count,
BG_action) : error message)
088
See "Understanding Audit Trails" in TIBCO iProcess Engine Administrator's
Guide for more details.
Support for Database
In this release, SQL Server 2014 is supported.
Release 11.4.1
The following are new features in this release.
TIBCO iProcess Engine Release Notes
New Features 7
|
Set Case Priority for Deadlines (IPE-3224)
You can set the priority for case deadlines. The FORCE_DEADLINE_PRIORITY and
USE_PRIORITY_DEADLINE process attributes have been added to help set deadline
priority.
See TIBCO iProcess Engine Administrator's Guide for more information about the
process attributes. See TIBCO iProcess Modeler Advanced Design for more
information about rules of case deadline priority setting.
Check the Time for Acquiring a User’s Mutex (IPE-3280)
You can define the maximum amount of time (in milliseconds) that an iProcess
Objects Server process should take to acquire for a user’s mutex by using the
SPO_USERMUTEX_WAITTIME process attribute. If the time for acquiring a user’s
mutex is longer than the time you set in the process attribute, an error is logged in
the sw_warn file.
See TIBCO iProcess Engine Administrator's Guide for more information.
Function for Calculating the Default Number of Message Processing Threads (IPE-3282)
You can calculate the default number of message processing threads by using the
defined function.
See TIBCO iProcess Objects Server Administrator’s Guide for more information.
Remove the Orphaned Work Items (IPE-3290)
Add the swutil CHECKITEM and swutil CLEANITEM commands to check and to
remove the work items in a work queue that is cached by the WIS process, if the
work items do not have matching records in the outstanding_addr table.
See TIBCO iProcess swutil and swbatch Reference Guide for more information.
Track the Time for Dequeuing a Message from an Mbox Set (IPE-3296)
The duration of dequeuing a message from an Mbox set is tracked and an error
message is logged in the sw_warn file if the duration is equal to or over the time
that is defined in the newly added MBSET_DEQUEUE_TIMEOUT process attribute.
See TIBCO iProcess Engine Administrator's Guide for more information.
Track the Time for Processing an EAI Step (IPE-3297)
The duration of processing an EAI step is tracked and an error message is logged
in the sw_warn file if the duration is equal to or over the time that is defined in the
EAI_STEP_TIMEOUT process attribute, which is newly added.
TIBCO iProcess Engine Release Notes
8
|
Release Notes
See TIBCO iProcess Engine Administrator's Guide for more information.
Add the MEMSET Debug String for Debugging iProcess Engine Server Processes (IPE-3298)
If the debugging is disabled for an iProcess Engine server process, the MEMSET
debug string will be applied to record the debug information.
See TIBCO iProcess Engine System Message Guide for more information.
Case Counting Performance Improvements (IPE-3300)
The case counting performance has been improved by resetting the default value
of the CCOUNT_CACHE_REFRESH process attribute to 0. In such cases, the cached list
of cases currently on the system will not be refreshed and the case counting will
not be performed.
See TIBCO iProcess Engine Administrator's Guide for more information.
Exact Timestamps for Instructions in Audit Trail (IPE-3369)
In previous releases, the timestamps used in the audit_trail table recorded
when the actual Release actions of the instruction are carried out.
The timestamps in the audit_trail table now can either record when the user
does a specified operation or record when BG or RPCBG processes an instruction.
See TIBCO iProcess Engine Administrator’s Guide for more information.
Release 11.4.0
The following are new features in this release.
Define how many of the Latest Versions of Procedure Definition to be Cached (IPE-2975)
To define how many of the latest versions of procedure definitions are to be
cached by the iProcess Objects Server processes, you can use the
RESTART_SPO_CACHE_PROC process attribute when restarting or quick starting
iProcess Engine, and use the SPO_CACHE_PROC process attribute when the iProcess
Objects Server process starts normally.
See TIBCO iProcess Engine Administrator's Guide for more information.
Enable Quick Start Mode (IPE-2976)
You can quick start iProcess Engine server processes with quick start mode by
running the following command:
TIBCO iProcess Engine Release Notes
New Features 9
|
swstart -q
See TIBCO iProcess Engine Administrator's Guide for more information.
Define the Minimum Size of a Work Queue to Cache on a Restart (IPE-2990)
You can control the minimum size of a queue to be cached by a WIS process by
using the RESTART_WIS_CACHE_THRESHOLD process attribute when quick starting
or restarting iProcess Engine.
The RESTART_WIS_CACHE_THRESHOLD attribute will be used only for restart and
quick start.
See TIBCO iProcess Engine Administrator's Guide and TIBCO iProcess Engine
Installation for more information.
Procedure Level Events (IPE-3016)
Procedure level events are introduced with the following functionalities:
— You can define an event, which is triggered just before or after performing
the purge, close, resurrect, suspend, or resume action, from the Events tab
of the Properties dialog. The Event tab contains the following procedure
level events: OnBeforePurge, OnBeforeClose, OnAfterClose,
OnBeforeResurrect, OnAfterResurrect, OnBeforeSuspend,
OnAfterSuspend, OnBeforeResume, and OnAfterResume. See TIBCO
iProcess Modeler Procedure Management for more information on the Event
tab.
— You can use the CancelProcEvent expression to cancel the purge, close,
resurrect, suspend, or resume action that is set in the OnBeforeEvent
procedure level events. See TIBCO iProcess Expressions and Functions
Reference Guide for more information.
— You can use swutil and swbatch utilities to purge or close cases without
triggering events. See TIBCO iProcess swutil and swbatch Reference Guide for
more information.
— The SW_PURGE_WITHOUT_EVENT and SW_CLOSE_WITHOUT_EVENT SSOLite
command procedures are added to purge or close cases without triggering
events. See the appropriate TIBCO iProcess Engine (Database) Administrator’s
Guide for more information.
— The definition of procedure events is stored in the proc_event table, and
the information of cases that are interrupted by triggered events when
processing the purge, close, resurrect, suspend, or resume operation is
stored in the case_event table. The case information is recorded in the
case_event table only when the BG process is handling the delayed release
EAI steps, which are defined in the triggered event. See the appropriate
TIBCO iProcess Engine Release Notes
10
|
Release Notes
TIBCO iProcess Engine (Database) Administrator’s Guide for more
information.
Set Auto-Purge and Deadlines for Cases (IPE-3019)
You can configure delay auto-purge and deadline for cases in TIBCO iProcess
Engine. The information of the auto-purge delay is recorded in the proc_index
table.
You can create a case deadline for a case to trigger an event after a specified time
period, as well as update and delete a case deadline. The definitions of the case
deadlines are recorded in the proc_deadline table. When a case is started, the
information of the case deadline is saved in the case_deadline_event table.
See TIBCO iProcess Modeler Procedure Management for more information on the
configuration of delay auto-purge and case deadlines, proc_index,
proc_deadline, and case_deadline_event tables.
See TIBCO iProcess Engine (Database) Administrator’s Guide for more information
on the proc_index table.
See TIBCO iProcess Expressions and Functions Reference Guide for more information
on the CreateCaseDeadline, UpdateCaseDeadline, and DeleteCaseDeadline
functions.
Test the Event Mechanism Manually (IPE-3052)
You can test the event mechanism manually by using the following command:
swadm evloopback
When Process Sentinel starts, a START event is issued, or a SHUTDOWN event is
issued, the event mechanism is tested automatically.
See TIBCO iProcess Engine Administrator's Guide for more information.
Additional IP Addresses Support (IPE-3055)
IPv6 addresses are supported on Windows and Linux systems.
See TIBCO iProcess Engine Installation Guide for more information on the
configuration.
TIBCO iProcess Engine Release Notes
New Features 11
|
When communicating with TIBCO iProcess Technology Plug-ins with an IPv6
address, you need to note that TIBCO iProcess Technology Plug-ins only supports
inbound communication at runtime with IPv6 addresses.
•
If you want to use an IPv6 address for inbound communication at design time,
you must upgrade TIBCO iProcess Server Objects to a version that is higher
than 11.4.0 after installing TIBCO BusinessWorks iProcess Plug-in, and make
sure the upgraded version supports IPv6. Contact TIBCO Support for details
of versions of TIBCO iProcess Server Objects that support IPv6.
•
If you use TIBCO iProcess Server Objects as the protocol for inbound
communication, make sure the Auto Config Date Format check box is
unchecked in the Advanced tab of the iProcess Connection activity.
TIBCO iProcess Engine Release Notes
12
|
Release Notes
Deprecated and Removed Features
This section describes any features that have been deprecated or removed since
the version 11.4.0 of this product.
For deprecated features, if relevant, useful alternative to the deprecated features
are listed. Any use of a deprecated feature should be discontinued as it may be
removed in a future release. You should avoid becoming dependent on
deprecated features and become familiar with the suggested alternative features.
Release 11.6.0
Deprecated Features
The following features are deprecated in this release:
•
TIBCO iProcess Client (ASP) and TIBCO iProcess Client (JSP) are deprecated
and might be removed from a future release. You can use TIBCO iProcess
Workspace (Browser) as an alternative client interface for TIBCO iProcess
Suite.
•
TIBCO iProcess Objects (C++) is deprecated and might be removed in a future
release. You can use TIBCO iProcess Server Objects as an alternative interface
for your iProcess applications.
Removed Features
From this release, SQL Server 2005 and 2008 are no longer supported.
Release 11.5.0
Deprecated Features
No features are deprecated in this release.
Removed Features
From this release, Microsoft Windows Server 2003 is no longer supported.
TIBCO iProcess Engine Release Notes
Deprecated and Removed Features 13
|
Release 11.4.1
Deprecated Features
From this release, the support for Microsoft Windows Server 2003 is deprecated.
Removed Features
From this release, Microsoft Windows XP is no longer supported.
Release 11.4.0
No features are deprecated and removed in this release.
TIBCO iProcess Engine Release Notes
14
|
Release Notes
Compatibility
In addition to other versions of TIBCO iProcess® Suite components, the following
TIBCO products have been successfully tested for compatibility with version
11.6.0 of TIBCO iProcess Engine.
Product
TIBCO
iProcess®
Version(s)
Decisions Server Plug-in
Version 10.3.0.01
TIBCO iProcess® Web Services Server Plug-in
Version 11.3.0
TIBCO iProcess® Technology Plug-ins
Version 11.6.0
TIBCO iProcess® Server Objects
Version 11.4.1
If you have any queries regarding product compatibility with this version of the
iProcess Engine, contact TIBCO Support for further assistance.
TIBCO iProcess Engine Release Notes
Change History 15
|
Change History
The following JIRA issues and Modification Requests (MRs) have been
implemented since version 11.4.0 of TIBCO iProcess Engine.
Release 11.6.0
Defect #
Description
IPE-3640
If you specified a different value for the SW_CP_VALUE property other than the
Priority property in the Input tab of the iProcess Complete Delayed Release
activity, the message priority was not changed to the value specified in the
SW_CP_VALUE property after completing the delayed release.
(Parent JIRA
IPE-3626)
Corrected.
IPE-3686
The installer crashed when upgrading iProcess Engine from version 11.1.0.7 to
11.4.1.10.
Corrected.
IPE-3687
TIBCO iProcess Objects Server crashed when multiple threads concurrently
called the UVAPI interface.
Corrected.
IPE-3698
The status of the WISMBD process was not correct when WIS processes were
suspended and the WISMBD process was terminated.
Corrected.
IPE-3700
(Parent JIRA
IPE-3681)
When the BG process was used to publish audited activity messages to the
IAPJMS process, the IAPJMS process spent a lot of time looking up a dynamic
JMS topic; therefore, both the IAPJMS process and BG process worked very
slowly.
Corrected.
IPE-3702
(Parent JIRA
IPE-3682)
In a clustered environment, the SPO process crashed after the client initiated a
connection to the SPO server.
Corrected.
TIBCO iProcess Engine Release Notes
16
|
Release Notes
Defect #
Description
IPE-3703
The WIS process crashed when caching the procedures that were stored in the
proc_index table.
(Parent JIRA
IPE-3695)
IPE-3710
(Parent JIRA
IPE-3707)
Corrected.
When using the swutil EVENT command with an abox file to update field
data, if the abox file contained a numeric field and the value of this field
contained a leading zero with no decimal point, after updating, the leading
zero in the value was removed and replaced with a decimal point behind the
value in the database table. For example, if the original value was"09", the
value in the database table was updated to "9." .
Corrected.
IPE-3720
When starting a case and executing a graft step either using sw_graft stored
procedure or an iProcess Server Objects application, if the auto-purge option
was enabled for the graft sub procedure, an error was returned to iProcess
Workspace (Browser).
Corrected.
IPE-3729
The SW_EVENT procedure did not work after upgrading to iProcess Engine
version 11.5.0.
Corrected
IPE-3741
The RPC_POOL process crashed when releasing an unreleased procedure that
had configured case deadlines.
Corrected.
IPE-3753
(Parent JIRA
IPE-3692)
When multiple users attempted to log in to TIBCO iProcess Objects Server
through different client applications (.net/java), a "No response from SPO
Server" error message was displayed for certain users.
Corrected.
IPE-3757
(Parent JIRA
IPE-3691)
If a TIBCO iProcess Engine client connected to TIBCO iProcess Objects Server
that had already exited, and it did not close the connection to TIBCO iProcess
Objects Server, TIBCO iProcess Objects Server might crash.
Corrected.
IPE-3758
An error occurred when using the save as > new procedure option to rename a
procedure.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 17
|
Defect #
Description
IPE-3759
The BG process crashed when running the SSOLITE stored procedure that
contained graft steps.
Corrected.
IPE-3795
The standard file descriptor (for example, 0, 1, 2) was used in the RPC
depository.
Corrected.
Release 11.5.0
Defect #
Description
IPE-701
When using the swstart script that was located in the SWDIR/bin directory to
start all the server processes in a node cluster, if multiple nodes had similar
names, the server processes did not start.
Corrected.
IPE-3141
The step_addr column of the predict table displayed NOADDR when a new
user was added to TIBCO iProcess Engine.
Corrected.
IPE-3394
When installing iProcess Engine, if you used JBoss EAP 6.1.0 as the JMS
provider, the configuration information written to the
iapjms_classpath.properties file that was located in the $SWDIR/etc
directory was incorrect.
Corrected.
IPE-3396
When calling the triggerEvent() method, the SPO process did not unlock the
procedure cache if an error occurred.
Corrected.
IPE-3399
When using the TIBCO iProcess Objects Server process to cache a specified
version of the procedure definition that did not exist in TIBCO iProcess Engine,
the following error message was displayed in the TIBCO iProcess Objects
Server log file:
SPO did not unlock every the read/write lock.
Corrected.
TIBCO iProcess Engine Release Notes
18
|
Release Notes
Defect #
Description
IPE-3400
When importing a procedure library using the swutil IMPORTLIB command
for the second time, if the description of the procedure exceeded 24 characters,
the importing of the procedure library failed.
Corrected.
IPE-3403
The Database Connection tab in the iProcess Connection resource by default
had the Auto Config selected to retrieve the database configuration from the
iProcess Objects Server, in a Windows SQL Server environment, the database
URL was populated by the ODBC data source name, not the name of the SQL
Server database.
Corrected.
IPE-3407
When you started more than 1000 cases using the SSOLite stored procedures
on SQL Server 2014, some cases were not started successfully.
Corrected.
IPE-3414
When using the swsvrmgr START_NEW command to start a new instance of the
process, the Process Sentinels crashed.
BG
Corrected.
IPE-3416
The following functions are introduced to manage system events:
•
Enable system events logging
•
Audit system events
•
Publish system events
•
Query information about system events
•
Turn off system events
•
Import configuration files of system events into iProcess Engine
•
Export configuration information of system events to a command line
Implemented. See System Events Management (IPE-3416) on page 2.
IPE-3421
When starting a case that contained a numeric field in iProcess Engine 11.4.1, if
the NLS_LANG parameter was set to en_US and the decimal seperator in the
numeric field was set to the period character rather than the comma character,
a warning message was displayed in the sw_warn file.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 19
|
Defect #
Description
IPE-3424
A closed case was not opened by using SSOLite stored procedures.
Corrected.
IPE-3425
After successfully caching a version of a procedure definition by using the
iProcess Objects Server process, the following error message was displayed in
the TIBCO iProcess Objects Server log file:
g_proc_cache_rwlock was read-locked.
cache_the_procedure() SEO_node_namefind() failed.
Corrected.
IPE-3436
The SPO process unlocked the read and write lock before locking the process
cache.
Corrected.
IPE-3437
(Parent JIRA
IPE-3380)
IPE-3438
(Parent JIRA
IPE-3405)
IPE-3439
(Parent JIRA
IPE-3406)
When running a script, which called the markfieldchanged function, to
release work items, the work items were locked.
Corrected.
When you installed TIBCO iProcess Engine 11.4.x or upgraded TIBCO iProcess
Engine to 11.4.x in silent mode, the process was suspended.
Corrected.
When installing TIBCO iProcess Engine 11.4.x on SQL Server 2014, the
following warning occurred unexpectedly:
WARNING: the version of SQL Server you are using is not
supported.
Corrected.
IPE-3440
(Parent JIRA
IPE-3415)
IPE-3441
(Parent JIRA
IPE-3417)
When installing a slave node while the master node was running, the slave
node installation was suspended.
Corrected.
When calling the GetNextDeltaItem() method to retrieve a new or modified
work item from a work queue, the error message "invalid format of delta
details from SAL" was recorded in the TIBCO iProcess Objects Server log
file.
Corrected.
TIBCO iProcess Engine Release Notes
20
|
Release Notes
Defect #
Description
IPE-3445
When deploying a procedure in TIBCO Business Studio, the procedure
inherited the access control settings of the deployer, instead of the predefined
access control settings from the procedure library.
Corrected.
IPE-3455
Add the sqloptim file, which is located in the SWDIR/etc directory, to optimize
SQL statements execution.
Implemented. See Optimize SQL Statements Execution (IPE-3455) on page 4.
IPE-3457
The swutil
EXPORT
command was case sensitive for the iProcess users.
Corrected.
IPE-3459
When specifying values for fields in the case_data table, if Support Unicode
Encoding was enabled and the length of the values exceeded the predefined
size, the values were not truncated before they were stored in the table.
Corrected.
IPE-3463
When using the swutil PROC RELEASE command to release a version of a
procedure with the -M ALL option, if the required libraries and the EAI plug-in
were not loaded because of an EAI failure, the specified version of the
procedure was released, but all the active cases were not migrated to the new
version.
Corrected.
IPE-3467
After forwarding work items to another queue, the Arrival-time attribute
was not displayed correctly.
Corrected.
IPE-3468
Reduce the average time for a user to log in to a TIBCO iProcess Engine node
with many user groups and users created.
Implemented. See Reduce Login Time (IPE-3468) on page 4.
IPE-3472
Add the MN_UNLOCKER process attribute to define who can have the permission
to unlock work items.
Implemented. See Unlock Work Items (IPE-3472) on page 4.
IPE-3473
Add the WRITELOG function to write messages to log files.
Implemented. See WRITELOG Function Introduced ( IPE-3473) on page 4.
TIBCO iProcess Engine Release Notes
Change History 21
|
Defect #
Description
IPE-3476
Add support for defining the maximum size of log files.
Implemented. See Define the Maximum Size of Log Files (IPE-3476) on page 5.
IPE-3477
Add the WARN_ERROR_LOG_SIZE process attribute to define the maximum size
of the sw_warn and sw_error log files.
Implemented. See Define the Maximum Size of the sw_warn and sw_error Log
Files (IPE-3477) on page 5.
IPE-3480
Add the requestid as the unique identifier for each work item.
Implemented. See Work Items Are Unique to Users (IPE-3480) on page 5.
IPE-3486
When triggering a graft step, TIBCO iProcess Objects server crashed.
Corrected.
IPE-3491
When using the SW_JUMPTO procedure to have a case jumped from its current
step to another step in the sub-procedure, if the case tag contained the main
procedure name and the withdraw list was set to the asterisk (*) wildcard, the
transaction failed and an error message was displayed in the sw_error file.
Corrected.
IPE-3496
The participation data within the WQS process was not unlocked after it was
locked.
Monitor logic is added in the WQS process to accurately trace the locations
where participation data is locked.
Implemented.
IPE-3497
The sw_partic_unlock_external() method was called to unlock a locker
that was not created in the participation data.
Corrected.
IPE-3498
The sw_partic_unlock_external() method was not called to unlock a locker
after the locker was created in the participation data.
Corrected.
IPE-3513
Change field data type in the database.
Implemented. See Change Field Data Type (IPE-3513) on page 5.
TIBCO iProcess Engine Release Notes
22
|
Release Notes
Defect #
Description
IPE-3516
When upgrading iProcess Engine to 11.4.1.8, the master server was incorrectly
treated as a slave server, which caused the Upgrade Schema check box to be
disabled and the database upgrade to fail.
Corrected.
IPE-3536
Add the W_DELAYED_RELEASE_ERR stored procedure in the database and
system-define error message in audit trail to trace delayed release.
Implemented. See Delayed Release Has Been Enhanced (IPE-3536) on page 6.
IPE-3537
When installing TIBCO iProcess Engine, if you specified an incorrect password
for the database user, no warning messages were displayed until the
installation failed.
Corrected.
IPE-3538
When starting the iProcess Objects Server (SPO) process, the memory was
rapidly consumed.
Corrected.
IPE-3588
When migrating only live cases from swutil by running the swutil PROC
command, all cases (including close cases) were migrated.
RELEASE -M
Corrected.
IPE-3615
When the MakeProc function was called to return the minor version of a
released procedure, if the major version and minor version parameters were
both set to -1 in the function, an incorrect procedure version was returned.
Corrected.
IPE-3621
The following deadlock error occurred on SQL Server 2012 SP2:
fil_dbq_delete_msg() Unable to execute statement(non-select)
Transaction was deadlocked on lock resources with another process
and has been chosen as the deadlock victim. Rerun the
transaction.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 23
|
Defect #
Description
IPE-3627
Upgrade Java 1.7 to new versions on the following platforms of iProcess
Engine:
•
Windows, Linux, and Solaris: 1.7.0.75
•
HP: 1.7.0.11
•
AIX: 7.0.0.195
Implemented.
IPE-3629
When using the trigger event function in a script step to change the value of
a memo field, if the new value of the memo field exceeded 4096 characters, the
memo data stored in the memo table was incorrect.
Corrected.
IPE-3632
After installing TIBCO iProcess Engine 11.4.1.8, the "Cannot
grant, deny, or
revoke permissions to sa, dbo, entity owner, information_schema,
sys, or yourself."
warning message was displayed when running the
file.
manual_usqli11_4_1_5.sql
Corrected.
IPE-3633
When installing TIBCO iProcess Engine 11.4.1.8, if the Upgrade NobleNet
Portmapper check box is selected in the Select components to configure
dialog, the installer was crashed or the "Failed to start the NobleNet
Portmapper for TCP service or contact it once it had been
started"
error message was displayed.
Corrected.
IPE-3641
When completing a delayed release in TIBCO ActiveMatrix BusinessWorks, if
the SW_CP_VALUE field was set to a value, the value of the message priority in
TIBCO iProcess Engine was not changed.
Corrected.
IPE-3642
TIBCO iProcess Engine failed to insert the outstanding workitems information
into the outstanding_addr table.
Corrected.
IPE-3650
Upgrade Tomcat to version 7.0.59.
Implemented.
TIBCO iProcess Engine Release Notes
24
|
Release Notes
Release 11.4.1
Defect #
Description
IPE-734
Error messages were generated when deploying a procedure with EAI steps
from TIBCO Business Studio to TIBCO iProcess Engine.
Corrected.
IPE-1754
After starting a case, which contained only one step, the BG process crashed
when the step deadline expired.
Corrected.
IPE-3013
TIBCO iProcess Engine ran out of case numbers.
Corrected.
IPE-3215
(Parent JIRA
IPE-3189)
The BG processes crashed because TIBCO iProcess Engine unexpectedly
released memory addresses twice. Also, a memory leak occurred in the BG
processes.
Corrected.
IPE-3217
(Parent JIRA
IPE-3177)
IPE-3218
(Parent JIRA
IPE-1982)
If an error occurred when closing a case, the BG process did not catch the error
nor roll back the transaction.
Corrected.
If an EAISQL step failed to process, for example, you specified unexisting
database parameters, the cases that should have remained outstanding were
terminated.
Corrected.
IPE-3224
Add support to set priority for case deadlines.
Implemented. See Set Case Priority for Deadlines (IPE-3224) on page 7.
IPE-3231
When you close or purge a case that contains sub-cases, delete certain
audit_trail entries to reduce the number of returned sub-cases.
Implemented.
TIBCO iProcess Engine Release Notes
Change History 25
|
Defect #
Description
IPE-3242
After installing EAICOM with TIBCO iProcess Engine, the following error
message was continually displayed in the sw_error log file if the BG processes
did not work due to the session level failover:
1945-Database error: idl_SQL_allocate_connection_from_pool()
idl_SQL_enlist_connection() Failed (Statement ID - 0)
(ORA-25402: transaction must roll back)
Corrected.
IPE-3249
An error message was generated in the Event Viewer Application log when
starting up TIBCO iProcess Objects Director.
Corrected.
IPE-3255
After performing failover twice on SQL Server 2008 R2, the BG processes failed
to connect to the database if EAICOM was registered.
Corrected.
IPE-3258
Add more logs to detect the reason for the crashed iProcess Objects Server
process when purging cases.
Implemented.
IPE-3261
In the BG processes, a memory leak occurred in procedure definition sessions.
(Parent JIRA
IPE-2821)
Implemented.
IPE-3263
The iProcess Objects Server processes crashed when purging cases.
Corrected.
IPE-3269
(Parent JIRA
IPE-3265)
When the iProcess Objects Server process caching procedures, the released
version of procedures occasionally were in the version list rather than in the
released version list.
Corrected.
IPE-3270
(Parent JIRA
IPE-3259)
IPE-3271
(Parent JIRA
IPE-3267)
The iProcess Objects Server process crashed after you deleted a withdrawn
procedure.
Corrected.
The iProcess Objects Server process did not unlock the read/write lock each
time for the procedure cache.
Corrected.
TIBCO iProcess Engine Release Notes
26
|
Release Notes
Defect #
Description
IPE-3278
After migrating cases in a procedure version to a new version, the cases were
kept in the original procedure version.
(Parent JIRA
IPE-3087)
IPE-3279
Corrected.
The watcher Process Sentinel process crashed when starting up process
sentinels if you set the value of the TIMZONE process attribute containing a line
break.
Corrected.
IPE-3280
Add the SPO_USERMUTEX_WAITTIME process attribute to define the maximum
amount of time (in milliseconds) that an iProcess Objects Server process should
take to acquire for a user’s mutex before reporting the time to the log file.
Implemented. See Check the Time for Acquiring a User’s Mutex (IPE-3280) on
page 7.
IPE-3282
Add a function to calculate the default number of message processing threads.
Implemented. See Function for Calculating the Default Number of Message
Processing Threads (IPE-3282) on page 7.
IPE-3289
(Parent JIRA
IPE-3263)
IPE-3290
The iProcess Objects Server process crashed when purging cases that had been
purged previously.
Corrected.
Add support to check and to remove work items in a work queue that is cached
by the WIS process, but do not have matching records in the
outstanding_addr table.
Implemented. See Remove the Orphaned Work Items (IPE-3290) on page 7.
IPE-3293
(Parent JIRA
IPE-3319)
IPE-3296
After executing the swstop command, the BG processes on the master node
were not stopped.
Corrected.
Add support to track the duration for dequeuing a message from an Mbox set.
Implemented. See Track the Time for Dequeuing a Message from an Mbox Set
(IPE-3296) on page 7.
IPE-3297
Add support to track the duration for processing an EAI step.
Implemented. See Track the Time for Processing an EAI Step (IPE-3297) on
page 7.
TIBCO iProcess Engine Release Notes
Change History 27
|
Defect #
Description
IPE-3298
Add the MEMSET debug string to record the debug information if the debugging
is disabled for an iProcess Engine server process.
Implemented. See Add the MEMSET Debug String for Debugging iProcess
Engine Server Processes (IPE-3298) on page 8.
IPE-3299
Failed to upgrade from TIBCO iProcess Engine version 11.1 to 11.3.1 if you
tried to upgrade TIBCO iProcess Engine more than once because the leavers
table was not dropped from the SSOLite package.
Corrected.
IPE-3300
Case counting is not performed by default.
Implemented. See Case Counting Performance Improvements (IPE-3300) on
page 8.
IPE-3309
(Parent JIRA
IPE-3257)
After importing procedures through the XML Process Definition Language
(XPDL) file, the access control on the library containing the imported
procedures was reverted to the default settings.
Corrected.
IPE-3310
(Parent JIRA
IPE-3287)
IPE-3311
(Parent JIRA
IPE-3256)
The WIS process was suspended due to the m_IndexLock parameter was used
in the CIndex::SetDeleted() and CIndex::IsDeleted() functions.
Corrected.
When connecting a LDAP server through a LDAP proxy server, the following
error message was reported if the time delay between the two calls exceeded
the idle timeout:
An error has occurred in 2nd call to SW_LDAP_search(): Error
whilst performing Search (entries = 0)
Corrected.
IPE-3312
The number of connections between the IAPJMS process and TIBCO Enterprise
Message Service increased when the IAPJMS process sent a message to TIBCO
Enterprise Message Service after you have stopped the BG process.
Corrected.
IPE-3313
The user step following the OnAfterClose event was not displayed in the
queue after closing the case to trigger the defined OnAfterClose event.
Corrected.
TIBCO iProcess Engine Release Notes
28
|
Release Notes
Defect #
Description
IPE-3314
The TIBCO iProcess Engine user successfully logged in through TIBCO
iProcess Workspace (Browser) with an expired and unusable password.
(Parent JIRA
IPE-3305)
IPE-3315
(Parent JIRA
IPE-3307)
IPE-3324
Implemented.
After changing password for a user while its SAL session was available, the
TIBCO iProcess Engine user failed to log in with the new password.
Implemented.
The file descriptors leak occurred when the IAPJMS process sent messages to
TIBCO Enterprise Message Service, which was not running.
Corrected.
IPE-3326
The DBQD process was continually recording useless messages into the
log file, which was located in the SWDIR/logs/process
directory.
DBQD_1_stdout
Corrected.
IPE-3329
When creating a procedure with a Message Event Request (MER) message, the
record of the last deleted procedure, which was monitored by its MER
message, was not removed from the iap_monitor table and was used for the
newly created procedure.
Corrected.
IPE-3331
TIBCO iProcess Objects Server crashed when filtering work items by using F2
filter through the Work Item Server if one of the filter strings for a field
exceeded 512 characters, which is the maximum capacity.
Corrected.
IPE-3332
(Parent JIRA
IPE-3304)
Error messages were recorded in the audit trail of a case when starting the
sub-case if a script was mapped from a field of the procedure to a MEMO field
of its sub-procedure.
Corrected.
IPE-3335
A deadlock occurred in the iProcess Objects Server cache of procedures.
(Parent JIRA
IPE-3334)
Corrected.
TIBCO iProcess Engine Release Notes
Change History 29
|
Defect #
Description
IPE-3341
The error message "cannot start a new transaction" was reported in the
sw_error file when deleting user information if EAICOM was registered in
TIBCO iProcess Engine.
(Parent JIRA
IPE-3333)
Corrected.
IPE-3343
(Parent JIRA
IPE-3342)
The procedure information was missing when TIBCO iProcess Objects (C++
and Java) requested for the procedure information from iProcess Objects Server
if the procedures were newly created or updated.
Corrected.
IPE-3344
An iProcess Objects Server timeout exception was reported when TIBCO
iProcess Workspace (Browser) client sent a message to the iProcess Objects
Server process if the message capacity was exceeded.
Corrected.
IPE-3358
(Parent JIRA
IPE-3346)
IPE-3359
(Parent JIRA
IPE-3348)
More logs have been added to trace the information of the locks in the
CIndex_MUTEX lock pool used by the WIS process.
Implemented.
A deadlock occurred which caused all the "worker" threads and the update
thread in WIS process were suspended when more than one "worker" thread
were processing the WIS session simultaneously.
Corrected.
IPE-3361
Add the TIBCO Enterprise Message Service 8.0 option for Java Message Service
provider when installing TIBCO iProcess Engine.
Implemented.
IPE-3364
TIBCO iProcess Server Manager was not displayed correctly in Internet
Explorer and Firefox.
Note: For Internet Explorer, you must use the compatibility view to display
TIBCO iProcess Server Manager.
Corrected.
IPE-3365
TIBCO iProcess Engine provides a new interface for setting priority for
purging and closing messages with SSO.
Implemented.
TIBCO iProcess Engine Release Notes
30
|
Release Notes
Defect #
Description
IPE-3366
TIBCO iProcess Objects Server uses the new SAL interface to support setting
priority for purging and closing messages with SSO.
Implemented.
IPE-3369
Add the EXACT_OPERATION_TIMESTAMP attribute to record in the audit trail
either when the user does a specified operation or when BG or RPCBG processes
an instruction.
Implemented. See Exact Timestamps for Instructions in Audit Trail (IPE-3369).
IPE-3373
When starting TIBCO iProcess Engine, the IAPJMS process was not started if
using JBoss EAP 6.1 after installing TIBCO iProcess Engine with JBoss selected
as the JMS provider.
Corrected.
IPE-3374
When starting TIBCO iProcess Engine, the IAPJMS process was not started if
using IBM WebSphere 7.x or 8.x after installing TIBCO iProcess Engine with
IBM WebSphere V7.x selected as the JMS provider.
Corrected.
IPE-3375
(Parent JIRA
IPE-3367)
IPE-3379
An error occurred when using TIBCO iProcess Server Objects to start a new
case of a procedure which was released recently.
Corrected.
A transaction was not committed or rolled back when using the PROCMGR
process to run the SELECT SQL statement in a loop.
Corrected.
IPE-3381
Database scripts did not run sucessfully if using the scripts the second time
when upgrading TIBCO iProcess Engine to version 11.4.1.
Corrected.
IPE-3383
(Parent JIRA
IPE-3371)
IPE-3384
(Parent JIRA
IPE-3370)
TIBCO iProcess Objects Server supports the extension of the length of the login
password for TIBCO iProcess Engine to 32,768 bytes.
Implemented.
The length of a password used for logging into TIBCO iProcess Engine, has
been extended to 32,768 bytes.
Implemented.
TIBCO iProcess Engine Release Notes
Change History 31
|
Defect #
Description
IPE-3385
Upgrade Tomcat to version 7.0.52.
Implemented.
IPE-3386
Update TIBCO iProcess Engine to use new TIBCO logo.
Implemented.
Release 11.4.0
Defect #
Description
IPE-163
An error occurred when checking permissions of the running users due to the
user name being case-sensitive on Windows systems.
Corrected.
IPE-2975
Add the RESTART_SPO_CACHE_PROC process attribute to define how many of
the latest versions of the procedure definition will be cached by the iProcess
Objects Server processes when restarting or quick starting iProcess Engine.
Add the SPO_CACHE_PROC process attribute to define this behavior when
starting iProcess Engine normally.
Implemented. See Define how many of the Latest Versions of Procedure
Definition to be Cached (IPE-2975) on page 8.
IPE-2976
Add a new option –q to the swstart command for quick starting iProcess
Engine.
Implemented. See Enable Quick Start Mode (IPE-2976) on page 8.
IPE-2990
The RESTART_WIS_CACHE_THRESHOLD process attribute, defining the threshold
number of work items in a work queue, is added to determine whether to
cache all the work items in the work queue when a WIS process restarts or
quick starts.
Implemented. See Define the Minimum Size of a Work Queue to Cache on a
Restart (IPE-2990) on page 9.
IPE-3014
The CNUM_SEQ_CACHE and REQID_SEQ_CACHE attributes are applied to SSOLITE
for SQL Server and DB2 databases. The default values of CNUM_SEQ_CACHE and
REQID_SEQ_CACHE attributes for SSOLITE on SQL Server and DB2 are changed
to 10.
Implemented.
TIBCO iProcess Engine Release Notes
32
|
Release Notes
Defect #
Description
IPE-3016
The procedure level event is added to TIBCO iProcess Engine to record
information about cases that are interrupted by triggered events when
processing the purge, close, resurrect, suspend, or resume operation.
Implemented. See Procedure Level Events (IPE-3016) on page 9.
IPE-3017
Changed the default values of the CNUM_SEQ_CACHE and REQID_SEQ_CACHE
process attributes to 5 for the iProcess Objects, and SSOLITE on Oracle.
Changed the default value of the WIS_UPDATE_PERIOD attribute to 20.
Corrected.
IPE-3019
Add support to delay the case auto-purge operation and to set case deadlines.
Implemented. See Set Auto-Purge and Deadlines for Cases (IPE-3019) on
page 10.
IPE-3020
(Parent JIRA
IPE-2978)
IPE-3028
The message priority was not controlled by setting the value of the
field through TIBCO ActiveMatrix BusinessWorks Plug-in.
SW_CP_VALUE
Corrected.
Upgrade Java from version 1.6 to 1.7 on all platforms of TIBCO iProcess
Engine.
Implemented.
IPE-3036
An error message was logged in the seo_error log when starting TIBCO
iProcess Objects Server after upgrading iProcess Engine to version 11.3.1.
Corrected.
IPE-3037
(Parent JIRA
IPE-3018)
IPE-3038
(Parent JIRA
IPE-2967)
The EAI SQL step failed when inserting more than 4,000 characters into a
memo field.
Corrected.
Mapping from the sub-procedure fields to expressions continued after the
"sal_validsh (): session_lock (21248) failed" error occurred, resulting
in incorrect mappings.
Corrected.
IPE-3039
(Parent JIRA
IPE-2981)
Users imported from the LDAP Server could log in through TIBCO iProcess
Workspace (Windows) or TIBCO iProcess Workspace (Browser) with an
incorrect password.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 33
|
Defect #
Description
IPE-3040
The trigger event operation did not work when the case number was greater
than 2147483647.
(Parent JIRA
IPE-3004)
IPE-3041
(Parent JIRA
IPE-3005)
IPE-3042
(Parent JIRA
IPE-3025)
Corrected.
When releasing a script, the CALL function did not work if the scriptname
parameter in the function was not enclosed in double quotation marks.
Corrected.
When using the JumpTo function to jump from main procedures to dynamic
sub-procedures, the "unexpected exception, Message Item not found."
error message was reported.
Corrected.
IPE-3043
(Parent JIRA
IPE-3030)
If the user name of a case had been changed, for example, changing S02460 to
s02460, the original user was inserted into the leavers and redir_defn tables
as a recently deleted user.
Corrected.
IPE-3044
(Parent JIRA
IPE-3015)
The following error message was displayed when starting cases through
SSOLite on SQL Server 2012:
Unable to create DMO connection, check user is system
administrator.
Corrected.
IPE-3045
(Parent JIRA
IPE-2974)
When attempting to release a work item, which contained fields with
validations, error messages were generated in the TIBCO iProcess Objects
Server log file.
Corrected.
IPE-3046
(Parent JIRA
IPE-2994)
When creating an XList of work items from a queue by using TIBCO iProcess
Objects (COM) and looping through the XList to lock each work item, after the
first work item was locked and then released, other work items failed to be
locked.
Corrected.
IPE-3035
The NOLOCK hint is applied in SQL Server when the PROCMGR processes are
running the select count (*) command on the Mbox tables.
Implemented.
TIBCO iProcess Engine Release Notes
34
|
Release Notes
Defect #
Description
IPE-3047
A deadlock occurred when upgrading TIBCO iProcess Engine from a previous
version to 11.3.0 and then to 11.3.1 due to incorrectly clustered indexes on the
rowid and priority columns.
(Parent JIRA
IPE-2989)
Corrected.
IPE-3052
Add the swadm EVLOOPBACK command to test event mechanism manually, and
report error messages if events do not work.
Implemented. See Test the Event Mechanism Manually (IPE-3052) on page 10.
IPE-3055
IPv6 addresses are supported on Windows and Linux systems.
Implemented. See Additional IP Addresses Support (IPE-3055) on page 10.
IPE-3072
(Parent JIRA
IPE-3048)
After cases were migrated to a new procedure version by using the swutil
IMPORT +c command, duplicated work items were displayed in a case when
triggering an event.
Corrected.
IPE-3073
Case start was slow after installing TIBCO iProcess Engine 11.3.0_HF-008.
(Parent JIRA
IPE-3053)
Corrected.
IPE-3078
After migrating existing cases of a procedure to a new version, the existing
cases were still in the old version.
Corrected.
IPE-3083
An error was returned when clicking the Load Known Agents button on the
iProcess Server Manager page.
Corrected.
IPE-3088
An error message was not displayed when an LDAP attribute was mapped for
more than one iProcess property.
Corrected.
IPE-3090
The F3 filter failed to filter work items via Case Data Queue Parameter (CDQP)
if the field held 255 characters, the maximum capacity.
Corrected.
TIBCO iProcess Engine Release Notes
Change History 35
|
Defect #
Description
IPE-3096
The MEMATTS sections in the old version and new version of the procedures
did not match after the XFR file was imported by using the SWUTIL command.
Corrected.
IPE-3115
After you have forwarded a work item from a cached queue to another queue
to be cached, the work item was not displayed in the destination queue.
Corrected.
IPE-3116
Only iProcess Engine database user (swuser) account is used to connect to
databases.
Implemented.
IPE-3122
(Parent JIRA
IPE-3063)
IPE-3126
(Parent JIRA
IPE-3101)
IPE-3145
(Parent JIRA
IPE-3131)
When the BG process failed to handle the SUBDONE message because of a
deadlock, the BG process did not roll back the affected transaction.
Corrected.
Chinese characters were not retrieved correctly by using iProcess Server
Objects (Java) if they were split by TIBCO iProcess Objects Server.
Corrected.
An error occurred when using the output mapping script to assign the
sub-procedure output values to the Date type and Time type fields of the main
procedure.
Corrected.
IPE-3155
The archived log files were not deleted as per the LogFileMaxArchives
setting.
Corrected.
IPE-3156
(Parent JIRA
IPE-3144)
The user defined attributes of Group were missing after synchronizing iProcess
user data with the LDAP directory by using the LDAPCONF utility.
Corrected.
IPE-3177
If an error occurred when closing a case, the BG process did not catch the error
nor roll back the transaction.
IPE-3205
Upgrade Tomcat from version 6.0.35 to 7.0.40.
Implemented.
TIBCO iProcess Engine Release Notes
36
|
Release Notes
Defect #
Description
IPE-3209
The background (BG) processes crashed because iProcess Engine unexpectedly
released memory addresses twice. Also, a memory leak occurred in the BG
processes.
(Parent JIRA
IPE-3189)
Corrected.
IPE-3237
(Parent JIRA
IPE-3231)
IPE-3243
(Parent JIRA
IPE-3240)
When you close or purge a case that contains sub-cases, delete certain
audit_trail entries to reduce the number of returned sub-cases.
Implemented.
After importing a new version of a procedure by using the SWUTIL command,
MEMO fields are created for the new version of the procedure referencing the
same MEMO ID.
Corrected.
TIBCO iProcess Engine Release Notes
Restrictions 37
|
Restrictions
The table in this section lists known restrictions in this release.
Defect #
Summary/Workaround
IPE-3113
Summary An error occurs when loading XPDL for a procedure library with any
new functionality into iProcess Workspace (Windows), if the procedure library is
saved as XPDL from a later version of TIBCO iPrcoess Engine, and loaded into an
earlier version of TIBCO iProcess Engine.
Workaround TIBCO does not recommend that you import procedures, which are
exported from a later version of TIBCO iProcess Engine, to an earlier version of
TIBCO iProcess Engine.
See TIBCO iProcess swutil and swbatch Reference Guide for more information.
MR 40988
Summary When a procedure is exported to an XPDL file from TIBCO iProcess
Workspace (Windows), no list or table information is included.
Workaround None.
MR 35194
Summary The iProcess Server Manager does not support language translation.
Workaround None.
CR 19525
Summary A temporary file is always left behind when installing the iProcess
Engine, whether the installation is successful or not. The location of the file is
defined by the TEMP system variable. The name of the file is _ISTMPn.DIR where n
is a number that increments each time you install the iProcess Engine. For example,
_ISTMP1.DIR, _ISTMP2.DIR and so on.
Workaround Manually delete the temporary file(s) once the iProcess Engine
installation is complete.
CR 19301
Summary Installation fails if the username of the background user starts with a
numeric; for example, 1swpro.
Workaround Define the background user to start with an alphabetic character.
CR 19010
Summary If the WIS process handles an update event (for example, from a
SWDIR\bin\swutil EVENT -p command) while a user has a work item open, the
Case Description and WQ Parameters revert to the values they had prior to the
update when the work item is kept.
Workaround None.
TIBCO iProcess Engine Release Notes
38
|
Release Notes
Defect #
Summary/Workaround
CR 18799
Summary If lots of MOVESYSINFO operations are being performed by BG
processes, then the other processes that have to recache the user/group information
might fail due to becoming deadlocked.
It is also possible that the caching process might load group membership or attribute
values that don't match the attributes or queues loaded. This is because the caching
process would first load the queues, then the attributes and finally the attribute
values. If a MOVESYSINFO changed the attribute values before they were loaded
then they may not match the attributes that were loaded prior to the
MOVESYSINFO.
Workaround Once all operations have been completed, modify the user/group area
and perform one last MOVESYSINFO.
CR 18631
Summary If you have an outstanding test mail item for an unreleased procedure and
you delete the step from the procedure that the outstanding mail refers to, the test
mail item can no longer be accessed. This is to be expected as the step has been
deleted from the procedure. However, if you then purge the case for this inaccessible
step the case is purged but the item is never removed from the message queue.
Workaround Clean up the item using the swutil CLEANITEM command.
CR 18614
Summary When a user logs in to the iProcess Workspace (Windows) test queues are
not displayed in Work Queue Manager. This is because the user's personal work
queue (from which the test queues are created) has not been cached yet.
Workaround If a new work item is sent to a test queue this causes the Rebuild List
button to appear. Alternatively, the user can select their personal work queue and
press F5. This also causes the Rebuild List button to appear. Clicking Rebuild List
displays the test queues.
CR 18467
Summary TIMEZONE setting does not correctly handle daylight savings time on
Windows for zones that do not use North American rules.
Workaround None.
TIBCO iProcess Engine Release Notes
Restrictions 39
|
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 <Emphasis>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.
CR 16878
Summary Filtering a view of a case via the TIBCO iProcess Objects Server with a
filter expression that uses a Question mark (?) or Asterisk (*) 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 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.
TIBCO iProcess Engine Release Notes
40
|
Release Notes
Defect #
Summary/Workaround
CR 15444
Summary During the upgrade process, the iProcess Engine services are deleted and
then re-created. If the Services window is open during this process the system will
not actually delete the service but will mark it for deletion, which will be performed
at the next reboot.
Workaround If this error occurs during upgrade you will need to reboot the machine
and re-run the upgrade process.
CR 15334
Summary When you upgrade from a Version 9 Process Engine the entries in the
at_id column of the audit_trail table are migrated to the audit_usecs column. at_id
values that are greater than 1 million are truncated after upgrade, which means that
the correct ordering of audit trail rows is lost.
This is only an issue when the number rolls over from 6 to 7 digits and the audit trail
items are from the same case and have the same timestamp. If all the numbers are
above 6 digits then all entries are truncated and ordering is preserved.
Workaround None.
CR 15319
Summary If you change the date separator in the SWDIR\etc\staffpms file to a
hyphen (-):
•
when you enter a date field in a form the separators are displayed correctly, but
change to backslash characters (/) when you tab off the field.
•
when you release the form, one or more background processes crash.
Workaround None.
CR 15311
Summary The following fields do not appear in the Available Fields list of fields in
the Inputs or Outputs tab for iProcess Engine plug-ins:
•
SW_IP* Fields
•
SW_STEPNAME
•
SW_STEPDESC
Workaround None.
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.
TIBCO iProcess Engine Release Notes
Restrictions 41
|
Defect #
Summary/Workaround
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 14225
Summary When viewing cases, filter criteria that use the Question mark (?) (such as
SW_CASENUM ? "2") or regular expressions using the same character
(SW_CASENUM ? "1234?") will fail.
Workaround Either:
CR 12037
•
Use the Equal sign (=) instead; for example, SW_CASENUM = "2", or
•
Use a Asterisk (*) 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.
Summary You should not use any of the following special characters when naming
new groups, roles, lists or tables:
" \ / [ ] : ; | = , + * ? < > @ \0 "
Workaround None.
CR 12001
Summary The iProcess Engine’s DNS Host Name must be identical (including case)
to its Computer Name. If these names are different, users will not be able to log in to
this iProcess Engine from the TIBCO iProcess Workspace (Windows).
Workaround To make sure the names are identical:
1. In Control Panel, double-click the System icon. The System Properties dialog is
displayed.
2. On the Network Identification tab, click Properties. The Identification
Changes dialog is displayed.
3. Click More. The DNS Suffix and NetBIOS Computer Name dialog is
displayed.
4. Note the Primary DNS suffix of this computer. If it is not already the same,
change this name to match the NetBIOS computer name.
TIBCO iProcess Engine Release Notes
42
|
Release Notes
Defect #
Summary/Workaround
CR 11428
Summary During the starting or stopping of the iProcess Engine, there can be a
pause of 60 seconds between a process (once shutdown) publishing an event and all
the subscribers receiving it. This makes it look like the system has not fully
shutdown or started up. This is a problem with the COM+ Events system and a
resolution is being sought from Microsoft.
Workaround None.
TIBCO iProcess Engine Release Notes
Known Issues 43
|
Known Issues
This section lists known issues in the current release.
Summary
Summary TIBCO iProcess Engine fails to be moved to another machine in the
same Microsoft Windows cluster by using Move To option in the Failover
Cluster Administrator.
Workaround Before moving TIBCO iProcess Engine to another machine in the
same Microsoft Windows cluster in the Failover Cluster Administrator, run the
following command at the command prompt:
SWDIR\util\swadm move_server machine_id machine_name
where:
— machine_id is the server identifier of the source server, such as, 1, 2, 3.
— machine_name is the name of the Microsoft Distributed Transaction
Coordinator resource (MSDTC). See "What is MSDTC" in TIBCO iProcess
Engine Architecture Guide for more information.
Summary After installing TIBCO iProcess Engine on a Microsoft Windows
platform, an iProcess Engine service user without the local administrator rights
cannot start the iProcess Engine services if User Access Control (UAC) is
enabled on the Microsoft Windows platform.
Workaround Disable User Access Control (UAC) on the Microsoft Windows
platform.
TIBCO iProcess Engine Release Notes
44
|
Release Notes
Summary
Summary TIBCO iProcess Engine Server Manager cannot work with TIBCO
HAWK (64bit) on the Microsoft Windows platforms.
Workaround Follow these steps:
1. Back up the tomcat and java folders under SWDIR.
2. Copy the 64bit tomcat and JDK folder to SWDIR and rename them to
tomcat and java respectively.
3. Copy the ipsvrmgr folder and iProcessReports.war file under the
backed-up tomca\webapps folder to SWDIR\tomcat\webapps folder.
4. Delete contents under SWDIR\tomcat\work.
5. Rename the tomcat6.exe and tomcat6w.exe files under the
SWDIN\tomcat\bin folder to tomcat5.exe and tomcat5w.exe.
6. Restart TIBCO iProcess Engine.
Summary Work items cannot be seen in the work queue when configuring
IAPJMS
for JBoss.
Workaround Follow these steps:
1. Copy JBOSS_HOME/client/log4j.jar to $SWDIR/jar/thirdpart/
2. Open the SWDIR/etc/iapjms_classpath.properties configuration file
and replace classpath.internal.log4j=thirdparty/log4j-1.2.8.jar
with classpath.internal.log4j=thirdparty/log4j.jar
3. Restart TIBCO iProcess Engine.
Summary 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.
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.
TIBCO iProcess Engine Release Notes
Known Issues 45
|
Summary
Summary Services are not removed correctly if the Microsoft Management
Console dialog is open.
If the Microsoft Management Console dialog is open and a service is stopped
and then deleted, the Startup Type of the service can be shown as Disabled.
The service will be removed when the Microsoft Management Console dialog
is closed.
The problem does not occur if you are using command line utilities. This is a
known problem documented in the Microsoft Knowledge Base.
Summary Disabling cached logon information in a domain environment.
By default, Windows Server 2008 R2 caches previous users’ logon information
locally. This ensures that users can log on if a domain logon server is
unavailable during subsequent logon attempts. However, this feature could
result in users with invalid passwords still being able to log on to the iProcess
Suite. For example, a user whose password has been changed attempts to
logon to the iProcess Suite with their old password. If the domain controller is
not available to validate the current password but the old password is still
cached locally, the logon attempt will be accepted.
You can prevent this from happening by disabling the cached logon
information feature in Windows Server 2008 R2. If you do this, a user will not
be able to logon to the iProcess Suite if the domain controller is not available to
validate their password.
For more information about how to disable logon caching, refer to the Cached
Logon Information article (Article ID: Q172931), available from the Microsoft
Personal Support Centre at:
http://support.microsoft.com
TIBCO iProcess Engine Release Notes
46
|
Release Notes
Summary
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.
Summary Large Number of User Logins May Cause Problems.
If your client application performs a large number of user logins to the iProcess
Engine, it may experience problems that are a result of running out of TCP
ports, or attempting to connect to a TCP port above 5000. You may see one of
the following problems in the client application or the iProcess Engine:
•
the system hanging or exhibiting unexpected behavior
•
unable to create new connections to the server
•
Event ID 2009 “Number of sessions exceeds 2048” may be written to the
event log
•
the local computer responds with a WSENOBUFS (10055) error
For information about resolving these issues, refer to Microsoft Knowledge
Base articles Q149532 and Q196271. These can be found at:
http://support.microsoft.com.
Summary Same user logged on multiple times causes degradation/possible
errors.
The same user logging on multiple times to the same iProcess Engine may
result in performance degradation. The iProcess Engine will allow only one
transaction to be processed at a time for users that are logged on multiple times
to that server, resulting in slower processing.
TIBCO iProcess Engine Release Notes
Known Issues 47
|
Summary
Summary Locking work items.
The SAL SDK allows long locking multiple times by the same user name. Consequently, in the iProcess Engine, it is possible to lock the same work item from
a work queue using a different login session if there are two or more clients
logged in as the same user name.
Summary Text field attribute lengths stored in multiples of 24.
All attributes except for text fields are set to a length of 24 if a length is not
specified or if some length (up to 24) is specified. Decimal places are not stored.
For text fields, length is set to 24 if no length is specified. If a length is specified,
the actual length will be the next multiple of 24, up to the maximum length of
255. For example, creating a text field 25 characters long will result in the field
actually being 48 characters long.
Summary Audit filtering limitations on sub-cases.
When specifying an audit filter for a sub-case, or a parent case that contains a
sub-case, the following limitation applies: If your filter criteria does not match
the sub-case started audit entry in the parent case, no audit entries are returned
for the sub-case, regardless of whether the filter criteria matches audit entries
of the sub-case.
The work around for this is to specify the following in your AuditFilterExpr filter expression:
FILTER_FLAGS=[AF_ALL_SUBSTART]
TIBCO iProcess Engine Release Notes
48
|
Release Notes
Other Information
Installing the iProcess Engine Against a SQL Server Instance That Uses
“Windows Only” Authentication
If you want to install the iProcess Engine against a SQL Server instance that uses
“Windows Only” authentication (so that the iProcess Engine must use
Windows-authenticated accounts to access the SQL Server instance), you must
modify the installation procedures described in the TIBCO iProcess Engine (SQL
Server) Installation guide as described below.
Note that:
•
If there is any conflict between the following modifications and the
information in the Installation guide, the information here takes precedence.
•
Any information, steps or procedures that are not explicitly mentioned here
remain as described in the Installation guide.
•
If you are still unsure about how to proceed with the installation, please
contact TIBCO Support for further assistance.
1. Manually create the iProcess Engine database and logins
If you want the iProcess Engine to use Windows-authenticated accounts to access
the SQL Server instance, Setup cannot create the iProcess Engine database and
logins for you. You must manually do this before you run Setup. Perform the
following steps:
1. Follow steps 1 to 9 of the procedure described in the section “Create the SQL
Server Database and Logins“ in the Installation guide (at the appropriate point
in your pre-installation procedures).
2. Create the IPE DB Owner and IPE DB User SQL Server login IDs. To do this
(for each login):
a. Expand Security, right-click Logins, then click New Login.
b. In the Name field, enter (or use the Browse button to select) the
appropriate Windows user for the login. You can use any name you want
to, but the suggested ones are swpro for the IPE DB Owner and swuser for
the IPE DB User.
The name must be a domain or machine qualified account name in the form
"DOMAIN\username". For example, “EMEA\swpro”.
TIBCO iProcess Engine Release Notes
Other Information 49
|
c. Select Windows Authentication, the appropriate Domain, and Grant
Access.
d. Click OK.
3. Add these login IDs as users in the iProcess Engine database. To do this:
a. Expand the iProcess Engine database, right-click Users, then select New
Database User.
b. In the Login name field, select the login ID you just created. The User
name field is automatically filled in with the same name.
c. In the User name field, delete the DOMAIN\ component, leaving just the
user name. For example, if the Login name field is “EMEA\swpro”, edit
the User name field to be “swpro”.
d. In the Database role section, select the db_owner check box for the IPE DB
Owner user, or db_datareader for the IPE DB User user.
e. Click OK.
4. Continue with steps 11 to 14 of the procedure described in the section “Create
the SQL Server Database and Logins“ in the Installation guide.
2. Completing the Setup Type dialog
When you run Setup, in the Setup Type dialog, select Custom.
3. Completing the SQL/ODBC Details dialog
In the SQL/ODBC Details dialog:
1. Select Enter a new ODBC Data Source and enter a name for the new ODBC
data source.
2. Select the SQL Server that you have set up (above) to connect to.
3. Select the Use Integrated Windows authentication check box.
4. Clear the You have DBA privileges check box.
4. Completing the Database Details dialog
In the Database Details dialog:
1. In the Database name field, enter the name of the database you created earlier.
TIBCO iProcess Engine Release Notes
50
|
Release Notes
2. In the iPE DB Owner login and iPE DB User login fields, enter the database
User names that you entered for these accounts above.
Do not enter the (fully qualified) Login names. Make sure that you use just the
simple username, without the DOMAIN\ component. For example, enter
“swpro”, not “EMEA\swpro”.
Using SWDIR\util\plist
You can use the SWDIR\util\plist X option to provide backwards compatibility
with Staffware 2000. For example, using plist -pv does not report counts, but you
can use plist -pvX to specify Staffware 2000 compatibility so that counts are
derived. Enter SWDIR\util\plist at the command line to display a full list of
options.
Must Normalize Case Data to View Cases
When you install the iProcess Engine, there is a check box in the Configuration
window that is used to enable a feature called CaseData Normalization. If you are
using an application developed with iProcess Objects or iProcess Server Objects,
you must enable case data normalization. If it is not enabled, cases will not appear
in the case list.
Case data normalization can be enabled either during the installation, or at a later
time using the Case Data Normalization utility, swnormcd.
For more information about case data normalization and using swnormcd, see
TIBCO iProcess Engine Administrator’s Guide.
Large Number of User Logins May Cause Problems
If your client application performs a large number of user logins to the iProcess
Engine (for example, in a stateless or web environment), it may experience
problems that are a result of running out of TCP ports, or attempting to connect to
a TCP port above 5000. You may see one of the following problems on either the
client or iProcess Engine:
•
the system suspending or exhibiting unexpected behavior
•
unable to create new connections to the server
•
Event ID 2009 "Number of sessions exceeds 2048" may be written to the event
log
•
the local computer responds with a WSENOBUFS (10055) error
TIBCO iProcess Engine Release Notes
Other Information 51
|
Upgrading from Earlier Version May Cause Error Messages in Log File
Upgrading from an earlier version of the iProcess Engine to version i10.0 (0.0) or
later may cause error messages similar to the following to appear in the iProcess
Engine log file:
ERROR|error in sal_pver_audlist procname($EMAIL) err(0) curridx(1)
ERROR|error in sal_pver_audlist procname($SYSTEM) err(0)
curridx(1)
ERROR|error in sal_pver_audlist procname(CARPOOL) err(0)
curridx(1)
These messages are a result of the upgrade, but an error has not occurred.
Disregard the messages.
TIBCO iProcess Engine Release Notes
52
|
Release Notes
TIBCO iProcess Engine Release Notes
Was this manual useful for you? yes no
Thank you for your participation!

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

Download PDF

advertisement