JMF Dr. Rainer Prosi CTO, CIP4 Senior Software Architect, Heidelberg

Messaging with JMF Small XML Structures Synchronized with JDF Used for: –Plug + Play Bootstrapping –Snapshots of Job / Device Status –Dynamic Job update –Queue Support –Capabilities interchange

Message Families Query: Request for Information Command: Request for State Change Response: Synchronous reply to a Query or Command Acknowledge: Asynchronous reply to a Command –JDF 1.3: Also Asynchronous reply to a Query Signal: Inline Query Response Pair: –Query provides the Context –Response provides the Information –JDF 1.3: Also inline Command-Response Pair

Subscriptions Also refered to as „Persistent Channels“ Define a list of trigger conditions for Signals May be set up: –as JMF –Within a JDF Allows HTTP Client only implementations

Message Types Bootstrapping (still under construction) –Plug & play Pressroom Device Information –Consumable Level –Status –Settings –Currently executing jobs Job Status / Progress Messages –Job Phase –Job Progress –Events –Job Modifications - NewJDF

Message Types continued Queue Handling –Set Priority –Reorder / Group jobs –Hold / restart queued jobs –Abort running Job Job Submission –Submission via HTTP JDF + Content in MIME package –File Based JDF submission hot folder URL

Message Types continued Device Control –Startup –Shutdown –Resource Modification –Flush Resources

Pipes Pipe Interactions –models the phone call from operator to operator –Start Production –Stop Production –High Water / Low Water marks –Individual Resource Requests –Resource Changes for iterative processing

Messages vs. Audit Elements JMF Messages –Transports Job information in quasi real time –Methods defined for Unidirectional Signals Bi-directional Query-Response Pairs –Immediate Synchronous Responses –Delayed Asynchronous Responses Audit Objects –Logs actual, post-facto job properties in the JDF Resource Usage and Modifications Process Times Events –Logged in the JDF Job Ticket –Transported inside the Job Ticket

Transport Protocol Flat XML over HTTP –Command, Signal XML in the body of an HTTP Post Response in the body of the HTTP Response –Acknowledge, Signal XML in the body of an HTTP Post Empty body in the HTTP Response

Transport Protocol MIME Package over HTTP –JMF must be the first MIME section in a MIME Multipart/Related package File based JMF exchange: used only in special Device-to-Device interactions (e.g. RIP to ImageSetter) Use of SSL is still under development –Two-way authentication –Automated certificate exchange Use of SOAP has been discussed and postponed

JMF Thank you very much for your attention!