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.

	Note
	Use the id attribute to identify the bean, not the name attribute.

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
	By default, the Select component dialog opens with the Show only palette components option enabled. To see all available components, disable this option.

	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.

	Note
	For the JMS component, the destination type defaults to queue. This default value does not appear in the uri field on the Details page until you have entered a value in Destination Name (required field).

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:

	Note
	To view or edit a property that you specified when you added a global bean, select the bean in the Configurations tab and then click Edit.

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

Right-click it to open the context menu, and then select Run As > Local Camel Context.

	Note
	Selecting Local Camel Context (without tests) directs the tooling to run the project without performing validation tests, which may be faster.

Right-click it to open the context menu, and then select Run As > Maven build.

The Select JCo3 and IDoc3 Archive to Import screen opens. Next to the JCo Archive File field, use the Browse button to select the JCo archive that you downloaded from the SAP Service Marketplace. After selecting the JCo archive, the Archive Version and Archive OS Platform fields are automatically filled in, so that you can check whether the library you are installing has the correct version and OS platform.

Next to the IDoc3 Archive File field, use the Browse button to select the IDoc archive that you downloaded from the SAP Service Marketplace.

After selecting both archive files, click Finish.

A new Install wizard (for installing Eclipse plug-ins) opens automatically. This wizard displays the following to plug-ins to be installed:

Navigate to the global Configurations tab of the route editor and click Add.

The Create new global element view appears.

Under SAP, select the type of connection you would like to create. Choose the SAP Connection and click Ok.

The Edit SAP Connection Configuration dialog appears. It allows you to create, edit and delete the Destination and Server Connection Configurations.

To create a new Destination Data Store, click the Add Destination tab.

The Create Destination dialog appears.

In the Properties dialog,

You are now ready to test the destination connection. In the Edit SAP Connection Configuration dialog, right-click on the destination name and select Test.

The Test Destination Connection dialog opens.

The dialog uses the current destination configuration settings to connect to the SAP Destination Data Store. If the test is successful, you will see the following message in the status area:

Connection test for destination 'YourDestination' succeeded.

Otherwise, an error report appears in the status area.

Navigate to the global Configurations tab of route editor and click Add.

The Create new global element view appears.

Under SAP, select the type of connection you would like to create. Choose the SAP Connection and click Ok.

The Edit SAP Connection Configuration dialog appears. It allows you to create, edit and delete the Destination and Server Connection Configurations.

To create a new Server Data Store, click the Add Server tab.

The Create Server dialog appears.

In the Properties dialog,

You are now ready to test the server connection. In the Edit SAP Connection Configuration dialog, right-click on the server name and select Test.

The Test Server Connection dialog opens.

The dialog uses the current server configuration settings to connect to the SAP Server Data Store. If the test is successful, you will see the following message in the status area:

Server state: STARTED
Server state: ALIVE

If the test fails, the server status is reported as DEAD.

Navigate to the global Configurations tab of route editor and click Add.

The Create new global element view appears.

Under SAP, select the SAP Connection and click Ok.

The Edit SAP Connection Configuration dialog appears. It allows you to create, edit and delete the Destination and Server Connection Configurations.

Click Delete. It will delete the selected connections.

Atlast, click Finish. It will save all the changes.

Open your Camel XML file in the route editor. If you have already installed the JBoss Fuse SAP Tool Suite, you should be able to see the SAP components under the Components palette in the route editor. The following SAP components are provided by the tool suite:

When specifying an SAP endpoint URI, you must embed either a destination name or a server connection name in the URI format. For example, the sap-srfc-destination component has the following URI format:

sap-srfc-destination:destinationName:rfcName

To reference a particular destination, use the value of the relevant entry element’s key attribute as the destinationName in this URI.

Click Next to open the Maven Projects wizard.

Click Browse to find and select the root directory of the starter quickstart application.

If the browse operation finds multiple projects, make sure you select the starter quickstart application. The full path to the starter quickstart application appears in the Projects pane.

Click Finish.

After the import operation finishes, the starter project appears in the Project Explorer view.

Double-click starter/src/main/resources/META-INF/spring/camel-context.xml to open the route in the route editor’s Design tab.

Click the Source tab to view the underlying XML.

You can see that an XML file is produced from a source endpoint and a JSON file is consumed by a target endpoint.

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:camel="http://camel.apache.org/schema/spring"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="        http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd        http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">

    <camelContext id="camelContext-272d04f8-e498-466d-b34b-3c24d01a4e10" xmlns="http://camel.apache.org/schema/spring"
        <route id="_route1">
            <from id="_from1" uri="file:src/data?fileName=abc-order.xml&noop=true"/>
            <to id="_to1" uri="file:target/messages?fileName=xyz-order.json"/>
        </route>
    </camelContext>
</beans>

Drag a Data Transformation pattern over the canvas and drop it on the Route_route1 container.

The New Transformation wizard opens with the Project, Dozer File Path, and Camel File Path fields auto filled.

Fill in the remaining fields:

Click Next.

The Source Type (XML) definition page opens, where you specify either an XML Schema (default) or an example XML Instance Document to provide the type definition of the source data:

For Source file, browse to the location of the XML schema file or the XML instance file to use for the type definition of the source data, and select it (in this case, abc-order.xsd).

The XML Structure Preview pane displays a preview of the XML structure.

In the Element root field, enter ABCOrder.

The tooling uses this text to label the pane that displays the source data items to map.

The Source Type (XML) definition page should now look like this:

Click Next to open the Target Type (JSON) definition page. This is where you specify the type definition for the target data.

Click JSON Instance Document.

In the Target File field, enter the path to the xyz-order.json instance document, or browse to it. The JSON Structure Preview pane displays a preview of the JSON data structure:

Expand all items in the Source and Target panels located on left and right sides of the Mappings panel.

Drag a data item from the Source panel and drop it on its corresponding data item in the Target panel.

For example, drag the customerNum data item from the Source panel and drop it on the custId data item in the Target panel.

The mapping appears in the Mappings panel, and the details of both the Source and Target data items appear below in the details pane.

Continue dragging and dropping source data items onto their corresponding target data items until you have completed all basic mappings.

In the starter example, the remaining data items to map are:

	Note
	You can map collections (data items containing lists or sets) to noncollection data items and vice versa, but you cannot map collections to other collections.

Click on both the Source and Target panels to quickly determine whether all data items have been mapped.

Only data items that have not been mapped are listed in the Source and Target panels.

In the starter example, the remaining unmapped Target attributes are approvalCode and origin.

Hover your cursor over each endpoint to reveal its connecter arrow.

Selecting the file:src/data?fil…​ node, drag and drop its connector arrow onto the ref:xml2json node. Likewise drag and drop the connector arrow from the ref:xml2json node onto the file:target/messa…​ node.

Connecting the nodes on the canvas creates a valid Camel route, which you can now save.

In the New Transformation Test wizard, set the following values:

Add the following code to the transform method:

startEndpoint.sendBodyAndHeader(readFile("src/data/abc-order.xml"), "approvalID", "AUTO_OK");

Click File > Save.

You can now run a JUnit test on your transformation file at any point in these tutorials.

Right click it to open the context menu, and select Run as JUnit Test.

The JUnit Test pane opens to display the status of the test. To avoid cluttering your workspace, drag and drop the pane in the bottom panel near the Console view.

In the Source panel, click the Variables view.

In the Variables view, click to open the Enter a new variable name dialog.

Enter a name for the variable you want to create.

For the starter example, enter ORIGIN.

Click OK.

The newly created variable ORIGIN appears in the Variables view in the Name column and the default value ORIGIN in the Value column.

Drag and drop the new variable ORIGIN onto the origin data item in the Target panel.

The new mapping of the variable $(ORIGIN) appears in the Mappings panel and in the details pane.

Run a JUnit test on your TransformationTest.java file. For details, see Creating the transformation test file and running the JUnit test.

The Console view displays the JSON-formatted output data:

{"custId":"ACME-123","priority":"GOLD","orderId":"ORDER1","origin":"Web",
"approvalCode":"AUTO_OK","lineItems":[{"itemId":"PICKLE","amount":1000,"cost":2.25},
{"itemId":"BANANA","amount":400,"cost":1.25}]}

Click to add an empty transformation map to the Mappings panel.

From the Target panel, drag and drop the approvalCode data item to the target field of the newly created mapping in the Mappings panel.

The approvalCode data item also appears in the details pane’s target box.

In the details pane, click on the ABCOrder source box to open the drop-down menu.

Menu options depend on the selected data item’s data type. The available options are bolded.

Select Set expression to open the Expression dialog.

In Language, select the expression language to use from the list of those available. Available options depend on the data item’s data type.

For the starter example, select Header.

In the details pane, select the source of the expression to use.

The options are Value and Script.

For the starter example, click Value, and then enter ApprovalID.

Click OK.

Both the Mappings panel and the details pane display the new mapping for the target data item approvalCode.

Run a JUnit test on your TransformationTest.java file. For details, see Creating the transformation test file and running the JUnit test.

The Console view displays the JSON-formatted output data:

{"custId":"ACME-123","priority":"GOLD","orderId":"ORDER1","origin":"Web",
"approvalCode":"AUTO_OK","lineItems":[{"itemId":"PICKLE","amount":1000,"cost":2.25},
{"itemId":"BANANA","amount":400,"cost":1.25}]}

In the Mappings panel, select the customerNum mapping to populate the details pane.

In the details pane, click on the ABCOrder source box to open the drop-down menu.

Select Add custom transformation to open the Add Custom Transformation page.

Click next to the Class field to open the Create a New Java Class wizard.

Modify the following fields:

Click Finish.

The Add Custom Transformation page opens with the Class and Method fields auto filled:

Click OK to open the MyCustomMapper.java file in the Java editor:

Edit the brackets method to change the last line return null; to this:

return "[" + input + "]";

Click the transformation.xml tab to switch back to the transformation editor.

The details pane shows that the brackets method has been associated with the customerNum data item.

The brackets method is executed on the source input before it is sent to the target system.

Run a JUnit test on your TransformationTest.java file. For details, see Creating the transformation test file and running the JUnit test.

The Console view displays the JSON-formatted output data:

{"custId":"[ACME-123]","priority":"GOLD","orderId":"ORDER1","origin":"Web",
"approvalCode":"AUTO_OK","lineItems":[{"itemId":"PICKLE","amount":1000,"cost":2.25},
{"itemId":"BANANA","amount":400,"cost":1.25}]}

In the Mappings panel, select the mapping id  — > itemId to display the mapping in the details pane.

On the Source box, click to open the drop-down menu, and select Set property.

In the Select a property page, expand the header node and select customerNum. Click OK to save the changes.

The details pane now shows that XyzOrder has a lineItems field. Click the toggle button next to lineItems to increase its value to 1.

	Note
	Indexes are zero-based, so a value of 1 selects the second instance of itemId in the collection.

Notice that the details pane shows customerNum mapped to the itemId of the second item in the lineItems collection.

Run a JUnit test on your TransformationTest.java file. For details, see Creating the transformation test file and running the JUnit test.

The Console view displays the JSON-formatted output data:

{"custId":"[ACME-123]","priority":"GOLD","orderId":"ORDER1","origin":"Web",
"approvalCode":"AUTO_OK","lineItems":[{"amount":1000,"cost":2.25},
{"itemId":"ACME-123","amount":400,"cost":1.25}]}

In the Transformations panel, select the status to priority mapping to populate the details pane.

In the Source box, click to open the drop-down menu, and select Add transformation.

In the Transformations pane, select append, and in the Arguments pane, enter -level for the value of suffix.

This append function adds the specified suffix to the end of the status string before mapping it to the target priority data item.

Click OK.

By default, the details pane displays the results of adding the append function to the status data item in a user-friendly format. You can change this formatting by clicking the right-most on the Source box, and selecting Show standard formatting.

Run a JUnit test on your TransformationTest.java file. For details, see Creating the transformation test file and running the JUnit test.

The Console view displays the JSON-formatted output data:

{"custId":"[ACME-123]","priority":"GOLD-level","orderId":"ORDER1","origin":"Web",
"approvalCode":"AUTO_OK","lineItems":[{"amount":1000,"cost":2.25},{"itemId":"ACME-123",
"amount":400,"cost":1.25}]}

Start the JBoss Fuse Server (see Starting a Server), and wait for the JBoss Fuse shell to appear in the Terminal view:

For each of the required camel- features, at the JBossFuse:admin@root> prompt type:

features:install camel-<featureName>

Where featureName is one of dozer, jackson, or jaxb.

To verify that each of the features was successfully installed, at the JBossFuse:admin@root> prompt type:

features:list --ordered --installed

You should see the camel features you just installed in the output listing: