book
Article ID: KB0105943
calendar_today
Updated On:
Description
Description:
Following are the enhancements done in TIBCO Integration Manager 4.1.0 hotfix15 -
* Enhancements:
HOTFIX-15:(Current Hotfix-Release)
* Starting with this release, we are changing the terminology from
PATCH to HOTFIX to follow the new TIBCO company-wide release
guideline.
* Defect Id : 1-155S6G [Enhancement]
Option '-timeout' has been added to imadmin tool to specify time
in secs to wait for responses from all engines
* Defect Id : 1-X9X01
Internal property driven fixes to job mon events:
1. put current time into each event
2. fire an additional event before task.eval
Properties [all default to false for backwards compatibility]:
Config.Primary.Trace.Job.FixMonEvent: applies both fixes
Config.Primary.Trace.Job.ShowRealTime: applies fix #1 only
Config.Primary.Trace.Job.PreTaskExecEvent: applies fix #2 only
* Defect Id: 1-XCTSW
Added support for property-driven feature to allow mapper task
instances to offload work onto different thread pool from IM
worker thread. Also, allow creation of pool of mapping objects
to alleviate the problem that the mapping object is not thread safe.
Mapper.Pool.Private.Task.[*|mapperName]=true|default=false
Mapper.Pool.Size.Task.[*|mapperName]=N|default=0
How the properties are used
1] Mapper.Pool.Size.Task.*=N
controls the size of the global thread pool to be shared by all
mapper instances that do not have their own pool. If this is not set,
these mapper instances are going to use the IM worker thread.
2] Mapper.Pool.Size.Task.mapperName=N
a] if Mapper.Pool.Private.Task.mapperName=true or
Mapper.Pool.Private.Task.*=true,
controls the size of the private thread pool, as well as the pool of
mapping objects specific to mapper task instance "mapperName"
b] otherwise,
controls only the size of pool of the mapping objects. Map processing
is carried out using the common global thread pool or the IM worker
thread.
3] in the absence of any of the new properties, or they are not set with
valid values, each mapper task instance has one mapper instance created
whose access needs to be synchronized, and whose processing is done on the
IM worker thread (backward-compatibility mode).
Notes:
1] N should be an integer >0
2] mapperName is the full name of the mapper instance including the
process name. A process name can be nested directory-like. The
separator between each directory segment, as well as that between
the process name and the map name, is the forward-slash ( "/" ).
Some simplistic usage hints -
1] Control mapper instances that are known to take a long time to process
with property set
Mapper.Pool.Size.Task.process-name/slow-map = N
Mapper.Pool.Private.Task.process-name/slow-map = true
2] To avoid any other mapper instances to use precious IM thread resource,
have property
Mapper.Pool.Size.Task.* = M
where M should perhaps be greater than N's for specific mappers.
* Defect Id : 1-ZOUPP
Enhancement to add ^encoding^ field to AE message envelope if
version is 3.0 or later.
* Defect Id : 1-100QYI
The XML parser was not preserving valid white space content.
Issue/Introduction
TIBCO Integration Manager 4.1.0 hotfix15 is now available
Environment
Product: TIBCO IntegrationManager
Version: 4.1.0
OS: All
--------------------