ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » HTTP Input Node: Destination list based routing

Post new topic  Reply to topic
 HTTP Input Node: Destination list based routing « View previous topic :: View next topic » 
Author Message
raghuiib
PostPosted: Wed Jan 09, 2019 2:28 pm    Post subject: HTTP Input Node: Destination list based routing Reply with quote

Novice

Joined: 01 Oct 2018
Posts: 11

Hello,

IIB 10.0.0.5.
I have a simple message flow:

Code:
HTTP Input Node --> Route to label

MyFirstLabel     --> Compute --> MQ Output
MySecondLabel --> Compute --> MQ Output
MyThirdLabel    --> Compute --> MQ Output


HTTP Input node:
Path Suffix to URL: /foo/v1*
Advanced: Set destination list = Yes
Input message parsing: JSON

I am invoking my msg flow like this:
Code:
curl -H "Content-Type: application/json" 'servername:7080/foo/v1/MyFirstLabel' -d '{"f1":"v1", "f2":"v2"}'


When the message flow is invoiked, I can see correct HTTP headers and Json parsing is good too.
However the destination data as labelName set to 'POST':

Code:
LocalEnvironment
   Destination
         HTTP
               RequestIdentifier:BLOB:[B@c9ff2297
         RouterList
               DestinationData
                     labelName:CHARACTER:POST


How do I get the HTTPInputNode to correctly populate the destination data to 'method-named-labels' such as 'MyFirstLabel' in my example.

Is the configuration in my HTTPInput node incorrect? or the parameters in my curl call incorrect?

Of course, I can make this work by inspecting the data and then route it appropriately. But my reading of HTTP Input node documentation is that the this node creates the destination data based on the method/operation invoked.

Any help is appreciated.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » HTTP Input Node: Destination list based routing
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.