Using the attachmentsDescriptor.xsd

Monitoring Instance Message Data With Oracle BAM 23-5

5. To configure Source Value Formatting, check the DateTime Specification

checkbox, and select the MMddyy H:mm:ss format in the drop-down list.

6. Complete the Source to Data Object Field Mapping so that data from the

incoming XML can be mapped to an appropriate field in the B2B data object. See Table 23–2 for a list of fields in the incoming XML which will be retrieved from the B2B instance table.

7. Click Save.

8. Select the B2B_EMS Enterprise Message Source, and click Start. The status changes

to Started in a few seconds. After starting the Enterprise Message Source, any messages that are inserted by the database job into the AQ JMS queue are instantly available in the B2BDO data object. To view the contents of the B2BDO data object, select Data Objects from the Oracle BAM Architect drop-down menu. Browse and select the B2BDO object. Click Contents to view the contents. New rows are inserted into B2BDO as the database job reads incoming messages from the B2B instance table and inserts them onto the AQ JMS queue. For more information on creating Oracle BAM Enterprise Message Sources, see Creating Oracle BAM Enterprise Message Sources in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. Table 23–1 Enterprise Message Source Properties for AQ JMS Queue Property Values and Examples Name Enter a display name for the Enterprise Message Source for example, B2B_EMS. Initial Context Factory Enter weblogic.jndi.WLInitialContextFactory JNDI Service Provider URL Enter t3:localhost:9001 Note: If Oracle BAM is installed is on an Administrator Server use port 9001. If Oracle BAM is installed on a managed server use default port 7001, or the port number configured by the system administrator. TopicQueue Connection Factory Name Enter the name of your connection factory for example, jmsBAMAQQueueCF. TopicQueue Name Enter the name of your JJMS topic or queue for example, jmsBAMAQQueue. Data Object Name: Choose the B2B data object to send the values received from AQ JMS server Operation Choose the Insert or Upsert operation, depending on the use case. Note: The incoming XML value for the date, in the format MMddyy HH24:MI:SS, must be converted into the MMddyy H:mm:ss format that the Enterprise Message Source expects so that it can be stored correctly in the data object 23-6 Oracle Fusion Middleware Users Guide for Oracle B2B

23.6 Mapping Oracle B2B Instance Messages to Oracle BAM Data Objects

Table 23–2 lists the Oracle B2B instance message fields. These fields can be used to design data objects and Enterprise Message Sources in Oracle BAM to monitor Oracle B2B performance in real time. Note that the payloads APP_PAYLOAD, PAYLOAD, WIREPAYLOAD are not included in the list below. They are not transferred for performance reasons. Table 23–2 Oracle B2B Instance Message Fields Field Type ID NOT NULL VARCHAR2256 REFERTOID VARCHAR2256 B2BMESSAGEID NOT NULL VARCHAR2256 ACKNOWLEDGEMODE VARCHAR2256 MESSAGEDATETIME DATE MESSAGETYPE VARCHAR2256 STATE VARCHAR2256 REMAININGRETRY NUMBER10 DIRECTION VARCHAR2256 TIMETOACK VARCHAR2256 TPA_NAME VARCHAR2256 XPATH_EXPRESSION1 VARCHAR21024 XPATH_EXPRESSION2 VARCHAR21024 XPATH_EXPRESSION3 VARCHAR21024 XPATH_NAME1 VARCHAR2256 XPATH_NAME2 VARCHAR2256 XPATH_NAME3 VARCHAR2256 XPATH_VALUE1 VARCHAR2256 XPATH_VALUE2 VARCHAR2256 XPATH_VALUE3 VARCHAR2256 DOCUMENT_DEFINITION VARCHAR2256 CREATED DATE MODIFIED DATE SEND_TIMESTAMP DATE RECEIVE_TIMESTAMP DATE NATIVE_MSG_SIZE NUMBER10 TRANSLATED_MSG_SIZE NUMBER10 BM_RESUBMIT_COUNT NUMBER10 ERRORCODE VARCHAR2256 ERRORTEXT VARCHAR21024