Loading

JDF/JMF implementation of PRISMAdirect

In PRISMAdirect, order submission consists of the following steps:

  1. Select a product to create the job. The selected product determines the available file options and ticket items for the job.

  2. If required, add one or more files.

  3. Set the required values for the ticket items.

  4. Submit the order.

An external application (called JDF Manager) that uses the JDF/JMF interface can submit orders to PRISMAdirect. The JDF Manager must provide the required information as described in the steps above. The JDF/JMF interface of PRISMAdirect supports order submission and status requests. The JDF Manager can submit an order and request its status by executing the following steps:

Step 1 – Submit an order via a JDF ticket

  1. By using a JMF SubmitQueueEntry command

  2. By using a HTTP Post

By using a JMF SubmitQueueEntry command

The JDF Manager submits an order by sending a JMF SubmitQueueEntry command to PRISMAdirect. This JMF message must contain a reference to the JDF ticket describing the settings for the new order. The JDF ticket must contain:

  • One or more references to the data files.

  • The name of the product to create the job. If no product is specified, PRISMAdirect uses the default product for the authenticated user to create the job.

Once PRISMAdirect receives the JMF SubmitQueueEntry command, the mapping file of JDF-to-PD is called. The mapping file converts the JDF ticket and its values into a PRISMAdirect ticket for the selected product. PRISMAdirect uses the PRISMAdirect ticket and the data files to create an order that contains one job.

By using a HTTP Post

PRISMAdirect is capable of receiving JDF tickets by a HTTP Post command. It will be treated as a JMF SubmitQueueEntry command.

Please be aware that the content type in the header must be: “application/vnd.cip4-jdf+xml”

After a successful submission the HTTP response from PRISMAdirect will be a full JMF SubmitQueueEntry response.

NOTE

Next to JDF, PRISMAdirect can also receive XML files via a JMF SubmitQueueEntry or a HTTP Post. The only prerequisite is that a transformation must be applied via a XSLT file to create a valid JDF ticket. See the XSLT chapter in this TRM

Step 2 - Response

PRISMAdirect sends a response message to the JDF Manager which includes:

  • The unique QueueEntryID of the order and job(s)

The new order in PRISMAdirect goes through the normal workflow of preparation and printing.

Step 3- Order status feedback

The JDF Manager can request a status update for the orders and jobs by sending a JMF QueueStatus query to PRISMAdirect. Optionally, it can subscribe to automatic status updates.

Optional step – Request the available products

When the JDF Manager needs to know which products are available for submission. That is possible by sending a JMF KnownDevices query to request the available products for the concerning JDF endpoint. PRISMAdirect returns the available products of that JDF endpoint in a response message to the JDF Manager.