Monday, March 16, 2020

12c SOA - JMS adapter - publish a message to a distributed queue

Implementation steps:
Create a SOA Project
 
 Create a XSD
 <?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>
 Drag and drop JMS adapter




 Choose publish Message
 select Destination Name

 Use Default JNDI.
 Use the schema


 drag and drop a Oneway BPEL



 Take a Invoke activity and wire with JMS partnerlink.


 assign the inputs

 Deploy and test
 You can see that message has been published to distributed queue.

 From Admin console,
To set custome JMS Header properties ⏩12c-soa-set-custom-jms-header-property

No comments:

Post a Comment

Featured Post

OIC - Removing Base64 Padding (=) for JWT Generation in Oracle Integration Cloud (OIC)

When generating a JWT in Oracle Integration Cloud (OIC), the header and payload must be Base64URL encoded before creating the signature. Sta...