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.
- Table 1 lists the values that you must enter when you run the Database
Loader installation wizard. When you are planning your installation,
you can record required installation information in this table. For
example, the database instance name and tablespace information.
- Table 2 lists the values that you must enter when you run the Business
Integration Connect installation wizard. As you plan your installation,
you can record required installation information such as the host name of the
WebSphere MQ server and port numbers for the Community Console, Receiver, and
Document Manager.
This section contains the following topics:
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:
- 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.
- Business Integration uses a user in this group to manage Business
Integration Connect components.
- From the Users and Groups dialog box, right click Groups and
select New Group.
- The New Group dialog box appears. Add the group bcggroup.
- Add the following users to bcggroup: bcguser, bcgcon, bcgdoc and
bcgrecv.
- Note:
- Oracle users are only required to add bcguser user to bcggroup.
- Exit the computer management.
- Record the user names and passwords in the tables in "Pre-installation checklist tables".
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:
- Confirm that you are logged into your operating system as an administrator
or a user that is a member of the administrator's group.
- Create the queue manager:
crtmqm -q bcg.queue.manager
- 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
- If the computer has more than one CPU, enter the following command:
setmqcap <number of CPUs>
- Start the queue manager with the following command:
strmqm bcg.queue.manager
- Start the listener with the following command:
runmqlsr -t tcp -p 9999 -m bcg.queue.manager
- The listener runs in this window, so leave it open.
- Open a new window and start the JMS Broker (the publish-subscribe broker)
with the following command:
strmqbrk -m bcg.queue.manager
- Start the MQ command services with the following command:
strmqcsv bcg.queue.manager
- 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.
- 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
- Record the MQ host name, queue manager name, and listener port in "Pre-installation checklist tables".
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:
- Install DB2 by following the installation instructions provided and using
the DB2 Setup wizard. In the wizard, do the following:
- When you come to the screen in which you select the type of installation,
select a Custom install. In the following screen, add
Application Development Toolkit to the default selections.
- For the remaining screens, use the default values or your own
values. Note the instance name, instance owner userid, and password,
and record them in the Information required by the Database Loader
Installation wizard table later in this section. For information
on these options, see the installation guide for DB2.
- When you have completed the DB2 installation, install the FixPack2 using
the instructions in the FixPackReadme.txt.
- If DB2 is not running, start it by running the following command:
db2start
- 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:
- Verify that the DB2 Application Development Toolkit is installed.
For information on how to install the toolkit, see the DB2
documentation.
- Verify that the include directory exists. For example
DB2HomeInstallDir\IBM\SQLLIB\include
- 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".
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:
- 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.
- 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.
The following tasks must be performed before you install Business
Integration Connect:
- Note:
- These tasks assume a single machine installation.
- 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.
- DB2 or Oracle is installed and configured on a server.
- WebSphere MQ is installed and configured on a server.
- A SMTP server exists.(optional)
- 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)
|
