From the menu bar, select menu: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.

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 2.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:

In the Route_route1 container, select the From _from1 node and drag it’s connector arrow ( ) over the To_Others node, then release 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 2.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 menu: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>

If you haven’t already done so, download the prefabricated test message files (see Chapter 1, 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 2.1, “Preconstructed test messages” shows the contents of each remaining prefabricated message file.

In Project Explorer, select CBRroute/Camel Contexts/src/main/resources/OSGi-INF/blueprint/blueprint.xml :

Right-click it to open the context menu, then select menu:Run As[ > > Local Camel Context (without tests) > ].

The Console panel opens to display log messages that reflect the progress of the project’s execution. At the beginning, Maven downloads the resources necessary to update the local Maven repository, which may take a few minutes.

Messages similar to the following at the end of the output indicate that the route executed successfully:

...
[Blueprint Extender: 3] BlueprintCamelContext INFO  Route: _route1 started and consuming from:Endpoint[file://src/data?noop=true]
[Blueprint Extender: 3] BlueprintCamelContext INFO  Total 1 routes, of which 1 are started.
[Blueprint Extender: 1] BlueprintCamelContext INFO  Apache Camel 2.18.0.redhat-000015 (CamelContext: ...) started in 0.163 seconds
[Blueprint Extender: 3] BlueprintCamelContext INFO  Apache Camel 2.18.0.redhat-000015 (CamelContext: ...) started in 0.918 seconds

In Project Explorer, locate the folder target/messages/ and expand it:

Double-click message1.xml to open it in the route editor’s Design tab, then select the Source tab at the bottom, left of the canvas to see the XML code.

Its contents should match that shown in Example 3.1, “Contents of message1.xml”.

<?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>

In the Palette, open the Routing drawer and drag a Choice ( ) pattern to the canvas and drop it in the Route_route1 container.

The Route_route1 container expands to accommodate the Choice_choice1 node.

In the Route_route1 container, select the From_from1 node and drag its connector arrow over the Choice_choice1 node, then release it:

In the Properties view, _choice1 appears in the Id field:

Leave the Id field as is.

From the Routing drawer, drag a When ( ) pattern to the canvas and drop it on the Choice_choice1 node:

The Choice_choice1 container expands to accommodate the When_when1 node. The decorating the When_when1 node indicates that one or more required property values must be set.

On the canvas, select the When_when1 node, to open its properties in the Properties view:

Click the button in the Language field to open the list of available languages, and select xpath:

In the Expression field, enter /order/orderline/quantity/text() > /order/orderline/maxAllowed/text().

This expression determines which messages will transit this path in the route.

Leave each of the remaining properties as is.

Enabling Trim removes any leading or trailing white spaces and line breaks from the message.

Click the Source tab to view the XML for the route:

Drag the Log component to the canvas and drop it on the When_when1 node:

The When_when1 container expands to accommodate the Log_log1 node.

In the Message field, enter quantity requested exceeds the maximum allowed - contact customer:

Leave each of the remaining properties as is.

Drag the Set Header pattern to the canvas and drop it in the When_when1 container.

The When_when1 container expands to accommodate the SetHeader_setHeader1 node.

On the canvas, select the Log_log1 node and drag its connector arrow over the SetHeader_setHeader1 node, and then release it:

On the canvas, select the SetHeader_setHeader1 node to open its properties in the Properties view:

Click the button in the Language field to open the list of available languages, and select constant:

Drag the File component to the canvas and drop it in the When_when1 container.

The When_when1 container expands to accommodate the To_to1 node.

On the canvas, select the SetHeader_setHeader1 node and drag its connector arrow over the To_to1 node, and then release it:

On the canvas, select the To_to1 node to open its properties in the Properties view:

On the Details tab, replace directoryName with target/messages/invalidOrders in the Uri field, and enter _Invalid in the Id field:

Click the Source tab to view the XML for the route:

Drag the Otherwise pattern to the canvas and drop it into the Choice_choice1 container:

The Choice_choice1 container expands to accommodate the Otherwise_otherwise1 node.

In the Id field, enter _else2:

Drag the Log component to the canvas and drop it on the Otherwise_else2 node:

The Otherwise-else2 container expands to accommodate the Log_log2 node.

In the Message field, enter valid order - process:

Leave each of the remaining properties as is.

Drag the Set Header pattern to the canvas and drop it into the Otherwise_else2 container.

The Otherwise_else2 container expands to accommodate the SetHeader_setHeader2 node.

On the canvas, select the Log_log2 node and drag its connector arrow over the SetHeader_setHeader2 node, and then release it:

Note

You can collapse containers to free up space when the diagram becomes congested. To do so, select the container you want to collapse, and then click its button:

To reopen the container, select it and then click its button:

Collapsing and expanding containers in the Design tab does not affect the routing context file. It remains unchanged.

Click the button in the Language field to open the list of available languages, and select constant:

Drag the File component to the canvas and drop it into the Otherwise_else2 container.

The Otherwise_else2 container expands to accommodate the To_to1 node.

On the canvas, select the SetHeader_setHeader2 node, and drag its connector arrow over the To_to1 node and then release it:

In the URI field, replace directoryName with target/messages/validOrders, and in the Id field, enter _Valid:

On the menu bar, click File → Save to save the routing context file.

This is the completed content-based router with logs and message headers:

Click the Source tab at the bottom, left of the canvas to display the XML for the route.

The camelContext element will look like that shown in Example 4.1, “XML for content-based router”.

<?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"/>
        <choice id="_choice1">
           <when id="_when1">
              <xpath>order/orderline/quantity/text() > /order/orderline/maxAllowed/text()</xpath>
              <log id="_log1" message="quantity requested exceeds the maximum allowed - contact customer"/>
              <setHeader headerName="Destination" id="_setHeader1">
                  <constant>InvalidOrders</constant>
              </setHeader>
              <to id="_Invalid" uri="file:target/messages/invalidOrders"/>
           </when>
           <otherwise id="_else2">
              <log id="_log2" message="valid order - process"/>
              <setHeader headerName="Destination" id="_setHeader2">
                  <constant>Dispatcher</constant>
              </setHeader>
              <to id="_Valid" uri="file:target/messages/validOrders"/>
           </otherwise>
        </choice>
    </route>
  </camelContext>
</blueprint>

Under the project root node (CBRroute), locate the folder target/messages/ and expand it.

Check that the target/messages/invalidOrders folder contains message2.xml and message4.xml.

In these messages, the value of the quantity element should exceed the value of the maxAllowed element.

Check that the target/messages/validOrders folder contains the four message files that contain valid orders: message1.xml, message3.xml , message5.xml and message6.xml.

In these messages, the value of the quantity element should be less than or equal to the value of the maxAllowed element.

Drag the Route pattern to the canvas and drop it next to the Route_route1 container:

The Route pattern becomes the Route_route2 container node on the canvas.

In the Palette, open the Components drawer and drag a Direct component ( ) to the canvas and drop it in the Route_route2 container:

The Route_route2 container expands to accommodate the From_from2 node.

On the canvas, select the From_from2 node to open its properties in the Properties view:

In the Palette, open the Routing drawer and drag a Choice ( ) pattern to the canvas and drop it in the Route_route2 container.

The Route_route2 container expands to accommodate the Choice_choice2 node.

In the Route_route2 container, select the direct:OrderFulfillment node and drag its connector arrow over the Choice_choice2 node, then release it:

In the Palette, open the Routing drawer and drag a When ( ) pattern to the canvas and drop it in the Choice_choice2 container:

The Choice_choice2 container expands to accommodate the When_when2 node.

On the canvas, select the When_when2 node to open its properties in the Properties view:

Set the node’s properties this way:

In the Palette, open the Transformation drawer and drag the Set Header pattern to the canvas and drop on the When_when/usa node:

The When_when/usa container expands to accommodate the SetHeader_setHeader3 node.

On the canvas, select the SetHeader_setHeader3 node to open its properties in the Properties view:

Set the node’s properties this way:

In the Palette, open the Components drawer and drag a Log component ( ) to the canvas and drop it in the When_when/usa container.

The When_when/usa container expands to accommodate the Log_log3 node.

On the canvas, select the SetHeader_setHead_usa node and drag its connector arrow over the Log_log3 node, then release it:

On the canvas, select the Log_log3 node to open its properties in the Properties view:

In the Properties view:

In the Palette, open the Components drawer and drag a File component ( ) to the canvas and drop it in the When_when/usa container.

The When_when/usa container expands to accommodate the To_to1 node.

On the canvas, select the Log_usa node and drag its connector arrow over the To_to1 node, then release it:

In the Properties view:

On the menu bar, click File → Save to save the routing context file.

The USA branch of Route_route2 should look like this:

In the Palette, open the Routing drawer and drag a When pattern ( ) to the canvas and drop it in the Choice_choice2 container:

The Choice_choice2 container expands to accommodate the When_when2 node.

In the Properties view:

In the Palette, open the Transformation drawer and drag a Set Header pattern ( ) to the canvas and drop it on the When_when/gb node:

The When_when/gb container expands to accommodate the SetHeader_setHeader3 node.

In the Properties view:

In the Palette, open the Components drawer and drag a Log pattern ( ) to the canvas and drop it in the When_when/gb container.

The When_when/gb container expands to accommodate the Log_log3 node.

On the canvas, select the SetHeader_setHead_uk node and drag its connector arrow over the Log_log3 node, and then release it:

In the Properties view:

From the Components drawer, drag a File pattern ( ) to the canvas and drop it in the When_when/gb container.

The When_when/gb container expands to accommodate the To_to1 node.

On the canvas, select the Log_uk node and drag its connector arrow over the To_to1 node, and then release it:

In the Properties view:

On the menu bar, click File → Save to save the routing context file.

The Great Britain branch of Route_route2 should look like this:

In the Palette, open the Routing drawer and drag a When pattern ( ) to the canvas and drop it in the Choice_choice2 container:

The Choice_choice2 container expands to accommodate the When_when2 node.

In the Properties view:

In the Palette, open the Transformation drawer and drag a Set Header pattern ( ) to the canvas and drop it on the When_when/ger node:

The When_when/ger container expands to accommodate the SetHeader_setHeader3 node.

In the Properties view:

In the Palette, open the Components drawer and drag a Log pattern ( ) to the canvas and drop it in the When_when/ger container.

The When_when/ger container expands to accommodate the Log_log3 node.

On the canvas, select the SetHeader_setHead_ger node and drag its connector arrow over the Log_log3 node, and then release it:

In the Properties view:

From the Components drawer, drag a File pattern ( ) to the canvas and drop it in the When_when/ger container.

The When_when/ger container expands to accommodate the To_to1 node.

On the canvas, select the Log_ger node and drag its connector arrow over the To_to1 node, and then release it:

In the Properties view:

On the menu bar, click File → Save to save the routing context file.

The Germany branch of Route_route2 should look like this:

In the Palette, open the *Routing drawer and drag an Otherwise pattern ( ) to the canvas and drop it in the Choice_choice2 container:

The Choice_choice2 container expands to accommodate the Otherwise_otherwise1 node.

In the Palette, open the Transformation drawer and drag a Set Header pattern ( ) to the canvas and drop it on the Otherwise_else/fr node:

The Otherwise_else/fr container expands to accommodate the SetHeader_setHeader3 node.

In the Properties view:

In the Palette, open the Components drawer and drag a Log pattern ( ) to the canvas and drop it in the Otherwise_else/fr container.

The Otherwise_else/fr container expands to accommodate the Log_log3 node.

On the canvas, select the SetHeader_setHead_fr node and drag its connector arrow over the Log_log3 node, and then release it:

In the Properties view:

From the Components drawer, drag a File pattern ( ) to the canvas and drop it in the Otherwise_else/fr container.

The Otherwise_else/fr container expands to accommodate the To_to1 node.

On the canvas, select the Log_fr node and drag its connector arrow over the To_to1 node, and then release it:

In the Properties view:

On the menu bar, click File → Save to save the routing context file.

The France branch of Route_route2 should look like this:

If needed, on the menu bar, select File → Save to save the routing context.

The routes on the canvas should look like this:

image::./images/tutCBRRte1Completed.png[Completed first route in the CBRroute routing context]

image::./images/tutCBRRte2Completed.png[Completed second route in the CBRroute routing context]

Click the Source tab at the bottom, left of the canvas to display the XML for the route.

The camelContext element should look like that shown in Example 5.1, “XML for dual-route content-based router”:

<?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" shutdownRoute="Default">
          <from id="_from1" uri="file:src/data?noop=true"/>
          <choice id="_choice1">
              <when id="_when1">
                  <xpath>/order/orderline/quantity/text() > /order/orderline/maxAllowed/text()</xpath>
                  <log id="_log1" message="quantity exceeds the maximum allowed - contact customer"/>
                  <setHeader headerName="Destination" id="_setHeader1">
                      <constant>InvalidOrders</constant>
                  </setHeader>
                  <to id="_Invalid" uri="file:target/messages/invalidOrders"/>
              </when>
              <otherwise id="_else2">
                  <log id="_log2" message="valid order - process"/>
                  <setHeader headerName="Destination" id="_setHeader2">
                      <constant>Dispatcher</constant>
                  </setHeader>
                  <to id="_Fulfill" uri="direct:OrderFulfillment"/>
              </otherwise>
          </choice>
      </route>
      <route id="_route2">
          <from id="_direct:OrderFulfillment" uri="direct:OrderFulfillment"/>
          <choice id="_choice2">
              <when id="_when/usa">
                  <xpath>/order/customer/country = 'USA'</xpath>
                  <setHeader headerName="Destination" id="_setHead_usa">
                      <constant>USA</constant>
                  </setHeader>
                  <log id="_usa" message="Valid order - ship to USA customer"/>
                  <to id="_US" uri="file:target/messages/USA"/>
              </when>
              <when id="_when/gb">
                  <xpath>/order/customer/country = 'Great Britain'</xpath>
                  <setHeader headerName="Destination" id="_setHead_uk">
                      <constant>UK</constant>
                  </setHeader>
                  <log id="_uk" message="Valid order - ship animals to UK customer"/>
                  <to id="_UK" uri="file:target/messages/GreatBritain"/>
              </when>
              <when id="_when/ger">
                  <xpath>/order/customer/country = 'Germany'</xpath>
                  <setHeader headerName="Destination" id="_setHead_ger">
                      <constant>Germany</constant>
                  </setHeader>
                  <log id="_ger" message="Valid order - ship to Germany customer"/>
                  <to id="_GER" uri="file:target/messages/Germany"/>
              </when>
              <otherwise id="_else/fr">
                  <setHeader headerName="Destination" id="_setHead_fr">
                      <constant>France</constant>
                  </setHeader>
                  <log id="_fr" message="Valid order - ship animals to France customer"/>
                  <to id="_FR" uri="file:target/messages/France"/>
              </otherwise>
          </choice>
      </route>
  </camelContext>
</blueprint>

Expand the folder target/messages/ as shown in Figure 5.1, “Target message destinations in Project Explorer”. The message*.xml files should be dispersed in your target destinations like this:

Figure 5.1. Target message destinations in Project Explorer

On the canvas, select the Choice_choice1 node, and then click its icon to set an unconditional breakpoint:

Repeat [setBPstep] to set an unconditional breakpoint on the following Route_Route1 nodes:

Repeat [setBPstep] to set an unconditional breakpoint on the following Route_Route2 nodes:

Right-click the blueprint.xml file to open its context menu, and then click menu:Debug As…​[ > > Local Camel Context > ].

The Camel debugger suspends execution at the first breakpoint it encounters and asks whether you want to open Debug perspective now:

Click Yes.

Debug perspective opens with the routing context suspended at _choice1 in Route1 [blueprint.xml] as shown in the Debug view:

In the Variables view, expand the nodes to expose the variables and values available for each node.

As you step through the routing context, the variables whose values have changed since the last breakpoint are highlighted in yellow. You may need to expand the nodes at each breakpoint to reveal variables that have changed.

Click to step to the next breakpoint, _log2 in Route1 [blueprint.xml]:

Click to step to the next breakpoint, _setHeader2 in Route1 [blueprint.xml].

Examine the variables that changed since the breakpoint at _log2 in Route1 [blueprint.xml].

In the Debug view, click _log2 in Route1 [blueprint.xml] to populate the Variables view with the variable values from the breakpoint _log2 in Route1 [blueprint.xml] for a quick comparison.

In the Debug view, you can switch between breakpoints within the same message flow to quickly compare and monitor changing variable values in the Variables view.

Continue stepping through the routing context. When one message completes the routing context and the next message enters it, the new message flow appears in the Debug view, tagged with a new breadcrumb ID:

In this case, ID-janemurpheysmbp-home-55846-1471374645179-0-3 identifies the second message flow, corresponding to message2.xml having entered the routing context. Breadcrumb IDs are incremented by 2.

When message3.xml enters the breakpoint _choice1 in Route_route1 [blueprint.xml], examine the Processor variables. The values displayed are the metrics accumulated for message1.xml and message2.xml, which previously transited the routing context:

Timing metrics are in milliseconds.

In the Menu bar, click to terminate the Camel debugger. This will cause the Console to terminate, but you will have to manually clear the output.

In the Menu bar, right-click to open the context menu, and then select Close to close Debug perspective.

Doing so automatically returns you to perspective from which you launched the Camel debugger.

In Project Explorer, open the project’s context menu, and select Refresh to refresh the display.

Expand the CBRroute/target/messages/* directories to check that the messages were delivered to their expected destinations:

With message1 stopped at the first breakpoint, _choice1 in Route1 [blueprint.xml], add the variables NodeId and RouteId (in the Exchange category) and MessageBody and CamelFileName (in the Message category) to the watch list.

For each of the four variables:

Repeat [selectVariable] to add the variable Destination to the watch list.

The Expressions view should now contain these variables:

Right-click MessageBody to open its context menu, and select Change Value…​:

Change the value of quantity from 3 to 2:

This changes the in-memory value only.

Switch to the Expressions view, and select the MessageBody variable.

The pane below the list of variables displays the entire body of message2, making it easy to check the current value of order items:

Click to step to the next breakpoint.

Instead of following the branch leading to To_Invalid, message2 now follows the branch leading toTo_Fulfill and Route_route2:

Switch to the Breakpoints view, and disable all breakpoints (13) listed below _choice1:

Click to step to the next breakpoint:

The debugger jumps to _FulFill in Route1 [blueprint.xml].

Click again to step to the next breakpoint:

The debugger jumps to _UK in Route2 [blueprint.xml].

Change the value of quantity from 5 to 4:

In the tool bar, click to terminate the Camel debugger:

This will also cause the Console to terminate, but you will have to click its button to clear the output.

In the Menu bar, right-click to open the context menu, and then select Close to close Debug perspective.

Doing so automatically returns you to the perspective from which you launched the Camel debugger.

Expand the CBRroute/target/messages/* directories to check whether the messages were delivered as expected:

You should see that no messages were sent to the invalidOrders. Instead, message2.xml should appear in the USA folder, and message4.xml should appear the GreatBritain folder.

Click the button on the right side of the tool bar, and then select Fuse Integration from the list:

Fuse Integration perspective opens in the default layout:

Drag the JMX Navigator tab to the far right of the Terminal tab and drop it there:

This arrangement provides more space for Diagram View to display the routing context’s nodes graphically, which makes it easier for you to visually trace the path that messages take in traversing the routing context.

Note

To make it easy to access a routing context .xml file, especially when a project consists of multiple contexts, the tooling lists them under the Camel Contexts folder in Project Explorer.

Additionally, all routes in a routing context are displayed as icons directly under their context file entry. To display a single route in the routing context on the canvas, double-click its icon in Project Explorer. To display all routes in the routing context, double-click the context file entry.

Select menu:Run As[ > > Local Camel Context (without tests) > ].

In JMX Navigator, expand Local Processes.

When you first expand Local Processes, you see the node maven[Id][Disconnected]:

When you click this node, it changes to Local Camel Context[Id][Disconnected] (retaining the same Id as its predecessor):

Double click Local Camel Context[Id][Disconnected] to connect to it, and then expand the elements of your route:

Right-click the _context1 node to open the context menu, and select Start Tracing:

The tooling displays a graphical representation of your routing context in Diagram View:

In Project Explorer, expand CBRroute/src/data, so you can access the message files (message1.xml through message6.xml):

Drag message1.xml and drop it on the _context1>Endpoints>file>src/data?noop=true node in JMX Navigator:

As the message traverses the route, the tooling traces and records its passage at each step. To update Diagram View with the new message count, you need to click the _context1 node in JMX Navigator.

Click the _context1 node in JMX Navigator to initialize Messages View with message1.xml's details.

In Messages View, click the icon on the panel’s menu bar, and select Configure Columns…​ to open the Configure Columns wizard:

You can include or exclude items from Messages View by selecting or deselecting them. You can rearrange the columnar order in which items appear in Messages View by highlighting individual, selected items and moving them up or down in the list.

In the Configure Columns wizard, select and order the columns this way:

These columns and their order will persist in Messages View until you change them again.

In Messages View, click the (Refresh button) on top, right of the panel’s menu bar to populate the view with message1.xml's message traces.

Each time you drop a message on the input src node in JMX Navigator, you need to refresh Messages View to populate it with the message traces.

Click one of the message traces to see more details about it in Properties view:

The tooling displays the details about a message trace (including message headers when they are set) in the top half of the Properties view and the contents of the message instance in the bottom half of the Properties view. So, if your application sets headers at any step within a route, you can check the Message Details to see whether they were set as expected.

You can step through the message instances by highlighting each one to see how a particular message traversed the route and whether it was processed as expected at each step in the route.

In Diagram View, the associated step in the route is highlighted:

Drag message2.xml and drop it on the_context1>Endpoints>file>src/data?noop=true node in JMX Navigator.

Hover over each node in the tree until you expose the src/data?noop=true node, then drop message2.xml on it.

In Messages View, click the (Refresh button) on top, right of the panel’s menu bar to populate the view with message2.xml's message traces.

The tooling draws the route in Diagram View, tagging paths exiting a processing step with timing and performance metrics (in milliseconds). Only the metric Total exchanges is displayed in the diagram:

Hovering over the displayed metrics reveals additional metrics about message flow:

When done:

In the New Folder dialog, in the project tree pane, expand the CBRroute node and select the src folder.

Make sure CBRroute/src appears in the Enter or select the parent folder field.

In Folder name, enter /test/java:

Click Finish.

In Project Explorer, the new src/test/java folder appears under the src/main/resources folder:

Verify that the new /src/test/java folder is included in the build path.

Right-click it to open the context menu, and then select menu:New[ > > Camel Test Case > ]:

Next to the Camel XML file under test field, click Browse to open a file explorer configured to screen for XML files, and then select the CBRroute project’s blueprint.xml file:

Click OK.

By default, all endpoints are selected and will be included in the test case. Click Finish.

Add these lines to the end of the <dependencies> section:

<dependency>
       <groupId>commons-io</groupId>
       <artifactId>commons-io</artifactId>
       <version>2.5</version>
       <scope>test</scope>
</dependency>

Save the file.

The contents of the entire pom.xml file should look like this:

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

<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
  http://maven.apache.org/xsd/maven-4.0.0.xsd"
  xmlns="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <modelVersion>4.0.0</modelVersion>
  <groupId>co</groupId>
  <artifactId>camel-blueprint</artifactId>
  <version>1.0.0-SNAPSHOT</version>
  <packaging>bundle</packaging>
  <name>Camel Blueprint Quickstart</name>
  <description>Empty Camel Blueprint Example</description>

  <licenses>
    <license>
      <name>Apache License, Version 2.0</name>
      <url>http://www.apache.org/licenses/LICENSE-2.0.html</url>
      <distribution>repo</distribution>
    </license>
  </licenses>

  <properties>
    <camel.version>2.18.1.redhat-000015</camel.version>
    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
    <version.maven-bundle-plugin>2.3.7<</version.maven-bundle-plugin>
    <jboss.fuse.bom.version>6.3.0.redhat-187</jboss.fuse.bom.version>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.jboss.fuse.bom</groupId>
        <artifactId>jboss-fuse-parent</artifactId>
        <version>${jboss.fuse.bom.version}</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>

  <dependencies>
    <dependency>
      <groupId>org.apache.camel</groupId>
      <artifactId>camel-core</artifactId>
      <version>${camel.version}</version>
    </dependency>
    <dependency>
      <groupId>org.apache.camel</groupId>
      <artifactId>camel-blueprint</artifactId>
      <version>${camel.version}</version>
    </dependency>
    <dependency>
      <groupId>org.slf4j</groupId>
      <artifactId>slf4j-api</artifactId>
    </dependency>
    <dependency>
      <groupId>org.slf4j</groupId>
      <artifactId>slf4j-log4j12</artifactId>
    </dependency>
    <dependency>
      <groupId>log4j</groupId>
      <artifactId>log4j</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.camel</groupId>
      <artifactId>camel-test-blueprint</artifactId>
      <version>${camel.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>commons-io</groupId>
      <artifactId>commons-io</artifactId>
      <version>2.5</version>
      <scope>test</scope>
    </dependency>
  </dependencies>

  <repositories>
    <repository>
      <releases>
        <enabled>true</enabled>
        <updatePolicy>never</updatePolicy>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
      <id>fuse-public-repository</id>
      <name>FuseSource Community Release Repository</name>
      <url>https://repo.fusesource.com/nexus/content/groups/public</url>
    </repository>
    <repository>
      <releases>
        <enabled>true</enabled>
        <updatePolicy>never</updatePolicy>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
      <id>red-hat-ga-repository</id>
      <name>Red Hat GA Repository</name>
      <url>https://maven.repository.redhat.com/ga</url>
    </repository>
    <repository>
      <id>fuse-ea</id>
      <url>http://download.eng.brq.redhat.com/brewroot/repos/jb-fuse-6.2-build/latest/maven</url>
    </repository>
    <repository>
      <id>redhat-ea-repository</id>
      <url>https://maven.repository.redhat.com/earlyaccess/all</url>
    </repository>
  </repositories>

  <pluginRepositories>
    <pluginRepository>
      <releases>
        <enabled>true</enabled>
        <updatePolicy>never</updatePolicy>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
      <id>fuse-public-repository</id>
      <name>FuseSource Community Release Repository</name>
      <url>https://repo.fusesource.com/nexus/content/groups/public</url>
    </pluginRepository>
    <pluginRepository>
      <releases>
        <enabled>true</enabled>
        <updatePolicy>never</updatePolicy>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
      <id>red-hat-ga-repository</id>
      <name>Red Hat GA Repository</name>
      <url>https://maven.repository.redhat.com/ga<url>
    </pluginRepository>
    <pluginRepository>
      <id>fuse-ea</id>
      <url>http://download.eng.brq.redhat.com/brewroot/repos/jb-fuse-6.2-build/latest/maven</url>
    </pluginRepository>
    <pluginRepository>
      <id>redhat-ea-repository</id>
      <url>https://maven.repository.redhat.com/earlyaccess/all</url>
    </pluginRepository>
    <pluginRepository>
      <id>camelStaging</id>
      <url>https://repository.jboss.org/nexus/content/repositories/fusesource_releases_external-2384</url>
    </pluginRepository>
  </pluginRepositories>

  <build>
    <defaultGoal>install</defaultGoal>
    <plugins>
      <plugin>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <version>${version.maven-bundle-plugin}</version>
        <extensions>true</extensions>
        <configuration>
          <instructions>
            <Bundle-SymbolicName>CBRroute</Bundle-SymbolicName>
            <Bundle-Name>Empty Camel Blueprint Example [CBRroute]</Bundle-Name>
          </instructions>
        </configuration>
      </plugin>
      <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>3.5.1</version>
        <configuration>
          <source>1.8</source>
          <target>1.8</target>
        </configuration>
      </plugin>
      <plugin>
        <artifactId>maven-resources-plugin</artifactId>
        <version>3.0.1</version>
        <configuration>
          <encoding>UTF-8</encoding>
        </configuration>
      </plugin>
      <plugin>
        <groupId>org.apache.camel</groupId>
        <artifactId>camel-maven-plugin</artifactId>
        <version>${camel.version}</version>
        <configuration>
          <useBlueprint>true</useBlueprint>
        </configuration>
      </plugin>
    </plugins>
  </build>

</project>

Select menu:Run As[ > JUnit Test].

If the test runs successfully, you’ll see something like this:

When the test does fail, you’ll see something like this:

Examine the output and take action to resolve any test failures.

To see more of the errors displayed in the JUnit panel, click on the panel’s menu bar to maximize the view.

Before you run the JUnit test case again, delete any JUnit-generated test messages from the CBRroute project’s /src/data folder in Project Explorer (see Figure 8.1, “Trace-generated messages”).

Click the link No servers are available. Click this link to create a new server…​ to open the Define a New Server page.

Expand the JBoss Fuse node to expose the available server options:

Accept the defaults for Server’s host name (localhost) and Server name (JBoss Fuse 6.3 Runtime Server), and then click Next to open the JBoss Fuse Runtime page:

Select the runtime JRE from the drop-down menu next to Execution Environment.

Select either JavaSE-1.8 (recommended) or JavaSE-1.7. If neither appears as an option, click the Environments…​ button and select either version from the list.

Leave the Alternate JRE option as is.

Click Next to save the runtime definition for JBoss Fuse 6.3 Server and open the JBoss Fuse server configuration details page:

Accept the default for SSH Port (8101).

The runtime uses the SSH port to connect to the server’s Karaf shell. If this default is incorrect, you can discover the correct port number by looking in the Red Hat JBoss Fuse installDir/etc/org.apache.karaf.shell.cfg file.

In User Name, enter the name used to log into the server.

This is a user name stored in the Red Hat JBoss Fuse installDir/etc/users.properties file.

If one has not been set, you can either add one to that file using the format user=password,role (for example, joe=secret,Administrator), or you can set one using the karaf jaas command set:

In Password:, enter the password required for User name to log into the server.

This is the password set either in Red Hat JBoss Fuse’s installDir/etc/users.properties file or by the karaf jaas commands.

Click Finish.

JBoss Fuse 6.3 Runtime Server [stopped, Synchronized] appears in the Servers view.

In the Servers view, expand JBoss Fuse 6.3 Runtime Server [stopped, Synchronized]:

JMX[Disconnected] appears as a node under JBoss Fuse 6.3 Runtime Server [stopped, Synchronized] entry.

In the Servers view, double-click the JBoss Fuse 6.3 Runtime Server [stopped, Synchronized] entry to display its overview:

On the server’s Overview page, expand the Publishing section to expose the options.

Make sure the option Automatically publish when resources change is enabled.

Change the value of Publishing interval to speed up or delay publishing the project when changes have been made.

In the Servers view, select JBoss Fuse 6.3 Runtime Server and click to start it.

Wait a few seconds for JBoss Fuse 6.3 Server to start up. When it does:

Select Add and Remove to open the Add and Remove page:

Make sure the option If server is started, publish changes immediately is checked.

Select CBRroute and click Add to assign it to the JBoss Fuse server;

Click Finish.

Expand the Camel folder in the Servers view or JMX Navigator to expose the elements of the CBRroute.

You can interact with the CBRroute routing context using either the Servers view or JMX Navigator, but JMX Navigator provides more room to expand the routing context’s nodes, making it easier for you to access them.

Click the Bundles node to populate the Properties view with the list of bundles installed on the JBoss Fuse 6.3 Runtime Server:

Start typing CBRroute in the Properties view’s Search field to quickly determine whether your project’s CBRroute bundle is included in the list. Note that it is the last bundle in the list, identified by its Symbolic Name, CBRroute, which is the name you gave your project when you created it.

Note

Alternatively, you can issue the osgi:list command in the Terminal view to see a generated list of bundles installed on the JBoss Fuse server runtime. The tooling uses a different naming scheme for OSGi bundles displayed by the osgi:list command. In this case, the command returns Empty Camel Blueprint Project [CBRroute], which appears at the end of the list of installed bundles.

In the <build> section of project’s pom.xml file, you can find the bundle’s symbolic name and its bundle name (OSGi) listed in the maven-bundle-plugin entry:

Select Add and Remove:

In the Servers view, right-click JMX[Connected] to open the context menu, and then click Refresh.

The Camel tree under JMX[Connected] disappears.