Configure CollabNet TeamForge

After you have installed VMware Player, configure the CollabNet TeamForge VMware image.

Only one user needs to configure CollabNet TeamForge. This instance acts as the application server. To access CollabNet TeamForge , the CollabNet TeamForge application server must be running in VMware Player. Then other users can access it via a Web browser without running VMware Player.

  1. Start the VMware player.
    • On Windows, click Start > Programs > VMware > VMware Player .
    • On Linux, run the vmplayer executable.
    Note: You don't have to update the VMware player, but you can.
  2. In the Commands section, click Open.
  3. In the file window, browse to \TeamForge5.3\Image\TeamForge.vmx
    Note: Starting the VMware image may take a few minutes, depending on the speed of your system.
  4. Log in with the username root and the password changeme.
  5. Enter and confirm a new Linux password.
    Tip: The system may warn that your password does not meet security standards. For example, it may be too short. This does not mean the password is rejected. If you confirm the same password, it will work.
  6. When prompted to run the configuration tool, type y.
  7. Read the product license agreement. Type q to close it.
    Tip: You can use the space bar to advance a screen at a time.
  8. If you accept the license terms, type y.
  9. In the CollabNet TeamForge configuration tool, choose Dynamic Networking (DHCP) or Static Networking (Static IP)
    • Dynamic networking is useful for a one-person trial installation. It is quick and easy, but email integration with TeamForge will not work correctly.
      Note: If your IP address changes, you may also have to reconfigure source control.
    • Static networking is best if you are evaluating CollabNet TeamForge with a team, or if you already have a license and intend to use TeamForge to support your team.

      To configure static networking, you will need to get a static IP address and hostname from your network administrator, and specify your network settings when prompted.

      Tip: In this case, it's also a good idea to run TeamForge in VMware Player on a dedicated machine.
    The networking for TeamForge is restarted.
  10. Specify your outgoing email (SMTP) server.
    • For a one-person evaluation, accept the default value.
    • If you have a CollabNet TeamForge license and intend to send email outside of your firewall, use the SMTP server settings provided by your network administrator.
      Note: Depending on your corporate email configuration, your system administrator may need to permit TeamForge to send mail to the corporate mail server.
  11. Choose whether to run CollabNet TeamForge at startup.
    • Choose “Yes” to start CollabNet TeamForge automatically whenever you start the TeamForge VMware image.
    • Choose “No” to require a manual CollabNet TeamForge startup whenever you start the TeamForge VMware image.
  12. At the prompt, click Enter to start your CollabNet TeamForge site.
    Note: Startup can take several minutes, depending on the speed of the host system. On some slower systems, you may get a false failure message from JBoss, like this: jboss (app) (localhost:8080) ............................failed to start in 600 seconds, giving up now. Please check the log: /opt/collabnet/teamforge/log/apps/service.log FAILED

    This can safely be ignored.

    Tip: From now on, you can stop and restart TeamForge using these commands:
    • /etc/init.d/httpd stop
    • /etc/init.d/collabnet stop
    • /etc/init.d/postgresql stop
    • /etc/init.d/httpd start
    • /etc/init.d/postgresql start
    • /etc/init.d/collabnet start
  13. Log into your new site with the user name admin and the password admin. The URL for your site is the IP address or domain name provided in the Linux console at the end of the installation process.
    Note: You will have to change your administrator password when you first log in.
Any user with access to the network where the host system is running can now get to your site via a Web browser.