Starting and stopping DevOps Test Virtualization Control Panel

You can start IBM® DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) to enable users to log in by using a web browser. If the server is installed as a service, you can configure it for automatic startup on boot or for manual startup on demand.

On Windows™ systems, the server is, by default, configured to be installed as a service, and for automatic startup on boot. If you cleared these selections during the installation, then use the Modify option of Installation Manager to update the installation. See Starting and stopping on Windows systems.

On non-Windows systems, after installation, you must manually configure the server as a service. See the following procedures for non-Windows systems:
Note: You must run commands as an Administrator from the Windows command line.

Starting and stopping on Windows systems

Start and stop the server from the Windows command line:
  • Start the server from the command line. Run the startup.bat file from the default location C:\Program Files\IBM\DevOpsTestControlPanel\bin.
  • Stop the server from the command line. Run the shutdown.bat file from the default location C:\Program Files\IBM\DevOpsTestControlPanel\bin.
Start and stop the server if the server was installed as a Windows service:
  • Start the service from the Start menu. Click Start Control Panel Application
    Note: By default, the server is configured to start automatically on boot.
  • Stop the service from the Start menu. Click Stop Control Panel Application
    Important: Do not attempt to end the processes after you initiated the stopping of Test Virtualization Control Panel. Doing so might render the stored data in the workspace to become unusable.
Modify the Windows service from automatic startup to manual startup:
  • Follow these steps to change from automatic startup to manual startup:
    1. Go to Control Panel, and select System and Security > Windows Tools > Services.
    2. Double-click DevOps Test API Control Panel.
    3. Change the Startup type from Automatic to Manual.
    4. Click OK.
      Tip: You can also use this Control Panel option to start or stop the service.

Starting and stopping on non-Windows systems

Ensure that you have root permissions.
You can use either the init shell script or the systemd script to start or stop Test Virtualization Control Panel. You can find the scripts in /opt/IBM/DevOpsTestControlPanel/bin.
Start the server on non-Windows systems. Do one of the following steps:
  • If you are using the init shell script run the startup.sh file from the default location or where you installed Test Virtualization Control Panel.
  • If you are using the systemd script, follow these steps:
    1. Install the file and set permissions:
      
      sudo cp controlpanel.service /etc/systemd/system/controlpanel.service
      sudo chmod 644 /etc/systemd/system/controlpanel.service
      
    2. Start the service:
      
      sudo systemctl start controlpanel

      For more information about systemd, see the systemd documentation.

Stop the server on non-Windows systems. Do one of the following steps:
Important: Do not attempt to end the processes after you initiated the stopping of Test Virtualization Control Panel. Doing so might render the stored data in the workspace to become unusable.
  • If you are using the init shell script, run the shutdown.sh file from the default location: /opt/IBM/DevOpsTestControlPanel/bin.
  • If you are using the systemd script, run sudo systemctl stop controlpanel.
Configure automatic start on boot on non-Windows systems. Do one of the following steps.
  • Follow these steps to configure automatic start on boot for the init shell script:
    1. Add the startup.sh script to the path /etc/init.d.
    2. Create symbolic links to the script in the run-level folders, for example, /etc/rc3.d.
      Tip: For automatic shutdown, copy the shutdown.sh script to the path /etc/init.d, and create a symbolic link in the run-level folders, for example, /etc/rc0.d.
    3. Open a command prompt and run the following command:
      
      sudo update-rc.d startup.sh defaults 
      
  • Follow these steps to configure automatic start on boot for the systemd script:
    1. Enable automatic startup:
      
      sudo systemctl enable controlpanel
      
    2. Check the status:
      
      sudo systemctl status controlpanel
      

Configuring automatic start on boot on RedHat Linux systems

Ensure that you have root permissions.

The steps for RedHat Linux systems are different from those for non-Windows systems.

  1. Add the startup.sh script to the path /etc/init.d.
  2. Create symbolic links to the script in the run-level folders, for example, /etc/rc3.d.
  3. Edit startup.sh (located at both /etc/init.d and /etc/rc3.d) by using the following command: nano startup.sh.
  4. Replace the following lines:
    #!/bin/sh 
    . /opt/IBM/DevOpsTestControlPanel/bin/setenv.sh
    with the following:
    #!/bin/sh 
    #chkconfig: 345 99 01 
    #description: startup.sh 
    . /opt/IBM/DevOpsTestControlPanel/bin/setenv.sh

    This adds startup.sh to chkconfig.

  5. Run the following command: ntsysv.

    This command runs startup.sh automatically on boot.