Concurrent Manager: Output Post-processor issue

The concurrent program the output of which is XML report is failing in warning and the log shows the below message:
Beginning post-processing of request 5292785 on node AP6105RT at 02-AUG-2006 04:47:48. Post-processing of request 5292785 failed at 02-AUG-2006 04:49:48 with the error message:

The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status.
Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary. Example if the responce time is set to 60 make it atleast 180. Bounce the concurrent manager once this is done. This will resolve the issue.

If the issue still persist, check the OPP log file. You follow below navigation

System Administrator -> Concurrent : Manager -> Administrator

On this screen click on Output Post Processor and then click on Processes button -> Manager Log button

A new web page will open showing the manager log. Come to the bottom, you might see followng error

[10/7/08 10:15:56 PM] [1900472:RT5709298] Completed post-processing actions
for request 5709298.
[10/7/08 10:20:07 PM] [OPPServiceThread1] Post-processing request 5709301.
[10/7/08 10:20:07 PM] [1900472:RT5709301] Executing post-processing actions
for request 5709301.
[10/7/08 10:20:07 PM] [1900472:RT5709301] Starting XML Publisher
post-processing action.
[10/7/08 10:20:07 PM] [1900472:RT5709301]
@ Template code: FAXSRPIM
Template app:  OFA
Language:      EN
Territory:     US
Output type:   PDF
[10/7/08 10:20:07 PM] [UNEXPECTED] [1900472:RT5709301]
/appslog/fin_top/utl/fintest/out/ (No such
file or directory)

at Method)
@ at oracle.apps.xdo.common.tmp.TmpFile.createTmpFileJDK118(
@ at oracle.apps.xdo.common.tmp.TmpFile.createTmpFile(
at oracle.apps.xdo.template.FOProcessor.createFO(
at oracle.apps.xdo.template.FOProcessor.generate(

So the path /appslog/fin_top/utl/fintest/out/ is not correct. As per the note ID 428855.1 changed the path to valid location

Navigate the following as the responsibility “XML Publisher Administrator”
Select Administration on the Personal Home Page
Under the Configuration tab select Properties and then General.
From there the Temporary directory will be displayed.

Changed the path to some thing that is existing physically.

After that bounce the output post processor. This should resolve the issue.


MWA Service Management – Brief

MWA Service management – Brief

MWA is mobile web application. Using this we can have our applicaiton on mobile. MWA service is used in E-Business suite is for running the applicaiton on mobile. There are very few parameters that needs to be configured for this and we can start MWA service to be used on our mobile.

If we see context file we have a parameter named s_mwastatus which has to be enabled in order to use this service.

(oa_service_status oa_var=”s_mwastatus”)enabled(/oa_service_status)

Other then this, there will be a MWA port on which the service can be started. For ports we have two configuration, one is the telnetl port where we can start the service. If we have multiple telnet ports then we can have a dispatcher port which can load balance the telnet ports.

You can find the telnet port entry in context file as given below.

(mwaTelnetPortNo oa_var=”s_mwaTelnetPortNo” oa_type=”DUP_PORT” base=”10200 step=”6 range=”6 increment=”2 separator=”,” showall=”true” label=”MCSA Telnet Server Port”)10290,10292,10294(/mwaTelnetPortNo)

In E-Business suit we have the configuration file for MWA located at below path


The important configuration setting in thie configuration file is as give below.

DBC file path
mwa.DbcFolder=(Path to $FND_SECURE)

telnet port

Dispatcher port

Log directory path
mwa.logdir= (Log dir path)

Log file name
The above parameters are self explainatory. Also some explaination is provided in config file.

You can use any port which is greated then 1024 and that is not used by any other service and you can start your service on that port. But make sure you make the same port entry in context file and mwa.cfg, else when autoconfig runs it will update mwa.cfg with the port number form context file and your service may not run.

You can start the services by going to $INST_TOP/admin/scripts and running following command

For Telnet port: start (port number) &

For Dispatcher port: start (port number) &

MWA URL will be
telnet http://(server name):(telnet port)
telnet http://(server name):(dispatcher port)

Example: telnet://

You can use either telnet port or dispatcher port to log into the application. if dispatcher port is used, it will do load balancing.