(forCrossWorlds
Infrastructure versions 4.x and WBIA versions 2.x)
The patch notes contain the following sections:
This patch contains fixes for the following CRs based
on customer-reported cases
Available
as of Version |
CR
Number/APAR # |
Description |
2.7.1 |
CR60609 |
Added support for BIDI enablement. |
To
perform an upgrade to this version of the connector:
Add, replace, or remove the following files and directories
as indicated:
For Adapter Version |
Platform [WIN; UNIX] |
Add / Replace / Remove |
File (Starting from %CROSSWORLDS%/$CROSSWORLDS) |
2.7.1 |
WIN;UNIX |
Replace |
/connectors/JMS/CWJMS.jar |
CR60609:
JMS connection was BiDi enabled
JMS connector supports correct processing of BiDi data as part of both content data (business data) and meta data (configuration / meta data)
Following connector specific properties were BiDi enabled:
ArchiveDestination
ConnectionFactoryName
ErrorDestination
InProgressDestination
InputDestination
MessageFormatProperty
MessageResponseResultProperty
ReplyToDestination
UnsubscribedDestination
UnsubscribedOnTerminate
Following verb level ASI properties were BiDi enabled
Values in Message Selector String
JMS field names in Message Selector String
Following static meta BO attribute level ASI properties were BiDi enabled
InputFormat
OutputFormat
InputDestination
OutputDestination
ReplyToDestination
CorrelationID
BiDi support limitations
There is no BiDi support for content data in case of dynamic meta BO driven
message processing. The support is limited to static meta BO driven message
processing only. BiDi enablement is supported on Windows only.
BiDi support usage
BiDi support in JMS connector is controlled via following 4 standard connector properties.
1. BiDi.Transfromation
The BiDi.Transformation property defines whether the system performs a bidirectional transformation at run time.
If the property value is set to true, the BiDi.Application, BiDi.Broker, and BiDi.Metadata properties are available. If the property value is set to false, they are hidden.
Default value: false
Possible values: true or false
Update method: Component restart
Note: This property is valid only if the value of BrokerType is not WAS.
2. BiDi.Application
The BiDi.Application property specifies whether the bidirectional format for data is coming from an external application to the adapter in the form of a business object supported by this adapter. The property defines the bidirectional attributes of the application data. These attributes are:
Type of text: implicit or visual (I or V)
Text direction: left-to-right or right-to-left (L or R)
Symmetric swapping: on or off (Y or N)
Shaping (Arabic): on or off (S or N)
Numerical shaping (Arabic): Hindi, contextual, or nominal (H, C, or N)
This property is valid only if the BiDi.Transformation property value is set to true.
Default value: ILYNN (implicit, left-to-right, on, off, nominal).
Possible values: Any valid combination of these bidirectional attributes:
1st letter: I,V
2nd letter: L,R
3rd letter: Y, N
4th letter: S, N
5th letter: H, C, N
Update method: Component restart
Note: This property is valid only if the value of BiDi.Transformation is true.
3. BiDi.Metadata
The BiDi.Metadata property defines the bidirectional format or attributes for the metadata, which are listed in {BiDi.Application}. This property is valid only if the BiDi.Transformation property value is set to true.
Default value: ILYNN (five letters, implicit, left-to-right, on, off, nominal)
Possible values: Any valid combination of these bidirectional attributes:
* 1st letter: I,V
* 2nd letter: L,R
* 3rd letter: Y, N
* 4th letter: S, N
* 5th letter: H, C, N
Update method: Component restart
Note: This property is valid only if the value of BiDi.Transformation is true.
4. BiDi.Broker
The BiDi.Broker property specifies whether the bidirectional format for data is sent to or received from the integration broker. It defines the bidirectional attributes of the broker data, which are as listed in {BiDi.Application}.
This property is valid only if the BiDi.Transformation property value is set to true.
Default value: ILYNN (implicit, left-to-right, on, off, nominal).
Possible values: Any valid combination of these bidirectional attributes:
* 1st letter: I,V
* 2nd letter: L,R
* 3rd letter: Y, N
* 4th letter: S, N
* 5th letter: H, C, N
Update method: Component restart
Note: This property is valid only if the value of BiDi.Transformation is true and the value of BrokerType is ICS
© 2003 IBM
Proprietary and Confidential. All Rights Reserved.