WebSphere Message Brokers
File: as10009_
Writer: Lorraine Waitt

Task topic

This build: July 31, 2007 21:38:32

Migrating a user-defined node

Migrate your user-defined nodes to Version 6.1.

Start of changeThe tasks you must complete to migrate user-defined nodes depend on the version that you are migrating from:End of change

Start of change

Migrating a user-defined node from Version 6.0 and Version 5.1

To migrate from the Message Brokers ToolkitVersion 5.0 to the Message Brokers Toolkit Version 6.1:

  1. Import the user-defined node project into the Message Broker Toolkit Version 6.1.
  2. Select your user-defined node project in the Package Explorer, and click Project > Clean Project.
  3. If you have created new Version 6.1 brokers, copy the runtime code to each new broker system.
    • For C user-defined extensions, compile the code correctly for the target operating system. Save the .lil or .jar file in the directory that you specified for the -l parameter on the mqsicreatebroker or mqsichangebroker command.

      Also store the .pdb file that corresponds to the .lil file, in the same directory. The .pdb file provides symbolic information that is used in stack diagnostic information in the event of access violations or other software malfunctions.

    • For Java user-defined nodes, save the .lil or .jar file in the directory that you specified for the -l parameter on the mqsicreatebroker or mqsichangebroker command.
End of change

Migrating a user-defined node from Version 5.0

To migrate a user-defined node from Version 5.0 to Version 6.1, you must migrate both toolkit and runtime components.

Migrating the Message Brokers Toolkit representation of the user-defined node

To migrate from the Message Brokers Toolkit Version 5.0 to the Message Brokers Toolkit Version 6.1:

  1. Import the user-defined node project into the Message Brokers Toolkit Version 6.1.
  2. Select your user-defined node project in the Package Explorer, and click Project > Clean Project.
  3. Modify the <requires> element in the plugin.xml file in the user-defined node project root to match the following content:
    <requires>
            <import match="greaterOrEqual" plugin="com.ibm.etools.mft.api" version="6.0.0"/>
    </requires>
  4. Modify the extension point for "org.eclipse.help.contexts" in the same plugin.xml file to match the following content:
    <extension point="org.eclipse.help.contexts">
    	<contexts file="HelpContexts.xml"/>
    </extension>

When you have migrated your user-defined nodes, you do not need to migrate any message flows that contain the user-defined node.

You must now complete the step Migrating the user-defined node runtime code.

Migrating the user-defined node runtime code

To migrate the user-defined node runtime code:

  1. Store a copy of your compiled or packaged user-defined extension file on every broker system on which you intend to use it. Save the .lil or .jar file in the directory that you specified on the mqsicreatebroker or mqsichangebroker command for each Version 6.1 broker. (On Version 5.0 broker systems, the .lil or .jar file was saved in the installation directory.)
    • If you are migrating a Java user-defined node, you can build the user-defined extension file once and distribute it to each of your systems.
    • If you are migrating a C user-defined node, and all of your brokers are of the same machine type, you can build the user-defined extension file once and distribute it to each of your systems.
    • If you are migrating a C user-defined node and you have a cluster that consists of various machine types, for example one AIX, one Solaris, and one Windows broker, you must build the files separately on each machine type.
  2. For C user-defined extensions, also store the .pdb file that corresponds to the .lil file, in the specified directory. The .pdb file provides symbolic information that is used in stack diagnostic information in the event of access violations or other software malfunctions.
  3. Stop and start each broker to ensure that the existence of a new file is detected.
    A broker restart is not required in the following two scenarios:
    • If you have created an execution group in the Message Broker Toolkit, and you have not yet deployed to it, you can add the .lil, .pdb, and .jar file to your chosen directory.
    • If you have already deployed to the execution group that you want to use, add the .lil, .pdb, or .jar file to your chosen directory, then use the mqsireload command to restart the group. You cannot overwrite an existing file on the Windows operating system when the broker is running because of the file lock that is put in place by the operating system.
    Use these two approaches with caution because any execution group that is connected to the same broker will also detect the new .lil, .pdb, and .jar files when that execution group is restarted, or when something is first deployed to that execution group. By using the more conventional way of restarting the broker, you ensure that anyone with an interest in a particular execution group is made aware that recent changes have been made to the broker.

    These two situations assume that you have already completed the previous step, and have therefore used either the mqsichangebroker command or the mqsicreatebroker command to notify the broker of the directory in which the user-defined extension files have been placed.

    When you have installed a user-defined node, it is referred to by its schema and name, just like a message flow.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:38:32

as10009_ This topic's URL is: