Introduction to Archiving and Restoring B2B Business Messages Archiving B2B Business Messages

22-2 Oracle Fusion Middleware Users Guide for Oracle B2B Example: ipenqueue.properties queue = url = jdbc:oracle:thin:host:1521:sid user = user1 password = password replyToMsgID = from = Acme to = GlobalChips doctypeName = 850 doctypeRevision = 4010 payload = Acme_850.xml attachment =

22.1.2 AQ Dequeue

To dequeue messages, use the IPDequeue utility. 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 AQ, do the following: actionName=ATTACHMENT_NAME:Sample.txt url The database URL format is jdbc:oracle:thin:host:port:sid user The database user password The database password eventName Action name msgID Message ID optional. B2B generates its own message ID if it is not provided as part of an enqueue. msgType Provide an optional message type: ■ Request = 1 default ■ Response = 2 ■ Functional Ack = 9 dateFormat Used to convert the date format used in e-mail delivery channel DYNAMICEMAIL Provides the to party e-mail address as part of actionName. For example: actionName=DYNAMICEMAIL:email_id DYNAMIC_FROM_E MAIL Provides the from party e-mail address as part of actionName. For example: actionName=DYNAMIC_FROM_EMAIL:email_id Note: In Windows ja_JP locale instances, the VARCHARString values are not enqueued correctly to the queue. The INT and CLOB values are enqueued correctly. This causes some fields, such as the from and to fields, to be null when the IPEnqueue utility is used to enqueue a file. As a workaround, in ja_JP locales, orai18n.jar should be added to the classpath while using oracle.tip.b2b.data.IPEnqueue. Table 22–1 Cont. IPEnqueue Properties Name Description Utilities for Enqueuing and Dequeuing 22-3 Table 22–2 lists the Java AQ dequeue utility oracle.tip.b2b.data.IPDequeue properties. Example: ipdequeue.properties: queue = count = 1 output = t1.trc url = jdbc:oracle:thin:host:1521:sid user = user1 password = password

22.2 JMS Enqueue and Dequeue Utilities

You can enqueue to and dequeue from a JMS destination queue or topic using utilities. If a user name and password are not provided, the local JNDI is used, including in a clustered environment, provided that the destinations are distributed. Oracle B2B does not support javax.jms.ObjectMessage.

22.2.1 JMS Enqueue

Use the JMS enqueue utility, oracle.tip.b2b.data.JMSEnqueue, to send a message to a JMS destination queue or topic. This utility expects a property file to be provided as a command-line argument where it reads the details to be sent. Table 22–3 lists the properties that can be configured in the file. Table 22–2 IPDequeue Properties Name Description queue The inbound AQ queue name. If unspecified, the Java dequeue utility uses the default inbound queue IP_IN_QUEUE. count The number of messages to dequeue. If unspecified, only one message is dequeued. output Output file name url The database URL format is jdbc:oracle:thin:host:port:sid user The database user password The database password Table 22–3 JMS Enqueue Properties Name Description destination JNDI name of queue or topic to send message to cf JNDI name of connection factory to use factory Factory provider class isTopic Indicator for topic optional url The JNDI URL format is url=t3:host_name:port_number user The application server administrator userID. password The application server administrator password from From party 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