locked
Enterprise librart 5.0 with BizTalk 2010 RRS feed

Answers

  • Thanks you guys for your valuable replies. I found couple of things to make Ent Lib 5.0 work with BizTalk 2010.

    1. Add a. Enterprise Logging, b. Enterprise Common and c. Service Location DLLs as reference to Class Library project.

    2. Assign a Strong Name Key to Class Library project.

    3. Manually GAC above mentioned DLLs, if receiving assembly not found error.

    4. Add these DLLs as resources to BizTalk project-post deployment, if receiving assembly not found error after GACing them.

    5. Add logging to both 32 and 64 bit BizTalk Config files.

    Thanks.......

    Tuesday, August 7, 2012 5:56 PM

All replies

  • I personaly don't use EL too much.

    ESB Toolkit 2.1 is using EL 4.1. EL 5.0 conflicts with 4.1.

    The logging blok in EL 4.1 almost the same as in EL 5.0. So if you can, use EL 4.1 or don't use EL 5.0 on the same machine as ESB Toolkit.

    For using EL Logging block see the EL Help, it gives you all details.

    For loggin without EL use the .NET System.Diagnostics classes like EventLog


    Leonid Ganeline [BizTalk MVP] BizTalkien: Naming Conventions for the BizTalk Solutions

    Monday, August 6, 2012 9:47 PM
    Moderator
  • In addition to the answer Leonid provided:

    If you need to log information from several places in BizTalk you could also look at the CAT instrumentation framework as an alternative.

    http://blogs.msdn.com/b/asgisv/archive/2010/05/11/best-practices-for-instrumenting-high-performance-biztalk-solutions.aspx

    This is a very performant and easy to use instrumentation framework from the Microsoft Customer Advisory Team.

    It uses the same logging framework as BizTalk itself (ETW). With a console application (http://btscatifcontroller.codeplex.com/) you can switch it on or off without having to change the BizTalk config file so you can also enable it very easy on production environments.

    It is completely open source so you can also adjust the code to log to the eventlog if you like, but that degrades performance.


    Jean-Paul Smit | Didago IT Consultancy
    Blog | Twitter | LinkedIn
    MCTS BizTalk 2006/2010 + Certified SOA Architect

    Please indicate "Mark as Answer" if this post has answered the question.


    Tuesday, August 7, 2012 7:31 AM
  • Thank you guys for your valuable inputs.

    Actually I'm not using ESB ToolKit, so I'm fime with Ent Lib 5.0 as there is no conflict or ambiguity in framework. The issue is "Is there any sample to Lab or Guideline Doc on how to use Ent Lib 5.0 with BizTalk 2010?"

    Thanks.........


    • Edited by Rik_at_BTS Tuesday, August 7, 2012 12:55 PM
    Tuesday, August 7, 2012 12:33 PM
  • What exactly doesn't work?

    You don't see any output or do you get an error?

    Did you use the hands-on labs to get acquainted with Enterprise Library 5.0 logging?

    If so then it probably is a configuration issue and will this blog post help you.


    Jean-Paul Smit | Didago IT Consultancy
    Blog | Twitter | LinkedIn
    MCTS BizTalk 2006/2010 + Certified SOA Architect

    Please indicate "Mark as Answer" if this post has answered the question.

    Tuesday, August 7, 2012 1:03 PM
  • In addition to what is suggested by Leonid and Jean. Could you please specify what is the error you are facing, that would help? There is no document(as far as i know) which can give you direct steps to integrate it with BTS. All you need to refer is http://msdn.microsoft.com/en-us/library/ff632023.aspx and try out. you may run into config settings issues until you try it.
    Tuesday, August 7, 2012 3:05 PM
  • Thanks you guys for your valuable replies. I found couple of things to make Ent Lib 5.0 work with BizTalk 2010.

    1. Add a. Enterprise Logging, b. Enterprise Common and c. Service Location DLLs as reference to Class Library project.

    2. Assign a Strong Name Key to Class Library project.

    3. Manually GAC above mentioned DLLs, if receiving assembly not found error.

    4. Add these DLLs as resources to BizTalk project-post deployment, if receiving assembly not found error after GACing them.

    5. Add logging to both 32 and 64 bit BizTalk Config files.

    Thanks.......

    Tuesday, August 7, 2012 5:56 PM