New users: Use this topic to get information about deploying and testing your message flows during development. When you have developed your message flows, message models, and other resources, you are ready to deploy them to an integration node.
You can use features that are provided in the IBM® Integration Toolkit to help you test your message flows. Read How do I deploy and configure message flows? for information about deploying and configuring message flows for use in a production environment.
Use the links in this section to get instructions on how to deploy your message flows, message model schema files, and related resources to an integration node. Read Deploying integration solutions for an overview of the concepts of deployment of message flow resources.
A BAR file is a compressed file that contains compiled message flows, message dictionaries, and other application development resources. Use this link for instructions about how to create a BAR file. You can use the BAR file editor to add or remove message flows and message model schema files to, or from, your BAR . You can also use the BAR editor to edit the configurable properties in your BAR .
You can add message flows and message model schema files to a BAR file. The message flows, message model schema files, and related resources are compiled when they are added to the BAR file. You can also choose to add the source files to the BAR file. You cannot add resources to a BAR file from a project that contains an error.
Find out about the different ways that you can deploy a BAR file to an integration node. For deploying message flows for development to a test environment, the simplest method is to use the IBM Integration Toolkit.
Find out about the ways that you can check the results of deployment. When you deploy message flows to a test environment, the simplest method is to use the IBM Integration Toolkit. You can also use the mqsilist command with the name of the integration node and integration server to which you deployed your BAR file.
System objects that are defined in message flows have configurable properties that you can update within the BAR file before deployment. By changing configurable properties, you can customize a BAR file for a new domain, without needing to edit and rebuild the message flows or other resources.
You can refresh the contents of a BAR file by removing resources from it and, having made required changes, add the resources back again. Alternatively, you can use the Refresh option in the BAR file editor.
Use the links in this section to get information about the different features that are provided in the IBM Integration Toolkit to help you to check that your message flows are processing messages as expected.
You can use the flow debugger to help test your message flows by tracking the path that a message takes through your message flow. You can also step through the ESQL, Java™, and message mappings in your message flows, to view the output messages that are being constructed.
If you are having difficulty deploying your message flows and other resources, or receiving unexpected results when you test your message flows, look at the problem determination information in this topic.