Installation steps in Installation Manager

Use IBM Installation Manager to install product components on most platforms.

Before you begin

You must have started Installation Manager and selected the Build Forge package to install to follow these instructions.

About this task

Follow the prompts to install the desired packages:

Procedure

  1. Install Packages – Select the Build Forge and Version check boxes. If Installation Manager is not already installed, select the Installation Manager check box. Click Next after you make the selections.
  2. Install Packages: Location - Shared Resources – Enter or choose the directory where you want shared resources installed, and then click Next.
  3. Install Packages: Location - Package Group – Choose the directory where you want the installation packages installed, and then click Next. The default location is: C:\Program Files\IBM\Build Forge.
  4. Install Packages: Features – By default all three core product modules are installed: Web Interface, Process Engine, and Services Layer. Click Next.
  5. Install Packages: License Server Configuration – Select the "Run as" user and the type of license the console will use. Fill in the following information, then click Next.
    • (UNIX and Linux) At Which user should Build Forge run as?, accept the default user (root) or specify a different user. This user will start the Build Forge engine and the supplied Apache Tomcat. The user must have read and execute permissions for the database libraries and the JDBC jar files specified in the Database Configuration page in Installation Manager.
    • Rational License Server Based: Enter the host name of the Rational License Server.
      • Enter a valid host name for the license server. If you plan to provide the host name later, do not leave this field blank. Enter a character or value in this field. Leaving this field blank might result in an incomplete and unusable product.

        After installation is complete, provided the correct host name. For instructions, see Configuring a Rational license server for Build Forge.

      • If a license server is displayed but greyed out, your FLEXlm license client has already registered a license server for the host.

        After installation is complete, provide the correct host name. For instructions, see Changing the license server for the Management Console.

    • File Based: browse to the location where you downloaded the license file.
  6. Database Configuration
    Depending on the OS platform you are installing Build Forge on and the database you want to install, you must specify certain information. Refer to database setup instructions in Database setup for the following:
    • For DB2 Express, seeDB2 Express setup.
    • For DB2, see DB2 setup.
    • For Microsoft SQL Server, see Microsoft SQL Server setup. Note that the JDBC driver to specify depends on the version you choose (SQL Server 2005 or SQL Server 2008).
    • For MySQL, see MySQL setup.
    • For Oracle, see Oracle setup. Note that you must choose the version that corresponds to the Oracle Instant Client version you installed (Oracle 10 or Oracle 11).
    Note: On UNIX and Linux platforms, you must install and use 32-bit database client drivers if you are using an Oracle, DB2, or MySQL database. On the Database Configuration page in Installation Manager, for your specific database type, make sure that you specify the 32-bit version of driver libraries in the Path to the [DB2|Oracle|MySQL] client libraries field on the Database Configuration page. Also, for DB2, load the db2profile.
  7. Install Packages: Application and Web Server Configuration – Fill in the requested information, and then click Next.
    1. Web Server/PHP Configuration
      • Supply your own webserver? Select Yes if you want to supply your own web server. No is the default.
      • Do you wish to use Secure HTTP? Select Yes if you want to use Secure HTTP. No is the default.
      • Which port should the web server use? If you do not want the web server to use port 80, enter a different port number. 80 is the default.
      • Memory Limit for PHP: Enter a memory limit for PHP if you do not want to use the default. 256 MB is the default.
    2. Application Server Configuration
      • Supply your own application server? Select Yes if you want to configure Build Forge to use an application server that you have already installed. No is the default.
        Note: You do this only if you are configuring Build Forge to use one or more components that you have already installed. Normally Build Forge installs these components during installation. See Installing using your own components.

    3. Security Configuration Enter and verify a password for the keystore that the installer creates for Build Forge in the following fields.
      Note: If these fields are not visible, scroll down to find them.
      • Keystore Password
      • Verify Password
      The password is required to enable the default secure login (credential encryption). It is also required if you intend to configure Build Forge to use HTTPS/SSL.
      Important: Changing the password later is possible but a fairly long process. Use a strong password that meets your local requirements for complexity.

      You have the following options:

      • Use the self-signed certificate that the installer creates as is. Do the following:
        1. Do you wish to modify default or upload a custom certificate? Select No.
        2. Do you have an existing secure certificate? Select No.
      • Use the self-signed certificate that the installer creates, but modify its fields. Do the following:
        1. Do you wish to modify default or upload a custom certificate? Select Yes. Additional fields for the certificate are displayed. Fill them in.
        2. Do you have an existing secure certificate? Select No.
      • Provide the location of your own certificate. The certificate must be on the host, it must be in pkcs12 format, and you must provide the existing password for the keystore it is in. Do the following:
        1. Do you wish to modify default or upload a custom certificate? Select Yes.
        2. Do you have an existing secure certificate? Select Yes. Additional fields are displayed.
        3. Please specify a signed certificate in a keystore of type pkcs12. Enter the filename or use Browse to locate it.
        4. Keystore Password Enter the password for the keystore containing your certificate.
        5. Verify Password Re-enter the password for the keystore containing your certificate.
      Note: Browsers typically warn about accessing a secure site that has a self-signed certificate. Users are typically given the option to proceed, but may be required to confirm the exception.
  8. Services Configuration Fill in the requested information, then click Next.
    • Will services layer run on this machine? Click No if you do not want the services layer to run on this machine. Yes is the default.

      If you click No, you are prompted for the host name of the application server that runs the services layer application.

    • Listen on port: 3966 is the default. One or both ports must be selected as the services port.
    • Listen on secure port: 49150 is the default. One or both ports must be selected as the services port.
  9. Install Packages: Console Start Options – fill in the requested information, and then click Next.

      • Create a shortcut on the desktop? The default is create a shortcut on the desktop (for Windows).
        Note: On Linux, a desktop shortcut is not created.
    1. Startup Options
      • Do not start the Console: The Console starts by default. Click the radio button if you do not want to the Console to start automatically.
      • Start the Console in Service Mode: The Console starts in service mode by default.
      • Start the Console in Foreground Mode: The Console does not start in foreground mode, by default. If you want the Console to start in foreground mode, click the radio button.
  10. Install Packages: Summary review – Review the summary information on this page to confirm where the Build Forge components will be installed, and then click Install.
    1. Target Location
      • Package Group Name: buildforge.console is the default package name.
      • Installation Directory: The default installation directory is C:\Program Files\IBM\Build Forge.
      • Shared Resources Directory: The default shared resources directory. The defaults are as follows:
        • Windows: C:\Program Files\IBM\SDP70Shared
        • UNIX and Linux: /opt/IBM/SDP70Shared
    2. Features
      • Build Forge Features You can review what features or modules will be installed. For example, the core product modules are: Web Interface, Process Engine, and Services Layer.
    3. Environment
      • English is the default environment.
    4. Repository Information
      • Files will be retrieved from the following locations: Use this section to review and confirm the repository location.
  11. Access the Management Console. Start a browser. Go to the URL for the Management Console:
    • General form: http://<hostname>[:<portnumber>]. The port number is optional if you used the HTTP default, port 80.
    • Local: if you are running the browser on the same host where the Management Console is running, you can use http://localhost.
    Note: If you cannot log in immediately after installation, wait a minute or so and try again. On first startup the engine (bfengine) has to load the database schema.
    Important: Do not stop bfengine immediately after an install. Doing so can corrupt the database schema. In that case you would need to drop all Build Forge tables from the database and reinstall Build Forge.
  12. Log in. Use user name root, password root. Change the root password immediately.

Feedback