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


Deploying an integration solution

After you have created and populated a BAR file with the integration solution resources, deploy the integration solution to an integration server

Before you begin

Package your integration solution in a BAR file; see Packaging resources.

About this task

If you change a BAR file, and want to propagate those changes to one or more integration nodes, you can redeploy the updated BAR file by following the instructions in Redeploying a BAR file.

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.

When you deploy a message flow that contains a subflow that is defined in .subflow file, you must deploy the subflow to the same integration server. You cannot deploy the message flow before the subflow, but you can deploy the subflow first, or both resources together. If you redeploy a subflow that is defined in a .subflow file to an integration server, any message flows that use the subflow in that integration server are stopped and restarted. When the message flows restart, they use the updated subflow.

If you deploy an application that references a shared library, you must deploy the shared library before you can deploy the application.

Deploying with the web user interface

About this task

You can select a BAR file and deploy it to an integration server by using the web user interface.

You can also select an overrides file, which defines the BAR file properties that you want to change for a specific deployment. For more information, see mqsiapplybaroverride command.

Procedure

  1. Start the web user interface for your integration node; see Accessing the web user interface. The navigator is displayed on the left side of the pane, showing the servers (integration servers), message flows, and other resources that are owned by your integration node.
  2. Expand the Servers section and click the arrow beside the integration server (where you want to deploy the BAR file) to display the menu.
  3. Click Deploy. The Deploy BAR File dialog is displayed.
  4. To select a BAR file, click Browse, navigate to your BAR file and click Open. The BAR file properties and the associated values are displayed in the dialog.
  5. Optional: To select an overrides file, click the down arrow beside Overrides and click Select overrides file, navigate to the overrides file, and click Open. For information about the format of an overrides file, see mqsiapplybaroverride command. Any property values that are specified in the overrides file are displayed in the dialog, in place of the original property values. If you want to restore the original property values from the BAR file, click the down arrow beside Overrides and click Clear overrides file.
  6. Click Deploy.

Results

The BAR file is transferred to the integration node, which deploys the file contents to the integration server. In the web user interface navigator, the deployed resources are listed under the appropriate integration server.

Deploying with the IBM Integration Toolkit

About this task

To deploy a BAR file by using the IBM® Integration Toolkit, complete the following steps. You can deploy to only one integration server at a time.

Procedure

  1. Optional: Typically, an incremental BAR file deployment is performed. To perform a complete BAR file deployment, right-click the target integration server in the Integration Nodes view and click Delete > All Flows and Resources. Wait for the operation to complete before continuing.

    Do not click Delete > All Flows and Resources if you want to refresh one or more of the child processes with the contents of the BAR file. For an explanation of the difference between a complete and an incremental BAR file deployment, see BAR file deployment.

  2. Deploy a BAR file or message flow to an integration server by using one of the following methods. If you want to deploy .msgflow files and .subflow files that are contained in an application or library, you must deploy the containing application or library.
    • Drag an application, library, .msgflow file, .subflow file, or BAR file onto your target integration server in the Integration Nodes view.
    • Right-click the application, library, .msgflow file, .subflow file, or BAR file, then click Deploy. The Deploy dialog box opens, listing the integration servers to which the IBM Integration Toolkit is connected.

      Select an integration server, then click OK.

    • Right-click the integration server, and click Deploy. The Resources dialog box opens. You can choose to deploy resources from the workspace, or BAR files from the file system.
      • Specify the type of resource to deploy by selecting the appropriate radio button. The available resources for that category are listed.
      • Select the resource that you want to deploy.
      • Click OK.
  3. If you have not saved the BAR file since you last edited it, you are asked whether you want to save the file before deploying. If you click Cancel, the BAR file is not saved and deployment does not take place.

Results

The BAR file is transferred to the integration node, which deploys the file contents (for example, message flows and message sets) to the integration server. In the Integration Nodes view, the deployed resources are added to the appropriate integration server.

Deploying with the mqsideploy command

About this task

To deploy a BAR file by using the mqsideploy command, complete the following steps.

Procedure

  1. Open a command window that is configured for your environment.
  2. Enter the appropriate command for your operating system and configuration, by using the following examples as a guide.
    On distributed systems:
    mqsideploy -i ipAddress -p port -e egroup -a barfile

    The command performs an incremental deployment. Add the -m parameter to perform a complete BAR file deployment.

    The -i (IP address) and -p (port) parameters represent the connection details for the queue manager that is associated with the integration node. If you have created the integration node on the computer on which you run this command, you can specify the integration node name instead.

    You must also specify the -e (integration server name), and -a (BAR file name) parameters.

    On z/OS®:
    /f IB01NODE,dp e=egroup a=barfile

    The command performs an incremental deployment. Add the m=yes parameter to perform a complete BAR file deployment.

    In the example, IB01NODE is the name of the integration node. You must also specify the names of the integration server and the BAR file (the e= and a= parameters).

Results

The command reports when responses are received from the integration node. If the command completes successfully, it returns 0 (zero).

Deploying with the IBM Integration API

About this task

To deploy by using the IBM Integration API, use the deploy method of the ExecutionGroupProxy class.

The following code shows how an application can perform an incremental deployment:
import com.ibm.broker.config.proxy.*;
public class DeployBAR {

  public static void main(String[] args) {
    BrokerConnectionParameters bcp =
       new IntegrationNodeConnectionParameters("localhost", 4414);
    try {
      BrokerProxy b = BrokerProxy.getInstance(bcp);
      ExecutionGroupProxy eg = b.getExecutionGroupByName("default");
      DeployResult dr = eg.deploy("MyBAR.bar", true, 30000);
      System.out.println("Result = "+dr.getCompletionCode());
    } catch (Exception e) {
      e.printStackTrace();
    }
  }
}
By default, the deploy method performs an incremental deployment. To perform a complete deployment, use a variant of the method that includes a false value for the Boolean isIncremental parameter. For example, e.deploy("deploy.bar",false,0). Set this parameter to true to request an incremental deployment.

af03890_.htm | Last updated 2015-05-28 20:51:08