Implementing the solution for the message map conversion scenario

Implementing the solution in this scenario involves converting the message mapping solution to a graphical data map.

Before you begin

The starting point for this scenario is an existing and working message map for the initial messaging infrastructure. If you want to try out the scenario, you can either follow the instructions to convert your message map to a graphical data map, or set up a copy of the sample message map scenario as described in Creating the scenario message map configuration.

About this task

Figure 1. Order of tasks to complete for this scenario.
A diagram of each task required to convert a map

To implement the scenario, you must complete the following steps:

  1. If you are using the provided sample files for the scenario, download and check the configuration. See Creating the scenario message map configuration.
  2. Convert the message map to a graphical data map. See Converting the message map.
  3. When the map is converted, check the transform behavior and configure. See Configuring the converted transforms.
  4. Verify that the message flow works in the runtime. See Verifying the solution.
If you experience any technical problems during the process of implementing the scenario, check the error log for your system.
  • On Linux® systems, the local error log is the syslog. Where syslog messages are sent depends on how you configure your Linux system.
  • On z/OS®, the local error log is the operator console.
  • On DB2®, The Windows Event Viewer is where IBM® Integration Bus writes records to the local system. Use Windows system facilities to view this log:
    1. Open a command prompt.
    2. At the prompt, type eventvwr. The Windows Event Viewer opens.
    3. Click Windows Logs > Application.
    4. Review the error or errors listed.

For more information on error logs, see Local error logs.

To see what the scenario files look like before and after conversion, review the following topics: