Skip to Content
author's profile photo Former Member
Former Member

Write to Seeburger Message Tracking

Hi,

We have a new version of Seeburger MT (2.2.2) and the old configuration that we had does not seem to work. Message Tracker is getting filled with some information, but not everything that I want. I guess that the information that do get written comes from the communication channel module settings because this works even if I remove the UDF.

My UDF is like this in our old system:

GlobalContainer myGlobalContainer;
myGlobalContainer = container.getGlobalContainer();
AbstractTrace trace = container.getTrace();


try
{
  java.util.Map map = container.getTransformationParameters();
  // Message ID for this message
  String messageID = (String) map.get(StreamTransformationConstants.MESSAGE_ID);
  // Message ID for original message
  String parentID = (String) map.get(StreamTransformationConstants.REF_TO_MESSAGE_ID);
  String senderParty = (String) map.get(StreamTransformationConstants.SENDER_PARTY);
  String senderService = (String) map.get(StreamTransformationConstants.SENDER_SERVICE);
  String receiverParty = (String) map.get(StreamTransformationConstants.RECEIVER_PARTY);
  String receiverService = (String) map.get(StreamTransformationConstants.RECEIVER_SERVICE);
  String interfaceName = (String) map.get(StreamTransformationConstants.INTERFACE);
  String sourceMsg = "";


  DateFormat dateFormat = new SimpleDateFormat("MM.dd.yyyy / HH:mm:ss");
  Date date = new Date();
  String dateTime = dateFormat.format(date);


  // Only write to MT if we have a messageID
  if (messageID != null && !messageID.equals("")) {


  // Update XML Message
  MTMasterXI masterXML = new MTMasterXI();
  masterXML.clear();
  messageID = masterXML.getID(messageID,MT_MESSAGE_TYPE_XML);
  masterXML.setField(MTMaster.FREE3, interfaceName);
  masterXML.setField(MTMaster.FREE6, sender);
  masterXML.setField(MTMaster.FREE7, receiver);
  masterXML.setField(MTMaster.FREE9, dateTime);
  masterXML.setField(MTMaster.FREE12, messageNr);


  masterXML.writeRecord(messageID.substring(0,36), MT_MESSAGE_TYPE_XML);
  }
}
catch (MTException error)
{
  trace.addWarning(error.toString());
}


return "";

However, nothing happens in the MT. Anyone got some ideas? The new Message Tracking is brand new so if I could have missed some initial settings. Any help is appreciated.

I have also attached two screenshots of how the communication channels module is looking.

2.JPG (31.4 kB)
1.JPG (143.0 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Aug 31, 2015 at 02:10 PM

    Hi,

    The Message Tracking gets filled usually with information from the Communication Channel as well as anything that is written to the Database via UDFs.

    That explains why you have already some setting in the MT. These are the basic settings that are created with the 1:1 Conversion (BIC-Adapter) if the parameter "archiveXI=true" is set.

    So if this works, then it means that the entries that are written in your UDF probably cannot be correlated to an existing entry (e.g. if the Message ID has changed or is not prepared correct inside the UDF)

    Did you also change the PI/PO-Version that is used ?

    Kind Regards

    Stefan

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.