For example, if you define the Centera log file name and other logging parameters in a file named CenteraLogging.cfg, you would set the value of this property to be the fully qualified name for that file, such as C:\config\CenteraLogging.cfg, and Content Engine would then pass that file name to Centera. The information logged by Centera to your specified log file can be useful for diagnosing connectivity and performance issues between Content Engine and the Centera fixed content device.
For information on the configuration parameters, see the Centera documentation. The following are some of the parameters currently available:
- FP_LOGPATH=fully qualified log file name
- FP_LOG_STATE_POLL_INTERVAL=configuration file poll interval in minutes
- FP_LOGKEEP=[OVERWRITE|APPEND|CREATE]
- FP_LOGLEVEL=[1|2|3|4]
- FP_LOGFORMAT=[XML|TAB]
For example, a configuration file might specify these parameters and
values:
FP_LOGPATH=C:\logs\Centera.log
FP_LOG_STATE_POLL_INTERVAL=10
FP_LOGKEEP=APPEND
FP_LOGLEVEL=1
FP_LOGFORMAT=TAB
Assembly: FileNet.Api (in FileNet.Api.dll)
Syntax
Visual Basic (Declaration) |
---|
Property FPLogConfigFile As String |
C# |
---|
string FPLogConfigFile { get; set; } |
Visual C++ |
---|
property String^ FPLogConfigFile { String^ get (); void set (String^ value); } |
JavaScript |
---|
function get_fpLogConfigFile(); function set_fpLogConfigFile(value); |
Remarks
Metadata
AllowsDefaultChange: false
Cardinality: SINGLE
CopyToReservation: false
DataType: STRING
IsHidden: true
IsOrderable: false
IsSearchable: false
IsValueRequired: false
MaximumLengthString: 2083
ModificationAccessRequired: WRITE
PersistenceType: OWN_COLUMN
RequiresUniqueElements: false
Settability: READ_WRITE
TargetAccessRequired: READ