The Printing Reusable Component prints tags through the WebSphere® Premises Server print
API.
The input attributes for the Printing Reusable Component are: Print
profile name, Pack type, EPC value, and printer ID and mode. This
Reusable Component also requires a labelData Map of information to
write to the tag. It returns a print job ID which can be ignored if
it is not needed.
WebSphere Premises Server configuration
Table 1. Printing agent propertiesName |
Description |
PID |
Agent properties |
PrintingAgent |
RUC Printing Agent |
com.ibm.premises.reusable.printing.PrintingAgent |
- ruc.targetBackend=ruc.premises
- print.output.success=rucresponse/printing/print/success
- print.output.failure=rucresponse/printing/print/failure
|
WebSphere Application Server configuration
Table 2. Activation specification valuesName |
JNDI name |
Destination type |
Destination JNDI name |
Message selector |
Bus name |
PrintingRUCAS |
eis/PrintingRUCAS |
Topic |
jms/ibmse |
ibmse LIKE ‘rucaction/printing/%’ OR ibmse LIKE
‘%/rucaction/printing/%’ |
ibmsensorevent |
Methods
- (String)printEvent(ISensorEvent IBMSE)
- (String)print(String IBMSE_XML) (Exposed as
Web service)
- (String)printMap(Map IBMSE_Payload_Attrs)
Using the Printing Reusable Component
To
invoke the Printing Reusable Component using IBM® Sensor Events or XML, the payload must include:
- PrintingRUCConstants.PRINT_RUC_PROFILE_NAME
- PrintingRUCConstants.PRINT_RUC_PACK_TYPE
- PrintingRUCConstants.PRINT_RUC_EPC_VALUE
- PrintingRUCConstants.PRINT_RUC_PRINTER_ID
- PrintingRUCConstants.PRINT_RUC_PRINT_MODE_KEY
- PrintingRUCConstants.PRINT_RUC_LABELDATA
Note: PrintingRUCConstants.PRINT_RUC_PRINT_MODE_KEY defaults
to print. To reprint, set to PrintingRUCConstants.PRINT_RUC_REPRINT_MODE.
To
publish to Reusable Components MDBs, set the following values for
the JMS topic and eventType. For single-action Reusable Components,
the topic is only checked in the message selector.
- print: profileid/rucaction/printing
The JMS topic and eventType for the MDB output from the Reusable
Component comes from the agent properties. Default output topics for
success and failure for each action are shown in Table 1. The payload
includes:
- print: PrintRUCConstants.PRINT_RUC_RESULTJOBID_KEY_OUT