From the menu bar, select File > > > New > > Other > > JBoss Fuse > > Fuse Integration Project > and click Next to open the New Fuse Integration Project wizard:

Click Next to open the Select a Target Runtime page:

Accept No Runtime selected for Target Runtime, and 2.18.1.redhat-000015 for Camel Version.

	Note
	You will add the runtime later in the tutorial To Publish a Fuse Project to JBoss Fuse.

Click Next to open the Advanced Project Setup page:

Click Finish.

Fuse Tooling starts downloading from the Maven repository all of the files it needs to build the project, and then adds the new project to Project Explorer.

If you are not in the Fuse Integration perspective, the tooling asks whether you want to switch to it now:

Click Yes to open the new CBRroute project in the Fuse Integration perspective:

The new CBRroute project contains everything needed to create and run routes. As shown in Figure 1, “Generated project files”, the files generated for CBRroute include:

Drag a File component ( ) from the Palette's Components drawer to the canvas, and drop it in the Route_route1 container node.

The File component changes to a From _from1 node inside the Route_route1 container node.

On the canvas, select the From _from1 node.

The Properties view, located below the canvas, displays the node’s property fields for editing.

In the Properties view, click the Advanced tab:

You need to create a folder for the project’s source data and enter that folder’s name in the Directory Name field.

In the Directory Name field, enter src/data:

The path src/data is relative to the project’s directory.

On the Consumer tab, enable the Noop option by clicking its check box.

The Noop option prevents the message#.xml files being deleted from the src/data folder, and it enables idempotency to ensure that each message#.xml file is consumed only once.

Select the Details tab to open the file node’s Details page.

The tooling automatically populates the Uri field with the Directory Name and Noop properties you configured on the Advanced tab. It also populates the Id field with an autogenerated ID (_from1):

Drag another File component from the Palette's Components drawer and drop it in the Route_route1 container node.

The File component changes to a To _to1 node inside the Route_route1 container node.

On the canvas, select the To _to1 node.

The Properties view, located below the canvas, displays the node’s property fields for editing.

On the Details tab, enter file:target/messages/others in the Uri field, and _Others in the Id field:

	Note
	The tooling will create the target/messages/others folder at runtime.

In the Route_route1 container, select the From _from1 node and drag it’s connector arrow ( ) over the To_Others node, then release it:

	Note
	The two file nodes are connected and aligned on the canvas according to the route editor’s layout direction preference setting. The choices are Right and Down (default).

	Note
	If you do not connect the nodes before you close the project, the tooling automatically connects them when you reopen it.

Click the Source tab at bottom, left of the canvas to display the XML for the route. The camelContext element will look like Example 1, “XML for CBRroute”:

<?xml version="1.0" encoding="UTF-8"?>

<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
    https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
    http://camel.apache.org/schema/blueprint
    http://camel.apache.org/schema/blueprint/camel-blueprint.xsd">

    <camelContext id="_context1" xmlns="http://camel.apache.org/schema/blueprint">
        <route id="_route1">
            <from id="_from1" uri="file:src/data?noop=true"/>
            <to id="_Others" uri="file:target/messages/others"/>
        </route>
    </camelContext>
</blueprint>

Click New > > > Fuse Message > to open the New File wizard:

Click Finish to open the test message, message1.xml in the Design tab:

Click the Source tab at the bottom of the canvas:

In the Source tab, enter this text:

<?xml version="1.0" encoding="UTF-8"?>

<order>
  <customer>
    <name>Brooklyn Zoo</name>
    <city>Brooklyn</city>
    <country>USA</country>
  </customer>
  <orderline>
    <animal>wombat</animal>
    <quantity>15</quantity>
    <maxAllowed>25</maxAllowed>
  </orderline>
</order>

	Note
	You can safely ignore the on the last line of the newly created message1.xml file, which advises you that there are no grammar constraints (DTD or XML Schema) referenced by the document.

If you haven’t already done so, download the prefabricated test message files (see Using the Fuse Tooling Resource Files for instructions). Copy message2.xml through message6.xml into the newly created CBRroute/src/data folder. You will use all six test messages in the remaining Fuse Tooling tutorials.

Table 1, “Preconstructed test messages” shows the contents of each remaining prefabricated message file.