Skip to main content

Posts

Showing posts from November, 2017

Oracle JCA Adapter for Microsoft Message Queueing

Hello, In Oracle SOA 12C, Oracle added few new adapters which can be used across with BPM/BPEL/OSB components. One of them is "Microsoft Message Queueing".  Microsoft Message Queuing is similar to weblogic JMS queues, difference is it's a Microsoft technologies. Microsoft Message Queuing provide most of the all functionalities and use case implementation which are provide by JMS queues. During the design of SOA applications it is inevitable that from time to time you will need to interface with Microsoft-based applications. While technologies like SOAP and REST do a great job when  request-reply  communication is needed, most people struggle when a  messaging-based  communication is required. This blog will present two approaches to get messaging working between Microsoft and  SOA Suite 12c . Before going to implementation part, let c what is it and why we should use it. What is MSMQ: Microsoft Message Queueing (MSMQ) is a message infrastructure and a deve

Multiple Runtime Endpoint Locations for Partner Link

Hello All, Hope you all are doing well!!! Oracle SOA Suite provides support for specifying multiple partner link endpoint Locations. This capability is useful for failover purposes if the first endpoint is down. “ endpointURI ” is the property that we need to add in partner link reference to support multiple endpoint location. <property name=”endpointURI”>endpoint</property> Below is sample code: <reference name=”SayHello” ui:wsdlLocation=”SayHello.wsdl”> <interface.wsdl interface=”http://xmlns.oracle.com/TestApplication/First/BPELProcess1#wsdl.interface(BPELProcess1)”/> <binding.ws port=”http://xmlns.oracle.com/TestApplication/Second/BPELProcess1#wsdl.endpoint(bpelprocess1_client_ep/BPELProcess1_pt)” location=”http://localhost:8001/soa-infra/services/default/First/bpelprocess1_client_ep?WSDL” > <property name=”endpointURI”> http://localhost:8001/soa-infra/services/default/Second/bpelprocess1_client_ep </property> </binding.ws&

SOA Suite 12c Coherence Adapter

Hello All, Recently i came up with a use case where how we can implement oracle caching in SOA services, As few of you may know that OSB 11G already provides a facility of cache in OSB level only but in SOA11G there was no such configuration was available. With the latest SOA version 12C, oracle added a coherence adapter which uses oracle caching management system. What is SOA 12 C coherence: The Coherence Adapter provides access to Oracles Coherence Data Grid.  The adapter provides access to the cache capabilities of the grid, it does not currently support the many other features of the grid such as entry processors – more on this at the end of the blog. Previously if you wanted to use Coherence from within SOA Suite you either used the built in caching capability of OSB or resorted to writing Java code wrapped as a Spring component.  The new adapter significantly simplifies simple cache access operations. Compatibility : Note that when using the Coherence adapter in