| Author |
Message
|
| fat_tony |
 Posted: Thu Feb 22, 2007 11:34 am Post subject: HTTP Input/Apache Tomcat |
 |
|
Novice
Joined: 02 Dec 2006
Posts: 15
|
Is there any way to get hold of the IP address of the calling machine in a flow triggered by HTTP Input node? I've set up a sample flow and looked through all the properties at runtime but it doesn't seem to be available. I'd like to use it for some audit logging.
Version 6.0.0.2 of Broker runtime on Windows.
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Feb 22, 2007 11:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you just need logging of the requests, you can look at Support Pack IE01.
Otherwise, I don't think you can get this information in your flow.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bhaski |
| Posted: Tue Apr 03, 2007 5:03 am Post subject: |
|
|
Voyager
Joined: 13 Sep 2006
Posts: 78
Location: USA
|
you have to use java API and call it inside the compute node to get the IP address. I think no other way to get it inside the flow.
Bhaski. |
|
| Back to top |
|
|
| mgk |
| Posted: Tue Apr 03, 2007 8:09 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
This has been fixed under an APAR, and will be rolled into the next fix-pac. You can wait till then, or raise a PMR to get the fix now. I cannot remember the APAR number before you ask 
The IP address will turn up in the HTTPInputHeaders as "X-Remote-Addrheader" (or something similar - I forget the exact name).
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 |
|
|
| mlafleur |
| Posted: Thu Apr 12, 2007 11:14 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2004
Posts: 73
|
The fix is for defect 45072. Here are the notes provided with it:
Notes
-----
This fix is for the following problem(s):
D45072
Problem summary
The output of the getRemoteAddr() method call is fed into a new
"X-Remote-Addr" header which will under of the HTTPInputHeader parser in
the message tree leaving the HTTPInput node. Therefore you should be
able to see this OK in a JCN.
.
In addition support was also added for:
.
X-Remote-Host from getRemoteHost()
X-Server-Name from getServerName()
X-Server-Port from getServerPort()
X-Query-String from getQueryString()
X-Scheme from getScheme()
X-Remote-User from getRemoteUser()
.
Note that all the X-* headers will only be listed under the
HTTPInputHeader parser if the corresponding java method does not return
NULL for that call. |
|
| Back to top |
|
|
|
|
