Patch 8 for TIBCO Adapter for Swift 4.2.0 available.
Article ID: KB0105680
Updated On:
| Products | Versions |
|---|---|
| TIBCO Adapter for SWIFT | - |
| Not Applicable | - |
Description
Description:
Patch 8 is available for Windows NT/2000 and Solaris 2.7.The issues addressed in the patch have been listed below.Please refer to the readme file with the patch for more details.This patch is cummulative and contains fixes from patch1.lease contact TIBCO Support to get the patch.
Defects Fixed in Patch8
-----------------------
Defect_Id assigned: 1-1VYKP4
----------------------------
Defect description: Parser generates an "Invalid character found exception" when the value for the first sub-part [1!a] is not present in 57A field of MT103.
Solution: This defect has been fixed.
Please unzip and run the patchinstaller to apply the patch.
Defects Fixed in Patch7
-----------------------
The SWIFT IM Custom Plugin functionality works with the IntegrationManager 450,hotfix 12.3.
Please ensure that the IntegrationManager 450,hotfix 12.3 is applied.
Defect_Id assigned: 1-1AERH2
----------------------------
Defect description: The SwiftAdapter when configured for the MQSA Interface did not publish the incoming Tracking ID for the outgoing message. Instead a new Tracking Id was published for the outgoing message.
Solution: This defect has been fixed.
Defect_Id assigned: 1-1AOURP
----------------------------
Defect description: The adapter did the double conversion for the fields having "d" datatype and hence incorrect message with the exponent E was sent to SWIFT Alliance Access. SwiftAlliance Access does not support message with the exponent E for d datatype.
Solution: This defect has been fixed.
Following are the important notes for the above defect:
1.Add the flag "adswift.DoubleExponentConversion" in the adswiftSender.tra,adswiftReceiver.tra and Tester.tra and set its value to off to switch off the double conversion.
(for eg: adswift.DoubleExponentConversion Off)
2.The flag "adswift.DoubleExponentConversion" is used in the adswiftSender and adswiftReceiver tra files to switch on and off the double conversion.If the value of the flag is set to ON or if the flag is not added in the tra and the validate parameter is set to true in the adapter configuration, then the double Conversion will be performed. If the value of the flag is set to "OFF" and the validate parameter is set to true in the adapter configuration, then the double conversion will not be performed.If any invalid value is specified for this flag,then the double conversion will be performed.
3.For the CustomIMPlugin , add a custom property "DoubleExponentConversion" and set its value to on/off. The behaviour with this property set to on/off is same as that of the flag "adswift.DoubleExponentConversion" in the adapter.
Defects/Enhancements Fixed in Patch6
------------------------------------
Defect_Id assigned: 1-YB5LG
----------------------------
Defect description: When fields of type 'x' contain '%' characters in the message, the data gets truncated from the '%' character up to end-of-line.
Solution: This defect has been fixed.
Defect_Id assigned: 1-17KHAT
----------------------------
Defect description: When the adapter is running in CASmf mode on Solaris, messages processed by the adapter during the recovery session are rejected by SWIFT Alliance Access due to incorrect carriage-return/line-feed character present in the recovered messages.
Solution: This defect has been fixed.
Defect_Id assigned: 1-186FLQ
----------------------------
Enhancement description: The SWIFT IM Custom Plugin now takes in Validate parameter through the Jobslot of Parser and Renderer Processes. Local Publication and Local Subscription of Parser/Renderer processes are removed.
Following are the important notes for the above enhancement:
1.The "Config.Primary.Compatibility.AE.UseSDK" property should be set to true in the IM properties file.
2.The Parser Process takes in "InputString" and "ValidateParser" as input Jobslots. The SWIFT Message to be parsed is specified in the InputString Jobslot. ValidateParameter is specified in string format and accepts values "true", "TRUE", "false", "FALSE". This parameter can be specified at either the Jobslot or in the IM properties file. However the value of ValidateParser in the Jobslot precedes that of in the IM properties file. The Parser places the output AE Swift Message in "OutputMInstance" Jobslot.
4.The Renderer Process takes in "InputInstance" and "ValidateRenderer" as input Jobslots. The AE Swift Message to be rendered is placed in InputInstance Jobslot. The ValidateRenderer parameter is specified in string format and accepts values "true", "TRUE", "false", "FALSE". This parameter can be specified at either the Jobslot or in the IM properties file. However the value of ValidateRenderer in the Jobslot precedes that of in the IM properties file.The Renderer places the output string in "OutputSwiftString" Jobslot.
5.The SWIFT message having "{S:" block which contains the information added by SWIFT Alliance Access will be treated as a part of CustomTrailer and will be added in the CustomTrailer attribute of SWIFT AE Schema.
Defects Fixed in Patch5
-----------------------
Defect_Id assigned: 1-173VIL
----------------------------
Defect description: When the field with same names exist inside a sequence and its optional subsequence, then the field is not populated in the correct location of the AE schema. This occurs only when the optional subsequence is not present in the message and Validate flag is set to false.
Solution: This defect has been fixed.
Defect_Id assigned: 1-1794VN
----------------------------
Defect description: Tag 57A not parsed properly when Validate flag is set to false and when the optional subfield (34x) contains data starting with "//" character.
Solution: This defect has been fixed.
Defect_Id assigned: 1-173VIW
----------------------------
Defect description: IM Custom Activity Enhancements - Local subject names should be configurable and return paths should return Success, Nodata and Error transition.
Solution: This defect has been fixed.
Defect_Id assigned: 1-16YZKL
----------------------------
Defect description: The field 70E in MT564 contains repeating qualifiers and the same should be represented as sequence in the generated schema.
Solution: This defect has been fixed.
Defects Fixed in Patch4
------------------------
Defect_Id assigned: 1-ZIBD9
---------------------------
Defect description: Swift Sender does not place error messages in RemoteErrorDir.
Solution: This defect has been fixed.
Defect_Id assigned: 1-NUK99
---------------------------
Defect description: The SWIFT TIBCO IntegrationManager Custom Task for Renderer did not publish the SWIFT message when the UseSDK flag in the TIBCO IntegrationManager property file was switched off.
Solution: This defect has been fixed.
Defect_Id assigned: 1-UIOPW
---------------------------
Defect description: Qualifier "TTCO" in field 22F does not process more than one occurrence of the same eventhough TTCO is a repeating.
Solution: This defect has been fixed.
Defects Fixed in Patch3
------------------------
Defect_Id assigned: 1-U7095
---------------------------
Defect description: When Multi Process is running (Single/Multi engine) & Multi Messages are published, 1st Message is duplicated & rest are lost
Solution: This defect has been fixed.
Defects Fixed in Patch2
------------------------
Defect_Id assigned: 1-I5A7L
---------------------------
Defect description: In the case of AIX and IIS FTP servers, SWIFT receiver hangs when there are no files present on the FTP directory that is being polled.
Solution: This defect has been fixed.
Defect_Id assigned: 1-IGX8L
---------------------------
Defect description: Swift message is not published and throws error when currency "NOK" is used.
Solution: This defect has been fixed.
Defect_Id assigned: 1-IGX73
---------------------------
Defect description: Adapter does not start on machines containing non en_US locale.
Solution: This defect has been fixed.
Defect_Id assigned: 1-IGX7K
---------------------------
Defect description: SWIFT sample for Custom plugin, provided with the adapter installation does not work.
Solution: This defect has been fixed.
Defect_Id assigned: 1-IGX8A
---------------------------
Defect description: SWIFT IM Plugin for parser does not publish an AE object.
Solution: This defect has been fixed.
Defects Fixed in Patch1
-----------------------
Defect_Id assigned: 1-G2WZ1
---------------------------
Defect description: Swift Adapter does not handle enter characters present in the fields.
Solution: This defect has been fixed.
Patch 8 is available for Windows NT/2000 and Solaris 2.7.The issues addressed in the patch have been listed below.Please refer to the readme file with the patch for more details.This patch is cummulative and contains fixes from patch1.lease contact TIBCO Support to get the patch.
Defects Fixed in Patch8
-----------------------
Defect_Id assigned: 1-1VYKP4
----------------------------
Defect description: Parser generates an "Invalid character found exception" when the value for the first sub-part [1!a] is not present in 57A field of MT103.
Solution: This defect has been fixed.
Please unzip and run the patchinstaller to apply the patch.
Defects Fixed in Patch7
-----------------------
The SWIFT IM Custom Plugin functionality works with the IntegrationManager 450,hotfix 12.3.
Please ensure that the IntegrationManager 450,hotfix 12.3 is applied.
Defect_Id assigned: 1-1AERH2
----------------------------
Defect description: The SwiftAdapter when configured for the MQSA Interface did not publish the incoming Tracking ID for the outgoing message. Instead a new Tracking Id was published for the outgoing message.
Solution: This defect has been fixed.
Defect_Id assigned: 1-1AOURP
----------------------------
Defect description: The adapter did the double conversion for the fields having "d" datatype and hence incorrect message with the exponent E was sent to SWIFT Alliance Access. SwiftAlliance Access does not support message with the exponent E for d datatype.
Solution: This defect has been fixed.
Following are the important notes for the above defect:
1.Add the flag "adswift.DoubleExponentConversion" in the adswiftSender.tra,adswiftReceiver.tra and Tester.tra and set its value to off to switch off the double conversion.
(for eg: adswift.DoubleExponentConversion Off)
2.The flag "adswift.DoubleExponentConversion" is used in the adswiftSender and adswiftReceiver tra files to switch on and off the double conversion.If the value of the flag is set to ON or if the flag is not added in the tra and the validate parameter is set to true in the adapter configuration, then the double Conversion will be performed. If the value of the flag is set to "OFF" and the validate parameter is set to true in the adapter configuration, then the double conversion will not be performed.If any invalid value is specified for this flag,then the double conversion will be performed.
3.For the CustomIMPlugin , add a custom property "DoubleExponentConversion" and set its value to on/off. The behaviour with this property set to on/off is same as that of the flag "adswift.DoubleExponentConversion" in the adapter.
Defects/Enhancements Fixed in Patch6
------------------------------------
Defect_Id assigned: 1-YB5LG
----------------------------
Defect description: When fields of type 'x' contain '%' characters in the message, the data gets truncated from the '%' character up to end-of-line.
Solution: This defect has been fixed.
Defect_Id assigned: 1-17KHAT
----------------------------
Defect description: When the adapter is running in CASmf mode on Solaris, messages processed by the adapter during the recovery session are rejected by SWIFT Alliance Access due to incorrect carriage-return/line-feed character present in the recovered messages.
Solution: This defect has been fixed.
Defect_Id assigned: 1-186FLQ
----------------------------
Enhancement description: The SWIFT IM Custom Plugin now takes in Validate parameter through the Jobslot of Parser and Renderer Processes. Local Publication and Local Subscription of Parser/Renderer processes are removed.
Following are the important notes for the above enhancement:
1.The "Config.Primary.Compatibility.AE.UseSDK" property should be set to true in the IM properties file.
2.The Parser Process takes in "InputString" and "ValidateParser" as input Jobslots. The SWIFT Message to be parsed is specified in the InputString Jobslot. ValidateParameter is specified in string format and accepts values "true", "TRUE", "false", "FALSE". This parameter can be specified at either the Jobslot or in the IM properties file. However the value of ValidateParser in the Jobslot precedes that of in the IM properties file. The Parser places the output AE Swift Message in "OutputMInstance" Jobslot.
4.The Renderer Process takes in "InputInstance" and "ValidateRenderer" as input Jobslots. The AE Swift Message to be rendered is placed in InputInstance Jobslot. The ValidateRenderer parameter is specified in string format and accepts values "true", "TRUE", "false", "FALSE". This parameter can be specified at either the Jobslot or in the IM properties file. However the value of ValidateRenderer in the Jobslot precedes that of in the IM properties file.The Renderer places the output string in "OutputSwiftString" Jobslot.
5.The SWIFT message having "{S:" block which contains the information added by SWIFT Alliance Access will be treated as a part of CustomTrailer and will be added in the CustomTrailer attribute of SWIFT AE Schema.
Defects Fixed in Patch5
-----------------------
Defect_Id assigned: 1-173VIL
----------------------------
Defect description: When the field with same names exist inside a sequence and its optional subsequence, then the field is not populated in the correct location of the AE schema. This occurs only when the optional subsequence is not present in the message and Validate flag is set to false.
Solution: This defect has been fixed.
Defect_Id assigned: 1-1794VN
----------------------------
Defect description: Tag 57A not parsed properly when Validate flag is set to false and when the optional subfield (34x) contains data starting with "//" character.
Solution: This defect has been fixed.
Defect_Id assigned: 1-173VIW
----------------------------
Defect description: IM Custom Activity Enhancements - Local subject names should be configurable and return paths should return Success, Nodata and Error transition.
Solution: This defect has been fixed.
Defect_Id assigned: 1-16YZKL
----------------------------
Defect description: The field 70E in MT564 contains repeating qualifiers and the same should be represented as sequence in the generated schema.
Solution: This defect has been fixed.
Defects Fixed in Patch4
------------------------
Defect_Id assigned: 1-ZIBD9
---------------------------
Defect description: Swift Sender does not place error messages in RemoteErrorDir.
Solution: This defect has been fixed.
Defect_Id assigned: 1-NUK99
---------------------------
Defect description: The SWIFT TIBCO IntegrationManager Custom Task for Renderer did not publish the SWIFT message when the UseSDK flag in the TIBCO IntegrationManager property file was switched off.
Solution: This defect has been fixed.
Defect_Id assigned: 1-UIOPW
---------------------------
Defect description: Qualifier "TTCO" in field 22F does not process more than one occurrence of the same eventhough TTCO is a repeating.
Solution: This defect has been fixed.
Defects Fixed in Patch3
------------------------
Defect_Id assigned: 1-U7095
---------------------------
Defect description: When Multi Process is running (Single/Multi engine) & Multi Messages are published, 1st Message is duplicated & rest are lost
Solution: This defect has been fixed.
Defects Fixed in Patch2
------------------------
Defect_Id assigned: 1-I5A7L
---------------------------
Defect description: In the case of AIX and IIS FTP servers, SWIFT receiver hangs when there are no files present on the FTP directory that is being polled.
Solution: This defect has been fixed.
Defect_Id assigned: 1-IGX8L
---------------------------
Defect description: Swift message is not published and throws error when currency "NOK" is used.
Solution: This defect has been fixed.
Defect_Id assigned: 1-IGX73
---------------------------
Defect description: Adapter does not start on machines containing non en_US locale.
Solution: This defect has been fixed.
Defect_Id assigned: 1-IGX7K
---------------------------
Defect description: SWIFT sample for Custom plugin, provided with the adapter installation does not work.
Solution: This defect has been fixed.
Defect_Id assigned: 1-IGX8A
---------------------------
Defect description: SWIFT IM Plugin for parser does not publish an AE object.
Solution: This defect has been fixed.
Defects Fixed in Patch1
-----------------------
Defect_Id assigned: 1-G2WZ1
---------------------------
Defect description: Swift Adapter does not handle enter characters present in the fields.
Solution: This defect has been fixed.
Issue/Introduction
Patch 8 for TIBCO Adapter for Swift 4.2.0 available.
Environment
Product: TIBCO Adapter for SWIFT
Version: 4.2.0
OS: All
--------------------
Feedback
Yes
No
Powered by
