Skip Headers
Oracle® Fusion Middleware User's Guide for Oracle B2B
11g Release 1 (11.1.1.7)

Part Number E10229-13
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

C Synchronous Request/Reply Support

This appendix describes how to configure Oracle JDeveloper and Oracle B2B to enable synchronous request and reply support in Oracle B2B.

The appendix contains the following topics:

C.1 Introduction

Oracle B2B provides synchronous request/response between from Fabric to Oracle B2B. However, only HTTP transport is supported for the initial release. Figure C-1 shows the end-to-end scenario.

Figure C-1 Synchronous Request/Reply

Description of Figure C-1 follows
Description of "Figure C-1 Synchronous Request/Reply"

C.2 Configuring Sender

To configure the sender, you need to perform the following tasks:

C.2.1 Configuring Oracle JDeveloper

You need to use B2B Configuration Wizard in Oracle JDeveloper to configure the sender for synchronous request/reply support:

C.2.2 Configuring Oracle B2B

In Oracle B2B console, you need to:

  • Set up Oracle B2B agreements: You need to define two agreements. One agreement is required to send the Request, and the other agreement is needed to receive the Response as shown in Figure C-4. You do not need to set up any Oracle B2B property for this. Based on the call from the Fabric to Oracle B2B, the message type "sync request" is determined.

    Figure C-4 Setting Up Oracle B2B Agreements

    Description of Figure C-4 follows
    Description of "Figure C-4 Setting Up Oracle B2B Agreements"

  • Create a Trading Partner channel: You need to create a remote Trading Partner Channel to point to http://server:port/b2b/syncreceiver as shown in Figure C-5. This is required if the communication is between two Oracle B2B products. Please note that the URL will be different if the communication takes place between two different B2B products.

    Figure C-5 Creating a Trading Partner Channel

    Description of Figure C-5 follows
    Description of "Figure C-5 Creating a Trading Partner Channel"

C.3 Configuring Receiver

To configure the receiver, you need to perform the following tasks:

C.3.1 Configuring Oracle JDeveloper

You need to use B2B Configuration Wizard in Oracle JDeveloper to configure the receiver for synchronous request/reply support:

C.3.2 Configuring Oracle B2B

In Oracle B2B console, you need to:

  • Set up Oracle B2B agreements: You need to define two agreements. One agreement is required to receive the Request, and the other agreement is needed to send the Response as shown in Figure C-8. You do not need to set up any Oracle B2B property for this. The synchronous HTTP receiver decides the message type as "sync request".

    Figure C-8 Setting Up Oracle B2B Agreements

    Description of Figure C-8 follows
    Description of "Figure C-8 Setting Up Oracle B2B Agreements"

  • Create a dummy Trading Partner channel: You need to create a dummy remote Trading Partner Channel, but this channel is not used at runtime. You can specify any URL value, but the value needs to be in the format http://host:port/xyz as shown in Figure C-9.

    Figure C-9 Creating a Dummy Trading Partner Channel

    Description of Figure C-9 follows
    Description of "Figure C-9 Creating a Dummy Trading Partner Channel"

C.4 Resubmitting Messages

Synchronous request or response resubmit must be done from the Application side. Although the Oracle B2B console allows resubmit of Application or Wire messages from Oracle B2B, however, it resubmits the messages in the as nonsynchronous mode. Sometimes, the message processing logic is nondeterministic. For example, if an Application or a Wire message is resubmitted from Sender side Oracle B2B, the message is posted to http://server:port/b2b/syncreceiver. The Receiver Oracle B2B processes the message as synchronous request or response. The response message on the Sender side is ignored.