When you have met all of the prerequisites noted in previous sections, you are ready to run the Database Loader and WebSphere Business Integration Connect installation wizards.
The Database Loader and Hub install wizards use the X Windows system on UNIX to display the graphical user interface. The X Windows system requires that the DISPLAY environment variable be exported to the system environment. The following lines set the DISPLAY environment variable to the IP_Address from a Bourne shell:
DISPLAY=IP_Address:0.0
export DISPLAY
Use the syntax appropriate to your shell to set the DISPLAY environment variable.
Business Integration Connect provides a launch pad program, see Figure 2, to provide one-stop access to the Product Overview, ReadMe File, product documentation, database loader, and Business Integration Connect 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.
The launch pad executable file is located in:
{CD_ROM/MEDIA DIR}/LaunchPad.*
Business Integration Connect 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. You can then use the SQL files to create and populate the tables. Running the SQL files manually allows the database administrator 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. See "Installing the components using the command line" for information.
To set up the database tables:
cd DBLoader
Table 5. Platform-specific executables for Installer
Platform | Executable |
---|---|
Linux
|
setupLinux
|
AIX
|
setupAIX
|
Solaris
|
setupSunOS
|
The Database Loader wizard starts and displays the Welcome screen. Click Next.
Select a location with enough space for your database and all the application data that will be stored in it. Click Next.
DB2:
Figure 5. DB2 Database Information screen
Oracle:
Once you have entered the required information, click Next.
DB2:
Figure 7. DB2 Database Location screen
Oracle:
Figure 9. Component Configuration screen
In the User name and Password text boxes for the Community Console, Document Manager and Receiver, type the name and password of the user for each component. These users were created when the server was configured.
In the Group Name text box, type the name of the group that contains the Business Integration Connect users.
The system displays the Mount point for shared information screen.
Figure 10. Run the SQL Files screen
When the Database Loader runs the SQL files, it does the following:
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 Business Integration Connect database.
If you want the Database Loader to run the files for you, check the Run the SQL files check box.
Click Next when you are finished.
When you have set up the Business Integration Connect database, you are ready to install the Business Integration Connect components.
The following section describes how to install the components using the InstallShield wizard GUI. You can also install the components without using the GUI. See "Installing the components using the command line" for information.
Business Integration Connect has three main components: Community Console, Receiver, and Document Manager. All three components share common content. You can install the components and common content on a single server, install each component on a separate server, or use a combination of these two options. 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.
Before you begin, make sure that the prerequisite software is installed and configured properly. Consult the Requirements for all Business Integration Connect servers table in Platform, hardware, and software requirements for software prerequisites and Installation overview for information on how to configure that software. You must also have the Business Integration Connect 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.
Common components need to be installed only once when using anything other than the consolidated topology.
To install Business Integration Connect:
The Hub installer requires root/Administrator privilege to integrate with the native software registry.
cd hub
Table 6. Platform-specific executables for Installer
Platform | Executable |
---|---|
Linux
|
setupLinux
|
AIX
|
setupAIX
|
Solaris
|
setupSolaris
|
The wizard starts and displays the Welcome screen. Click Next.
Figure 12. Component Selection screen
The rest of this procedure assumes that you are installing all of the components on this server. If you are not installing all of them, some of the screens described in the rest of this procedure will not appear.
DB2:
If you selected DB2, the DB2 Database Information screen appears. See Figure 14.
Enter the host name of the computer running DB2 if it is not installed on the current system by replacing localhost with the name of the system containing DB2.
In the Port text field, type the port number 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 type the following DB2 configuration command into a command prompt: db2 get dbm cfg. This DB2 configuration information is also saved by the Database Loader in the system temp/WBIConnect/logs directory. The default port is 50000.
In the User name, Password, Database name, and Instance name text fields, type the owner name, owner's password, database name and the instance name respectively. These are the names used in the Database Loader installation to define the database. See "Creating the database".
Click Next.
Figure 14. DB2 Database Information screen
Oracle:
If you selected Oracle, the Database information screen appears. See Figure 15.
Enter the required information about the Oracle database. The default port is 1521.
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 9i installation directory. It can be downloaded from http://otn.oracle.com/software/tech/java/sqlj-jdbc/index.html. In the section JDBC Driver Downloads, click on Oracle 9i Release 2 drivers. Be sure to select the driver version that matches the Oracle 9i (9.2.0) service version that you are running.
Figure 15. Oracle Database Information screen
The Database Connection Confirmation screen will appear. See Figure 16. If your connection is successful, note and confirm
the Table, View, Function, and Procedure count information. If the
connection fails, review the information screen for guidance or refer to your
database documentation to address the error code. See Figure 17.
Figure 16. Database connection confirmation screen
Figure 18. WebSphere MQ Server screen
In the Host name text box, if WebSphere MQ is not on the current machine, replace localhost with the name of the system containing WebSphere MQ.
In the Queue Manager text box, replace the default name with the name that was used when configuring WebSphere MQ (See 2 in "Configuring WebSphere MQ").
In the Listener Port text box, type the port that the listener is using (see "Configuring WebSphere MQ"). The default port is 9999.
Click Next.
Figure 19. Community Console Configuration screen
In the User name text box, type the user ID that the Community Console component uses to log in to the database.
In the Password text box, 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 text box, type the name 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 text box, enter the name 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.
Click Next.
Figure 20. Receiver Configuration screen
Figure 22. RosettaNet Configuration screen
In the Name text box, type the name of the person that should be contacted for RosettaNet problems.
In the Phone number and Fax number text boxes, type the telephone and fax numbers for the RosettaNet contact.
In the E-mail address text box, type the e-mail address for the RosettaNet contact person.
Click Next.
Figure 23. Alert Notification screen
In the SMTP relay text box, type the host name of the SMTP if it is not running on this computer.
In the From e-mail address text box, type the e-mail address Business Integration Connect uses to send e-mails.
In the To e-mail address text box, type the destination e-mail address that users responding to Alert Notifications use when they send a response e-mail.
Click Next.
Repeat this procedure on each server where you want to install Business Integration Connect 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 Business Integration Connect components, see "Starting Business Integration Connect".