TIBCO BusinessEvents Standard Edition 5.1.2 Hotfix 01 is available for download.

TIBCO BusinessEvents Standard Edition 5.1.2 Hotfix 01 is available for download.

book

Article ID: KB0104837

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Description:
You can download this HotFix from the TIBCO Product Support ftp server, https://mft.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.2/hotfix-01 to download the fix appropriate for your edition and operating system platform.

================================================================================
Product Name:    TIBCO BusinessEvents(R)
Release Version: 5.1.2_HF-001
Release Date:    March 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 is the first hotfix for TIBCO BusoinessEvents 5.1.2.

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

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

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. Copy the TIBCO Universal Installer from
    {TIBCO_HOME}/tools/universal_installer 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:
    Hotfixes for TIBCO BusinessEvents and add-on products for version 5.1.2
        must be uninstalled one at a time. For example, first uninstall Hotfix 8,
        then Hotfix 7, and so on, until Hotfix 1 is uninstalled.
        Do not select all the 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.2 Hotfix 1, and click Next.

 6. At the summary screen, review the information and click Uninstall.
    The hotfixes are uninstalled. Click Finish to exit UniversalInstaller.
  
 7. Restart your TIBCO applications.

================================================================================
Affected Files for 5.1.2_HF-001

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.2_HF-001_readme.txt

   Standard Edition only:
   {TIBCO_HOME}/be/5.1/lib directory:
   - cep-backingstore.jar
   - cep-datagrid-oracle.jar
   - cep-as-channel.jar
   - cep-datagrid-tibco.jar
  
   {TIBCO_HOME}/be/5.1/mm/lib directory:
   - be-q.jar
  
   {TIBCO_HOME}/be/5.1/rms/bin directory:
   - RMS.ear
   - RMS.cdd
   - 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
 
  Standard/Express Edition:
   {TIBCO_HOME}/be/5.1/lib directory:
   - cep-drivers.jar
   - cep-container.jar
   - cep-common.jar
   - cep-kernel.jar
   - be-functions.jar
   - cep-security.jar
  
   {TIBCO_HOME}/be/5.1/admin-plugins directory:
   - be-admin.jar 
  
   Process Orchestration Only:
   {TIBCO_HOME}/be/5.1/lib directory:
   - cep-bpmn.jar
  
   Data Modeling Only:
   {TIBCO_HOME}/be/5.1/lib directory:
   - cep-modules.jar
  
   Event Stream Processing Only:
   {TIBCO_HOME}/be/5.1/lib directory:
   - cep-query.jar 
  
   BE Views Only:
   {TIBCO_HOME}/be/5.1/views/lib directory:
   - be-dashboardagent.jar
   - cep-metric.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.2.jar
   - com.tibco.cep.studio.application_5.1.2.jar
   - com.tibco.cep.rt_5.1.2.jar
   - com.tibco.cep.studio.core_5.1.2.jar
   - com.tibco.cep.studio.tester.core_5.1.2.jar
   - com.tibco.cep.studio.ws_5.1.2.jar
  
   Decision Manager Only:
   {TIBCO_HOME}/be/5.1/studio/eclipse/plugins directory:
   - com.tibco.cep.studio.rms.ui_5.1.2.jar
   - com.tibco.cep.decision.table.core_5.1.2.jar
   - com.tibco.cep.decision.table.common__5.1.2.jar
  
   Process Orchestration Only:
   {TIBCO_HOME}/be/5.1/studio/eclipse/plugins directory:
   - com.tibco.cep.bpmn.core_1.1.0.jar

================================================================================
Closed Issues in 5.1.2_HF-001 (This Release)

BE-20445
Support for merging SOAP/JMS resources during WSDL import was added.

BE-20321
While running RMS as a Windows service, the option "Generate Deployable" would
hung and time out. This was fixed and deployables are generated properly.

BE-20320
Basic validation for Domain Model usage is now supported.

BE-20310
TIBCO BusinessEvents throws NullpointerException in function
Database.createQuery() when resultTypeURI is set to Null and the query
has no result.
This has been fixed.

BE-20115
Double quote around "SOAPAction" were missing in the release 5.1.2.
This was fixed.

BE-20114
BE Views query and the resulting export to MS Excel was showing duplicates.
This was fixed.

BE-20104
The function Engine.Rtc.abortRTC() was not working as expected. Deleted
concepts were still stored in cache, even after calling abortRTC().
This was fixed.

BE-20061
Studio-tools utility now supports migration of SharedNothing folder structure
as described in 5.1.2 Release Notes - section Migration and Compatibility ->
Release 5.1.2 -> Update the SharedNothing Folder Structure as per HostAware
Naming Convention.

Run the following studio-tools command on each machine and for each engine
deployed on those machines.

studio-tools -sharednothing migrate-files -p <datastore path>
-c <cluster name> -n <engine name>
For example:
studio-tools -sharednothing migrate-files -p C:\data -c cluster1 -n cache1

BE-20057
100% CPU usage in the secondary (passive) agent was occurring when it
was started before the primary (active) agent.
This was fixed.

BE-20056
WebStudio login username/password didn't support multibyte characters
for file-based authentication.
This was fixed.

BE-20054
Managing the life cycle of Domain models in WebStudio/RMS and BE Studio
is expected to proceed without restarting RMS.
This was fixed.

BE-20052
The Database.* catalog functions should not log any exceptions in the log
file. Exceptions are handled by the calling Rule/RuleFunction.
This was fixed.

BE-20050
The BQL Query (delete from ...) was giving a NullPointerException after
enabling the option "Shared Nothing".
This was fixed.

BE-20049
Support for Proxy configuration in HTTP-based catalog functions was added.

BE-19966
When using the AS.lockEvent() channel function, there was no option to
specify timeout.
This was fixed.

BE-19300
When Shared Nothing persistence is used, the getInstance Hawk method in
TIBCO Administrator doesn't return data for an external ID search.
This was fixed.

BE-18004
Provide a SOAP message serializer for the JMS channel.

A serializer/deserializer for SOAP/JMS has been added to the JMS destinations.
This serializer handles the conversion between JMS messages and SOAPEvent
events. Two helper catalog functions are provided as well:

-  SOAP.registerEventUri()
   void registerEventUri(String eventUri, String destinationUri, String
   serviceName, String soapAction)

   It associates an event type to a given input destination, target service,
   and SOAP action. This is used by the SOAP/JMS deserializer to generate
   events of specific types (eventUri), instead of using the default event
   type resolution mechanism.

   -  eventUri: String path of an event type in the project.

   -  destinationUri: String path of the BusinessEvents destination receiving
      the message. If empty, matches all destinations.

   -  serviceName: String name of the target service declared in the message
      received. If empty, matches all service names.

   -  soapAction: String value of the soapAction parameter in the message
      received.

-  SOAP.newCorrelationId()
   String newCorrelationId(String responseEventUri)

   Creates a new correlation ID for use when sending a message in a request/
   response case. This is used by the SOAP/JMS deserializer to generate a
   response event of a specific type, instead of using the default event type
   resolution mechanism.

   -  responseEventUri: String path of an event type in the project.
   -  returns: String correlation ID.

BE-5074
Now it is possible to re-use the workKey in the scheduler.
It was not possible before this hotfix.

BE-5552
The WSDL import wizard now generates resources for handling SOAP/JMS
bindings in the following way:

Events

-  One Event type named /Events/SoapJms: this event type inherits from
   SOAPEvent and provides a set of properties that may be useful for SOAP/
   JMS (see also the RegisterSoapEventUris function below).

-  Operation-specific events: they are imported similarly to the SOAP/HTTP
   WSDL import.

Channels

-  A JMS channel (by default located at /Channels/SoapJms) for each different
   set of parameters, with the following:

   -  One shared JMS connection resource (by default located in the Transport
      folder of the imported service folder).

   -  One destination for each different set of destination parameters (by
      default named destinationName), using the serializer
      SoapMessageSerializer and the default event type /Events/SoapJms
      (see the RegisterSoapEventUris function below).

Rules

-  One rule for each operation, imported similarly as for the SOAP/HTTP WSDL
   import. By default the rule replies with a SOAP fault saying that the
   operation is not implemented.

RuleFunctions

-  One RuleFunction for each operation, imported similarly as for the SOAP/HTTP
   WSDL import. If desired this can be used as a preprocessor function,
   for example.

-  One RuleFunction named RegisterSoapEventUris (by default located in the
   Transport folder of the imported service folder).
   This function instructs the deserializer how to deserialize messages into
   operation-specific events instead of using the destination's default.
  
   RegisterSoapEventUris registers, in the JMS SoapMessageSerializer, an event
   type for each operation that is reachable by a SOAP/JMS binding.
   It should be invoked as a startup function.


BE-3819
Deleted entities are now removed from the write-behind SharedAll store instead
of being marked for deletion.

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

================================================================================
Patents

U.S. Patent No. 7,472,101

================================================================================
Copyright

Copyright (C) 2004-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information


Issue/Introduction

TIBCO BusinessEvents Standard Edition 5.1.2 Hotfix 01 is available for download.

Environment

BE 5.1.2, All Platforms

Additional Information

TIB_businessevents-hf_5.1.2_HF-001_readme.txt

Attachments

TIBCO BusinessEvents Standard Edition 5.1.2 Hotfix 01 is available for download. get_app