Context-based Routing

If your non-EDI data does not need any value-added processing (parsing, translation) by IBM Sterling B2B Integration SaaS, you can used context-based routing. Any non-EDI data that is not fixed-length flat file or wrapped in private header/trailer records is treated as context-based routing. (This data can include XML files, MS Office files, CAD/CAM drawings, and PDF files.) You can still use several of the B2B Integration SaaS services, such as Document Tracking, mailslot carbon copy, and control reports, although the level of detail is different from content-based routing. Another difference is that data cannot be batched–each file can only contain data for only one recipient.

Data is routed based on how it is sent to SCN. For example:

  • For FTP, routing is based on which directory the file is placed in
  • For AS2, routing is based on the AS2_To name.

Context-based routing can be used with any B2B Integration SaaS-supported protocol. However, there are different requirements depending on which protocol you are using.

If you are using async, Connect:Direct, FTP (using the sciftp.commerce.stercomm.com URL), or MQ, the following requirements apply:

  • Everything from a specific sender mailslot is routed to a unique receiver mailslot (1-to-1 relationship).
  • IDs are assigned (for Document Tracking).
  • FTP users can log on to multiple slots during the same communications session and “put” files for multiple recipients.
  • MQ users can place messages for specific receivers on the appropriate queues (one queue per receiver).

If you are using AS1, AS2, FTP (using the ftp.gts.globalec.com URL), HTTP/S, SMTP, or X.400 the following requirements apply:

  • The sender decides which recipient the file is delivered to based on which folder they put data in.
  • The sender has more flexibility–they can ‘put' multiple files in multiple directories for multiple recipients.
  • SMTP is based on the receiver's email address, which must use FTP, X.400, or SMTP.

Binary Data Transfer Support

Binary data is sent in a type of file that contains binary data (such as PDF files) or a machine-readable computer program.

You can send binary data through B2B Integration SaaS:

  • In the ANSI X12 Bin segment in the 841 transaction set
  • In a document complying with the ANSI X12.58 security structure
  • Using context-based routing

Binary data transfer support is available in most countries for the ANSI X12 EDI standard only.