Deploying to a message broker workspace

To deploy the project to a message broker workspace (for WebSphere Business Integration Message Broker used as the integration broker), do the following from System Manager:

  1. Right-click on the name of the new project in the User Projects panel, then select "Deploy to message broker workspace" as shown in the following illustration:
    Screen capture showing selection of "Deploy to message broker workspace"
    The following window appears, showing the available business objects:
    Screen capture showing "Deploy to Message broker workspace" window
  2. Choose the desired business objects in the list (or "Select all business objects" or "Show only Top level Business objects").
  3. Click Next. The following window appears:
    Screen capture showing Select the Parameters window
  4. Enter a name for the Message Set project (required) and any other parameters (optional). The parameters are described in more detail below:

    Message set project name . Any text string designating the name of this project. This name will appear in the System Manager window when deployment is complete.

    Base message set project and base message set. If you enter names of an existing base message set project and base message set, then the contents of the base message set will be used as the basis of the new destination project. All the message set definitions in the base project will be copied to the new destination project. In addition, the destination project will also include any business objects you selected from the previous window during this deployment. You can view the names of existing message set projects and base message sets from the Broker Application Development perspective of Message Broker Tooling.

    Note:
    You must enter both a base message set project and a base message set; if only one of these parameters is specified, it will be ignored, and only those business objects selected during this deployment will be included in the project.

    Replace existing project with the same name. This option is applicable if the name entered in the Enter message set project name field is identical to the name of an existing project. If so, selecting this option replaces an existing project's content with content based on your selections during this deployment (only the name remains the same) . If this option is not checked and the specified project name matches that of an existing project, then the project retains whatever business objects it already contained and those selected during this deployment will be added. All existing business objects with the same names will be overwritten. If this option is checked but the project name does not match an existing project, this option is ignored and a new project is created.

    Namespace aware and xml namespace format. By default, XML namespace format is set to short. It is important to select the correct combination of choices for Namespace aware and XML namespace format, or your deployment might fail. Refer to Choosing XML Namespace length for information on whether to select long or short for this parameter.

    Deploy in verbose mode . Selecting this option will cause more details of the deployment process to be displayed or logged during deployment.

  5. Click Finish. If the project deploys successfully, a window will display a message indicating successful deployment. In addition, The results of the deployment will be recorded in the default log file mqsicreatemsgdefs.report.txt,located in the importer directory (default directory eclipse ). Also refer to the console panel of System Manager; it will display which business objects have successfully deployed.
    Note:
    The Message Broker Toolkit must closed when you click Finish for deployment to succeed. If the Toolkit was open at this time, you will receive a message stating that deployment of some or all of the business objects and message sets failed. You must redeploy from the beginning of the process, making sure that the Toolkit is closed.


[ Top of Page | Previous Page | Next Page | Table of Contents ]

Copyright IBM Corp. 1997, 2003