1. Create a connection to each application that you want to integrate.

2. Select the start connection. This connection is to the application that contains the data that you want to share with another application.

   Alternatively, you can start the integration with a timer or a webhook that accepts an HTTP request.

3. Select the finish connection. This connection is to the application that receives data from the start connection and that completes the integration.
4. Map data fields from the start connection to data fields in the finish connection.
5. Give the integration a name.
6. Click Publish to start running the integration.

Procedure overview

1. In the Fuse Online OAuth Application Management page, in the entry for the application with which you want to register Fuse Online, click Register to display the client ID and client secret fields.
2. Near the top of the OAuth Application Management page, where you see During registration, enter this callback URL:, copy that URL to the clipboard.
3. In another browser tab, go to the web site for the application that you want to register with and perform the steps required to obtain a client ID and secret. One of these steps requires you to enter the callback URL for your Fuse Online environment. Paste the URL that you copied to the clipboard in the second step.
4. In Fuse Online, on the Settings page, paste the client ID and client secret and save the settings.

1. In the left panel, click Connections.
2. Click the connection that you want to validate or for which you want to obtain a new access token.
3. In the connection’s details page, click Validate or click Reconnect.

1. Determine whether an application that you want to connect to uses the OAuth protocol. For each application that uses OAuth, register Fuse Online as a client that is authorized to access that application. Applications that use the OAuth protocol include:

   • Dropbox
   • Gmail
   • Google Calendar
   • Salesforce
   • SAP Concur
   • Twitter
2. Determine whether an application that you want to connect to uses HTTP basic authentication. For each application that does, identify the user name and password for accessing that application. You need to provide this information when you create the integration.
3. For each application that you want to integrate, create a connection.

Procedure

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

3. Choose and configure the start connection:

   1. On the Choose a Start Connection page, click the connection that you want to use to start the integration. When this integration is running, Fuse Online will connect to this application and obtain data that you want the integration to operate on.
   2. On the Choose an Action page, click the action you want this connection to perform. The available actions vary for each connection.
   3. On the page for configuring the action, enter values in the fields.
   4. Optionally, if the connection requires data type specification, Fuse Online prompts you to click Next to specify the input and/or output type of the action.
   5. Click Done to add the start connection.

   As an alternative to connecting to an application, a start connection can be a timer that triggers integration execution at intervals that you specify or it can be a webhook that accepts HTTP requests.

4. Choose and configure the finish connection:

   1. On the Choose a Finish Connection page, click the connection you want to use to complete the integration. When this integration is running, Fuse Online will connect to this application with the data that the integration has been operating on.
   2. On the Choose an Action page, click the action you want this connection to perform. The available actions vary for each connection.
   3. On the page for configuring the action, enter values in the fields.
   4. Optionally, if the connection requires data type specification, Fuse Online prompts you to click Next to specify the input and/or output type of the action.
   5. Click Done to add the finish connection.

   As an alternative to connecting to an application, a finish connection can send information to the integration’s log about the messages that the integration processed.

5. Optionally, add one or more connections between the start connection and the finish connections. For each connection, choose its action and enter any required configuration details.
6. Optionally, add one or more steps that operate on integration data between connections. See About adding steps between connections.
7. When the integration contains all needed steps, click Save as Draft or Publish according to whether you want to start running the integration.
8. In the Integration Name field, enter a name that distinguishes this integration from any other integrations.
9. In the Description field, enter a description, for example, you can indicate what this integration does.
10. If you are ready to start running the integration, in the upper right, click Publish. Otherwise, click Save as Draft.

Procedure

1. In the left panel, where you want to add a data mapper step, hover over the .
2. In the popup that appears, click Add a Step.
3. On the Choose a Step page, click Data Mapper to display source and target fields.

Procedure

1. In the left panel, where you want to add a filter step to the integration, hover over the and in the popup that appears, click Add a Step.
2. On the Add a Step page, click Basic Filter.

3. On the Configure Basic Filter Step page, in the Continue only if incoming data match field, select one of the following options:

   • Accept the default that all defined rules must be satisfied.
   • Indicate that only one rule must be satisfied by selecting ANY of the following.

4. Define the filter rule:

   1. For this field: In the field on the left, enter the name of the field that contains the content you want the filter to evaluate. For example, suppose the data coming in to the step consists of tweets that mention your Twitter handle. You want to continue the integration only when the tweet contains certain content. The tweet is in a field named text so you enter or select text as the value in the first field.

      You can define the field value in the following ways:

      • Start typing. The data name field has a typeahead feature that provides a list of possible completions for you in a pop-up box. Select the correct one from the box.
      • Click in the text field. A dropdown box appears with a list of available fields. Select the field of interest from the list.
   2. This condition must be satisfied: In the middle field, select a condition from the dropdown box. The setting defaults to Contains. For the integration to continue, the condition that you select in this field must be true for the value that you enter in the third field.
   3. For this value: In the third field, enter a value to filter on. For example, if you want to operate on mentions of a certain product from the Twitter feed, you would enter the product name here.

5. Optionally, click + Add another rule and define another rule.

   You can delete a rule by clicking the trash can icon next to the entry.

6. When the filter step is complete, click Done to add it to the integration.

Procedure

1. In the left panel, where you want to add an advanced filter step to the integration, hover over the and in the popup that appears, click Add a Step.
2. Select Advanced Filter.

3. In the edit box, use the Camel Simple Expression language to specify a filter expression. For example, the following expression evaluates to true when the message header’s type field is set to widget:

   ${in.header.type} == 'widget'

   In the following example, the expression evaluates to true when the body of the message contains a title field:

   ${in.body.title}

4. Click Done to add the advanced filter step to the integration.

Procedure

1. In the integration visualization panel on the left, hover over the at the location where you want to add a log step.
2. In the popup, click Add a Step.
3. On the Choose a Step page, click Log.

4. On the Configure Log Step page, select the content that you want to log. If you select Custom text, then in the text input field, enter one of the following:

   • The text that you want to log
   • A Camel Simple language expression

   If you enter an expression, Fuse Online resolves the expression and logs the resulting text.

5. When log step configuration is complete, click Done to add the step to the integration.
6. When the integration is complete, publish it to start seeing output from the new log step.

Procedure

1. In the integration visualization panel on the left, hover over the at the location where you want to add a template step.
2. In the popup, click Add a Step.
3. On the Choose a Step page, click Template. The Upload Template page opens and prompts you to choose how you want to define the template.

4. To define the template, do one of the following:

   • Drag and drop a template file or a file that contains text that you want to modify to create a template, into the template editor.
   • Click browse to upload, navigate to a file, and upload it.

   • In the template editor, start typing to define a template.

     Note that you might upload a template that is valid in other environments but that has errors in Fuse Online. Fuse Online requires that you append the body. prefix to each placeholder inside double curly braces. For example, while {{text}} is valid in a typical template, you must specify {{body.text}} in a template that you use with Fuse Online. Here is an example of a valid template:

   At {{body.time}}, {{body.name}} tweeted:
   {{body.text}}

5. In the template editor, ensure that the template is valid for use with Fuse Online. Fuse Online displays to the left of a line that contains a syntax error. Hovering over a red indicator displays hints about how to resolve the error.

   Inside each set of double curly braces, the body. prefix is required. Data mapping does not work if the body. prefix is missing. For example, if you upload a template that does not have the body. prefix on each placeholder, Fuse Online displays an error icon on those lines.

6. Click Done to add the template step to the integration.

   If the Done button is not enabled then there is at least one syntax error that you must correct.

   Input to a template step must be in the form of a JSON object. Consequently, you must add a data mapping step before a template step.

7. To add a data mapper step before the template step:

   1. In the left panel, hover over the that is immediately before the template step that you just added and then click Add a Step.
   2. On the Choose a Step page, click Data Mapper.

   3. In the data mapper, map a source field to each template placeholder field.

      For example, using the template above, map a source field to each of these template fields:

      • body.time
      • body.name
      • body.text
   4. In the upper right, click Done to add the data mapper step to the integration.

   Output from a template step is always a JSON object. Consequently, you must add a data mapper step after a template step.

8. To add a data mapper step after the template step:

   1. In the left panel, hover over the that is immediately after the template step you just added and then click Add a Step.
   2. On the Choose a Step page, click Data Mapper.
   3. In the data mapper, map the template’s message field, which always contains the result of inserting source fields into the template, to a target field. For example, suppose that a Gmail connection is next in the integration and you want to send the result of the template step as the content of a Gmail message. To do this, you would map the message source field to the text target field.
   4. In the upper right, click Done.

Procedure

1. In the left panel, where you want to add a custom step to the integration, hover over the and in the popup that appears, click Add a Step.

2. On the Add a Step page, click the custom step that you want to add.

   The list of available steps includes any custom steps that are defined in extensions that were uploaded to your Fuse Online environment.

1. Respond to prompts for any information that is required to perform the step. This information varies for each custom step.

Procedure

1. In the integration visualization panel on the left, look for any icons.

2. Click the icon to see the message. A Data Type Mismatch notification indicates that you need to add a data mapper step before that connection.

   In the integration’s visualization panel, to the right of a connection, click to display information about that connection, including its input and/or output type.

Procedure

1. In the Sources panel, click the data field that you want to map from.

   You might need to expand an integration step to see the data fields that it provides.

   When there are many source fields, you can search for the field of interest by clicking the and entering the name of the data field in the search field.

2. In the Target panel, click the data field that you want to map to.

   The data mapper displays a line that connects the two fields that you just selected.

3. Optionally, preview the data mapping result. This is useful when you add a transformation to the mapping or when the mapping requires a type conversion.

   1. In the upper right of the data mapper, click and select Show Mapping Preview to display a text input field on the source field and a read-only result field on the target field.
   2. In the source field’s data input field, enter text. Click somewhere outside this text box to display the mapping result in the read-only field on the target field.
   3. Optionally, to see the result of a transformation, add a transformation in the Mapping Details panel.
   4. Hide the preview fields by clicking again and selecting Show Mapping Preview.

4. Optionally, to confirm that the mapping is defined, in the upper right, click to display the defined mappings.

   You can also preview data mapping results in this view. If preview fields are not visible, click and select Show Mapping Preview. Enter data as described in the previous step. In the table of defined mappings, preview fields appear for only the selected mapping. To see preview fields for another mapping, select it.

   Click again to display the data field panels.

5. In the upper right, click Done to add the data mapper step to the integration.

1. In the Configure Mapper page, in the upper right, click the plus sign to display the Mapping Details panel.
2. In the Sources section, enter the name of the source field.
3. In the Action section, accept the default Map action.
4. In the Target section, enter the name of the field that you want to map to and click Enter.

Procedure

1. In the Target panel, click the field into which you want to map more than one source field.

2. In the Sources panel, if there is a field that contains the fields that you want to map to the target field, then click that container field to map all contained fields to the target field.

   To individually select each source field, click the first field that you want to combine into the target field. For each of the other fields that you want to combine into the target field, hover over that field, and press CTRL-Mouse1 (CMD-Mouse1 on MacOS).

   The data mapper automatically changes the field action from Map to Combine.

   When you are done you should see a line from each of the source fields to the target field.

3. In the Mapping Details panel, in the Separator field, accept or select the character that the data mapper inserts in the target field between the content from different source fields. The default is a space.

4. In the Mapping Details panel, under Sources, ensure that the source fields are in the same order as the corresponding content in the compound target field.

   If necessary, drag and drop source fields to achieve the same order. The data mapper automatically updates the index numbers to reflect the new order.

5. If you mapped a source field to each part of the compound target field, then skip to the next step.

   If the target field expects data that is not available to be mapped, then in the Mapping Details panel, edit the index of each source field so that it is the same as the index of the corresponding data in the compound target field. The data mapper automatically adds padding fields as needed to indicate missing data.

   If you accidentally create too many padding fields, click the trash-can icon on each extra padding field to delete it.

6. Optionally, preview the data mapping result:

   1. In the upper right of the data mapper, click and select Show Mapping Preview to display a text input field on each source field for the currently selected mapping and a read-only result field on the target field of the currently selected mapping.

   2. In the source data input fields, enter text. Click outside the text box to display the mapping result in the read-only field on the target field.

      If you reorder the source fields or add a transformation to the mapping then the result field on the target field reflects this. If the data mapper detects any errors, it displays informative messages at the top of the Mapping Details panel.

   3. Hide the preview fields by clicking again and selecting Show Mapping Preview.

      If you redisplay the preview fields, any data that you entered in them is still there and it remains there until you exit the data mapper.

7. To confirm that the mapping is correctly defined, in the upper right, click to display the mappings defined in this step. A mapping that combines the values of more than one source field into one target field looks like this: .

   You can also preview mapping results in this view. Click , select Show Mapping Preview, and enter text as described in the previous step. Preview fields appear for only the selected mapping. Click another mapping in the table to view preview fields for it.

Procedure

1. In the Sources panel, click the field whose content you want to separate.
2. In the Target panel, click the first field that you want to separate the source field data into.

3. In the Target panel, for each additional target field that you want to contain some of the data from the source field, hover over the field and press CTRL-Mouse1 (CMD-Mouse1 on MacOS) to select it.

   The data mapper automatically changes the field action to Separate.

   When you are done selecting target fields, you should see lines from the source field to each of the target fields.

4. In the Mapping Details panel, in the Separator field, accept or select the character in the source field that indicates where to separate the source field values. The default is a space.

5. In the Mapping Details panel, under Targets, ensure that the target fields are in the same order as the corresponding content in the compound source field.

   If necessary, drag and drop target fields to achieve the same order. The data mapper automatically updates the index numbers to reflect the new order.

6. If you mapped each part of the compound source field to a target field, then skip to the next step.

   If the source field contains data that you do not need, then in the Mapping Details panel, edit the index of each target field so that it is the same as the index of the corresponding data in the compound source field. The data mapper automatically adds padding fields as needed to indicate unwanted data.

7. Optionally, preview the data mapping result:

   1. In the upper right of the data mapper, click and select Show Mapping Preview to display a text input field on the source field and read-only result fields on each target field.

   2. In the source field’s data input field, enter text. Be sure to enter the separator character between the parts of the field. Click outside the text box to display the mapping result in the read-only fields on the target fields.

      If you reorder the target fields or add a transformation to a target field then the result fields on the target fields reflect this. If the data mapper detects any errors, it displays informative messages at the top of the Mapping Details panel.

   3. Hide the preview fields by clicking again and selecting Show Mapping Preview.

      If you redisplay the preview fields, any data that you entered in them is still there and it remains there until you exit the data mapper.

8. To confirm that the mapping is correctly defined, click to display the mappings defined in this step. A mapping that separates the value of a source field into multiple target fields looks like this: .

   You can also preview mapping results in this view. Click , select Show Mapping Preview, and enter text as described in the previous step. Preview fields appear for only the selected mapping. Click another mapping in the table to view preview fields for it.

Procedure

1. Map the fields. This can be a one-to-one mapping, a combination mapping, or a separation mapping.
2. In the Mapping Details panel, under Sources or under Targets, in the box for the field that you want to transform, click the arrow that points to the trash can. This displays a field where you can select the transformation that you want the data mapper to perform.
3. Click in this field to display the list of transformations.
4. Click the transformation that you want to perform.
5. If the transformation requires any input parameters, specify them in the appropriate input fields.
6. To add another transformation, click the arrow that points to the trash can again.

Procedure

1. In the upper right, click .
2. To dismiss the list of mappings and redisplay the source and target fields, click again.

Procedure

1. Learn about copying an integration to another environment.
2. Export the integration from the development environment. See Export an integration.
3. Import the integration into the test environment. See Import an integration.

Procedure

1. In the left Fuse Online panel, click Integrations.
2. In the list of integrations, click the entry for the integration that you want to update.

3. On the integration’s summary page, in the upper right corner, click Edit Integration.

   In the left panel, you can see that each step in the integration is represented by an icon that indicates whether it is a connection or a data operation between connections.

4. Update the integration as needed:

   • To add a step, in the left panel, hover over the plus sign that is in the location where you want to add it. Click Add a Connection or Add a Step.
   • To delete a step, in the left panel, click to the right of the step that you want to delete.
   • To change the configuration of a step, in the left panel, click the step that you want to update. In the configuration page, update the parameter settings as needed.

Procedure

1. In the left Fuse Online panel, click Integrations.
2. In the list of integrations, at the right of the entry for the integration that you want to delete, click and select Delete.
3. In the popup, click OK to confirm that you want to delete the integration.

1. In the left panel, click Integrations.
2. In the list of integrations, click the entry for the integration that stopped running.
3. In the integration’s summary page, in the visual integration flow, click the icon for the application that you want to reconnect to.
4. In the connection’s details page, click Reconnect.

5. Respond to that application’s OAuth workflow prompts.

   Fuse Online displays a message to indicate that its access to that application has been authorized. For some applications, this takes a few seconds but it can take longer for other applications.

6. After reconnecting to the application, start the integration.

1. Re-register Fuse Online as a client of the application. See General procedure for obtaining authorization.
2. Create a new connection.

3. Edit each integration that was using the old connection:

   1. Remove the old connection.
   2. Replace it with the new connection.
4. Publish each updated integration.

1. On the Choose a Start Connection page, click the API Provider card.

2. On the Start integration with an API call page, upload a file that contains an OpenAPI 2.0 schema or indicate that you want to create the schema now. If you upload a file, you can review and edit it. If you select Create from scratch, Fuse Online opens an editor that supports creation of OpenAPI schemas.

   Caution

   After you save or publish an API provider integration, you cannot update the OpenAPI definition for the REST API service. If you need to edit the OpenAPI definition then you must start over and create a new API provider integration.

3. Give the integration a name and save it.

4. On the Choose operation page, for each operation that the OpenAPI schema defines, create the integration flow for that operation:

   1. Click an operation to display the Add to Integration page.
   2. Add the connections that are required to implement the selected operation.
   3. Add additional steps that process data between connections. For example, in the visual representation of this integration flow, check for data type mismatch indications. For each data type mismatch, add a step that maps data fields.

   4. In the visual representation of this integration flow, click the flow’s finish connection and specify a return code. When Fuse Online executes this integration flow and reaches this connection, Fuse Online sends the return code to your API service, which in turn sends a response to the caller that invoked the API that triggered the integration.

      In this release, because an API provider integration is a Technology Preview feature, the integration flow always returns the code that you select. Error handling is not yet supported.

5. Publish the integration.

   Fuse Online provides the URL where your REST API service is available.

6. Optionally, use the curl utility to test the integration flows.

   For example, suppose that the following curl command triggers execution of an integration flow for the Get Task by ID operation. The HTTP GET command is the default request so there is no requirement to specify GET. The last part of the URL specifies the ID of the task to get:

   curl -k https://i-task-api-proj319352.6a63.fuse-ignite.openshiftapps.com/api/todo/1

Procedure

1. In Fuse Online, in the left navigation panel, click Integrations.
2. In the upper right, click Create Integration.
3. On the Choose a Start Connection page, click the API Provider card.

4. On the Start integration with an API call page, if you have an OpenAPI 2.0 schema that defines the REST API operations then upload it in one of the following ways:

   • Drag and drop the file that contains the schema.
   • Click Choose File to navigate to and select the file that contains the schema.
   • Click Use a URL and enter the URL for the schema.

   Or, if you need to define the schema, select Create from scratch.

5. Click Next.

   • If you uploaded a schema, remember that this is your only opportunity to change it. To review or edit the schema:

     1. Click Review/Edit to open the Apicurio editor.
     2. Review and edit as needed.
     3. In the upper right, click Save or Cancel to close the editor.
     4. Click Next and go to step 6 in this procedure.

   • If you are creating a schema from scratch then in the Apicurio editor that Syndesis opens:

     1. Define the OpenAPI schema.
     2. In the upper right, click Save, which closes the editor.
     3. Click Next.

   For information about using the Apicurio editor, see Design and develop an API definition with Apicurito. In this Technology Preview release, you cannot edit the operation description that will appear in the operations list in Fuse Online.

6. On the Give this integration a name page, enter a name for your integration.
7. Optionally, enter a description that helps you distinguish this integration from other integrations.
8. Click Save and continue to display the Choose Operation page. You are ready to define a flow for each operation.

Procedure

1. In the Choose operation page, click the entry for an operation whose flow you want to edit. This opens the Add to Integration page.

2. In the integration visualization panel on the left, click the icon at the bottom. When you hover over this icon, Provided API Return Path appears.

   Every API provider integration ends each integration flow by sending a response to the REST API caller that triggered execution of the integration flow.

3. Specify the operation’s return code as follows:

   1. In the Provided API Return Path page, click in the Return Code input field, which displays a list of possible return codes.

   2. Scroll to 200 OK and click it.

      If there is a return code that better describes the result then you can select that one instead. However, in this Technology Preview release, you can select only one return code. Whenever an API call triggers execution of this integration flow, this is the return code. This Technology Preview release does not support error handling.

   3. Click Done.

   4. In the upper right, click Save as Draft.

      After you implement the return code for at least one operation, you can publish the integration to start running it. When it is running, you can invoke an API call that triggers execution of the integration flow for which you defined the return code. However, you probably want to add more steps to the operation’s flow.

4. In this integration flow, to connect to another application or service:

   1. In the integration flow visualization panel on the left, hover over the plus sign in the location where you want to add a connection and in the popup that appears, click Add a connection.
   2. Click the connection that you want to add to this integration flow.
   3. Click the action that you want this connection to perform.
   4. Configure the action.
   5. Click Done.
   6. In the upper right, click Save as Draft.

   For each connection that you want to add to this integration flow, repeat this subset of instructions. Add all desired connections to the integration flow before you continue.

5. In this integration flow, to process data between connections:

   1. In the integration flow visualization panel on the left, hover over the plus sign in the location where you want to add a step and in the popup that appears, click Add a step.
   2. In the Choose a Step page, click the step that you want to add.
   3. Configure the step.
   4. Click Done.

   5. In the upper right, click Save as Draft.

      For help, see Adding steps between connections.

   Repeat this subset of instructions to add another step that processes data between connections.

6. In the integration flow visualization panel on the left, check for data type mismatch icons, which indicate that the connection cannot process the incoming data. You need to add a data mapper step here. Go back to the previous subset of instructions. On the Choose a Step page, click Data Mapper, and define the needed mappings. For help, see Map integration data fields to the next connection in the integration.

7. When this integration flow has all needed connections and steps, do one of the following:

   • To start running the integration, in the upper right, click Publish. This builds the integration and makes it available to be executed. You can publish the integration each time that you complete the creation of an operation’s integration flow or each time that you edit an operation’s integration flow.
   • To edit the integration flow for another operation, in the upper right, click Go to Operations List.

Procedure

1. To import the Task API quickstart integration:

   1. Go to https://github.com/syndesisio/syndesis-quickstarts/tree/master/api-provider and download TaskAPI-export.zip.
   2. In Fuse Online, in the left navigation panel, click Integrations.
   3. In the upper right, click Import.
   4. Drag and drop the zip file that you downloaded. Fuse Online indicates that it has successfully imported the file.
   5. In the left navigation panel, click Integrations to see an entry for the Task API integration that you just imported. The entry indicates that configuration is required.

2. To configure the Task API integration:

   1. Click the Task API entry to display the integration summary.
   2. In the upper right, click Edit Integration to display a list of the operations that this API provides.

   3. To configure the integration flow for the Create Task operation:

      1. Click the Create Task entry to display a page that prompts you to add a connection or add a step.

         Connections and steps have already been added to this integration flow. In the integration flow visualization panel on the left, move your cursor over the icons to see what they represent. Click a step or connection to view its configuration. When you are done examining one, click another one to examine it. When you click a database connection, you can see the SQL statement that it executes.

      2. In the integration flow visualization panel on the left, click the icon at the bottom. You might have to scroll down to see it. When you hover over it, Fuse Online displays Provided API Return Path.
      3. Click in the Return Code input field and scroll to select 201 Created.
      4. Click Done.
      5. In the upper right, click Save as Draft and then Go to Operation List.

   4. To configure the integration flow for the Delete Task for ID operation:

      1. Click the Delete Task for ID entry to display a page that prompts you to add a connection or add a step.

         This integration flow has a data mapper step and a connection to the sample database that is provided with Fuse Online. In the integration flow visualization panel, click the database connection to view the SQL statement that it executes.

      2. In the integration flow visualization panel, click the icon at the bottom.
      3. Click in the Return Code input field and scroll to select 200 OK.
      4. Click Done.
      5. In the upper right, click Save as Draft and then Go to Operation List.

   5. To configure the integration flow for the Get Task by ID operation:

      1. Click the Get Task by ID entry to display a page that prompts you to add a connection or add a step.

         This integration flow has two data mapper steps, a connection to the sample database that is provided with Fuse Online, and a log step. In the integration flow visualization panel, click an icon for a step or connection to view its configuration. When you are done examining one, click another one.

      2. In the integration flow visualization panel, click the icon at the bottom.
      3. Click in the Return Code input field and scroll to select 200 OK.
      4. Click Done.

3. In the upper right, click Publish.

   Fuse Online displays the integration summary page and shows publication progress as it assemblies, builds, deploys, and starts the integration. The integration summary page also provides the external URL for the API provider service, which looks something like this:

   https://i-task-api-proj319352.6a63.fuse-ignite.openshiftapps.com/api/

   This is where Fuse Online makes the Task API service available. REST API calls specify URLs that start with this base URL.

Procedure

1. In Fuse Online, in the left navigation panel, click Integrations.
2. Click the Task API integration to display its summary.
3. Copy the integration’s external URL.

4. In a terminal, invoke a command such as the following to assign the integration’s external URL to the externalURL environment variable. Be sure to replace the URL in this sample command with the URL you copied:

   export externalURL="https://i-task-api-proj319352.6a63.fuse-ignite.openshiftapps.com/api"

5. Invoke a curl command that triggers execution of the integration flow for the Create Task operation:

   curl -k --header "Content-Type: application/json" --request POST --data '{ "task":"my new task!"}' $externalURL/todo

   • -k allows curl to proceed and operate even for server connections that are otherwise considered insecure.
   • --header indicates that the command is sending JSON format data.
   • --request specifies the HTTP POST command, which stores data.
   • --data specifies the JSON format content to be stored. In this example the content is { "task":"my new task!"}.

   • $externalURL/todo is the URL to invoke.

     This command sends an HTTP POST request to the Task API service, which triggers execution of the Create Task operation’s integration flow. The integration flow adds a new task to the sample database and returns a message such as the following to indicate what it did:

   {"completed":false,"id":1,"task":"my new task!"}

6. Invoke a curl command that triggers execution of the integration flow for the Get Task by ID operation:

   curl -k $externalURL/todo/1

   To obtain a task, the curl command needs to specify only the URL. The HTTP GET command is the default request. The last part of the URL specifies the ID of the task to get.

7. Invoke a curl command that triggers execution of the integration flow for the Delete Task for ID operation:

   curl -k -X DELETE $externalURL/todo/1

   This command invokes the HTTP DELETE command with the same URL as the command that obtained a task by its ID.

1. A user with cluster administration permissions:

   1. Downloads the installation script.
   2. Registers a custom resource definition (CRD) at the cluster level.
   3. Grants permission for a user to install Fuse Online in their projects.

2. A user who is granted permission to install Fuse Online:

   1. Ensures that all prerequisites are met.
   2. Decides how to install Fuse Online with regard to the OpenShift project to install into, the OpenShift route for Fuse Online, and the level of accessibility of OpenShift logs.
   3. Downloads the installation script.
   4. Invokes the installation script with the command that implements decisions.
   5. Confirms that Fuse Online is running.

Procedure

1. Download the Fuse Online installation script to the current local directory by invoking the following command:

   $ wget https://raw.githubusercontent.com/syndesisio/fuse-online-install/1.5/install_ocp.sh

2. To verify that you are properly connected and can list custom resource definitions, invoke the following command:

   $ oc get crd

3. To register the custom resource definition at the cluster level, invoke the following command:

   $ bash install_ocp.sh --setup

4. Grant installation permission to each user who needs to install Fuse Online. For example, suppose you want to grant permission to an account with the user name developer. The following command grants permission to developer to install Fuse Online into any project that the developer account can access on the currently connected cluster:

   $ bash install_ocp.sh --grant developer --cluster

   Repeat this command for each user account that needs permission to install Fuse Online.

Procedure

1. Download the Fuse Online installation script to the current local directory by invoking the following command:

   $ wget https://raw.githubusercontent.com/syndesisio/fuse-online-install/1.5/install_ocp.sh

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

   $ oc login -u developer -p developer

3. Ensure that the current project is the project into which you want to install Fuse Online. To view the current project:

   $ oc project

4. In the directory in which you downloaded the installation script, invoke the installation script:

   • To perform the default installation, invoke:

     $ bash install_ocp.sh

   • To specify installation options, you might invoke something like the following command, which specifies three options:

     $ bash install_ocp.sh \
         --project my-project \
         --route my-project.6a63.fuse-online.openshiftapps.com \
         --console https://console.fuse-online.openshift.com/console

     • --project specifies the name of the OpenShift project in which you want to install Fuse Online. You need to specify this option only when you want to install Fuse Online into an OpenShift project other than the current OpenShift project.

     • --route specifies the URL that your Fuse Online environment will have. This URL will be where you access your Fuse Online environment. This URL specifies the project in which you are installing Fuse Online followed by the domain that is specific to your OpenShift cluster.

       In other words, specify the project name followed by the hostname that is associated with the OpenShift route that is used to access Fuse Online. The DNS resolution of the specified hostname must point to the OpenShift Router.

     • --console specifies the full URL for your OpenShift console.

   To learn more about the installation script options, invoke the $ bash install_ocp.sh --help command.

5. Confirm that installation was successful:

   1. Display the OpenShift OAuth proxy log-in page at https://openshift-route.

      If you specified the --route option when you ran the installation script, replace openshift-route with the route name that you specified. If you chose to let the installation script calculate the OpenShift route, then the script displays the calculated route near the end of its execution. Replace openshift-route with the value that the script provided.

   2. If you are not already logged in to the OpenShift console, its log-in page appears. Enter your OpenShift user name and password to log in.

   The Fuse Online home page appears either immediately or after you log in to the OpenShift console.

Procedure

1. Log in to the OpenShift console.
2. Open the project in which you installed Fuse Online.
3. In the left pane of the OpenShift console, select Applications > Routes.
4. Click the syndesis-prometheus Hostname URL to open the Prometheus dashboard in a new browser tab or window.

Procedure

1. Download the latest Fuse Online release to the current local directory by invoking the following command:

   $ wget https://github.com/syndesisio/fuse-online-install/archive/1.5.tar.gz

2. Uncompress the downloaded file.

3. Change to the directory that contains the extracted archive. For example:

   $ cd fuse-online-install-1.5

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

   $ oc login -u developer

5. Invoke the following command, which returns the name of the current project, to ensure that the current project is the project where Fuse Online is installed:

   $ oc project

   If you need to switch to the project where Fuse Online is installed then invoke the following command with the name of the OpenShift project that contains Fuse Online:

   $ oc project project-name

6. To check which version you are about to upgrade to, run the update script with the --version option, as follows:

   $ bash update_ocp.sh --version

7. Invoke the update script as follows:

   $ bash update_ocp.sh

   To learn more about the script, invoke $ bash update_ocp.sh --help.

   During and after an infrastructure upgrade, existing integrations continue to run with the older versions of Fuse Online libraries and dependencies.

8. Upgrade Fuse Online integrations that are running as follows:

   1. In Fuse Online, select the integration that you want to upgrade.
   2. Select Edit.
   3. Select Publish to republish the integration.

   Republishing the integration forces a rebuild that uses the latest Fuse Online dependencies.