Tooling Tutorials

Open Red Hat CodeReady Studio.

When you start CodeReady Studio for the first time, it opens in the JBoss perspective:

Otherwise, it opens in the perspective that you were using in your previous CodeReady Studio session.

From the menu , select File → New → Fuse Integration Project to open the New Fuse Integration Project wizard:

In the Project Name field, enter ZooOrderApp.

Leave the Use default workspace location option checked.

Click Next to open the Select a Target Runtime page:

Choose Karaf/Fuse on Karaf and accept None selected for the runtime.

Accept the default Apache Camel version.

Click Next to open the Advanced Project Setup page, and then select the Empty - Blueprint DSL template:

Click Finish.

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

If CodeReady Studio is not already showing the Fuse Integration perspective, it asks whether you want to switch to it now:

Click Yes.

The new ZooOrderApp project opens in the Fuse Integration perspective:

The ZooOrderApp project contains all of the files that you need to create and run routes, including:

To view the preliminary routing context, open the blueprint.xml file in the Editor view, and then click the Source tab.

Open the Editor preferences page:

Check the Use ID values for all component labels option.

In the CodeReady Studio Project Explorer view, create a folder to contain the test messages:

Click here to open a web browser to the location of the provided Tooling Tutorial resource Fuse-tooling-tutorials-jbds-10.3.zip file.

Download the Fuse-tooling-tutorials-jbds-10.3.zip file to a convenient location that is external to the ZooOrderApp project’s workspace, and then unzip it. It contains two folders as described in Chapter 1, About the Fuse Tooling Tutorials.

From the messages folder, copy the six XML files to your ZooOrderApp project’s src/data folder.

Click the Source tab.

The XML file opens in the Editor view.

For example, the contents of the message1.xml file shows an order from the Bronx Zoo for 12 wombats:

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

<order>
  <customer>
    <name>Bronx Zoo</name>
    <city>Bronx NY</city>
    <country>USA</country>
  </customer>
  <orderline>
    <animal>wombat</animal>
    <quantity>12</quantity>
  </orderline>
</order>

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.

To specify the source directory for the message files, in the Properties view, click the Advanced tab:

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 from 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.

Notice that 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):

Leave the autogenerated Id as is.

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:

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

Click the Source tab at the bottom of the canvas to display the XML for the route:

<?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="_Received" uri="file:target/messages/received"/>
        </route>
    </camelContext>
</blueprint>

One of the following:

In Project Explorer, select ZooOrderApp/Camel Contexts/blueprint.xml :

Right-click the blueprint.xml, and then select 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. The Maven download process can take a few minutes.

Wait for messages (similar to the following) to appear at the end of the output. These messages indicate that the route executed successfully:

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

In Project Explorer, locate the target/messages/ folder and expand it to verify that the target/messages/received folder contains the six message files, message1.xml through message6.xml:

Double-click message1.xml to open it in the route editor’s Design tab, and then select the Source tab to see the XML code:

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

<order>
  <customer>
    <name>Bronx Zoo</name>
    <city>Bronx NY</city>
    <country>USA</country>
  </customer>
  <orderline>
    <animal>wombat</animal>
    <quantity>12</quantity>
  </orderline>
</order>

In the Palette, open the Routing drawer, click a Choice ( ) pattern, and then (in the Design canvas) click the From_from1 node.

The Route_route1 container expands to accommodate the Choice_choice1 node. The error icon indicates that the Choice_choice1 node requires a child node, which you add next.

From the Routing drawer, click the When ( ) pattern and then, in the canvas, click 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:

Select xpath (for the XML query language) because the test messages are written in XML.

In the indented Expression field, type: /order/orderline/quantity/text() > 10

This expression specifies that only messages in which the value of the quantity field is greater than 10 travel this path in the route (to the invalidOrders folder).

Leave each of the remaining properties as they are.

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

In the canvas, click the When_when1 node.

The When_when1 container expands to accommodate the Log_log1 node:

In the Message field, type: The quantity requested exceeds the maximum allowed - contact customer.

In the canvas, click the Log_log1 node.

The When_when1 container expands to accommodate the SetHeader_setHeader1 node:

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

Leave the remaining properties as they are.

In the canvas, click the SetHeader_setHeader1 node.

The When_when1 container expands to accommodate the To_to1 node.

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 type _Invalid in the Id field:

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

In the canvas, click the Choice_choice1 container:

The Choice_choice1 container expands to accommodate the Otherwise_otherwise1 node.

In the Id field, change _otherwise1 to _elseValid:

In the canvas, click the Otherwise_elseValid node:

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

In the Message field, type This is a valid order - OK to process.

Leave the remaining properties as they are.

In the canvas, click the Log_log2 node.

The Otherwise_elseValid container expands to accommodate the SetHeader_setHeader2 node.

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.

Leave the remaining properties as they are.

In the canvas, click the SetHeader_setHeader2 node.

The Otherwise_elseValid container expands to accommodate the To_to1 node.

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

Save the routing context file.

The completed content-based router should look like this:

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

<?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() &gt; 10</xpath>
                    <log id="_log1" message="The quantity requested exceeds the maximum allowed - contact customer."/>
                    <setHeader headerName="Destination" id="_setHeader1">
                        <constant>Invalid</constant>
                    </setHeader>
                    <to id="_Invalid" uri="file:target/messages/invalidOrders"/>
                </when>
                <otherwise id="_elseValid">
                    <log id="_log2" message="This is a valid order - OK to process."/>
                    <setHeader headerName="Destination" id="_setHeader2">
                        <constant>ReadyForDispatcher</constant>
                    </setHeader>
                    <to id="_Valid" uri="file:target/messages/validOrders"/>
                </otherwise>
            </choice>
        </route>
    </camelContext>
</blueprint>

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

Check that the target/messages/invalidOrders folder contains message1.xml and message3.xml.

In these messages, the value of the quantity element exceeds 10.

Check that the target/messages/validOrders folder contains the four message files that contain valid orders:

In the canvas, click to the right of the Route_route1 container:

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

In the canvas, click the Route_route2 container:

The Route_route2 container expands to accommodate the Direct component (the From_from2 node):

In the Uri field, replace name (following direct:) with OrderFulfillment, and in the Id field, enter _direct:OrderFulfillment.

In the canvas, click the From _direct:OrderFulfillment node.

The Route_route2 container expands to accommodate the Choice_choice2 node:

In the Properties view, leave the Choice_choice2 node’s properties as they are.

In the canvas, click the Choice_choice2 node.

The Choice_choice2 container expands to accommodate the When_when2 node.

Set the When_when2 node’s properties as follows:

In the canvas, click the When_when/usa container.

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

In the Properties view:

In the canvas, click the When_when/usa node.

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

Set the node’s properties as follows:

In the canvas, click above the SetHeader node.

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

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

In the Properties view:

Save the file.

The USA branch of Route_route2 should look like this:

In the canvas, click the Choice_choice2 container.

The Choice_choice2 container expands to accommodate the Otherwise_otherwise1 node.

In the canvas, click the Otherwise_else/ger node.

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

In the Properties view:

In the canvas, click below the SetHeader_setHead_ger node.

The Otherwise_else/ger container expands to accommodate the Log_log3 node. If needed, drag the connector error from the Log_log3 node to the SetHeader_setHead_ger node:

In the Properties view:

In the Components drawer, select a File pattern ( ) and then click below the Log_ger node.

The Otherwise_else/ger container expands to accommodate the To_to1 node. If needed, drag the connector error from the SetHeader_setHead_ger node to the To_to1 node:

In the Properties view:

Check the end of the Console’s output. You should see these lines:

Check the target destination folders to verify that the routes executed properly:

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

Set unconditional breakpoints on the following Route_Route1 nodes:

Set unconditional breakpoints on the following Route_Route2 nodes:

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:

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 15 to 10 (to change it from an invalid order to a valid order):

This changes the in-memory value only (it does not edit the message3.xml file).

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

The pane below the list of variables displays the entire body of message3, 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, message3 now follows the branch leading toTo_Fulfill and Route_route2.

Switch to the Breakpoints view, and clear each check box next to the breakpoints listed below _choice1. Clearing the check box of a breakpoint temporarily disables it.

Click to step to the next breakpoint:

The debugger skips over the disabled breakpoints and jumps to _FulFill in _route1 [blueprint.xml].

Click again to step to the next breakpoint:

The debugger jumps to _GER in _route2 [blueprint.xml].

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

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

You should see that only message1 was sent to the invalidOrders and that message3.xml appears in the validOrders/Germany folder.

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

The 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 Run As → Local Camel Context (without tests).

In JMX Navigator, expand Local Processes.

Expand the elements of your route:

Right-click the Routes node and then select Start Tracing:

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

To see all message flow paths clearly, you probably need to rearrange the nodes by dragging them to fit neatly in the Diagram View tab. You may also need to adjust the size of the other views and tabs in Red Hat CodeReady Studio to allow the Diagram View tab to expand.

In Project Explorer, expand ZooOrderApp/src/data, so that 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.

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) to populate the view with message2.xml message traces.

Each time you drop a message on 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.

Open Diagram View, to see that the associated step in the route is highlighted:

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.

Hover the mouse pointer over the displayed metrics to reveal additional metrics about message flow:

Optionally, you can drag and drop the remaining messages in ZooOrderApp/src/data/ into the _context1>Endpoints>file>src/data?noop=true node in JMX Navigator at any time, as long as tracing remains enabled.

On each subsequent drop, remember to click the (Refresh button) to populate Messages View with the new message traces.

When done:

To start this tutorial, you need the ZooOrderApp project resulting from one of the following:

Delete any trace-generated messages from the ZooOrderApp project’s /src/data/ directory and /target/messages/ subdirectories in Project Explorer. Trace-generated messages begin with the ID- prefix. For example, Figure 9.1, “Trace-generated messages” shows eight trace-generated messages:

Figure 9.1. Trace-generated messages

Select all trace-generated messages in batch, right-click and then select Delete.

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

Make sure ZooOrderApp/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 and then select New → Camel Test Case.

In the Camel XML file under test field, click to open a file explorer configured to filter for XML files, and then select the ZooOrderApp project’s blueprint.xml file:

Click OK. The Name field defaults to BlueprintXmlTest.

Click Next to open the Test Endpoints page.

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

Click Finish.

In Project Explorer, expand the ZooOrderApp project to expose the BlueprintXmlTest.java file:

Add the two lines shown in bold text. Adding the first line causes an error that will be resolved when you update the pom.xml file as instructed in the next section.

package tutorial.zooapp.route;

import org.apache.camel.EndpointInject;
import org.apache.camel.Produce;
import org.apache.camel.ProducerTemplate;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.component.mock.MockEndpoint;
import org.apache.camel.test.blueprint.CamelBlueprintTestSupport;
import org.apache.commons.io.FileUtils;
import org.junit.Test;
import java.io.File;

Replace those lines — protected Object[] expectedBodies={ …​…​ expectedBody2</something>"}; —  with these protected String body#; lines:

protected String body1; protected String body2; protected String body3; protected String body4; protected String body5; protected String body6;

Scroll down to the line public void testCamelRoute() throws Exception {, and insert directly after it the lines body# = FileUtils.readFileToString(new File("src/data/message#.xml"), "UTF-8"); shown below. These lines will indicate an error until you update the pom.xml file as instructed in the next section.

// Valid orders body2 = FileUtils.readFileToString(new File("src/data/message2.xml"), "UTF-8"); body4 = FileUtils.readFileToString(new File("src/data/message4.xml"), "UTF-8"); body5 = FileUtils.readFileToString(new File("src/data/message5.xml"), "UTF-8"); body6 = FileUtils.readFileToString(new File("src/data/message6.xml"), "UTF-8"); // Invalid orders body1 = FileUtils.readFileToString(new File("src/data/message1.xml"), "UTF-8"); body3 = FileUtils.readFileToString(new File("src/data/message3.xml"), "UTF-8");

Replace the block of code that begins with outputEndpoint.expectedBodiesReceivedInAnyOrder(expectedBodies); and ends with …​inputEndpoint.sendBody(expectedBody); } with the lines shown here:

// Invalid orders outputEndpoint.expectedBodiesReceived(body1, body3); // Valid orders for USA output3Endpoint.expectedBodiesReceived(body2, body5, body6); // Valid order for Germany output4Endpoint.expectedBodiesReceived(body4);

Leave the remaining code as is.

Check that your updated BlueprintXmlTest.java file has the required modifications. It should look something like this:

package tutorial.zooapp.route;

import org.apache.camel.EndpointInject;
import org.apache.camel.Produce;
import org.apache.camel.ProducerTemplate;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.component.mock.MockEndpoint;
import org.apache.camel.test.blueprint.CamelBlueprintTestSupport;
import org.apache.commons.io.FileUtils;
import org.junit.Test;
import java.io.file;

public class BlueprintXmlTest extends CamelBlueprintTestSupport {

	// TODO Create test message bodies that work for the route(s) being tested
	// Expected message bodies
	protected String body1;
	protected String body2;
	protected String body3;
	protected String body4;
	protected String body5;
	protected String body6;
	// Templates to send to input endpoints
	@Produce(uri = "file:src/data?noop=true")
	protected ProducerTemplate inputEndpoint;
	@Produce(uri = "direct:OrderFulfillment")
	protected ProducerTemplate input2Endpoint;
	// Mock endpoints used to consume messages from the output endpoints and then perform assertions
	@EndpointInject(uri = "mock:output")
	protected MockEndpoint outputEndpoint;
	@EndpointInject(uri = "mock:output2")
	protected MockEndpoint output2Endpoint;
	@EndpointInject(uri = "mock:output3")
	protected MockEndpoint output3Endpoint;
	@EndpointInject(uri = "mock:output4")
	protected MockEndpoint output4Endpoint;

	@Test
	public void testCamelRoute() throws Exception {
		// Create routes from the output endpoints to our mock endpoints so we can assert expectations
		context.addRoutes(new RouteBuilder() {
			@Override
			public void configure() throws Exception {
				// Valid orders
				body2 = FileUtils.readFileToString(new File("src/data/message2.xml"), "UTF-8");
				body4 = FileUtils.readFileToString(new File("src/data/message4.xml"), "UTF-8");
				body5 = FileUtils.readFileToString(new File("src/data/message5.xml"), "UTF-8");
				body6 = FileUtils.readFileToString(new File("src/data/message6.xml"), "UTF-8");

				// Invalid orders
				body1 = FileUtils.readFileToString(new File("src/data/message1.xml"), "UTF-8");
				body3 = FileUtils.readFileToString(new File("src/data/message3.xml"), "UTF-8");

				from("file:target/messages/invalidOrders").to(outputEndpoint);
				from("file:target/messages/validOrders/USA").to(output3Endpoint);
				from("file:target/messages/validOrders/Germany").to(output4Endpoint);
				from("direct:OrderFulfillment").to(output2Endpoint);
			}
		});

		// Define some expectations

		// TODO Ensure expectations make sense for the route(s) we're testing
		// Invalid orders
		outputEndpoint.expectedBodiesReceived(body1, body3);

		// Valid orders for USA
		output3Endpoint.expectedBodiesReceived(body2, body5, body6);

		// Valid order for Germany
		output4Endpoint.expectedBodiesReceived(body4);

		// Validate our expectations
		assertMockEndpointsSatisfied();
	}

	@Override
	protected String getBlueprintDescriptor() {
		return "OSGI-INF/blueprint/blueprint.xml";
	}

}

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>

Select Run As → JUnit Test.

By default, the JUnit view opens in the sidebar. (To provide a better view, drag it to the bottom, right panel that displays the Console, Servers, and Properties tabs.)

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

Figure 9.2. Successful JUnit run

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

Figure 9.3. Failed JUnit run

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 ZooOrderApp project’s /src/data folder in Project Explorer (see Figure 9.1, “Trace-generated messages”).

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

Expand the Red Hat JBoss Middleware node to expose the available server options:

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

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

Select JavaSE-1.8 (recommended). If necessary, click the Environments button to select it from the list.

Click Next to save the runtime definition for the Fuse Server and open the 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 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 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, type the password required for User name to log into the server.

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

Click Finish.

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

In the Servers view, expand the Runtime Server:

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

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

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

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

Wait a few seconds for the server to start. When it does:

In the Servers view, right-click n.n Runtime Server [Started] and then 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 ZooOrderApp and click Add to assign it to the Fuse server:

Click Finish.

The Servers view should show the following:

In the JMX Navigator, expand the Camel folder to expose the elements of the ZooOrderApp.

Click the Bundles node to populate the Properties view with the list of bundles installed on the runtime server:

In the Search field, type ZooOrderApp. The corresponding bundle is shown:

Note

Alternatively, you can issue the osgi:list command in the Terminal view to see a generated list of bundles installed on the server runtime. The tooling uses a different naming scheme for OSGi bundles displayed by the osgi:list command. In this case, the command returns Camel Blueprint Quickstart, 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] and then click Refresh.

The Camel tree under JMX[Connected] disappears.