Chapter 6. Editing a routing context in the route editor

Select one of the methods for adding a route.

With the Design tab selected, notice that the Properties view displays the list of the new route’s properties for you to edit.

In the Properties view, enter :

Drag the pattern over the target Route container and drop it.

Alternatively, you can drop a pattern on an existing node that has no outgoing connection, or on a connection existing between two nodes, to have the tooling automatically wire the connections between all nodes involved.

The tooling checks whether the resulting connection is valid and then either allows or prevents you from dropping the pattern on the drop target. For valid connections, the tooling:

Drag the source node’s connector arrow ( ) to the target node.

The direction of the connection represents the direction messages flow between the nodes in the route.

While hovering over the target node, release the mouse button to drop the connector on it.

The route editor updates the <route> element in the routing context file with the xml generated from the connection. You can view the xml in the Source tab.

On the canvas, select the node you want to configure.

The Properties view lists all of the selected node’s properties for you to edit. For EIPs, the Details tab lists all of a pattern’s properties. For components from the Components drawer, the Details tab lists the general properties and those that require a value, and the Advanced tab lists additional properties grouped according to function.

The Documentation tab describes the pattern and each of its properties.

If the routing context contains more than one route, first select the route you want to delete in the Project Explorer view.

On the canvas, click the Route container’s icon.

Enter the bean elements needed by your route before the camelContext element.

For example:

<!-- Configure the Inbound SAP Connections -->
 <bean id="sap-configuration" class="org.fusesource.camel.component.sap.SapConnectionConfiguration" activation="eager">
     <property name="destinationDataStore">
         <map>
             <entry key="quickstartDest" value-ref="quickstartDestinationData" />
         </map>
     </property>
     <property name="serverDataStore">
         <map>
             <entry key="quickstartServer" value-ref="quickstartServerData" />
         </map
     </property>
 </bean>

...

 <camelContext trace="false" id="sap-srfc-destination-fuse-context" xmlns="http://camel.apache.org/schema/blueprint">
	 <route id="sap-srfc-destination-fuse-route">
	     <from uri="file:work/camel-sap/input"/>
	     <convertBodyTo type="java.lang.String"/>
	     <log message="${body}" loggingLevel="INFO"/>
	     <to uri="sap-srfc-destination:quickstartDest:BAPI_FLCUST_GETLIST"/>
	     <log message="${body}" loggingLevel="INFO"/>
      </route>
 </camelContext>

At the bottom of the route editor, click the Configurations tab to display global configurations, if there are any.

Click Add to open the Create a new global element dialog.

The options are:

In the Create a new global element dialog, select Endpoint and click OK to open the Select component dialog.

Note

The Grouped by categories option groups components by type.

In the Select component dialog, scroll through the list of Camel components to find and select the component you want to add to the context file, and then enter an ID for it in the Id field.

In this example, the JMS component is selected and myJMS is the Id value.

Click Finish.

You can now set properties in the Properties view as needed.

The tooling autofills Id with the value you entered in the component’s Id field in [globalEndptSelect]. In this example, Camel builds the uri (required field) starting with the component’s schema (in this case, jms:), but you must specify the destinationName and the destinationType to complete the component’s uri.

In the Destination Name field, enter the name of the destination endpoint (for example, FOO.BAR). In the Destination Type field, enter the endpoint destination’s type (for example, queue, topic), temp:queue, or temp:topic).

The Properties view’s Details and Advanced tabs provide access to all properties available for configuring a particular component.

For example, click the Consumer (advanced) tab.

Enable the properties Eager Loading Of Properties and Expose Listener Session.

In the route editor, switch to the Source tab to see the code that the tooling added to the context file (in this example, a configured JMS endpoint), before the first route element.

In the Create a new global element dialog, select Data Format and click OK to open the Create a global Data Format dialog.

The data format defaults to avro, the format at the top of the list of those available.

In the Id field, enter a name for the format, for example, myDataFormat).

Click Finish.

In the Properties view, set property values as appropriate for your project, for example:

In the route editor, click the Source tab to see the code that the tooling added to the context file. In this example, a configured xmljson data format is before the first route element.

In the Create a new global element window, select Bean and click OK to open the Bean Definition dialog.

Identify a bean class or a factory bean.

To specify a factory bean, you must have already added another global bean with a factory class specified. You can then select that global bean to declare it as a global bean factory. One instance of the bean factory class will be in the runtime. Other global beans can call factory methods on that class to create their own instances of other classes.

To fill the Class field, do one of the following:

If the bean you are adding requires one or more arguments, in the Constructor Arguments section, for each argument:

Optionally specify one or more properties that are accessible to the global bean. In the Bean Properties section, do the following for each property:

Click Finish to add the global bean to the configuration. The global bean ID you specified appears in the Configurations tab, for example:

Switch to the Source tab to see the bean element that the tooling added to the context file. For example:

Click the Configurations tab to return to the list of global elements and select a global bean to display its standard properties in the Properties view, for example:

Set global bean properties as needed:

In the Configurations tab, select the global element that you want to delete.

For example, suppose you want to delete the data format myDataFormat that was added in the section called “Adding a global data format”:

Click Delete.

The global element myDataFormat disappears from the Configurations tab.

Switch to the Source tab to check that the tooling removed the XML code from the routing context.

In the Configurations tab, select the global element that you want to edit.

For example, to edit the endpoint myJMS that was added in the section called “Adding a global endpoint”:

Click Edit.

In the Properties view, modify the element’s properties as needed.

For example, open the Advanced Consumer tab, and change the value of Concurrent Consumers to 2:

In the route editor, click the Source tab and check that the tooling added the property concurrentConsumers=2 to the routing context:

When done, click OK to close the Preferences dialog.

You can restore the route editor’s original defaults at any time by returning to the Editor preferences dialog and clicking Restore Defaults.