Posts Tagged ‘Pipeline Components’
I ran across a few things that I needed to update and have posted them here as well.
Notable changes include:
Added Pipeline Component property of Extension. This allows you to specify what extension you want to place at the end of your encrypted file. The default value is PGP.
Added capability to decrypt a signed message.
Updated decryption to handle other than .PGP extension. Previously hard coded to remove only the .pgp from the filename.
Updated TestFixture form to be more user friendly. You can now specify where you want your output file to be generated.
Minor code changes that don’t necessarily affect logic, but may [...]
read more
So let me break this down for you…
Company A (Acme, Inc) wants to exchange data with Company C (Charlie Company). However, I represent Company B (BizTalk United) and we want to collect some of the data as well. A requirement has been made that all data will be transmitted using FTP and will also be encrypted. So, as the broker of the integration, I must resolve how to get data from point A to C and still be able to read the data myself.
The solution:
Company A will encrypt their file using the public key from Company B and transmit the [...]
read more
Recently I was required to perform some PGP encryption and decryption of files. Realizing this was going to require a custom Pipeline Component, off I went to Google to find one. Hey, why reinvent the wheel.
I’m not certain why Microsoft didn’t put one in place with the release of BTS 2006, but who am I to judge.
The ones that kept popping up:
Gnu Privacy Guard (GPG/PGP) for .NET [v1.0]
Pro BizTalk 2006 (Pro) (Paperback) by George Dunphy (Author), Ahmed Metwally (Author)
And a few others that wanted you to buy it. Sorry, but I’m [...]
read more
Ok. So this isn’t the fanciest of things, but it really saved my bacon.
Problem: I have a predefined flat file schema to transform a fixed-length positional file. However, for some unknown reason, random records in the file extend beyond extend beyond the specified record length. I was able to deduce that those records consistently contained a certain value instead of what was expected. They should have been passing a series of zeroes, but instead converted them to decimals. Instead of 00000000 I was getting 00000000.00000000. I tried a few other solutions, but wound up with the need for a custom [...]
read more
|

|