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 » Requested URL in HTTPInput node with wildcard suffix

Post new topic  Reply to topic
 Requested URL in HTTPInput node with wildcard suffix « View previous topic :: View next topic » 
Author Message
Cogito-Ergo-Sum
PostPosted: Mon May 28, 2012 5:53 am    Post subject: Requested URL in HTTPInput node with wildcard suffix Reply with quote

Master

Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India

Hi,
I have a HTTPInput node with path suffix as /api/*. I am sending an XML payload to http://server.com:7080/api/create. I want to determine that the URL qualifying was create or /api/create. Is this information in HTTP header ? Because, I can see the original command
Code:

  (0x01000000:Name  ):HTTPInputHeader = ( ['WSINPHDR' : 0x8d8dac0]
    (0x03000000:NameValue):X-Original-HTTP-Command = 'POST http://server.com:7080/api/create HTTP/1.1' (CHARACTER)


I set-up a trace node after HTTPInput node for ${LocalEnvironment} and all I see is the request identifier
Code:

( ['MQROOT' : 0x8ab0250]
  (0x01000000:Name):Destination = (
    (0x01000000:Name):HTTP = (
      (0x03000000:NameValue):RequestIdentifier = X'414d51204e5355425241484d2e514d30d25dc34f032f0020' (BLOB)
    )
  )
)


I tried with a Compute node looking for InputLocalEnvironment.HTTP.Input.RequestLine; nothing. Note, I could see the HTTP.Input.RequestLine in the Mapping node graphical mapper.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes
Back to top
View user's profile Send private message
mgk
PostPosted: Mon May 28, 2012 6:20 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

So, the creation of this info in the LE is triggered by the setting of the 'Set Destination List' property:

Code:
(0x01000000:Name):HTTP        = (
    (0x01000000:Name):Input = (
      (0x01000000:Name):RequestLine = (
        (0x03000000:NameValue):Method      = 'POST' (CHARACTER)
        (0x03000000:NameValue):RequestURI  = '/Wss001/services/Wss001' (CHARACTER)
        (0x03000000:NameValue):HTTPVersion = 'HTTP/1.1' (CHARACTER)
      )
    )
  )



Kind Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
Cogito-Ergo-Sum
PostPosted: Mon May 28, 2012 6:38 am    Post subject: Reply with quote

Master

Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India

Many thanks !

I will admit that the documentation on HTTPInput in Infocenter did not make this obvious to me. Also, the LocalEnvironment as described here, mentions that some nodes may not set the fields.
Quote:

The root of the local environment tree is called LocalEnvironment. This tree is always present in the input message, it is created when a message is received by the input node. Some input nodes create local environment fields, others leave it empty.


So, I couldn't arrive at the use of Destination List.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes
Back to top
View user's profile Send private message
mgk
PostPosted: Mon May 28, 2012 7:03 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

Quote:
So, I couldn't arrive at the use of Destination List.


I understand entirely and I will try and get the docs improved in this area.

Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
Cogito-Ergo-Sum
PostPosted: Mon May 28, 2012 8:54 am    Post subject: Reply with quote

Master

Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India

Quote:
I understand entirely and I will try and get the docs improved in this area.


Many thanks !
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes
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 » Requested URL in HTTPInput node with wildcard suffix
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.