Configuring global coordination with Sybase using a 32-bit queue manager

Configure your broker environment to globally coordinate message flow transactions with updates in Sybase databases under the control of a 32–bit queue manager.

Before you start:

All WebSphere® MQ Version 5.3 queue managers and all WebSphere MQ Version 6 queue managers on 32-bit platforms run in 32-bit mode. 32-bit queue managers can coordinate transactions only in 32-bit mode and can coordinate message flows that are deployed only to 32-bit execution groups.

All WebSphere MQ Version 6 queue managers on 64-bit platforms run in 64-bit mode. 64-bit queue managers can coordinate transactions only in 64-bit mode. If the broker uses a 64-bit queue manager, you can globally coordinate message flows that are deployed to either 64-bit or 32-bit execution groups, but if you are using 32-bit execution groups, you must define the data source name of the user database in both odbc.ini and odbc64.ini. If the broker uses a 64-bit queue manager, or has a 64-bit execution group, the databases to which the broker connects must also be 64-bit mode.

To configure your broker environment for global coordination using a 32-bit queue manager as the transaction manager:

  1. Linux platformUNIX platform On Linux® on x86 and UNIX® only, create the following symbolic links to specify the location of the database drivers that are supplied with WebSphere Message Broker:
    AIX platform On AIX®:
    ln –s install_dir/merant/lib/libUKicu20.a /var/mqm/exits/libUKicu20.a 
    ln –s install_dir/merant/lib/UKase20.so /var/mqm/exits/UKase20.so
    ln –s install_dir/merant/lib/UKasedtc20.so /var/mqm/exits/UKasedtc20.so
    HP-UX platform On HP-UX on PA-RISC:
    ln –s install_dir/merant/lib/libUKicu20.sl  /var/mqm/exits/libUKicu20.sl 
    ln –s install_dir/merant/lib/UKase20.sl /var/mqm/exits/UKase20.sl
    ln –s install_dir/merant/lib/UKasedtc20.sl /var/mqm/exits/UKasedtc20.sl
    Linux platformSolaris platform On Solaris on SPARC and Linux on x86:
    ln –s install_dir/merant/lib/libUKicu20.so /var/mqm/exits/libUKicu20.so 
    ln –s install_dir/merant/lib/UKase20.so /var/mqm/exits/UKase20.so
    ln –s install_dir/merant/lib/UKasedtc20.so /var/mqm/exits/UKasedtc20.so
  2. Configure the broker's queue manager with XA resource manager information for each database that is involved in the transaction that the queue manager will globally coordinate. If the message flows reference message dictionaries, or contain Publication nodes, you must use the same method to define XA resource manager information for the broker database and for the user databases.

    Linux platformUNIX platform On Linux on x86 and UNIX:

    1. Open the queue manager's qm.ini file in a text editor. The qm.ini file is located at /var/mqm/qmgrs/queue_manager_name/qm.ini, where queue_manager_name is the name of the broker that is associated with the queue manager.
    2. At the end of the qm.ini file, paste the following stanza:
      XAResourceManager:
          Name=SYBASEXA
          SwitchFile=SwitchFileName
          XAOpenString=-NSYBASEDB -AMyServerName,MyPortNumber -Uuid -Ppwd -K2
          XACloseString=
          ThreadOfControl=THREAD
    3. On the SwitchFile line of the stanza, replace SwitchFilePath with the full path to the switch file for your operating system. The following table shows the file path of the switch file for each operating system, where install_dir is the location in which the broker is installed.
      Operating system Switch file path
      HP-UX on PA-RISC install_dir/merant/lib/UKasedtc20.sl
      All other platforms install_dir/merant/lib/UKasedtc20.so

      The switch file is supplied by WebSphere Message Broker.

    4. On the XAOpenString line, replace the following values with values that are appropriate for your configuration:
      • MyServerName is the name of the TCP/IP host that hosts the Sybase ASE server.
      • MyPortNumber is the TCP/IP port on which the Sybase ASE server is listening.
      • uid must be the user name that the broker uses to connect to the database. The user name that the broker uses can be defined in a number of ways. If you use the -u parameter on the mqsicreatebroker command when you create the broker, this user name is used to connect to the database, unless the mqsisetdbparms command has been used to associate a specific user name and password with a specific data source name (DSN). If you use neither the -u parameter on the mqsicreatebroker command, nor the mqsisetdbparms command, the name used is the broker's service user name, which you define with the -i parameter on the mqsicreatebroker command.
      • pwd is the password that is associated with the user name.
    5. Accept the default values for all the other lines in the stanza. For example, on AIX:
      XAResourceManager:
          Name=SYBASEXA
          SwitchFile=/opt/mqsi/merant/lib/UKasedtc20.so
          XAOpenString=-NSYBASEDB -Adiaz,1521 -Uwbrkuid -Pwbrkpw -K2
          XACloseString=
          ThreadOfControl=THREAD
    On Windows®:
    1. From the Start menu, open the graphical administration tool for your version of WebSphere MQ:
      • WebSphere MQ Version 5.3: WebSphere MQ Services
      • WebSphere MQ Version 6: WebSphere MQ Explorer
    2. Open the queue manager's Properties dialog box, then open the Resources (Version 5.3) or XA resource managers (Version 6) page.
    3. In the SwitchFile field, enter the full path to the switch file, as shown in the following example where install_dir is the location in which the broker is installed:
      install_dir\bin\ukase20.dll
    4. In the XAOpenString field, paste the following string:
      -NSYBASEDB -AMyServerName,MyPortNumber -WWinsock -Uuid -Ppwd -K2
    5. In the XAOpenString field, replace the values with values that are appropriate for your configuration:
      • install_dir is the location in which the broker is installed.
      • MyServerName is the name of the TCP/IP host that hosts the Sybase ASE server.
      • MyPortNumber is the TCP/IP port on which the Sybase ASE server is listening.
      • uid must be the user name that the broker uses to connect to the database. The user name that the broker uses can be defined in a number of ways. If you use the -u parameter on the mqsicreatebroker command when you create the broker, this user name is used to connect to the database, unless the mqsisetdbparms command has been used to associate a specific user name and password with a specific data source name (DSN). If you use neither the -u parameter on the mqsicreatebroker command, nor the mqsisetdbparms command, the name used is the broker's service user name, which you define with the -i parameter on the mqsicreatebroker command.
      • pwd is the password that is associated with the user name.
      For example:
      -NSYBASEDB -Adiaz,1521 -WWinsock -Uwbrkuid -Pwbrkpw -K2
    6. Accept the default values for all the other fields on the page.
  3. Stop then restart the queue manager to apply the changes, because qm.ini is read only while the queue manager is running.
    To stop then restart the queue manager, enter the following commands, where queue_manager_name is the name of the queue manager:
    endmqm queue_manager_name
    strmqm queue_manager_name

    When the queue manager restarts, check the queue manager's log for any warnings that are associated with the restart. The log files are located in /var/mqm/qmgrs/queue_manager_name/errors, where queue_manager_name is the name of the queue manager that you restarted.

    When the queue manager restarts successfully, the changes that you made to qm.ini are applied.

Sybase is now configured for global coordination with a 32-bit queue manager coordinating transactions.

Next: you can deploy globally coordinated message flows to the broker.
Related tasks
Configuring globally coordinated message flows
Configuring global coordination of transactions (two-phase commit)
Related reference
Supported databases
mqsicreatebroker command - Windows, Linux, and UNIX systems
mqsisetdbparms command
Related information
WebSphere MQ Version 6 information center online
WebSphere MQ library Web page
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:19:59

ac00920_