When you have met all of the prerequisites noted in previous
sections, you are ready to run the Database Loader and WebSphere
Partner Gateway installation wizards.
WebSphere Partner Gateway provides a launch pad program
to provide one-stop access to the Product Overview,
ReadMe file, product documentation, Database Loader, and WebSphere
Partner Gateway Installer. Alternatively, you can start the database
loader and installation programs using the supplied setup*.* programs.
See Creating the database and Installing the components using the install wizard.
Some options on the launch pad require a browser
to be installed and available in the system path.
WebSphere Partner Gateway includes an installation wizard
to set up the database tables. This wizard, Database Loader, gathers
information to create and populate the tables for you. Alternatively,
it can save the SQL files it uses to create the tables so that you
can then use them to manually create and populate the tables. Running
the SQL files manually allows you to review the database tables
before populating them.
Before you begin, verify that your database server is installed,
configured correctly, and running.
The following procedure describes how to configure the database
using the Database Loader GUI. You can also install the Database
Loader without using the GUI.
If you plan to use DB2 as your database server,
you must execute the SQL (either manually or automatically) as the
DB2ADMIN Windows user.
- Log in as DB2ADMIN if you are using DB2 as your database.
- Run the Database Loader CD-MediaDir\DBLoader\setup.exe file
located on the WebSphere Partner Gateway system product CD.
The Database Loader wizard starts and displays the Welcome window.
Click Next.
- In the Software License Agreement window, read the Software
License Agreement. If you agree to the terms in the agreement, select I accept the terms of the license agreement.
Click Next.
-
In the Directory Name window, type the path and directory name of the directory that the Database Loader will use when it sets up the database. IBM recommends that you create a new directory location, or select an empty one.
Select a location with enough space for your database and all
the application data that will be stored in it.
Note:
When browsing to select a directory, enter a "."
in the Enter file name field after selecting
the desired install path. If a "." is not entered, the Select a directory window
will not return to the window from which it was launched.
Click Next.
- In the database type selection window, select the database server
you plan to use for WebSphere Partner Gateway. You can select either
DB2 8.2 or Oracle 9i 9.2.0.4 or later. Click Next.
- In the Database Information window, type the following database
information, then click Next when you are
finished.
DB2
If you selected DB2, the DB2 Database Information window appears.
Enter the following DB2 database information:
- Database name
- Instance name
- Group name
- Owner name
- Owner password
Note:
If any of these values are changed, they must exist
before executing the SQL files. If they do not exist, then they
must be created manually.
Oracle
- If you selected Oracle, the Oracle Database Information window
appears. Enter the following Oracle database information:
- Administrator login ID
- Administrator password
- Oracle SID
- Schema owner login
- Schema owner password
- The Oracle home location window appears. Type in or click Browse to
input the Oracle Home directory location. Figure 19 .
Note:
If any of these values are changed, they must exist
before executing the SQL files. If they do not exist, then they
must be created manually.
Figure 19. Oracle home directory location window
- In the database location window, select a file system location
with sufficient space to hold the database and all application data.
The database size will increase while running WebSphere Partner
Gateway.
DB2
Type the location of the database and each one of its tablespaces
on the RDBMS server. The fields must contain the full path. Click Next.
See Figure 2.
Note:
When browsing to select a directory, enter a "."
in the Enter file name field after selecting
the desired install path. If a "." is not entered, the Select a directory window
will not return to the window from which it was launched.
Figure 20. DB2 database location window
Oracle
Type the location of the database and each one of its tablespaces
on the RDBMS server. The fields must contain the full path. Click Next.
See Figure 21.
Note:
When browsing to select a directory, enter a "."
in the Enter file name field after selecting
the desired install path. If a "." is not entered, the Select a directory window
will not return to the window from which it was launched.
Figure 21. Oracle database location window
- In the Component Configuration window, see Figure 22, type the login information for the WebSphere Partner
Gateway components and the location of the common shared files.
In the User name and Password fields
for the Community Console, Document Manager, and Receiver, type
the name and password of the user for each component. If using DB2,
these users were created when the server was configured.
In the Group Name field, type the name
of the group that contains the WebSphere Partner Gateway users.
Click Next.
Figure 22. Component configuration window
- The system displays the Mount point for shared information window.
Type the location of the common shared files used by the main components
of WebSphere Partner Gateway. Click Next.
Notes:
- If you are installing WebSphere Partner Gateway on multiple
machines, the shared common folder must use the same mount point
and directory structure on all of the machines.
- When browsing to select a directory, enter a "." in the Enter file name field after
selecting the desired install path. If a "." is not entered, the Select a directory window
will not return to the window from which it was launched.
- The wizard displays a window, see Figure 23, where you can select whether the Database Loader
either creates the SQL files only or creates the SQL files and then
runs them for you.
If the Database Loader runs the SQL files, it does the following:
- Creates the tablespaces
- Creates the schema
- Creates the tables, views, sequences, procedures, and functions,
then populates them with metadata
- Assigns permissions to the tables
- Creates the stored procedures
Because the Database Loader restarts the DB2 instance as part
of its routine, disconnect any applications that are using the DB2
instance where you are setting up the WebSphere Partner Gateway
database.
If you want the Database Loader to run the files for you, select
the Run the SQL files check box. Click Next.
Figure 23. Run the SQL files window
- Confirm the Database Loader installation location. Click Next.
- Click the Finish button when it is enabled.
- If you are running the SQL manually, refer to the Instructions.txt file in the bcgdbloader/scripts subdirectory (installed by
the Database Loader) for more information.
When you have set up the WebSphere Partner Gateway database,
you are ready to install the WebSphere Partner Gateway components.
WebSphere Partner Gateway has three main components: Community
Console, Receiver, and Document Manager. All three components share
common content. You can either install the components and common
content on a single server or install each component on a separate
server. You must install one instance of each component on at least
one server. See Environment
planning and Topologies for information
on how to plan the placement of the various components on different
servers.
If you are installing WebSphere Partner Gateway
on multiple machines, the shared common folder must use the same drive letter and directory structure
on all of the machines.
You must also have the WebSphere Partner Gateway database set
up. For information on this, see Creating the database. Finally,
your database server and WebSphere MQ must be running, including
the queue manager and listener.
The following procedure describes how to install the components
using the InstallShield wizard GUI.
You can also install the components using the command
line. See
Installing the components using the command line for
details.
- Log in as a user with Administrator privileges.
Hub installer requires Administrator privilege to properly create
the Windows service.
- Run the CD-MediaDir\hub\setup.exe file located on the WebSphere
Partner Gateway system product CD.
The wizard starts and displays the Welcome window. Click Next.
- In the Software License Agreement window, read the license agreement.
If you agree to its terms, click I accept the terms of the license agreement.
Click Next.
- In the Directory Name window, type the path and directory name of the directory where WebSphere Partner Gateway is installed. IBM recommends that you create a new directory location, or select an empty one. Click Next.
Note:
When browsing to select a directory, enter a "."
in the Enter file name field after selecting
the desired install path. If a "." is not entered, the Select a directory window
will not return to the window from which it was launched.
- In the component selection window, Figure 24, select the components you want to install on the
server. You can select multiple components. Click Next.
Figure 24. Component selection window
The rest of this procedure assumes that you are installing all
of the components. If you are not installing all of them, some of
the windows described in the rest of this procedure will not appear.
- Specify the fully qualified host name for the machine that you
are installing on. Click Next.
- Select one of the following WebSphere Application Servers that
will be used to host WebSphere Partner Gateway and click Next.
See Figure 7.
- In the database server selection window, Figure 26, select the database server that you plan to use.
You can select either DB2 8.2 or later or Oracle 9i.9.2.0.4 or later.
Click Next.
Figure 26. Database selection window
- The Database Information window appears. If you selected DB2
as your database, follow the DB2 specific instructions in this procedure.
If you selected Oracle as your database, follow the Oracle specific
instructions in this procedure.
DB2
If you selected DB2, the DB2 database information window appears.
See Figure 27.
In the Host name field, if DB2 is not on
the current system, replace localhost with the name of the system containing DB2.
In the Port field, type the port that the
DB2 instance is using. To find out which port the DB2 instance is
using, either use the DB2 Control Center (GUI) to determine the
properties, or enter the following on a command line: db2 get dbm cfg. This information (DB2 configuration) is also saved by the
Database Loader in the "system temp"/bcgdbloader/logs directory.
The default port is 50000.
In the Owner name, Owner password, Database name,
and Schema name text fields, enter the requested
information. These are the names that were used in the Database
Loader installation to define the database. See Creating the database.
Click Next.
Figure 27. DB2 information window
Oracle
If you selected Oracle, the Oracle database information window
appears.Figure 28.
Enter the required information about the Oracle database. The
default port is 1521.
Note:
The full path and name of the JDBC driver must point
to the correct version of the driver on this computer. The driver
can be found in the Oracle installed directory tree. It can also
be downloaded from the following website: http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/
index.html. In the section "JDBC Driver Downloads" click
on Oracle xx Release x drivers.
Be sure to select the driver version that matches the Oracle version
that you are running.
Note:
When browsing to select a directory, enter a "."
in the Enter file name field after selecting
the desired install path. If a "." is not entered, the Select a directory window
will not return to the window from which it was launched.
Figure 28. Oracle information window
The Database connection confirmation window will appear. See Figure 29. If your connection is successful,
note and confirm the Table, View, Function, and Procedure count
information. If the connection fails, review the information window
for guidance, or refer to your database documentation to address
the error code.
Figure 29. Database connection confirmation window
- In the Common information directory window, type the location
of the common shared components. This value must match the directory
location used in the Database Loader installation.
Note:
When browsing to select a directory, enter a "."
in the Enter file name field after selecting
the desired install path. If a "." is not entered, the Select a directory window
will not return to the window from which it was launched.
- In the WebSphere MQ server window, type the required information
about your WebSphere MQ server. See Figure 30.
In the Host name field, if WebSphere MQ
is not on the current machine, replace localhost with the name of the system containing WebSphere MQ.
In the Queue Manager field, replace the
default name with the name that was used when configuring WebSphere
MQ (see Configuring WebSphere MQ.)
In the Listener port field, type the port
that the listener is using (see Configuring WebSphere MQ.) The default port is 9999.
Click Next.
Figure 30. WebSphere MQ server window
- The Windows Service Installation window appears. If you would
like to register WebSphere Partner Gateway feature as a Windows
service, select the Install as Windows Service check
box. See Figure 31.
Click Next.
Figure 31. Windows service installation window
- If you selected to install the Community Console, configure
it using the Community Console configuration window. See Figure 32.
In the User name field, type the user ID
that the Community Console component uses to log into the database.
In the Password field, type the password
associated with the user name. Make sure that you enter the correct
password, because the Community Console will not function with an
incorrect password.
In the HTTP Port field, type the number
of the port on which the component listens for messages. The Community
Console, Receiver, and Document Manager must have unique port numbers,
and they must be available on this computer. The default port is 58080.
In the HTTPS Port field, enter the number
of the secure port on which the component listens for messages.
The Community Console, Receiver, and Document Manager must have
unique port numbers, and they must be available on this computer.
The default port is 58443.
In the Help System host name field, enter
the server address that the Help System will reside on.
In the Help System port number field, enter
the port number for access to the Help System.
Click Next.
Note:
If the database connection fails, the database information
window will appear. Review the information window for guidance,
or refer to your database documentation to address the error code.
Figure 32. Community Console window
- If you selected the Receiver or Document Manager components,
configure them using their configuration windows. These windows
have the same fields as the Community Console Configuration window.
All three components (Community Console, Receiver, and Document
Manager) must have different HTTP and HTTPS ports. See Figure 33 and Figure 34.
Note:
If you are installing the Receiver and Document
Manager on different machines, the Receiver machine must have a
host name that can be resolved by the Document Manager machine.
Click Next when you are finished.
Figure 33. Receiver configuration window
Figure 34. Document Manager configuration window
- In the RosettaNet configuration window, Figure 35, type the contact information for RosettaNet messages.
Values are required in these text fields. Use the default values
if you do not know the proper values. This information is required
if you are using RosettaNet and is recommended for all installations.
In the Name field, type the name of the
person that should be contacted for RosettaNet problems.
In the Phone number and Fax number fields,
type the telephone and fax numbers of the RosettaNet contact person.
In the e-mail address field, type the RosettaNet
contact's e-mail address.
Click Next.
Figure 35. RosettaNet configuration window
- In the alert notification window, Figure 36, configure WebSphere Partner Gateway so that it can
send alerts by e-mail. Values are required. Use the default values
if you do not know the proper values.
In the SMTP relay field, type the location
of the SMTP server.
In the From e-mail address field, type
the e-mail address that WebSphere Partner Gateway uses to send e-mails.
In the To e-mail address field, type the
destination e-mail address that users responding to alert notifications
use when they send a response e-mail.
Click Next.
Figure 36. Alert notification window
- In the Summary window, review the information, which identifies
the components that will be installed. If any of this information
is incorrect, click Back to return to previous
windows. When all of the information on the summary window is correct,
click Next.
- The WebSphere Partner Gateway Installer installs and configures
the selected components. When it has completed this task, the installer
enables the Finish button. Click Finish.
- Verify that the following values are set:
DB2:
- Open the console\lib\config\bcg_console.properties file. Verify
that the following value is set: bcg.co.db.schema=DB2ADMIN.
- Open the receiver\lib\config\bcg_receiver.properties file. Verify
that the following value is set: bcg.co.db.schema=DB2ADMIN.
- Open the router\lib\config\bcg.properties file. Verify that
the following value is set: bcg.co.db.schema=DB2ADMIN.
Oracle:
- Open the console\lib\config\bcg_console.properties file. Verify
that the following value is set: bcg.co.db.schema=BCGAPPS.
- Open the receiver\lib\config\bcg_receiver.properties file. Verify
that the following value is set: bcg.co.db.schema=BCGAPPS.
- Open the router\lib\config\bcg.properties file. Verify that
the following value is set: bcg.co.db.schema=BCGAPPS.
- Repeat this procedure on each server where you want to install
WebSphere Partner Gateway components. The common content needs to
be installed only once because it is available to all computers
via the shared file system.
When you have installed all WebSphere Partner Gateway components,
see Installing the components using the command line.