Oracle BAM supports the reporting based on the data from External
Messaging Sources.
This post explains the steps to create a report based on the
data from the weblogic Queue.
Create the data object:
Create a data object with required fields to populate the
data from the JMS Queue (Refer the previous post for the steps to create the
Data Object).Here I am creating the Employee data object with three fields.
Configure the External Messaging Source:
These steps configure the JMS queue and map the JMS data to
the data object (Employee) created in the previous step.
- Click on Architect button from the Start up page.
- Select External Message Source from the drop down list.
- Enter the name for the message source and also the JNDI
Service provider URL, Queue connection factory name and Queue name.
- Select the JMS Message Type as TextMessage.
- Select the Data object name as Employee created in the
previous step and also select the operation as Insert.
XML Formatting – Pre-Processing can be
used to process the incoming xml message with XSLT (For this scenario I am not
using any XSLT processing).
- Enter the Message Element name as the
parent element of the message.For my case the Message Element Name is EMPLOYEEDETAILS.
<?xml
version="1.0" encoding="UTF-8"?>
<EMPLOYEEDETAILS
xmlns="http://bamems.sample.com">
<EMPNAME>Albin</EMPNAME>
<EMPNO>24</EMPNO>
<EMPAGE>27</EMPAGE>
</EMPLOYEEDETAILS>
- Select Namespace Qualified checkbox and enter the name space
value if the message is qualified with the name space. My case the name space
is http://bamems.sample.com.
- Select the Column value as Element Tag.
- Select the data object the field name enter the corresponding
XML tag name.
- Click on save.
- Post the sample data to the JMS queue and same can be
verified in the Employee data object.
<?xml
version="1.0" encoding="UTF-8"?>
<EMPLOYEEDETAILS
xmlns="http://bamems.sample.com">
<EMPNAME>Albin</EMPNAME>
<EMPNO>24</EMPNO>
<EMPAGE>27</EMPAGE>
</EMPLOYEEDETAILS>
Create the Report:
- Create a report based on the Employee data object.
|
0 comments:
Post a Comment