xlates vs raw routes with tcl procs

Homepage Clovertech Forums Read Only Archives Cloverleaf Cloverleaf xlates vs raw routes with tcl procs

  • Creator
    Topic
  • #51423
    herm ernst
    Participant

    What are the advantages, if any, to using xlates instead of raw routes with tcl procs to do message translations?

    I have mutiple ADT message types (A01-A16) where one tcl proc could handle the edits or should I create xlates for each message type?  Some, not all of the messages will need variants created also.

Viewing 0 reply threads
  • Author
    Replies
    • #70230
      Keith McLeod
      Participant

      This is a matter of preference.  I like to have the rule of not manipulating messages in the tps inbound or prexlate if it can be avoided.  This allows you to view the inbound SMAT files to know what fields you are actually going to work with.  I use these locations to filter out messages.

      I then manipulate the message in an xlate.  If you don’t want to have multiple xlates consider using the wild card route with a single xlate.  This may require a generic structure be established in a variant.  I would also suggest using the latest variants since most fields have been added.

      Hope this helps…..

Viewing 0 reply threads
  • The forum ‘Cloverleaf’ is closed to new topics and replies.

Forum Statistics

Registered Users
5,117
Forums
28
Topics
9,292
Replies
34,432
Topic Tags
286
Empty Topic Tags
10