EDIINT Header Scanning Service

The following table provides an overview of the EDIINT Header Scanning service:

System name
None
Graphical Process Modeler (GPM) categories
All Services
Description
This service parses the header area of EDIINT messages and other MIME-based messages without loading or examining the entire message and outputs the header information to process data.

This service is currently used by the EDIINTParse business process to scan message headers prior to parsing the message, to determine whether the sender of the message is an AS2 trading partner for which deferred extraction has been configured.

The EDIINTParse business process currently uses this service to help determine whether the sender of the message is an AS2 trading partner for which deferred extraction has been configured. The value from the AS2-To header is needed to determine whether the sender is a trading partner in the AS2 Trading Partner Information database table, and, if so, whether the deferred extraction behavior has been enabled for the sender. This service can be used to scan the headers of MIME-based messages for any purpose.

Business usage
A user has implemented deferred extraction behavior for a trading partner that sends AS2 messages.
Usage example
An example of the usage of this service when you are using the IBM® Sterling B2B Integrator AS2 Edition is as follows:
  1. Sterling B2B Integrator receives an AS2 message.
  2. A business process is invoked to process the message.
  3. The business process invokes the EDIINT Header Scanning service to determine whether deferred extraction of the payload should occur.
  4. The EDIINT Header Scanning parses the header information and outputs it to process data.
  5. Any situation in which you need to parse the header area of MIME-based messages and load that information to process data.
Preconfigured?
Yes.
Requires third party files?
No.
Platform availability
All supported application platforms.
Related services
This service is used in conjunction with the EDIINT Pipeline service and the EDIINT MDN Building service.
Application requirements
No.
Initiates business processes?
No.
Invocation
Used in the EDIINTParse business process. Can be used in any business process for which this functionality is desired.
Restrictions
No.

How the EDIINT Header Scanning Service Works

The following steps summarize how the EDIINT Header Scanning service works within a business process:

  1. The EDIINT Header Scanning service parses the header area of each EDIINT message (without loading or examining the message).
  2. The EDIINT Header Scanning service outputs the header information to process data.

Implementing the EDIINT Header Scanning Service

To implement the EDIINT Header Scanning service, complete the following tasks:

  1. Activate your license for the EDIINT Header Scanning service.
  2. Create an EDIINT Header Scanning service configuration. You can also modify the EDIINTHeaderScan predefined service instance.
  3. Configure the EDIINT Header Scanning service only once in the user interface and the GPM.
  4. Use the EDIINT Header Scanning service in a business process.

Configuring the EDIINT Header Scanning Service

To configure the EDIINT Header Scanning service, you must specify settings for the following fields in the IBM Sterling B2B Integrator one time only.

Field
Description
Name
Unique and meaningful name for the service configuration. Required.
Description
Meaningful description for the service configuration, for reference purposes. Required.
Select a Group
Select one of the options:
  • None – You do not want to include this configuration in a group at this time.
  • Create New Group – You can enter a name for a new group in this field, which will then be created along with this configuration.
  • Select Group – If you have already created one or more groups for this service type, they are displayed in the list. Select a group from the list.
Show transcripts
Whether to enable extended logging to the advanced status shown in the process monitor. Valid values are Yes (default) and No. Required.
Protocol
The communications protocol through which the message was received. The HTTP Server adapter supplies the value for this parameter when it receives a message.
Note: For AS2, this parameter should always be set to http.

Process Data Example

This example shows the EDIINT Header Scanning service used to output header information to process data:


<MIMEEntity name="test2:00.000.00.00:1135fdf492d:72484">
    <EDIINT-Message-Sender>test1_as2</EDIINT-Message-Sender>
    <EDIINT-Message-Recipient>test2_as2</EDIINT-Message-Recipient>
    <content-type>application</content-type>
    <content-subtype>pkcs7-mime</content-subtype>
    <content-type-parameters>
      <content-type-parameter 
name="smime-type">enveloped-data</content-type-parameter>
      <content-type-parameter name="name">smime.p7m</content-type-parameter>
    </content-type-parameters>
    <content-transfer-encoding>7bit</content-transfer-encoding>
    <content-location/>
    <content-id/>
    <OtherMIMEEntityHeaders>
      <OtherEntityHeader name="host"><![CDATA[test2:16033]]></OtherEntityHeader>
      <OtherEntityHeader name="user-agent">
       <![CDATA[SI/PsHttpClientAdapter]]></OtherEntityHeader>
      <OtherEntityHeader name="as2-version"><![CDATA[1.1]]></OtherEntityHeader>
      <OtherEntityHeader name="as2-to"><![CDATA[test2_as2]]></OtherEntityHeader>
      <OtherEntityHeader 
name="as2-from"><![CDATA[test1_as2]]></OtherEntityHeader>
      <OtherEntityHeader name="message-id">
       
<![CDATA[<MOKOyama-1477dadd-11363544df4--6514test10as2@test1>]]></OtherEntityHead
er>
      <OtherEntityHeader name="date">
       <![CDATA[Mon, 25 Jun 2007 03:57:11 GMT]]></OtherEntityHeader>
      <OtherEntityHeader name="subject">
       <![CDATA[Integrator Message]]></OtherEntityHeader>
      <OtherEntityHeader name="disposition-notification-to">
       <![CDATA[test1_as2]]></OtherEntityHeader>
      <OtherEntityHeader name="disposition-notification-options">
       <![CDATA[signed-receipt-protocol=optional,pkcs7-signature;signed-receipt-
        micalg=optional,sha1]]></OtherEntityHeader>
      <OtherEntityHeader 
name="content-length"><![CDATA[2305]]></OtherEntityHeader>
      <OtherEntityHeader 
name="uri"><![CDATA[/b2bhttp/inbound/as2]]></OtherEntityHeader>
    </OtherMIMEEntityHeaders>
    <EntityBody name="unknown">
      <Data/>
      <DocumentID/>
    </EntityBody>
</MIMEEntity>