Description:
This patch has fixed the following defects-
General Issues
Defect Id :1-115T9Q
Added a backward compatibility property 'Config.Primary.Compatibility.HawkMicroAgent.Style' which when set to '4.1.0' will switch the IM Hawk micro-agent names to 4.1.0 style names.


Defect Id :1-ZWKHL
File Job Creator : Introduced a new property called 'Config.Primary.FileJC.Process.Order' which now takes two values,-


TIMESTAMP_ASCENDING - Jobs get processed in the ascending order of file timestamp,- which means oldest file gets processed first and newest one last.
TIMESTAMP_DESCENDING - The opposite of 1. The default behavior is the old behavior which used to process files reverse-alphabetically,- z1.txt gets processed first and a1.txt last.



Defect Id :1-10O32L
If the remote path for mget is coming from a job slot and the the job slot content changes in subsequent jobs, IM Engine is not picking up the correct path.It was always using the path from the first Job. This has been fixed.


Defect Id :1-UBEET
The name of Engine Monitor microagent can now be over-ridden with the property 'Config.Primary.Hawk.EngineMonitorAgent.Service.Name'.


Defect Id :1-ZA7H3
If the ledger file is empty, reviewLedger() will now show an empty record instead of throwing an Error.


Defect Id :1-ZSYZG
Now, for ASCII mode, the FTP Invoke task will check the OS on which it's running.

If it's Windows, each line will get concluded by CRLF
If it's UNIX, each line will get concluded by LF only.
This will avoid ^M chars appearing on UNIX.


Defect Id : 1-10326F
Under load, a job who's matching event arrives in a signal in task was unable to get paged in. This has been fixed.


Defect Id : 1-WKQJF
Enhancement to allow loading of WSDL content through proxy servers. At design time, either of the following 3 sets of properties must be set.

Config.Editor.WsdlLoad.Proxy.http.port
Config.Editor.WsdlLoad.Proxy.http.user
Config.Editor.WsdlLoad.Proxy.http.password

Config.Editor.WsdlLoad.Proxy.socks4.host
Config.Editor.WsdlLoad.Proxy.socks4.port

Config.Editor.WsdlLoad.Proxy.socks5.host
Config.Editor.WsdlLoad.Proxy.socks5.port
Config.Editor.WsdlLoad.Proxy.socks5.user
Config.Editor.WsdlLoad.Proxy.socks5.password

If more than 1 sets is specified, the order of preference is http, socks4, then socks5. In case none is set, direct internet connection is assumed. Config.Editor.WsdlLoad.Proxy.debug if set to true causes debugging information to be output to the console.

At runtime, whether WSDL content is loaded through any proxy server is determined by the Shared Parameter attached to the Invoke Web Service task. To use socks proxy, set Config.Primary.Soap.Http.Proxy to either socks4 or socks5; the other valid value (default) is http.

Some HTTP proxy servers do not seem to be able to handle a separate CONNECT command, followed by the GET/POST instruction ( e.g. proxies Squid and Netscape ). For these servers, property Config.Proxy.Http.SkipSeparateConnectCmd should be set to true.


Defect Id : 1-YGLIE
Scrollbars were not appearing in debug panel data area when values were larger than the text area could display.
This has been fixed.


Defect Id : 1-ZX1SE
Enhancement to add ^encoding^ field to AE message envelope if version is 3.0 or later.


Defect Id : 1-ZOP2P, 1-Z90EX, 1-110LJ9
Internal fix for TIBCO BusinessConnect.


Defect Id : 1-ZZYN8
Fixed problem with HTTP/S working with self-signed certificates.


Defect Id : 1-ZMXRJ
IM does not export the global scripts used within mapper formulas.


Defect Id : 1-10Q4OS
Enhancement to have the signal out task publish explicit nulls.
By setting the property "Config.Primary.Compatibility.SignalOut.publishExplicitNull" to true, the signal out task will be able to publish explicit nulls. The property is defaulted to false.


Defect Id : 1-10GBTO
In the database update task, the binding of the SQL/Numeric type to the Java type is incorrect. This may result in a loss of precision when the actual value is updated in the database.


Defect Id : 1-10U5D0
If an user is telneting into the SOAP server port and breaks out of the telnet session, the IM SOAP server will throw a null pointer exception and stops processing messages.


Mapper, XML Parser and Renderer Issues:

Defect Id : 1-ZQBZC
Extraneous elements were part of the mapper output though it appears only once on the input side. Apparently, mapper formulas containing constants within the sequence of unions was the culprit.

By setting the property "Config.Primary.Compatibility.Mapper.HandleConstantsInSequenceOfUnion" to true, the mapper will be able to handle the mapping correctly. The property is defaulted to false.


Defect Id : 1-ZXYC2
Mapper XML output does not contain the appropriate namespace declarations.
This has been fixed.


Defect Id : 1-ZNNGA
The XML Render and Mapper task do not apply the proper namespace for some elements. This occurs when the XML schema uses substitution group and the same element name appears in multiple namespaces.
This has been fixed.


Defect Id : 1-101HCD
The mapper should take error transition after encountering errors. This is related to defect 1-XXKPR. An additional feature has been added so that the mapper output is created eventhough the mapper encountered errors. The mapper output will contained all the successful mappings. To enable this feature, the property "Config.Primary.Compatibility.Mapper.OutputResultDespiteError" must be set to true. The property is defaulted to false.
This has been fixed.


Defect Id : 1-ZXYE3
The XML Parser task is not be able to parse a XML instance if it contains an empty content element of datatype xsd:integer.
This has been fixed.


Defect Id : 1-10KZ6T
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 &gt0
(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