book
Article ID: KB0104475
calendar_today
Updated On:
Description
Description:
This hot fix can be downloaded from the TIBCO Support file transfer server mft.tibco.com.
Server name: mft.tibco.com
Credentials: use your TSC (TIBCO Support Central website) login.
Browser: https://mft.tibco.com
FTP: port 21
SFTP: port 22
FTP using your browser is not supported, please use an FTP client or command-line. TIBCO employees must use a secure protocol. Once logged on you can find the hot fix under:
/available_downloads/Kabira/KPSA/3.7.0/hotfix03/ .
The Session Layers are available here:
/available_downloads/Kabira/KPSA-SessionLayers/3.7.0/hotfix03/
================================================================================
Product Name: TIBCO(R) KPSA
Release Version: 3.7.0_HF-003
Release Date: February 2014
================================================================================
Legal Notice
This Hotfix is provided pursuant to the terms and conditions of the written
maintenance and support agreement between you (or your company) and TIBCO and
use of the Hotfix is controlled by the terms of such written maintenance and
support agreement.
================================================================================
Introduction
Hotfixes are cumulative. This hotfix includes all previous generally available
hotfixes for TIBCO KPSA.
================================================================================
Installation
All platforms:
1. Stop the KPSA node.
2. Stop the Administration Tools (OAM) UI application.
3. Unzip the installation package to a temporary directory.
4. Copy the TIBCO Universal Installer from the $TIBCO_HOME/tools/universal_installer
directory into the same temporary directory you unzipped the installation package.
5. Run the TIBCO Universal Installer.
6. In the Welcome dialog, click "Next".
7. Click the "I accept ..." option to agree to the license agreement, and then
click "Next".
8. In the Installation Profile Selection dialog, click "Next".
9. In the TIBCO Installation Home dialog, select the $TIBCO_HOME location from
the "Use an existing TIBCO_HOME" drop-down list. This location must refer to
the location that you specified when installing the original product.
10. Review the information on the Pre-Install Summary dialog, and then click
"Install".
11. On the Post Install Summary dialog, click "Finish" to complete the
installation.
12. Start OAM UI application (it uses new files) using the same database IDs.
13. Apply database migration if required. See the <oam_node>/lib/migration/README
for instructions.
14. Start the KPSA and OAM nodes.
================================================================================
Uninstallation
All Platforms:
1. Shutdown all running TIBCO KPSA applications.
2. Run the TIBCO Universal Installer located in the following directory:
$TIBCO_HOME/tools/universal_installer.
3. In the TIBCO Installation Manager dialog, select the
"Uninstall Products from Selected TIBCO Home Location" option.
4. From the TIBCO HOME location drop-down list, select $TIBCO_HOME, then click
"Next".
5. In the Welcome dialog, click "Next".
6. In the Uninstallation Type dialog, select "Custom Uninstall", then click
"Next".
7. In the Product Uninstall Selection dialog, select the check box for the
hotfix and then click "Next".
8. In the Pre-Uninstall Summary dialog, click "Uninstall".
9. In the Post-Uninstall Summary dialog, click "Finish" to complete
uninstallation.
10. Restart your TIBCO KPSA applications.
================================================================================
Affected Files for 3.7.0_HF-003
The following files are installed by this hotfix. Note that some files
are platform-specific and are installed only on that platform.
All Platforms:
- TIB_kabira-kpsa-mobile_3.7.0_HF-003_readme.txt
$SW_HOME directory:
- KPSAPATCH-3.7.0-<MMDDYY>-<PLATFORM>
- P.HTTP-3.7.1-<YYMMDD>-<PLATFORM>
- P.SOAP-3.6.1-<YYMMDD>-<PLATFORM>
- P.KPSA-3.7.1-<YYMMDD>-<PLATFORM>
- P.KPSAOAM-1.1.3-<YYMMDD>-<PLATFORM>
- P.EMSCA-3.7.1-<YYMMDD>-<PLATFORM>
- P.AFFCA-3.7.1-<YYMMDD>-<PLATFORM>
================================================================================
Closed Issues in 3.7.0_HF-003
AP-944
Generated csv files have now a unique filename including date, time
and counter.
AP-943
When stopping OAM, non loaded csv files are saved and recovered on
node reconnection.
AP-942
Disconnect and Reconnect commands have been added to pause and resume
injection for a specific KPSA node.
AP-940
In OAM ui, the status of an order processed by LoadBalancer was not properly
updated.
AP-937
We added an index to the order_trace table (knode + orderId) to speed up the
queries and improved Queries for log Orders.
AP-936
The oam provadmin plugin verifies that GNU sed and GNU awk are in
PATH env var
AP-930
Old snapshots are now properly removed.
AP-929
Purges returned errors if too many orders were removed. The purge
mechanism now removes orders daily.
AP-915
Loading heavy configuration files may take some time. The parsing of KOP
conditions has been improved to increase the speed of Catalog startup.
AP-914
Previously, if the checkpoint for a CAMSF was lost, all pending SOs were stuck
and only a flush of the camsf could unlock them. The CAMSF can now recover from a
lost probe.
AP-883
SQL scripts have been added to by-pass Symfony (which consumes CPU/memory). All
database backends now use these kinds of scripts to purge and remove old
snapshots.
AP-882
Some Order present in OSSM were not displayed on KOP ui. Fixed
AP-866
We fixed the migration script to support the KPSA-3.7 database
================================================================================
Closed Issues in 3.7.0_HF-002
AP-829
New Order Query for Orders in the Processing status was not showing the correct
result on the Dashboard.
AP-828
Old snapshots are not all removed after database load.
AP-825 - MSF: Monitor failed depending on module creation order.
Error message "cannot find MessageStoreAndForward <mymsf>." may appear when the
MSF monitor is not properly initialized. Now fixed monitor are updated at
creation time.
AP-818 - The 'Age' parameter was not taken into account when purging orders
in OAM. Purging the database using provadmin purge OAM can remove more than
expected. We fixed this issue and only objects older than Age parameter are
removed.
AP-816 - The OAM GUI did not start if 'mime.type' file is not present in the
/etc directory. mime.type file was expected in the hard path on the host
machine. Now mime.type file is copied from shipped.
AP-807 "password" field in not required to "add a node" (ssh key is required)
To connect a remote KPSA node, user must set the correct ssh keys between KPSA
node and OAM host. Consequently, password field is not required when using
"provadmin connect oam".
AP-805 - XSLTXF: ProductOrderData was not correctly instantiated.
Now productVerb and productName are set at the creation time.
AP-801 - NETMANCA: The server would hang after checkpoint recovery.
Connection reference is now refreshed after checkpoint recovery.
AP-800 - Signal 11 crashed after Work Order completion.
In some cases, using substitution rules in KOP can cause an endless status
propagation after WOD execution, that may raise signal 11. This has been fixed.
AP-795 - POP: Async response throttling was causing KPSA freeze.
An application freeze may occur due to wrong duration computation.
This is now fixed.
AP-478 - httputil unreferenced symbol setContentLengthHeaderName was observed.
An enum value is missing in the httputil package. Fixed.
AP-466 - The remote KPSA node could not be connected to the OAM.
It was not possible to connect a remote from OAM host. Now fixed.
Also, in OAMui, the form to add a node checks every parameter before enabling
the save button.
AP-451 - The 'RewriteEngine' command was invalid during a KOP GUI startup.
Using clean URLs is no longer possible for KPSA Catalog. KOP ui has been
updated accordingly.
AP-220 - Invalid handle on NVSet in CommitPoint after swap out.
DSEBuiltin::ExceptionInvalidHandle exception may appear after swap out.
This has been fixed.
================================================================================
Closed Issues in 3.7.0_HF-001
AP-288
In the OAM GUI, logs for an orderID were not correctly displayed.
For example, on searching for an orderID equal to 1, the log contained all the
orderIDs starting with 1.
AP-284
OAM GUI was blank because of the following error:
ERROR: value too long for type character varying(5).
AP-215
KPSAOAM dataload parallelization performance was low.
AP-143
HTTP: httputil & zero length buffer.
FLUENCY-3968
NETTCP: Added support for non-blocking SSL connections.
================================================================================
TIBCO Product Support
- For an overview of TIBCO Support Services, and information about
getting started with TIBCO Product Support, visit this site:
http://www.tibco.com/services/support/default.jsp
- If you already have a valid maintenance or support contract,
visit the TIBCO Product Support site: https://support.tibco.com
Entry to this site requires a username and password. If you do
not have a username, you can request one.
- Check the TIBCO Product Support site "Late Breaking News" page
for product information that was not available at release time.
================================================================================
Copyright
Copyright (C) 2001 - 2014 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information.
Issue/Introduction
TIBCO KPSA 3.7.0 Hotfix03 is available
Environment
Product Name: TIBCO(R) KPSA
Release Version: 3.7.0_HF-003
Release Date: February 2014
OS: Redhat 6 & Solaris 10