We have a scenario wherin we receive flat files from UNIX and windows
environment and send flat files to Unix and Windows Environment. In UNIX the
line terminator is LF whereas in Windows it CRLF.

1) If we change the Flat File schema delimiter to cater to Unix environment
it will not work for windows environment. and vice versa.

2) Is that only by writing a .net component which will read the whole input
flat file and add CR to LF in case of file being received from unix
environment and remove CR from CRLF in case we are sending files to UNIX
environment.

3) If we write a .net component and use it in pipelines, what should be the
approach to improve the performance.

4)If we write a .net component and use it in Orchestration, what should be
the approach to improve the performance.

5)Is there any other way we can do this...in BizTalk Server 2004.

Thanks Much.

[ Post a follow-up to this message ]

Nateshan,

If it is possible, put unix and win files into different folders (or
different file names). The idea is to direct them to different ports.
Then create flat file schema and receive (send) pipeline for each type
of file.

[ Post a follow-up to this message ]

Hi Natesan,

You've not specified how you get the files across from/to the UNIX system ?

The problem of CrLf conversion is done by the FTP mechanism under the ASCII
transfer mode. If you incorporate the receive into BTS over FTP and Transmit
onto UNIX Through FTP, you should not see this issue.
--
Ravi Shankar


"Nateshan" wrote:

> We have a scenario wherin we receive flat files from UNIX and windows
> environment and send flat files to Unix and Windows Environment. In UNIX t
he
> line terminator is LF whereas in Windows it CRLF.
>
> 1) If we change the Flat File schema delimiter to cater to Unix environmen
t
> it will not work for windows environment. and vice versa.
>
> 2) Is that only by writing a .net component which will read the whole inpu
t
> flat file and add CR to LF in case of file being received from unix
> environment and remove CR from CRLF in case we are sending files to UNIX
> environment.
>
> 3) If we write a .net component and use it in pipelines, what should be th
e
> approach to improve the performance.
>
> 4)If we write a .net component and use it in Orchestration, what should be
> the approach to improve the performance.
>
> 5)Is there any other way we can do this...in BizTalk Server 2004.
>
> Thanks Much.
>

[ Post a follow-up to this message ]

The problem is we are using SFTP Adapter...and it reads only in binary
mode....thats where the actual problem is

"Ravi Shankar" wrote:
[vbcol=seagreen]
> Hi Natesan,
>
> You've not specified how you get the files across from/to the UNIX system 
?
>
> The problem of CrLf conversion is done by the FTP mechanism under the ASCI
I
> transfer mode. If you incorporate the receive into BTS over FTP and Transm
it
> onto UNIX Through FTP, you should not see this issue.
> --
> Ravi Shankar
>
>
> "Nateshan" wrote:
> 

[ Post a follow-up to this message ]