This section describes what you need to do after installing the
Build Forge system.
- Check the PATH variable.
- Identify the proxy server for PHP to use, if 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
Optional: this step
is needed only if the Management Console needs 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)
Optional:
this step is needed only 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 1 GB (1024 MB) heap size. If you get Out of Memory
errors while running reports (possible on large reports), increase
this setting. That may in turn require you to add memory to the host.
JAVA_OPTS -Xmx1024M
Log message migration
Build Forge stores job
messages in a different manner from older releases. As such, if the
Build Forge install is an upgrade from a previous release, the "Message"
column in the job output page may be temporarily blank until the migration
of that particular job is complete. As this happens in small, low-priority
batches, the migration may take time; if any job has blank messages,
it is recommended that the user simply wait until that job's
message migration is complete.