All services on a single: RHEL/CentOS 7.3 server | RHEL/CentOS 6.9 server
Refer to the following topics if you plan to install TeamForge 17.8 on a three-server distributed setup.
| RHEL/CentOS 7.3 |
|---|
| Install TeamForge 17.8 and EventQ on two separate servers and: |
| Database and Datamart on a separate server |
| Black Duck Code Sight on a separate server |
| SCM and Git on a separate server |
| Oracle database on a separate server |
| Git on a separate server |
Refer to the following topic if you plan to install TeamForge 17.8 on a four-server distributed setup.
Install TeamForge 17.8 on a server and EventQ, Database and SCM on separate servers
| Supply license key: From TeamForge user interface | As a text file |
| Verify your TeamForge 17.8 installation |
| Maintain your site |
You may choose to upgrade on the same hardware or new hardware. Refer to the topic that suits your needs.
| Upgrade on same hardware | Upgrade on new hardware |
|---|---|
| From 17.4 to 17.8 on: RHEL/CentOS 6.9/7.3 server | From 17.4 to 17.8 on: RHEL/CentOS 7.3 server |
| From 16.3 to 17.8 on RHEL/CentOS |
Refer to the following topics if you have TeamForge 17.4 running on a three-server distributed setup and are planning to upgrade to TeamForge 17.8 on the same hardware.
| RHEL/CentOS 6.9/7.3 |
|---|
| Upgrade TeamForge and EventQ running on two separate servers and: |
| Database and datamart on a separate server |
| Black Duck Code Sight on a separate server |
| Git on a separate server |
| Oracle database on a separate server |
Refer to the following topics if you have TeamForge 17.4 running on a four-server distributed setup and are planning to upgrade to TeamForge 17.8 on the same hardware.
| RHEL/CentOS 6.9/7.3 |
|---|
| Upgrade TeamForge, EventQ, Database and SCM on four separate servers |