IBM Integration Bus, Version 10.0.0.0 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Deploying message maps

By default, message map files are deployed in BAR files as a part of an application, integration service, or library that provides an integration solution. You can also deploy a map as an independent resource if you are managing your message flows that way. If you change a message map, you must redeploy your integration solution, or independent message flows.

About this task

IBM® Integration Bus prepares message maps for execution on deployment instead of when the first message is flowed through the Mapping node.

This behavior has the following advantages:
  • There is no drop in performance from initializing a message map when the first message is flowed through the node.
  • The message map and its dependencies, such as any referenced message models, are resolved and validated during deployment to ensure that the message map runs successfully on first message.
  • The message map syntax is validated during deployment to ensure that the message map runs successfully on first message.
  • When IBM Integration Bus is restarted, the message map syntax and its dependencies are validated before the message flow can be restored.
Note: To avoid a deployment failure, you must include all the message map dependencies, referenced schemas, ESQL modules, Java™ classes, and other resources in your BAR file. You must resolve any message map static errors such as an invalid XPath expression. If these requirements are not met, you receive a BIP message that reports the map generation failure.

Procedure

When you deploy message maps, the behavior of IBM Integration Bus is as follows:


br28805_.htm | Last updated 2015-03-27 19:28:35