Reply To: Table Lookup and Xlate

[Jim Kosloskey]

Femina,

I am guessing this table could be quite dynamic – that is requiring frequent updates.

If that is so, you might consider the impact on your Integration Engineers having to maintain this table.

Now it does not matter whether you use a lookup table or Tcl if the information is dynamic. The maintenance impact could be unacceptable.

If you still want to do this in the engine, I would suggest using a Table but just put the exceptions in the Table (with the default being the complement to the exception). That way the Table size can be reduced and potentially so can the maintenance.

Then do the filtering in the routing (pre – Xlate) with a Tcl proc doing the Table lookup using the Lookup Table you configure.

It is more efficient to do message filtering pre Xlate.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.