Configuring a virtual file system pull destination

The virtual file system pull destination is the message partition channel from which B2B Advanced Communications pulls the message response. In a RESTful HTTP or HTTPS message exchange, the messages that can be pulled by a trading partner are stored in the virtual file system pull destination. You can configure a destination to enable a trading partner to retrieve files from your system with a RESTful HTTP or HTTPS inbound one-way pull exchange. Use Destinations to create and configure a virtual file system pull destination

Before you begin

You also can import a destination as a resource from another installation of B2B Advanced Communications.

About this task

To create a virtual file system pull destination, complete the following procedure:

Procedure

  1. Log in to B2B Advanced Communications.
  2. Click Exchanges > Destinations.
  3. On the Destinations page, click New and select Virtual File System Pull.
  4. On the Create virtual file system pull destination page, specify values for the applicable fields as follows:
    Associated Organization

    Click Select and select the owner organization with which the virtual file system pull destination is associated.

    Name

    Type a name for the destination.

    Description

    Optional: Type a description for the destination.

    Virtual file system
    The virtual reference point from which an organization retrieves a pull response or to which a pull request is sent. Click New Virtual File System to add a new reference point.
  5. Click Save to save the virtual file system pull destination. The new virtual file system pull destination is listed on the Destinations page.
    Tip: To change the properties, click the destination Name on the Destinations page, and click Edit next to the property you want to change.
  6. Click the destination link to view the details of the virtual file system pull destination.

What to do next

After you configure a virtual file system pull destination, you can use the destination in a RESTful HTTP or HTTPS inbound one-way pull exchange. To conduct an exchange with HTTP or HTTPS, you must configure a RESTful HTTP or HTTPS exchange profile. For more information about configuring a RESTful HTTP or HTTPS inbound one-way pull exchange, see Configuring a RESTful HTTP or HTTPS inbound pull exchange profile.