There is one thing that I do not like... The fact that it's a challenge to get more than one transaction server running.
Remember that your configuration of subscribers is half the battle - you can configure multiple subscribers and have them separated by name and environment - nicely.
Only subscribe to certain messages for certain environments and wow - everything looks nice from P90701A.
The main problem is that the RTE server polls the F90710 that is defined in the OCMs that you put in the transaction server config.
So, it's poll that table with a very simple SQL
SELECT MIN(ETEVNTSEQ) FROM SY910.F90710 WHERE (ETEVNTST = 3);
The same thing, said another way.
The transaction server does not check subscriber information, this is important. When defining a subscriber and then a connection and events and active environments, remember that this is not going to completely define where messages will end up... What do you mean? I hear you ask.
It's not just triggers from the JDE kernels on the enterprise server that initiate the consumption of RTE, the txn server itself polls the F90710 using the statement above.
The following sequence of screens shows this slight calamity
|My subscriber, defined for port 136 only|
|my subscriptions defined for port 136|
|My environments saying only PY910 messages|
|my RTE server in DV with the message! Boo hoo!|
It might be a simplistic point of view, but the transaction server could compare environments that are subscribed to and not grab the messages. The transaction server could also look at F90706 etc to see if it was the machine that was referenced in the subscriber configuration and once again ignore the messages if this was the case.
Any of the two changes to the code would allow multiple transaction servers using a single set of configuration, much better!