B2B Framework^® for Sterling Integrator

Overview

B2B Framework^® for Sterling Integrator provides a set of generic business processes for all Sterling Integrator supported communication protocols, with consistent tracking and error notification for all message and document processing.

1. Receive Protocol Handlers. Triggered by messages from internal business systems or external trading partners. Validation of channel (security) and collection of metadata.
2. Collect. Scheduled collection of messages from email, FTP, etc.
3. Receive. Logs message information. Queries Receive Rules for routing information. Routes non-structured data based on message attributes.
4. Identify & Split. Message split into individual documents if required. Core message identification attributes identified (Source, Destination, etc.), and Split Rules queried. EDI messages de-enveloped as required.
5. Route. Logs document and queries Route Rules using the document metadata. Optionally calls the Pre-Process, Core Process, Post-Process and Send Process.
6. Pre-Process. Optional process to, for example, extract business information from a document before translation, saving it to a database for future reporting.
7. Core Process. Optional process typically verifying and/or translating the document.
8. Post-Process. Optional process to, for example, replace or remove certain characters from the document before it is sent
9. Send. Optional process logging status and delivering message to its ultimate destination. Queries Send Rules to determine how to send the message.
10. Post-Send Process. Optional configurable process for additional processing after successful send.
11. Send Protocol Handlers. Processes called to send messages over the various communication channels. Provides retry and recovery logic. Destination can be internal business systems or an external trading partner.

Other Framework Functions

Sterling Integrator Mailbox (Optional)

• Provides core “Store and Forward” function for managing sending/receiving messages
• Acts as server for FTP/SFTP client connections. Can also interface to Connect:Direct
• All other non-Mailbox protocols can store copies of any messages sent or received
• Partners can use the Mailbox Client GUI to access Message History
• Alert Rules
• Allow Error notifications to be routed to selected parties based on document meta-data (Source, Destination, Document Type and Error Type)

Document Management Interface (DMI)

• Pre- and post-processing, allows all documents processed to be searched and viewed through a common portal
• Standard functions for reprocessing or resending messages and documents which trigger execution of Sterling Integrator Business Processes

Got Questions?

If you have any questions, please don't hesitate to contact us via email or phone: 866.595.6700