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.
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 WebSphere Partner Gateway.
This section contains the following topics:
In order to operate securely, 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. Note that if you use your own group and user names, they cannot exceed eight characters.
If you are installing WebSphere Partner Gateway on multiple machines, the group's ID (GID) and the user's ID (UID) on each machine must match the group GIDs and user UIDs on all of the other machines.
The following procedure assumes that all WebSphere Partner Gateway features and components are being installed on one machine.
To create user accounts:
Business Integration uses a user in this group to manage WebSphere Partner Gateway components.
WebSphere Partner Gateway uses this user to manage WebSphere Partner Gateway components. The installation wizard installs and runs software as this user. This is a normal user, not a super user. For example, create bcguser.
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.
To configure WebSphere MQ:
su - mqm
crtmqm -q bcg.queue.manager
IBM recommends changing the following default log parameters, located in <MQInstallDir>/qmgrs/<qmgr>/qm.ini, to avoid potential Process Transaction Rollback errors. Refer to the WebSphere MQ documentation for specific information on these attributes.
Channels: MaxChannels=1000 MaxActiveChannels=1000
Enter an empty line below MaxActiveChannels=1000 and save the changes to the configuration file.
setmqcap <number of CPUs>
strmqm bcg.queue.manager
runmqlsr -t tcp -p 9999 -m bcg.queue.manager &
strmqbrk -m bcg.queue.manager
strmqcsv bcg.queue.manager
runmqsc bcg.queue.manager < <CD image>/Tools/MQSeries/BCGCreate_Queues.mqsc
Where <CD image> is the mount location of the WebSphere Partner Gateway installation CD or the location of the uninstalled WebSphere Partner Gateway installation files.
runmqsc bcg.queue.manager < <MQHomeInstallDir>/mqm/Java/bin/MQJMS_PSQ.mqsc
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.
Use the following procedure to install and configure DB2:
db2start
For quick reference, record the names and passwords in the tables in Pre-installation checklist tables. Record the default values also, especially if the default values were changed.
This guide does not provide installation instructions for Oracle. For procedures on how to install Oracle, see the appropriate Oracle documentation.
IBM recommends that you follow the guidelines in this section during your Oracle installation:
Record the names and passwords in the tables in Pre-installation checklist tables. Record default values also, especially if the default values were changed.
The following checklist items must be performed before you install WebSphere Partner Gateway:
Table 8 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.
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) |
Help System |
(58888 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) |