Scenarios
Scenarios provide a concise description of how a particular user might use B2B Advanced Communications or use B2B Advanced Communications with Sterling B2B Integrator to achieve a goal.
These scenarios provide cross-component and multiproduct solutions, and they link to tasks and concepts to furnish extra details. These scenarios are intended to help you understand how to use B2B Advanced Communications to meet your business needs.
- Scenario: Installing B2B Advanced Communications
One scenario for the installation of B2B Advanced Communications is a minimum high availability installation that connects to Sterling B2B Integrator. - Scenario: Creating a user profile with a new owner organization
You can create a new user profile that you can associate with a new owner organization. You can then assign that owner organization to an exchange profile that can be used by only the new user. - Scenario: Receiving an AS2 inbound request
An exchange profile defines how messages are exchanged with a trading partner, and how those messages are processed internally. You can exchange data and messages synchronously or asynchronously with your trading partner using the AS2 protocol based on the requirements and agreement. - Scenario: Sending an AS2 outbound request
An exchange profile defines how messages are exchanged with a trading partner, and how those messages are processed internally. You can exchange data and messages synchronously or asynchronously with your trading artner using the AS2 protocol based on the requirements and agreement. - Scenario: Receiving an AS4 inbound two-way synchronous request
In an inbound exchange, a synchronous exchange pattern is used when the sender needs an immediate processing and acknowledgement or response of the request that is sent. The sender must wait until B2B Advanced Communications and the business application process the request and send an appropriate response. - Scenario: Receiving an AS4 inbound one-way push request
An inbound one-way push message exchange pattern (asynchronous) is used to receive catalog updates, product promotions, or periodical status updates on order status or tax return from your trading partner. - Scenario: Receiving an AS4 inbound two-way push pull response
A two-way push pull message exchange pattern (asynchronous) is used when the receiver (of the request) requires more time to process the request or the sender does not want to (or cannot) stay idle until the response arrives. - Scenario: Receiving an AS4 inbound one-way pull request
A one-way pull exchange involves the transfer of a single user message unit. The one-way pull exchange pattern is initiated by the receiving message service handler. - Scenario: Sending an AS4 outbound two-way synchronous request
In an outbound exchange, you can use a two-way synchronous exchange pattern when you want your trading partner to process your request immediately and provide an acknowledgement or a business response. In a two-way synchronous exchange, the sender must wait until the request is processed and an appropriate response is received. - Scenario: Sending an AS4 outbound one-way push request
An outbound one-way push message exchange pattern (asynchronous) is used when you want to send catalog updates, product promotions, or periodical status updates on order status or tax return submits to the trading partner. - Scenario: Sending an AS4 outbound two-way push pull response
A two-way push pull message exchange pattern (asynchronous) is used when the receiver (responder or consumer) of the request requires more time to process the request (large documents) or the sender (initiator or producer) does not want to wait until the response arrives. - Scenario: Sending an AS4 outbound one-way pull request
A one-way pull exchange involves transfer of a single user message unit. The one-way pull exchange pattern is initiated by the receiving message service handler. - Scenario: Sending a receipt to a purchase order with an SFTP exchange
Your partner can also retrieve a purchase receipt with an SFTP inbound one-way pull exchange. - Scenario: Receiving a purchase order with an SFTP exchange
You can enable a trading partner to deposit a purchase order with an SFTP inbound one-way push exchange. - Scenario: Receiving a deposit receipt from the bank with an SFTP exchange
You can also request and retrieve a deposit receipt from your bank with an SFTP outbound one-way pull exchange. - Scenario: Making a deposit to the bank with an SFTP exchange
You can send a deposit to an affiliated bank with an SFTP outbound one-way push exchange. - Scenario: Configuring the bridge adapters for AS2 inbound EDI exchanges
You can use the AS2 inbound exchange pattern for Sterling B2B Integrator to process documents sent from B2B Advanced Communications. - Scenario: Configuring the bridge adapters for AS2 outbound EDI exchanges
You can use the AS2 outbound exchange pattern for B2B Advanced Communications to receive processed documents from Sterling B2B Integrator. - Scenario: Configuring the bridge adapters for AS4 inbound two-way push-pull exchanges
You can use an inbound two-way push-pull exchange pattern for Sterling B2B Integrator to process your request and provide an acknowledgment or a business response later. - Scenario: Configuring the bridge adapters for AS4 outbound two-way push-pull exchanges
You can use an outbound two-way exchange pattern for Sterling B2B Integrator to send a processed document to B2B Advanced Communications and receive an acknowledgment or a business response later. - Scenario: Configuring the bridge adapters for AS4 outbound two-way sync exchanges
You can use an outbound two-way synchronous exchange pattern to send documents to a trading partner with AS4 and get a response. - Scenario: Configuring the bridge adapters for AS4 inbound two-way sync exchanges
You can use an inbound two-way synchronous exchange pattern for Sterling B2B Integrator to process your request and provide an acknowledgment or a business response. - Scenario: Developing authentication user exits
To develop authentication user exits, you must develop OSGi services that include the provided user exit APIs. - Scenario: Developing destination user exits
To develop destination user exits, you must develop OSGi services that include the provided user exit APIs. - Scenario: Developing receiver user exits
To develop receiver user exits, you must develop OSGi services that include the provided user exit APIs. - Scenario: Configuring user exits in AS4 destinations
To configure AS4 HTTP or HTTPS destinations with user exits, you must deploy the user exit OSGi services that you developed with the provided user exit APIs. - Scenario: Configuring user exits in AS4 receivers
To configure AS4 receivers with user exits, you must deploy the user exit OSGi services that you developed with the provided user exit APIs.
Parent topic: B2B Advanced Communications