Message Archiving Receive Pipeline Component

Update: The Message Archiving Component is now maintained by Atomic-Scope, visit http://www.atomic-scope.com/downloadtrial for more information.

Today I’m releasing a message archive receive pipeline component (BTS06 only) – I’ve been meaning to release the code for this component for some time, but never got around to it.

The component is designed to be used in the decode stage of a receive pipeline to archive a message before any BizTalk processing (with the exception of the adapter) is started. An output directory and filename can be specified in the component properties, with the following macros (which will be expanded to their real-world values) available in the filename:

  • %MessageID% – Expands to the unique Message Id;
  • %ReceivedFileName% – Expands to the received filename, less the extension;

the remainder all expand to their context property values:

  • %InboundTransportLocation%
  • %InterchangeID%
  • %ReceivePortID%
  • %ReceivePortName%
  • %AuthenticationRequiredOnReceivePort%
  • %InboundTransportType%
  • %MessageExchangePattern%
  • %PortName%
  • %ReceivePipelineID%

For example, specifying an archive filename of:

%ReceivedFileName%-%MessageID%.xml

with a file called ‘TestArchive.xml’ will produce an output filename of:

TestArchive-{2AABABE3-4D25-4A5E-A730-E4B9A71B23F7}.xml

The VS project (including full source-code) can be found in the downloads area under ‘Message Archiving Receive Pipeline Component’ (a 14Kb zip file). Details of how to make the compiled binary available in a BizTalk project can be found here.

Advertisements

One thought on “Message Archiving Receive Pipeline Component

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s