1. Go to https://aws.amazon.com/s3/.
2. Hover over My Account, select AWS Management Console and sign in to the console with the AWS account that created the bucket that you want to access or with the account that you want the connection to use to create the bucket.
3. In the console, in the upper right, click the down arrow next to the user name and click My Security Credentials.
4. Expand Access Keys and click Create New Access Keys.
5. Follow the prompts to obtain the keys.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display Fuse Online connectors.
3. Click the Amazon S3 connector.
4. In the Access Key field, enter the Amazon S3 access key ID, provided by AWS, for the AWS account that created the bucket that you want this connection to access. If the bucket you want the connection to access does not already exist then when Fuse Online tries to start running the integration, it uses the AWS account associated with this access key to create the bucket. However, if the bucket already exists in some other AWS account, then the connection cannot create the bucket and the integration cannot start.
5. In the Bucket Name or Amazon Resource Name field, enter the name of the bucket that you want this connection to access or enter the bucket’s ARN. If the bucket does not already exist in either the AWS account being used or in any other AWS account, then the connection creates it.
6. In the Region field, select the AWS region in which the bucket resides. If the connection creates the bucket, then it creates it in the selected region.
7. In the Secret Key field, enter the Amazon S3 secret access key, provided by AWS, for the account that created, or will create, the bucket that you want this connection to access.
8. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether or not validation is successful. If validation fails, revise the configuration details as needed and try again.
9. When validation is successful, click Next.
10. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter Obtain S3 Data.
11. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter Sample S3 connection that obtains data from the northeast bucket.
12. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that Obtain S3 Data appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the Amazon S3 connection that you want to use to start the integration.

4. On the Choose an Action page, click the action that you want the connection to perform:

   • Get Object obtains a file from the bucket that the connection accesses. In the File Name field, enter the name of the file that you want to obtain. If the specified file is not in the bucket, it is a runtime error.

   • Poll an Amazon S3 Bucket periodically obtains files from the bucket that the connection accesses. To configure this action:

     1. In the Delay field, accept the default of 500 milliseconds as the time that elapses between polls. Or, to specify a different polling interval, enter a number and select its time unit.

     2. In the Maximum Objects to Retrieve field, enter the largest number of files that one poll operation can obtain. The default is 10.

        To have no limit on the number of files that can be obtained, specify 0 or a negative integer. When Maximum Objects to Retrieve is unlimited, the poll action obtains all files in the bucket.

        If the bucket contains more than the specified maximum number of files then the action obtains the files that were most recently modified or created.

     3. In the Prefix field, optionally specify a regular expression that evaluates to a string. If you specify a prefix then this action retrieves a file only when its name starts with that string.
     4. Indicate whether you want to Obtain files and then delete them from the bucket.
5. After you configure the action, click Done to specify the action’s output type.

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

   Otherwise, 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.
7. 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.

8. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

9. 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.
10. Click Done.

Procedure

1. Start creating the integration.
2. Add and configure the start connection.
3. On the Choose a Finish Connection page, click the Amazon S3 connection that you want to use to finish the integration.

4. Click the action that you want the connection to perform:

   • Copy Object adds one or more objects to the bucket.

     To add one file to the bucket, you can enter its name in the File Name field.

     To add multiple files to the bucket, do not specify a file name. In this case, the action adds all objects that it obtains from the previous integration step(s).

     If you used the poll action to obtain multiple files and you specify a file name then the Copy Object action adds only the last file that was received from the poll action.

   • Delete Object deletes an object from the bucket. In the File Name field, specify the name of the object that you want to delete. If the specified file is not in the bucket, the integration continues with no error.
5. After you configure the chosen action, click Next to specify the action’s input type.

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

   Otherwise, 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.
7. 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.

8. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

9. 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.
10. Click Done.

Procedure

1. Click the Amazon S3 connection that you want to use in the middle of a flow.

2. Click the action that you want the connection to perform:

   • Copy Object adds one or more objects to the bucket.

     To add one file to the bucket, you can enter its name in the File Name field.

     To add multiple files to the bucket, do not specify a file name. In this case, the action adds all objects that it obtains from the previous integration step(s).

     If you used the poll action to obtain multiple files and you specify a file name then the Copy Object action adds only the last file that was received from the poll action.

   • Delete Object deletes an object from the bucket. In the File Name field, specify the name of the object that you want to delete. If the specified file is not in the bucket, the integration continues with no error.
3. After you configure the chosen action, click Next to specify the action’s input type.

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

   Otherwise, 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.
5. 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.

6. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

7. 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.
8. Click Done.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display connectors.
3. Click the Red Hat AMQ connector.

4. Configure the connection by entering:

   1. In the Broker URL field, enter the location that you want to send data to or obtain data from, for example, tcp://localhost:61616.
   2. In the User Name field, enter the user name for the account that you want to use to access this broker.
   3. In the Password field, enter the password for the account that you want to use to access this broker.
   4. In the Client ID field, enter the ID that allows connections to close and reopen without missing messages. The destination type must be a topic.
   5. If this connection will be used in a development environment, you can save some time by disabling Check Certificates. Disabling the checking of certificates is a convenience for development environments. For secure production environments, always enable Check Certificates.
   6. In the Broker Certificate field, paste the Red Hat AMQ broker’s PEM certificate text. This is required except when you disable checking the certificates.
   7. In the Client Certificate field, paste the Red Hat client’s PEM certificate text. Content in this field is always optional.
5. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise the configuration details as needed and try again.
6. If validation is successful, click Next.
7. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, you might enter Red Hat AMQ 1.
8. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter Sample Red Hat AMQ connection that uses a provided broker.
9. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that Red Hat AMQ 1 appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the Red Hat AMQ connection that you want to use to start the integration.
4. On the Choose an Action page, click the Subscribe for messages action to receive messages from the queue or topic that you specify.

5. To configure the action:

   1. In the Destination Name field, enter the name of the queue or topic to receive data from.
   2. For the Destination Type, accept Queue or select Topic.
   3. In the Durable Subscription ID field, to allow connections to close and reopen without missing messages, enter the durable subscription ID. The destination type must be a topic.

   4. In the Message Selector field, if you want to receive only data that satisfies a particular condition, enter a filter expression.

      A message selector is a string that contains an expression. The syntax of the expression is based on a subset of the SQL92 conditional expression syntax. The message selector in the following example selects any message that has a NewsType property whose value is set to Sports or Opinion:

      NewsType = ’Sports’ OR NewsType = ’Opinion’

      The message consumer receives only those messages whose headers and properties match the message selector expression. A message selector cannot select messages on the basis of the content of the message body.

6. Click Next to specify the action’s output type.

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

   Otherwise, 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.
8. 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.

9. 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 panel and in the data mapper.

10. 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.
11. Click Done.

Procedure

1. On the Choose a Finish Connection page, click the Red Hat AMQ connection that you want to use to finish the integration.
2. On the Choose an Action page, click the Publish messages action to publish messages to the queue or topic that you specify.
3. In the Destination Name field, enter the name of the queue or topic to send messages to.
4. For the Destination Type, accept Queue or select Topic.
5. Select Persistent to guarantee message delivery even if a connection fails.
6. Click Next to specify the action’s input/output type.

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

   Otherwise, 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.
8. 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.

9. 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 panel and in the data mapper.

10. 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.
11. Click Done.

Procedure

1. Click the Red Hat AMQ connection that you want in the middle of the flow.

2. On the Choose an Action page, select one of the following actions:

   • Publish messages action to publish messages to the queue or topic that you specify. To configure this action:

     1. In the Destination Name field, enter the name of the queue or topic to send messages to.
     2. For the Destination Type, accept Queue or select Topic.
     3. Select Persistent to guarantee message delivery even if a connection fails.

   • Request response using messages to send messages to the JMS destination that you specify and receive a response. To configure this action:

     1. In the Destination Name field, enter the name of the queue or topic to send messages to.
     2. For the Destination Type, accept Queue or select Topic.

     3. In the Message Selector field, if you want to receive only responses that satisfy a particular condition, enter a filter expression.

        A message selector is a string that contains an expression. The syntax of the expression is based on a subset of the SQL92 conditional expression syntax. The message selector in the following example selects any message that has a NewsType property whose value is set to Sports or Opinion:

        NewsType = ’Sports’ OR NewsType = ’Opinion’

        The message consumer receives only those messages whose headers and properties match the message selector expression. A message selector cannot select messages on the basis of the content of the message body.

     4. In the Named Reply To field, enter the name of a queue or topic. The destination sends its response to this queue or topic.
     5. Select Persistent to guarantee message delivery even if a connection fails.
     6. In the Response Time Out field, specify the number of milliseconds that this connection waits for a response message before throwing a runtime exception. The default is 5000 milliseconds (5 seconds).
3. Click Next to specify the action’s input type and then the action’s output type.

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

   Otherwise, 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.
5. 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.

6. 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 panel and in the data mapper.

7. 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.
8. Click Done.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display connectors.
3. Click the AMQP Message Broker connector.

4. Configure the connection by entering:

   1. In the Connection URI field, enter the location you want to send data to or obtain data from.
   2. In the User Name field, enter the user name for the account that you want to use to access this broker.
   3. In the Password field, enter the password for the account that you want to use to access this broker.
   4. In the Client ID field, enter the ID that allows connections to close and reopen without missing messages. The destination type must be a topic.
   5. If this connection will be used in a development environment, you can save some time by disabling Check Certificates. Disabling the checking of certificates is a convenience for development environments. For secure production environments, always enable Check Certificates.
   6. In the Broker Certificate field, paste the broker’s PEM certificate text. This is required except when disable checking the certificates.
   7. In the Client Certificate field, paste the client’s PEM certificate text. Content in this field is always optional.
5. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise the configuration details as needed and try again.
6. If validation is successful, click Next.
7. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, you might enter AMQP 1.
8. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter Sample AMQP connection
9. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that AMQP 1 appears as a connection that you can choose to add to an integration.

Procedure

1. On the Choose a Start Connection page, click the AMQP connection that you want to use to start the integration.
2. On the Choose an Action page, click the Subscribe for messages action to receive messages from the queue or topic that you specify.

3. To configure the action:

   1. In the Destination Name field, enter the name of the queue or topic to receive data from.
   2. For the Destination Type, accept Queue or select Topic.
   3. In the Durable Subscription ID field, to allow connections to close and reopen without missing messages, enter the durable subscription ID. The destination type must be a topic.

   4. In the Message Selector field, if you want to receive only data that satisfies a particular condition, enter a filter expression.

      A message selector is a string that contains an expression. The syntax of the expression is based on a subset of the SQL92 conditional expression syntax. The message selector in the following example selects any message that has a NewsType property whose value is set to Sports or Opinion:

      NewsType = ’Sports’ OR NewsType = ’Opinion’

      The message consumer receives only those messages whose headers and properties match the message selector expression. A message selector cannot select messages on the basis of the content of the message body.

4. Click Next to specify the action’s output type.

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

   Otherwise, 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.
6. 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.

7. 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 panel and in the data mapper.

8. 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.
9. Click Done.

Procedure

1. Click the AMQP connection that you want to use to publish messages.

2. On the Choose an Action page, select one of the following actions:

   • Publish messages to publish messages to the queue or topic that you specify without receiving a response. To configure this action:

     1. In the Destination Name field, enter the name of the queue or topic to send messages to.
     2. For the Destination Type, accept Queue or select Topic.
     3. Select Persistent to guarantee message delivery even if a connection fails.

   • Request response using messages to publish messages to the queue or topic that you specify and receive a response.

     Note

     When the finish connection in a simple integration is an AMQP connection that performs the Request response using messages action, the connection publishes the messages but the response is discarded. To avoid losing the response, add an AMQP connection as a middle connection that performs the Request response using messages action and finish the simple integration with a log step.

     To configure this action:

     1. In the Destination Name field, enter the name of the queue or topic to send messages to.
     2. For the Destination Type, accept Queue or select Topic.
     3. In the Durable Subscription ID field, to allow connections to close and reopen without missing messages, enter the durable subscription ID. The destination type must be a topic.

     4. In the Message Selector field, if you want to receive only responses that satisfy a particular condition, enter a filter expression.

        A message selector is a string that contains an expression. The syntax of the expression is based on a subset of the SQL92 conditional expression syntax. The message selector in the following example selects any message that has a NewsType property whose value is set to Sports or Opinion:

        NewsType = ’Sports’ OR NewsType = ’Opinion’

        The message consumer receives only those messages whose headers and properties match the message selector expression. A message selector cannot select messages on the basis of the content of the message body.

3. Click Next to specify the action’s input and output type.

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

   Otherwise, 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.
5. 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.

6. 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 panel and in the data mapper.

7. 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.
8. Click Done.

Procedure

1. In Fuse Online:

   1. In the left panel, click Settings.
   2. On the Settings page, near the top, to the right of the callback URL, click to copy the callback URL for your Fuse Online environment to the clipboard. You will need this URL toward the end of this procedure.

2. In another browser tab, go to https://www.dropbox.com and do the following:

   1. Sign in to the Dropbox account that has the data that you want to access in an integration.
   2. After signing in, go to https://www.dropbox.com/developers/apps.
   3. Click Create App.
   4. Select Dropbox API.
   5. Near the top of the page, in the sentence that starts with During registration, enter this callback URL:, paste the URL that you copied to the clipboard at the beginning of this procedure. For example, the URL that you paste is something like this: https://app-proj9128.7b63.fuse-ignite.openshiftapps.com/api/v1/credentials/callback.
   6. Choose whether Fuse Online can access a single folder or all of the folders and files.
   7. Specify a name for your Dropbox app. For example, you might specify Fuse Online Access From Aslan LLC. The name you specify must be unique in the set of Dropbox app names.
   8. Check the box to indicate that you agree to Dropbox API terms and conditions.
   9. Click Create App.
   10. In the Dropbox Settings page for your new app, in the input field for OAuth2 Redirect URIs, paste your Fuse Online URL, which you copied to the clipboard at the beginning of this procedure.
   11. Click Add.

Procedure

1. In a new browser tab, go to https://www.dropbox.com and do the following:

   1. Sign in to the Dropbox account in which you created the app that registers access from your Fuse Online environment.
   2. Go to https://www.dropbox.com/developers/apps.
   3. Click the Fuse Online app to display its settings.

2. In another browser tab, in Fuse Online, do the following:

   1. In the left panel, click Connections to display any available connections.
   2. In the upper right, click Create Connection to display the available connectors.
   3. Click the Dropbox connector.

3. Go back to the Dropbox settings display for your app and do the following:

   1. Scroll down to see Generated Access Token.
   2. Click Generate.
   3. Copy the generated access token to the clipboard.
4. Back in Fuse Online, in the Configure Connection page, in the Access Token field, paste the generated access token.
5. In the Client Identifier field, enter the name that you specified when you created the Dropbox app.
6. Click Validate. Fuse Online displays a message that indicates whether it can validate this connection. If validation fails, try again and be sure to enter the correct values.
7. When validation is successful, in the upper right, click Next.
8. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter Dropbox Connect 1.
9. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter Sample Dropbox connection that can access all content in our company Dropbox account.
10. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that Dropbox Connect 1 appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the Dropbox connection that you want to use to start the integration.
4. On the Choose an Action page, click the Download action to obtain one or more files from the Dropbox account that this connection accesses.
5. To configure the action, in the Folder or file name path to download field, specify the filename path for the content that you want the integration to obtain. In this release, you can download only a single file.
6. Click Next to specify the action’s output type.

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

   Otherwise, 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.
8. 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.

9. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

10. 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.
11. Click Done.

Procedure

1. On the Choose a Finish Connection page, click the Dropbox connection that you want to use to finish the integration.
2. On the Choose an Action page, click the Upload action to add the current integration data to the Dropbox account that this connection accesses.
3. In the Remote Path field, enter the local filename path for file that you want to upload. Dropbox stores the file with the same path and name. In this release, you can upload only a single file.

4. For the Upload mode:

   • Select Add to upload a file only when a file with the same name is not already in the same Dropbox folder. If a file with the same name is already in the same Dropbox folder, then the file is not uploaded and the integration continues. This is the behavior regardless of whether the content in the file you are trying to upload has been updated.
   • Select Force to ensure that the file is uploaded even if a file with the same name is present in the same Dropbox folder. Dropbox overwrites the file that it already has with the file that you are uploading.
5. Click Next to specify the action’s input type.

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

   Otherwise, 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.
7. 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.

8. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

9. 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.
10. Click Done.

Procedure

1. Click the Dropbox connection that you want the integration to use.

2. On the Choose an Action page, click Upload to add the current integration data to the Dropbox account that this connection accesses. To configure this action:

   1. In the Remote Path field, specify the local path and file name of the file that you want to upload. Dropbox stores the file with the same path and name. In this release, you can upload only a single file.

   2. For the Upload mode:

      • Select Add to upload a file only when a file with the same name is not already in the same Dropbox folder. If a file with the same name is already in the same Dropbox folder, then the file is not uploaded and the integration continues. This is the behavior regardless of whether the content in the file you are trying to upload has been updated.
      • Select Force to ensure that the file is uploaded even if a file with the same name is present in the same Dropbox folder. Dropbox overwrites the file that it already has with the file that you are uploading.
3. Click Next to specify the action’s input and output type.

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

   Otherwise, 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.
5. 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.

6. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

7. 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.
8. Click Done.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display connectors.

3. Click the FHIR connector and configure the connection as follows:

   1. In the FHIR version field, accept DSTU3, which is required.
   2. In the FHIR server URL field, enter the URL for the FHIR server that you want to access. While creating an integration, you might accept the default test server http://fhirtest.uhn.ca/baseDstu3.
   3. In the FHIR server username field, enter your username. This is required by FHIR servers that use basic authentication.
   4. In the FHIR server password field, enter your password, which is also required by FHIR servers that use basic authentication.
   5. In the FHIR server bearer token field, enter your token. This is required by FHIR servers that use OAuth authentication.
4. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise the input parameters and try again.
5. If validation is successful, click Next.
6. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, you might enter FHIR West.
7. In the Description field, optionally enter any information that is helpful to know about this connection.
8. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that FHIR West appears as a connection that you can choose to add to an integration.

Procedure

1. Click the FHIR connection that can access the resource that you want to obtain.
2. On the Choose an Action page, click Read.
3. Click in the Resource Type field to display a list of FHIR resource types. Select or enter the type of resource that you want to obtain.

4. In the Contained Resource Types field, if the resource type that you want contains other resource types, select them. Use the Ctrl key if you need to select more than one.

   Identifying contained resource types lets the data mapper display the fields that are in the contained resources. If you do not specify a contained resource type then you cannot map from any fields that are in the contained resource. There is no harm in selecting a resource that is not actually contained.

5. In the Resource Id field, enter the ID of the resource that you want. Or, leave this field blank if you plan to map it from an earlier step that is in the flow.
6. In the Resource version field, optionally specify a version ID for the resource. Leave this field blank to obtain the most recent version of the resource or to map the version ID of the resource that you want to obtain from a previous step.
7. Click Next to add this connection to the flow.

Procedure

1. Click the FHIR connection that has the resources that you want to obtain.
2. On the Choose an Action page, click Search.
3. Click in the Resource Type field to display a list of FHIR resource types. Select or enter the type of resource that you want to obtain.
4. In the Query field, specify a FHIR query or leave this field blank to map the query from a previous step. For details about forming a FHIR query, see FHIR Release 3 Search.
5. Click Next to add this connection to the flow.

Procedure

1. Click the FHIR connection to the server that you want to add a resource to.
2. On the Choose an Action page, click Create.
3. Click in the Resource Type field to display a list of FHIR resource types. Select or enter the type of resource that you want to create.

4. In the Contained Resource Types field, if the resource type that you want to create contains other resource types, select them. Use the Ctrl key if you need to select more than one.

   Identifying contained resource types lets the data mapper display the fields that are in the contained resources. If you do not specify a contained resource type then you cannot map to or from any fields that are in the contained resource. There is no harm in selecting a resource that is not actually contained.

5. Click Next to add this connection to the flow.

Procedure

1. Click the FHIR connection that you want to use to update a resource on a FHIR server.
2. On the Choose an Action page, click Update.
3. Click in the Resource Type field to display a list of FHIR resource types. Select or enter the type of resource that you want to update or create.

4. In the Contained Resource Types field, if the resource type that you want to update or create contains other resource types, select them. Use the Ctrl key if you need to select more than one.

   Identifying contained resource types lets the data mapper display the fields that are in the contained resources. If you do not specify a contained resource type then you cannot map to or from any fields that are in the contained resource. There is no harm in selecting a resource that is not actually contained.

5. Click Next to add this connection to the flow.
6. If this flow needs additional steps to obtain the data that you want the updated resource to contain, add them before this FHIR connection.
7. In the integration visualization panel, click the plus sign that is before the FHIR connection that updates a resource.
8. Click Data Mapper.

9. In the data mapper:

   1. Map a resource ID to the target resource ID. This is the only way to specify the resource ID for a new resource.
   2. Map to each resource field that you want the updated or new resource to contain. Be sure to map fields whose values are not changing, as well as fields whose values need to be updated.
   3. Click Done to add the data mapper step to the flow.

Procedure

1. Click the FHIR connection that you want to use to update the resource.
2. On the Choose an Action page, click Patch.
3. Click in the Resource Type field to display a list of FHIR resource types. Select or enter the type of the resource whose fields you want to update.
4. In the Number of Operations field, specify the number of fields that you want to update.
5. Leave the Resource id field blank if you want to map the value from a previous step in the flow, which is typically what you want to do. Otherwise, specify the resource ID of the resource whose fields you want to update.
6. Specify a JSON patch that describes the updates. The JSON patch must have the format described in What is a JSON Patch?. For some updates, you must specify the JSON patch when you configure the Patch action. For example, if you want to copy the value of a resource field to another field. For other updates, you can leave the JSON Patch field blank and instead map values that define each update.
7. Click Done to add this connection to the flow.

8. If you did not specify a JSON patch and/or a resource ID, then add a data mapper step:

   1. In the flow visualization panel, click the plus sign that is before the FHIR connection that you just added.

   2. On the Choose a Step page, click Data Mapper.

      The Target panel displays a numbered folder for each field that you want to update. When you configured the Patch action, you specified how many fields to update. The data mapper displays this number of folders in the Target panel. For example, if you specified 3 as the number of fields to update, you would see three target folders with the labels 1, 2, and 3.

   3. For each field that you want to update, map to the fields in one target folder:

      1. In the Target panel, expand a folder to display three fields for op, path, and value.
      2. Map a source field, constant, or property to the target path field. The path identifies the resource field that you want to update. In a path value, a number indicates the index of a list field, and a slash leads to a child field. For example, map this path /name/1/given/1/value to update the value of the given name field.
      3. Accept the default update operation, which replaces the current value of the field, or map a source field, constant, or property to the op field to indicate how you want to update the field. For details about possible operations, see JSON patch operations.
      4. If you are updating a field to have a new value, then map a source field, constant, or property to the target value. This is the new value that you want the field to contain.
   4. If you did not specify a resource ID when you configured the Patch action, then map the resource ID to the target id field.
   5. Click Done to add the data mapper step to the flow.

Procedure

1. Click the FHIR connection that you want to use to create and add new resources to a FHIR server.
2. On the Choose an Action page, click Transaction.
3. In the Included Resource Types field, select the resource types that this connection creates. Use the Ctrl key to select multiple resource types. The connection creates one resource of each type that you select.
4. Click Next to add this connection to the flow.

5. To populate fields in the new resources, add a data mapper step before this connection:

   1. In the flow visualization on the left, click the plus sign that is before the connection that you just added.
   2. Click Data Mapper.
   3. In the data mapper, map source fields to the target resource fields. The new resources contain only the target fields that you map to.
   4. Click Done to add the data mapper step to the flow.

Procedure

1. Click the FHIR connection that you want to use to delete the resource.
2. On the Choose an Action page, click Delete.
3. Click in the Resource Type field to display a list of FHIR resource types. Select or enter the type of resource that you want to delete.
4. In the Resource Id field, specify the resource ID of the resource that you want to delete or leave this field blank if you plan to map the resource ID from an earlier step in the integration.
5. In the Resource version field, optionally specify a version ID for the resource. Leave this field blank to delete the most recent version of the resource or to map the version ID of the resource that you want to delete from a previous step.
6. Click Done to add this connection to the flow. .

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display Fuse Online connectors.

3. To create a connection that uses File Transfer Protocol, click the FTP connector.

   Or, to create a connection that uses Secure File Transfer Protocol, click the SFTP connector.

4. Configure the connection.

   • For an FTP connection:

     • Host is the only parameter that you must specify. Enter the host name of the server that you want to connect to. For example, if the name of your FTP host is FTP.WEST, then you would enter exactly that, FTP.WEST. Do not specify the protocol, for example, you should not specify something like this: ftp://FTP.WEST.
     • Port is required and has a default value of 21. This is the port that the FTP server is listening on.
     • All other parameters are either not required or have default values. The defaults are suitable for most integrations. Descriptions of these parameters are after this procedure.

   • For an SFTP connection, there must be values for these parameters:

     • Host is the host name of the SFTP server that you want to connect to. For example, if the name of your SFTP host is SFTP.EAST, then you would enter exactly that, SFTP.EAST. Do not specify the protocol, for example, you should not specify something like this: sftp://SFTP.EAST.
     • Port has a default of 22. This is the port that the SFTP server is listening on.
     • User name of the account that you want to use to access the SFTP server.
     • Password that is associated with that user name.
     • All other parameters have default values. The defaults are suitable for most integrations. Descriptions of these parameters are after this procedure.
5. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether or not validation is successful. If validation fails, revise the configuration details as needed and try again.
6. When validation is successful, click Next.
7. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter XLight FTP Server.
8. In the Description field, optionally enter any information that is helpful to know about this connection.
9. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that XLight FTP Server appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the FTP or SFTP connection that you want to use to poll an FTP or SFTP server.
4. On the Choose an Action page, click Download.
5. In the File name expression field, if you are interested in a single file, then enter an Apache Camel Simple language expression that resolves to a file name. You cannot specify a regular expression. The connection polls (periodically checks) the server for this file and downloads it when it is found. Leave this field blank if you want to download more than one file.
6. In the FTP directory field, enter the absolute or relative path of the server directory to poll. The connection watches this directory for any content and downloads all files when it finds any content.
7. In the Milliseconds before polling starts field, accept the default of 1000 milliseconds or change the number of milliseconds.
8. In the Milliseconds before the next poll field, accept the default of 500 milliseconds or change the number of milliseconds. This is the interval between polls.
9. In the Delete after download field, accept the default of No or select Yes to download the file(s) and then delete it(them) from the server.
10. Click Next to specify the action’s output type.

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

    Otherwise, 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.
12. 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.

13. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

14. 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.
15. Click Done.

Procedure

1. Click the FTP or SFTP connection that you want to use to upload files.
2. On the Choose an Action page, click Upload.
3. In the File name expression field, if you want to upload only one particular file, then enter an Apache Camel Simple language expression that resolves to a file name. This is the name of the file that the action uploads to the server. You cannot specify a regular expression. To upload more than one file, leave this field blank.
4. In the FTP directory field, enter the absolute or relative name of a server directory. If the File name expression field contains an expression, then the connection stores the specified file in this directory. If the File name expression field is blank, then the connection uploads to this directory all files that were received from the previous step.

5. In the If file exists field, indicate the behavior when you are uploading a file that has the same path and name as a file that is on the server. Accept the default, Override, to overwrite the file that is on the server with the file that you are uploading. Or, select one of the following:

   • Append adds the content in the file being uploaded to the file that is on the server.
   • Fail throws GenericFileOperationException. The integration does not enter an error state.
   • Ignore does not upload the file. The integration continues running under the assumption that everything is okay.
   • Move renames one of the files.
   • TryRename uploads the file with a temporary name and renames the file to the desired name. This operation does not check for the existence of a file with the desired name, which makes the operation faster on most servers than when existence checks are done.
6. In the Temporary file prefix while copying field, specify a string. The connection prepends this string to the name of a file while it is being uploaded. This enables the connection to write to a temporary file on the server and then rename that temporary file to have the correct name. This is useful for reducing locks when uploading very large files.
7. In the Temporary file name while copying field, specify a string. The connection renames a file being uploaded to have this name while it is being uploaded. This enables the connection to write to a temporary file on the server and then rename that temporary file to have the correct name. This is useful for reducing locks when uploading very large files.
8. Click Next to specify the action’s input type.

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

   Otherwise, 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.
10. 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.

11. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

12. 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.
13. Click Done.

Procedure

1. In Fuse Online:

   1. In the left navigation panel, click Settings.
   2. On the Settings page, near the top, to the right of the callback URL, click to copy the callback URL for your Fuse Online environment to the clipboard. You will need this URL later in this procedure.

2. In another browser tab, go to https://console.developers.google.com and do the following:

   1. Check that you are signed into the Google account that you want to use to register Fuse Online as a Google client application. Or, choose a different Google account and sign in to that account.

      The name of the current Google project appears at the top of the Google APIs page.

   2. To use the current project to grant authorization to Fuse Online, continue to the next step. To grant authorization to Fuse Online in another Google project, choose or create that project. If this Google account does not already have a project, you must create one.

   3. Enable Google APIs:

      1. In the upper left corner, click and select APIs and Services > Library.
      2. If necessary, scroll down to see the G Suite row of cards.
      3. Click the Google Calendar API card, which displays a page that indicates that the Google Calendar API is enabled.
      4. Scroll down and click the Gmail API card, which displays a page that indicates that the Gmail API is enabled.
      5. In the upper left corner, click and select APIs and Services > Library.
      6. If necessary, scroll down to see the G Suite row of cards.
      7. Click the Google Sheets API card, which displays a page that indicates that the Google Sheets API is enabled.

   4. Give your client application a name:

      1. Click MANAGE.
      2. In the page that appears, in the left navigation panel, click Credentials and then on the right, click Credentials in APIs & Services.
      3. Click the OAuth consent screen tab.
      4. In the page that appears, in the Application Name field, enter a name for the Fuse Online client application. For example, enter Fuse Online client application.
      5. Skip the other fields.
      6. Click Save.

   5. Obtain client application credentials as follows:

      1. To the right of Create Credentials, click the down arrow to display a menu and select OAuth client ID.
      2. In the page that appears, select Web application to display more content.
      3. In the Name field, enter a name for the OAuth client ID for your Fuse Online environment. This is different from the name that you entered for the client application itself. For example, enter OAuth client ID for Fuse Online.
      4. Skip Authorized JavaScript origins.
      5. In the Authorized redirect URIs field, paste the callback URL that you copied from your Fuse Online environment at the beginning of this procedure.
      6. Click Create to display the client ID and client secret for your Fuse Online environment.
   6. To the right of the client ID field, click to copy the client ID to your clipboard.

3. Return to the Fuse Online Settings page and do the following:

   1. Expand the entries for Gmail, Google Calendar, and Google Sheets.
   2. In the Client ID field for each Google application, paste the Google client ID that you just copied.
4. Return to the Google developers site and to the right of the client secret field, click to copy the client secret to your clipboard.

5. Return to the Fuse Online Settings page and do the following in the entry for each Google application:

   1. In the Client Secret field, paste the Google client secret that you just copied.
   2. Click Save. You should get a Registration Successful! notification.
   3. Click Ok to collapse the entry.

1. Registering Fuse Online as a Google client application.
2. Creating a Gmail connection. When you do this you choose the Gmail account that the connection is authorized to access.
3. If your integration sends an email from a Gmail account, decide how to populate an email to send.
4. Adding a Gmail connection to an integration flow.
5. For a Gmail connection that sends an email, optionally mapping integration data to the email fields.

Procedures

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display Fuse Online connectors.
3. If you want to use Hyper Text Transfer Protocol to connect to the endpoint, then click the HTTP connector. If you want to use Hyper Text Transfer Protocol Secure, then click the HTTPS connector.
4. In the Base URL field, enter the endpoint path. For example, www.mycompany.com/sales.
5. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise specification of the base URL and try again.
6. If validation is successful, click Next.
7. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter HTTPS My Company Sales.
8. In the Description field, optionally enter any information that is helpful to know about this connection.
9. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that HTTPS My Company Sales appears as a connection that you can choose to add to an integration.

Procedure

1. Click the HTTP or HTTPS connection that you want to add to the flow.

2. Select the action that you want the connection to perform:

   • If you are adding a start connection, then Periodic invoke URL is the only available action. This action invokes the endpoint at intervals that you specify and triggers the integration if the endpoint returns any data.
   • If you are adding a middle or finish connection, then Invoke URL is the only available action. This action invokes the endpoint once.
3. In the URL Path field, specify the location of the endpoint that you want to invoke.

4. In the HTTP Method field, select the method that you want the connection to perform. The default method is GET.

   • GET obtains the content at the URL path.
   • PUT replaces the content at the URL path with the integration data.
   • POST stores the integration data at the URL path to create new content.
   • DELETE removes content at the URL path.
   • HEAD obtains metadata about the content at the URL path.
   • OPTIONS obtains communication option settings at the URL path.
   • TRACE obtains information for testing and diagnostic purposes.
   • PATCH partially updates the content at the URL path according to the integration data.
5. If you are adding a start connection, which periodically invokes the URL, then in the Period field, accept the default interval of 1 second or specify a number and its unit (milliseconds, seconds, minutes, or hours) to indicate how long to wait between invocations.
6. Click Done to specify the action’s input or output type.

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

   Otherwise, 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.
8. 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.

9. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

10. 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.
11. Click Done.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display Fuse Online connectors.
3. Click the IRC connector.
4. In the Hostname field, enter an IRC hostname. You can specify an IP address or a name, for example, chat.freenode.net.
5. In the Port field, enter the port that the IRC server is listening on, for example, 6665.
6. In the Password field, if the IRC server requires a password, enter it here.
7. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise the connection configuration values and try again.
8. If validation is successful, click Next.
9. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter IRC Freenode.
10. In the Description field, optionally enter any information that is helpful to know about this connection.
11. In the upper right, click Create to see the updated list of available connections, including the connection that you just created. If you entered the example name, you would see that IRC Freenode appears as a connection that you can choose to add to an integration. You can add this connection to any number of integrations.

Procedure

1. Click the IRC connection that you want to use to start the integration.
2. Click the IRC Receive Private Message action.
3. In the Channels field, optionally specify one or more IRC channels separated with commas.
4. In the Nickname field, specify the IRC nickname that the integration uses. For any channels that you specify, this nickname joins the channel. During execution, the integration retrieves messages that are sent to this nickname and passes them to the next step in the integration.
5. In the NickServ Password field, if the specified nickname has a password, enter it.
6. Click Next to specify the action’s output type.

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

   Otherwise, 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.
8. 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.

9. 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 panel and in the data mapper.

10. 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.
11. Click Done to add the connection to the flow.

Procedure

1. Click the IRC connection that you want to add to the flow.

2. Click IRC Send Message to Channel to send a message to one or more channels.

   • In the Channels field, enter one or more IRC channels delimited by commas. During execution, this connection sends messages from the IRC nickname that you specify to these channels.
3. In the Nickname field, specify the IRC nickname that sends messages to the specified channels.
4. In the NickServ password field, if the nickname that you specified has a password, specify it here.
5. Click Next to specify the action’s input type.

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

   Otherwise, 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.
7. 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.

8. 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 panel and in the data mapper.

9. 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.
10. Click Done to add the connection to the flow.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display connectors.
3. Click the Kafka connector.
4. In the Kafka bootstraps URI field, enter a comma separated list of Kafka broker URIs. Each URI should be in the form host:port.
5. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise the input parameter and try again.
6. If validation is successful, click Next.
7. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, you might enter Kafka West.
8. In the Description field, optionally enter any information that is helpful to know about this connection.
9. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that Kafka West appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the Kafka connection that you want to use to start the integration.
4. On the Choose an Action page, click the Subscribe action to receive data from the topic that you specify.
5. In the Topic Name field, click the down carat to display a list of topics and click the topic that you want to subscribe to.
6. Click Next to specify the action’s output type.

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

   Otherwise, 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.
8. 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.

9. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

10. 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.
11. Click Done.

Procedure

1. Click the Kafka connection that you want to use to publish messages.
2. On the Choose an Action page, click Publish.
3. In the Topic Name field, click the down carat to display a list of topics and click the topic that you want to publish to.
4. Click Next to specify the action’s input type.

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

   Otherwise, 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.
6. 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.

7. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

8. 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.
9. Click Done.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display connectors.
3. Click the Apache Kudu connector.

4. To configure the connection:

   1. In the Address of Kudu master host field, enter the hostname or the IP address of the Kudu master host.
   2. In the Port to establish connection to field, enter the port that Kudu is listening on. The default is 7051.
5. Click Next.
6. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, you might enter Kudu North.
7. In the Description field, optionally enter any information that is helpful to know about this connection.
8. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that Kudu North appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the Kudu connection that you want to use to start the integration.
4. On the Choose an Action page, click the Scan a Kudu table action.
5. In the Table field, enter the name of the table that you want to obtain records from.
6. In the Period field, accept the default of one minute, or enter the interval at which you want the connection to scan the table and return the records that are in the table.
7. Click Done.

Procedure

1. Click the Kudu connection that you want to use. Note that when a Kudu connection inserts data, the connection does not return anything.
2. On the Choose an Action page, click Insert data into a Kudu table.

3. To configure the action, in the Table field, specify the name of the table to add records to.

   It is important for you to have an understanding of how the Kudu table that you are adding records to is set up. For example, a Kudu table that you are adding records to might have a unique key. If you try to add a record that contains a key value that is already in the table, the Kudu connection does not add that record.

4. Click Done.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display connectors.
3. Click the MQTT Message Broker connector.

4. To configure the connection:

   1. In the MQTT broker URL field, enter the location of the MQTT broker that you want to send data to or obtain data from. This is the only required field.
   2. In the User Name field, optionally enter the user name for the MQTT account whose credentials you want to use to access the broker.
   3. In the Password field, if you specified a user name, then specify the password associated with that account.
   4. In the Client ID field, optionally enter the ID that allows connections to close and reopen without missing messages. The connection must subscribe to or publish to a topic.
5. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise the input parameters and try again.
6. If validation is successful, click Next.
7. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, you might enter MQTT West.
8. In the Description field, optionally enter any information that is helpful to know about this connection.
9. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that MQTT West appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the MQTT connection that you want to use to start the integration.
4. On the Choose an Action page, click the Subscribe action to receive messages from the queue or topic that you specify.
5. In the MQTT queue/topic name field, enter the name of the queue or topic to subscribe to in order to receive data.
6. Click Next to specify the action’s output type.

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

   Otherwise, 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.
8. 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.

9. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

10. 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.
11. Click Done.

Procedure

1. Click the MQTT connection that you want to use to publish a message.
2. On the Choose an Action page, click Publish.
3. In the MQTT queue/topic name field, specify the name of the queue or topic to publish the message to.
4. Click Next to specify the action’s input type.

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

   Otherwise, 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.
6. 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.

7. In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can 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 panel and in the data mapper.

8. 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.
9. Click Done.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display connectors.
3. Click the OData connector.

4. To configure the connection:

   1. In the Service Root URL field, enter the base URL for the OData service that you want to access.
   2. In the User Name field, if the service uses basic authentication, then enter your user name.
   3. In the Password field, if the service uses basic authentication, then enter your password.

   4. In the Server Certificate field, if the service requires it, paste the content of an SSL certificate.

      Typically, a public OData service does not require a certificate in addition to the certificates provided by the browser. However, for an internal OData service, you might have created your own SSL certificate and self-signed it. Since this certificate is not trusted by a certificate authority, connections to your OData service would fail. To enable connections, paste the self-signed certificate here.

      One way to get the certificate is to load the service in a browser. The steps after that depend on which browser you are using, but it will be something like the following: click the Not secure padlock symbol next to the address bar, then click View Certificate, export the displayed certificate to a file, copy the certificate, and paste it into this field.

5. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise the input parameter(s) and try again.
6. If validation is successful, click Next.
7. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, you might enter OData North.
8. In the Description field, optionally enter any information that is helpful to know about this connection.
9. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that OData North appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the OData connection that you want to use to start the integration.
4. On the Choose an Action page, click the Read action.

5. To configure the Read action:

   1. In the Resource Collection field, select the name of the OData resource that you want to query. Fuse Online fetches data from the OData service to provide a list of available resource collections.
   2. In the Entity Key Predicate field, to obtain a particular entity, identify the entity that you want by specifying its key predicate. For example, specify something like UserName='Bob' or Categories(1). To obtain multiple entities, leave this field blank.

   3. In the Query Options field, enter a query that you want to apply to the resource. Use OData syntax. For example, $filter=startswith(name, 'N') returns a message for each entity in the resource that has a name field that starts with N.

      You can specify both Entity Key Predicate and Query Options. If you do, the OData service obtains the specified entity and applies the query to that entity. For example, suppose that you set Entity Key Predicate to UserName='russellwhyte'/Emails and you set Query Options to $filter=contains($it,'example'). The connection creates a request that looks something like this:

      https://services.odata.org/TripPinRESTierService/People(UserName='russellwhyte')/Emails?$filter=contains($it, 'example')

      The service returns all email addresses for Russell Whyte that contain the domain example.

   4. Select the Filter Old Results checkbox to obtain a particular message only once.

   5. Select the Split Results checkbox if you want the connection to return individual messages rather than a collection of messages.

      Fuse Online also provides discrete split and aggregate steps, which you can add to a flow. If you want to process individual messages in one or more steps and then aggregate the messages into a collection, do not select the Split Results checkbox. Instead, leave the checkbox empty and then add a split step to the flow after this connection. A split step is required if you want an aggregate step in the flow.

   6. In the Interval Before Polling Starts field, accept the default of 1 second, or enter the length of time that you want to elapse before the connection starts to poll the OData service.
   7. In the Delay field, accept the default of 30 seconds, or enter the interval at which you want the connection to poll the OData service.

   8. In the Backoff Idle Threshold field, accept the default of 1 or enter an integer that indicates the number of consecutive polls that can return no data. After this number of polls, the connection increases the interval between subsequent polls. The connection determines the new length of the polling interval by multiplying the Delay value by the Backoff Multiplier value.

      For example, suppose that the polling interval (the Delay value) is the default of 30 seconds, Backoff Idle Threshold is set to 5, and Backoff Multiplier is set to 12. After 5 consecutive polls that return no data, the connection waits 360 seconds (30 x 12) before polling again. The connection continues to poll every 360 seconds until a poll returns data. After a poll returns data, the connection resumes polling every 30 seconds.

   9. In the Backoff Multiplier field, accept the default of 1 or enter an integer that indicates the multiplier for increasing the polling interval if the value set for the Backoff Idle Threshold is reached.

      If you accept the default of 1 for the Backoff Multiplier, then the connection continues to poll at the specified interval no matter how many consecutive polls return no results.

      The values that you specify for Backoff Idle Threshold and Backoff Multiplier are useful for reducing CPU overhead since the connection can automatically poll less often during quiet periods.

6. Click Done.

Procedure

1. Click the OData connection that you want to use. Note that when an OData connection updates or deletes an entity, the connection does not return anything. When the OData connection creates an entity, the connection returns the new entity.

2. On the Choose an Action page, click the action that you want the connection to perform:

   • Create adds an entity to an OData resource.
   • Delete removes an entity from an OData resource.
   • Update changes an entity that is in an OData resource.

3. To configure the action, select the OData resource that you want to update.

   It is important for you to have an understanding of how the OData resource that you are updating is set up. The backing data source for an OData service determines the rules for updates and resolving conflicts. For example, suppose an OData connection tries to create a new entity but an entity with that predicate key already exists. The OData service might overwrite the existing entity, or it might update some fields in the existing entity, or it might ignore the operation. It is up to you to know how the OData service behaves in this situation.

4. Click Done.

Procedure

1. In Fuse Online:

   1. On the Settings page, near the top, to the right of the callback URL, click to copy the callback URL for your Fuse Online environment to the clipboard. You will need this URL later in this procedure.
   2. Look for the name of the API you want to connect to and click its Register button to display its client ID and client secret fields.

2. In another browser window, you must register Fuse Online as an OAuth client of the API you want to connect to. The exact steps for doing this vary for each API service. Typically, the API service provides an OAuth custom application setting page. Go to that page and do the following:

   1. Provide the Fuse Online callback URL, which you copied at the beginning of this procedure.
   2. Respond to any other prompts that require your input.
   3. Obtain the client ID and client secret that the API service assigns to your Fuse Online environment.

3. Return to the Fuse Online Settings page entry for the API service you are registering with and do the following:

   1. Paste the assigned client ID.
   2. Paste the assigned client secret.
   3. Click Save.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display available connectors.
3. Click the connector for the API that you want to create a connection for.
4. Respond to prompts for additional information. The definition of the API determines what Fuse Online prompts for. For example, for an API that uses HTTP Basic Authentication, Fuse Online prompts for the user name and password to use to access the API. For an API that uses OAuth, Fuse Online displays a button for you to click so that Fuse Online can verify its registration credentials for connecting to the API.
5. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections.
6. In the Description field, optionally enter any information that is helpful to know about this connection.
7. In the upper right, click Create to see that you can now choose the connection you created and add to an integration.

Procedure

1. On the page that displays available steps, click the REST API connection that you want to add to the flow.
2. Click the action that you want the connection to perform. The actions that are available are based on the resource operations specified in the OpenAPI document that was uploaded to Fuse Online and that describes the API that you are connecting to.
3. Depending on the action you select, enter any parameters that Fuse Online prompts for.
4. Click Done.

Procedure

1. In Fuse Online:

   1. In the left panel, click Settings.
   2. On the Settings page, near the top, to the right of the callback URL, click to copy the callback URL for your Fuse Online environment to the clipboard. You will need this URL toward the end of this procedure.
   3. To the right of the Salesforce entry, click Register to display the Client ID and Client Secret fields.

2. In another browser tab, log in to your Salesforce account and follow the steps below to create a connected app. These instructions assume that you are using the Salesforce Classic user interface. To switch from the Salesforce Lightning Experience interface, click your profile icon and select Switch to Salesforce Classic. For additional information, see the Salesforce documentation for Create a Connected App.

   1. In Salesforce, in the upper right, click Setup.
   2. In the left panel, select Build > Create > Apps.
   3. Scroll down to Connected Apps and click New.
   4. Enter the required information and then select Enable OAuth Settings.
   5. In the Callback URL field, paste your Fuse Online URL, which you copied at the beginning of this procedure. For example: https://app-proj912876.7b63.fuse-ignite.openshiftapps.com/api/v1/credentials/callback.

   6. For OAuth Scopes, add:

      • Access and manage your data (api)
      • Allow access to your unique identifier (openid)
      • Perform requests on your behalf at any time (refresh_token, offline_accesss)
   7. Select Configure ID token and then Include Standard Claims.
   8. Scroll down and click Save.
   9. Scroll up to see that Salesforce indicates a short wait:
   10. Click Continue.
   11. Copy the consumer key that Salesforce provides.
3. Return to your Fuse Online Settings page and paste the Salesforce-provided consumer key into the Fuse Online Salesforce Client ID field.
4. Return to Salesforce and copy the consumer secret that Salesforce provides.
5. Return to your Fuse Online Settings page and paste the Salesforce-provided consumer secret into the Fuse Online Salesforce Client Secret field.
6. Click Save and then click Ok.

Procedure

1. In Fuse Online, in the left panel, click Connections to display available connections.
2. In the upper right, click Create Connection to display the available connectors. A connector is a template for creating one or more connections.
3. Click the Salesforce connector.

4. Click Connect Salesforce to display a Salesforce authorization page. You might need to log in to Salesforce before you see the authorization page.

   If Connect Salesforce does not appear, then your Fuse Online environment is not registered as a Salesforce client application. See Registering Fuse Online as a Salesforce client application. When you try to create a Salesforce connection and your Fuse Online environment is not registered as a Salesforce client application, then Fuse Online displays multiple fields that prompt for authorization information. While you can create a Salesforce connection by entering values in these fields, it is not recommended.

   Note

   The following error indicates that Salesforce does not have the correct Fuse Online callback URL:

   error=redirect_uri_mismatch&error_description=redirect_uri%20must%20match%20configuration

   If you get this error message, then in Salesforce, ensure that the Fuse Online callback URL is specified according to the instructions in Registering Fuse Online as a Salesforce client application.

5. Click Allow to return to Fuse Online.
6. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter SF Connect 1.
7. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter Sample Salesforce connection that uses my Salesforce login credentials.
8. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that SF Connect 1 appears as a connection that you can choose to add to an integration.

Procedure

1. Click the Salesforce connection that you want to add to the flow. When the integration uses the connection that you select to connect to Salesforce, Fuse Online uses the credentials defined in that connection.
2. Click the action that you want the selected connection to perform. Each Salesforce connection that you add to a flow performs only the action you choose.
3. Specify the Salesforce object that the action operates on, for example, it might be a contact, lead or price book entry. Click in the Object field to select from a list of Salesforce objects or enter the name of the object.
4. Click Done to add the connection to the flow.

1. Obtain two sets of OAuth credentials from SAP Concur:

   • One set for access to the SAP Concur implementation site
   • Another set for access to the SAP Concur production site
2. Configure the SAP Concur connector for access to the appropriate SAP Concur site.
3. Create a SAP Concur connection.

Procedure

1. In Fuse Online, in the left panel, click Settings.
2. On the Settings page, expand the SAP Concur entry.
3. In the Client ID field, enter the client ID that you received from SAP Concur.

4. In the Client Secret field, enter the client secret that you received from SAP Concur.

   Fuse Online populates the other fields.

5. Click Save.

   Fuse Online immediately tries to validate the configuration. If validation is not successful, correct the input values and try again. If validation is successful, you can create a SAP Concur connection, which you can add to an integration.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display the available connectors. A connector is a template that you use to create one or more connections.
3. Click the SAP Concur connector.

4. In the Configure Connection page, click Connect SAP Concur, which takes you to the SAP Concur site for which the connector is configured.

   If Connect SAP Concur does not appear, then the SAP Concur connector in your Fuse Online environment is not configured. See Configuring the SAP Concur connector.

   If redirect_uri is improper or not previously registered appears, then the SAP Concur connector configuration is incorrect. Return to the Fuse Online Settings page to update and validate the connector configuration.

5. On the SAP Concur OAuth site:

   1. Enter the email address for the SAP Concur account that you want this connection to use to access SAP Concur.
   2. Ensure that Username is selected.
   3. Click Continue.
   4. Enter the SAP Concur password associated with the email address.
   5. Click Sign In, which returns you to Fuse Online.
6. In the Fuse Online Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter SAP Concur Test1.
7. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter Sample SAP Concur connection to the implementation site.
8. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that SAP Concur Test1 appears as a connection that you can choose to add to an integration.

Procedure

1. Click the SAP Concur connection that you want to add to the flow. When the integration uses the connection that you select to connect to SAP Concur, Fuse Online uses the credentials defined in that connection.

2. Click the action that you want the selected connection to perform. Each SAP Concur connection that you add to a flow performs only the action you choose.

   For details about SAP Concur actions, visit the SAP Concur developer center and expand v3.0.

3. Click Done to add the connection to the flow.

1. Click Data Mapper. When the data fields appear, the Sources panel on the left displays the fields that are available from the database connection. In this example, the source fields include concur-list-id and project-code. The Target panel on the right displays the SAP Concur id and content parameters for the update list action, which the connection performs.
2. Map the concur-list-id source field to the id target field.
3. Map the project-code source field to the content target field.
4. In the upper right, click Done to add the data mapper step to the integration.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display Fuse Online connectors.
3. Click the ServiceNow connector.

4. Configure this ServiceNow connection:

   1. In the Instance Name field, enter the name of the ServiceNow instance that you want to obtain records from or copy records to. For example, if the URL for your ServiceNow instance is https://abc12345.service-now.com, the instance name is abc12345.
   2. In the User Name field, enter your ServiceNow user name.
   3. In the User Password field, enter your ServiceNow password.
   4. Optionally, in the Client ID field, enter your client ID if you received one from your ServiceNow administrator.
   5. Optionally, in the Client Secret field, enter your client secret if you received one from your ServiceNow administrator.
   6. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, update the configuration details as needed and try again.
   7. When validation is successful, click Next.
5. In the Connection Name field, enter a name that helps you distinguish this connection from other connections. For example, enter ServiceNow Con 1.
6. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter ServiceNow connection that uses administrative credentials.
7. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that ServiceNow Con 1 appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the ServiceNow connection that you want to use to start the integration.
4. On the Choose an Action page, click Retrieve Record to obtain records from a ServiceNow table that you select.

5. Configure the Retrieve Record action:

   1. Click in the Table name field and select the table that you want to obtain records from.
   2. In the Query to filter the result set field, enter a ServiceNow query. For example, consider the state=1^impact=2 query on a table that keeps records about incidents. This query returns records for new incidents (state=1) that have a medium impact (impact=2). If you do not enter a query and the records in the table do not change, the connection obtains the same records every time.
   3. In the Limit of elements per page field, enter the maximum number of records that you want the connection to obtain. In this release, you must enter a value, the recommendation is to enter 1000 or less, and pagination is not supported.
   4. In the Period field, indicate how often you want to obtain records. The default is every minute. In other words, by default, Fuse Online executes this integration every 60 seconds.
   5. Click Done.

Procedure in ServiceNow

1. In ServiceNow, search for web services.
2. In the results, under System Web Services > Inbound, click Create New.

3. In the Create Web Service page:

   1. In the Label field, specify the display name for the web service. The web service’s import set will also have this name.
   2. In the Target table field, select the ServiceNow table that this service updates.
   3. Select Copy fields from target table. This creates an import set that has the same schema as the target table. The import set is a staging area for updating the target table.
   4. Select Create transform map. This map enables ServiceNow to copy and transform data from the import set to the target table.
4. Click Create.
5. In the next display, under Related Links, click Auto Map Matching Fields to display a list of fields in the target table that you selected.

6. Select one target table field to be the correlation (or coalesce) field.

   When the value of the correlation field in a record in the import set matches the value of a correlation field in the target table, ServiceNow updates that record in the target table rather than creating a new record.

7. Select Coalesce to identify the field that you just selected as the correlation field. Without a correlation field, ServiceNow adds each record in the import set to the target table.
8. Click Update.

9. Confirm that the transform map was created:

   1. In ServiceNow, search for transform map.
   2. Under System Import Sets, click Transform Maps to display a list of transform maps.
   3. In this list, confirm that there is a transform map whose name is the value that you specified for the label of the web service that you created.

Procedure

1. Click the ServiceNow connection that you want to add to the integration.
2. Click the Add Record action.
3. Click in the Import Set field and select the import set that you want to add records to.
4. Click Next.

1. Add the Salesforce connection as the start connection.

   • To create the integration that obtains new cases, select the On create action.
   • To create the integration that obtains updated cases, select the On update action.
2. Select the Case object for the action to operate on. This Salesforce connection returns new Case objects or updated Case objects according to the chosen action.
3. Add the ServiceNow connection as the finish connection.

4. Select the Create Record action, and then select Cases from Salesforce as the import set that the integration updates.

   This ServiceNow connection adds new or updated Salesforce cases to the Cases from Salesforce import set.

5. Add a data mapper step that maps:

   • Salesforce case id to the ServiceNow import set’s correlation_Id
   • Salesforce subject to the ServiceNow short_description
   • Salesforce description to the ServiceNow description

6. Give the integration a name and then publish it.

   • For the integration that obtains new cases, use On SF Create Case.
   • For the integration that obtains updated cases, On SF Update Case.

1. In Salesforce, create a case.
2. In Fuse Online, view the summary for the On SF Create Case integration. Click its Activity tab to see that Fuse Online executed the integration once.
3. In ServiceNow, view the Incidents table. You should see a new incident that has the subject and description that you specified in Salesforce.
4. Back in Salesforce, update the case that you just created by changing its subject.
5. In Fuse Online, view the summary for the On SF Update Case integration. Click its Activity tab to see that Fuse Online executed the integration once.
6. In ServiceNow, view the Incidents table and expand the entry for the incident that was previously new. You should see that this incident has an updated short_description value. ServiceNow checks the import set entry for the value of its correlation_Id. If this value already exists in the Incidents table, ServiceNow updates the incident that has that value.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display Fuse Online connectors.
3. Click the Slack connector.
4. In the Slack webhook URL field, enter the webhook URL for your Slack app.
5. In the Token for accessing Slack API field, enter the Slack-provided token, which you can obtain from Slack.

6. Optionally, enter values for additional parameters:

   • In the Sending username for messages field, enter the user name that the bot has when it sends messages to Slack.

   • In the Message avatar emoji field, specify one emoji, which the bot uses as the message avatar when it sends a message. Examples: :smile:, :wave:, :question:.

     Tip

     Search the web for emoji cheat sheet to see some emoji codes.

   • In the Message avatar icon URL field, specify the URL of the avatar that the bot uses when it sends messages to Slack.

   If you specify an emoji and an icon URL, then the integration uses the icon URL. If you specify neither an emoji nor an icon URL, then the message is sent without an avatar.

7. Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise the connection configuration values and try again.
8. If validation is successful, click Next.
9. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter Slack for Tracking Company Sales.
10. In the Description field, optionally enter any information that is helpful to know about this connection.
11. In the upper right, click Create to see the updated list of available connections, including the connection that you just created. If you entered the example name, you would see that Slack for Tracking Company Sales appears as a connection that you can choose to add to an integration. You can add this connection to any number of integrations.

Procedure

1. Click the Slack connection that you want to use to start the integration.
2. Click the Read Messages action.
3. In the Channel field, specify the Slack channel from which you want to obtain messages.
4. In the Delay field, accept the default of 500 milliseconds as the time that elapses between polls for messages. Or, to specify a different interval for checking for messages, enter a number and select its time unit.

5. In the Maximum Messages to Retrieve field, accept the default of 10 or indicate the maximum number of messages that the connection can return for each poll. If the connection finds more than this number of unread messages, then it returns the most recent messages. The connection returns a particular message only once.

   For example, if you accept the default of 10 and there are 15 messages at the time of a poll then the connection returns the 10 most recent messages. At the next poll, the connection checks for messages that have a time stamp that is after the most recent message that the connection previously returned. This means that the 5 messages that were not returned in the first example poll are never returned.

   When a Slack connection returns more than one message, the integration processes the messages as a batch. In other words, Fuse Online executes the integration once for the batch.

6. Click Done to add the connection to the integration.

Procedure

1. Click the Slack connection that you want to add to the flow.

2. Select the action that you want the connection to perform.

   • Click Username to send a message to one user. To configure this action, in the User name field, specify the Slack name of the user to send the message to.
   • Click Channel to publish a message on a channel. To configure this action, in the Channel field, specify the channel to publish the message to.
3. Click Done to add the connection to the flow.
4. Optionally, add additional connections to the flow. Whether additional connections are needed depends on what you want the flow to do. The important point is to add all connections before you continue.
5. Add a data mapping step just before the Slack connection that you added in this procedure. In the mapping step, map a string from a data mapping source to the Slack message field. This string should contain the message that you want to send to the Slack user or channel. See Adding a data mapping step.

Procedure

1. Ensure that the JDBC driver for the database that you want to connect to is on your classpath. If you uploaded a JDBC driver library extension to connect to a proprietary database, then the upload process puts the driver on your classpath. See Creating JDBC driver library extensions.
2. In Fuse Online, in the left panel, click Connections to display any available connections.
3. In the upper right, click Create Connection to display Fuse Online connectors.
4. Click the Database connector.

5. Configure the connection by entering:

   1. In the Connection URL field, enter the JDBC URL for the database that you want to connect to. For example, enter jdbc:postgresql://ignite-db1234/sampledb.
   2. In the Username field, enter the name of the account that you want to use to access the database. Ensure that the specified password and user name are for the same account.
   3. In the Password field, enter the password associated with the user account you want to use to access the database.
   4. In the Schema field, enter the name of the schema for the database. If the connection URL specifies the schema, ensure that this field indicates the same schema as the connection URL. For example, enter sampledb.
6. Click Validate. Fuse Online tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise the configuration details as needed and try again.
7. If validation is successful, click Next.
8. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter PostgreSQL DB 1.
9. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter Sample PostgreSQL connection that uses my login credentials.
10. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that PostgreSQL DB 1 appears as a connection that you can choose to add to an integration.

Procedure

1. In the Fuse Online panel on the left, click Integrations.
2. Click Create Integration.
3. On the Choose a Start Connection page, click the database connection that you want to use to start an integration.

4. On the Choose an Action page, click one of the following:

   • Periodic SQL invocation obtains data by periodically invoking the SQL query you specify.
   • Periodic stored procedure invocation obtains data by periodically invoking the stored procedure that you specify or select.

5. If you selected Periodic SQL invocation, in the Query field, enter a SQL SELECT statement to obtain one or more records. For example: SELECT * from my_db_table. The database table that contains the data you want must already exist.

   If you selected Periodic stored procedure invocation, in the Procedure name field, select or enter the stored procedure to invoke to obtain the data of interest. The stored procedure you specify must already exist. The database administrator should have created any stored procedures you need to use in an integration.

6. In the Period field, enter an integer and indicate whether the unit is milliseconds, seconds, minutes, hours, or days. For example, if you specify 5 minutes then the connection invokes the specified query or stored procedure every five minutes.
7. Click Done.

Procedure

1. Click the database connection for the database that you want to access.

2. On the Choose an Action page, click one of the following:

   • Invoke SQL operates on data by executing the SQL statement you specify.
   • Invoke stored procedure operates on data by invoking the stored procedure that you specify or select.

3. If you selected Invoke SQL, in the SQL Statement field:

   • For a middle connection, enter a SQL SELECT statement that obtains one or more records or enter a SQL INSERT, UPDATE, or DELETE statement that operates on one or more records. The database table that contains the data must already exist.
   • For a finish connection, enter a SQL INSERT, UPDATE or DELETE statement to operate on one or more records.

   If you selected Invoke stored procedure, in the Procedure name field, select or enter the name of the stored procedure to invoke to operate on the data of interest. The stored procedure you specify must already exist. The database administrator should have created any stored procedures you need to use in an integration.

   • See the information below about specifying placeholder parameters in queries.
4. Click Done.

1. A developer creates a library extension that contains the JDBC driver for the database that you want to access in an integration. See Creating JDBC driver library extensions.
2. The developer provides a .jar file that contains the library extension.
3. You upload that .jar file to Fuse Online. See Making extensions available.
4. You create a connection to your database by selecting the Fuse Online Database connector and specifying the connection URL for your database. See Creating a database connection.
5. In an integration, you add the connection to your database. See Starting an integration by accessing a database or Accessing a database in the middle or to complete an integration.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display Fuse Online connectors.
3. Click the Telegram connector.
4. In the Authorization Token field, enter the Telegram authorization token for the bot that you want to get messages from and send messages to.
5. Click Next.
6. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter Telegram for Product Mentions.
7. In the Description field, optionally enter any information that is helpful to know about this connection.
8. In the upper right, click Create to see the updated list of available connections, including the connection that you just created. If you entered the example name, you would see that Telegram for Product Mentions appears as a connection that you can choose to add to an integration. You can add this connection to any number of integrations.

Procedure

1. Click the Telegram connection that you want to use to start the integration.

2. Click the Read Messages action to receive all messages that are sent to the chat bot.

   The connection configuration identifies the chat bot that you want to receive messages from. No other configuration is required.

Procedure

1. Click the Telegram connection that you want to add to the flow.
2. Click the Send a Text Message action.

3. In the Chat Id field, enter the ID for the Telegram chat that you are sending a message to.

   If you leave this field blank, and if there is an earlier Telegram connection that receives messages, then Fuse Online uses the chat ID that is in an incoming message.

   To obtain the ID for a chat:

   1. In Telegram, add a bot to the chat that you want to send a message to. The BotFather response includes a bot access token.
   2. Copy the access token to the clipboard.
   3. In Telegram, send a message directly to that chat. Do not use the bot to send the message.

   4. Read messages that are sent to that chat by invoking a curl command in the following format. Replace bot-access-token with the access token in the clipboard.

      curl https://api.telegram.org/bot-access-token/getUpdates\?offset\=0

      The response is in JSON format. The JSON chat object contains the chat ID.

4. Click Done to add the connection to the flow.

Procedure

1. In Fuse Online, on the left, click Integrations.
2. In the upper right, click Create Integration.

3. On the Choose a Start Connection page, click the Timer connection.

   Fuse Online provides a Timer connection; you do not need to create a timer connection. However, if you inadvertently deleted the provided Timer connection and created a new timer connection then you might have given it a different name.

4. On the Choose an Action page, click Cron Timer or Simple Timer.

   • A cron timer requires a cron expression that specifies the schedule for triggering integration execution.
   • A simple timer prompts you to specify a period and its time unit, for example, 5 seconds, 1 hour. Available units are milliseconds, seconds, minutes, hours, days.
5. According the type of timer that you are adding, enter a cron expression or a period with a selected time unit.
6. Click Done to add the Timer connection as the integration’s start connection.

Procedure

1. In Fuse Online, in the left panel, click Connections.
2. In the upper right, click Create Connection.
3. Click the Timer connector.
4. In the Add Connection Details page, enter a name for the connection, for example, Timer.
5. Optionally, enter a description that distinguishes this connection.
6. In the upper right, click Create. Fuse Online displays a list of available connections and you can see the timer connection that you just created.

Procedure

1. In Fuse Online:

   1. In the left panel, click Settings.
   2. On the Settings page, near the top, to the right of the callback URL, click to copy the callback URL for your installation of Fuse Online to the clipboard. You will need this URL later in this procedure.
   3. To the right of the Twitter entry, click Register to display the Consumer API Key and ConsumerAPI Secret Key fields.

2. In another browser tab, go to your Twitter developer account, sign in if you need to, and do the following:

   1. In the upper right, next to the name of your developer project, click the down caret and click Apps.
   2. In the upper right, click Create an app.
   3. In the App name field, enter a name such as My Fuse Online Client.
   4. In the Application description field, enter a tip such as For leveraging tweets.
   5. In the Website URL field, paste the URL that you copied at the beginning of this procedure and remove api/v1/credentials/callback from the end of the URL.
   6. Select Enable Sign in with Twitter.
   7. In the Callback URLs field, paste the URL again. It should be something like this: https://app-proj912876.7b63.fuse-ignite.openshiftapps.com/api/v1/credentials/callback.
   8. A 100-character description of how you plan to use this app is required. For convenience, you can copy and paste: This is a demo application so that I can evaluate how to integrate Twitter with my enterprise applications.
   9. Click Create.
   10. Click Create again to confirm that you reviewed the developer terms.
   11. At the top of the page for the app you just created, click the Keys and tokens tab.
   12. Copy the consumer API key.
3. Return to your Fuse Online Settings page and paste the Twitter consumer API key into the Fuse Online Twitter Consumer API Key field.
4. Return to the Twitter Keys and tokens tab and copy the consumer API secret key.
5. Return to your Fuse Online Settings page and paste the Twitter consumer API secret key into the Fuse Online Twitter Consumer API Secret Key field.
6. Click Save and then click Ok.

Procedure

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display the available connectors. A connector is a template that you use to create one or more connections.
3. Click the Twitter connector.

4. Click Connect Twitter to display a Twitter authorization page. You might need to log in to Twitter before you see the authorization page.

   If Connect Twitter does not appear, then your Fuse Online environment is not registered as a Twitter client application. See Registering Fuse Online as a Twitter client application. When you try to create a Twitter connection and your Fuse Online environment is not registered as a Twitter client application, then Fuse Online displays multiple fields that prompt for authorization information. While you can create a Twitter connection by entering values in these fields, it is not recommended.

5. Click Authorize app to return to Fuse Online.
6. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter Twitter Connect 1.
7. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter Sample Twitter connection that uses my Twitter login credentials.
8. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that Twitter Connect 1 appears as a connection that you can choose to add to an integration.

Procedure

1. Click the Twitter connection that you want to add to the integration. When the integration uses the selected connection to connect to Twitter, Fuse Online uses the credentials defined in that connection.

2. Click the action that you want the selected connection to perform. A Twitter connection that you add to an integration performs only the action you choose.

   • Mention triggers execution of the integration when a tweet contains your handle.
   • Search triggers execution of the integration when a tweet contains text that you specify.
3. Optionally, enter the configuration information that Fuse Online prompts for. For example, the Search action prompts you to specify how often to search and keywords to search for.
4. Click Done to add the connection to the integration.

1. Decide whether you want to send a GET or POST request to Fuse Online.
2. Plan your integration to handle this request.

3. Create the connection that finishes the integration.

   Fuse Online provides a Webhook connection that you use as the start connection.

4. Create any other connections that you want to add to the integration.

5. Create the integration:

   1. Add the Webhook connection as the start connection.

   2. Add the finish connection and then any other connections that are required in the integration. The finish connection and any middle connections handle the HTTP request that triggers execution of the integration. It is up to you to choose and specify the most appropriate HTTP request for accomplishing your goals. Keep the following in mind:

      • Add a connection to the application that contains the data that you want to obtain or that contains the data that you want to update.
      • A GET request is limited to specification of key/value parameters.
      • A POST request can provide an arbitrary body, such as an XML or JSON instance.
      • Fuse Online returns only an HTTP status header and does not return any data. Consequently, you can define an integration that is triggered by a GET request and that updates data rather than obtaining data. Likewise, you can define an integration that is triggered by a POST request and that obtains data rather than updating data.

   3. Add a data mapper step after the Webhook connection.

      For a GET request, map the parameter fields in the HTTP request to the data fields in the next connection.

      For a POST request, you might have specified the output data shape in the request by passing a JSON instance, JSON schema, XML instance, or XML schema. If you did not, then when you add a Webhook connection as the start connection of an integration, Fuse Online prompts you to specify the output data type. If you do not, then the default Webhook connection output data type is in JSON format.

   4. Add any other steps that the integration needs.
6. Publish the integration and wait for it to be Running.
7. Go to the integration summary page and copy the external URL that Fuse Online provides.
8. Modify this external URL to construct your GET or POST request.
9. Implement the application that sends the HTTP GET or POST request to Fuse Online.

Procedure:

1. In Fuse Online, in the left panel, click Connections to display any available connections.
2. In the upper right, click Create Connection to display connectors.
3. Click the Webhook connector.
4. In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, you might enter Webhook 1.
5. In the Description field, optionally enter any information that is helpful to know about this connection. For example, enter Sample Webhook connection.
6. In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that Webhook 1 appears as a connection that you can choose to add to an integration.