| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Funny HTTP call |
« View previous topic :: View next topic » |
| Author |
Message
|
| francoisvdm |
 Posted: Thu Oct 04, 2007 1:03 am Post subject: Funny HTTP call |
 |
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
MB 602 on Windows
I'm trying to call an Oracle XDB as follows:
| Code: |
| http://EAI_OWNER:EAI_OWNER@xxx.xx.xxx.xxx:8080/oradb/EAI_OWNER/V3_OUTLET_XML/ROW[ROW_ID='1-7CMB9']/CUSTOMER?ContentType=text/xml;charset=UTF-8 |
but it does not like the userid:password@ portion in the beginning.
Here is the error that I get when I try to deploy this: (from Event Log)
| Code: |
BIP2211E: Invalid configuration message containing attribute value 'http://EAI_OWNER:EAI_OWNER@xxx.xx.xxx.xxx:8080/oradb/EAI_OWNER/V3_OUTLET_XML/ROW[ROW_ID='1-7CMB9']/CUSTOMER?ContentType=text/xml;charset=UTF-8' which is not valid for target attribute 'URLSpecifier', object 'V3_MF.'; valid values are 'http://host[:port][/path]'
The message broker received a configuration message containing the attribute value 'http://EAI_OWNER:EAI_OWNER@xxx.xx.xxx.xxx:8080/oradb/EAI_OWNER/V3_OUTLET_XML/ROW[ROW_ID='1-7CMB9']/CUSTOMER?ContentType=text/xml;charset=UTF-8' which is not valid for the target attribute 'URLSpecifier', on object 'V3_MF.'. Valid values are 'http://host[:port][/path]'. This can be caused by a mismatch in levels between the Message Brokers Toolkit, the Configuration Manager and the Broker, or as a result of a user or third party written user-defined node where the implementation library installed at the broker does not match the node definition held at the Configuration manager and Message Brokers Toolkit. |
But, I can type this URL in Firefox and then it works.
If not a fix for this.... is there another way to call Oracle XDB and specify the userid / password as part of the URL?
Thanks a lot for any pointers.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Oct 04, 2007 3:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Does it work if you set the URL in the HTTPRequestHeader, rather than on the node? That is, set the node to something that will deploy, but override the URL that will be called using the HTTPRequestHeader tree.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Fri Oct 05, 2007 2:27 am Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
OK, I can deploy again following jefflowrey advice.... now I just need to figure out how to pass the userid and pwd. Thanks
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
|
| mgk |
| Posted: Fri Oct 05, 2007 3:26 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi.
The HTTPRequest node does not support a username and password being encoded in the URL, whether the URL is on the node or provided dynamically in the LocalEnvrionment or via a 3xx "redirection" status code. You can construct HTTP Basic-Auth headers instead if the remote server supports that, and that has been covered on this forum before.
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
