Tuesday, November 25, 2008

실전커뮤니티 4차 세미나 (2008년 12월 10일 수요일)

BizTalk 실전 커뮤니티(BizTalker) 4차 세미나 : Dublin vs. BizTalk

안녕하십니까.
벌써 찬바람에 옷깃을 여매는 겨울에 2008년12월03일, 네 번째 BizTalk 실전 커뮤니티 세미나를 실시하게 되어 안내 드립니다.
또한 Microsoft BizTalk Server를 활용하시거나 관심이 있으신 여러분을 BizTalk 실전 커뮤니티인 BIZTALKER(비즈토커) 멤버로 초청 드립니다. 이번 세미나는 김현수 (BizTalk MVP)께서 Dublin vs. BizTalk이라는 주제로 앞으로의 Microsoft 기술 방향과 더불어 BizTalk Server의 미래를 짐작해보는 세미나입니다.

새로운 기술 경험 습득을 통한 지속적인 발전과 휴먼네트워킹에 관심이 있으신 BizTalk 개발자/운영자뿐 아니라 많은 .NET개발자분들의 참여를 희망하며, 참석 여부에 대해서 아래 기재된 문의 연락처로 12월01일(월)까지 확인 연락해 주십시오. (전화 신청 혹은 ‘등록하기’ 버튼을 활용하여 참가신청 email 발송)
실전 커뮤니티는 궁금한 것을 서로 나누는 자리인 만큼, 사전 등록하신 분들을 대상으로 한 질의 사항 Survey가 모임1주전까지 실시됩니다.

그럼 12월03일 수요일 저녁에 뵙겠습니다.
감사합니다. .


  • 일시 : 12월 03일 수요일 저녁 7시

  • 장소: 강남구 대치동 포스코 빌딩 서관 5층 마이크로소프트 Synergy 세미나 실

  • 주제: PDC 2008에서 발표된 Oslo, Dublin을 제대로 이해하고 BizTalk의 미래를 짐작

Agenda

18:30 ~ 19:00 등록 확인 및 간단한 저녁식사 (도시락 제공)
19:20 ~ 20:40 4차 실전 세미나 주제 발표 및 Q&A 세션 (경품 추천) - 김현수 BizTalk MVP
20:40 ~ 20:50 차기 모임 주제 및 일정 협의
21:00 ~ 22:00 BizTalker 친목 모임 (HOF 회비 1만원)


  • Oslo란?
    Oslo는 마이크로소프트의 차세대 모델 지향 애플리케이션 플랫폼 (Platform for model-driven applications)의 코드명입니다.
  • Dublin란?
    WF, WCF 애플리케이션을 위한 Windows Server Application Server 코드명입니다.

문의 및 참석 확인

BizTalk 실전 커뮤니티 운영 방향
목적 및 의의
  • 가치있는 BizTalk 정보 제공 및 네트워크 형성을 위해 Microsoft에서 지원하는 BizTalk Leadership & Networking 프로그램
  • 참여자간 BizTalk 실전 경험 / 정보 교류 활성화를 통한 상호 협력 및 발전 기회 제공

주요활동

  • 기업내 BizTalk 적용 이슈 및 기술 연구
  • BizTalk 활용 시나리오 및 베스트 프랙티스 연구
  • BizTalk 제품 로드맵 업데이트 및 피드백 디스커션
  • BizTalk 개발자/운영자간 친목 도모 On/Offline Communication 모임
활동사이트: BizTalk MVP Blog
커뮤니티의 대상
  • BizTalk 협력사
  • BizTalk 고객사
  • BizTalk에 관심있는 .NET 개발자
모임 형식 및 주제
  • 격월 3째주 수요일 저녁 (18:30 ~ 21:00) à 변경시 사전 공지 및 매월로 확대 고려.
  • 모임은 주제 발표 세미나 및 Q&A 세션, 이후 간단한 친목 도모 모임으로 진행
  • 주요 Topic 주제는 사전 정의 (주제 발표자와 커뮤니티 리더를 중심으로 질의 응답 사전 수집)
  • 모임 결과 자료는 리더 BizTalk Café (http://cafe.naver.com/BizTalker) 를 통해 공유
  • 경품 추천 및 증정
    한국어판 Beginning XML(3/e) 4권 추천 증정 (사이텍미디어 협찬)

세미나 등록하실분은 아래 링크로 메일 보내주세요.

Blogspot reactivating!!!

네이버 블로그로 옮겨서 운영하다보니.. (http://blog.naver.com/dhysys)
타 검색사이트에서는 검색 안되는..매우 난감한 상황이..

BizTalk Server를 알고 싶어하시는 분은 네이버보다 타 검색사이트를 더 많이 이용하실것 같기도 하고 해서 양쪽 블로그를 같이 운영할려고 합니다.

한동안 이쪽은 운영안했는데 다시 운영합니다!

Tuesday, May 22, 2007

Managing a Successful Performance Lab

This paper outlines some key strategies for managing a successful performance lab with Microsoft BizTalk Server 2006.

BTS2k6PerformanceLabs.doc

Tuesday, April 03, 2007

Public Beta for BizTalk 2006 R2 has released!

We are pleased to announce the public Beta 2 release of BizTalk 2006 R2. The beta 2 files are available from the Microsoft Connect site. While there are numerous improvements to BizTalk, this release has three major themes:

EDI: The native support for comprehensive EDI and AS2 protocols in BizTalk Server 2006 R2 will provide much richer data integration and management capabilities for our customers. The Base EDI adapter that comes with BizTalk Server 2006 enables the sending and receiving of messages using X12 and EDIFACT. Customers can leverage this base functionality in order to build custom EDI solutions.

RFID: BizTalk RFID provides rich data, device and event management, as well as open APIs and tools. The capabilities allow customers to cost effectively build vertical solutions and configure intelligent RFID-driven processes.

Platform Alignment: BizTalk Server 2006 R2 features improved alignment with 2007 Microsoft Office system and Windows Vista, including key .NET Framework 3.0 technologies such as WF and WCF. This alignment will help customers access LOB data, as well as system-to-system or supply-chain processes from within their Office System applications (like SharePoint Server, InfoPath and Dynamics).
BizTalk Server 2006 R2 Beta 2 is an unsupported beta, however there are community-based support forums available for the release.
Regards,
Marjan Kalantar

Sunday, February 25, 2007

Clean up scripts for BizTalk

Clean Up Scripts for BizTalk
Since I always have a hard time remembering where it is and what to run, there are two scripts that you can run in your non-production region that can clean up currently running orchestrations that you have already terminated and it is waiting to clear it up.
You will first need to go and create the real stored procedure bts_CleanupMsgBox (this replaces the shell that is there). This file is located in the ..\BizTalk Server 200X\Schema\msgbox_cleanup_logic.sql.
The instructions are as follows to clean it up:
Stop BTS.
Do IISRESET if you are using web services.
Run "bts_CleanupMsgbox" on your message box database. This will mark your instances for deletion and it will not actually delete it.
Run "bts_PurgeSubscriptions" on your message box database. This will purge all your messages marked for deletion.
Restart your BTS.
If you want to completely purge the DTADb there is a nice little stored proc that takes it time to run, but it gives you a completely clean database:
Stop BTS
Run "dtasp_CleanHMData" on the DTADb
Restart your BTS

Tuesday, January 30, 2007

BTS 2006: Transactional Adapter Whitepaper Published

A new BizTalk Server 2006 whitepaper has been posted on the subject of developing a transactional BizTalk Adapter using the Microsoft Base Adapter Classes.

You can find the paper here:
http://download.microsoft.com/download/3/7/6/376a6f6c-8c97-4ab5-9d5a-416c76793fbb/Transact_Adapter.doc

Monday, January 29, 2007

BizTalk Server Scenario Seminar Thanks mail

This is my BizTalk Server scenario Seminar Thanks mail...
Thanks for comming seminar.

You can Downloads BizTalk Server Scenario Seminar PPT Files

Thursday, November 23, 2006

An error occurred when parsing the incoming document

We meet like this error when was connected other system.

Reason: An error occurred when parsing the incoming document: "'.', hexadecimal value 0x00, is an invalid character. Line 1, position 76531."

This error is include unicode in xml data. we must removed unicode.

XML standard characters. look at refrenece.
http://www.w3.org/TR/2004/REC-xml11-20040204/#charsets

Character Range
[2] Char ::= [#x1-#xD7FF] [#xE000-#xFFFD] [#x10000-#x10FFFF]
/* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */
[2a] RestrictedChar ::= [#x1-#x8] [#xB-#xC] [#xE-#x1F] [#x7F-#x84] [#x86-#x9F]

thanks.

Tuesday, November 07, 2006

At least release the BizTalk Server 2004 SP2

Microsoft BizTalk Server 2004 Service Pack 2 contains many important fixes. In addition, a new feature called Archiving and Purging has been added which can automatically manage both the purging and the archiving of the tracking database. Some of the most important fixes that are included in this service pack are:


  • Performance issues with different orchestration scenarios

  • EDI transmit fails with certain structures of outgoing messages

  • Disassembling large flat file messages in the pipeline stalls other processing

  • The rules engine is not honoring rule priorities correctly in high load

  • Body tracking doesn’t track the original message

  • Dynamic send ports causing 10 second delay in subscription

  • 100% CPU in orchestration when calling PrepareForActivationComplete

  • Messages could still be delivered even though the orchestration instances were zombied

  • Connection problems with HTTP Request-response requests

  • Request to turn off FTP Throttling

  • Memory Leak problem in PipelineContextWrapper/Interop.ResourceTrackerbr

    IMPORTANT: BizTalk Server 2004 SP2 is not compatible with BizTalk Server 2002 and BizTalk Server 2000 systems.
    Please be sure to read and review the SP2 documentation before installing SP2.

    Download the link.
    BizTalk Server Service Pack 2 (EN)

  • Tuesday, October 17, 2006

    BizTalk MSMQ Adapter and the MsmqAdapterProperties.dll

    I have been working on an application which needs to send a message to a queue in which the queue location was contained in the incoming XML Message. This was simple as you can just set the send port binding to Dynamic and provide the address through a distinguished field using an expression shape and the following code; MSMQSend(Microsoft.XLANGs.BaseTypes.Address) = ;. The address needs to be in the following syntax; "MSMQ://FORMATNAME:DIRECT=OS:MachineName/Private$/QueueName.

    The difficult part came into play when I then needed to set a label on the outgoing message as well as set the queue transaction property to true (which by default is false).

    When I looked at all of the properties available through the Message Assignment shape on the outgoing message there were no properties available for MSMQ. However, all of the standard properties were available including the MSMQ/T properties.

    What I found is that you need to add a reference to the MsmqAdapterProperties.dll to the orchestration project. This DLL is found in the directory in which you installed the MSMQ Adapter (Program Files\Microsoft BizTalk 2004 Adapter for MSMQ). Once this DLL was added I was able to see all of the MSMQ specific context properties that I would expect to see when dealing with MSMQ.

    So, to set a label on the outgoing messages add the following line of code in the expression editor
    (MSMQ.Label) = "Label";

    Also listed was the transactional property.

    In addition, if there are errors sending the message the message will not reach the remote queue but instead will be placed in the local dead letter queue.

    reference:
    Stephen Kaufman's WebLog
    http://blogs.msdn.com/skaufman/archive/2005/03/13/394747.aspx

    Friday, October 13, 2006

    Attended at the Microsoft SOA & Business Process Conference


    I attended in the Microsoft SOA & Business Process Conference which is opened from SEATTLE.

    03 OCT 2006 ~ 6 OCT 2006 Redmond Microsoft Conference Center

    It has a pleasant experience. The picture is David Chappell. He's an evangelist of SOA. I saw twice him. I first saw in Korea. I'm so impressed his lecture.

    Friday, September 15, 2006

    New BizTalk Server 2006 Troubleshooters Guide

    I found a good Document to BizTalk Server from BizTalk Server Team Blog

    BizTalk Server 2006 Troubleshooting Guide has been published! This document provides troubleshooting techniques through BizTalk Admin console, HAT, Event Log, network monitoring as well as specific tactics for developers to debug adapters, web services, orchestrations, pipelines and much more.

    Thursday, September 14, 2006

    Microsoft BizTalk Server 2006 Documentation Update (CHM)

    Yesterday updated BizTalk Server 2006 document. The file format is CHM.

    Microsoft BizTalk Server 2006 Documentation Update (CHM)

    In this Help Update, you'll find the following content:
  • Complete documentation for all BizTalk Server Line of Business Adapters, including new tutorials, one for each adapter. See the section "Using Adapters."
  • Troubleshooting guidance for each of the native BizTalk adapters. See the section "Troubleshooting Adapters."
  • Troubleshooting Instructions for how to capture a memory dump. See the section "How to Capture a Memory Dump of a BizTalk Process."
  • Disaster recovery instructions for backing up and restoring your BizTalk Server and databases. See the section "Backing Up and Restoring BizTalk Server"
  • Updated Tutorials. See the section, "BizTalk Server 2006 Tutorials"
  • Information for improving fault tolerance. See the section "Planning and Architecture"
  • Updated Developer's Reference that now includes the BAM namespaces that were not included in the RTM documentation. See the section "Developer's Reference"
  • Steve Jobs to 2005 graduates: 'Stay hungry, stay foolish'

    'You've got to find what you love,' Jobs says
    This is the text of the Commencement address by Steve Jobs, CEO of Apple Computer and of Pixar Animation Studios, delivered on June 12, 2005.
    I am honored to be with you today at your commencement from one of the finest universities in the world. Truth be told, I never graduated from college. this is the closest I've ever gotten to a college graduation. Today I want to tell you three stories from my life. That's it. No big deal. Just three stories.
    The first story is about connecting the dots.
    I dropped out of Reed College after the first 6 months, but then stayed around as a drop-in for another 18 months or so before I really quit. So why did I drop out?
    It started before I was born. My biological mother was a young, unwed college graduate student, and she decided to put me up for adoption. She felt very strongly that I should be adopted by college graduates, so everything was all set for me to be adopted at birth by a lawyer and his wife. Except that when I popped out they decided at the last minute that they really wanted a girl. So my parents, who were on a waiting list, got a call in the middle of the night asking: "We have an unexpected baby boy; do you want him?" They said: "Of course." My biological mother later found out that my mother had never graduated from college and that my father had never graduated from high school. She refused to sign the final adoption papers. She only relented a few months later when my parents promised that I would someday go to college.
    And 17 years later I did go to college. But I naively chose a college that was almost as expensive as Stanford, and all of my working-class parents' savings were being spent on my college tuition. After six months, I couldn't see the value in it. I had no idea what I wanted to do with my life and no idea how college was going to help me figure it out. And here I was spending all of the money my parents had saved their entire life. So I decided to drop out and trust that it would all work out OK. It was pretty scary at the time, but looking back it was one of the best decisions I ever made. The minute I dropped out I could stop taking the required classes that didn't interest me, and begin dropping in on the ones that looked interesting.
    It wasn't all romantic. I didn't have a dorm room, so I slept on the floor in friends' rooms, I returned coke bottles for the 5¢ deposits to buy food with, and I would walk the 7 miles across town every Sunday night to get one good meal a week at the Hare Krishna temple. I loved it. And much of what I stumbled into by following my curiosity and intuition turned out to be priceless later on. Let me give you one example:
    Reed College at that time offered perhaps the best calligraphy instruction in the country. Throughout the campus every poster, every label on every drawer, was beautifully hand calligraphed. Because I had dropped out and didn't have to take the normal classes, I decided to take a calligraphy class to learn how to do this. I learned about serif and san serif typefaces, about varying the amount of space between different letter combinations, about what makes great typography great. It was beautiful, historical, artistically subtle in a way that science can't capture, and I found it fascinating.
    None of this had even a hope of any practical application in my life. But ten years later, when we were designing the first Macintosh computer, it all came back to me. And we designed it all into the Mac. It was the first computer with beautiful typography. If I had never dropped in on that single course in college, the Mac would have never had multiple typefaces or proportionally spaced fonts. And since Windows just copied the Mac, its likely that no personal computer would have them. If I had never dropped out, I would have never dropped in on this calligraphy class, and personal computers might not have the wonderful typography that they do. Of course it was impossible to connect the dots looking forward when I was in college. But it was very, very clear looking backwards ten years later.
    Again, you can't connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something — your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life.
    My second story is about love and loss.
    I was lucky — I found what I loved to do early in life. Woz and I started Apple in my parents garage when I was 20. We worked hard, and in 10 years Apple had grown from just the two of us in a garage into a $2 billion company with over 4000 employees. We had just released our finest creation — the Macintosh — a year earlier, and I had just turned 30. And then I got fired. How can you get fired from a company you started? Well, as Apple grew we hired someone who I thought was very talented to run the company with me, and for the first year or so things went well. But then our visions of the future began to diverge and eventually we had a falling out. When we did, our Board of Directors sided with him. So at 30 I was out. And very publicly out. What had been the focus of my entire adult life was gone, and it was devastating.
    I really didn't know what to do for a few months. I felt that I had let the previous generation of entrepreneurs down - that I had dropped the baton as it was being passed to me. I met with David Packard and Bob Noyce and tried to apologize for screwing up so badly. I was a very public failure, and I even thought about running away from the valley. But something slowly began to dawn on me — I still loved what I did. The turn of events at Apple had not changed that one bit. I had been rejected, but I was still in love. And so I decided to start over.
    I didn't see it then, but it turned out that getting fired from Apple was the best thing that could have ever happened to me. The heaviness of being successful was replaced by the lightness of being a beginner again, less sure about everything. It freed me to enter one of the most creative periods of my life.
    During the next five years, I started a company named NeXT, another company named Pixar, and fell in love with an amazing woman who would become my wife. Pixar went on to create the worlds first computer animated feature film, Toy Story, and is now the most successful animation studio in the world. In a remarkable turn of events, Apple bought NeXT, I returned to Apple, and the technology we developed at NeXT is at the heart of Apple's current renaissance. And Laurene and I have a wonderful family together.
    I'm pretty sure none of this would have happened if I hadn't been fired from Apple. It was awful tasting medicine, but I guess the patient needed it. Sometimes life hits you in the head with a brick. Don't lose faith. I'm convinced that the only thing that kept me going was that I loved what I did. You've got to find what you love. And that is as true for your work as it is for your lovers. Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven't found it yet, keep looking. Don't settle. As with all matters of the heart, you'll know when you find it. And, like any great relationship, it just gets better and better as the years roll on. So keep looking until you find it. Don't settle.
    My third story is about death.
    When I was 17, I read a quote that went something like: "If you live each day as if it was your last, someday you'll most certainly be right." It made an impression on me, and since then, for the past 33 years, I have looked in the mirror every morning and asked myself: "If today were the last day of my life, would I want to do what I am about to do today?" And whenever the answer has been "No" for too many days in a row, I know I need to change something.
    Remembering that I'll be dead soon is the most important tool I've ever encountered to help me make the big choices in life. Because almost everything — all external expectations, all pride, all fear of embarrassment or failure - these things just fall away in the face of death, leaving only what is truly important. Remembering that you are going to die is the best way I know to avoid the trap of thinking you have something to lose. You are already naked. There is no reason not to follow your heart.
    About a year ago I was diagnosed with cancer. I had a scan at 7:30 in the morning, and it clearly showed a tumor on my pancreas. I didn't even know what a pancreas was. The doctors told me this was almost certainly a type of cancer that is incurable, and that I should expect to live no longer than three to six months. My doctor advised me to go home and get my affairs in order, which is doctor's code for prepare to die. It means to try to tell your kids everything you thought you'd have the next 10 years to tell them in just a few months. It means to make sure everything is buttoned up so that it will be as easy as possible for your family. It means to say your goodbyes.
    I lived with that diagnosis all day. Later that evening I had a biopsy, where they stuck an endoscope down my throat, through my stomach and into my intestines, put a needle into my pancreas and got a few cells from the tumor. I was sedated, but my wife, who was there, told me that when they viewed the cells under a microscope the doctors started crying because it turned out to be a very rare form of pancreatic cancer that is curable with surgery. I had the surgery and I'm fine now.
    This was the closest I've been to facing death, and I hope its the closest I get for a few more decades. Having lived through it, I can now say this to you with a bit more certainty than when death was a useful but purely intellectual concept:
    No one wants to die. Even people who want to go to heaven don't want to die to get there. And yet death is the destination we all share. No one has ever escaped it. And that is as it should be, because Death is very likely the single best invention of Life. It is Life's change agent. It clears out the old to make way for the new. Right now the new is you, but someday not too long from now, you will gradually become the old and be cleared away. Sorry to be so dramatic, but it is quite true.
    Your time is limited, so don't waste it living someone else's life. Don't be trapped by dogma — which is living with the results of other people's thinking. Don't let the noise of others' opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary.
    When I was young, there was an amazing publication called The Whole Earth Catalog, which was one of the bibles of my generation. It was created by a fellow named Stewart Brand not far from here in Menlo Park, and he brought it to life with his poetic touch. This was in the late 1960's, before personal computers and desktop publishing, so it was all made with typewriters, scissors, and polaroid cameras. It was sort of like Google in paperback form, 35 years before Google came along: it was idealistic, and overflowing with neat tools and great notions.
    Stewart and his team put out several issues of The Whole Earth Catalog, and then when it had run its course, they put out a final issue. It was the mid-1970s, and I was your age. On the back cover of their final issue was a photograph of an early morning country road, the kind you might find yourself hitchhiking on if you were so adventurous. Beneath it were the words: "Stay Hungry. Stay Foolish." It was their farewell message as they signed off. Stay Hungry. Stay Foolish. And I have always wished that for myself. And now, as you graduate to begin anew, I wish that for you.
    Stay Hungry. Stay Foolish.
    Thank you all very much.

    Wednesday, September 13, 2006

    Used XPath get to the value from message

    Get to the one value

    Follow this BizTalk Expression Code
    Create string variable from "Orchestration View"
    strValue = xpath(messageName, "string(/*...XPATH)");

    Get to the mutiple value

    Follow this BizTalk Expression Code
    Create int variable from "Orchestration View"
    iCnt = xpath(messageName, "number(count(/*...XPATH))");

    Loop shape code
    Create int variable from "Orchestration View"
    iLoop = 1;
    iLoop <= iCnt

    Number of count get value
    Create string variable from "Orchestration View"
    strValue = xpath(messageName, "string(/*...and namespace-uri()='namespace'][{0}]/*[local-name()='VALUE'...)", iLoop)

    cheers!

    BizTalk Server 2004 "BizTalkDTADB" clean script

    Around client we happen this problem. It became larger too.
    We must create job schedule this script

    I have been ever see "BizTalkDTADB" size is 60GB before.

    This is a default istallation sdk directory.
    C:\Program Files\Microsoft BizTalk Server 2004\SDK\Samples\Admin\Database Maintenance\Purge_DTADB.sql

    DECLARE @Today datetime
    SET @Today = GETDATE() - 30
    EXEC dtasp_PruneTrackingDatabase @Today


    If you want Tracking Log count, run the following:

    select datepart(year,dtTimeStamp), datepart(month,dtTimeStamp), count(*) as 'rowcount' from dta_DebugTrace group by datepart(year,dtTimeStamp), datepart(month,dtTimeStamp)order by datepart(year,dtTimeStamp), datepart(month,dtTimeStamp)

    To clean up this database, it is suggested you run the following:

    select * from dta_DebugTracewhere dtTimeStamp < '2006-01-01'
    But this script is running very long time 20hours more
    I found reference link.
    http://support.microsoft.com/?id=894253

    How are you doing?


    Hello there!