1. In Fuse Online, in the left navigation panel, click Integrations.
2. Click Create Integration.
3. On the Choose a connection page, click the API Provider card.
4. Drag the raw version of the task-api.json file that you downloaded to the Upload an OpenAPI file section. Fuse Online displays a message that it has successfully imported the file.

5. Click Next.

   Note

   You can safely ignore the warning messages.

6. Click Review/Edit.

   The API opens in API Designer.

7. Explore the structure of the API. It includes the following components:

   • Two paths (/ and /{id}) with these operations:

     • GET - Get a list of all tasks
     • POST - Create a new task
     • GET - Fetch a task by its ID
     • PUT - Update a task by its ID
     • DELETE - Delete a task by its ID
   • The Task data type

8. To save time, rather than building the integration from this OpenAPI specification, you exit the API Designer and return to Fuse Online so that you can import the entire pre-built integration that is provided in the other quickstart file (TaskAPI-export.zip) that you downloaded in Section 2.3, “Downloading the Task Management API Provider quickstart files”.

   To exit the API Designer, click Cancel three times and then Confirm the cancellation until you return to the Fuse Online dashboard.

Procedure

1. Import the TaskAPI quickstart integration:

   1. In Fuse Online, in the left navigation panel, click Integrations.
   2. Click Import.
   3. Drag the TaskAPI-export.zip file that you downloaded to the Import page. Fuse Online indicates that it has successfully imported the file.
   4. In the left navigation panel, click Integrations to see an entry for the TaskAPI integration that you just imported. Although the entry indicates that configuration is required, this integration is ready to publish.

2. In the TaskAPI entry, click and then click Edit to display a list of the operations that this API provides.

   Each operation has a flow defined for it. In Fuse Online, a flow defines the connections and other steps to execute for each REST operation in the integration. The imported quickstart provides pre-defined flows for each operation.

3. To examine the flows for each operation:

   1. Click its Edit flow button to display the visualization for that flow.

      Each flow already has a database connection, one or more data mapper steps, and a Provided API Return Path step that finishes the flow.

   2. For the Invoke SQL step, click Configure to see the SQL statement that the connection executes. Then click Cancel to return to that operation’s visualization flow.
   3. For a data mapper step, click Configure to see the mappings. Then click Cancel to return to the visualization.
   4. For the Provided API Return Path step, which is the last step in every operation’s flow, click Configure to see the HTTP return codes that the operation might send to the caller. Click Cancel to return to the visualization.
   5. After examining one operation’s flow, click the Integrations> TaskAPI> Operation drop down menu and then select another operation.
   6. Repeat this subset of steps to examine each flow.

4. After examining the flows, click Publish, edit the integration name if you want to, and then click Save and publish.

   Fuse Online displays the summary page for this integration and shows publication progress as it assembles, builds, deploys, and starts the integration.

1. Log in to the 3scale Administration Portal.
2. In the Admin Portal’s dashboard, click New Product.
3. Choose Import from OpenShift.
4. In the Namespace field, specify or select the OpenShift project that contains the API, for example fuse.
5. In the Name field, type or select the name of an OpenShift service within that namespace, for example i-task-api.
6. Click Create Product.
7. Wait for the new API service to be asynchronously imported into 3scale. A message appears in the upper right section of the Admin Portal: The service will be imported shortly. You will receive a notification when it is done.