Author |
Message
|
scravr |
Posted: Fri Nov 18, 2011 8:52 am Post subject: Node Name+Terminal in JAVA |
|
|
 Partisan
Joined: 03 Apr 2003 Posts: 391 Location: NY NY USA 10021
|
In WMB V7:
How can JCN find-out the name of sending Node and it's terminal name?
EX:
If NodeA with terminal A1 is connected to JAVA Compute Node:
How can this JAVA get "NodeA" and "A1" as input-node-name and input-terminal-name? |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Nov 18, 2011 9:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You can't do this in ESQL.
Why would you expect to do this in Java?
Whatever reason you have for wanting to do this, you need to rethink it.
You are basically asking the same question as asking "How can a java method know what method called that method?". |
|
Back to top |
|
 |
scravr |
Posted: Fri Nov 18, 2011 9:36 am Post subject: |
|
|
 Partisan
Joined: 03 Apr 2003 Posts: 391 Location: NY NY USA 10021
|
This generic JCN acts based on input-type: MQInput, FileInput.... Also needs to identify terminals: Out, End-Of-Data terminal(for files), etc....
There are other Process Flow tools that give this info. |
|
Back to top |
|
 |
Vitor |
Posted: Fri Nov 18, 2011 9:49 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
scravr wrote: |
There are other Process Flow tools that give this info. |
WPS is a different product to WMB. It's also a different product to WMQ & WAS. It doesn't make one better or worse than the other, just that they have different capabilities and are used for different things.
WPS (and AFAIK WESB) do store the state & route of a payload through their flows. WMB does not because WMB is designed to be stateless.
You could easily enough tag inbound messages with origin data. How much this decreases the utility of your generic node is a question dependant on your design. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Nov 18, 2011 9:51 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
There is a saying about SAP installations.
1) Don't try to fit SAP to how your organisation works.
2) Change your organistation to fit SAP
Something like your requirement then...
Just like trying to get Broker ESQL code to explicity handle every different type of ODBC connection failure. _________________ 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 |
|
 |
|