Verifying and configuring installed prerequisites

Before you install WebSphere Partner Gateway, 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 WebSphere Partner Gateway software.

A pre-installation checklist (Table 11) is included at the end of this section to help you prepare for the installation. This checklist lists the tasks that must be performed before you install WebSphere Partner Gateway. You can also use it when planning your installation to:

This section contains the following topics:

Adding user accounts

In order to connect with the database, WebSphere Partner Gateway 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 plan to have only 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 the following 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 WebSphere Partner Gateway 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 window.
  7. Record the user names and passwords in the table in Pre-installation checklist.

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 wherever 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 by entering the following:
    crtmqm -q bcg.queue.manager

    IBM recommends changing the following default log parameters to avoid potential Process Transaction Rollback errors. Refer to the WebSphere MQ documentation for specific information on these attributes. These attributes can be viewed from the Log tab of the queue manager's Properties window in MQ Services.

  3. Update the channel parameters:
    1. From MQServices, right click your queue manager, select Properties, and select the Channels tab.
    2. 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 and 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\BCGCreate_Queues.mqsc file to define the queues and channels for the queue manager:
    runmqsc bcg.queue.manager <
     <CD image>\Tools\MQSeries\BCGCreate_Queues.mqsc

    Where <CD image> is the location of the WebSphere Partner Gateway CD or the location of the unarchived WebSphere Partner Gateway 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 the Pre-installation checklist.

Installing and configuring DB2

For maximum performance in a production environment, the WebSphere Partner Gateway database should reside on a dedicated server.

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. You should review the database configuration with your database administrator and modify it if necessary to conform to your specific database environment.

Note:
WebSphere Partner Gateway does not use the fenced-user option. Do not use the fenced-user ID as part of the WebSphere Partner Gateway 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:
    Note:
    You can also use an existing installation.
  2. If DB2 is not running, start it by entering the following command:

    db2start

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

Installing and configuring Oracle

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

WebSphere Partner Gateway is a Unicode application. Please ensure that the database character set and the national character set for your database are set to Unicode.

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

  1. Export Oracle system environment variables (including: ORACLE_HOME, ORACLE_SID, and ORACLE_BASE), 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 WebSphere Partner Gateway installation process.
  2. The Oracle 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 Pre-installation checklist in the next section. Record the default values also, especially if they were changed.

Pre-installation checklist

The following tasks must be performed before you install WebSphere Partner Gateway:

Note:
These tasks assume a single machine installation.

  1. Ensure that the bcggroup user group exists in the operating system. Also ensure that bcguser user exists and is a member of bcggroup. If you are using DB2, operating system users bcgcon, bcgdoc, and bcgrecv must all exist as members of bcggroup. If you are using Oracle, the operating system 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. An SMTP server exists. (This is 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.

Table 11 identifies information that you must have before you start the Database Loader and WebSphere Partner Gateway installation wizards. Consult the table as you run the wizards.

Table 11. Required information checklist
Required Information Value

WebSphere Partner Gateway user name

(bcguser is the default)

WebSphere Partner Gateway user password

WebSphere Partner Gateway 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)

Help System

(58888 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

DB2=50000 is the default if using the default Instance.
Oracle=1521 is the default.

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, 2005