You can also use the runtimeconfig web application / Application configuration to alter the location of the temp directory.
Also from the release notes:
25. To deploy packed war files (vs expanded directory) on WebLogic, a directory is needed for writing
application logs and recording files. By default, OD will create a directory with the application
name in the OS's root ("C:/" for windows and "/" for Linux), and the log files and recording files
will be written to the data/logs and data/temp directories respectively. Alternatively, you can set a
specific directory by using the system property avaya.dd.temp.dir. This is where a sub-directory is
created for each application. For example:
-Davaya.dd.tempdir=c:\temp or some other value.
In either case (default or tempdir), OD assumes that it can create directories and files in that
location. If directory create is disabled, then you must create a subdirectory for each OD web
application deployed with sub directories temp and data/log. When recording, temp recording files
will be placed in temp and if tracing is enabled the trace.log and report.log will be in data/log. If
you have a deployed application named Simple, under c:\temp you would see: c:\temp\Simple\temp
and \data\log.
If the avaya.dd.tempdir is not writable then recording will not work, nor will tracing and local
reporting. The avaya.dd.tempdir can also be used with non-packed war files as well, thus providing
a mechanism to move the temp and log files out of the web application to a separate area.
Lastly when altering the location of the temporary directories,, the URL returned for the recorded
file will be in the file:// protocol format and is NOT directly usable in a prompt to replay the
recording since the file URL is not accessible on the platform where the voice browser is
executing. To replay the message you will need to write java code to move the file from the temp
location to a web context and reference the file there using the http protocol.
|