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.

DISPLAY environment variable

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.

Note:
Test that the DISPLAY system environment variable and X Windows system are properly configured by running an X client program, such as xclock, from the command line. If the xclock client displays on the X Server window (local or remote), then the wizards should also display properly.

LaunchPad

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.

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

To set up the database tables:

  1. Log in as the root administrator.
  2. Database Loader requires administrator privileges to automatically run the SQL create/change ownership of the tablespaces directories.
  3. From the Database Loader directory, run the setup executable, listed in Table 5 specific to your platform:


    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.

  4. 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.
  5. 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. Embedded spaces or special character should not be used in directory names. See Figure 3.

    Select a location with enough space for your database and all the application data that will be stored in it. 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 3. The Directory Name screen


  6. In the Database Type Selection screen, select the database server you plan to use for Business Integration Connect. Click Next. See Figure 4.

    Figure 4. Database Type Selection screen


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

    DB2:

    Figure 5. DB2 Database Information screen


    Oracle:

    Figure 6. Oracle Database Information screen


  8. In the Database Location screen, Figure 7, type the full path for the location of the database and each of its tablespaces on the database server. For example the DB2 database directory path might look like the this: DB2Home/IBM/WBIConnect/DBLoader/tables.
    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.
    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.

    Once you have entered the required information, click Next.

    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:

    Figure 7. DB2 Database Location screen

    Oracle:

    Figure 8. Oracle Database Location screen


  9. In the Component Configuration screen, Figure 9, type the login information for the Business Integration Connect components and the location of the common shared files. Click Next when you are finished.

    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.

  10. 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.
  11. 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.
  12. The wizard displays a screen where you can select whether the Database Loader just creates the SQL files or creates the SQL files and then runs them. See Figure 10.

    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.

  13. Click Finish when the Finish button is enabled.
  14. If you are running the SQL manually, refer to the Instructions.txt file in the SQL directory (installed by the Database Loader installation wizard) for more information.

    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.

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 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.

Note:
If you are installing Business Integration Connect on multiple machines, the shared common folder must use the same mount point 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 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.

Note:
If you are using a Linux platform, follow these steps to prevent memory leaks:
a. Change the max semaphores kernel parameter from 32000 to 256000 on the database server.
b. Upgrade the linux kernel to at least 2.4.9-e.27.

To install Business Integration Connect:

  1. Log in as root.

    The Hub installer requires root/Administrator privilege to integrate with the native software registry.

  2. In the hub directory, run the setup executable, listed in Table 6 specific to your platform.


    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.

  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 11, type the path and name of the directory that the wizard uses when it installs Business Integration Connect. Embedded spaces or special character should not be used in directory names. 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 11. Directory Name screen


  5. In the Component Selection screen, Figure 12, select the components you want to install on the server. You can select multiple components. 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.

  6. In the Database Server Selection screen, Figure 13, 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 13. Database Server Selection screen


  7. The Database information screen appears. If you selected DB2 as your Database server, follow the DB2 specific instructions in this procedure. If you selected Oracle as your Database server, follow the Oracle specific instructions in this procedure.

    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.

    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 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 17. Database connection failure screen

  8. In the User Information screen, enter the user name, password, and group name of the administrator responsible for the installation.
    Note:
    This information must match the information used in the Database Loader installation.
  9. In the Common information directory screen, enter the location of the common information shared by the components. 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.
  10. In the WebSphere MQ Server screen, Figure 18, enter the host name of the computer running WebSphere MQ if it is not installed on this computer. Make sure to change the name of the queue manager if the default name was not used. See Figure 18.

    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.

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

    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.

    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 20 and Figure 21.
    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.

    Figure 20. Receiver Configuration screen


    Figure 21. Document Manager Configuration screen


  13. In the RosettaNet Configuration screen, Figure 22, type the Contact Information for RosettaNet messages. If you do not know the proper values, use the required default values. This information is required if you are using RosettaNet and is recommended for all installations.

    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.

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

    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.

  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.

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

Copyright IBM Corp. 2003, 2004