Completing the installation

After the server is installed, you must consider some configuration options before continuing.

• Some files contain passwords. Those files should be protected so that they are readable only by users authorized to know the password for the accounts.
  • teamserver.properties - The Jazz® Team Server, CCM, RM, and QM applications require that the database password is stored in JazzInstallDir/server/conf/application/teamserver.properties. When properties files are saved, the application always makes a backup copy of the previous version in the same directory. If you want to remove all files that contain the clear-text password, remove the backup properties files after configuring the server for the first time.
  • The ClearCase Synchronizer sync engine requires that user passwords be stored in an properties file.
  • cqconnector.properties - The ClearQuest® Synchronizer requires that both ClearQuest user IDs and passwords be stored in a properties file.
• When connecting to Jazz Team Server you might see security certificate warnings. To disable the warning, see Configuring security certificates.
• Optionally, make the login case-insensitive for interoperability between UNIX systems and Windows. On UNIX systems, the native file system is case-sensitive while on Windows computers the native file system is case-insensitive. The default setting for user ID in Jazz Team Server is case-sensitive. To change the default setting to case-insensitive, follow these steps:
  1. Login to Jazz Team Server administrative web interface as an administrator.
  2. Under Configurations, click Advanced Properties.
  3. In the Advanced Properties page, search for Use case insensitive user ID matching.
  4. Click Edit and under Current® Value, select true.

  Note: For IBM® i, using the case-insensitive option allows user IDs to be lowercase instead of uppercase only.
• The creation of the warehouse on Oracle requires more permissions as compared to other databases. When you specify the database user in the connection spec for data warehouse, ensure that the database user has DBA permissions.

  GRANT DBA TO data warehouse user

  If this type of permission is a concern, after the data warehouse is created, you may change the user in the connection spec, using the Reports Admin Web UI. You need to change this value in the JTS, CCM, RM, and QM applications. To create the new user with less permissions for running data collection (ETL) jobs, open a SQL *Plus window and run the following commands:

  CREATE USER <etl db user> PROFILE DEFAULT 
  IDENTIFIED BY <password> DEFAULT TABLESPACE USERS
  ACCOUNT UNLOCK;
  
  ALTER USER <etl db user> TEMPORARY TABLESPACE RIS_TEMP;
  ALTER USER <etl db user> QUOTA UNLIMITED ON VNF_32K;
  ALTER USER <etl db user> QUOTA UNLIMITED ON VNF_IDX;
  ALTER USER <etl db user> QUOTA UNLIMITED ON USERS;
  ALTER USER <etl db user> QUOTA UNLIMITED ON VSTR_32K;
  ALTER USER <etl db user> QUOTA UNLIMITED ON VSTR_IDX;
  
  GRANT CREATE SESSION TO <etl db user>;
  GRANT CONNECT TO <etl db user>;
  GRANT ANALYZE ANY TO <etl db user>;
  
  BEGIN
  FOR TABNAME IN (SELECT OWNER,TABLE_NAME FROM ALL_TABLES WHERE OWNER IN ('RIODS','RIDW','CONFIG','RIASSET','RISCHK','RICALM'))
  LOOP
  EXECUTE IMMEDIATE 'GRANT SELECT,UPDATE,DELETE,INSERT ON ' || TABNAME.OWNER || '."' || TABNAME.TABLE_NAME || '" TO <etl db user>';
  END LOOP;
  END;
  /
  
  BEGIN
  FOR VNAME IN (SELECT OWNER,VIEW_NAME FROM ALL_VIEWS WHERE OWNER IN ('RIDW','RICALM')) 
  LOOP    
  EXECUTE IMMEDIATE 'GRANT SELECT ON ' || VNAME.OWNER || '."' || VNAME.VIEW_NAME || '" TO <etl db user>';
  END LOOP;
  END;
  /

  For more information about Oracle data warehouse setup, see this wiki.