Hubs

Updated: June 5, 2020
Contents

Overview

To use a commerce platform infrastructure in Connect, the provider (the platform owner) must register this platform as a hub. A hub enables the provider to present vendor products for customers.

A provider can register as many hubs as they need. Every hub represents a separate infrastructure used for a certain purpose, for example:

  • To serve as a production or test (lab) hub
  • To cover different geographical regions

Regarding the first purpose in the above list, when requesting a connection to a vendor, the provider must specify whether that connection is used for testing or production.

Registering a Hub

When registering a hub, the provider (the hub owner) must ensure a secure connection between Connect and a server that represents the hub. The Connect CLI tools installed on that server assist in creating a secure connection. These tools enable the provider to generate a hub access token (to authorize that hub in Connect) by running the following command:

# apsconnect hub-token
ab8719ff-d818-4b6f-8023-0229f768e086

The generated token command returns the token that you must supply in the provider portal for the hub registration.

After completing his step, open the provider portal and navigate to the Hubs manager:

On the Hubs screen, click REGISTER:

In the popup, enter the requested data:

  • Name: a descriptive name that identifies the hub to be registered in Connect. This name is used in various Connect modules, for example, it is used in reports on requests to display hubs where the requests are originated from.
  • Description: a short description of the hub.
  • Token: the hub token obtained as the output of the command apsconnect hub-token described earlier.

After filling this pop-up form, click REGISTER. You can use the registered hub to request connections to vendors. 

Is this page helpful?
Translate with Google
Copied to clipboard