Install and Configure Team Server and Repository

From TeamServer ER/Studio
Jump to: navigation, search

Go Up to Installation Notes

Please ensure that you have read the Installation Notes before proceeding.

Notepad blue icon 2.pngNote: Repository 2016 installation is now part of Team Server 2016 installation.

To install Team Server and Repository, you need to run the new installer and follow the steps. You need a user with administrative privileges to run the installation wizard.

In this page, you can find detailed information about the different steps of the installation wizard.

Magic Wand Icon.pngTip: You may have to create a blank database before starting the installation, please check the Installation Checklist.

  1. Run the installation wizard. Select I agree...and click Install.
    Notepad blue icon 2.pngNote: In case you need to change the default Port or the Install location, please click Options previous to Install.
  2. In the Configurator Welcome Page, use Admin/Admin (case-sensitive) as the login and password and click Login to start the configuration wizard.
  3. In the Repository page, click on Select DBMS to start the Database configuration.
  4. In the Repository Setup page, you need to specify the information to connect to your Repository database:
    1. Select the DBMS type.
    2. Complete the information about the Repository database:
      Notepad blue icon 2.pngNote: If you have installed Team Server, CONNECT, or Portal in the past, please see Upgrading Team Server and Repository.
      1. In the Host Name:Port field, enter the hostname of the machine that contains the Repository database. The port number appears by default. Change it if needed.
      2. In the Login field, enter the username to access the Repository database.
      3. In the Password field, enter the password for the user specified earlier.
      4. On the Database field, enter the name of the database that you have previously created to be your Repository database.
      5. Login credentials to be used by Team Server to interact with the database (case-sensitive).
      Additional Notes: Depending on the database platform that you selected previously, complete the following fields:
      If you selected Oracle:
      • On the SID field, enter your database identifier.
      • If you selected Use Oracle Service Name, the SID field will be Oracle Service Name. Enter the service name you use.
      If you selected Microsoft SQL Server:
      • If the database server is a named instance, specify the Host Name in the HostName\NamedInstanceName format. For example, DEWKBOW01\DBServer.
      • Optionally, for Microsoft SQL Server 2012 and 2014 only, you can check Use SSL to enable the Secure Sockets Layer (SSL) communication protocol, which encrypts messages. When SSL is enabled, Team Server uses ports 80 and 443 for secure communications. Please check SSL enablement requirements.
      • It is possible to have the installer create your MSSQL database for you at this point. If you enter the name of a non-existent database, the installer will pop up a confirmation window and then create the database.
    3. Click Next to continue.
    DB2 Setup page Oracle Setup page
    Notepad blue icon 2.pngNote: If you want to just install the Repository, exit the configurator at this point and stop the Tomcat service (Team Server).
  5. In the Accounts page:
    1. In the Windows User field, enter the name of a Windows user that Team Server can use to log into the system. The user account must have local administrative privileges. The name should be in the format "machine_name\username".
    2. In the Password field, enter the password of the Windows user.
    3. Login credentials to be used by Team Server to interact with repository (case-sensitive):
      • Leave it in blank to keep using Admin/Admin to log into ER/Studio Repository.
      • If you want to modify the super user login to enter into ER/Studio Repository, introduce the information. If the login does not exist, it will be created.
    4. Click Next to continue.
    Q6Installer(local admin).png
  6. In the License page, you can register your licenses.
    1. In the EDN Login or Email Address field enter your existing Developer Network account. If you need a new user account, click Create Account. Fill in the required information.
    2. In the Password field, enter your EDN password.
    3. Specify the serial number to register in the Serial Number field.
    4. Click Next.
    Notepad blue icon 2.pngNote: If you have a license file, please use the Import from file button to register.
  7. In the HTTPS Setup page, you can optionally choose to enable HTTPS (SSL). It is recommended that you enable secure communications as this will keep your password transmissions secure.
    1. Optionally, select Enable Secure Communication (HTTPS) to enable it.
    2. If you do not have SSL set up on your server, you can click the Self-Signed button to walk you through the short wizard that will create a Keystore file allowing you to use encryption.
      • Fill out the fields of the Self-Signed wizard and click Generate. The Keystore file will be created in the location of your choosing.
    3. If you already have SSL set up on your server, directly enter the information required.
    4. Click Next.
  8. In the Single Sign-On via LDAP page, optionally, check Use LDAP server for authentication to use the Lightweight Directory Access Protocol (LDAP) and enable the ability for users to log into Team Server using their domain username and password. You can enable LDAP authentication anytime later:
    1. In the LDAP URL field, enter the URL of the server running LDAP.
    2. In the Manager DN field, enter the distinguished name for the user that is used to authenticate users. Team Server uses this to connect to the LDAP server and validate user credentials. For example, CN=administrator,CN=Users,DC=mydomain,DC=com.
      Notepad blue icon 2.pngNote: In this example, administrator has been used. In which case, Users is defined as a container rather than an organizational unit as is the Microsoft Active Directory default. Your user accounts may be in an organizational unit; in this case, you would specify it differently, for example, CN=user1,OU=sales,DC=mydomain,DC=com.
    3. In the Manager Password field, enter the password for the administrative user.
    4. In the Search Base DN field, enter the name of the root node in LDAP from which to search for users. For example, CN=Users,DC=mydomain,DC=com.
    5. In the Search Attribute field, enter the attribute in LDAP holding the user's login name. For example, sAMAccountName (for ActiveDirectory).
    6. In the Test User/Password field, enter the username and password of a sample user to attempt to authenticate against the LDAP server. The installer uses this information to validate the given LDAP information before moving to the next page.
    7. Click Test Connection. If it is ok, this will enable the Next button.
    8. Click Next.
  9. In the Notification Enablement page, optionally, check Enable Email Notifications via SMTP to allow users to send search results and reports by email directly from Team Server. You can enable notifications anytime later:
    1. In the Email Address field, enter the email address that you want to use as the sender of the emails sent from Team Server. You may want to prepare a special email address on your email server for this purpose.
    2. In the Server/Port field, enter the host name of the email server (for example, "mail"), the fully qualified network name (for example: ""), or the IP address (for example: "") and the port number where the email server is listening. The default port is 25.
    3. Optionally, check "Requires Authentication" if your email server requires authentication. When you check this option, the User Name and Password fields are highlighted. Fill them with the required values to authenticate Team Server against your STMP server.
    4. Click Next.
  10. In the Migration page, you perform the data migration during an upgrade. Click the Start button for this purpose.You can load or save the log file generated by clicking Load log file.
    Migration 2.png

Notepad blue icon 2.pngNote: Please note that the configurator will show the Migration tab only if you are upgrading.

Team Server and Repository are now installed and configured on your system.

Modify Configuration

You can modify the configuration at any moment:

  • Use Configure Team Server. From Windows: Start > All Programs > Team Server 2016 > Configure Team Server.
  • Select My Setting > Configurator once you are logged as Admin in Team Server.

See Also