Restoring B2B Business Messages

22-4 Oracle Fusion Middleware Users Guide for Oracle B2B Example 22–1 shows the sample jms_enqueue.properties file. Example 22–1 Sample jms_enqueue.properties File Destination Details destination = jmsb2bB2B_IN_QUEUE cf = jmsb2bB2BQueueConnectionFactory Server and Factory Details factory=weblogic.jndi.WLInitialContextFactory url=t3:host_name:port_number user=uncomment and provide you username password=uncomment and proivde you password if required Payload Details from=Acme to=GlobalChips eventName=SampleEvent doctypeName=Custom doctypeRevision=1.0 payload=scratchworkGlobalChips_1234.dat See the sample documentation for how to run these utilities. to To party eventName Action name doctypeName Document type name doctypeRevision Document type revision payload Payload file path attachment Attachment file path msgID Message ID optional. B2B generates its own message ID if it is not provided as part of an enqueue. replyToMsgID Reply to message optional msgType Message type; the default is Request optional. ATTACHMENT_NA ME Attachment file name. Use this property to assign a name to the attachment file that is something other than the e-mail subject name. For a custom outbound message over e-mail with JMS do the following: constant : Sample.xml property : jca.jms.JMSProperty.ATTACHMENT_NAME dateFormat Used to convert the date format used in e-mail delivery channel DYNAMICEMAIL Provides the to party e-mail address. For example: constant : email_id property : jca.jms.JMSProperty.DYNAMICEMAIL DYNAMIC_FROM_E MAIL Provides the from party e-mail address. For example: constant : email_id property : jca.jms.JMSProperty.DYNAMIC_FROM_EMAIL Table 22–3 Cont. JMS Enqueue Properties Name Description Utilities for Enqueuing and Dequeuing 22-5

22.2.2 Enqueue—Using a JMS JCA Adapter or Custom Utilities

The properties used by the AQ and JMS utilities are translated internally before the message is sent to the destination. Ensure that the properties in Table 22–4 are set as part of the javax.jms.Message delivered to the destination that B2B listens on.

22.2.3 JMS Dequeue

The JMS dequeue utility, oracle.tip.b2b.data.JMSDequeue, receives messages from the destination. The count property can be specified to control the number of messages to be picked up from the destination. Retrieved messages are written to the file JMSDequeue.txt at the current path where you run the utility. See the samples documentation on Oracle Technology Network for how to run these utilities. Example 22–2 shows the sample JMS dequeue properties file. Example 22–2 Sample jms_dequeue.properties File Destination Details destination = jmsb2bB2B_IN_QUEUE cf = jmsb2bB2BQueueConnectionFactory count=1 Server and Factory Details factory=weblogic.jndi.WLInitialContextFactory url=t3:host_name:port_number user=uncomment and provide your username password=uncomment and provide your password if required Table 22–4 How AQJMS Properties Are Translated for Custom Utilities AQJMS Utilities Translated Value—For Custom Utilities JMS Message from FROM_PARTY Sent as a string type message property to TO_PARTY Sent as a string type message property doctypeName DOCTYPE_NAME Sent as a string type message property doctypeRevision DOCTYPE_REVISION Sent as a string type message property eventName ACTION_NAME Sent as a string type message property msgID MSG_ID Sent as a string type message property replyToMsgID INREPLYTO_MSG_ID Sent as a string type message property msgType MSG_TYPE Sent as a string type message property attachment ATTACHMENT Sent as a string type message property payload - Sent as the message body 22-6 Oracle Fusion Middleware Users Guide for Oracle B2B

22.3 Using the attachmentsDescriptor.xsd

Use the attachmentsDescriptor.xsd file for sending attachments. Example 22–3 shows a sample attachment XML file. Example 22–3 Sample Attachment XML File ?xml version=1.0 encoding=ISO-8859-1? --Sample XML file generated by XMLSpy v2005 sp1 U http:www.xmlspy.com-- Attachments xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:noNamespaceSchemaLocation=AttachmentsDescriptor.xsd version=1.0 boundary=boundary--- AttachmentPart Locationfile:homeuser_dirdata.xmlLocation Content-Type Top-Level-TypetextTop-Level-Type Sub-TypeplainSub-Type Parameter Value=charset Name=us-ascii Content-Type --Content-Transfer-EncodingBASE64Content-Transfer-Encoding-- Content-ID Content-Description AttachmentPart Attachments