When the Web Interface is installed, a configuration file named harweb.cfg is created in the \harweb\WEB-INF directory. The following settings can be modified:
Specifies whether to use internal (CA Harvest SCM) authentication or external authentication, such as OpenLDAP authentication.
AuthMode=internal|openldap
Sets the Web Interface authentication mode to the same value used by the Web Interface broker. You typically set the authentication mode during the Web Interface installation. If you change the authentication mode for the Web Interface broker after the Web Interface installation, change the authentication mode for the Web Interface to the same value as its broker. For example, if you change the Web Interface broker to use OpenLDAP authentication after the installation, update the harweb.cfg file to specify the setting AuthMode=openldap, which configures the Web Interface to use OpenLDAP authentication.
MixedAuthMode={1|0}
(Optional) Specifies whether the CA Harvest SCM server uses mixed-mode authentication.
1
Allows internal (CA Harvest SCM) accounts to be maintained and authenticated.
0
Specifies all accounts to be external.
Default: N
Specifies the product broker name.
Specifies the product RTServer name.
Specifies the product RTServer port.
Note: For an RTServer running on nondefault port, modify rtserverport with the appropriate port number.
An administrator should manage this directory for space considerations.
Specifies the name of the JDBC driver that the Web Interface uses to register the database driver before connecting to the product database. Use the following information to specify the JDBC driver for the DBMS.
|
DBMS |
JDBC Driver |
|---|---|
|
Oracle |
oracle.jdbc.driver.OracleDriver |
|
SQL Server |
com.microsoft.sqlserver.jdbc.SQLServerDriver |
Specifies the settings that the Web Interface uses to connect to the product database. If you change any values used in the database connection string, record the new values and edit the database connection string in the Web Interface configuration file (harweb.cfg) to specify the new values. You must specify these values to help ensure that the product and the Web Interface continue to connect to the same database.
Example: Database Connection String (Oracle)
This example illustrates the database connection string for Oracle.
JDBCConnectionURL=jdbc:oracle:thin:@[hostname]:[port-number]:[sid]
Specifies the computer name or IP address where the Oracle database is running. The Oracle hostname is not an Oracle TCP/IP service name.
Specifies the Oracle listener port number. This value is the TNS listener port number. The default is 1521 or 1526.
Identifies the database instance. The default value is ORCL.
The following is a sample Oracle database connection string.
JDBCConnectionURL=jdbc:oracle:thin:@santbarb110:1526:ORCL
Example: Database Connection String (SQL Server 2012)
This example illustrates the database connection string for SQL Server 2012 JDBC Driver.
JDBCConnectionURL= jdbc:sqlserver://[servername];instanceName=[instancename]; databaseName=[ databasename];forwardReadOnlyMethod=serverCursor
Specifies the computer name or IP address where the SQL Server database is running. The port-number is the SQL Server listener port number. The default is 1433.
Specifies the name of the SQL Server database.
(SQL Server 2012 JDBC Driver) Specifies the instance name of your SQL Server. The default instance name is literally “default” (without quotation marks). If you are using default instance, you do not need to specify the instancename in the connection string.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|