Output post processor in concurrent manager

Concurrent Processing using the Output Post Processor (OPP) to enforce post-processing actions for concurrent requests.

Post-processing actions are actions taken on concurrent request output.

Example of a post-processing action is that used in Concurrent Processing support of XML Publisher.

If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.

Tuning for Output post processor

1.Increase the number of Output Post Processor as follows:

 Logon to Applications with "System Administrator" responsibility

 Navigate to Concurrent -> Manager -> Define

 Query for "Output Post Processor"

 Click on "Work Shifts" and Increase the number of processes.

(If you have 2 processes then make them 4 if required to 8).

 make sure that you have oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5 under Parameters

2. Please ensure the following settings:

 Logon to Applications with "XMLPublisher Administrator" responsibility

 On the admin tab ensure the following settings:

- Use XML Publisher's à FO Processing àXSLT processor TRUE

- Enable scalable feature of XSLT processor TRUE

- Enable XSLT runtime optimization TRUE

 Set the Temporary Directory to a valid path

Make sure that the tmp directory is at least 5GB or 20x larger than largest data file running

See also Note 406195.1 >> XML Publisher Temp Directory

3. Increase the value of the Concurrent Process Timeout as follows:

1)Logon to Applications with "System Administrator" responsibility

Navigate to Profile -> System

Query for "Concurrent:OPP Response Timeout".

If the value of the Concurrent:OPP Response Timeout is 120 increase it to 240. 

2)Query for "Concurrent:OPP Process Timeout".

Set the value to 10800 sec (3 hours)

4. Determine the heap size per OPP process:

select DEVELOPER_PARAMETERS from FND_CP_SERVICES

where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES

where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

The default is: J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m

You can increase the heap space per process to 1024 (or another value like 2048 depending on the java capabilities on the concurrent server)

For example, to increase to 1024:

update FND_CP_SERVICES

set DEVELOPER_PARAMETERS =

'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'

where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES

where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');