Installing and Configuring DevTest Server

This section describes how to install and configure lsvr.
dts105
This section describes how to install and configure
DevTest Server
.
2
If you are upgrading from an earlier version of
DevTest Solutions
, carefully consider the impacts of the upgrade to your current authentication scheme. For more information, see Identity and Access Manager.
Install DevTest Server on Windows
Before you start the installation procedure, download the following files from the Download Center:
  • The installer for your platform
  • (Optional) The demo server zip file
    Typically, the Demo Server is installed with the Server components only in a standalone system. In a distributed system, the Demo Server is usually installed with
    DevTest Workstation
    for users who are new to
    DevTest Solutions
    . The Demo Server is used for tutorials and for many of the artifacts in the Examples project.
Follow these steps:
  1. Run the installer file; for example, devtest_win_x64.exe.
    The Welcome to the
    DevTest Solutions
    Setup Wizard step opens.
  2. Click
    Next
    .
    The End User License Agreement step opens.
  3. Read the license agreement, scrolling to the end, select the
    I accept the terms of the License Agreement
    option, and click
    Next
    .
    The Select Components step opens.
  4. Ensure that the
    Server
    check box is selected. An embedded Workstation is installed with the Server. Click
    Next
    .
    The Select Destination Directory step opens.
  5. Enter the path and folder name for the installation directory (LISA_HOME).
    • Consider a name that includes the release identifier, if you want to keep the current release separate from older releases. For example, enter: C:\DevTestServer_10.4. Or, accept the default (C:\Program Files\CA\DevTest).
    • If you browse to a path, and you enter the name of a new folder, the installation wizard creates the folder.
    • For more information about selecting the appropriate destination and data directory, see Installation Options.
  6. If you are upgrading from a shared install, enter the path and folder name for the data directory.
    • If you are not upgrading from a shared install, this option does not appear.
    • Enter the path and folder name for the data directory. The default is the data directory detected from the previous shared installation.
    • The specified data directory must exist and the user must have write permissions to it. If it does not exist, the installer will create it and will test to be sure it is writable.
    • If the data directory is different than the installation directory,
      DevTest
      creates a lisa.user.properties file in both the installation directory and in the user's home folder. The
      lisa.data.dir
      property in this property file tells the product where the data directory is located.
    • The data directory will include hotdeploy for server components.  Other server component files will be in the installation directory.
  7. Click
    Next
    .
    The Identity and Access Manager step opens. Identity and Access Manager is required for a
    DevTest
    Solutions installation.
  8. Select one of the following options and click
    Next
    .
    • Install or upgrade Identity and Access Manager
      If this is the first time you are installing IAM, or if you want to upgrade your existing IAM, select this option.
    • Connect to an existing Identity and Access Manager
      If you want to connect to an existing IAM in your environment, select this option. Enter the URL for the existing IAM. This URL is the host and port where Identity and Access Manager was installed. Clicking
      Validate
      verifies that you have entered a valid URL, but does not attempt to connect to IAM.
      A single Identity and Access Manager instance for your entire enterprise allows component access to be managed in a single location. However, if you have multiple registries and need to manage access to each registry separately, you need to install a separate IAM for each registry. This is especially true if users from one registry cannot have rights to another. For more information, see DevTest Process Relationships.
      When using external databases, each Registry, Enterprise Dashboard, and Identity and Access Manager requires a separate database. Pointing all three components to the same database results in schema errors. For more information, see the Database Requirements section of System Requirements.
    The Identity and Access Manager Configure Database step opens.
  9. Select the type of database you want to use for your user management.
    • If you select the default value,
      Embedded Database
      , no additional configuration is required.
    • If you select another option, enter the details for your database and click
      Validate
      .
    Using the embedded database is not recommended as an enterprise solution. This database is not intended for use in a production environment.
  10. Click
    Next
    .
    The Enterprise Dashboard step opens.
  11. Specify one of the following options:
    • Install New Enterprise Dashboard Server
      If this is the first Server you are installing, select one of the following options:
      • Broadcom Subscription Portfolio License Agreement
        .
        Select this option if you are using a Broadcom PLA.
      • Use license file
        Select this option if you are using a standard license file.
        Click
        Browse
        , navigate to the location of your license file,
        devtestlic.xml
        . The installer copies the
        devtestlic.xml
        file to the specified installation directory (LISA_HOME) on the local host. The new Enterprise Dashboard process is installed in the LISA_HOME\bin directory. This option specifies that all registries are to connect to the new Enterprise Dashboard.
        To upgrade from DevTest 10.3 or earlier, you must request a new license file. For more information, see License Administration
    • Existing Enterprise Dashboard Server
      If this is not the first Server that is installed in this network, enter the location of the existing Enterprise Dashboard. This option specifies that the registry installed with this Server is to connect to the existing Enterprise Dashboard.
      localhost:1506
      To find the URL for an existing Enterprise Dashboard, navigate to the
      DevTest
      home directory and locate the
      site.properties
      file. The
      devtest.enterprisedashboard.host
      and
      devtest.enterprisedashboard.port
      properties define the Enterprise Dashboard location.
  12. Click
    Next
    .
    If you selected
    Broadcom Subscription Portfolio License Agreement
    , the Activate Your Product step opens. If you did not select this option, skip to Step 14.
  13. Activate your product:
    1. Enter the Company Domain and Enterprise Site ID for your Product License Agreement.
    2. Optionally, enter an internal identifier if you want to assign an identifier for your own tracking purposes.
    3. Select whether you want to use a proxy to send usage data.
      • Sending usage data telemetry is required for a Portfolio License Agreement.
      • Port 443 is used by default for sending usage data. If that port is unavailable, enter a Proxy URI and the associated user name and password.
      • For more information about the usage data that is collected, see Telemetry.
    4. Click
      Next
      .
    The Demo Server step opens.
  14. If you want the installer to unzip the DevTestDemoServer.zip into the LISA_HOME directory, select the
    Install demo server
    option. Then, accept the default path (the Downloads directory) or specify another fully qualified path.
    In a distributed system where Workstations are installed on user computers, the demo server is typically installed with the Workstations for new users; not with the Server.
  15. Click
    Next
    .
    The Select Start Menu Folder step opens.
  16. (Optional) Specify whether the
    DevTest Solutions
    processes can be started from the Start menu. (You can start the executable for each process manually from the bin directory under the installation directory.) The advantage of starting the executables, as opposed to the associated services, is that you can monitor messages that are displayed in the command-line interface (CLI).
    • To create a Start menu folder with shortcuts for all users, accept all defaults. Optionally, enter a new folder name.
    • To have no Start menu folder, clear the
      Create a Start Menu folder
      check box. To create a Start menu folder and restrict the shortcut display to your Start menu:
      • Accept the selection of
        Create a Start Menu folder
        .
      • Accept the default name or enter another name.
      • Clear the
        Create shortcuts for all users
        check box.
  17. Click
    Next
    .
    The Desktop Icons step opens.
  18. (Optional) If you do not want to create desktop icons for
    DevTest
    Enterprise Dashboard UI,
    DevTest
    Portal UI, and
    DevTest
    Workstation, clear the check box.
  19. Click
    Next
    .
    The Windows Services step opens.
  20. (Optional) Select
    Install Services
    to create the following Windows services.
    • DevTest
      Broker Service (for
      Application Insight
      )
    • DevTest
      Coordinator Service
    • DevTest
      Enterprise Dashboard Service
    • DevTest
      Identity and Access Manager Service
    • DevTest
      Portal Service
    • DevTest
      Registry Service
    • DevTest
      Simulator Service
    • DevTest
      VSE Service
    This selection adds the services to Administrative Tools, Component Services, Services. The advantage to starting services as opposed to the associated executables is that you reduce the number of icons that are displayed on the system tray. If you want the Startup type to be defined as Automatic so that the services start when the host computer is restarted, select the
    Start on bootup
    check box. You can configure Automatic startup within Services, if you do not select this check box here.
    The services on Windows run under a specific user account, click
    Optional Service Account
    . To have the services run under the system account, select
    System Account
    . To have the services run under another account,enter the account name and password in the
    Account Name
    and
    Account Password
    fields.
  21. Click
    Next
    .
    The Select File Associations step opens. All associations are selected by default.
  22. Leave all associations selected or clear the file extensions that you do not want to associate with
    DevTest Solutions
    .
  23. Click
    Install
    to start the installation.
    The Installing step opens. When the installation finishes, the Information step opens.
  24. Read the information and click
    Next
    .
  25. The Completing the
    DevTest Solutions
    Setup Wizard step opens.
  26. Click
    Finish
    .
Install DevTest Server on UNIX

Before you start the installation procedure, download the following files from the Download Center:
  • The installer for your platform
  • (Optional) The demo server zip file
    Typically, the Demo Server is installed with the Server components only in a standalone system. In a distributed system, the Demo Server is usually installed with DevTest Workstation for users who are new to DevTest Solutions.
The following procedure is based on the graphical version of the installer. To use the command-line version of the installer, add the
-c
option. For example:
./devtest_linux_x64.sh -c
If a graphical front end is not available on your computer, you must use the command-line version.
If you downloaded the generic UNIX installer, ensure that a Java virtual machine (JVM) is on the same computer. If the installer cannot find a JVM, the installer displays a message and exits. For more information, see the section on supplying your own JVM in System Requirements.
Follow these steps:
  1. In a terminal window, navigate to the directory where the installer file is located.
  2. Ensure that the installer file has the execute permission. For example:
    chmod 777 devtest_linux_x64.sh
    This command gives the read, write, and execute permissions to each class of user.
  3. Run the installer file. For example:
    ./devtest_linux_x64.sh
    On Ubuntu systems, if you install as root user, you can not display DevTest icons on the desktop.
    The Welcome to the
    DevTest Solutions
    Setup Wizard opens.
  4. Click
    Next
    .
    The End User License Agreement step opens.
  5. Read the license agreement, scrolling to the end, select the
    I accept the terms of the License Agreement
    option, and click
    Next
    .
    The Select Components step opens.
  6. Ensure that the
    Server
    check box is selected; an embedded Workstation is installed with the Server. Click
    Next
    .
    The Select Destination Directory step opens.
  7. Specify the directory where you want to install
    DevTest Solutions
    , for example,
    /opt/CA/DevTest
    . Do not use a path with a directory name that contains spaces.
    • For more information about selecting the appropriate destination and data directory, see Installation Options.
  8. If you are upgrading from a shared install, enter the path and folder name for the data directory.
    • If you are not upgrading from a shared install, this option does not appear.
    • Enter the path and folder name for the data directory. The default data directory is the same as the installation folder.
    • The specified data directory must exist and the user must have write permissions to it. If it does not exist, the installer will create it and will test to be sure it is writable.
    • If the data directory is different than the installation directory, then
      DevTest
      will create a lisa.user.properties file in both the installation directory and in the user's home folder. The
      lisa.data.dir
      property in this property file tells the product where the data directory is located.
    • The data directory will include hotdeploy for server components. Other server component files will be in the installation directory.
  9. Click
    Next
    .
    The Identity and Access Manager step opens. Identity and Access Manager is required for a
    DevTest
    Solutions installation.
  10. Select one of the following options and click
    Next
    .
    • Install or upgrade Identity and Access Manager
      If this is the first time you are installing IAM, or if you want to upgrade your existing IAM, select this option.
    • Connect to an existing Identity and Access Manager
      If you want to connect to an existing IAM in your environment, select this option. Enter the URL for the existing IAM. This URL is the host and port where Identity and Access Manager was installed. Clicking
      Validate
      verifies that you have entered a valid URL, but does not attempt to connect to IAM.
      A single Identity and Access Manager instance for your entire enterprise allows component access to be managed in a single location. However, if you have multiple registries and need to manage access to each registry separately, you need to install a separate IAM for each registry. This is especially true if users from one registry cannot have rights to another. For more information, see DevTest Process Relationships.
      When using external databases, each Registry, Enterprise Dashboard, and Identity and Access Manager requires a separate database. Pointing all three components to the same database results in schema errors. For more information, see the Database Requirements section of System Requirements.
    The Identity and Access Manager Configure Database step opens.
  11. Select the type of database you want to use for your user management.
    • If you select the default value,
      Embedded Database
      , no additional configuration is required.
    • If you select another option, enter the details for your database and click
      Validate
      .
    Using the embedded database is not recommended as an enterprise solution. This database is not intended for use in a production environment.
  12. Click
    Next
    .
    The Enterprise Dashboard step opens.
  13. Specify one of the following options:
    • Install New Enterprise Dashboard Server
      If this is the first Server you are installing, select one of the following options:
      • Broadcom Subscription Portfolio License Agreement
        .
        Select this option if you are using a Broadcom PLA.
      • Use license file
        Select this option if you are using a standard license file.
        Click
        Browse
        , navigate to the location of your license file,
        devtestlic.xml
        . The installer copies the
        devtestlic.xml
        file to the specified installation directory (LISA_HOME) on the local host. The new Enterprise Dashboard process is installed in the LISA_HOME\bin directory. This option specifies that all registries are to connect to the new Enterprise Dashboard.
        To upgrade from DevTest 10.3 or earlier, you must request a new license file. For more information, see License Administration
    • Existing Enterprise Dashboard Server
      If this is not the first Server that is installed in this network, enter the location of the existing Enterprise Dashboard. This option specifies that the registry installed with this Server is to connect to the existing Enterprise Dashboard.
      localhost:1506
      To find the URL for an existing Enterprise Dashboard, navigate to the
      DevTest
      home directory and locate the
      site.properties
      file. The
      devtest.enterprisedashboard.host
      and
      devtest.enterprisedashboard.port
      properties define the Enterprise Dashboard location.
  14. Click
    Next
    .
    If you selected
    Broadcom Subscription Portfolio License Agreement
    , the Activate Your Product step opens. If you did not select this option, skip to Step 16.
  15. Activate your product:
    1. Enter the Company Domain and Enterprise Site ID for your Product License Agreement.
    2. Optionally, enter an internal identifier if you want to assign an identifier for your own tracking purposes.
    3. Select whether you want to use a proxy to send usage data.
      • Sending usage data telemetry is required for a Portfolio License Agreement.
      • Port 443 is used by default for sending usage data. If that port is unavailable, enter a Proxy URI and the associated user name and password.
      • For more information about the usage data that is collected, see Telemetry.
    4. Click
      Next
      .
    The Demo Server step opens.
  16. If you want the installer to unzip the demo server into the same directory where you are installing the
    DevTest Server
    , select the
    Install demo server
    check box and browse to the DevTestDemoServer.zip file.
  17. Click
    Next
    .
    The Select Directory for Symlinks step opens.
  18. Click
    Browse
    and navigate to the directory where
    DevTest
    creates symbolic links to the executable files. The default is
    /usr/local/bin
    . You must have the required permissions to write to the directory. If you do not want symbolic links to be created, clear the
    Create symlinks
    check box.
  19. Click
    Next
    .
    The Desktop Icons step opens.
  20. (Optional) If you do not want to create desktop icons for
    DevTest Workstation
    ,
    DevTest
    Portal, and Enterprise Dashboard, clear the check box.
  21. Click
    Install
    to start the installation.
    The Installing step opens. When the installation finishes, the Information step opens.
  22. Read the information and click
    Next
    .
    The Completing the
    DevTest Solutions
    Setup Wizard step opens.
  23. Click
    Finish
    .
Install DevTest Server on OS X
Before you start the installation procedure, download the following files from the Download Center:
  • The installer for your platform
  • (Optional) The demo server zip file
    Typically, the Demo Server is installed with the Server components only in a standalone system. In a distributed system, the Demo Server is usually installed with
    DevTest Workstation
    for users who are new to
    DevTest Solutions
    . The Demo Server is used for tutorials.
Follow these steps:
  1. Run the installer file, for example, devtest_osx_x64.dmg.
    The Welcome to the
    DevTest Solutions
    Setup Wizard step opens.
  2. Click
    Next
    .
    The End User License Agreement step opens.
  3. Read the license agreement, scrolling to the end, select the
    I accept the terms of the License Agreement
    option, and click
    Next
    .
    The Select Components step opens.
  4. Ensure that the
    Server
    check box is selected; an embedded Workstation is installed with the Server. Click
    Next
    .
    The Select Destination Directory step opens.
  5. Specify the folder where you want to install one or more components of the
    DevTest Solutions
    . If you specify a folder that does not exist, the Setup wizard creates it.
    • For more information about selecting the appropriate destination and data directory, see Installation Options.
  6. If you are upgrading from a shared install, enter the path and folder name for the data directory.
    • If you are not upgrading from a shared install, this option does not appear.
    • Enter the path and folder name for the data directory. The default data directory is the same as the installation folder.
    • The specified data directory must exist and the user must have write permissions to it. If it does not exist, the installer will create it and will test to be sure it is writable.
    • If the data directory is different than the installation directory, then
      DevTest
      will create a lisa.user.properties file in both the installation directory and in the user's home folder. The
      lisa.data.dir
      property in this property file tells the product where the data directory is located.
    • The data directory will include hotdeploy for server components. Other server component files will be in the installation directory.
  7. Click
    Next
    .
    The Identity and Access Manager step opens. Identity and Access Manager is required for a
    DevTest
    Solutions installation.
  8. Select one of the following options and click
    Next
    .
    • Install or upgrade Identity and Access Manager
      If this is the first time you are installing IAM, or if you want to upgrade your existing IAM, select this option.
    • Connect to an existing Identity and Access Manager
      If you want to connect to an existing IAM in your environment, select this option. Enter the URL for the existing IAM. This URL is the host and port where Identity and Access Manager was installed. Clicking
      Validate
      verifies that you have entered a valid URL, but does not attempt to connect to IAM.
      A single Identity and Access Manager instance for your entire enterprise allows component access to be managed in a single location. However, if you have multiple registries and need to manage access to each registry separately, you need to install a separate IAM for each registry. This is especially true if users from one registry cannot have rights to another. For more information, see DevTest Process Relationships.
      When using external databases, each Registry, Enterprise Dashboard, and Identity and Access Manager requires a separate database. Pointing all three components to the same database results in schema errors. For more information, see the Database Requirements section of System Requirements.
    The Identity and Access Manager Configure Database step opens.
  9. Select the type of database you want to use for your user management.
    • If you select the default value,
      Embedded Database
      , no additional configuration is required.
    • If you select another option, enter the details for your database and click
      Validate
      .
    Using the embedded database is not recommended as an enterprise solution. This database is not intended for use in a production environment.
  10. Click
    Next
    .
    The Enterprise Dashboard step opens.
  11. Specify one of the following options:
    • Install New Enterprise Dashboard Server
      If this is the first Server you are installing, select one of the following options:
      • Broadcom Subscription Portfolio License Agreement
        .
        Select this option if you are using a Broadcom PLA.
      • Use license file
        Select this option if you are using a standard license file.
        Click
        Browse
        , navigate to the location of your license file,
        devtestlic.xml
        . The installer copies the
        devtestlic.xml
        file to the specified installation directory (LISA_HOME) on the local host. The new Enterprise Dashboard process is installed in the LISA_HOME\bin directory. This option specifies that all registries are to connect to the new Enterprise Dashboard.
        To upgrade from DevTest 10.3 or earlier, you must request a new license file. For more information, see License Administration
    • Existing Enterprise Dashboard Server
      If this is not the first Server that is installed in this network, enter the location of the existing Enterprise Dashboard. This option specifies that the registry installed with this Server is to connect to the existing Enterprise Dashboard.
      localhost:1506
      To find the URL for an existing Enterprise Dashboard, navigate to the
      DevTest
      home directory and locate the
      site.properties
      file. The
      devtest.enterprisedashboard.host
      and
      devtest.enterprisedashboard.port
      properties define the Enterprise Dashboard location.
  12. Click
    Next
    .
    If you selected
    Broadcom Subscription Portfolio License Agreement
    , the Activate Your Product step opens. If you did not select this option, skip to Step 14.
  13. Activate your product:
    1. Enter the Company Domain and Enterprise Site ID for your Product License Agreement.
    2. Optionally, enter an internal identifier if you want to assign an identifier for your own tracking purposes.
    3. Select whether you want to use a proxy to send usage data.
      • Sending usage data telemetry is required for a Portfolio License Agreement.
      • Port 443 is used by default for sending usage data. If that port is unavailable, enter a Proxy URI and the associated user name and password.
      • For more information about the usage data that is collected, see Telemetry.
    4. Click
      Next
      .
    The Demo Server step opens.
  14. If you want the installer to unzip the demo server into the LISA_HOME directory, select the
    Install demo server
    option. Then, accept the default path (the Downloads directory) or specify another fully qualified path.
    In a distributed system where Workstations are installed on user computers, the demo server is typically installed with the Workstations for new users; not with the Server.
  15. Click
    Next
    .
    The Desktop Icons step opens.
  16. (Optional) If you do not want to create desktop icons for
    DevTest
    Enterprise Dashboard,
    DevTest
    Portal UI, and
    DevTest
    Workstation, clear the check box. Click
    Next
    .
  17. Click
    Install
    to start the installation.
    The Installing step opens. When the installation finishes, the Information step opens.
  18. Read the information and click
    Next
    .
    The Completing the
    DevTest Solutions
    Setup Wizard step opens.
  19. Click
    Finish
    .