Implementation steps:
Create a SOA project and drag and drop jms adapter to the exposed service lane
Select Oracle Weblogic JMS
Select Appserver connection or create one to use.
select Consume Message option
Browse for Destination name.
Search Queue name
Put default JNDI eis/wls/Queue or if u want, use your created one.
select the schema for the message to be consumed.
XSD used:
<?xml version= '1.0' encoding= 'UTF-8' ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.cal.org" targetNamespace="http://www.cal.org"
elementFormDefault="qualified">
<xsd:element name="process">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Id" type="xsd:string"/>
<xsd:element name="FirstName" type="xsd:string"/>
<xsd:element name="LastName" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
wire the JMS adapter to BPEL Process
delete the default one and wire with JMS Service partner link.
Deploy the service to EM console and create a message manually to the queue from Admin console or publish a message to the queue.
XML payload used:
<?xml version="1.0" encoding="UTF-8" ?>
<process xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.cal.org emp.xsd"
xmlns="http://www.cal.org">
<Id>1</Id>
<FirstName>Sri</FirstName>
<LastName>Das</LastName>
</process>
No comments:
Post a Comment