WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Creating a graphical data map programmatically

Use the Graphical Data Map Specification Language to create a graphical data map programmatically.

The file msl.xsd provides the XML schema that describes the Graphical Data Map Specification Language, also known as MSL. This file is available in the Graphical Data Mapping component Version 1040, and later versions.

You can find the msl.xsd file inside the com.ibm.msl.mapping.api_7.5.0.jar jar file.

In IBM® Integration Bus, you can find the jar file in any of the following directories:
  • In a 32 bit Windows platform installation: C:\Program Files(x86)\IBM\MQSI\server\ct\lib\
  • In a 64 bit Windows platform installation: C:\Program Files\IBM\MQSI\server\ct\lib\
  • In a Linux platform installation: /opt/ibm/mqsi/server/ct/lib/

You must perform the following steps to programmatically generate a map file:

  1. Create a template map in the Graphical Data Mapping editor.

    Deploy and test your template map in the run time to confirm that the message transformation is correct.

  2. Inspect the MSL XML content in the template map.

    Use the MSL schema to identify the mapping constructs and the definition of the points of variation for the template map.

  3. Develop the scripts and programs to generate the MSL XML for the new maps that you plan to generate programmatically.

    When you use a development approach based on JAXB, the bindings file msl_jaxb_bindings.xml available in the com.ibm.msl.mapping.api_7.5.0.jar file provides the minimal required bindings.

  4. Validate the syntax of each generated map file (.map) against the provided MSL schema msl.xsd.
  5. Import each generated map file into your development environment. Then, check that all the referenced resources, such as xsd files, are imported into the relevant project types. Ensure the relevant builder is invoked to semantically validate each generated map file. Also, check using the Graphical Data Mapping editor that the transforms in your generated map are correct and free of error and warnings.
  6. Package and deploy into the run time your programmatically generated maps. Then, test your application to confirm that the message transformation is correct.

    Check that each generated map file is built into the relevant deployment artifact.

Deploy and test the map. For more information, see Troubleshooting graphical data maps.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:30


Task topicTask topic | Version 8.0.0.7 | cm28007_