The print profile application program interface (API) supports outbound and inbound printing and provides abstract and concrete methods.
For information about the WebSphere® Premises Server Java™ API, refer to the WebSphere Premises Server API documentation.
For more information on predefined agents and their topics, refer to Predefined task agents.
WebSphere Premises Server listens to the inbound print profile topics. Inbound message are processed by a message-driven bean (MDB) which updates the appropriate tables with the received information. The inbound print profile can update the status for a single tag or a print job.
The inbound API concrete method publishes a print job or tag status to these topics on the WebSphere Application Server SIBus.
You can also use a servlet to update the status of inbound print profile topics. The servlet can be accessed at the following URL, where Premises_Server is the host name or IP address of your WebSphere Premises Server: http://Premises_Server:9080/ibmse/eventpublish
See Configuration samples for print profile support for examples of the servlet URLs and XML for updating the print job or tag status.
Print jobs submitted from Print, Verify, and Ship and bound to a printer device type (outbound print profile) publish to the following topics on the WebSphere Application Server service integration bus (SIBus). Printer vendors can use the abstract method to implement outbound printing and subscribe to these print topics using the API.