public class AutomaticTraceFileDelete extends TraceFileHandlerImpl
While it is possible to control where the RFC trace files end up through use of system properties and environment properties, this implementation only checks the current working directory for any trace files. If you have configured the SAP Java Connector to create files in an alternative directory then you should perform any artifact clean up manually.
In the adapter configuration file this class is aliased as sapjco3-automatic-trace-file-delete which is the preferred alternative to the fully qualified classname when building your configuration.
Constructor and Description |
---|
AutomaticTraceFileDelete() |
AutomaticTraceFileDelete(int days) |
Modifier and Type | Method and Description |
---|---|
void |
doHousekeeping()
Do any housekeeping required regardless of trace mode operation.
|
java.lang.Integer |
getPurgeOlderThanDays() |
void |
setPurgeOlderThanDays(java.lang.Integer cleanPeriod)
The number of days after which RFC Trace files are deleted.
|
doHousekeeping
public AutomaticTraceFileDelete()
public AutomaticTraceFileDelete(int days)
public void doHousekeeping()
TraceFileHandler
public java.lang.Integer getPurgeOlderThanDays()
public void setPurgeOlderThanDays(java.lang.Integer cleanPeriod)
cleanPeriod
- the cleanPeriod to setCopyright Adaptris