IBM Sterling B2B Integrator

The transaction engine Sterling B2B Integrator executes the operations you specify and controls them in accordance with your business needs. Its platform allows flexible interface with numerous internal systems and outside business partners, high-volume electronic message transmission, complicated routing, and translation.

The strategic configuration of Sterling B2B Integrator is created around the particular procedures essential to the success of your business. It covers your integration needs for batch and transaction-oriented processes and is compatible with conventional Electronic Data Interchange (EDI) protocols and web-based XML protocols. You can make it possible for your current systems to include technological advancements from the past, present, and future.

Instead of using the simple mail transport protocol (SMTP) as the transport protocol, AS2 offers an Internet solution for securely sending EDI over the Internet using Multipurpose Internet Mail Extensions (MIME) and the hypertext transmission protocol (HTTP). AS2 outlines the methods for securely connecting, sending, validating, and responding to (receiving) data. Only the transfer of the EDI document is important to AS2, not its content.

As a result of AS2, EDI flat files can be transferred over the Internet rather than through a dial-up connection to a value-added network (VAN). AS2 is a real-time solution that encrypts and offers security for HTTP traffic.

In Sterling B2B Integrator, a business process is a series of linked software and possibly human activities that accomplishes a business goal. The activities in a business process are primarily performed by components known as services and adapters and are orchestrated by the Sterling B2B Integrator integration engine.

The signing and encrypting of emails and data is the PGP feature that is most frequently used. A file can be “signed” to confirm the accuracy of the original work.
This is how it’s done:

Make a “hash” or digest of the email or report. A hash is a collection of rules that, in theory, creates a unique output from an input (the message). Add the hash to the message’s quit. When someone wishes to make sure that a message hasn’t been altered, they run it through the hash set of rules and compare the results to the hash at the message’s end. The message has not been changed if the signatures are valid.