- This topic has 1 reply, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
I’m new to Biztalk, and have a project dealing with flat files and a good old mainframe.
I’ve developed a pipeline to read in the flat file, and filter it based on a flag field. I create two output files, one for records to process further in BizTalk, one for data that needs no work (about 98% of the file).
My problem is, both of these end up XML. However, I’d like to have the larger one, that needs no more work , remain in its original flat file format. Is there a way to have the pipeline do that? I’ve seen this question other places, but no solution was given.
Finally, I need to output a flat again, when I’m done with the ones that need work. Getting these as XML is fine. I will be exchanging messages with the MF in XML and doing other things appropriate to BizTalk and XML. These then need to get merged with the other data.
Would it be better to pre-filter the data outside of Biztalk with say a little C# program to split the file in two?
That still leaves me with the problem of merging the data fixed in Biztalk back into the flat file for use by the MF.
-
To output a flat file from Biztalk you need to use a send pipeline with the FlatFile Assembler (this does the opposite of the FlatFile Disassembler) i.e. converts an Xml message into a flat file message. It uses a schema that is defined by the MessageType.
If the output file is the same format as the input flat file then you already have the schema, just create a send pipeline and place the flat file assembler component in the assembler stage, build and deploy. On you send port specify this send pipeline on your send port. You should not need to specify the document schema in the assembler as the outbound message should have the BTS.MessageType property set, which is the key to the schema deployed in BizTalk.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.