03-24-04 10:59 PM
If all you need is to receive a message and convert it to a flat file,
there's no need for a custom component most likely.
I'm assuming you have created a schema for the inbound and outbound
documents? The BizTalk editor should be able to create a schema to
describe most flat-file formats, just add a new schema, open it, highlight
the <schema> element and in the properties window go to the Schema Editor
Extensions entry and add the flat-file extensions. With this enabled you
have a few additional properties to add delimiters and such to your schema
to describe the flat-file format you are using.
If you want to validate a native instance of your file, or generate an
instance, right click on the schema in the Solution Explorer window and
select properties. Here you can set the instance to create and to validate
along with whether the instance will be xml or native (flat-file in this
case.)
Next create a new project, call it flat-file pipeline or something like
that. Add a new item and select a send pipeline. Open up the pipeline you
added, go to the toolbox and drag the Flat-File assemblier and drop it on
the assembler stage in the pipeline. Now go right click on references and
add a reference to the dll you compiled with your schemas.
Select the flat-file assembler, should get a properties window on it. Set
the document schema to the flat-file outbound schema from your assembly.
Will be all the way at the bottom of the list most likely.
Compile this, copy the dll for this project to \microsoft biztalk server
2004\pipeline components.
Now if you create a send port you should have the option of selecting the
flat-file pipeline you just created. Let me know if you have questions on
this.
Larry Franks
This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| Thread-Topic: Custom pipeline
| thread-index: AcQRsNd18OjM9vKnTdivpIrLyHI+HA==
| X-Tomcat-NG: microsoft.public.biztalk.orchestration
| From: examnotes <anonymous@discussions.microsoft.com>
| References: <D1B394B9-C9D0-445A-BA8E-A35354FF64AE@microsoft.com>
<rWayTZQEEHA.2956@cpmsftngxa06.phx.gbl>
| Subject: RE: Custom pipeline
| Date: Wed, 24 Mar 2004 07:01:09 -0800
| Lines: 5
| Message-ID: <7115DA48-856A-42C6-84AC-6B47D62C6C8D@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.biztalk.orchestration
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.orchestration:5267
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.biztalk.orchestration
|
| Hello Larry,
Yes I am trying to write a custom component pipeline. I have looked at the
sdk sample, but just by looking at it, I don't understand it enough to know
what is the minimum I need to write to interface my component with my
Orchestration business process. Basically I just want to be able to
receive a message and convert it to a propietary flat file and send it to
the trading partner. There is no place in the BT 2004 doc that states that
if you want to write a custom comp. pipleline do these steps.
|
[ Post a follow-up to this message ]
| 
