Application parameters:

app.runStartUp

Indicates whether TeamConnect is set to execute start up code.

Enter YES to run start up code defined in TeamConnect's Documents area in the /Root/ System/StartUp folder.

Enter NO to disable the start up code. The default value is YES.

YES or NO

app.runStartUp.failOnError

Indicates whether TeamConnect will continue to execute start up code if it encounters an error or exception.

Enter YES to stop the execution of the rest of the class files on error or exception.

Enter NO to continue onto the next class file. The default value is NO.

YES or NO

app.logFolder

The directory where TeamConnect stores log files. Logging can be configured through System Logging on the Admin tab, Logging sub-tab, in the TeamConnect user interface.

Tip: If you are running multiple instances of TeamConnect on a single application server (for example, in a development environment), set different log folders for each of them so that you can more easily distinguish between the logs.

Default value is ./logs.

./TeamConnect/logs(use backslashes for Windows)

app.dontUseSecurityViews

This parameter influences how object security is checked when a search is executed. A value of NO means that object security is checked at the database level, using database views introduced in version 3.3. This approach reduces network traffic between application server and database server.

A value of YES means that security-related database views are ignored and security checking takes place in the application's memory space. This is the better choice if your database server is not powerful, and if you have resources available on your application server. If you are encountering performance issues when using the security views, change this property to YES.

NO (default)

app.preLoadStores

This parameter influences how static resources are fetched into application memory. A value of YES causes all resources to be fetched at startup. This slows the startup process, but improves response time for all subsequent processes during the application session. A value of NO causes resources to be loaded only when required for the current process, which speeds startup but causes all other processes to run more slowly.

YES (default)

app.expiresHeader.timeInM inutes

Determines how long, in minutes, static resources may persist in cache before they are explicitly refreshed.

360 (default)

db.product

The database being used to store TeamConnect data.

Enter the appropriate software name.

Oracle or SQLServer

url.adminHelp

Specifies the TeamConnect online Designer help location.

http://<hostname>/TeamConnectHelp/ DesignerHelp/tc_designer_help.html

(where <hostname> can be web application server name or IP address and might include port number).

See under Description

url.userHelp

Specifies the TeamConnect online user help location.

http://<hostname>/TeamConnectHelp/user/ tc_user_help.html

(where <hostname> can be web application server name or IP address and might include port number).

See under Description

javax.xml.soap.MessageFactory

Specifies the SOAP messaging implementation that will be used. This is required for using Web Services on WebLogic and WebSphere servers, and overrides the default SOAP implementation that those servers use. This parameter is ignored for Tomcat servers. The parameter has the following default value:

com.sun.xml.internal.messaging.saaj.so ap.ver1_1.SOAPMessageFactory1_1Impl

If you have a version of Weblogic earlier than 10.3.6, use the following argument:

com.sun.xml.messaging.saaj.soap.ver1_1.

SOAPMessageFactory1_1Impl

url.userHelp

jmonitor.configuration.file

Specifies the location of the file that contains configuration information for the Performance

See under Description

Monitor (see Performance Monitor). If you do not specify a location, the file will reside in the same folder as the Java Virtual Machine that is being used by TeamConnect. In environments with multiple TeamConnect installations, you should override the default with a location that is specific to the current TeamConnect installation.

url.userHelp

EclipseLink parameters:

eclipselink.sequencePreallocationSize

The EclipseLink primary key sequence pre- allocation size. This value should not be changed.

500

eclipselink.minConnections

The minimum number of connections the EclipseLink connection pool is initialized with.

30

eclipselink.maxConnection s

The maximum number of connections the EclipseLink connection pool can grow to.

30

eclipselink.minReadConne ctions

The minimum number of connections the EclipseLink READ connection pool is initialized with.

30

eclipselink.maxReadConne ctions

The maximum number of connections the EclipseLink READ connection pool can grow to.

30

eclipselink.bindParameters (Optional)

Whether to use bind variables in database queries. Affects performance. Default behavior is as shown in Suggested Values.

YES (for Oracle) or NO (for SQL Server)

Parameters for directdatabase connection (Only for Tomcat deployments):

db.username

The username that TeamConnect should use to access the database.

db.password

The password that TeamConnect should use to access the database.

Important: This password is encrypted automatically when the Installer runs. Future changes to the password must be manually encrypted using the encryption tool provided by Mitratech. For more details, see Encryption Tool.

db.databaseName

(SQL Server only)

The name of the database.

db.server

For SQL Server—Specify only the hostname and port number of your database, separated by colons.

For Oracle Thin connection—Specify the hostname, port number, and the SID of your database, separated by colons.

Data source parameters:

app.useDataSource

Enter YES to use a data source (defined in the application server) as the database connection mechanism. If set to YES, all EclipseLink connection pool and WebLogic connection pool parameters are ignored.

Enter NO to use a EclipseLink connection pool or a WebLogic connection pool. By default, the value is YES.

YES or NO

appserver.datasourceName

The name of the data source to use, if app.useDataSource is set to YES.

If you do not provide a data source name, the name defaults to TeamConnect.

Data Warehouse parameters:

dwh.db.product

The database being used to store Data Warehouse data.

Enter the appropriate software name.

Oracle or

SQLServer

dwh.useDataSource

Enter YES to use a data source (defined in the application server) as the database connection mechanism. If set to YES, all EclipseLink connection pool and WebLogic connection pool parameters are ignored.

Enter NO to use a EclipseLink connection pool or a WebLogic connection pool. By default, the value is NO.

YES or NO

dwh.datasourceName

The name of the data source to use, if dwh.useDataSource is set to YES.

If you do not provide a data source name, the name defaults to TeamConnect.

dwh.db.username

The username that TeamConnect should use to access the Data Warehouse database.

dwh.db.password

The password that TeamConnect should use to access the Data Warehouse database.

Important: This password is encrypted automatically when the Installer runs. Future changes to the password must be manually encrypted using the encryption tool provided by Mitratech. For more details, see Encryption Tool.

dwh.db.databaseName

(SQL Server only) The name of the database.

dwh.db.server

The location of the database, in format hostname:port:SID.

Global search parameters:

globalSearchMenu.doNotS how

This property can be used to suppress the display of certain options in Global Search.

If you do not want the "All" option to appear in the dropdown list of Global Search, enter the following property and value:

globalSearchMenu.doNotShow=All

If you want neither the "All" option nor the "All Projects" option to appear in the dropdown list of Global Search, enter the following property and value:

globalSearchMenu.doNotShow=AllAndAllPr ojects

Security enhancement parameters:

app.disableSpringSecurityL ogging

Indicates whether the spring security logger assumes the TeamConnect logging levels. By default, this parameter is not in the .properties file and is automatically set to false, which means that the spring security logger does not use the logging levels. If the logger levels are set to debug and you want the spring security logger to include debug messages, add this parameter to the file and set it to true.

Note: If this parameter is set to true, the spring logger may log sensitive information, such a CSRF token and session IDs.

Indicates whether the spring security logger assumes the TeamConnect logging levels. By default, this parameter is not in the .properties file and is automatically set to false, which means that the spring security logger does not use the logging levels. If the logger levels are set to debug and you want the spring security logger to include debug messages, add this parameter to the file and set it to true.

Note: If this parameter is set to true, the spring logger may log sensitive information, such a CSRF token and session IDs.

app.setupAccessPort

Allows you to specify a valid port number that gives users access to the TeamConnect setup. Even if the user has the correct TeamConnect security rights and permissions, TeamConnect blocks users without this port from accessing the setup. From your web server, you can also specify the same port to block external traffic.

encryption.iterations

Specifies the number of iterations that TeamConnect runs the password encryption algorithm. The default is 10000.

encryption.algorithm

It determines the algorithm in use. Enter any of these valid values: SHA256, bcrypt
Note: If this not configured, then SHA256 is set for legacy compatibility.
encryption.algorithm=bcrypt

SHA256, bcrypt