Products | Versions |
---|---|
TIBCO IntegrationManager | - |
Not Applicable | - |
Description:
Following are the defect fixes in TIBCO Integration Manager 4.5.0 hotfix14 -
General Issues:
* Defect Id : 1-1JWPKC
Add support to ignore impact-action commands. To put this change in
effect, set property Config.Admin.SkippedImpactActionCmds to one or
more of the following values, comma-separated: Shutdown, Kill, Suspend.
If Shutdown is specified, the only to bring down the server would be
to issue a system kill or Ctrl-C.
* Defect Id : 1-1H9JPP
Internal enhancement/fix for TIBCO BusinessConnect.
* Defect Id : 1-1FQ8WW
Fixed problem where SOAP/Webservice job creators may fail to
initialize when set up with WSDL that defines only one service
operation.
* Defect Id : 1-1EEGFM
Added property 'Config.Primary.Initialize.Security.On.StartUp', which by
default is false and which, if set to true, will force the initialization
of the security package very early on during start-up.
* Defect Id : 1-1D3JJG
In case the log files are stored on a network drive, spurrious
errors can periodically cause log writing to fail; failure is
difficult to reproduce. Changes were made to make the logging module
more robust.
* Defect Id : 1-1ET5XJ
Added support for automatic instatiation of inner classes while creating
an AE object, for backward-compatibility reason. Property
Config.IM221StyleAEInstantiation needs to be set to true to put this
enhancement in effect.
* Defect Id : 1-1DL2CH
In property editor, expand comment, associated with property controlling
the prefix for the data manager's database table names, to state clearly
that the prefix is prepended only to table names that are not explicitly
specified.
* Defect Id : 1-1EBXKP
Fixed to make the Reader/Writer task thread-safe.
* Defect Id : 1-1FL331
Enhanced the Reader/Writer task so it can parse inputs that are
AttributeNode of data, in addition to AttributeNode of AttributeNode
of data.
* Defect Id : 1-1KG6CE
Fix to destroy JMS temporary destination objects ( queues and
topics, as well as the associated sessions ), so resources can be re-claimed;
otherwise, after some time, JMS client and/or server would run out of memory.
Mapper, XML Parser and Renderer Issues:
* Defect Id : 1-1IL75Y
Add a property to allow users to keep the order of multiple policy nodes output
as it was in IM 4.1. Property Config.Primary.Compatibility.Mapper.MultiplePolicyOrder
needs to be set to true to enable compatibility mode. This property is defaulted to false.
* Defect Id : 1-1IZZU2
Mapper hangs on XML instance that contains many empty content elements.
* Known Issues:
Mapper, XML Parser and Renderer Issues:
1) The following is a list of reserved words used by IM Mapper code. They
should not be used to name XML elements and attributes:
ANY, anonClass, CDATA, choice, choiceGroup, sequence,
sequenceGroup, union