IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Configuring global coordination with Sybase

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

Before you start:

To configure your broker environment for global coordination using a WebSphere® MQ queue manager as the transaction manager with the DataDirect drivers:

  1. Linux platformUNIX platformOn Linux and UNIX, run the mqsimanagexalinks command.
  2. Configure the broker queue manager with XA resource manager information for each database that is involved in the transaction that the queue manager will globally coordinate.

    Linux platformUNIX platformOn Linux 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=UKasedtc26.so
          XAOpenString=-NSYBASEDB -AMyServerName,MyPortNumber -Uuid -Ppwd -K2
          XACloseString=
          ThreadOfControl=THREAD
    3. 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.
        You can define the user name that the broker uses in a number of ways; make sure that you specify the correct name in this file. The broker determines the user name by checking the following conditions in the order listed:
        1. A specific user name and password for this data source name (DSN), that you have defined by running the mqsisetdbparms command.
        2. A default user name and password for all DSNs, that you have defined by running the mqsisetdbparms command.
        3. A default user name and password for all DSNs, that you have defined by specifying the -u parameter on the mqsicreatebroker command.

          This parameter is valid only for brokers that you have migrated from previous releases.

        4. The broker 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.
    4. Accept the default values for all the other lines in the stanza. For example:
      • On AIX®:
        XAResourceManager:
            Name=SYBASEXA
            SwitchFile=UKasedtc26.so
            XAOpenString=-NSYBASEDB -Adiaz,1521 -Uwbrkuid -Pwbrkpw -K2
            XACloseString=
            ThreadOfControl=THREAD
    Windows platformOn Windows 32-bit:
    1. From the Start menu, open WebSphere MQ Explorer.
    2. Open the Properties dialog box for the queue manager, then open XA resource managers.
    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\ukase26.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.
        You can define the user name that the broker uses in a number of ways; make sure that you specify the correct name in this file. The broker determines the user name by checking the following conditions in the order listed:
        1. A specific user name and password for this data source name (DSN), that you have defined by running the mqsisetdbparms command.
        2. A default user name and password for all DSNs, that you have defined by running the mqsisetdbparms command.
        3. A default user name and password for all DSNs, that you have defined by specifying the -u parameter on the mqsicreatebroker command.

          This parameter is valid only for brokers that you have migrated from previous releases.

        4. The broker 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 and 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 log for all 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 your queue manager coordinating transactions.

Next: you can deploy globally coordinated message flows to the broker.

ac00920_.htm | Last updated Friday, 21 July 2017