IBM WebSphere(R) Business Integration Server Express supports bidirectional scripts. This support is in a standard Windows(R)-type bidirectional format (logical left to right). (Examples of languages involved in bidirectional design are Hebrew and Arabic.) Because of this support, all collaborations also support bidirectional scripts. However, data entering a collaboration may come from:
Bidirectional format inconsistencies cause comparisons within a collaboration to return incorrect results. These types of errors can be avoided by following these guidelines:
To enable a connector to support a bidirectional script:
Letter position | Purpose | Values | Description | Default |
---|---|---|---|---|
1 | Type | I | Implicit (Logical) | I |
V | Visual | |||
2 | Direction | L | Left to Right | L |
R | Right to Left | |||
3 | Symmetric Swapping | Y | Symmetric swapping is on | Y |
N | Symmetric swapping is off | |||
4 | Shaping | Y | Text is shaped | N |
N | Text is not shaped | |||
5 | Numeric Shaping | H | Hindi | N |
C | Contextual | |||
N | Nominal |
WebSphere Business Integration Server Express supports bidirectional scripts for communication links from an outside environment. The external systems use Access Interface to connect to WebSphere Business Integration Server Express. Bidirectional script data from the source is converted to the standard Windows-type bidirectional format for processing. The data is then converted back to its original format for communication with the source.
Since configuration, and not development, is necessary for this bidirectional conversion, the System Administrator rather than the developer is responsible for supporting this feature.
You can define the properties for the collaboration template in Process Designer Express and provide values for these properties at deployment in System Manager.
For more information on setting collaboration object properties, see the System Implementation Guide.
Configuring the collaboration template for bidirectional data with Access InterfaceTo define one bidirectional format for all business object data passed through all collaboration ports, add the following property:
BiDi_AI_Application --The name is not case sensitive. Valid values are 5-letter strings specifying the bidirectional format of business object data passed between the external application and the collaboration. For a list of valid values for this property, see Table 25.
To define different bidirectional formats for business object data passed to the collaboration through different ports, add the following property for each port:
BiDi_<port name>_AI_Application -- The name is not case sensitive. Valid values are 5-letter strings specifying the bidirectional format of business object data passed between the external application and the collaboration. For a list of valid values for this property, see Table 25.