KoalaBaby
Member
The XML Publisher kernel has two separate sets of logs that you need to capture depending on the issue you are troubleshooting:
Enable Logging:
Enable Logging:
- Login to Server Manager Management Console.
- From Dashboard / Managed Homes / Managed Instances choose the EnterpriseOne Enterprise Server where the BI Publisher report will be generated.
- From "Runtime Metrics" box on the left side choose "Process Detail".
- Click on the "Process Name" column so to sort it in DESCENDING order. This will bring all instances of XML Publisher kernel into view.
- Click on the "XML Publisher Kernel" link.
- In the "Log Configuration" section check the box "Enable JDEDEBUG.LOG?" and click the "Save" button.
- Repeat the previous two steps until you have enabled debug on all running instances XML Publisher kernel.
- Write down the process ID of each of instance of XML Publisher kernel. This will be helpful to later identify the correct log files.
- Create and Retrieve the Logs:
Submit the Report Definition you wish to troubleshoot. Use application P95630 to monitor the completion of the job, or wait until the error condition occurs.
From Dashboard / Managed Homes / Managed Instances choose the EnterpriseOne Enterprise Server where the Report Definition ran.
In the "Available Log Files" section identify the corresponding logs for your XML Publisher kernels. The log file names will follow this convention:
jde_PROCESSID_DATESTAMP.log
jdedebug_PROCESSID_DATESTAMP.log
Click on the log file to open it and then click on the "Download Entire Log File" link to download the log.
Repeat the previous step until you have saved the jde and jdedebug log for all XML Publisher kernels identified in step 8.
Disable Logging:
From Dashboard / Managed Homes / Managed Instances choose the EnterpriseOne Enterprise Server where the Report Definition ran.
From "Runtime Metrics" box on the left side choose "Process Detail"
Click on the "Process Name column so to sort it in DESCENDING order. This will bring all instances of XML Publisher kernel into view.
Click on the "XML Publisher Kernel" link.
In the "Log Configuration" section un-check the box "Enable JDEDEBUG.LOG?" and click the "Save" button.
Repeat the previous two steps until you have disabled debug on all running instances XML Publisher kernel.
Kernel VM Trace Logs
The process below will require that you restart EnterpriseOne services on your enterprise server. Use caution when applying the steps below to a production server because this process will enable JVM Trace on all XML PUBLISHER kernels that run on the server, which could lead to undesired performance degradation.
Enable Logging:
Login to Server Manager Management Console.
From Dashboard / Managed Homes / Managed Instances choose the EnterpriseOne Enterprise Server where the BI Publisher report will be generated.
From "Configuration" box on the bottom left side choose the "Advanced" view (version 9.1) and then click on "Miscellaneous"
In the "JVM Configuration" section enable the "VM Trace" and add the following parameter to "XMLP VM Options":
-verbose:class
Note: Click on the Help button to the right of the VM Options to see which one is noted for the INI Entry XMLPVMOptions
Click the "Apply" button to save.
From Dashboard / Managed Homes / Managed Instances choose the EnterpriseOne Enterprise Server where the BI Publisher will be generated
Click the "Stop" button to stop EnterpriseOne services on the enterprise server. Any server dependent process will be halted. Make sure you don't do this while other users are connected to EnterpriseOne. Wait for services to stop and then click on the "Start" button to start EnterpriseOne services again.
Create and Retrieve the Logs:
Submit the Report Definition you wish to troubleshoot. Use application P95630 to monitor the completion of the job, or wait until the error condition occurs.
From Dashboard / Managed Homes / Managed Instances choose the EnterpriseOne Enterprise Server where the Report Definition ran.
