Using converters from a previous level of the product

If you have applications that need a code page that is not in the default set of code pages that WebSphere® Message Broker Version 6.0 supports, you can use a code page from an earlier version of WebSphere Message Broker.

Before you start:
  • Read Code page converters, which provides information about what a code page converter is, and about the code pages that WebSphere Message Broker supports.

The changes in converters between WebSphere Business Integration Message Broker Version 5.0 and WebSphere Message Broker Version 6.0 are significant, therefore the set of converters from the previous level has been included with WebSphere Message Broker Version 6.0.

To use one of the converters from the previous version:

  1. Extract the list of WebSphere Business Integration Message Broker Version 5.0 code page converters from your installation directory to a temporary directory:
    • On Windows®: extract install_dir\sample\converters\mqsiconverters-v5.zip
    • On Linux®: extract install_dir/sample/converters/mqsiconverters-v5.tar.bz2
    • On UNIX®: extract install_dir/sample/converters/mqsiconverters-v5.tar.gz
    where install_dir is the directory you have specified for your WebSphere Message Broker installation.
  2. Find the .cnv file for the code page that you want in the temporary directory, and copy it to a directory that is accessible by the broker. Give the file a unique name to make sure that the copied file does not conflict with an existing converter; do not use a number that is already used in one of the supported code pages. For example:
    • Linux platformUNIX platform On Linux and UNIX systems, copy the file to /var/mqsi/converters.
    • Windows platform On Windows systems, copy the file to C:\Documents and Settings\All Users\Application Data\IBM\MQSI\converters. C:\Documents and Settings\All Users\ is the default path; the actual value might be different on your computer.

    If the converter will be used by ESQL, the converter must be of the form ibm-<ccsid>, because converters are referenced through their numeric CCSID, not their name.

  3. Associate the broker with the code page converter by entering the name of the directory where you have stored the converter.

    If you are using a converter that matches one of the built-in converters that are provided with Version 6.0, and that converter is the local code page for the broker, do not use the mqsicreatebroker or mqsichangebroker command with the -c parameter to set the converter path. Use the ICU_DATA environment variable instead.

    • To create a new broker that is associated with a converter, include the -c parameter on the mqsicreatebroker command.
    • To alter an existing broker to recognize the converter, include the -c parameter on the mqsichangebroker command. For example:
      mqsichangebroker broker_name -c directory
    • To affect all the products and the broker command-line tools using international components for Unicode (ICU), add the directory to the ICU_DATA environment variable.
    If you have already used either the mqsicreatebroker command or the mqsichangebroker command to specify the code page converter to be used, the broker ignores the ICU_DATA value.

    Copy the entire set of converters (*.cnv) and aliases (*.icu) to reproduce the behavior of the previous level of the product.

Related concepts
Code page converters
Related tasks
Changing locales
Related reference
Supported code pages
mqsicreatebroker command
mqsichangebroker command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:20:36

ac30160_