Skip to main content

Applying a WSDL from a local entry to a proxy service in WSO2 ESB

Local Entry (Local Registry Entry)

The local registry acts as a memory registry where an user can store text strings, XML strings, and URLs. Local entries can be used to hold various configuration elements required by sequences and proxy services. Usually they are used to hold WSDLs, XSDs, XSLT files etc. A local entry can contain XML content as well as plain text content. A local entry can be configured to load content from a remote file too. WSO2 ESB allows to add new local entries easily using user interface configuration

From this blog,I'll explain  how to attach a WSDL to a proxy service from local registry. Note that you can keep a WSDL as a local entry. But it is recommended to keep wsdls in the registry instead, for easier and better management.

Below steps will explainhow to add a WSDL from a local entry to a proxy service.
  1. Extract WSO2 ESB downloaded pack and start it.
  2. Log-in to ESB admin-console.
  3. Create the local entry for WSDL.

  • Navigate to ESB_menu->Manage->Service Bus->Local Entries 


  • Select Add Local Entries option and add the wsdl from In-lined XML Entry option or Source URL Entry option. 
  • After finished adding it,you'll see the local entry is listed in UI.For more information refer the document [1]. 

  1. Create the proxy service 
  • Navigate to ESB_menu->Manage->Add->Proxy Service and select your wanted proxy service template.Here we will select custom proxy template.
           
  • Then for the 'Publish WSDL Options';set 'Publishing WSDL' as 'Pick from registry' as below.


  • To enter 'Reference Key' value click on 'Configuration Registry' link appeared in the UI 
  • Then you will see the Resource Browser UI will pop up.


  • In that Resource Browser UI,on the top you'll see,there's a field called 'Local Registry' with a drop down.



  • Click on the drop down and you'll see the added local entry is listed there as in below image. 
              
  • Select your local entry from this dropdown and click 'Ok' on resource browser UI.Note that please don't picked the path for wsdl from browsing the registry tree.
  • Then proceed with setting endpoints,insequences,outsequences,etc properly to your proxy service.Finally you'll able to successfully create the proxy service. 

Comments

  1. Hung NguyenOctober 19, 2015 at 3:47 AM

    Hi Lalaji,
    How can we do that directly from Dev Studio ?

    ReplyDelete
  2. Justin Raj SJune 1, 2022 at 9:07 AM

    Hi @Lalaji,

    Thanks for the sharing your knowledge, could you please share proxy code for the same blog?

    ReplyDelete

Post a Comment

Popular posts from this blog

Passing end-user details from client to real backend endpoint via JWT token

In real-world business system,WSO2 API Manager useful on exposing company APIs, in a secured and controlled manner with the features provided by APIManager as; OAuth support [To secure API invocations] Throttling support [To control API invocations] Monitoring support [To track API usage] More technically what happening is when a user sends a particular API request,it will goes to WSO2 APIManager node and from there,the request will route to the real implemented back-end endpoint of the particular API and get back the response and returned it to the API invoked user. There can be a use-case,that this back-end endpoint may expect the details of API invoked user as to pass those details to some internal company usage  as; Additional authentication/authorization Track usage data from an internal system. So how to support above requirement from WSO2 AM. There comes the use of JSON Web Token[JWT] implementation done inside WSO2 AM. JWT is a means of representing claims to...
7 comments
Read more

How to rollback/commit processing messages from WSO2 ESB when enabled JMS transaction

This blog post describes the below use-case where WSO2 ESB 4.6.0 act as the intermediate channel in-between two JMS queues. The Use-case First messages will be de-queue to a proxy service deployed in WSO2 ESB from an queue in ActiveMQ message broker. Then inside ESB,the incoming messages will undergo with some message mediation flow and then the message will be send to another JMS queue deployed in JBoss server. Inside the ESB,following failures could be happen;            a) Failures during message mediation process failure inside ESB [for example if you                use   dbreportmediator/lookup mediator inside mediation flow,some times failures can                happen due  to database connection failures]          b) Message sending failure,due to endpoint is unavailability.[For example,the JBoss  ...
4 comments
Read more

TPP Journey through WSO2 Open Banking

Introduction 2018 is all set to be a game-changing year for European banking. The Revised Payment Services Directive (PSD2) has opened the door to new third party providers [TPPs] to connect with banks and manage finances of bank customers on behalf of them. The PSD2 regulation has mandated banks to expose their core-banking account data and payment services to authorized TPPs to consume. Thus as a bank it’s essential to have a solution which will securely expose their internal banking services to third party providers in a trusted manner. WSO2 Open Banking solution provides all required components to expose bank APIs in a well secured manner in order to become PSD2 compliant. This article explains about the importance of the TPP role in PSD2 domain, the requirements set that banks need to provide for TPPs by PSD2 regulations and how WSO2 Open Banking solution supports these requirements.  From my last blog ,I have given an introduction for PSD2 and WSO2 Open Banking soluti...
4 comments
Read more