Skip to main content

Remove headers from OSB Proxy WS

Their are many times when we notice that when we call any ws from OSB web service, we find UN-necessary information in proxy WS header response.
As this header data is available in time of WS response, so does not bind the end client to send those headers in the WS request, But here question is how we can manage these headers to end user will not receives these headers in his final response of OSB proxy WS.
As in OSB their are many context variables available, which can help us to remove these headers from the proxy WS response.

Predefined Context Variables:

  • header
  • body
  • attachments
  • inbound
  • outbound
  • etc...
by using the header context variable we can remove those extra headers from WS response.

Example Scenario: In this example scenario, we are calling a simple BPEL WS using BPEL DIRECT-BINDING with OSB Business soa-direct.
1.Create a business service
2.Create a proxy service, which will call this BPEL WS.
3.Let us test this WS.
As you see in the attached test result, we are getting
<Header>
      <wsa:ReplyTo xmlns:wsa="http://www.w3.org/2005/08/addressing">
         <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
         <wsa:ReferenceParameters>
            <instra:tracking.ecid xmlns:instra="http://xmlns.oracle.com/sca/tracking/1.0">4d7f5aac5fbbb28b:653f1acf:14d7a6669ef:-8000-000000000000005f</instra:tracking.ecid>
         </wsa:ReferenceParameters>
      </wsa:ReplyTo>
   </Header>
this information is generated from OSB proxy layer, which is not required for end client, here ques is how we will remove this headers,
Here OSB tricks come and we will change the proxy WS layer.
Here on OSB proxy layer, in routing component we added "DELETE" in response pipe line and marked header as ".".
You did it !!!!!

Comments

Post a Comment

Popular posts from this blog

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 ...

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...

ParseEscapedXML Function In Oracle BPEL XSLT Is Throwing Parsing Error For Special Character &

The ampersand escape sequence "&" in a Database Record/XML Payload is being converted to '&amp;' by the BPEL composite.  This results in the XSLT transformation code throwing an oracle.xml.parser.v2.XMLParseException error/exception when the parseEscapedXML method is invoked against the data. The parseEscapedXML method was deprecated in in 12C and should not longer be used. It has been replaced by the new method oraext:parseXML. There is a know bug in the oraext:parseXML method that was address in patch 21377740. The fixes that were made in 21377740 where incorporated into the  12.2.1.0.0 GA release, thus there no patch needed  for the issue.   Note: No backport fix for 12.1.3 was released