Where are output files created during bursting?

C_Blocklin

Summary

Where are output files created during bursting?

Content

We have a report being bursted and all the pdf files that were generated and then bursted were being stored in a specific directory /var/tmp and accumulating there.  In the Bursting Control File, found that this is because the directory was hard-coded in the xapi:document tag as follows:

<xapi:document output="/var/tmp/${SALES_ORDER_NUMBER}" output-type="pdf" delivery="123">

Now when we remove the /var/tmp:

<xapi:document output="${SALES_ORDER_NUMBER}" output-type="pdf" delivery="123">

the bursting still works as desired - but we are not sure where the output files are being created?  Under XML Publisher Administrator > Administration tab > Properties > General > the "Temporary directory" setting is "/usr/tmp" - but there is nothing being created in that directory.

We are just trying to change the setting so that the files are not being written to a hard-coded location so that we can monitor the space in whatever directory is getting these files and ensure it is being cleaned up.

Can anyone tell me where these files are being created when not defined in the xapi:document output tag?

Pieter Breugelmans-Oracle

If you're not specifying a directory then I would expect it to be using the working directory of Concurrent Processing. I haven't tried it but I suggest that you take a look at the following locations on the concurrent processing tier:

• $APPLCSF/$APPLLOG
• $APPLCSF/$APPLOUT
• $APPLTMP

C_Blocklin

There does not seem to be anything under $APPLCSF/$APPLLOG.  The originally generated concurrent request output is still in $APPLCSF/$APPLOUT - but not renamed like ${SALES_ORDER_NUMBER} as it was in /var/tmp.  Also, could not find it in $APPLTMP.

I'm thinking that we are not finding anything - XML Publisher is just creating a temporary version of the file before emailing it, then the file is being deleted immediately.  I'm just hoping someone can confirm that behavior so that we can ensure we don't have a huge accumulation of these PDFs somewhere on the server.

Thanks for your input!