Starting supporting software

Before you start InterChange Server, verify that:

Note:
You must start the supporting software (such as the database server and WebSphere MQ) before you start InterChange Server.

Verifying the database server

On a UNIX system, the databases that InterChange Server uses are managed by either the DB2 or Oracle server. To determine if the server is running, verify that:

Oracle:
Before you can access Oracle tools, make sure that you set the Oracle environment variables such as ORACLE_HOME and ORACLE_SID. For information about these environment variables, see Table 16. You might want to add these environment variables to the personal profile file (such as .profile) of the WebSphere business integration administrator account.
DB2:
Before you can access DB2 server, make sure that you set the DB2INSTANCE environment variable. For information about this environment variable, see Table 15. You might want to add this environment variable to the personal profile file (such as .profile) of the WebSphere business integration administrator account.

Starting WebSphere MQ Queue Manager

After the InterChange Server software is installed, you must configure the WebSphere MQ messaging system to work with InterChange Server by:

Important:
If using DB2 Server, set EXTSHM=OFF before starting WebSphere MQ. See Installation information for the location of this setting. After WebSphere MQ is started successfully, set EXTSHM=ON before starting InterChange Server.

Configuring the WebSphere MQ scripts

Do the following to configure the WebSphere MQ scripts:

  1. Go to the ProductDir/mqseries directory.
  2. Make sure that the name of the WebSphere MQ queue manager in the clear_mq, configure_mq, start_mq, and end_mq scripts matches the name that the UNIX system administrator has assigned in the queue manager line of the /etc/inetd.conf system file.
    Note:
    If you are working on Linux, the name of the queue manager is defined in a configuration file in the /etc/xinetd.d directory, rather than in the /etc/inetd.conf system file.

    Installer assigns the value from the Queue Manager Name field in the WebSphere MQ tab in the InterChange Server Configuration GUI as the name of the queue manager in the crossworlds_mq.tst, clear_mq, configure_mq, start_mq, and end_mq scripts.

    If the value entered in this field does not match the name in the /etc/inetd.conf entry for your queue manager, WebSphere MQ does not operate correctly. Change the clear_mq, configure_mq, start_mq, and end_mq scripts to match the name defined in the /etc/inetd.conf system file. If you need help determining the queue name from this system file, consult your UNIX system administrator.

  3. Check the crossworlds_mq.tst file to make sure that the entries for all queue definitions are correct.

    Be sure that:

If you need to customize the WebSphere MQ scripts, you can customize the executable scripts in the ProductDir/mqseries directory. Changes you make directly in these versions of the WebSphere MQ scripts are overwritten if you reconfigure InterChange Server from the Apply button of the WebSphere MQ tab in the InterChange Server Configuration GUI.

Setting up the WebSphere MQ message system

To set up the WebSphere MQ messaging system for InterChange Server:

  1. Make sure that the crossworlds_mq.tst, configure_mq, and start_mq scripts in the ProductDir/mqseries directory are configured correctly for your system. For more information, see "Configuring the WebSphere MQ scripts".
  2. If you have already created a queue manager, delete it before creating the new one.
  3. Make sure you are logged in as a user with WebSphere MQ privileges.

    Start up WebSphere MQ and run scripts in the mqseries directory as the WebSphere business integration administrator (admin) or another user who is a member of the WebSphere MQ group, mqm. If you are not already one of these users, use the su command or log in again as the appropriate user. You can use the groups command to obtain a list of the groups to which you belong.

  4. Run the configure_mq script with the following command:
    ./configure_mq
    
    
    

    This script creates a WebSphere MQ queue manager and assigns it the name that was defined in the installation program. Create a queue manager only the first time you configure an InterChange Server system. The output of a successfully run command contains the line:

    No commands have a syntax error.
    
  5. Start the WebSphere MQ queue manager with the following command:
    ./start_mq
    
    
    
  6. Run the testMQ.sh script to see if WebSphere MQ is ready for communication with InterChange Server by navigating to the directory ProductDir/bin and running the testMQ.sh script by entering the following command:
    ./testMQ.sh
    
    
    

Check the /var/mqm/errors directory to ensure that there were no errors logged to AMQERR01. To stop the WebSphere MQ queue manager, use the end_mq script.

Copyright IBM Corp. 1997, 2004