





  INSTALLING TEAMCONNECTION FOR WINDOWS
  _____________________________________





  This chapter lists the hardware and software that are required before you can
  install and use the TeamConnection for Windows products.  It also describes
  the tasks that you must do before installation, and provides detailed
  instructions for installing and configuring the TeamConnection family server
  and client.


  HARDWARE REQUIREMENTS
  _____________________

  The following are hardware requirements for the TeamConnection Windows NT
  FAMILY SERVER machine:

  +---------------------------------------------------------------------------+
  | Table 1. Hardware Requirements for a Windows TeamConnection Server        |
  +------------------+--------------------------------------------------------+
  | FAMILY SERVER    | o   Processor: 90 MHz Pentium-based processor or       |
  |                  |     higher (however, the PowerPC is not supported)     |
  |                  | o   Pointing device: A mouse or other pointing device  |
  |                  | o   Monitor: VGA or higher resolution with the         |
  |                  |     appropriate adapter                                |
  |                  | o   Memory: 48 MB memory minimum; more may be needed   |
  |                  |     according to number of users and database size     |
  |                  | o   Disk space:                                        |
  |                  |     -   200 MB for operating system and prerequisites  |
  |                  |     -   200 MB for user data (1+ GB recommended)       |
  |                  |     -   60 MB for TeamConnection server code           |
  |                  |     -   128 MB for swapper space (150+ MB recommended) |
  |                  | o   Communications support: Network card supported by  |
  |                  |     TCP/IP for Windows NT                              |
  |                  | o   A CD-ROM drive (internal or external) for          |
  |                  |     installation of the product                        |
  +------------------+--------------------------------------------------------+
  | BUILD AGENT AND  | o   Processor: Any processor supported by the required |
  | PROCESSOR        |     version of Windows, except the PowerPC             |
  |                  | o   Pointing device: A mouse or other pointing device  |
  |                  | o   Monitor: VGA or higher resolution with the         |
  |                  |     appropriate adapter                                |
  |                  | o   Memory: 32 MB memory minimum; more may be needed   |
  |                  |     according to compilers and linkers used            |
  |                  | o   Disk space:                                        |
  |                  |     -   75 MB for operating system and prerequisites   |
  |                  |     -   15 MB for TeamConnection build server code     |
  |                  |     -   45 MB for swapper space                        |
  |                  | o   Communications support: Network card supported by  |
  |                  |     TCP/IP for Windows NT or Windows 95                |
  |                  | o   A CD-ROM drive (internal or external) for          |
  |                  |     installation of the product                        |
  +------------------+--------------------------------------------------------+


  (C) Copyright IBM Corp. 1cryears.                                           1









  SOFTWARE REQUIREMENTS
  _____________________

  The following are software requirements for the Windows FAMILY SERVER, BUILD
  PROCESSOR, BUILD AGENT, and CLIENT machines:

  +---------------------------------------------------------------------------+
  | Table 2. Software Requirements for TeamConnection for Windows             |
  +------------------+--------------------------------------------------------+
  | SERVER AND BUILD | Microsoft Windows NT, Version 3.5.1 or later, which    |
  | AGENT            | includes TCP/IP                                        |
  +------------------+--------------------------------------------------------+
  | CLIENTS          | One of the following:                                  |
  |                  |                                                        |
  |                  | o   Microsoft Windows 95, which includes TCP/IP        |
  |                  | o   Microsoft Windows NT, Version 3.5.1 or Version     |
  |                  |     4.0, which includes TCP/IP                         |
  |                  | o   Microsoft Windows, Version 3.1 or later and the    |
  |                  |     following:                                         |
  |                  |     -   DOS Version 3.3 or later                       |
  |                  |     -   IBM TCP/IP for DOS Version 2.1.1 (part number  |
  |                  |         87G7184)                                       |
  +------------------+--------------------------------------------------------+
  | WINDOWS NT BUILD | Microsoft Windows NT, Version 3.5.1 or later, which    |
  | PROCESSOR        | includes TCP/IP                                        |
  +------------------+--------------------------------------------------------+
  | WINDOWS 95 BUILD | Microsoft Windows 95                                   |
  | PROCESSOR        |                                                        |
  +------------------+--------------------------------------------------------+


  PREPARING TO INSTALL TEAMCONNECTION FOR WINDOWS
  _______________________________________________

  This section explains what you need to do before installing TeamConnection
  for Windows.


  UPDATING TCP/IP FILES

  Before you install the TeamConnection code, you must have the correct version
  of TCP/IP installed on your workstation.  See "Software requirements" for the
  communications software requirements for your operating system.

  TeamConnection uses the value of the TCP/IP USER environment variable to
  create the initial user in the database.  If this variable is not set,
  installation will fail.  Type "set | more" to display the environment
  variables and look for the USER variable.  If the variable is not set, or if
  you want to change its value, type "set user=userid" in the System window of
                                               ______
  the Control Panel folder, where userid is the ID you want TeamConnection to
                                  ______
  use.  Shut down the workstation and then restart it to accept the changes
  made to the environment variables.  If there is no user environment variable
  specified, TeamConnection sets TC_USER and TC_BECOME to TCUSER.  You can
  change these values as described above.

  After TCP/IP is installed, update your TCP/IP services and hosts files.


  2









  Do the following steps.

  1.  Update the services file, which is located in the directory where TCP/IP
      is installed.  To determine the directory name, type "echo %etc%" at a
      prompt.

      Include the family name and port address of the TeamConnection server.
      The port address can be any 4-digit number, as long as it does not
      already exist in your services file.  You might want to ask your TCP/IP
      administrator to assign you a number.

      Type the following entries in your services file:

        #  TeamConnection servers
        testfam    ffff/tcp     # port address for the TeamConnection test family
                   ____
        bldsock    bbbb/tcp     # port address for the build agent and build processor
                   ____

      NOTES:

      a.  For this installation, replace ffff and bbbb in the above example
                                         ____     ____
          with appropriate port addresses.
      b.  Follow each line with a carriage return.

  2.  Update the TCP/IP hosts file.  If you have a hosts file, it is located in
      the winnt/sys32/drivers/etc subdirectory.  If the hosts file does not
      exist, you must configure it through TCP/IP.

      Add the following:

      o   IP address.
      o   Server name.
      o   Alias name of the TeamConnection family server, which is your family
          name.  For this initial installation of TeamConnection, the family
          name is testfam.
                  _______
      o   Alias name for the build socket.  For this initial installation of
                             ____________
          TeamConnection, use bldsock.
                              _______

      The following is an example of the entry you would type in your hosts
      file:

        9.12.345.67   teamserv.company.com   testfam   bldsock

      NOTE:  Follow the line with a carriage return.  You can use the hostname
             command to get the name of the server.

  3.  Do the following to verify that you can connect to your TeamConnection
      family:

      a.  At a prompt, type "ping testfam".







                                       Installing TeamConnection for Windows  3









      If you receive information that is similar to the following, you can
      successfully connect to your TeamConnection family:

        PINGING teamserv.company.com (9.12.345.67): with 32 bytes of data:

        Reply from 9.12.345.67: bytes=32 time=10ms TTL=255
        ...

      The PING command will send four requests and then it will stop.

      If you receive the message "unknown host testfam", you cannot connect to
      the family.  Verify that the data you entered in the hosts and services
      files is correct, and then try the command again.  If you still do not
      get the correct response, contact your TCP/IP administrator to solve the
      problem.

  4.  Do the following to verify that you can connect to your TeamConnection
      build server:

      a.  At a prompt, type "ping bldsock".
      b.  Press Ctrl+C to end the command.

      If you receive information that is similar to the following, you can
      successfully connect to your TeamConnection family:

        PING teamserv.company.com: 56 data bytes
        64 bytes from 1.23.457.78: icmp_seg:0. time=0. ms
        64 bytes from 1.23.456.78: icmp_seg:1. time=0. ms
        64 bytes from 1.23.456.78: icmp_seg:2. time=0. ms

      If you receive the message "unknown host bldsock", you cannot connect to
      the build server.  Verify that the data you entered in the hosts and
      services files is correct, and then try the command again.  If you still
      do not get the correct response, contact your TCP/IP administrator to
      solve the problem.

      Do not install the TeamConnection components until the ping commands
      successfully complete.


  GETTING TEAMCONNECTION UP AND RUNNING
  _____________________________________

  This section provides step-by-step instructions for the initial installation
  of TeamConnection, and gives instructions for verifying the installation.

  This section is intended for the administrator who does the initial install
  of TeamConnection for your organization.  It assumes that you are installing
  all of the following components on the same workstation:

  o   TeamConnection family server (including ObjectStore database)
  o   Client
  o   Build agent
  o   Build processor
  o   Online documentation


  4









  If you do not follow these instructions as written, the verification step on
  page 12 might fail.

  The time required for installing this program varies depending on your
  workstation.  In general, installation of the product takes about 15 minutes.

  After completing the instructions in this section, you will have a family
  called testfam.  Consider this your test family, and use it to verify that
  TeamConnection is working properly.  This family is configured with the
  default information that IBM ships.

  You can use testfam to explore and learn about TeamConnection.  Using testfam
  with the shipped default information will help you determine how to customize
  TeamConnection to fit your development needs.

  NOTE:  When installing only a client, follow the instructions in Getting
                                                                   _______
         Started with the TeamConnection Clients.
         _______________________________________

  The following is a list of the tasks you do to install TeamConnection.

  +---------------------------------------------------------------+-----------+
  | TASK                                                          | PAGE      |
  +---------------------------------------------------------------+-----------+
  | Install the TeamConnection components                         | 5         |
  +---------------------------------------------------------------+-----------+
  | Set the environment variables                                 | 6         |
  +---------------------------------------------------------------+-----------+
  | Configure and start the ObjectStore server                    | 7         |
  +---------------------------------------------------------------+-----------+
  | Verify installation                                           | 8         |
  +---------------------------------------------------------------+-----------+
  | Start the TeamConnection client                               | 13        |
  +---------------------------------------------------------------+-----------+


  INSTALLING THE TEAMCONNECTION COMPONENTS

  This section describes the steps to follow when installing the TeamConnection
  components.  It is assumed that you have already completed the
  pre-installation tasks noted in "Preparing to install TeamConnection for
  Windows" on page 2.


  Step 1:  Starting the installation

  1.  Insert the CD-ROM into the reader.

  2.  In the Program Manager, select RUN from the FILE menu, then type
      "x:\install" in the entry field and press OK.  Replace x with the CD-ROM
       _                                                     _
      drive letter.

  3.  On the Welcome window, select NEXT to advance to the next window.




                                       Installing TeamConnection for Windows  5









  Step 3:  Selecting the components for installation

  Use the Select Components window to select which components you want to
  install and where you want to install them.

  1.  Select SELECT ALL to install all the TeamConnection components.  To
      choose components, select CLEAR ALL and then select the components you
      want installed.

  2.  Select NEXT to advance to the next window.

      The Select Destination Directory window indicates the space needed to
      install the components you selected.

  3.  To change the destination directory, select BROWSE.  you can type a new
      path in the entry field of the window displayed or select a new
      destination directory from the drive and directory
       lists.  Select OK to return to the Select Destination Directory window,
      then NEXT to advance to the next window.


  4.  On the Select Program Folder window type the name you want to use for
      your TeamConnection folder or select an existing folder fro m the list.
      The default is TeamConnection.  Select NEXT to advance to the next
      window.

      The Start Copying Files window displays.  This window summarizes the
      components, install path, and folder you have selected.

  5.  Select NEXT to perform the installation.

      The Setup Complete window displays.  This window presents the option to
      restart the computer now or later.

  6.  Select Finish to complete the installation.


  Step 4:  Completing the installation

  Verify that the installation program created a program group for
  TeamConnection, which includes several program icons.  If you did not restart
  your computer during installation, do so now.


  SETTING THE ENVIRONMENT VARIABLES

  During installation, TeamConnection automatically updated your Control Panel
  with environment variables.  If you need to change any of the environment
  variables, update them in your Control Panel and then restart your computer.
  TeamConnection places the following environment variables in the System
  Environment Variables section of the Control Panel:





  6









  We recommend that you use the default values for this initial installation.
  If you change the values, you will need to provide them when you set up the
  TeamConnection server.

      BOOKMGR=x:\teamc\nls\doc\enu
      HELP=x:\teamc\nls\msg\enu
      LOCPATH=x:\teamc\locale
      NLSPATH=x:\teamc\nls\msg\enu\%N
      READIBM=x:\teamc\nls\doc\enu
      TC_BECOME=TCUSER (unless specified)
      TC_DBPATH=x:\teamc\testfam
      TC_FAMILY=testfam
      TC_USER= TCUSER (unless specified)

  For ObjectStore, the following variables are created:

      INCLUDE=x:\ostore\include
      LIB=x:\ostore\lib
      OS_ROOTDIR=x:\ostore

  Where:

  o   x is the drive on which the TeamConnection server is installed.
      _
  o   teamc is the default directory created for the server.

  NOTE:  If a TCP/IP USER variable already exists in the Control Panel,
         TeamConnection uses the value of that variable for the TC_BECOME and
         TC_USER e nvironment variables.


  CONFIGURING AND STARTING THE OBJECTSTORE SERVER

  The TeamConnection server communicates with the ObjectStore database through
  an ObjectStore server.  This database was installed with the family server.

  NOTE:  You can have only one version of the ObjectStore database on the
         server machine.

  Do the following to configure the ObjectStore server:

  1.  Start the ObjectStore for Windows Setup program to initialize the
      ObjectStore server parameters.  Start the program in one of two ways:

      o   From the TeamConnection Group folder on the desktop, select the
          OBJECTSTORE SETUP VERSION 4.0 icon.

      o   From the directory where the ObjectStore server is installed
          (teamc\bin is the default), type "ossetup" and press Enter.

      The ObjectStore for Windows Setup window appears.

  2.  Select AUTO START SERVER if it is not already selected.




                                       Installing TeamConnection for Windows  7









  3.  Select INITIALIZE SERVER.  This push button is named REINITIALIZE SERVER
      if you are re-installing ObjectStore.  The Server Initialization window
      appears.

  4.  Change the default log file's name, drive, or directory if appropriate.

  5.  Select OK.

  6.  If you are re-installing ObjectStore, the Confirm window appears.  Select
      YES.

  7.  The ObjectStore for Windows Setup window appears.  Select EXIT.

  8.  Start the ObjectStore server in one of two ways:

      o   During setup, you can set an autostart option to automatically start
          the ObjectStore server when you start your computer.

      o   Start the server using the Services window in the Control Panel
          folder.  Locate the ObjectStore Server and ObjectStore Cache Manager
          entries in the listbox.  If the status isn't started, select each
          entry in turn and then select START.

      Verify that the ObjectStore server (OSSERVER) is active in the Services
      window in the Control Panel folder.

  If you experience problems configuring and starting the ObjectStore server,
  the following files can provide you additional information about ObjectStore
  errors.  These files are located in the teamc\temp directory.

  o   osserver.txt
  o   osc4.out
  o   oss.out


  VERIFYING THE INSTALLATION OF TEAMCONNECTION

  Do the following to verify that TeamConnection installed successfully.


  Step 1. Create your test family

  Before you can verify that TeamConnection is installed correctly, you must
  create your family.  When you create your family, you are loading default
  information shipped by IBM and creating a superuser ID.  A superuser ID is
  required so that at least one person has privileged access to the family to
  perform special tasks, such as creating other user IDs.

  This section leads you through the following procedures to create a test
  family called testfam.
                ________

  1.  Verifying that the ObjectStore server is active

  2.  Creating testfam


  8









  VERIFYING THAT THE OBJECTSTORE SERVER IS ACTIVE:  Before you create your test
  family, verify that the ObjectStore server (OSSERVER) is active in the Task
  List.

  CREATING TESTFAM:  To create a test family to be used for installation
  verification, follow these steps.

      To start the family administrator program, select the TeamConnection
      Family Administrator icon from the TeamConnection Group folder o n the
      desktop.

  1.  From the TeamConnection Family Administrator window, select
      FAMILY > NEW > DEFAULT.

      A settings notebook opens.  You use this window to set up your test
      family.  This notebook contains several pages, but for now you need only
      the FAMILY INFORMATION and INITIAL SUPERUSER pages.  See page 89 of
      the TeamConnection Administrator's Guide for more information on
      all of the family options you can set using this notebook.

      NOTE:  In these instructions, the values you can enter appear as follows.
             TeamConnection's installation verification procedure requires that
             some of these values be set exactly as shown.

             o   BOLDFACE indicates values you need to enter exactly as shown.
             o   Italics indicates values that you can substitute to suit your
                 _______
                 needs or local conventions.

  2.  Complete the fields on the FAMILY INFORMATION page of the settings
      notebook as follows.

      NAME      TESTFAM

      PATH      d:\dbpath
                _________

                Specify the fully-qualified path name of the directory where
                you want testfam stored.  TeamConnection creates testfam in a
                subdirectory of the path you specify.  This subdirectory has
                the same name as the family.  If you specify C:\PRODDEV as the
                path name for testfam, for example, TeamConnection places all
                files related to the family in the directory path
                c:\proddev\testfam.

                NOTE:  If a testfam directory already exists, you will need to
                       delete it before you proceed.  This procedure will fail
                       if a testfam directory already exists.

      PORT      xxxx
                ____

                Specify the TCP/IP port address for testfam, which was set in
                your TCP/IP services file before you installed the product.
                See page 2 for more information.

      MAILER    MAILEXIT


                                       Installing TeamConnection for Windows  9









  3.  Complete the fields on the INITIAL SUPERUSER page of the settings
      notebook as follows.

      LOGIN     loginID
                _______

                Specify a login ID for the superuser for the family.  This
                parameter is used in multiuser environments, such as AIX,
                HP-UX, and Windows NT, to identify the user account to which
                the TeamConnection superuser ID is assigned.  Single-user
                environments, such as OS/2, do not define a separate login ID.
                If you do not set a value in the USER field, it defaults to the
                value specified for the LOGIN field.  Use the value set for the
                TC_USER environment variable.  To see this value, type the
                following from a command prompt and look for the TC_USER
                variable:

                  set | more

      NAME      userName
                ________

                Specify the full name of the superuser, for example, Thomas C.
                Jones.

      HOST      hostname
                ________

                Specify the TCP/IP host name for the family server machine,
                which was set in your TCP/IP hosts file before you installed
                the product.  See page 2 for more information.

                To see this value, type the following from a command prompt:

                  hostname

                NOTE:  You do not need to use the fully-qualified host name.
                       You can, for example, specify myServer instead of
                                                     ________
                       myServer.myCompany.com.
                       ______________________

      USER      Specify the TeamConnection user ID for the superuser.  If you
                omit this parameter, it defaults to the value specified in the
                LOGIN field.  It is a good idea to give the superuser an ID
                that is readily identifiable as a superuser.  A good way to do
                this is to preface the user ID with su_, such as su_john.

      PASSWORD  Specify the password to be used to verify the superuser's
                access to the TeamConnection server.

  4.  After you have set all the values on the FAMILY INFORMATION and INITIAL
      SUPERUSER pages, of the family settings notebook, select the CREATE push
      button.

      As TeamConnection creates testfam, the CREATE FAMILY window appears
      showing the commands executed and the status of each step in the family
      creation process.  The following is an example of this window.



  10










  Figure 1. Create Family window

      For an explanation of the commands executed in each step of the family
      creation process, see page 253 of the TeamConnection Administrator
      Guide.  After testfam is created, you should be able to see the
      following:

  o   A family administrator icon labeled testfam in the TEAMCONNECTION FAMILY
      ADMINISTRATOR window.
  o   A subdirectory called testfam in the directory path that you specified on
      the family settings notebook.

  This subdirectory, in turn, contains the following:

  AUTHORIT.LD
    The default authority groups for the family

  CFGFIELD
    A subdirectory containing default configurable field information

  COMPROC.LD
    The default component processes for the family

  CONFIG
    A subdirectory containing default user exit information for the family and
    security information

  CONFIG.LD
    The default configurable field types for the family

  INTEREST.LD
    The default interest groups for the family

  QUEUE
    A subdirectory for the messages to be sent by the notify daemon

  RELPROC.LD
    The default release processes for the family

  SCHEMA.ADB
    Metadata (definitions of objects such as users, parts, and releases) for
    the family

  TESTFAM.TCD
    The family database










                                      Installing TeamConnection for Windows  11









  Step 2. Start the family server

  You can start the TeamConnection server in the following ways:

  o   Double-click the testfam icon in the TeamConnection Family Administrator
      window.

  o   From the TeamConnection Family Administrator window, select the testfam
      icon and then select FAMILY > OPEN &RARRO W. SERVER from the pop-up menu.
      In the TESTFAM - FAMILY SERVERS window, select the START BOTH push
      button.

      After the family and notification servers are running, you can minimize
      the TESTFAM - FAMILY SERVERS window, but d o not close it.  Closing this
      window stops the servers.

  o   From a command prompt, type the following command.  Use of this command
      assumes that the path statements and environment variables have been set
      properly.

        teamcd testfam

      Where:

      -   x is the drive where the server is installed.
          _
      -   teamc\bin is the default directory where the server is installed.
      -   testfam is the name of your TeamConnection test family.

  See page 76 of the Administrator's Guide for more information about
  the teamcd command.


  Step 3. Verify TeamConnection installation

  The following installation verification procedure runs a command file called
  univwin.cmd, which performs a series of TeamConnection actions on testfam.
  Executing this command file requires that you have a full build environment
  set up, including VisualAge C++.  page 211 of the Administrator's
  Guide explains how to install the build function.  If you have not
  installed the build function or VisualAge C++, please omit this
  procedure.

  To verify that TeamConnection installed correctly, do the following:

  1.  Type the following at a prompt in the directory where TeamConnection is
      installed, and then press Enter.

        univwin

      Type YES when you are asked if you want to start the build server.  When
      you are asked to enter the build server socket name, type BLDSOCK.  This
      is the build socket name that is specified in the hosts file.

      A file called univwin.log is created.



  12









  2.  Review univwin.log for a completion code of zero on the commands it
      executes.  If all commands execute successfully, then TeamConnection was
      installed and configured correctly.


  STARTING THE TEAMCONNECTION CLIENT

  To start the TeamConnection client, select the TEAMCONNECTION CLIENT icon
  from the TeamConnection Group folder on the desktop.  The Task List window
  appears.


  WHAT DO YOU DO NOW?
  ___________________

  You now have your initial family installed and running.  As mentioned earlier
  in this chapter, you or someone else in your organization can use this family
  to verify that TeamConnection is working properly.  You can also use this
  family to explore and learn about TeamConnection, and test configuration
  changes, user exits, automated backup utilities, and automated build and
  packaging events.

  Before your users install the TeamConnection client, read page 69 of the
  Administrator's Guide to understand what you can do to simplify their
  installation procedure.

  The remaining chapters of this book provide instructions for installing build
  processors or build agents on a different machine and instructions for
  starting and stopping the servers.

  To learn more about planning for and creating your TeamConnection
  production family, see page 89 of the Administrator's Guide.

























                                      Installing TeamConnection for Windows  13



