Migrating a user-defined node from Version 5.0 or Version 5.1

Migrate your user-defined nodes to Version 6.0.

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

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

To migrate from the Version 5.1 Message Brokers Toolkit to the Version 6.0 Message Brokers Toolkit:
  1. Import the user-defined node project into the Version 6.0 Message Brokers Toolkit.
  2. Select your user-defined node project in the Package Explorer, and click Project > Clean Project.

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

  1. Import the user-defined node project into the Version 6.0 Message Brokers Toolkit.
  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.

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.0 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 Brokers Toolkit, and you have not yet deployed to it, you can add the LIL, PDB, and JAR files to your chosen directory.
    • If you have already deployed to the execution group that you want to use, add the LIL, PDB, and JAR files 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, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:23:16

as10009_