How to: |
To debug a WebFOCUS API application, you must enable WebFOCUS API Traces in the WebFOCUS Administration Console and access the trace file to identify errors in processing.
Complete the following steps to aid the debugging process of an application that calls the WebFOCUS API.
The ibi.webfoc.WFWorkerUtil.processRequest() method enables developers to specify a trace file name and return exceptions. For an example:
WFWorkerUtil.processRequest( Globals.CGILOCATION,
wfWorkerReq,
wfWorkerResp,
wfSrvTabExt,
null,
null,
request,
null,
true,
ApiTestApp");
Note: You must have administrative privileges to enable WebFOCUS traces using the WebFOCUS Administration Console. If you do not have administrative privileges, contact your WebFOCUS administrator.
Use the URL below to access the WebFOCUS Administration console, then complete the following steps to enable WebFOCUS API Traces.
http://localhost/ibi_html/wfconsole.htm
The following trace file format is generated:
<sequence number> _<component name> _<subcomponent name> _<date> _<timestamp> .trace
A new sequence number is generated with every trace file that gets created and helps determine the order of processing. The component portion of the trace file name is the name you specified using the WFWorkerUtil.processRequest() method. The subcomponent portion of the file name specifies the component being accessed by the application at the time the trace was generated. The date and time portions specify the date and time the file was created. Also, the request that was sent to the WebFOCUS API appears.
WebFOCUS |