This section describes what to do after installing the Rational® Build
Forge® system.
- Check the PATH variable.
- Identify the proxy server for PHP to use if the management console
must go through a proxy server to access the database.
- Set JVM memory.
- Log message migration.
Check PATH variable on Windows
The PATH environment
variable on Windows must include the path to the database client or
driver DLLs. Check the PATH manually for these databases:
- DB2 - directory containing db2cli.dll and sqlar.dll
- MySQL - directory containing libmysql.dll
- Oracle - directory containing oci.dll
For Microsoft SQL Server, setting up the ODBC connection takes
care of this requirement.
Identify proxy server
This step is optional.
It is required only if the management console has to use a proxy server
to access its database. You must configure PHP to use the proxy server.
Set JVM memory (required for Quick Report)
This
step is optional; however, it is required if your edition includes
Quick Report (Standard Edition, Enterprise Edition, Enterprise Plus
Edition).
- Set the maximum memory for the JVM to 1 MB or more. Running reports
requires a minimum of 1 GB (1024 MB) heap size. If you get Out
of Memory errors while running reports (possible on large
reports), increase this setting. If you increase this setting, you
might have to add memory to the host.
JAVA_OPTS -Xmx1024M
Log message migration
Rational® Build
Forge® stores job messages
in a different manner from older releases. Therefore, if the Rational® Build
Forge® installation is an
upgrade from a previous release, the Message column in the job output
page might be temporarily blank until the migration of that job is
complete. As this happens in small, low-priority batches, the migration
might take time. If any job has blank messages, it is recommended
that you wait until that job's message migration has completed.