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


Deploying integration solutions during development

During development, you can deploy a solution directly to an integration server by using options in the IBM® Integration Toolkit.

Before you begin

You must have an integration node and integration server that are defined in the IBM Integration Toolkit. By default, the IBM Integration Toolkit is configured with a single integration node that is named TESTNODE_user_name (where user_name is the name of the user who is logged in), and an integration server that is named default. If you disabled the creation of these resources, you can manually create an integration node and integration server; see Creating an integration node.

About this task

The mode in which your integration node is working can affect the number of integration servers and message flows that you can deploy, and the types of node that you can use. See Restrictions that apply in each operation mode.

If you are developing a solution and you want to test the solution or some of the solution resources quickly, you can deploy the resources that you want to test directly to an integration server. You can deploy the following resources:
  • An application or library
  • A message flow that is contained in an integration project
  • A subflow that is defined in a .subflow file and contained in an integration project
Note: For prerequisites and guidelines that are associated with the deployment of integration solutions, see Deployment rules and guidelines.

Procedure

In the IBM Integration Toolkit, deploy your resources by using one of the following methods:

Results

Your solution resources are deployed. One or more BAR files are generated automatically, and deployed to the integration node. You can find these BAR files in the GeneratedBarFiles folder in the Application Development view. If you deploy an application that refers to a static library, the static library is added to the same BAR file as the application. If you deploy an application that refers to a shared library, you must first deploy the shared library; a separate BAR file is generated for the shared library.


af26200_.htm | Last updated 2015-09-24 12:52:43