Verifying and configuring installed prerequisites

Before you install Business Integration Connect, ensure that you have all the necessary prerequisites. The topics in this section give you a brief overview of the system hardware and software requirements, the supported databases, and the user accounts required to run Business Integration Connect software.

Pre-installation checklists are included at the end of this section to help prepare for the installation. These checklists list the tasks that must be performed before you install Business Integration Connect.

This section contains the following topics:

Adding user accounts

In order to connect with the database, Business Integration Connect requires a set of operating system users. The following procedure walks you through setting up these users. Although this procedure uses default names, you can substitute your own user and group names. Group and user names cannot exceed eight characters.

Note:
It is not necessary to create a group if you only plan to have one user.

To create user accounts:

  1. Click Start > Settings > Control screen, then double-click Administrative Tools > Computer Management > Local Users and Groups.

    The Local Users and Groups dialog box appears. Right click Users and select New User.

    The New User dialog box appears. Add users, bcguser, bcgcon, bcgdoc and bcgrecv. Also select the Password Never Expires option.

    Note:
    Oracle users are only required to create the bcguser user.
  2. Business Integration uses a user in this group to manage Business Integration Connect components.
  3. From the Users and Groups dialog box, right click Groups and select New Group.
  4. The New Group dialog box appears. Add the group bcggroup.
  5. Add the following users to bcggroup: bcguser, bcgcon, bcgdoc and bcgrecv.
    Note:
    Oracle users are only required to add bcguser user to bcggroup.
  6. Exit the computer management.
  7. Record the user names and passwords in the tables in "Pre-installation checklist tables".

Configuring WebSphere MQ

The following procedure describes how to configure WebSphere MQ after it is installed. See "Platform, hardware, and software requirements" for a list of SupportPacs and updates that must be applied. For information on specific commands used in this procedure, see the WebSphere MQ documentation.

Note:
The default queue manager name is bcg.queue.manager, and the default listener port is 9999. If you change these default values, you must be sure to change them everywhere that they are used.

To configure WebSphere MQ:

  1. Confirm that you are logged into your operating system as an administrator or a user that is a member of the administrator's group.
  2. Create the queue manager:

    crtmqm -q bcg.queue.manager

  3. Update the channel parameters by changing the properties in this procedure. From MQServices, right click your queue manager, select properties, and channels.

    Update the channel properties with the following values:

    MaxChannels=1000
     
    MaxActiveChannels=1000
    
  4. If the computer has more than one CPU, enter the following command:
    setmqcap <number of CPUs> 
    
  5. Start the queue manager with the following command:
    strmqm bcg.queue.manager
    
  6. Start the listener with the following command:

    runmqlsr -t tcp -p 9999 -m bcg.queue.manager

  7. The listener runs in this window, so leave it open.
  8. Open a new window and start the JMS Broker (the publish-subscribe broker) with the following command:
    strmqbrk -m bcg.queue.manager
    
  9. Start the MQ command services with the following command:
    strmqcsv bcg.queue.manager
    
  10. Use the Tools\MQSeries\create_wbic_queues.mqsc file to define the queues and channels for the queue manager:
    runmqsc bcg.queue.manager <
     <CD image>\Tools\MQSeries\create_wbic_queues.mqsc
    

    Where <CD image> is the location of Business Integration Connect CD or the location of the unarchived Business Integration Connect installation files.

  11. Use the MQHomeInstallDir\java\bin\MQJMS_PSQ.mqsc file to configure the JMS publish and subscribe queues:

    runmqsc bcg.queue.manager <
    MQHomeInstallDir\mqm\java\bin\MQJMS_PSQ.mqsc

  12. Record the MQ host name, queue manager name, and listener port in "Pre-installation checklist tables".

Installing and configuring DB2

For maximum performance in a production environment, the Business Integration Connect database should reside on a dedicated server.

When installing WebSphere Business Integration Connect, you can use the Create_db2.sql script to create and configure the database. The database is configured with the assumption that DB2 UDB is running on a multi-processor machine. In particular the DFT_DEGREE parameter is set to 4 which indicates that a SQL query is executed as 4 sub-processes running in parallel. If you are running DB2 UDB on a single processor machine, this configuration is not optimal and might cause a system memory and CPU conflict. We recommend that you review the database configuration with your database administration and modify it if necessary to conform to your specific database environment.

Note:
Business Integration Connect does not use the fenced-user option. Do not use the fenced-user ID as part of the Business Integration Connect Installation.

Use the following procedure to install and configure DB2:

  1. Install DB2 by following the installation instructions provided and using the DB2 Setup wizard. In the wizard, do the following:
  2. When you have completed the DB2 installation, install the FixPack2 using the instructions in the FixPackReadme.txt.
  3. If DB2 is not running, start it by running the following command:

    db2start

  4. Verify that the correct C++ compiler and libraries are installed. Make sure that system environment variables (%PATH, %LIB, %INCLUDE) are set to point to the C++ compiler. When you set the system environment variables, make sure you log out of Windows 2000 and log in to make sure the system environment has been updated with all new processes. Refer to the DB2 Application Development Toolkit documentation for the required package names, and versions.

If you are using an existing installation, do the following:

  1. Verify that the DB2 Application Development Toolkit is installed. For information on how to install the toolkit, see the DB2 documentation.
  2. Verify that the include directory exists. For example DB2HomeInstallDir\IBM\SQLLIB\include
  3. Verify that the correct C++ compiler and libraries are installed. Make sure that system environment variables (%PATH, %LIB, %INCLUDE) are set to point to the C++ compiler. When you set the system environment variables, make sure you log out of Windows 2000 and log in again to make sure the system environment has been updated with all the new processes. Refer to the DB2 Application Development Toolkit documentation for the required package names, and versions.

Record the names and passwords in the tables in "Pre-installation checklist tables".

Installing and configuring Oracle

This guide does not provide installation instructions for Oracle 9i. See the appropriate Oracle documentation for the installation procedures.

IBM recommends that you follow these guidelines as you install your Oracle database:

  1. Export Oracle system environment variables, as described in the Oracle installation documentation. This is required for the administrator user if the Database Loader is to run SQL automatically during the Business Integration Connect installation process.
  2. The Oracle 9i JDBC driver must be available on each machine that will run the hub components. The JDBC driver must be the same level as the Oracle version that is installed.

Record the names and passwords in the tables in "Pre-installation checklist tables". Record the default values also, especially if they were changed.

Pre-installation checklist tables

The following tasks must be performed before you install Business Integration Connect:

Note:
These tasks assume a single machine installation.
  1. User group, bcggroup, exists in the operating system. Operating system user bcguser exists and is a member of bcggroup. If you are using DB2, operating system users bcgcon, bcgdoc & bcgrecv all exist and are members of bcggroup. If you are using Oracle, the O/S users bcgcon, bcgdoc and bcgrecv are not required.
  2. DB2 or Oracle is installed and configured on a server.
  3. WebSphere MQ is installed and configured on a server.
  4. A SMTP server exists.(optional)
  5. If multiple computers are used, you must create network file shares on each computer. This allows all of the computers to access and share the common files across the network.

The following table identifies information that you must have before you start the Database Loader and Business Integration Connect installation wizards. Consult the table as you run the wizards.

Required Information Value

Business Integration Connect user name

(bcguser is the default)

Business Integration Connect user password


Business Integration Connect group name

(bcggroup is the default)

Community Console user name

(bcgcon is the default)

Community Console user password


Community Console port numbers

(HTTP - 58080 is the default)

(HTTPS - 58443 is the default)

Document Manager user name

(bcgdoc is the default)

Document Manager user password


Document Manager port numbers

(HTTP - 56080 is the default)

(HTTPS - 56443 is the default)

Receiver user name

(bcgrecv is the default)

Receiver user password


Receiver port numbers

(HTTP - 57080 is the default)

(HTTPS - 57443 is the default)

WebSphere MQ host name


WebSphere MQ Queue Manager

(bcg.queue.manager is the default)

WebSphere MQ port for Listener

9999

Mount Point for Shared Location


Database host name


Database port

default is (DB2=50000 if using default Instance). (Oracle=1521)

Database owner (DB2)


Owner's password (DB2)


Database name (DB2)


Instance name (DB2)


Administrator login ID (Oracle)


Administrator password (Oracle)


Oracle SID (Oracle)


Schema owner login (Oracle)


Schema owner password (Oracle)


SMTP host name


SMTP Port Number

(25 is the default)

Copyright IBM Corp. 2003, 2004