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
See information about the latest product version
Implementing the solution
Implementing the solution in this scenario involves converting the message mapping solution to a graphical data map.
Before you begin
About this task
Figure 1. Order of tasks to complete
for this scenario.

To implement the scenario, you must complete the following steps:
- If you are using the provided sample files for the scenario, download and check the configuration. See Creating the scenario message map configuration.
- Convert the message map to a graphical data map. See Converting the message map.
- When the map is converted, check the transform behavior and configure. See Configuring the converted transforms.
- 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 UNIX and Linux systems, the local error log is the syslog. Where syslog messages are sent depends on how you configure your UNIX or Linux system.
- On z/OS®, the local error log is the operator console.
- On DB2®,
The Windows Event Viewer is where WebSphere® Message Broker writes
records to the local system. Use Windows system
facilities to view this log:
- Open a command prompt.
- At the prompt, type eventvwr. The Windows Event Viewer opens.
- Click .
- Review the error or errors listed.
For more information abut error logs, see Local error logs.
To see
what the scenario files look like before and after conversion, review: