Neuron ESB User Network

The Service Bus for the Connected Business

I am very confused. I thought it was pretty easy to create a service endpoint in Neuron that could take in calls for a REST service and act as a pass-through (redirect) layer passing that call on to the real endpoint. Here is what I have done. 

1) Create a service endpoint. 

2) Enabled binding as REST

3) Binding tab is request-reply

4) Client connector is set as publisher AppWebAPI, publish to topic PM.Data, URL is http://esb-myapi.com (no IIS listening here)

5) Service connector is set to subscriber Id PM.API (PM.API is set to subscribe to PM.Data topic), URL is http://esb-myapi.com (IIS listening here)

Everything else is default. Issue is when my app issues the REST GET call to the http://esb-myapi.com endpoint Neuron gets it and AppWebAPI sends a request over and over and over again... goes on until I stop Neuron. I nver see PM.API ever receive the message. 

If I switch the URLs around I see a normal send, receive, reply pattern but the reply is a 404 because IIS is not listening on that endpoint. 

Is this suppose to work? What is wrong? 

UPDATE: 

From what I can tell the client connector does not care at all what the URL is. It processes every request that comes to the box. I can put www.bing.com as the URL and event though I am sending a request to esb-myapi.com it still picks it up. It also means that when it publish the message again to api.myapi.com which is on the same box it just picks the same message up and again and republishes, again and again. Looks like I can't put a filter on the publisher or subscriber either as the key request URL fields are not accessible (at least not without custom code and pipelines). Not sure how you ever get this working on a local machine.  

Views: 643

Reply to This

Replies to This Discussion

Hi Todd..

I saw your support ticket. I will provide a response there.

John Petersen

Hi Todd,

I think you have a misunderstanding of how client connectors and service connectors work. Client Connectors (i.e. the info you fill out on the Client Connector tab) represents services hosted by the Neuron ESB runtime.  When you provide it a URL, the URL MUST reference the local Neuron ESB server that will be hosting and running the Neuron ESB configuration. For example, if your server name is "Neuron01", the url would have to be http://neuron01/.....

generally you would provide a port as well if anything else (like IIS ) is listening/runnning on the neuron server.

In contrast, service connectors (the info you fill out on the Service Connector Tab) represents service endpoints that already exist and are hosted somewhere in your environment.....this could be on the same machine as Neuron...or a remote machine.  In some interesting use cases...it could represent the url of our own client connector....but no need to think about that now :)

So to create a pass thru REST you can either create one service endpoint and fill out both the Client Connector and Service Connector tabs...or you can create 2 Service Endpoints...one with a Client Connector tab enabled...the other with The service connector tab enabled.  in both cases though, the URLs would be different, where the client connector tab url will represent the Neuron server hosted service, while the service connector tab will represent the service url that you want the incoming message passed on to.

I would strongly recommend that you go through the Neuron Web Services tutorial that you can find here:

http://www.neuronesb.com/resources/training/

RSS

Neuron ESB Product Support Forums and Communities

Latest Activity

Prasanth Kharade is now a member of Neuron ESB User Network
Dec 30, 2019
Suman vadde is now a member of Neuron ESB User Network
Dec 16, 2019
Morten Andreasen is now a member of Neuron ESB User Network
Dec 9, 2019
Profile IconCarl Porch, Cordier, Lahbib Marouan and 4 more joined Neuron ESB User Network
Nov 18, 2019
Miroslav Jelev posted a discussion

Using unsupported OAuth provider

Is it possible to create a custom OAuth provider?  Specifically, we are working with Cisco (https://cloudsso.cisco.com/as/token.oauth2).We have a requirement to integrate with a Cisco soap server which uses OAuth2 for authentication. We are using a Service Connector to send a message to the SOAP service, but we need to write custom code in a business process to authenticate with their Cisco OAuth provider. We saw that Neuron supports…See More
Jul 29, 2019
Profile Iconchris comer, Fahd EL YOUBI, Vishal Misal and 2 more joined Neuron ESB User Network
May 16, 2019
Alixx Skevington posted a discussion

Docker Windows 2019 - Neuron 3.5

Hi, We are using 3.5 for our application and I am trying to containerise it for our integration tests.  Building and deploying VM's as this is very time consuming to build and deploy.So I have decided that I to go down docker; everything in our stack has migrated nicely except Neuron.  The first issue was that I needed a later version of the 2016 image or 2019 image from MS which I have. I have managed to install MSMQ on it as well. But when I try to run a silent install everything runs.  But…See More
Apr 15, 2019

Badge

Loading…

© 2020   Created by Neuron Admin.   Powered by

Badges  |  Report an Issue  |  Terms of Service