Installing Business Integration Connect

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.

LaunchPad

Business Integration Connect provides a launch pad program, see Figure 24, 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.

Note:
Some options on the launch pad require a browser to be installed and available in the system path.

The launch pad executable file is located in:

{CD_ROM/MEDIA DIR}/LaunchPad.*



Figure 24. Launch pad screen

Creating the database

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.

Note:
If the SQL will be run automatically, the Database Loader must be run on the same server that the database resides on. This ensures that the correct host address is set for the database.

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.

Note:
If you plan to use DB2 as your database server, you must execute the SQL (either manually or automatically) as the DB2ADMIN Windows user.

To set up the database tables:

  1. Log in as DB2ADMIN if you are using DB2 as your database.
  2. Run the Database Loader CD-MediaDir\DBLoader\setup.exe file located on the WebSphere Business Integration Connect system product CD.

    The Database Loader wizard starts and displays the Welcome screen. Click Next.

  3. In the Software License Agreement screen, 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.
  4. In the Directory Name screen, type the path and directory name of the directory that the Database Loader will use when it sets up the database. See Figure 25.

    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 screen will not return to the screen from which it was launched.

    Click Next.

    Figure 25. Directory Name screen


  5. Select either DB2 or Oracle in the Database Selection screen and click Next. See Figure 26.

    Figure 26. Database Type Selection screen


  6. In the Database Information screen, type the following database information, then click Next when you are finished.

    DB2:

    If you selected DB2, the DB2 Database Information screen appears. Enter the following DB2 database information:

    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 screen appears. Enter the following Oracle database information:

    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.
  7. The Database Location screen appears.
    Note:
    Select a file system location with sufficient space to hold the database and all application data. The database size will increase while running Business Integration Connect.

    DB2:

    In the Database Location screen, Figure 27, type the location of the database and each one of its tablespaces on the RDBMS server. The text boxes must contain the full path. 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 screen will not return to the screen from which it was launched.



    Figure 27. DB2 Database Location screen

    Oracle:

    In the Database Location screen, Figure 28, type the location of the database and each one of its tablespaces on the RDBMS server. The text boxes must contain the full path. 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 screen will not return to the screen from which it was launched.

    Figure 28. Oracle Database Location screen


  8. In the Component Configuration screen, Figure 29, type the login information for the Business Integration Connect components and the location of the common shared files.

    Figure 29. 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 that 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.

    Click Next.

    The system displays the Mount point for shared information screen.

  9. Type the location of the common shared files used by the main components of Business Integration Connect.
    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 screen will not return to the screen from which it was launched.
  10. The system displays the Summary screen. Review the information on the Summary screen, which identifies where the Database Loader will be installed. If this location is incorrect, click Back to return to previous screens. When the information on the summary screen is correct, click Next.
  11. The wizard displays a screen, Figure 30, 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. The default behavior is to just create the SQL files.

    Figure 30. Run the SQL Files screen


    If 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, select the Run the SQL files check box.

    Click Next.

  12. When the Database Loader enables the Finish button, click it.
  13. If you are running the SQL manually, refer to the Instructions.txt file in the SQL directory (installed by the Database Loader) for more information.

    When you have set up the Business Integration Connect database, you are ready to install the Business Integration Connect components.

Installing the components using the install wizard

Business Integration Connect 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.

Note:
If you are installing Business Integration Connect on multiple machines, the shared common folder must use the same drive letter and directory structure on all of the machines.

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 Verifying and configuring installed prerequisites 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.

The following procedure describes how to install the components using the InstallShield wizard GUI.

Note:
You can also install the components using the command line. See Installing the components using the command line for details.

To install Business Integration Connect follow the steps below:

  1. Log in as a user with Administrator privileges.

    Hub installer requires Administrator privilege to properly create the Windows service.

  2. Run the CD-MediaDir\hub\setup.exe file located on the WebSphere Business Integration Connect system product CD.

    The wizard starts and displays the Welcome screen. Click Next.

  3. In the Software License Agreement screen, read the license agreement. If you agree to its terms, click I accept the terms of the license agreement. Click Next.
  4. In the Directory Name screen, Figure 31, type the path and directory name of the directory where Business Integration Connect is installed. 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 screen will not return to the screen from which it was launched.

    Figure 31. Directory Name screen


  5. In the Component Selection screen, Figure 32, select the components you want to install on the server. You can select multiple components. Click Next.

    Figure 32. Component Selection screen


    The rest of this procedure assumes that you are installing all of the components on the server. If you are not installing all of them, some of the screens described in the rest of this procedure will not appear.

  6. In the Database Server Selection screen, Figure 33, select the database server that you plan to use. You can select either DB2 8.1.2 or later or Oracle 9i.9.2.0 or later. Click Next.

    Figure 33. Database Server Selection screen


  7. The Database Information screen 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 screen appears. See Figure 34.

    Figure 34. DB2 Database Information screen


    Enter the requested information about the DB2 database.

    In the Host name text field, if DB2 is not on the current system, replace localhost with the name of the system containing DB2.

    In the Port text 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 type 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"/WBIConnect/logs directory. The default port is 50000.

    The path for DB2 is:

    C:\Documents and Settings\db2admin\Local Settings\Temp\WBIConnect\logs

    The path for Oracle is:

    C:\Documents and Settings\Administrator\Local Settings\Temp\WBIConnect\logs

    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.

    Oracle:

    If you selected Oracle, the Oracle Database information screen appears. See Figure 35.

    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 9i installed directory tree. 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.
    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 screen will not return to the screen from which it was launched.

    Figure 35. Oracle Database Information screen


    The Database Connection Confirmation screen will appear. See Figure 36. 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.

    Figure 36. Database confirmation screen

  8. In the Common information directory screen, 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 screen will not return to the screen from which it was launched.
  9. In the WebSphere MQ Server screen, type information about your WebSphere MQ server. See Figure 37.

    Figure 37. 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 "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.

  10. The Windows Service Installation screen appears. If you would like to register Business Integration Connect features as a Windows service, select the Install as Windows Service check box. See Figure 38.

    Click Next.

    Figure 38. Windows Service Installation screen


  11. If you selected to install the Community Console, configure it using the Community Console configuration screen. See Figure 39.

    Figure 39. Community Console screen


    In the User name text box, type the user ID that the Community Console component uses to log into 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 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 text box, 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.

    Click Next.

    Note:
    If the database connection fails, the database information screen will appear. Review the information screen for guidance or refer to your database documentation to address the error code.
  12. If you selected the Receiver or Document Manager components, configure them using their configuration screens. These screens have the same fields as the Community Console Configuration screen. All three components (Community Console, Receiver, and Document Manager) must have different HTTP and HTTPS ports. See Figure 40 and Figure 41.
    Note:
    If you are installing the Receiver and Document Manager on different machines, the Receiver machine must have a host name that is resolvable by the Document Manager machine.

    Click Next when you are finished.

    Figure 40. Receiver Configuration screen


    Figure 41. Document Manager Configuration screen


  13. In the RosettaNet Configuration screen, Figure 42, 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.

    Figure 42. 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 of the RosettaNet contact person.

    In the E-mail address text box, type the RosettaNet contacts' e-mail address.

    Click Next.

  14. In the Alert Notification screen, Figure 43, configure Business Integration Connect so that it can send alerts by e-mail. Values are required. Use the default values if you do not know the proper values

    Figure 43. Alert Notification screen


    In the SMTP relay text box, type the location of the SMTP server.

    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.

  15. In the Summary screen, review the information, which identifies the components that will be installed. If any of this information is incorrect, click Back to return to previous screens. When all of the information on the summary screen is correct, click Next.
  16. The Business Integration Connect Installer installs and configures the selected components. When it has completed this task, the installer enables the Finish button. Click Finish.
  17. Open console\was\wbic\config\bcg_console.properties. Verify that the following value is set: bcg.co.db.schema=DB2ADMIN.
  18. Open receiver\was\wbic\config\bcg_receiver.properties. Verify that the following value is set: bcg.co.db.schema=DB2ADMIN.
  19. Open router\was\wbic\config\bcg.properties. Verify that the following value is set: bcg.co.db.schema=DB2ADMIN.

    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 "Installing the components using the command line".

Copyright IBM Corp. 2003, 2004