In the context of the JDF/JMF interface to PRISMAdirect (PD) two types of mapping tables are used, one to map the JDF ticket to the PD ticket and one to map the PD job status to a customer specific job status. This document is meant to be a specification of the two mapping tables. It describes the syntax of the mapping files and also the customization possibilities.
The document should serve system engineers and C&SS as support for understanding the structure of the mapping tables and for adapting them to the needs of the customer if necessary.
The JDF/JMF interface enables job submission to PRISMAdirect and provides job status feedback for JDF-enabled client applications. It does this by enabling one or more configurable JMF endpoints which listen for and react to messages received over HTTP from the JDF Clients.
Job submission
The JDF Clients can submit a job to PRISMAdirect by sending a JDF ticket and the Data files attached. Because internally PRISMAdirect works with a proprietary ticket, the JDF ticket must be "converted" and the values from it must be transferred to a PD ticket. For this the system will use a mapping table (JDF-to-PD) which specifies "what values to take from the JDF ticket and where to put them in the PD ticket".
Status feedback
When required by the JDF Client, the system will expose the status of the jobs. The values for the status are specific to PRISMAdirect. The system will offer the possibility to customize these values to Client specific job statuses. For this again a mapping table (PD-to-JDF) will be used. The table will map each value of the status attributes in PD to another value.
The interface can be configured from the administration interface where the product administrator can add, remove and configure the JMF Endpoints.
Each JMF endpoint configured in the system will have one JDF-to-PD mapping table and one PD-to-JDF mapping table assigned to it. The mapping tables will be XML files stored separately for each endpoint. After installation the system provides two default mapping tables.
When adding a new JMF endpoint, the product administrator can associate the default mapping tables with it or choose other mapping tables. At any moment after this, the product administrator can change the assignment to another mapping table or he can modify the existing mapping table directly by editing the XML file.
This offers freedom to the customers to adapt the functionality of the JDF/JMF interface so that it fits to their own JDF structure and also to their own job status values.
To each JMF endpoint, the product administrator can assign a different couple of mapping tables. So, on the same PRISMAdirect installation, different JDF Client applications can interact with the system based on different mappings JDF-to-PD and PD-to-JDF.