Here is a list of the behaviors that I have found when using the custom pipeline component vs the adapter for receiving and sending data:
Pipeline
- Allows multiple recieve ’locations’ for a single party, where you define a receive location that has the configuration information and then multiple pick ups and drop offs, where they can be any adapter (file, ftp, http, MQ Series, etc.) can be used
- Ability to use Send Port Groups (archiving is an example of this usage)
- Does not check the interchange control number for duplication per party
- Data that is recieved or sent, is not archived in the location defined in the documentshome location in the parame table
- No information is logged to the audin and audout tables, so the HIPAA_EDI reports in HAT is not available
- Promoted properties in the WPC schemas are not invoked
Adapter
- Only a single port can be defined for receiving and sending
- Copies of both edi and xml data is stored in the documentshome location
- Interchange control number checking is done
- Information is stored in the audin and audout tables, so the HIPAA_EDI reports are accessable
- Using the DefaultXML pipelines; promoted properties can be used for correllation/filtering/orchestration usage
I have put together a really simple example of both usages, so differences can be seen.
Instructions:
- Deploy the Solution
- Using the Deployment wizard, import the Binding.xml file
- In the Management Console, in the HIPAA_EDI adapter, in the properties of the Send Handler, set the the Party to Us
- Restart the HIPAA service
- Enable the Receive Locations
- Start the Send Port
- Drop the file into the ..\input directory and see if the file is produced in the ..\output directory
- Notice the following information in HAT – HIPAA_EDI Reports