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.8.0/hotfix03/

Note that if you use HTTP Session Layer you have to use the updated version available here:
/available_downloads/Kabira/KPSA-SessionLayers/FP-3.8.0/HTTPSL-3.8.0/hotfix01

===============================================================================
Product Name:    TIBCO Fulfillment Provisioning
Release Version: 3.8.0_HF-003
Release Date:    October 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 Fulfillment Provisioning version 3.8.0.

================================================================================
Installation

All platforms:

1. Stop the Fulfillment Provisioning node.
2. Stop the Administration Tools (FPOMS) 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 Fulfillment Provisioning OMS UI application (it uses new files) using
    the same database IDs.
13. Apply database migration if required. See <fpoms_node>/lib/migration/README
    for instructions.
14. Start Fulfillment Provisioning and FPOMS nodes.

================================================================================
Uninstallation

All Platforms:
 
 1. Shutdown all running TIBCO Fulfillment Provisioning 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 Fulfillment Provisioning applications.

================================================================================
Affected Files for 3.8.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_fp_3.8.0_HF-003_readme.txt
   
$SW_HOME directory:

   - P.SOAP-3.8.0-<YYMMDD>-<PLATFORM>
   - P.FPHF-3.8.0.3-<YYMMDD>-<PLATFORM>
   - P.FPOMS-1.2.2-<YYMMDD>-<PLATFORM>
   - P.OSSJCA-3.8.1-<YYMMDD>-<PLATFORM>

================================================================================
Closed Issues in 3.8.0_HF-003 (This Release)

AP-970
The Service Orders that were processed in SOP / KOP was creating conflicts with
each other. The conflicts occurred because KOP utilized a lot of CPU resources.
The conflicts resulted in deadlock promotion and the work that was executed was
cancelled and restarted. This issue has been fixed.

AP-969
The Service Orders that were processed in SOP / KOP was creating conflicts with
each other. The conflicts occurred because KOP utilized a lot of CPU resources.
The conflicts resulted in deadlock. This issue has been fixed.

AP-968
The Service Orders that were processed in SOP / KOP was creating conflicts with
each other. The conflicts occurred because KOP utilized a lot of CPU resources.
The conflicts resulted in deadlock during session acquisition timeout. This
issue has been fixed.

AP-967
A throttling asynchronous instance log was generated in FP log engine. This
issue was fixed and the traces of the logs are moved to cartAdmin.

AP-963
When an instance, which executes asynchronous work orders, was disabled, the
service orders entered into an infinite loop between the POP and the
POPWaitingQueue resulting in excess consumption of CPU resources. The issue has
been fixed and the Service Orders will exit in Partial state allowing MSF to
perform intelligent resubmission.

NOTE: Work Orders failing at the "CONTINUE" phase will not resubmit the work
      to the network element. Once cartridge is re-enabled it will continue
      from the point where it failed.

================================================================================
Closed Issues in 3.8.0_HF-002

AP-952
After rollback, a ServiceOrder targeting a slow Network Element can be stuck in
heap. We fixed this issue

AP-931
In FPOMSui, the statuses of orders processed by LoadBalancer were not properly
updated. We fixed this issue.

AP-922
When stopping FPOMS, non loaded csv files are saved and recovered on
node reconnection.

AP-869
Generated csv files have now a unique filename including date, time
and counter.

AP-846
Disconnect and Reconnect commands have been added to pause and resume
injection for a specific FP node.

================================================================================
Closed Issues in 3.8.0_HF-001

AP-917
Using Oracle database, following error may appear: ORA-00904: "FALSE": invalid
identifier

AP-912
User can now filter a group of parameters using wildcard ('%')
Following templates are valid:
    'foo%' dataset name begins with foo
    '%foo%' dataset name contains foo
    '%foo' dataset name ends with foo
    form 'foo%bar' is not valid.

AP-903
Previously, if the checkpoint for a CAMSF was lost, all pending SOs were stuck
and only a flush of the camsf could unlock them. Now a new probe is elected if
the system detects that there is no probe when the checkpoint is reloaded.

AP-891
When users import XMI files from TIBCO Fulfillment Studio version 1.0, some part
of the BPMN file may be corrupted. After importing the flows, users should run
the 'fix_fs_bpmn_import.ksh' script to fix those BPMN2 files and keep the
resulting BPMN file. The script can be found here: distrib/kabira/kpsa/scripts/

AP-874
SOAP has been added to the Fulfillment Provisioning Installer. It was missing in
previous versions.

AP-872
An index has been added to order_trace table (knode + orderId). Queries for log
orders have also been improved.

AP-867
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-863
Loading heavy configuration files may take some time. The parsing of KOP
conditions has been improved to increase the speed of Catalog startup.

AP-824
Depending on the order of module creation, monitor initialization and processing
sometimes failed with an invalid handle. This issue has been fixed.

AP-820
NUL characters are now properly supported and displayed.

AP-817
Purges returned errors if too many orders were to be removed. The purge
mechanism now removes orders each day.

================================================================================
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.

TIBCO Fulfillment Provisioning 3.8.0 Hotfix03 is available