Posted: Sat Sep 08, 2012 11:11 am Post subject: TCPIPServer Node LocalEnvironment Overrides
Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
Broker 7.0.0.4 on Windoes Server 2008 64bit
The section titled 'Table 1. Input local environment properties ' in the InforCentre description of the TCPIP Server Output Node says the following:-
Quote:
LocalEnvironment/Destination/TCPIP/Output/Hostname - The host name used to make a connection.
I'm using this node to send some data to another system. The only TCPIP Outputnode that works is the Server Output variant. I was looking at the docs and saw the above. This would be perfect in that I could override the destination host name depending upon the enviroment. The Comparable Configurable Service does not allow you to specify as Destination hostname but you can make it work by putting the HOST:POST in the 'Connection Details' property.
I setup a test flow to see if it works and here is the LocalEnv prior to entering the node. I configured the node to use '127.0.0.1:3090'.
That tells me that the Port was overridden but the hostname wasn't.
I'm guessing that the InfoCentre is wrong in indicating that you can override the HostName but it is still there in 8.0.0.1
Does anyone know if this works in V8? I don't have a broker configured at the moment.
Is this worth raising a PMR? _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Joined: 29 Nov 2011 Posts: 490 Location: UK...somewhere
Using the TCPIP Client output node, overriding the hostname definitely works at v8. I havent tried with the 'Server' output node but I would have expected it to work.
I would say its PMR time if its definitely not working at v7 (although I would have expected that bug to have been picked up by Fixpack 4!)
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
Sadly, the TCPIP Client Output Node does not work with the remote system. The way the remote system is designed/configured is IMHO totally messed up and we are stuck with it. From the other systems produced by this company, this seems to be pretty common. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
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