Starting the system after a machine shutdown

The following sections describe how to start the system components if the machine where they reside has been out of service. You must first start DB2 and WebSphere MQ before you can start the Business Integration Connect components.

Starting DB2

To start DB2, use the following procedure.

  1. Change to the database owner (db2inst1 if the default was used):
    su - db2inst1
    
  2. Start the database instance:
    db2start
    

Starting WebSphere MQ

To start WebSphere MQ, use the following procedure.

  1. Change to the WebSphere MQ user:
    su - mqm
    
  2. Start the queue manager:
    strmqm <hostname>.queue.manager
    
  3. Start the listener:
    runmqlsr -t tcp -p <port number> -m <hostname>.queue.manager &
    
  4. Wait about 10 seconds and press Enter to return to the command prompt.
  5. Start the JMS Broker (the publish-subscribe broker):
    strmqbrk -m <hostname>.queue.manager
    

Starting Community Console, Receiver, and Document Manager

To start Community Console, Receiver, and Document Manager, use the following procedure.

  1. Change to the general Business Integration Connect user:
    su - bcguser
    
  2. Navigate to the Community Console script directory:
    cd <installation location>/console/was/bin
    

    where <installation location> is where Business Integration Connect is installed.

  3. Start Community Console:
    ./startServer.sh server1
    
  4. Navigate to the Receiver script directory:
    cd <installation location>/receiver/was/bin
    
  5. Start the Receiver:
    ./startServer.sh server1
    
  6. Navigate to the Document Manager script directory:
    cd <installation location>/router/was/bin
    
  7. Start the Document Manager:
    ./startServer.sh server1
    

Copyright IBM Corp. 2003, 2004