Configuring the security settings after installation by updating the security.config file

When you configure Rational® Test Control Panel in GUI mode, the security settings are saved to the security.config file in the security folder in the Rational® Test Control Panel workspace. To add or modify the security settings after installing the server in GUI mode or in console mode, use these instructions.

Copying security settings from another installation after installing in console mode

Procedure

  1. Install the server in GUI mode on another computer. For instructions, see Installation of Rational Test Control Panel.
  2. Go to the security folder in the Rational® Test Control Panel workspace and copy the security.config file.
    • On Windows systems, the folder is typically at C:\IBM\RTCP-Workspace\security.
    • On Unix-like systems, the folder is typically at /var/rtcp/security.
  3. Install the server in console mode on the target computer and configure it with the built-in security. For instructions, see Installing the software in console mode.
  4. Stop the server, if it is running.
    • On Windows systems, stop the IBM RTCP service.
    • On Unix-like systems, run the stop script. For assistance, contact your system administrator.
  5. Paste the security.config file you copied in Step 2 into the Rational® Test Control Panel workspace on the target computer.
  6. Edit the security.config file as necessary. For information about various properties associated with Active Directory and LDAP configuration, see Configuring the Active Directory settings and Configuring the Lightweight Directory Access Protocol (LDAP) settings.
  7. For the changes to take effect, start Rational® Test Control Panel and test your login credentials by using a web browser.

Modifying security settings manually after installing in GUI mode or console mode

Before you begin

Rational® Test Control Panel must be installed on the target computer.

About this task

When you install the server in console mode, you can configure it with the built-in security only. To configure the server to use Active Directory or LDAP, you need to manually edit the security.config file. For information about how to install the server in console mode, see Installing the software in console mode.

When you install in GUI mode, you can configure Active Directory or LDAP authentication during the installation. To make changes to the security configuration after installation, you can either use the Modify option in the IBM® Installation Manager GUI or edit the security.config file.

Procedure

  1. Stop the server, if it is running.
    • On Windows systems, stop the IBM RTCP service.
    • On Unix-like systems, run the stop script. For assistance, contact your system administrator.
  2. Go to the security folder in the server workspace.
    • On Windows systems, the folder is typically at C:\IBM\RTCP-Workspace\security.
    • On Unix-like systems, the folder is typically at /var/rtcp/security.
  3. Update the security.config file with Active Directory or Local Directory Access Protocol (LDAP) settings as necessary. For information about various properties associated with Active Directory and LDAP configuration, see Configuring the Active Directory settings and Configuring the Lightweight Directory Access Protocol (LDAP) settings.
  4. Run EncryptPassword.exe available at either of the following locations to encode your administrator password:
    • Rational® Integration Tester installation folder (C:\Program Files\IBM\RIT-Agent\ in Windows and /opt/IBM\RIT-Agent/ in Linux)
    • Rational® Integration Tester Agent installation folder (C:\Program Files\IBM\RIT-Agent\ in Windows and /opt/IBM/RIT-Agent/ in Linux).
    For example:
    EncryptPassword.exe myPassword 
    #com.ghc.1!b2b312954AC84469E34BA2E5
    Escape the special characters using the \ character as shown in the following example:
    \#com.ghc.1\!b2b312954AC84469E34BA2E5
    Update the adminpassword property in the security.config file with the resulting value.
  5. For the changes to take effect, start the server and test your login credentials by using a web browser.