DevOps Test Integrations and APIs for non-administrative users

To run HCL DevOps Test Integrations and APIs (Test Integrations and APIs) as a non-administrative user, you must install the software as a non-administrative user. On Linux™ systems, if you already installed Test Integrations and APIs as a root user, you can change the ownership of the product installation directories, and then use the software as a non-root user.

You have two options to make Test Integrations and APIs available to non-administrative user profiles.

Option 1: Install the software as a non-administrative user
  1. Install Installation Manager and Test Integrations and APIs for non-administrative users.
  2. If there are multiple users, create a non-administrative user group, and assign read and write permissions to the product and log directories to the user group. For Linux systems, see Modifying the directory ownership for Linux systems
When you install these products as a non-administrative user, the installation directory is the user's home directory: on Linux systems, $HOME for that user, and on Windows systems, %UserProfile% for the user.

Option 2: (applies to Linux installations only) Install the software as a root user, and change the ownership of product directories to a non-root user

  1. Install Installation Manager as an administrative user.
  2. Install Test Integrations and APIs as an administrative user.
  3. Change the ownership of all product files and directories, including the log directories, to a non-administrative user. If there are multiple users, create a non-administrative user group, and assign read and write permissions to the product and log directories to the user group. For Linux systems, see Modifying the directory ownership for Linux systems.
Remember: If you change file or directory permissions, you must repeat the process after each product upgrade.

Installing Installation Manager and Test Integrations and APIs for non-administrative users

  1. Install Installation Manager as a non-administrative user by using the userinst program. In the following table, see the installation command to use and the default installation directories.
    Installation Manager commands and directories for administrative and non-administrative user instances
    Installation commands and directories Administrative user installation Non-administrative user installation
    Command to install Installation Manager Windows™ systems: install.exe Windows™ systems: userinst.exe

    Linux™ systems: # ./install

    Linux™ systems: # ./userinst
    Installation Manager installation directory Windows™ systems: C:\Program Files\IBM\Installation Manager Windows™ systems: %UserProfile%\IBM\InstallationManager\eclipse

    Linux™ systems: /opt/IBM/InstallationManager

    Linux™ systems: $HOME/IBM/InstallationManager/eclipse
  2. Use Installation Manager to install Test Integrations and APIs and the required components. See the following table for the default installation directory for administrative and non-administrative user installations. During the installation you can modify the default installation directories.
    Tip: For non-administrative user installations on Linux systems, it is a good practice to set the installation directory to a path that is not in the home directory of the installing user. On Windows systems, do not install to the Program Files directories.
    Table 1. Test Integrations and APIs installation directories for administrative and non-administrative user instances
    Installation directories Administrative user instance Non-administrative user instance
    Test Integrations and APIs installation directory Windows™:C:\Program Files\HCL\DevOpsTestAPI Windows™: %UserProfile%\HCL\DevOpsTestAPI
    Linux™: /opt/HCL/DevOpsTestAPI Linux™ systems: $HOME/HCL/DevOpsTestAPI
    Test Integrations and APIs Agent Windows™: C:\Program Files\HCL\DevOpsTestAPIAgent Windows™ systems: %UserProfile%\HCL\DevOpsTestAPIAgent

    Linux™: /opt/HCL/DevOpsTestAPIAgent

    		 Linux™ systems: $HOME/HCL/DevOpsTestAPIAgent
    Test Virtualization Control Panel installation directory Windows™: C:\Program Files\HCL\DevOpsTestControlPanel Windows™ systems: %UserProfile%\HCL\DevOpsTestControlPanel

    Linux™: /opt/HCL/DevOpsTestControlPanel

    		 Linux™: $HOME/HCL/DevOpsTestControlPanel
  3. During the Test Virtualization Control Panel installation, enter the path to the Test Virtualization Control Panel workspace. See the following table for examples.
    Tip: Set the Test Virtualization Control Panel workspace to a directory location to which you have write permission. Ensure that the directory path does not have any spaces.
    Table 2. Test Virtualization Control Panel workspace locations for administrative and non-administrative user instances
    Installation directories Administrative user instance Non-administrative user instance
    Test Virtualization Control Panel workspace Windows™: C:\HCL\HQS-Workspace Windows™: %UserProfile%\HCL\HQS-Workspace
    Linux™: var/hqs Linux™: $HOME/var/hqs
  4. For the technologies that you want to use for testing, configure the application settings and the libraries to include by running the Library Manager for Test Integrations and APIs and Test Integrations and APIs Agent. For more information on running the Library Manager, see Working with Library Manager. Running the Library Manager creates the librarysettings.xml file. See the following table for the file location.
    Note: In the non-administrative installation environment, Library Manager cannot access the network interface, so you cannot use the packet capture recording mode. You can only use the external proxy server recording mode.
    Table 3. Location of the librarysettings.xml file
    File File location
    Test Integrations and APIs librarysettings.xml file Windows™: %UserProfile%\.integrationtester
    Linux™: $HOME/.integrationtester
    Test Integrations and APIs Agent librarysettings.xml file Windows™: %UserProfile%\HCL\DevOpsTestAPIAgent
    Linux™: $HOME/HCL/DevOpsTestAPIAgent
You can now run Test Integrations and APIs as a non-administrative user.

What to do next

For multiple users on Linux systems, create a non-administrative user group. Assign ownership to the product and log directories to the user group. For more information about assigning directory ownership, see Modifying the directory ownership for Linux systems

Modifying the directory ownership for Linux™ systems

If you installed Installation Manager and Test Integrations and APIs as an administrative or root user on Linux™, you can modify the installation directory ownership so that non-root users can run the software.

Note: This procedure is applicable in a Linux™ environment only. A similar process is not currently identified for Windows™ installations.

Before you begin

Before you change the directory permissions, ensure that you stop all services.

About this task

This process assumes that you installed Installation Manager as a root user, and then installed Test Integrations and APIs by using Installation Manager as a root user.

  1. Change ownership of each product installation directory by running the chown command.

    The command syntax is chown -R user:group dir, where user is the name of the user to change the ownership to, group is the user group name, and dir is the directory path of the directory that you want to change the ownership of.

    For example, to change ownership of the Test Integrations and APIs to a non-root user named John, run the following command: chown -R <john:usergroup1> opt/HCL/DevOpsTestAPI. You must change the ownership for the following installation directories:
    • opt/HCL/DevOpsTestAPI
    • /opt/HCL/DevOpsTestAPIAgent
    • /opt/HCL/DevOpsTestControlPanel
    • /opt/HCL//C:\Program Files\HCL\HCLIMShared
    Note: The C:\Program Files\HCL\HCLIMShared directory is created only if this is the first use of installing a product with Installation Manager, otherwise the currently used IMShared directory is used.
  2. Run the chown command on each product log directory that is not under one of the product installation directories specified in step 1. By default, the product logs are saved to the installation directory. If the location of the log directories is not the product installation directory, you must separately change the ownership of those directories.
  3. Run the chown command on the Test Virtualization Control Panel workspace directory. The workspace directory is specified by the workingDirectory= property in the /opt/HCL/DevOpsTestControlPanel/usr/servers/defaultServer/apps/RTCP.war/WEB-INF/classes/container.server.properties file.

You can now run Test Integrations and APIs and its components on Linux™ as a non-root user.