TIBCO BusinessWorks 5.1.2 Hotfix 2 is available

TIBCO BusinessWorks 5.1.2 Hotfix 2 is available

book

Article ID: KB0105530

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks -
Not Applicable -

Description

Description:
TIBCO BusinessWorks 5.1.2 Hotfix 2 must install with TIBCO Runtime Agent 5.1.2 Hotfix2. The patch can be downloaded at:
ftp://trapatch:sp3cial@csftp.tibco.com/5.1.2/hotfix2/bw/
To download TIBCO Runtime Agent 5.1.2 Hotfix, please see TIBCO Runtime Agent 5.1.2 Hotfix2 LBN entry.

Defects fixed:

  Defect Id: 1-17YJP1
    Migration: SOAPRequestReply activity input bindings are now
    migrated properly.
    
  Defect Id: 1-18GGZ5
    Content Filter is now able to handle empty elements
    (xsi: nil attribute) correctly.

  Defect Id: 1-19BJTK
    The HTTP server no longer stops responding with UTF-8
    encoding.  It looks at the response content-type before
    setting the encoding.  

  Defect Id: 1-1A7LWA
    In database checkpoint, Wait, Notify, the engine name column width
    now defaults to 128 (instead of 50).  There is also a new engine
    name property, Engine.Name.MaxLength, which you can use
    to override the default setting.  
  
  Defect Id: 1-1AQ73T
  Service Request Id: 1-1GXT3T, 1-1H2B56
    Default SOAP Fault message can now be deserialized.
  
  Defect Id: 1-1B944H
  Service Request Id: 1-1GYA3P
    The SOAP 'getAllPrimitiveArrays' service has been fixed to work
    with .Net server if the arrayType namespace was not provided.
    "ws:import" is now allowed in OAG schema used for message-part.
  
  Defect Id: 1-1B9DNR
  Service Request Id: 1-1B9K0V
    The Rendezvous Publisher activity is now able to publish
    message with field name 'body'.  
    
  Defect Id: 1-1BBP0X
    In the HTTP Post request, if the message does not have a specified
    Content-Type, 'application/x-www-form-urlencoded;charset=UTF-8'
    will be set when sending URL-Encoded data.
    
  Defect Id: 1-1BDVRW, 1-1GPGET
  Service Request Id: 1-19M1FD
    Added timeout parameter to Input, for these activities:
    Send Rendezvous Request, JDBC Call Procedure, and
    SOAP Request Reply. This parameter which will override the
    value specified in the Configuration panel.
    There are UI changes in these activities, and the
    documentation for the next BusinessWorks release will
    reflect the latest UI.
  
  Defect Id: 1-1C1KFH
    Migration errors and warnings will now go to the proper
    log files if logging is enabled.  
  
  Defect Id: 1-1E0QNH
  Service Request Id: 1-1DYRCR, 1-1GI1TL
    Rendezvous Request Reply activity no longer throws an error
    after receiving a request using RVDQ transport.
  
  Defect Id: 1-1E1JYM
  Service Request Id: 1-1EUNBH, 1-1EFZOM, 1-1I5Y5J
    Durable Subscription is now working with JMS Topic
    Subscriber.
  
  Defect Id: 1-1E1JZA
  Service Request Id: 1-1DXVUD
    "Suppress Local Messages" option in the JMS Topic Subscriber
    is now working as documented: Checking this field prevents
    the process from receiving messages sent by the same connection.
    Unchecking this option specifies messages sent by the same
    connection should be received.

  Defect Id: 1-1EGEQP
  Service Request Id: 1-1EFZ0M
    During a JMS Durable Topic Session (Using Durable Subscription
    within the JMS Topic Subscriber), messages transmitted when
    the subscriber is down were not getting re-transmitted.  This
    issue is now fixed.
    
  Defect Id: 1-1EYORG
  Service Request Id: 1-1E9NJ5
    Illegal XML data is now handled correctly across adapters
    and TIBCO BusinessWorks.

  Defect Id: 1-1FGR5H
    Configuration error in field "Endpoint URL" is now fixed.
    
  Defect Id: 1-1FJ6D7
  Service Request Id: 1-1FFPNH
    Fixed an issue in Send HTTP Request activity where it was not
    parsing 'Set-Cookie' header in the response properly.

  Defect Id: 1-1FPF4Y
  Service Request Id: 1-1FKUOL, 1-1FY5P1
    Fixed an issue in Mapper where the mapping of data elements
    of the _error schema was not working properly.
    
  Defect Id: 1-1FZVNL
  Service Request Id: 1-1F2NQT
    Fixed a substitution problem in Mapper coercion. When substituting
    on a non-repeating element inside a repeating element ancestor,
    the substitution gets the repetition.

  Defect Id: 1-1G0FQH
  Service Request Id: 1-1HWH0T
    Improved support for load balancing of SOAP activities.
  
  Defect Id: 1-1G4Z8H
  Service Request Id: 1-1FIABL
     EJB Plugin: A security context conflict has been resolved. This
     conflict occurs when:
        * BEA WebLogic Application Server is used
        * Process definitions are deployed within the same
          process engine that use more than one user name to
          connect to the application server

     For example, you have JMS activities that use one user
     name to connect to the application server and EJB
     activities use a different user name. The problem also
     occurs if you use different user names in multiple EJB
     Connection resources and configure multiple EJB within a
     process definition with these connections.
     Set the Maximum Connections field in the EJB Connection
     resource to "0" to avoid this problem.


  Defect Id: 1-1G4Z8W
  Service Request Id: 1-1FIABL
    JMS Plugin: A security context conflict has been resolved. This
    conflict occurs when:
       * BEA Weblogic Application Server is used
       * Process definitions are deployed within the same
         process engine that use more than one user name to
         connect to the application server
    
  
  Defect Id: 1-1G5JG8
  Service Request Id: 1-1FITRR
    'Publish to Adapter' activity, using JMS transport,
    will no longer generate the "Cannot create Transport" error when
    replyDestination but not the subject is specified.  

    When both subject and replyDestination are specified the
    JMSReplyTo in the JMS header were sent as NULL. This is now
    resolved.

  Defect Id: 1-1H3EA6
  Service Request Id: 1-1H0N6T
    Fixed the Reminder setting: when the start time was in the past
    it was not starting at the next interval time,
    it was starting at the engine startup time and every interval
    after that. Also fixed the DST crossover logic.
    
  Defect Id: 1-1H9YSL
    Some problems related to Active-Enterprise for Siebel UAN IAP
    migration are addressed.

  Defect Id: 1-1HAYL8
  Service Request Id: 1-1GWFNF
    Database checkpoint now works properly with Sybase 12.5
  
  Defect Id: 1-1HBV4H
    [Internal fix]
  
  Defect Id: 1-1HE7XM
  Service Request Id: 1-1DUYFX
    SOAP Event Source will not throw error when the input message
    is defined with no message part.

  Defect Id: 1-1HOJ4J
  Service Request Id: 1-1FHQ11
    Corrected the handling of 'xsd:choice' within a WSDL file.
  
  Defect Id: 1-1HR9ZJ
  Service Request Id: 1-1HPFXP
    Improved the rendering speed in the Process Designer.
    
  Defect Id: 1-1HRW21
    Added a nil sub-node for nillable elements on the left
    side in the Mapper function.
  
  Defect Id: 1-1HSFIC
    When a resource is retrieved using its namespace for schema or
    WSDL, the resource data will no longer return null.

  Defect Id: 1-1HSVUT
  Service Request Id: 1-1HWH0T
    Added support for OAG schema import in WSDL.
  
  Defect Id: 1-1HTINI
  Service Request Id: 1-1HJ7S9
    The original namespace prefixes as defined in the schema when
    using a non-xml source is no longer overwritten.
  
  Defect Id: 1-1HTP0T
  Service Request Id: 1-1GQM66
    Fixed a problem for imported schema where previous versions of
    

  Defect Id: 1-1HWXAX
  Service Request Id: 1-1DAKKH
    Fixed a problem where the ledger file on the subscriber side
    keep increasing with RV request/reply mechanism with RVCM
    quality of service.

  Defect Id: 1-1I82SB
  Service Request Id: 1-1I73CP
    Input and Error Output tabs are no longer missing in
    activity configuration within a group nested in another group.
  
  Defect Id: 1-1I9PLB
    Fixed a problem in the HTTP Receiver where the &ltLF> and &ltCR> were
    sometimes filtered out.

  Defect Id: 1-1IBV59
  Service Request Id: 1-1FFPNH
    Fixed a problem in the HTTP Server where it should response with
    multiple cookies, but only one is actually sent out.

  Defect Id: 1-1IMN89
    Improved the performance of inline type.
    
  Defect Id: 1-1IXHYX
    The Label Activity from General will no longer throw an
    exception when used in a non English environment.
    
  Defect Id: 1-1J5JEK
    Service Request Id: 1-1J0WT5
    The 'Publish to Adapter' activity with 'Adapter service default'
    transport (when the Adapter subscription service is using RVCMQ
    transport) is now publishing certified messages instead of
    publishing reliable messages.  

  Defect Id: 1-1IOR9C
    Service Request Id: 1-1IP8QX
    Under some situations, if the process data (based on an XML file)
    is invalid for one job, BusinessWorks will report the data for the
    next job is invalid even though it is valid.  This is now fixed.
    
  Defect Id: 1-VPY7Y
  Service Request Id: 1-UREA5
    Fixed a problem in the Mapper where it was mis-interpreting types
    of some data elements.

  Defect Id: 1-WS4YR
    Fixed refresh problem in the input editor where there were
    red underlines when doing type substitution.
    
======================================================================
  * HotFix-1 (Released December 15, 2003)
======================================================================

  Defect Id:  1-18QDBC
    Error messages in Activities are now refreshed correctly.  

  Defect Id:  1-18T0R1
  Service Request Id: 1-1DU0HV
    The issue with JDBC activities generating errors under
    multi-statement transaction scenario using a JConnect driver
    with a Sybase database has been resolved.

  Defect Id:  1-19QXFH
    The Call Process activity now always shows the correct list
    of subprocess activities.

  Defect Id:  1-1BKE34
    Coercion made in the Mapper for activities in a group now
    persists in the project.

  Defect Id:  1-1C10TX
    The Java Code activity no longer throws NoClassDefFoundError
    exceptions.

  Defect Id:  1-1C1S8J
    The Java Method activity no longer throws ClassNotFoundException
    exceptions.

  Defect Id:  1-1D48LV
  Service Request Id:  1-12ABZH
    Data retrieved from integer columns in the JDBC query activity,
    now always display as integers, not as decimal numbers.

  Defect Id:  1-1DL7LD
    Mapper wizard on Unix now displays the schema element
    selection in the wizard's auto map window.

  Defect Id:  1-1EFCXL
    Type checking of for-each-group/current-group is now working
    correctly in the Mapper.

  Defect Id:  1-1EFCY7
    All Custom XPath functions within a project are now
    automatically included when you build an EAR file.

  Defect Id:  1-1EOKC5
    To maintain backward compatibility with TIBCO BusinessWorks 2.x,
    all empty strings in JDBC activities continue to be interpreted
    as nil in TIBCO BusinessWorks 5.x.
    
  Defect Id:  1-1ERRI1
    A message published to an Adapter activity now contains a
    reply subject when a JMS transport is used.

  Defect Id:  1-1EU2EP
  Service Request Id:  1-1ERAN1
    A JDBC Query no longer trims leading or trailing spaces for  
    varchar or char typed columns.  

  Defect Id: 1-1F1IXJ
  Service Request Id:  SR 1-1FPM4T
    To maintain backward compatibility with TIBCO BusinessWorks 2.x,
    the TIBCO Rendezvous Plugins now handle the AE Class name mangling
    and un-mangling when TIBCO Rendezvous Plugins refer to an
    AE Schema.  
    (See the notes under 'AE-Schemas and Name-Mingling for
     RV-Plugins')
    

  Defect Id:  1-1F5LQ4
  Service Request Id:  1-1EYFNU
    Override of the dynamic process name is now working.

  Defect Id:  1-1FLW5H
    Add call to destroy Repo Client on Engine Shutdown.

  Defect Id:  1-1FFN4T
  Service Request Id:  1-1FGC9W
    Fix the migration to handle illegal XML character hex 17
    to newline, in the project repository.  

  Defect Id: 1-5K4Y9
  Service Request Id:  SR 1-15N4D5
    Global variable(s) added, changed, or renamed now appear
    immediately in the XPath Editor.  


======================================================================
AE-Schema and Name-Mangling for RV-Plugins (Defect 1-1F1IXJ):
======================================================================

  This is the behavior when using the flag "XML Compliant Field-Names"
  in any of the RV Activities:
  
  - No change for outbound cases.  When the flag is unchecked (off),
    Name un-mangling is done.
    
  - No change for inbound cases.  When the flag is unchecked (off),
    Name mangling is done.
    
  - In BW 5.x, the flag value set for 2.x migrated projects are:
        o True for custom schema
        o False for shared schema
        
  - For new projects created in 5.x,
        o By default, this flag will be set to false
        o If the AE Schema is referred in the RV Activities,
          the schema element names will be mangled
          using the AE-Name-Mangling rules.  Those
          names will appear in the input binding editor.
          When sending a message on the wire, these names need to
          be un-mangled (if flag set to false), so that the original
          names used in the AE-Schemas can appear on the wire.
          (No change in behavior from 2.X).
          
          If the flag is set to true, the names which appear on the
          input binding editor, will appear on the wire.
          
        o If the inline schema editor is used to create the inline
          schema, the field names would need to be specified with
          the following rules:
          
            If flag is true, the field name specified on the input
            editor (and shown on the input bind editor) will appear
            on the wire.
            For example, if the field name is "field__0", it will
            appear on the wire as "field__0".
            
            If flag is false, the field name specified on the input
            editor will appear on the wire after applying the
            name mangling/un-mangling rules.
            For example, if the field-name is "feld__0" (note the
            double underscores), it will appear on the wire as
            "field_0" (as the name mangling rule is applied)

  - The name mangling rule allows the wire to carry the field name with
    special characters (e.g. "^", "#" etc.)

Issue/Introduction

TIBCO BusinessWorks 5.1.2 Hotfix 2 is available

Environment

Product: TIBCO BusinessWorks Version: 5.1.2 OS: All --------------------

Attachments

TIBCO BusinessWorks 5.1.2 Hotfix 2 is available get_app