Audit Trails > Setting Up Database Connections > Using a Parameter File
  
Using a Parameter File
Depending on your environment, your parameter files may differ from these general guidelines.
The following guidelines apply to parameter files used to connect to a Progress database or Progress schema holder for an Oracle database:
• Specify the parameter file name in Parameter File.
• Specify connection parameters in the parameter file or in the corresponding fields. Do not include the parameters in both the file and in the corresponding fields.
• The parameter file must be accessible through the PROPATH or located in the directory specified in Database Directory.
• If you use a parameter file, you must still specify the database name in the Audit DB Maintenance screen. If the database is not located in the PROPATH, you must also specify the full path in Database Directory.
• The parameter file should not include either the -ld or -db parameters.
• The parameter file must include the -trig parameter that specifies the location of trigger files.
For Oracle audit databases, you specify the schema holder name in Physical Database Name and set Type to Oracle. The parameter file must include the parameters for the schema holder followed by parameters for connecting to the Oracle database, in this order:
• -trig parameter
• Other connection parameters for the schema holder
• -db parameter for the Oracle database
• The Oracle database connection parameters, including the -dt ORACLE parameter and the -ld parameter, if needed
Sample Parameter Files and Audit DB Maintenance Settings shows several sample database connection settings and corresponding parameter files.

Sample Parameter Files and Audit DB Maintenance Settings
 
Database Type
Audit DB Maintenance Settings
Parameter File Values
Progress
Physical Database Name: auditdb1
Database Directory: /qad/mfgpro/db
Host: mainserver
Server: audit1-service
Type: Progress
Network: TCP
Parameter File: example1.pf
-trig “triggers”
Progress
Physical Database Name: auditdb1
Database Directory: /qad/mfgpro/db
Host:
Server:
Type: Progress
Network: TCP
Parameter File: example2.pf
-trig “triggers”
-H mainserver
-S audit1-service
Oracle
Physical Database Name: audit
Database Directory: /qad/mfgpro/db
Host: mainserver
Server: otest3-service
Type: ORACLE
Network: TCP
Parameter File: example3.pf
-trig “triggers” -znotrim
-db otest3
-dt ORACLE
-U qad@otest3
-P QAD
Oracle
Physical Database Name: audit
Database Directory: /qad/mfgpro/db
Host:
Server:
Type:
Network: TCP
Parameter File: example4.pf
-trig “triggers” -znotrim
-H mainserver
-S audit1sh-service
-db otest3
-dt ORACLE
-U qad@otest3
-P QAD