| Author |
Message
|
| goldsg |
 Posted: Thu Mar 27, 2014 1:12 pm Post subject: IIB 9 - TCPIPClientOutput/GenericHL7Ouput auto-reconnect? |
 |
|
Newbie
Joined: 26 Nov 2013
Posts: 5
|
We're converting interface engines...... and one very important option I having found yet..
Is when a system goes down momentarily or for hours... instead of the messages erroring out and going to the DL queue, is the just queue up.
IIB retrying the TCP connection and automatically reconnect when that system comes back up... and then delivering the messages queued up.
I've read about TCPIP configurable services but I didn't see any documentation relating to this. Can someone point me in the right direction?
Thanks! |
|
| Back to top |
|
 |
| kimbert |
| Posted: Thu Mar 27, 2014 3:46 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Have you actually seen this happening? Or are you asking whether it is possible?
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Mar 27, 2014 11:12 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
It is perfectly feasible to create a flow that will retry the TCP/IP Output a defined number of times before putting the message on the BOQ.
All it takes is a little care and attention to detail AND how the different error conditions are handled by the Node. For example if the endpoint IP address is not there, you get one result/error code and if the address is there but nothing is listening on the port you get another.
One of these respects the timeout in the node and one does not (at least on 7.0.0.3/4) and you have to write some compensating code to make them be handled identically.
I have one customer whose requirement is for the message to retry every 30 seconds for approx 3 hours before being discarded.
Later versions of broker my handle the connection failures a little differently than 7.0.0.3/4.
_________________
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. |
|
| Back to top |
|
|
| GeneRK4 |
| Posted: Tue Dec 30, 2014 3:08 am Post subject: |
|
|
Master
Joined: 08 Jul 2013
Posts: 220
|
I am using WMB version8.I dont see any retry option available in TCP client output node.I have a requirement where I need to send request to a Remote TCP Server.If the TCP server is down,I need to try for some 3 times with a delay of 1 min and if all the 3 retries fail,then I need to hit alternate TCP address.Do we have to handle all these only in code?Do we have any properties in TCP node to control this retry?
As I have to connect to TCP addresses dynamically,I am overriding the TCP IP and port.Hence I believe alternate TCP address IP and port present in TCP Client configurable service cannot be used,as it is dynamic.Is this redirecting the request to alternate TCP address should also be done using coding?Kindly advice. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Dec 30, 2014 4:47 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
The dynamic assignment of the target IP address and port should be done in code by setting the appropriate values in the LocalEnvironment folder. The Node documantation has full documentation of the path to the port and IP Address values.
As for the retry, this again has to be done in code as I indicated in my previous post.
Just watch out for an endless loop that may cause the EG to abend.
_________________
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. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Dec 30, 2014 1:22 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
In case anybody missed it, the latest fix pack for the Healthcare Pack ( v3.0.0.1 ) includes a new property 'Retry Count' which allows the flow developer to specify how many times the HL7DFDLOutput node ( or GenericHL7Output node ) should retry if the destination system is not responding. The default time between retries is 10 seconds, but that is ( and always was ) configurable as well.
See http://www-01.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.healthcare.doc/ha00170.htm
btw, v3 is a later release than v8. The Healthcare Pack version numbers used to match the WMB version number. Not any more - industry packs have their own version numbers now. v3.0.0.1 can be used with WMBv8 or IIBv9.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
|
|
