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:

Bidirectional format inconsistencies cause comparisons within a map to return incorrect results. These types of errors can be avoided by:

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:

Steps for deploying Bidi API in a Web service

Perform these steps to deploy BiDi in a Web service:

  1. Register the Web service.

    For information on registering, testing, verifying and exporting a Web service see the System Implementation Guide.

  2. Test the Web service using BiDi data to determine the BiDi format standard.
  3. Export the Web service into Activity Editor.
  4. Design the data flow using Activity Editor. Figure 84 shows an example of a BiDi design process.
    This figure shows the Activity Editor with Web services containing BiDi characters highlighted in red. The screen displays the exported with Web services highlighted in the upper-left section, the Function Blocks highlighted in the lower-left and upper-right sections, and the generated code highlighted in the lower-right section. Any Web service that has BiDi characters must be correctly displayed in each section. (Highlights are circled in red.)
    Figure 84. Activity Editor screen with BiDi elements
  5. 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.

Copyright IBM Corp. 2004, 2005