|
|
|
This component sends data securely and reliably using the AS2 (Applicability Statement 2)
specification, an optionally encrypted and/or optionally signed SMIME based protocol, sent via HTTPS or HTTP.
AS2 is the definitive new messaging standard for secure message exchange over
the Internet, based upon certificate securiity and the S/MIME protocols. It
enables the sender of a message to know that a message has been delivered
successfully, the receiver to know that the message definitely originated from
the apparent sender, and both parties to know that the message was not
interfered with or corrupted in transit. Where appropriate the message can be
securely encrypted. AS2 is essentially HTTP based, enabling messages to be sent
synchronously and directly.
This component is configured in the usual way by dragging it onto a SQL Server
Integration Services control flow surface, and then double-clicking to display
the Configuration form.
Configuration
The
initial tab (above) allows you to set the content of the message to be sent by choosing the Message variable,
a variable from which the content will be taken at execution time. You can also optionally
select a Message Id variable, into which the generated unique identifier of the message will be placed.
Note - messages are generally assumed to be in text form unless your Message
variable is of type Object, in which case the message is retrieved as a binary
array (byte[]). Conversion between text and binary representations is
performed as required according to the Encoding property, accessible only
through the SQL Server Integration Services Property window.
Addressing
The Addressing tab (shown above) facilitates the setting for header, transport and security. The To, From
and Subject can be any phrase known between you the sender and the recipient (or partner).
The destination URL needs to be a http or https address, and if the User Id
is not set as <Anonymous> or <Windows>, a password should be provided. Selecting the security settings
Encrypt and/or Sign (both optional) produces
the pop-up windows detailed below.
This window is different in that each tab displays a particular certificate source. e.g (above), the <Local Machine / TrustedPeople> store is selected, and the available
certificates (one in this case) are listed below it.
The second choice is to paste in the raw certificate data (base64 encoded) using the link or Ctr-V.
The image above shows the window after a certificate has been pasted in.
The final choice is to load from file as shown above. The file can be either a .pxf Personal Information
Exchange file, a .cer Internet Security Certificate file, or a .crt GlobalSign Certificate File.
If you need to generate a certificate, you can use the makecert.exe utility, which can be found in the BlueSSIS installation folder. The following command-line will create a certificate called AS2Cert in a file C:\Certificates\AS2Cert.Cer, and register it in the Local Machine / My store.
makecert.exe -r -pe -n CN="AS2Cert" -b 01/01/2010 -e 01/01/2036 -sky exchange -sr LocalMachine -ss my -pe "C:\Certificates\AS2Cert.Cer"
For more details on this tool, we recommend that you Google makecert.exe.
Receipt
Back to the configuration, the last tab is displayed below.
This tab is for requesting a MDN (Message Disposition Notification). The Request receipt drop down has three choices; No
Receipt
will not request any notification, Synchronous, signed will request a signed notification,
and Synchronous, unsigned an unsigned notification.
The notifications will be returned over the same HTTP connection that was used to send the original message.
|
|
|
|
|