Skip to main content

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>
</reference>
Location attribute in the binding.ws tag is default location for the partner link.
Location=http://localhost:8001/soa-infra/services/default/First/bpelprocess1_client_ep?WSDL
Endpoint inside “endpointURI” is the alternate endpoint URI.
We have 3 composites.
  1. TestComposite
  2. SayHello
  3. SayHelloAlternate
TestComposite is calling SayHello composite but it should call SayHelloAlternate composite which is alternate composite in case “SayHello” is down.
Sample Partner Link reference
<reference name=”SayHello” ui:wsdlLocation=”SayHello.wsdl”>
<interface.wsdl interface=”http://xmlns.oracle.com/TestApplication/SayHello/BPELProcess1#wsdl.interface(BPELProcess1)”/>
<binding.ws port=”http://xmlns.oracle.com/TestApplication/SayHello/BPELProcess1#wsdl.endpoint(bpelprocess1_client_ep/BPELProcess1_pt)”
location=”http://localhost:8001/soa-infra/services/default/SayHelloAlternate/bpelprocess1_client_ep?WSDL”><property name=”endpointURI”>http://localhost:8001/soa-infra/services/default/SayHello/bpelprocess1_client_ep</property></binding.ws></reference>
When both “SayHello” and “SayHelloAlternate” composites are up then TestApplication will invoke “SayHello” partner link. That means it will take endpoint from “property”
  • <property name=”endpointURI”>http://localhost:8001/soa-infra/services/default/SayHello/bpelprocess1_client_ep</property>
When SayHello is down then it will invoke “SayHelloAlternate” partner link. That means it will take endpoint from location attribute of the binding.ws tag
  • location=”http://localhost:8001/soa-infra/services/default/SayHelloAlternate/bpelprocess1_client_ep?WSDL”
@Note:This is different from Dynamic partener Links, Dynamic links are used when we need to decide end point based on some business logic and this is used to process request in any end point fail-over cases.
Labels:

Comments

Post a Comment

Popular posts from this blog

Dynamic Routing in OSB 12C

Dynamic Routing in OSB cab be used when the BusinessService endpoint required to be determine at runtime in message flow. Consider a scenario where OSB has to route the incoming requests to 2 different services based on the CustomerType element value sent in the payload. So create a XQuery resource with the following contents. Observe that we are using the absolute path of business service in configuration as required by dynamic routing. Following is the XML schema that we use:>>  Customer.xsd <?xml version="1.0" encoding="windows-1252" ?> <xsd:schema targetNamespace="http://xmlns.oracle.com/schema/Customer" xmlns:xsd="http://www.w3.org/2001/XMLSchema"             xmlns:ns1="http://xmlns.oracle.com/schema/Customer">   <xsd:complexType name="Customer">     <xsd:sequence>       <xsd:element name="CustomerId" type="xsd:string"/>       <xsd:elemen
14 comments
Read more

Oracle SOA 12C rest adapter with Custom HTTP headers

Most existing web applications are connected through web services, which are commonly known as SOAP services. More and more users are relying on mobile devices for communication, and they’re looking for lighter ways to access enterprise information on the go. REST services are the answer for the mobile device platform, because they get rapid responses and fast access to data. Oracle SOA Suite 12 c  provides a complete set of service infrastructure components for designing, deploying, and managing composite applications. Oracle SOA Suite 12 c  enables services to be created, managed, and orchestrated into composite applications and business processes. Some time we have need to send HTTP headers in REST service, In OSB we use header component and add what ever is needed but in oracle SOA 12C it's little bit different. Let see how we can do it. Create one SOA Application. Create one SOA Sample project inside SOA Application. Go to composite and drag drop REST adapt
22 comments
Read more

Swagger API document from Any WADL & Schema in Oracle SOA

Hi everyone, Hope everyone is doing well these days, Recently i started a project work over how to generate swagger API document for your any REST API, In case if you don't know what is swagger please go and check " https://swagger.io/tools/swagger-editor/ ". It's a great and easy to use tool which will help to create user friendly, human readable form API documentation with extension for generating API client in different languages with capability of testing your API from same. What is swagger editor, Design, describe, and document your API on the first open source editor fully dedicated to OpenAPI-based APIs. The Swagger Editor is great for quickly getting started with the OpenAPI (formerly known as the Swagger Specification) specification, with support for Swagger 2.0 and OpenAPI 3.0.  What benefits you will get by using swagger, Runs Anywhere, The Editor works in any development environment, be it locally or in the web. Smart Feedback, Validate you
8 comments
Read more