Using
bidirectional functionality in Activity Editor
WebSphere Business Integration Server Express supports
bidirectional languages. This support is in a standard Windows-type
bidirectional format (logical left to right). Because of this support,
all maps also support bidirectional languages. However, data entering
a map may come from:
- An adapter that supports bidirectional languages. To determine
if your adapter supports bidirectional languages, see your adapter's
user's guide.
- A component that does not support
bidirectional languages, an adapter that does not support bidirectional
languages, or data imported from some external source where the
bidirectional support is unknown.
Bidirectional format inconsistencies cause comparisons within
a map to return incorrect results. These types of errors can be
avoided by:
- Only accepting input from sources that enforce the same bidirectional
format as the WebSphere Business Integration Server Express system
such as the adapters that are already enabled with this support.
- Enabling the connectors to this map to enforce the correct bidirectional
format (see "Enabling connectors for bidirectional languages" in
the Collaboration Development Guide).
- Using the APIs in the CwBidiEngine class to transform all data
into a consistent bidirectional format (see CwBidiEngine class).
InterChange Server Express automatically
enables BiDi functionality with the following ten connectors: Email, JDBC, JMS, JText, Lotus Domino, MQ Series, PS, SAP, Web services, and XML. Therefore, when data in Windows BiDi format utilizes these
enabled connectors in a Web service no special configuration is
needed.
In the event that a Web service operates with BiDi data that
is not in Windows BiDi format, two results are possible:
- The connection to such a service might fail all together.
- The BiDi data that is in a format different from Common Windows
Bidirectional Format (CWBF) gives unpredictable results in data
processing because the data is being compared against data in the CWBF format.
In other words, identical information is being held in different
BiDi formats. To rectify these potential situations, you need to
perform the following steps for Web service deployment inside Activity
Editor.
Steps for deploying Bidi API in a Web service
Perform these steps to deploy BiDi in a Web service:
- Register the Web service.
For information on registering, testing, verifying and exporting
a Web service see the System Implementation Guide.
- Test the Web service using BiDi data to determine the BiDi format
standard.
- Export the Web service into Activity Editor.
- Design the data flow using Activity Editor. Figure 84 shows an example of a BiDi design process.
Figure 84. Activity Editor screen with BiDi elements
- Add calls to BiDi API inside the generated code just before
the data is sent to the Web service and just after the reply is
received to preserve the BiDi data consistency.
Note:
For more information on the BiDi transformations
of BO instance content used in the BiDi API, see
CwBidiEngine class.
