Each JDF endpoint uses two mapping files:
One file to map the JDF ticket and its values to PRISMAdirect ticket items.
One file to map the job status used by PRISMAdirect into the job status used by the JDF client.
Mapping failures can occur when you have customised one or both of the mapping files. Or when a JDF client sends an unexpected attribute, etc. You can debug the mapping failures.
Set the trace level for the JDF service to [Debug].
Click [System] - [Services settings] - [JDF service] - [General settings].
Set the trace level for the JDF service to [Debug].
This trace level collects the information that you need to debug the files.
Click [Save].
Prepare the mapping file for debugging.
Go to the folder that contains the mapping files for the concerning JDF endpoint.
You can find the files on the server of PRISMAdirect in the following location: <disk drive>:\ocestorage\Asset\JMF Endpoints\<name of endpoint>.
Open the mapping file that you want to analyse in an editor, for example, Notepad++.
Set Optional="false" for each mapping node that you want to analyse. Or simply set Optional="false" for all mapping nodes.
When you have changed the mapping files, you must upload the files again in the "Configuration" workspace. At upload, the files are loaded from disc and kept in memory as long as the JDF endpoint is running. Just changing the mapping files in the folder on the server is not enough.
Click [System] - [Services settings] - [JDF service] - [JDF endpoints].
Enable option [Use custom mapping files] to use the prepared mapping files for the JDF endpoint.
Click [Upload] for the JDF ticket. Browse to the prepared mapping file and click "Open".
Click [Upload] for the job status. Browse to the prepared mapping file and click "Open".
Click [Save].
You receive a notification that the JDF service is restarted.
Use the SubmitQueueEntry command to submit an order to PRISMAdirect.
Collect and analyse the log file.
Start the "PRISMAdirect software support" tool to collect the log files:
Click: "Start - Search - Apps - Software Support".
Select tab "Logs" and start analysing the log file "JdfService.log".
For example, the log file contains the following error message when the ticket item FinalCost of PRISMAdirect cannot be mapped:
***2018-06-04 16:40:25,731 | PRISMAdirectLogger | ERROR | COULD NOT MAP MANDATORY ACCESS TCIKET FIELD: FinalCost. Error retrieving value from JDF ticket for access field. |
The mapping files are debugged and are ready to be used by the JDF endpoint.
Set the trace level for the JDF service back to [Error].
Click [System] - [Services settings] - [JDF service] - [General settings].
Set the trace level for the JDF service back to [Error].
Click [Save].
Use the debugged mapping files for the JDF endpoint.
Go to the folder that contains the debugged mapping files for the concerning JDF endpoint.
You can find the files on the server of PRISMAdirect in the following location: <disk drive>:\ocestorage\Asset\JMF Endpoints\<name of endpoint>.
Open the mapping file that you have debugged in an editor, for example, Notepad++.
Set Optional="true" for each mapping node that you have debugged. Or simply set Optional="true" for all mapping nodes.
When you have changed the mapping files, you must upload the files again in the "Configuration" workspace. At upload, the files are loaded from disc and kept in memory as long as the JDF endpoint is running. Just changing the mapping files in the folder on the server is not enough.
Click [System] - [Services settings] - [JDF service] - [JDF endpoints].
Enable option [Use custom mapping files] to use the debugged mapping files for the JDF endpoint.
Click [Upload] for the JDF ticket. Browse to the debugged mapping file and click "Open".
Click [Upload] for the job status. Browse to the debugged mapping file and click "Open".
Click [Save].
You receive a notification that the JDF service is restarted.
The JDF endpoint is now ready for use.