Chapter 16. Connecting to Knative resources

Procedure

1. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   $ oc login -u developer -p developer

2. Switch to the project in which Fuse Online is running, for example:

   $ oc project my-integration-project

3. Edit the syndesis custom resource:

   1. Invoke the following command, which typically opens the resource in an editor:

      oc edit syndesis

   2. Update the resource to specify the following:

      spec:
        addons:
           camelk:
             enabled: true
           knative:
             enabled: true

   3. Save the resource.

      Saving this change to the syndesis custom resource triggers syndesis-operator, which is responsible for installing Fuse Online, to redeploy syndesis-server.

      If camelk and knative are already enabled, you can close the file. Connections to Knative resources are enabled.

Procedure

1. In Fuse Online, in the left panel, click Integrations.
2. Click Create Integration.
3. On the Choose a connection page, click the Knative connection.
4. Select the Receive from Channel action.
5. Click in the Channel name field to display a list of available Knative channels.
6. Select the Knative channel name for the resource that you want to obtain messages from.

7. Click Next to specify the Receive from Channel action’s output type. This is the type that the connection passes to the next step in the integration.

   1. In the Select Type field, if the data type does not need to be known, accept Type specification not required and click Next. You do not need to follow the rest of these instructions.

      However, a structured data type is recommended. For example, if you want to map the connection output in a data mapper step then you must specify the data type. The data mapper cannot display fields for unstructured data.

      To specify the data type, click in the Select Type field and select one of the following as the schema type:

      • JSON schema is a document that describes the structure of JSON data. The document’s media type is application/schema+json.
      • JSON instance is a document that contains JSON data. The document’s media type is application/json.
      • XML schema is a document that describes the structure of XML data. The document’s file extension is .xsd.
      • XML instance is a document that contains XML data. The document’s file extension is .xml.
   2. In the Definition input box, paste a definition that conforms to the schema type you selected. For example, if you select JSON schema then you would paste the content of a JSON schema file, which has a media type of application/schema+json.

   3. In the Data Type Name field, enter a name that you choose for the data type. For example, if you are specifying a JSON schema for vendors then you might specify Vendor as the data type name.

      You will see this data type name when you are creating or editing an integration that uses the connection for which you are specifying this type. Fuse Online displays the type name in the integration visualization and in the data mapper.

   4. In the Data Type Description field, provide information that helps you distinguish this type. This description appears in the data mapper when you hover over the step that processes this type.
   5. Click Next.

Procedure

1. On the Add to Integration page, click the plus sign where you want to add the connection. Skip this step if Fuse Online is prompting you to choose the finish connection.
2. On the Choose a connection page, click the Knative connection.
3. Select the Send to Channel action.
4. Click in the Channel name field to display a list of the Knative channels that are available in the cluster that is running Fuse Online.
5. Select the channel that you want the integration to send messages to.

6. Click Next to specify the Send to Channel action’s input type. This is the type that the integration sends to the Knative channel.

   1. In the Select Type field, if the data type does not need to be known, or if the output from the previous integration step is the expected type, accept Type specification not required and click Next. You do not need to follow the rest of these instructions.

      However, a structured data type is recommended. For example, if you want to map the connection input in a data mapper step then you must specify the data type. The data mapper cannot display fields for unstructured data.

      To specify the data type, click in the Select Type field and select one of the following as the schema type:

      • JSON schema is a document that describes the structure of JSON data. The document’s media type is application/schema+json.
      • JSON instance is a document that contains JSON data. The document’s media type is application/json.
      • XML schema is a document that describes the structure of XML data. The document’s file extension is .xsd.
      • XML instance is a document that contains XML data. The document’s file extension is .xml.
   2. In the Definition input box, paste a definition that conforms to the schema type you selected. For example, if you select JSON schema then you would paste the content of a JSON schema file, which has a media type of application/schema+json.

   3. In the Data Type Name field, enter a name that you choose for the data type. For example, if you are specifying a JSON schema for vendors then you might specify Vendor as the data type name.

      You will see this data type name when you are creating or editing an integration that uses the connection for which you are specifying this type. Fuse Online displays the type name in the integration visualization and in the data mapper.

   4. In the Data Type Description field, provide information that helps you distinguish this type. This description appears in the data mapper when you hover over the step that processes this type.
   5. Click Next.

Procedure

1. In Fuse Online, in the left panel, click Integrations.
2. Click Create Integration.
3. On the Choose a connection page, click the Knative connection.
4. Select the Expose as Service action.

Procedure

1. On the Add to Integration page, click the plus sign where you want to add the connection. Skip this step if Fuse Online is prompting you to choose the finish connection.
2. On the Choose a connection page, click the Knative connection.
3. Select the Call Service action.
4. Click in the Service name field to display a list of the Knative services that are available in the cluster that is running Fuse Online.

5. Select the service that you want the integration to call.

   If you exposed an integration as a Knative service and that is the service that you want to call, the name of the service is similar, if not identical, to the name of the integration.

6. Click Next to specify the Call Service action’s input type. This is the type that the integration sends to the Knative service.

   1. In the Select Type field, if the data type does not need to be known, or if the output from the previous integration step is the expected type, accept Type specification not required and click Next. You do not need to follow this subset of instructions.

      A structured data type is recommended. For example, if you want to map the connection input in a data mapper step then you must specify the data type. The data mapper cannot display fields for unstructured data.

      To specify the data type, click in the Select Type field and select one of the following as the schema type:

      • JSON schema is a document that describes the structure of JSON data. The document’s media type is application/schema+json.
      • JSON instance is a document that contains JSON data. The document’s media type is application/json.
      • XML schema is a document that describes the structure of XML data. The document’s file extension is .xsd.
      • XML instance is a document that contains XML data. The document’s file extension is .xml.
   2. In the Definition input box, paste a definition that conforms to the schema type you selected. For example, if you select JSON schema then you would paste the content of a JSON schema file, which has a media type of application/schema+json.

   3. In the Data Type Name field, enter a name that you choose for the data type. For example, if you are specifying a JSON schema for vendors then you might specify Vendor as the data type name.

      You will see this data type name when you are creating or editing an integration that uses the connection for which you are specifying this type. Fuse Online displays the type name in the integration visualization and in the data mapper.

   4. In the Data Type Description field, provide information that helps you distinguish this type. This description appears in the data mapper when you hover over the step that processes this type.
   5. Click Next.

7. Specify the Call Service action’s output type.

   This is the type that the Knative service returns to the integration when the Knative connection is a middle connection.

   Repeat the previous subset of instructions to specify the output type. Or, if the Knative service response is empty, accept Type specification not required.

8. Click Next to add the connection.