Process Monitor Server Release Notes
Server - Release Notes
ProcessMonitor Server
Release Notes
Software Release 3.0.1
Published: November 2014
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 LICENSE FILE) OR IF THERE IS
NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S)
LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE
BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws
and treaties. No part of this document may be reproduced in any form without the written authorization of
TIBCO Software Inc.
TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Administrator,
TIBCO Enterprise Message Service, TIBCO InConcert, TIBCO Policy Manager, and TIBCO Hawk are either
registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.
EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING
SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README
FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE
PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW
EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE
PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY
OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY
RELEASE NOTES AND "READ ME" FILES.
Copyright © 2001-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
Contents
Release Notes
Installation
6
................................................................................................................................... 6
Release 3.0.1
.......................................................................................................................................................... 6
New Install
......................................................................................................................................................... 6
Upgrade from 3.0.0.x
......................................................................................................................................................... 6
Upgrade from 2.x release......................................................................................................................................................... 10
Release 3.0
.......................................................................................................................................................... 15
New Install
......................................................................................................................................................... 15
Upgrade
......................................................................................................................................................... 15
New Features ................................................................................................................................... 20
Release
Release
Release
Release
Release
Release
3.0.1
3.0
2.2
2.1.2
2.1.1
2.0
.......................................................................................................................................................... 20
.......................................................................................................................................................... 20
.......................................................................................................................................................... 21
.......................................................................................................................................................... 23
.......................................................................................................................................................... 23
.......................................................................................................................................................... 23
Change in functionality
................................................................................................................................... 24
Release
Release
Release
Release
Release
Release
Release
3.0.1
3.0
2.2.1
2.2
2.1.2
2.1.1
2.0
Bug fixes
Release
Release
Release
Release
Release
Release
Release
.......................................................................................................................................................... 24
.......................................................................................................................................................... 24
.......................................................................................................................................................... 24
.......................................................................................................................................................... 25
.......................................................................................................................................................... 25
.......................................................................................................................................................... 25
.......................................................................................................................................................... 25
................................................................................................................................... 26
3.0.1
3.0
2.2.1
2.2
2.1.2
2.1.1
2.0
.......................................................................................................................................................... 26
.......................................................................................................................................................... 27
.......................................................................................................................................................... 30
.......................................................................................................................................................... 32
.......................................................................................................................................................... 33
.......................................................................................................................................................... 34
.......................................................................................................................................................... 36
Deprecated Features
................................................................................................................................... 37
Release
Release
Release
Release
Release
Release
Release
3.0.1
3.0
2.2.1
2.2
2.1.2
2.1.1
2.0
Compatibility
Release
Release
Release
Release
Release
Release
3.0.1
3.0
2.2.1
2.2
2.1.2
2.1.1
.......................................................................................................................................................... 37
.......................................................................................................................................................... 37
.......................................................................................................................................................... 37
.......................................................................................................................................................... 37
.......................................................................................................................................................... 37
.......................................................................................................................................................... 37
.......................................................................................................................................................... 37
................................................................................................................................... 38
.......................................................................................................................................................... 38
.......................................................................................................................................................... 38
.......................................................................................................................................................... 38
.......................................................................................................................................................... 38
.......................................................................................................................................................... 38
.......................................................................................................................................................... 38
Release 2.0
Restrictions
.......................................................................................................................................................... 38
................................................................................................................................... 40
Release Notes
Installation
Release 3.0.1
New Install
To install this version, follow the instructions of the BWPM Installation Manual.
Upgrade from 3.0.0.x
Upgrade Prerequisite for Oracle DB:
Ensure the database user you use for the execution of the database script has the
following privileges, otherwise you may ask your DBA to execute the database upgrade
script:
Resource
Connect
Create Job, Create Materialized View, Create Procedure, Create Sequence,
Create Table, Create Trigger, Create View
Upgrade Prerequisite for MS SQL Server:
Ensure the database user is assigned to role SQLAgentUserRole and has SELECT
permission for the following objects:
msdb.dbo.sysjobactivity
msdb.dbo.sysjobs
msdb.dbo.sysjobhistory
msdb.dbo.sysjobschedules
|6
msdb.dbo.sysschedules
Please consider:
The execution of the database upgrade script may take some time. Depending on
your database size the migration script can take several hours to complete. Please
validate that the TIBCO EMS server provides enough storage for incoming log
message for the duration of the migration.
To upgrade from a 3.0.0.x release follow this procedure:
1) Stop the data providers, shutdown the web application and undeploy the current
version of TIBCO BusinessWorks(TM) Process Monitor application.
2) Deploy bwpm.war on your Apache Tomcat Server. For further information consult the
installation manual "Installaing TIBCO BusinessWorks(TM) Process Monitor
Server.pdf"
3) Start the application
4) Your browser might have cached an older version of bwpm. Please make sure to
delete your browser cache and reload your login page in your browser.
Firefox: press CTRL+SHIFT+DEL and confirm the dialog that appears.
Internet Explorer: press CTRL+SHIFT+DEL or open Settings menu, select Safety, and
click on Delete browsing history. In the dialog window select Temporary Internet files
and deselect Preserve Favorite website data.
5) Go to the BWPM web page and log in as administrator. The following dialog will be
displayed:
|7
If you select Download you can download the migration script.
To automatically migrate the database to the latest version click “Migrate”. The
following Warning message lets you confirm or cancel the execution of the migration
script:
To download the SQL file that contains all required changes click on “Download”. That
file can be reviewed and loaded into the DB by a DBA (instead of using the automatic
migration feature).
BWPM will inform you when the migration process has been finished.
|8
Note: until the migration script has been executed, no user can access the BWPM web
application. The following warning message will be displayed:
6) Log in as an administrator.
7) Navigate to Administration - System Management Start the data providers as
described in the user guide.
8) The system is now upgraded to version 3.0.1
|9
Upgrade from 2.x release
Upgrade Prerequisite for Oracle DB:
Ensure the database user you use for the execution of the database script has the
following privileges, otherwise you may ask your DBA to execute the database upgrade
script:
Resource
Connect
Create Job, Create Materialized View, Create Procedure, Create Sequence,
Create Table, Create Trigger, Create View
Upgrade Prerequisite for MS SQL Server:
Ensure the database user is assigned to role SQLAgentUserRole and has SELECT
permission for the following objects:
msdb.dbo.sysjobactivity
msdb.dbo.sysjobs
msdb.dbo.sysjobhistory
msdb.dbo.sysjobschedules
msdb.dbo.sysschedules
| 10
Please consider:
The execution of the database upgrade script may take some time. Depending on
your database size the migration script can take several hours to complete. Please
validate that the TIBCO EMS server provides enough storage for incoming log
message for the duration of the migration.
The execution of the post-migration script is optional and needs only be executed
to migrate historic track information. If you do not execute the post-migration
script, historic process instances (executed before the time of upgrading the
installation) will not show execution paths. All new instances (executed after
upgrading the server) will have correct execution path information.
The post-migration script can be executed any time after the server has been
upgraded. It can run in the background while the server is processing data.
Depending on the size of the table to migrate, the script may run multiple hours. It
can be stopped and restarted at any point in time while running, without risk of
loosing or corrupting data.
To upgrade from a 2.x release follow this procedure:
1) Stop the data providers, shutdown the web application and undeploy the current
version of TIBCO BusinessWorks(TM) Process Monitor application.
2) Deploy bwpm.war on your Apache Tomcat Server. For further information consult the
installation manual "Installaing TIBCO BusinessWorks(TM) Process Monitor
Server.pdf"
3) Start the application
4) Your browser might have cached an older version of bwpm. Please make sure to
delete your browser cache and reload your login page in your browser.
Firefox: press CTRL+SHIFT+DEL and confirm the dialog that appears.
Internet Explorer: press CTRL+SHIFT+DEL or open Settings menu, select Safety, and
click on Delete browsing history. In the dialog window select Temporary Internet files
and deselect Preserve Favorite website data.
5) Go to the BWPM web page and log in as administrator. The following dialog will be
displayed:
| 11
If you select Download you can download the migration script as well as the postinstallation script (which is optional):
Please consider:
By default the historic track information will not be migrated. In order to continue to
have the historic track information, you need to execute the post-migration script. If
you are going to migrate from any version prior 2.1 and the migration of the historic
track information is required, please contact TIBCO Support to get detailed
information about how to proceed.
To automatically migrate the database to the latest version click “Migrate”. The
following Warning message lets you confirm or cancel the execution of the migration
script:
| 12
To download the SQL file that contains all required changes click on “Download”. That
file can be reviewed and loaded into the DB by a DBA (instead of using the automatic
migration feature).
BWPM informs you when the migration process has been finished.
Note: until the migration script has been executed, no user can access the BWPM web
application. The following warning message will be displayed:
6) Log in as an administrator and the following warning will appear:
| 13
Confirm the message by clicking "Migrate" and wait until this final step of the migration
has completed.
7) Navigate to Administration - System Management Start the data providers as
described in the user guide.
8) The system is now upgraded to version 3.0.1
9) Optional: Download and execute the post-migration script. You can find the postmigration script in the following folder: <TOMCAT_WEBAPPS>/bwpm/download
In addition this folder contains the following scripts:
NJAMS_DB_INSTALL.SQL
Creating BWPM database (initial installation script)
NJAMS_DB_MIGRATE.SQL
Migrating to current version of BWPM
NJAMS_DB_POST_MIGRATE.SQL Optional migrations steps for current version of BWPM
| 14
Release 3.0
New Install
To install this version, follow the instructions of the BWPM Installation Manual.
Upgrade
Upgrade Prerequisite for Oracle DB:
Ensure the database user you use for the execution of the database script has the
following privileges, otherwise you may ask your DBA to execute the database upgrade
script:
Resource
Connect
Create View
Create Materialized View
Upgrade Prerequisite for MS SQL Server:
Ensure the database user is assigned to role SQLAgentUserRole and has SELECT
permission for the following objects:
msdb.dbo.sysjobactivity
msdb.dbo.sysjobs
msdb.dbo.sysjobhistory
msdb.dbo.sysjobschedules
msdb.dbo.sysschedules
| 15
Please consider:
The execution of the database upgrade script may take some time. Depending on
your database size the migration script can take several hours to complete. Please
validate that the TIBCO EMS server provides enough storage for incoming log
message for the duration of the migration.
The execution of the post-migration script is optional and needs only be executed
to migrate historic track information. If you do not execute the post-migration
script, historic process instances (executed before the time of upgrading the
installation) will not show execution paths. All new instances (executed after
upgrading the server) will have correct execution path information.
The post-migration script can be executed any time after the server has been
upgraded. It can run in the background while the server is processing data.
Depending on the size of the table to migrate, the script may run multiple hours. It
can be stopped and restarted at any point in time while running, without risk of
loosing or corrupting data.
To upgrade from a previous release follow this procedure:
1) Stop the data providers, shutdown the web application and undeploy the current
version of TIBCO BusinessWorks(TM) Process Monitor application.
2) Deploy bwpm.war on your Apache Tomcat Server. For further information consult the
installation manual "Installaing TIBCO BusinessWorks(TM) Process Monitor
Server.pdf"
3) Start the application
4) Your browser might have cached an older version of bwpm. Please make sure to
delete your browser cache and reload your login page in your browser.
Firefox: press CTRL+SHIFT+DEL and confirm the dialog that appears.
Internet Explorer: press CTRL+SHIFT+DEL or open Settings menu, select Safety, and
click on Delete browsing history. In the dialog window select Temporary Internet files
and deselect Preserve Favorite website data.
5) Go to the BWPM web page and log in as administrator. The following dialog will be
displayed:
| 16
If you select Download you can download the migration script as well as the postinstallation script (which is optional):
Please consider:
By default the historic track information will not be migrated. In order to continue to
have the historic track information, you need to execute the post-migration script. If
you are going to migrate from any version prior 2.1 and the migration of the historic
track information is required, please contact TIBCO Support to get detailed
information about how to proceed.
To automatically migrate the database to the latest version click “Migrate”. The
following Warning message lets you confirm or cancel the execution of the migration
script:
| 17
To download the SQL file that contains all required changes click on “Download”. That
file can be reviewed and loaded into the DB by a DBA (instead of using the automatic
migration feature).
BWPM informs you when the migration process has been finished.
Note: until the migration script has been executed, no user can access the BWPM web
application. The following warning message will be displayed:
6) Log in as an administrator and the following warning will appear:
| 18
Confirm the message by clicking "Migrate" and wait until this final step of the migration
has completed.
7) Navigate to Administration - System Management Start the data providers as
described in the user guide.
8) The system is now upgraded to version 3.0
9) Optional: Download and execute the post-migration script. You can find the postmigration script in the following folder: <TOMCAT_WEBAPPS>/bwpm/download
In addition this folder contains the following scripts:
NJAMS_DB_INSTALL.SQL
Creating BWPM database (initial installation script)
NJAMS_DB_MIGRATE.SQL
Migrating to current version of BWPM
NJAMS_DB_POST_MIGRATE.SQL Optional migrations steps for current version of BWPM
| 19
New Features
Release 3.0.1
The following enhancements are part of this service pack release:
Ticket NoTopic
#1492
Automatically create partitions, if there is no partition left created on advance.
(ORA-14400)
#1561
Search function for Payload and Stracktrace popup.
#1609
revise edit options of (quartz) jobs: Make LOCAL jobs non editable and
GLOBAL jobs undeleteable
#1624
Support for Tomcat 8
#1637
Performance improvements regarding NJAMS_JOB_DATA_MANAGEMENT and
NJAMS_T_TRACK_TEMPLATES SET LAST REFERENCED... changes from
2.2.1.8 transfered into 3.0.1
#1649
"Hybrid Delete" removed from data retention
#1657
Project messages which only contains resources, for example images, but no
process definition are now supported
Release 3.0
Multiple nodes per instance allow load balanced and fault tolerant setups
Domain objects can now be delete individually
The recorded payload can now be used in rules
TIBCO EMS JMS Connections can now use SSL
| 20
The following JMS Providers are supported: Apache ActiveMQ, IBM Websphere MQ,
JBoss, Oracle Weblogic, TIBCO EMS
LDAP
- LDAPS support
- group membership attribute is now configurable
- page size for LDAP queries to accomodate large resultsets
The interval of internal jobs can now be changed
Security enhancements
- one time passwords
- password expiration
- various more
Performance enhancements
Dashboard
- additional configuration options for gauges
- gauges can be pinned
- support for BusinessView
Facet Search
- fulltext search for payload, stacktrace, trace
Release 2.2
Automated correlation: injects context information (CorrelationLogID, ParentLogID) to
outbound event streams (JMS, HTTP, ServiceAgent over JMS) automatically (requires
BW 5.11 or greater)
| 21
LDAP Support: Synchronize LDAP members, LDAP based authentication
Exclude individual processes from monitoring
Tracing enhancements:
- "Deep trace": enable tracing for entire process chains (requires BW 5.11 or greater)
- Apply trace settings to multiple domain objects
- Apply trace points for multiple activities of one process at once
- Capture $_error object, if tracing is enabled
Extracts enhancements:
- Conditional extracts: rule based event type definition
- Apply extracts to many domain objects
- Additional fields added: Payload, Stacktrace, EventMsg, EventMsgCode
- Export/Import of extracts
Rule based alerting enhancements:
- Additional actions on alert: Write to log, HTTP action
- Wildcards for activity names
- Enable / Disable rules
- Export/Import of rules
Various UI improvements:
- Show/Resolve Global Variables
- Provide entire process stack in process graph
- Double-click on sub-processes (Firefox, only)
- Visualize data provider statistics (#449)
- etc.
| 22
Job management refined
Global performance and stability improvements
Optimization on persistence layer, client/server communication and messaging layer
Release 2.1.2
None.
Release 2.1.1
Added platform support for AIX 6.1
Added database support for MS-SQL Server 2008 R2
Extracts, as part of the Aspect configuration, can now act on input and output data of an
activity. Also the following rule types are available: disabled, static value, regular
expression and XPath 2.0
Release 2.0
Alerting Engine allows members of the admin role to create rules and actions for
specific events.
Aspects can be configured on any activity using the web interface
| 23
Change in functionality
Release 3.0.1
"Hybrid Delete" has been removed from data retention.
Release 3.0
The system does now support the installation of multiple nodes per BusinessWorks
ProcessMonitor Server instance to enable load balancing and fault tolerance setups.
If multiple nodes are to be installed, the system now requires an additional JMS topic of
name <prefix>.cluster for internal communication.
Release 2.2.1
During setup the server now validates that the correct JDBC driver version is used. If
unsupported JDBC driver versions are used, the setup process will not continue.
The default sort order for role members has been changed: role member's are now
sorted by their membership status first, and then name.
The default sort order for user's roles has been changed: roles listed for each user are
now sorted by their membership status first, and then name.
The following database objects have been removed:
table
NJAMS_T_STATISTICS
table
NJAMS_T_STATISTICS_HOUR
stored procedure
PROC_STATISTICS
stored procedure
PROC_STATISTICS_HOUR
stored procedure
PROC_SET_DIRTY_STATISTICS
stored procedure
PROC_SET_DIRTY_STATISTICS_HOUR
| 24
Release 2.2
None.
Release 2.1.2
None.
Release 2.1.1
Storage optimization for Track data. The new storage mechanism can reduce track
related data volumes.
DB jobs are moved from DBMS_JOBS to DBMS_SCHEDULER package. This change
requires the BWPM database user to have “create job” privilege.
Release 2.0
The minimum value for “timeoutPush” is now 1000 milliseconds
The minimum value for “timeoutCheckInterval” is now 1000 milliseconds
(Client) local settings are now stored in two files:
<BW engine name>_njams.properties (for trace settings)
<BW engine name>_extracts.xml (for aspect configurations)
| 25
Bug fixes
Release 3.0.1
Ticket No Topic
#1434
IE does not show the configuration of a transition
#1435
MSSQL: when using LDAP, the DELETE statement does not work
#1466
COMMIT_WRITE
#1508
Correct migration script where db objects will be created in wrong tablespace
#1550
Rules Export produce wrong filename if Rulename contains space character
#1554
Rule import dialog stays open after import
#1560
Data Management fails on non partitioned env. for old domain objects when
retention will be changed
#1566
table heading of list of all extracts is not sized correctly
#1577
Create View NJAMS_V_DP_CONNECTION does not work on Oracle 10g
#1596
Nullpointer Exception when stopping or starting dataprovider
#1615
deployed war file on tomcat 8 creates the folder njamsWEB-INF
#1616
delivered war file has log files of our development environment
#1621
controller_runstate.txt will reset content to "Stopped", when TOMCAT does a
shutdown and stops nJAMS application, which stops data provider
#1626
We are using deprecated oralce driver class, should use current instead
#1627
Data Management Job does not clean up trace points of sub processes in
NJAMS_T_MONITOR_BWTRACE
#1635
Cannot create partitions on Oracle DB because datetime format mismatch
(italian, english)
| 26
#1639
Data Provider does not start altough the logfile says "...all threads for
dp=dpQueue started!"
#1640
(MSSQL) the index on NJAMS_T_TRACK_TEMPLATES must be a clustered
index
#1644
NPE in LogFile when loading Mapping Tree
#1645
attributes of correlated entries are not shown
#1648
Njams server do not process projectmessage if getDomainObject returns 0
#1650
When generating two custom attributes only one is visible
#1651
Deadlock during partition switch
#1659
pretty printing does not work for all XML
#1663
getDomainObjectId cause deadlock in dataprovider when failing to get
connection
#1669
The current Connection Pool Size handling is misleading
#1680
Extract configuration is not deleted in server UI
#1707
Support Ticket #83, #89: Customer reports Tracing not working in production
Release 3.0
Ticket No
Topic
#1368
#1356
MSSQL: the start and end timestamps for active tracepoints shown on the UI
was not considering the browser's timezone settings for display.
MSSQL: the facet search by "Attributevalue" did not return correct results
#1352
The data mapping of an activity would not be rendered correctly, if the
mapping formula contained apostrophes
#1339
The SLA report would sometimes show the internal ID instead of the object's
name
| 27
#1333
A bug within the LDAP implementation would allow users to log in with
empty passwords, if LDAP was used for authentication
#1332
Stale JDBC connections were not re-established
#1327
The data provider statistics would always be shown in UTC timezone, rather
than the browser's timezone
#1310
Fixed an ORA-01000: maximum open cursors exceeded cause
#1307
You must now select at least one Extract to enable export of Extracts
#1306
Stopping a single data provider, while leaving others running, would
sometimes stop the rule engine
#1297
Changing the amount of threads for data providers would sometimes not be
applied correctly
#1295
Truncate too long values sent by the client before attempting a DB insert
#1294
When adding a new user, the user's language setting would not be stored.
#1293
Dashboard gauges are now stored per BusinessWorks ProcessMonitor
Server instance
#1288
Removed a security issue, which would allow administrators to bypass
authentication
#1277
Disabling a data provider left open JMS connections
#1269
Dashboard gauges did not check the browsers locale
#1267
When synchronizing users with an LDAP server, user names with an
apostrophe would not be synchronized correctly
#1253
The english language file contained entries of a different language
#1252
The server would fail in validating a client's hotfix level
#1250
Synchronizing with LDAP sometimes throws NjamsConfigOutdatedException
#1244
Large trace data was not made available for download
#1239
When moving a message to the error destination, the JMS message header
| 28
NJAMS_ERRORMESSAGE was not set correctly
#1237
Radio buttons in the JMS action of a rule were grouped incorrectly
#1236
Reports could not be exported anymore
#1223
In/Output trace data would only be displayed after selecting the tab multiple
times
#1202
Within an iteration group, the activity's execution time would not be
displayed correctly
#1184
The "search" icon of the facet search was without function
#1181
When using LDAP, users that should be added to the admin role were not
added to admin role
#1169
The input mapping of an activity would not render nicely, if the mapping
contained a static value
#1167
MSSQL: fixed an integer overflow issue
#1132
Upon logon, the UI was not always resized correctly
#1120
Some Oracle SQL was not optimized for Oracle 11, resulting in excess
"deprecated syntax ..." warnings in the Oracle RDBMS log file
#1116
The UI would become very slow on logon, if many hundred roles would be
configured in the system
#1076
Removed an unused icon from the process graph
#1057
The dialog showing an event's stacktrace had no scrollbars
#982
multiple instances of the product cannot be deployed into the same Tomcat
instance.
Deleting a trace point from the summary table would show incorrect result
#960
message
#947
The "show/hide Timings" button did not toggle correctly
#886
When displaying payload, underscores would not be rendered correctly
sometimes
| 29
#553
#543
Backslashes used for Business Service or Business Object values are not
displayed correctly in Business View
The trace settings dialog would mark some fields as mandatory, when they
are not mandatory in fact
#430
In very high load scenarios, some statistics would not be calculated correctly
Release 2.2.1
Ticket No Topic
#418
#538
When many thousand domain objects are managed, the GUI may become
slow.
BW Workflow activities are not shown in process graph
#716
domain objects could have been created multiple times
#952
after an EMS fail over or restart the JMS action of a rule would fail
#953
the process diagram did not show the correct group type
#966
line breaks in process diagram labels did not work correctly
#986
the "correlated processes" pie chart was grouping processes of same name,
but different deployments. This could lead to a false report.
#987
changing the password of the admin user could invalidate the admin account
#994
changing the password of a user could remove all role assignments for that
user
#999
navigating into a sub-process using the process diagram did not work for
complex situations
#1008
the table NJAMS_T_ACTIVITY_STATISTICS was not updated correctly for
some data
#1042
when restarting a data provider, a null pointer exception was shown in the log
file
#1043
multi-selecting of activities in process diagram opened additional browser
| 30
tabs
#1053
the non-partitioned setup of the DB was missing indexes required for
retention management
#1054
deep trace icon was not displayed on activities within groups
#1059
MS SQL: DOT filter buttons do not work
#1069
the start and end activities' icon was wrong, if the process diagram had a
custom icon configured
#1072
some activity icons of BW plugins would not display correctly in the process
diagram
#1093
the accuracy of number of records found by a search or report has been
improved
#1094
in some situations using business objects and business services would result
in incorrect statistics
#1107
assigning role memberships when using LDAP synchronization would only
work correctly from the second synchronization run. This has been fixed.
#1117
when many hundred users and many ten-thousand domain objects exist in the
system, initial login would take very long
#1118
on low resolution screens the table of Extracts would not show any scrollbar
#1119
on low resolution screens the buttons of the LDAP dialog were misplaced
#1121
fixed a Hazelcast error when updating the JDBC connection
#1125
if "admin" user was not of name "admin", the server could not communicate
with the client
#1126
fixed a bug that could slow down data processing in high-load scenarios
#1130
in rule condition "before" and "after" the date format was not recognized
correctly, resulting in corrupted rules
#1139
the lower graph's title was not refreshing when navigating the technical view
#1142
Attributes could not be referenced in rule condition or action
| 31
Hotfixes:
#1181
HF2: LDAP users are not added as members to admin role
#1252
HF3: Validate client version fails when version contains _HF*
#1310
HF4: maximum open cursors exceeded when retrieving domain objects'
ancestors
#1332
HF4: JDBC Connection pool does not re-establish stale connections
#1333
HF4: Security Issue: LDAP Logon without password possible
#1356
HF5: Search filter 'AttributeValue' does not work with MS SQL Server
Release 2.2
Ticket
No
#770
Topic
#773
clientlib log level cannot be changed, if DPs are stopped
#804
drop statements missing
#813
Extracts: XPATH formatting lost on reload
#822
Rules: remove case sensitivity for templateing language
#823
Rules: activity.name and activity.duration are not resolved
#849
resizing forces MainTable to refresh and hereby loss of the current position
#854
tracks for correlated process not shown
#864
Sort order of DOT should NOT be case sensitive
#868
#887
QuickSearch: attribute in combination with STATUS(Error) returns wrong
resultset
search doesn't work with seconds time range
#889
assumption that admin user is of name "admin" leads to wrong results
#891
no error message if DB feature is not supported
#892
empty EMS password is not supported
#895
The list of Trace Settings cannot be sorted by column "Tracing"
#904
Search using multiple *
Installation Documentation: tell the user that he has to log out as setup user
| 32
#905
The db connection pooling not working correctly
#907
tracing data sometime not shown in XPath configuration window
#915
Rules: E-mail notification misses translation of timestamps and process status
#917
#919
Rule: Empty error code and/or error message prevents sending email
notification
JMS connection closed exception
#922
Using single/double quotes in rules definition leads to errors
#923
duplicate track templates in database
#927
Instance of a specific process definition is not always shown (track is missing)
#936
Trace data: input and output tab
#940
Rules engine: Rule on process.duration does only fire when process finished
#987
Resetting a password does not work properly
#994
When a user changes password, all related roles are dropped, except his own
role
Release 2.1.2
Ticket Topic
No
#538 BW Workflow palette icons are not shown in process diagrams
#572 The domain object tree sometimes stays gray, even if there was activity on a
domain object.
#802 added missing labels for Extracts dialog
#814 some SQL statements had incompatibilities with Oracle 10g
#816 fixed a connection leak, if the EMS user did not have sufficient privileges to view a
destination
#817 queue length and oldest message information of status page was showing
inconsistent data in high volume installations
#828 if setting a trace point failed, the error message was not shown correctly
#831 wrong date time calculation could lead to not recognizing user role memberships
(MS-SQL, only)
#835 trace data was sometimes available to non-privileged users
#840 the execution path was not displayed correctly in very complex process diagrams
#843 the advice editor would not re-size correctly
| 33
#844 when switching between input and output data, the advice editor would not update
the “sample data” section correctly
#846 added missing unique indexes for role membership, business object and business
service tables
#872 the job NJAMS_JOB_DATA_MANAGEMENT would fail to drop expired partitions in
some cases
Release 2.1.1
Ticket
Topic
No
#603
ExternalLogId is saved into CustomId
#634
extracts.xml stores only last configuration element
#641
process with errors within iterations groups cannot be iterated through
#644
the administration category was missing a scroll bar
#645
the list of events was not scrollable
#646
admin user sometimes not created during the installation because of missing
commit statement in the installation script
#651
wrong error message when data provider settings could not be saved
#657
show descriptions of transitions just like TIBCO Designer does
#659
save changes the status of running data providers
#663
trace settings dialog can not be "applied" sometimes
#665
No error message if data provider cannot be deleted because it is used
#666
Rendering Tracks aborts when no Transitions exist in bwpm Context
#667
automatically reconnect to EMS in case EMS has been restarted
#669
the toolbar on top of activities in the process diagram had no tool tips
#674
newly created users do not get domain object tree displayed
#679
connection was not started when reconnected to EMS
#680
Setting trace points while JMS server is down
| 34
#681
Configuring extracts while JMS server is down
#683
Error occurs at DB generation, ORA-01450 maximum key length
#685
main table filter was reset when clicking on next page
#686
tool tips on main table pagination buttons where missing
#696
the search related "from" date was not respecting the browser's timezone, but
was always using UTC for date calculations triggered by the date buttons to its
left
#698
fixed an issue that would result in "maximum open cursor exceeded" errors
#699
large installations could experience domain object id collisions
#706
creating destinations in data provider screen would only work when JNDI was
used
#708
queue length's for data providers are now always read from the active EMS in
case of an FT configuration
#709
server now invalidates user session and logs out user when DB connection is
lost
#715
users are not shown as role members in UI
#716
in new installations domain objects could be created multiple times.
#752
configuration elements of rules can now contain apostrophe, quote, etc.
#754
multiple bwpm instances can now be run on the same MS-SQL Server
#755
the activity's configuration table was not scrollable
#756
the number formatting in some UI columns was wrong
#765
when selecting a main entry, the corresponding entry in the technical view is
now scrolled into view
#767
the trace table would not filter correctly when selecting an activity
#101474fixed jdbc error which lead to maximum open cursors exceeded
| 35
#483050Data management job was faulty for non-partitioned databases
Release 2.0
Ticket No - Topic
#619 – trace settings would ignore browser’s timezone
#617 – filter on main table would ignore the browser’s timezone
#588 – main table filter would not be shown correctly
#587 – stack traces of automatically captured errors would not be shown in rare
situations
#586 – input mappings could be expanded endlessly in some situations
#570 – the admin role can no longer be deleted from the system
#374 – Filter in Technical and Business View are now in a fixed position
| 36
Deprecated Features
This section lists deprecated features and specifies equivalent features that provide with
the same result. Please avoid becoming dependent on deprecated features and become
familiar with the equivalent feature.
Release 3.0.1
None.
Release 3.0
Oracle XE is no longer supported.
TIBCO EMS 5.x is no longer supported.
Release 2.2.1
None.
Release 2.2
none
Release 2.1.2
none
Release 2.1.1
Support for Oracle 10g is deprecated in this release.
Release 2.0
none
| 37
Compatibility
Release 3.0.1
This release supports all client releases starting with version 2.0.
Release 3.0
This release supports all client releases starting with version 2.0.
This release is only compatible with BusinessWorks ProcessMonitor Server version 3.0.
Release 2.2.1
This release supports all client releases starting with version 2.0.
Release 2.2
This release is not compatible with previous releases due to a necessary change made to
the underlying data model. This release supports all client releases starting with version
2.0.
Release 2.1.2
This release is compatible with all previous 2.x releases and hotfix levels.
Release 2.1.1
This release is not compatible with previous releases due to a necessary change made to
the underlying data model. All existing components (server and client) must be upgraded
to this release.
Release 2.0
This release is not compatible with previous releases due to a necessary change made to
the underlying data model. All existing components (server and client) must be upgraded
| 38
to this release.
| 39
Restrictions
The following table lists known restrictions in this release:
Defect # Summary / Workaround
283
Summary:
When a TIBCO BusinessWorks Engine stops unexpected the AuditStatus
remains in status “Running”
Workaround:
None.
990
Extracts can not be deleted, if the affected BW engine is not running.
Workaround: none
1068
if a process has a custom icon, the start and end activity will use that icon
instead of the default start/end icon.
Workaround: none / do not use custom icons for processes
1386
SSL is not supported for Apache MQ
1387
SSL is not supported for IBM Websphere MQ
1388
SSL is not supported for Jboss JMS
1389
SSL is not supported for Oracle Weblogic
| 40
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