Analyse the JDF/JMF communication when a new JDF host such as a MIS or pre-press is connected to the PRISMAsync Print Server.
In the logging you can find answers to questions like:
Is there any communication?
Which JMF messages are send?
What is PRISMAsync sending to the host?
Analyse the contents of a JDF ticket send by a host.
In the logging you can find answers to questions like:
Why is it not stapling?
Are there any finishing commands in the ticket?
Have a starting point for transforming the JDF ticket using XSLT. To transform the ticket, you have to know the content of the JDF ticket.
In the logging you can find answers to questions like:
Which other field can I use to add a staple?
For an explanation of JDF ticket transformations, see JDF ticket transformation using XSLT.
Create the log files:
Open the Settings Editor.
Click: Support - Troubleshooting - JMF message logging - Enable.
The log files are created and the logging starts immediately.
Download the log files:
Open the Settings Editor.
Click: Support - Troubleshooting - JMF message logging - Create and download JMF/JDF log file.
The ZIP file contains both "JMFlog.trc" and "JDFlog.trc".
Delete the log files and disable the logging
Open the Settings Editor.
Click: Support - Troubleshooting - JMF message logging - Disable.
The logging stops immediately and the log files are deleted.
For a fresh start with an empty log file: disable, then enable the JMF message logging.
JMF and JDF communication to and from the PRISMAsync Print Server is written to the log file "JMFlog.trc".
In the JMF log file, you can find the following messages:
Incoming JMF messages, for example:
**********************************************************************
03/22/18 15:19:14 Incoming JMF
----------------------------------------------------------------------
Incoming JDF tickets, for example:
**********************************************************************
03/22/18 15:19:14 Protocol name JMF. Incoming JDF ticket
----------------------------------------------------------------------
Response messages, for example:
**********************************************************************
03/22/18 15:19:14 Response
----------------------------------------------------------------------
Warning messages, for example, to warn for unsupported commands:
**********************************************************************
03/22/18 11:30:23 WARNING: JMF message handler not found (<name JMF command>)!
**********************************************************************
03/22/18 11:30:23 Protocol name JMF. Error description = Query/command not implemented
Query return code = NOT_IMPLEMENTED
**********************************************************************
The JDF ticket transformation steps are written to the log file "JDFlog.trc".
For an explanation of JDF ticket transformations, see JDF ticket transformation using XSLT.
Only information that is recognised as JMF/JDF is logged
The following information is logged since it is recognised as a JMF message:
<?xml version="1.0" encoding="UTF-8"?>
<JMF xmlns="http://www.CIP4.org/JDFSchema_1_1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="JMFRootMessage">
</JMF>
Note that the PRISMAsync Print Server will return an error message to the host because this JMF message is empty.
The following information is NOT logged. The tag <JMF> is missing and therefore it is not recognised as a JMF/JDF message:
<?xml version="1.0" encoding="UTF-8"?>
< xmlns="http://www.CIP4.org/JDFSchema_1_1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="JMFRootMessage">
</JMF>
No log files are created when:
The JMF message logging is enabled but there is no communication between the PRISMAsync Print Server and the JDF host.