Setting up authentication

About this task

Two types of authentication are allowed: external or database. You must choose one, as mixed mode authentication is not supported.

External authentication

Procedure

  1. Create User OPS$CCM_ROOT

    You must create user OPS$CCM_ROOT in your Oracle database in order for Rational Synergy to run. Use the following SQL statement as an example:

                      create user OPS$CCM_ROOT identified externally
                      default table space ccm
                      temporary table space temp
                      quota unlimited on ccm;
  2. Grant Privileges to User OPS$CCM_ROOT

    After creating user OPS$CCM_ROOT, grant the "CREATE SESSION" and "SELECT_CATALOG_ROLE" privileges to user OPS$CCM_ROOT as follows:

                   grant CREATE SESSION, SELECT_CATALOG_ROLE to OPS$CCM_ROOT;

Setting up remote authentication (optional)

About this task

If you plan to run on remote engines, you must enable remote authentication. You must set the initialization parameter as follows.

  • Set REMOTE_OS_AUTHENT to TRUE
  • Set REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE
  • Set OS_AUTHENT_PREFIX to OPS$

Database authentication

About this task

For database authentication, you must also set the following parameters:

Procedure

  1. Create user CCM_ROOT

    You must create user CCM_ROOT in your Oracle database in order for Rational Synergy to run. Use the following SQL statement as an example:

                   create user CCM_ROOT identified by ccm_root
                   default table space ccm
                   temporary table space temp
                   quota unlimited on ccm;
  2. Grant privileges to user CCM_ROOT

    After creating user CCM_ROOT, grant the "CREATE SESSION" and "SELECT_CATALOG_ROLE" privileges to user CCM_ROOT as follows:

                   grant CREATE SESSION, SELECT_CATALOG_ROLE to CCM_ROOT;
  3. Make sure ccmdb auth -d is run after the installation is completed to set the password of the Oracle database user CCM_ROOT.

Potential data loss when Rational Synergy and Oracle database use different character encoding

About this task

If any Rational Synergy client does not use the same character encoding schemes as the underlying Oracle database, certain characters entered into the client can be replaced when they are saved to Oracle, resulting in data loss.

For example, assume:

  • A user configures an Oracle database to use the 7-bit ASCII character set (US7ASCII).
  • A Rational Synergy client runs on a German operating system that uses the 8-bit ISO character set (WE8ISO8859P1).
  • A user enters a German character in the Rational Synergy client that is not part of the 7-bit ASCII character set.

The German character is converted as it is saved to the database. Different characters are converted in different ways; for example, the character "ß" is replaced with "?," and the character "ä" is replaced with "a."

To avoid data loss, configure the Oracle database so that its character set is a superset of, or equivalent to, the character sets on all systems that run Rational Synergy clients. For example, if German data is expected to be stored in Rational Synergy, configure the Oracle database and the client systems to use a character set that supports German characters.


Feedback