Use the mc-<version>-<build>.tar.gz tar file provided with the installation media to install and configure the Management Console on z/Linux. IBM Installation Manager is not used for this installation.
The console for z/Linux is packaged with the IBM HTTP server, rather than with the Apache web server.
After you install the Management Console, install the agent rpm package (zlinux-bfagent-<version>.rpm) on z/Linux to set up a z/Linux server for Build Forge®. For installation instructions, see Installing the agent on UNIX and Linux systems.
If you choose WebSphere Application Server, you provide more information:
http://mydomain.com:9080/jas
If you choose the provided IHS server, you provide more information about SSL, including whether to use SSL, ports and memory to use, and whether to use an existing secure certificate or create one.
./cmdline-install.sh
Install directory [/opt/buildforge]
What database will you be using?
Enter the # of the database you will use
1) DB2
2) Oracle
3) MySQL
What is your database hostname? 127.0.0.1
What is your database port number? [1521]
What is your database name? build
What is your database user name? build
What is your database user password?
Confirm your database user password?
Would you like this installation to create the Build Forge database schema? (y|n) [y]
Specify
client libraries and information at this point. Depending on your
choice of database, you are prompted as follows. Use absolute paths. Where are your 32-bit DB2 client libraries (libdb2.so.1)?
Where is your DB2 (DB2_HOME) installed?
Where are your MySQL client libraries (libmysqlclient.so)?
Where are your Oracle client libraries (libclntsh.so)?
Where is your Oracle instant client (ORACLE_HOME) installed?
Where is your tns.names file located (TNS_ADMIN)?
Please enter the directory with your database JDBC jar file?
Will you be using the supplied Tomcat app server? (y|n) n
Enter the full URL used to contact the services layer on your application server:
http://mydomain.com:9080/jas
Enter the directory to install the Build Forge Services plugins to:
Specify the war deployment directory:
Enter the path to a jar executable (which should be included in any JDK):
Enter the temporary storage path for the Services Layer:
What http port will the Build Forge services layer use? [3966]
What ssl port will the Build Forge services layer use? [49150]
Will you be using the supplied Apache web server? (y|n)[y]
Would you like Apache to use SSL? (y|n)[n] Enter 'y' to configure Apache for SSL
What ssl port will Apache use? [443]
Please enter a memory limit for PHP (in MB): [256]
Would you like to modify or specify a custom SSL certificate? (y|n) [n]
Do you have an existing secure certificate? (y|n)[n]
A validity period is required for this cert please enter in [number][period] format
Examples: 10Y = 10 years, 6M = 6 months, 350D = 350 daysEnter the validity period for this cert:
Enter the common name for the certificate (usually the name of the server) [linux142.rtp.raleigh.ibm.com]:
Please enter your Locality/City:
Please enter your State/Province:
Please enter your Organization Name:
Please enter your Organization Unit:
Please enter your Country from the list below:
France
Taiwan
Italy
Germany
Korea
United States
China
Brazil
Spain
Japan
Please enter your Street Address:
A keystore password is required, and must be at least 6 characters long
Please enter a keystore password
<bfinstall>/rc/buildforge start
<bfinstall>/server/tomcat/logs/catalina.out
The Management Console starts and displays the login prompt.
The license file for z/Linux is located in the <bfinstall> directory. The license file name is IRBF_license. After installation it contains a text message instructing you to download your actual license file from Passport Advantage.
After you have downloaded the license file and placed it in the <bfinstall> directory, configure Build Forge® to use it:
For example: <bfinstall>/IRBF_license.
Review Personal Certificates and Keystores
Keystore | Description |
---|---|
buildForgeKeyStore.p12 | Contains a password protected keyEntry (personal certificate with public/private key pair). |
buildForgeTrustStore.p12 | Contains a password protected trustedCertEntry (certificate with public key only). |
buildForgeKey.pem | Contains a password protected private key. |
buildForgeCert.pem | Contains a non-password protected certificate with public key corresponding to the private key in buildForgeKey.pem. |
buildForgeCA.pem | Initially, contains the same information as buildForgeCert.pem; other peer certificate are added to establish trust. |
buildForgeKeyForApache.pem | This keystore is needed to enable SSL for the Apache HTTP server. Unlike buildForgeKey.pem, it is not password protected allowing the Apache HTTP server to start up without a password prompt. |
For more information about converting an existing PEM certificate and managing certificates, see Managing certificates.
Configure IBM HTTP Server for SSL
See Configuring SSL for IHS in Using IBM HTTP Server instead of Apache HTTP Server. You must change keystore formats and add entries to httpd.conf.
Enable SSL in the Management Console UI
Use the Management Console user interface settings to enable SSL in the Management Console and update the Build Forge® database. You access those settings through . Then, check that the required property values are updated in the bfclient.conf configuration file.
Enable Debugging for SSL
To debug issues with SSL in the Management Console, complete the following steps to log additional information needed for SSL.
export BFDEBUG_SECURITY=1
com.buildforge.level = ALL
Restart Tomcat to make the changes take effect.