none
BizTalk custom pipeline component send custom FaultCode, FailureCategory and message to ESB RRS feed

  • Question

  • Hi All,

    We have a BizTalk 2016 custom C# pipeline component where on some conditions we are throwing out user exceptions with throw new exception statements as shown below.

    Currently when exception reaching to ESB its by default adding FailureCategory value as"0". We wanted to send custom value to the FailureCategory.

    For example, with below "Reached the threshold" exceptions, we wanted to set FailureCategory value as "7" and FaultCode value as "1xc1c11b12" , something like this...which will help us to separate user exceptions category in ESB

    if (count > 100 )
    {
    throw new Exception("Reached the threshold");
    }

    if (count > 100 && user > 50)
    {
    throw new Exception("User count increased");
    }

    Thank you.

    Tuesday, June 18, 2019 7:55 PM

All replies

  • So...the best way to solve this problem is to not use ESBT.

    There is nothing in ESBT that you can't do, easier and faster, with regular BizTalk and Windows.

    Instead of Fault Messages, write the event to the Windows Event Log, preferably a custom log where it can be monitored by System Center, Splunk or other Admin tool.

    Tuesday, June 18, 2019 8:13 PM
  • So...the best way to solve this problem is to not use ESBT.

    There is nothing in ESBT that you can't do, easier and faster, with regular BizTalk and Windows.

    Instead of Fault Messages, write the event to the Windows Event Log, preferably a custom log where it can be monitored by System Center, Splunk or other Admin tool.

    This is not the solution please to write on event log and not at all related to asked question.
    Wednesday, June 19, 2019 3:39 PM
  • Well, often the best solution is to avoid the problem.

    Here's the thing, the Windows Event Log exists exactly for this purpose and all apps should use that as the primary target for events.  The ESB Portal for events creates a risk by isolating this information in a place not easily consumable by standard monitoring tools.

    Wednesday, June 19, 2019 3:54 PM