Print Server Logs
Overview
Print logs to provide details about print server requests, connections, and status if a print request fails or times out. The enhanced print logs improve the logging to help administrators identify and isolate errors when print issues occur.
When a print error occurs, administrators can access the bm_print.log to view the following information:
Name | Description |
---|---|
Id |
The unique identifier that correlates entries between the bm_print.log, bm_print_xslfo.log, and printserver_dd.log. |
Transaction Id |
The bs_id of the transaction under process |
Action Variable Name |
The variable name of the action being performed. When a print error is not triggered by an action (e.g. Document Designer preview) <Not Applicable> is displayed. |
Origin |
The area where the action was invoked. For example; Commerce Action, Document Designer preview, or XSL View preview. |
XSL View Id |
The Id of the XSL View associated with the action that triggered the print error. This field is only available for Commerce flows. |
Login Name |
Login name of the user. |
Error |
An error message explaining possible cause for the failure. Sample Error Messages:
|
Start Time |
The time the request was sent to the print server. |
Elapsed Time |
The difference of time between when the print request was sent and the error response is received from the print server. This value is specified in milliseconds and is only calculated for print server failures. |
For example, the following image shows an error entry for Id: 1626702747849.
Print XSLFO Log (bm_print_xslfo.log)
When a print error occurs, administrators can use the Id from the bm_print.log to search for corresponding bm_print_xslfo.log entry. The XSL FO can help administrators recreate and isolate printing issues.
Note: You have to submit a service request on My Oracle Support to enable the bm_print_xslfo.log on your site.
Print Server DD Log (printserver_dd.log)
Oracle CPQ 21D also establishes a print server slow thread detection time limit. When the print request exceeds the pre-defined limit, a log entry is recorded in the printserver_dd.log. Log entries are recorded:
- Slow running print threads,
- When all print threads are busy, and
- When a print thread completes and is returned to the pool.
In addition to the new logs, print action failures and timeouts are now recorded in the Performance Log.
Administration
When enabled, administrators can perform the following steps to access the print logs if printing issues occur:
- Navigate to the Admin Home Page.
- Click Error Logs under Developer Tools.
- Click on the appropriate log: bm_print.log, bm_print_xslfo.log, printserver or printserver_dd.log
When enabled, administrators can perform the following steps to download the print logs to a text file if printing issues occur. This provides administrators with timely and usable troubleshooting information.
- Navigate to the Admin Home Page.
- Click Error Logs under Developer Tools.
- Download the print log file in one of two ways:
- Click (download arrow) next to the print log you want to download. The print log is downloaded to a local location.
- Click on the print log name link to open the print log and then click Download. The print log is downloaded to a local location.
Notes
Note: You have to submit a service request on My Oracle Support to enable the bm_print_xslfo.log on your site.