| Author |
How do I test custom Pipeline component in BTS 2004?
|
|
|
| I am kind of new the BizTalk 2004, can someone tell me how I can test my
custom (decode) pipeline component in BTS 2004?
| |
| David Downing [MSFT] 2004-08-23, 5:50 pm |
| Copy your custom assembly into ...\program files\Microsoft BizTalk Server
2004\Pipeline Components
Open or create a new BizTalk project.
Open the Toolbox.
Right-click and select Add/Remove items.
Select the BizTalk Pipeline Components Tab.
Check the checkbox associated with your custom pipeline component.
Click OK
Create a new receive pipeline.
Drag your component into the decode stage.
Build and deploy your project (when you've finished with everything
required by your scenario)
Configure your receive and send ports
Test your pipeline component.
Dave
--------------------[vbcol=seagreen]
microsoft.public.biztalk.appintegration,microsoft.public.biztalk.general,mic
rosoft.public.biztalk.tools,microsoft.public.dotnet.languages.csharp[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
.phx.gbl[vbcol=seagreen]
microsoft.public.biztalk.tools:4007
microsoft.public.dotnet.languages.csharp:267503
microsoft.public.biztalk.appintegration:7227[vbcol=seagreen]
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
| |
| Devdutt Patnaik 2004-08-23, 5:50 pm |
| In addition to this you can also attach the BTSNTSvc.exe process, put
breakpoints and step thru you custom pipeline component code.
Regards
Dev
""David Downing [MSFT]"" <ddowning@online.microsoft.com> wrote in message
news:TRmDe3UiEHA.3628@cpmsftngxa10.phx.gbl...
> Copy your custom assembly into ...\program files\Microsoft BizTalk Server
> 2004\Pipeline Components
> Open or create a new BizTalk project.
> Open the Toolbox.
> Right-click and select Add/Remove items.
> Select the BizTalk Pipeline Components Tab.
> Check the checkbox associated with your custom pipeline component.
> Click OK
>
> Create a new receive pipeline.
> Drag your component into the decode stage.
>
> Build and deploy your project (when you've finished with everything
> required by your scenario)
>
> Configure your receive and send ports
>
> Test your pipeline component.
>
> Dave
>
> --------------------
>
microsoft.public.biztalk.appintegration,microsoft.public.biztalk.general,mic
> rosoft.public.biztalk.tools,microsoft.public.dotnet.languages.csharp
>
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
> phx.gbl
> microsoft.public.biztalk.tools:4007
> microsoft.public.dotnet.languages.csharp:267503
> microsoft.public.biztalk.appintegration:7227
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> EBusiness Server Team
>
| |
|
|
| Matt Milner 2004-08-23, 5:50 pm |
| 1) use the pipeline tools in the SDK\Utilities\ folder to test out a
pipeline configured with your component and see if it works.
2) create a receive or send with your component in a custom pipeline and run
it. You can attach to the btsntsvc.exe process and set breakpoints in your
code to debug. you might also be able to do the same with the pipeline
tools mentioned in #1, but I haven't tried it.
matt
"Aaron" <someone@microsoft.com> wrote in message
news:%23AHyIpUiEHA.2704@TK2MSFTNGP10.phx.gbl...
> I am kind of new the BizTalk 2004, can someone tell me how I can test my
> custom (decode) pipeline component in BTS 2004?
>
>
| |
| Todd Sussman 2004-08-25, 5:53 pm |
| There are also some nice tools for testing Pipelines. I am not on a Biztalk
machine right now, but I believe they are in the SDK folder under
utilities\pipelines.
Todd
"Devdutt Patnaik" <devdutt.patnaik@amicore.com> wrote in message
news:urwQ0HViEHA.1040@TK2MSFTNGP09.phx.gbl...
> In addition to this you can also attach the BTSNTSvc.exe process, put
> breakpoints and step thru you custom pipeline component code.
>
> Regards
> Dev
>
> ""David Downing [MSFT]"" <ddowning@online.microsoft.com> wrote in message
> news:TRmDe3UiEHA.3628@cpmsftngxa10.phx.gbl...
> microsoft.public.biztalk.appintegration,microsoft.public.biztalk.general,mic
> cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
> rights.
>
>
| |
| Stefan 2004-08-27, 6:06 pm |
| You should also be aware of the fact that attaching to the BTSNTSVC.EXE does
not work for messages received through the HTTP adapter. In this case you'll
need to attach to DLLHOST.EXE (Win XP) or W3WP.EXE (Win 2003). This is
because the HTTP Adapter uses the isolated host mode, which means that the
pipeline components are executens in the context of IIS.
Cheers
Stefan Thurow
"Matt Milner" wrote:
> 1) use the pipeline tools in the SDK\Utilities\ folder to test out a
> pipeline configured with your component and see if it works.
>
> 2) create a receive or send with your component in a custom pipeline and run
> it. You can attach to the btsntsvc.exe process and set breakpoints in your
> code to debug. you might also be able to do the same with the pipeline
> tools mentioned in #1, but I haven't tried it.
>
> matt
>
>
> "Aaron" <someone@microsoft.com> wrote in message
> news:%23AHyIpUiEHA.2704@TK2MSFTNGP10.phx.gbl...
>
>
>
| |
| Stefan 2004-08-27, 6:06 pm |
| You should also be aware of the fact that attaching to the BTSNTSVC.EXE does
not work for messages received through the HTTP adapter. In this case you'll
need to attach to DLLHOST.EXE (Win XP) or W3WP.EXE (Win 2003). This is
because the HTTP Adapter uses the isolated host mode, which means that the
pipeline components are executens in the context of IIS.
Cheers
Stefan Thurow
"Matt Milner" wrote:
> 1) use the pipeline tools in the SDK\Utilities\ folder to test out a
> pipeline configured with your component and see if it works.
>
> 2) create a receive or send with your component in a custom pipeline and run
> it. You can attach to the btsntsvc.exe process and set breakpoints in your
> code to debug. you might also be able to do the same with the pipeline
> tools mentioned in #1, but I haven't tried it.
>
> matt
>
>
> "Aaron" <someone@microsoft.com> wrote in message
> news:%23AHyIpUiEHA.2704@TK2MSFTNGP10.phx.gbl...
>
>
>
|
|
|
|