TIBCO BWPM Server - Release Notes

Transcription

1 TIBCO BWPM Server Notes

2 Process Monitor Server Notes Software Published: December 2013

3 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 ADDON 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 Javabased 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 NONINFRINGEMENT. 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 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

4 Contents Notes Installation New Install Upgrade New Features Change in functionality Bug fixes Deprecated Features Compatibility Restrictions

5 Notes Installation 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 Create Job (Note: after upgrading to version or higher, this DB privilege is no longer required and can be revoked by the DBA) 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 5

6 TIBCO BWPM Server Notes 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. If you are migrating from a pre release: The execution of the postmigration script is optional and needs only be executed to migrate historic track information. If you do not execute the postmigration 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 postmigration 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 and shutdown the web application and stop Tomcat. 2) Upgrade to version 2.2 by patching the BWPM web application: a. Example on Windows system: copy the file TIB_BWPM_2.2.1_upgrade.zip (extracted in step 1) into the directory {TOMCAT_HOME}/webapps/bwpm rightclick the file and choose: Extract in the dialog choose the name of your bwpm application, e.g as destination folder: {TOMCAT_HOME}/webapps/bwpm Confirm you want to overwrite the existing files you can now remove the file TIB_BWPM_2.2.1_upgrade.zip b. Example on Linux system: copy the file TIB_BWPM_2.2.1_upgrade.zip (extracted in step 1) into bwpm web application directory, e.g. {TOMCAT_HOME}/webapps/bwpm execute the following command: unzip TIB_BWPM_2.2.1_upgrade.zip 3) Restart Tomcat 6

7 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 4+: press CTRL+SHIFT+DEL and confirm the dialog that appears. Internet Explorer 9, 10, 11: 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: 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 postmigration 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. 7

8 TIBCO BWPM Server Notes 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 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 start the data providers. 8

9 7) The system is now upgraded to version 2.2 8) Optional: Download and execute the postmigration 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 New Features 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) 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 9

10 TIBCO BWPM Server Notes 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 Doubleclick on subprocesses (Firefox, only) Visualize data provider statistics (#449) etc. Job management refined Global performance and stability improvements Optimization on persistence layer, client/server communication and messaging layer None Added platform support for AIX 6.1 Added database support for MSSQL 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 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 10

11 Change in functionality 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 PROC_STATISTICS procedure stored PROC_STATISTICS_HOUR procedure stored PROC_SET_DIRTY_STATISTICS procedure stored PROC_SET_DIRTY_STATISTICS_HOUR procedure 2.2 None None. 11

12 TIBCO BWPM Server Notes 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. 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) 12

13 Bug fixes Ticket Topic No #418 When many thousand domain objects are managed, the GUI may become slow. #538 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 subprocess 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 multiselecting of activities in process diagram opened additional browser tabs #1053 the nonpartitioned 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 13

14 TIBCO BWPM Server Notes #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 tenthousand 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 highload 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 2.2 Ticket No Topic 770 Installation Documentation: tell the user that he has to log out as setup user 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 14

15 868 QuickSearch: attribute in combination with STATUS(Error) returns wrong resultset 887 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 * 905 The db connection pooling not working correctly 907 tracing data sometime not shown in XPath configuration window 915 Rules: notification misses translation of timestamps and process status 917 Rule: Empty error code and/or error message prevents sending notification 919 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 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 (MSSQL, only) 15

16 TIBCO BWPM Server Notes #835 trace data was sometimes available to nonprivileged users #840 the execution path was not displayed correctly in very complex process diagrams #843 the advice editor would not resize correctly #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 Ticket NoTopic #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 16

17 #681 Configuring extracts while JMS server is down #683 Error occurs at DB generation, ORA01450 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 MSSQL 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 # fixed jdbc error which lead to maximum open cursors exceeded # Data management job was faulty for nonpartitioned databases 2.0 Ticket No Topic #619 trace settings would ignore browser s timezone #617 filter on main table would ignore the browser s timezone 17

18 TIBCO BWPM Server Notes #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 18

19 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 None. 2.2 none none Support for Oracle 10g is deprecated in this release. 2.0 none 19

20 TIBCO BWPM Server Notes Compatibility This release supports all client releases starting with version 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 This release is compatible with all previous 2.x releases and hotfix levels 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. 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 to this release. 20

21 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. 553 Backslashes used for Business Service or Business Object values are not displayed correctly in Business View Workaround: none / do not use backslash 982 multiple instances of the product cannot be deployed into the same Tomcat instance. Workaround: use multiple Tomcat servers 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 21