[itnole]

Anybody know how to configure OTM to provide more elegant and descriptive error messages in a Transmission Report other than a Java stack? I tried changing a few of the glog.integration properties, however, the IMessageText still consisted of a small description of the error and a large stack message. Any assistance would be greatly appreciated. Thanks.

[gig]

I'm not aware of a way to remove the stack. I can suggest running an XSL to remove the stack information or parse it prior to distributing it. In the past I just had a process that controlled getting the message and then I distributed the error message to the appropriate group.

Hope that helps.
John

[itnole]

John, thanks for the response. It is not the Java stack trace that is the issue, but the fact that the error description does not provide enough detail which is needed to resolve the failures.

[gig]

My mistake, I read it as you wanting to remove the stack, which personally bugs the heck out of me. Well if you don't mind the work you could take the integration message text that part of the Integration Guide and merge that text with the orginal ones you get as a response. This is a little more work, but is possible. I did this in a 4.5 implementaiton years ago. Mainly to segregate message for groups. I used a perl script to parse the XML message back and then resend an e-mail. Depends on the level of effort you want to go through.

Let me know if you a little more detail. Its been a while, but I do agree with you.

John

[itnole]

John,

That's a possibility in my scenario. Thanks for you help.

Chris