Content-based Routing
If you are sending non-EDI data, you can use all of the IBM Sterling B2B Integration SaaS services. (You might have to define your file formats ahead of time with Customer Support.) You can do this by using a fixed-length format for flat files or by enveloping your non-EDI data in private header/trailer records. Data can be batched for multiple receivers, and B2B Integration SaaS will parse the data accordingly. The one exception is that binary data.
Content-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:
- The header and trailer records must be consistent and identifiable.
- A 1–5 byte record identifier must start in position 1.
- The Receiver ID must be in the first 133 bytes of the header record.
- The record length cannot exceed 4096 bytes.
- Variable-length records must have a predefined segment terminator (using the private header/trailer records).
- Fixed-length records must be predefined to B2B Integration SaaS during the implementation process. (Contact Customer Support for details.)
- The Sender ID is optional. However, if you use one, it must be in first 133 bytes.
- The Control Number is optional. However, if you use one, it must be in first 133 bytes.
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 data must include a unique string (1 byte to 2 gigabytes long) that is consistently located within the file.
- The Sender ID, Receiver ID, and Control Number can be pulled from anywhere within the data or can be hard coded.
- The data can include both fixed- and variable-length records in the same file.
- The data can include binary segments (variable length with segment terminator).
- The data cannot include multiple character terminators (CR/LF).