Description:
You can download this HotFix from the TIBCO Product Support ftp server, support-ftp.tibco.com.  You will need to provide your eSupport username and password to access the server.  

Once you have successfully logged into the server, go to /available_downloads/BusinessEvents/StandardEdition/5.1.1/hotfix-02 to download the fix appropriate for your edition and operating system platform. Also need to download the latest Universal installer fromthe location mentioned below.


======================================================================
Product Name:    TIBCO BusinessEvents(R)
Release Version: 5.1.1_HF-002
Release Date:    April 2013
======================================================================
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 BusinessEvents 5.1.1.

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

Install this hotfix in the {TIBCO_HOME} directory of all host computers that run
TIBCO BusinessEvents version 5.1.1.

Selective installation for specific add-on products is not supported.

If this hotfix contains replacement files for any TRA file, and you have
customized your TRA files, you must customize the hotfix files accordingly.

All Platforms:

1. Shut down all running TIBCO applications.

2. Unzip the hotfix archive to a temporary location. The hotfix archive includes
    the files for TIBCO BusinessEvents and the add-on products.

3. Download the UniversalInstaller version 3.2.0 V2 or higher from the TIBCO
    Support FTP server, ftp://support-ftp.tibco.com. Provide your eSupport
    username and password to access the server, then go to
    /UniversalInstaller/TIBCOUniversalInstaller/ and locate the file to download.
    Copy it to the temporary location where you extracted the hotfix.

4. Run the installer executable.
    The installer installs hotfix files for TIBCO BusinessEvents and all
    installed add-ons.

5. Before you start Studio for the first time, re-initialize the plug-ins
    registry:
    Open a command prompt, change directory to {BE_HOME}/studio/eclipse, and
    run the command:
         studio -clean -initialize
    
    Then run the command to launch Studio:
     On Windows: studio.exe
     On UNIX   : ./studio

6. Rebuild Enterprise Archive (EAR) files for redeployment.

7. Restart your TIBCO applications.

Note:
    You must also rebuild the provided example project EAR files before use.

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

IMPORTANT NOTE:
    To uninstall hotfixes for TIBCO BusinessEvents and add-on products for  
        version 5.1.1, you must first uninstall Hotfix 2 and then uninstall
        Hotfix 1. Do not select both hotfixes for uninstallation at the same
    time.

Follow these instructions to roll back changes made in all hotfixes since the
last General Availability release.

All Platforms:

1. Shut down all running TIBCO applications.

2. Run the TIBCOUniversalInstaller located under
    {TIBCO_HOME}/tools/universal_installer.

3. Select the option "Uninstall Products From Selected TIBCO Home Location,"
    specify the {TIBCO_HOME} location, and click Next.

4. Select the option "Custom Uninstall" and click Next.

5. Select the TIBCO BusinessEvents and add-on products whose version
    specifies 5.1.1 Hotfix 2, and click Next.

6. At the summary screen, review the information and click Uninstall.
    The hotfixes are uninstalled. Click Finish to exit UniversalInstaller.
    This restores your environment to pre-hotfix 2 installation.

7. Repeat steps 1 to 6, selecting the TIBCO BusinessEvents and add-on products
    whose version specifies 5.1.1 Hotfix 1.
    This restores your environment to previous 5.1.1 installation.

8. Restart your TIBCO applications.

================================================================================
Affected Files for 5.1.1_HF-002

The following files are installed by this hotfix. Note that some
files are platform-specific and are installed only on that platform.

All Platforms:

   {TIBCO_HOME}/release_notes directory:
   - TIB_businessevents-hf_5.1.1_HF-002_readme.txt

   Standard Edition only:
   {TIBCO_HOME}/be/5.1/lib directory:
   - cep-as-channel.jar
   - cep-backingstore.jar
   - cep-datagrid-oracle.jar
   - cep-datagrid-tibco.jar
   - cep-hawk-channel.jar
  
   {TIBCO_HOME}/be/5.1/rms/bin directory:
   - RMS.ear
   - WebStudio.war
  
   {TIBCO_HOME}/be/5.1/rms/project/BRMS directory (RMS project files)
  
   {TIBCO_HOME}/be/5.1/rms/lib directory:
   - cep-rms.jar
   - cep-ui-rms-common.jar
  
   {TIBCO_HOME}/as/2.0/lib directory:
   - as-admin.jar
   - as-common.jar
   - as-agent.jar
   - *as-common*
   - *as-core*
   - *as-tibpgm*
   - *as-tibrv*
  
    {TIBCO_HOME}/as/2.0/bin directory:
   - as-agnet*
   - as-convert*
   - as-dump*
  

   Standard/Express Edition:
   {TIBCO_HOME}/be/5.1/lib directory:
   - be-functions.jar
   - cep-common.jar
   - cep-drivers.jar
   - cep-kernel.jar
   - cep-container.jar
   - cep-security.jar
   - cep-ui-rt-common.jar
   - be-studiofunctions.jar
  
   {TIBCO_HOME}/be/5.1/admin-plugins directory:
   - be-admin.jar
      
   {TIBCO_HOME}/be/5.1/mm/bin directory:
   - MM.ear

   {TIBCO_HOME}/lib/palettes directory:
   - be-bw.jar
  
   {TIBCO_HOME}/be/5.1/mm/lib directory:
   - be-q.jar
   - be-mm.jar
  
   {TIBCO_HOME}/be/5.1/mm/web-root directory:
   - emconsole.swf
  
   {TIBCO_HOME}/be/5.1examples/standard/FraudDetectionStore/FraudDetectionStore directory:
   - fdstore.cdd
  
   Event Stream Processing Only:
   {TIBCO_HOME}/be/5.1/examples/event_stream_processing/QueryTrades/QueryTradesProject/Archives directory:
   - InferenceAndQuery.cdd
  
   {TIBCO_HOME}/be/5.1/lib directory:
   - cep-query.jar
  

   Data Modeling Only:
   {TIBCO_HOME}/be/5.1/lib directory:
   - cep-modules.jar
  
  
   BE Views Only:
   {TIBCO_HOME}/be/5.1/views/lib directory:
   - cep-metric.jar
  
   Process Orchestration Only:
   {TIBCO_HOME}/be/5.1/lib/eclipse/plugins directory:
   - com.tibco.cep.bpmn.common_1.0.1.jar
  
Windows and Linux Platforms:

   The following files are installed in product directories outside the
   hotfix directory:

   Standard/Express Edition:
   {TIBCO_HOME}/be/5.1/studio/eclipse/plugins directory:
   - com.tibco.cep.sharedresource_5.1.1.jar
   - com.tibco.cep.studio.application_5.1.1.jar
   - com.tibco.cep.studio.cli_5.1.1.jar
   - com.tibco.cep.studio.common_5.1.1.jar
   - com.tibco.cep.studio.core_5.1.1.jar
   - com.tibco.cep.studio.debug.core_5.1.1.jar
   - com.tibco.cep.studio.ui_5.1.1.jar
   - com.tibco.cep.studio.ui.editors_5.1.1.jar
   - com.tibco.cep.studio.ws_5.1.1.jar
  
   BE Views Only:
   {TIBCO_HOME}/be/5.1/studio/eclipse/plugins directory:
   - com.tibco.cep.studio.dashboard.core_5.1.1.jar
  
   Process Orchestration Only:
   {TIBCO_HOME}/be/5.1/studio/eclipse/plugins directory:
   - com.tibco.cep.bpmn.ui_1.0.1.jar
   - com.tibco.cep.bpmn.common_1.0.1.jar

   Decision Manager Only:
   {TIBCO_HOME}/be/5.1/studio/eclipse/plugins directory:
   - com.tibco.cep.studio.rms.core_5.1.1.jar
   - com.tibco.cep.decision.table.core_5.1.1.jar

================================================================================
Closed Issues in 5.1.1_HF-002 (This Release)

BE-18310
A new property, tibco.be.datetime.parse.lenient, is introduced to control the
validation of DateTime field ranges when using the DateTime.parseString function.
By default, the property is set to true and the values of the DateTime field
ranges are normalized to fit the expected ranges.
Set the property to false to ensure that the values of the DateTime field ranges
are not normalized. An error will be thrown if the DateTime field ranges are
out of the expected range.

BE-18250
Multipe cache node failure was observed when using TIBCO BusinessEvents DataGrid.

BE-18226
The catalog function StudioUtil.buildEar returned true even if it failed to
generate the EAR file.

BE-18209
When some Active Directory users tried to log in, an exception
(HeadersTooLargeException) was thrown if the total size of the CNs or DNs of the
associated groups was large.

BE-18201
The option to build an EAR file using the legacy compiler (parameter '-lc') was
missing from the StudioUtil.buildEar catalog function.

BE-18194
With the property ?be.engine.cluster.as.tuple.explicit? set to true concepts
that were loaded would fire rules as though all their properties had been
modified.

BE-18188
When defining a coercion in the XSLT mapper, the cardinality of the coercion was
not saved after applying the mapping.

BE-18168
The build version displayed in TIBCO Administrator was different from the
actual build version.

BE-18159
An error was thrown when trying to insert or update a record into a table
with the primary key column managed by IDENTITY in SQL Server.

BE-18157
Foreign key was empty for database concepts when the key was created by a
sequence.

BE-18147
When using Shared-all persistence, providing null values to one or more field
names caused the operation to hang.

BE-18130
Delete queries were unable to handle bind variables. This has been fixed.

BE-18128
TIBCO BusinessEvents Views and RMS can now be configured to support secure
LDAP connections using the property be.auth.ldap.ssl. Set the property to true
in the CDD file to enable secure LDAP connections.

BE-18121
TIBCO BusinessEvents MM can now be configured to support secure
LDAP connections using the property be.mm.auth.ldap.ssl. Set the property to
true in the CDD file to enable secure LDAP connections.

BE-18115
Performance degradation was observed when inference agents were added and shared
nothing persistence was used. The degradation was visible even when the
additional inference engines were idle.

BE-18109
State timeouts and scheduled events would stop firing after a random amount
of time, and more likely under load.

BE-18104
TIBCO BusinessEvents threw an 'Invalid username and password' error when
connecting to an authorization enabled Hawk domain using EMS.

BE-18096
When multiple engines configured to listen on the same HTTP or HTTPS port were
started, the engines start without throwing a port binding error.
However, it was observed that only the engine that was started first processes
the HTTP requests on the configured port. This is because the channel is
started only on the engine that was started first.

BE-17964
You can configure the TIBCO BusinessEvents DataGrid protocol timeouts by
setting the following properties in the CDD file.
For read timeout, set
be.engine.cluster.as.read.timeout = &lttimeout_value_in_milliseconds>
For write timeout, set
be.engine.cluster.as.write.timeout = &lttimeout_value_in_milliseconds>

BE-17938
If too many domain name values are associated with a decision table, an
exception is thrown when it is exported to Excel:
"Export to Excel Failed due to : java.lang.IllegalArgumentException: String
literals in formulas can't be bigger than 255 characters ASCII"

BE-17807
The be-jdbcdeploy utility supports the use of encrypted passwords to
generate alter scripts. Perform the following tasks to generate and use the
encrypted passwords:
1. Generate the encrypted text using the studio_tools utility
   Run the following command:
     studio_tools.exe -crypto encrypt -i input text
   The encrypted text is written to STDOUT. The exit status 0 indicates success
   and -1 indicates error.
   Ensure that the exit status is 0 before using the encrypted text.
2. Set the password property in be-jdbcdeploy.tra.
   Before running the be-jdbcdeploy utility, edit the be-jdbcdeploy.tra file
   and set the password property, be.jdbc.schemamigration.pwd, to the generated
   encrypted text. (To use plain text, set the value of this property to the
   plain text password.)

BE-17580
Exceptions were thrown when using the function
Cluster.DataGrid.CacheLoadConceptsByExtId(extIds) and the persistence was set
to none. This has been fixed.

BE-17544
TIBCO BusinessEvents did not load the null values from backing store after a
restart. As a result, concepts with null values stored in a string array were
lost when the engine was restarted.
A new property, be.backingstore.nullarrayorhistoryvalue.skip, can be used to
control this behaviour. Set the property to false in the CDD file to enable
the null arrays or history values to be loaded from the backing store.

BE-15152
A java.lang.NumberFormatException was returned when a SOAP request did not
contain a content-length header.

================================================================================
Closed Issues in 5.1.1_HF-001

NOTE: See LBN1-EB5353 for more information about issues that were closed in
Release 5.1.1.

BE-18064
A memory leak was observed in TIBCO BusinessEvents DataGrid when repetitive
calls to getSpaceDef() were made and the space definition existed.

BE-18025
A high CPU usage was observed when running a project with Object Management
set to ?In Memory?. The CPU usage remained high even when the engine was idle.

BE-17985
When using cache-aside strategy, CacheLoadConceptByExtId or Instance.GetbyExtId
were not retrieving the data from the backing store if the data was not in the
cache.

BE-17982
Existing concepts were not loaded into the cache by the functions,
getByExtIdByUri or cacheLoadExtIdByUri, after the application was restarted if
the property 'useObjectTable' was set to false and the concept was added in the
Domain Objects override section. This was observed when using a backing store
with Shared All persistence.

BE-17971
This hot fix enables the hot deployment of new properties into existing TIBCO
BusinessEvents concepts. This functionality is only available when:
   - Cache Object Management is enabled with no persistence or Shared Nothing
     persistence.
   - The concepts with new properties are cache-only.

To enable this functionality:
Before starting TIBCO BusinessEvents Studio to build the EAR file:
1. Add the following line to the vmargs in the studio.ini file:
   -Dcom.tibco.be.hotdeploy.concept=true
2. Set the property com.tibco.be.hotdeploy.concept=true in the CDD file.

Note the following restrictions:
- When enabling this functionality with no backing store, ensure that the
  property be.engine.cluster.as.tuple.explicit=true is set in the CDD file.  
  This property is set to true by default when using shared nothing persistence.
- Adding a concept property of type contained concept with the contained
  concept type set to an existing concept is not supported.

BE-17946
When running the TIBCO BusinessEvents engine in the write-behind mode, with
DataGrid for object management caching and backing store enabled, getById
or getByExtId returned a null value when the object existed in database but not
in the cache.

BE-17942
When using shared-nothing persistence, the shared nothing file
contained corrupted data for a specific concept. This caused data loss
and failure during recovery.

BE-17544
Following a restart, the null values in a string array were not loaded from
the backing store although the record existed in the database.

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

- I