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
- Install Packages – Select the Build
Forge and Version check boxes. If Installation
Manager is not already installed, select the Installation
Manager check box. After you make the selections, click Next.
- License agreement page – Indicate that you accept
the license agreement, and click Next.
- Install Packages: Location - Package Group – Choose
the directory where you want the installation packages installed,
and click Next. The default locations
are listed below.
- Windows: C:\Program Files\IBM\Build Forge
- Linux and AIX: /opt/buildforge
- Solaris: /opt/buildforge_0
- Install Packages: Features – By default
all three core product modules are installed: Web Interface, Process
Engine, and Services Layer. Click Next.
- Install Packages: License Server Configuration – Select the Run as user and the type
of license the console will use. Complete the following information,
and click Next.
- UNIX and Linux – At the prompt Which user should Build
Forge run as, accept the default user (root) or specify
a different user. This user starts the Build Forge engine and the
supplied Apache Tomcat. The user must have read and executed permissions
for the database libraries and the JDBC jar files that are specified
on upcoming pages 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.
Important: 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.
- Database Configuration – To configure
the database, complete the following steps:
- To test the configuration, configure the database connection for
JAS and click Test connection near the bottom
of the screen. After the test passes, click Next.
- Configure the database client library and click Test
connection. After the test passes, click Next.
- 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, 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.
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.
- Install Packages: Application and web server configuration –
Complete the requested information on each of the four pages, clicking Next after
completing each page.
- Web Server/PHP Configuration
- Supply your own webserver? Select Yes if you want
to supply your own web server. 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.
- Do you wish to use Secure HTTP? Select Yes if you
want to use Secure HTTP. No is the default.
- Memory Limit for PHP: If you do not want to use the default,
enter a memory limit for PHP. 256 MB is the default.
- Application Server Configuration
- Supply your own application server? To configure Build
Forge to use an application server that you have already installed,
select Yes. No is the default.
Note: Select
Yes 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.
- Which port should application server use for HTTP? Enter
the port that you want the application server to use. 8080 is
the default.
- Which port should the application server use for SSL? Enter
the port that you want the application server to use for SSL. 8443 is
the default.
- Which port should the application server use for AJP? Enter
the port that you want the application server to use for AJP. 8009 is
the default.
- Which port should the application server use for SHUTDOWN? Enter
the port that the application server uses when shutting down. 8005 is
the default.
- Fully qualified Domain Name of the Application Server Enter
the application server’s fully qualified domain name. For example, WIN-TB4MVA22E7P.cn.ibm.com.
- Services Configuration Complete the
following fields on the Services Configuration panel.
- Listen on port - Select this check box.
One or both ports must be selected as the services port. 3966 is
the default.
- Listen on secure port - Select this check
box. One or both ports must be selected as the services port. 49150 is
the default.
- 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.
At the prompt, Do you wish to modify default or
upload a custom certificate?, choose from the following
options:
- To use the self-signed certificate that the installer creates
as is:
- At the prompt, Do you wish to modify default or upload
a custom certificate, select No.
The following prompt is displayed.
- Do you have an existing secure certificate? Select No.
- To use the self-signed certificate that the installer creates,
but modify its fields:
. Additional fields for the certificate are
displayed. Complete the fields and Next.
- At the prompt, Do you wish to modify default or upload
a custom certificate, select Yes.
- At the prompt, 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:
- Keystore Password Enter the password for
the keystore that contains your certificate.
- Verify Password Re-enter the password for
the keystore that contains your certificate.
- Specify a signed certificate in a keystore that is type pkcs12.
Note: Browsers typically warn about accessing a secure site that
has a self-signed certificate. Typically, you are given the option
to proceed, but might be required to confirm the exception.
- Install Packages: Console Start Options – Complete
the requested information.
- Specify the database port. Port 3306 is
the default.
- In the Database Name field, enter
the database name.
- In the Database Username field,
enter the user name to be used when logging on to the database.
- In the Password field, enter
a password that is required to log on to the database.
- In the Confirm Password field,
re-enter the password.
- In the JDBC Driver location field,
click Browse to search for and select the location
of the JDBC driver. The required driver JAR files
and required JDBC driver class are displayed.
- To test the database configuration connection, click Test
connection.
- After the test passes, click Next. The next panel of console start options is displayed.
- On the Database Client Library Configuration Information
panel, click Browse to search for and select
the path to your SQL client libraries.
- To test the database connection again, click Test
connection. The result of the test connection
is displayed.
- Click Next.
- 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.
- 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
- Features
- Build Forge Features Review the features or modules to
be installed. For example, the core product modules are: Web Interface,
Process Engine, and Services Layer.
- Environment
- English is the default environment.
- Repository Information
- Files will be retrieved from the following locations: Use
this section to review and confirm the repository location.
- 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, use http://localhost.
Note: If you cannot log in immediately
after the 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 installation.
Doing so can corrupt the database schema. If the database schema is
corrupted, you have to drop all Build
Forge® tables from the
database and reinstall Build Forge.
- Log in. Log in using the user name root and
the password root. Change the root password immediately.