Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.140.9. Example 2: Writing Data to SAP
Overview Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
This example demonstrates a route which creates a
FlightTrip
business object instance in SAP. The route invokes the FlightTrip
BAPI method, BAPI_FLTRIP_CREATE
, using a destination endpoint to create the object.
Java DSL for route Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
The Java DSL for the example route is as follows:
from("direct:createFlightTrip") .to("bean:createFlightTripRequest") .to("sap-srfc-destination:nplDest:BAPI_FLTRIP_GETLIST?transacted=true") .to("bean:returnFlightTripResponse");
from("direct:createFlightTrip")
.to("bean:createFlightTripRequest")
.to("sap-srfc-destination:nplDest:BAPI_FLTRIP_GETLIST?transacted=true")
.to("bean:returnFlightTripResponse");
XML DSL for route Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
And the Spring DSL for the same route is as follows:
Transaction support Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
Note that the URL for the SAP endpoint has the
transacted
option set to true
. As discussed in Section 140.5, “Transaction Support”, when this option is enabled the endpoint ensures that an SAP transaction session has been initiated before invoking the RFC call. Because this endpoint’s RFC creates new data in SAP, this options is necessary to make the route's changes permanent in SAP.
Populating request parameters Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
The
createFlightTripRequest
and returnFlightTripResponse
beans are responsible for populating request parameters into the SAP request and extracting response parameters from the SAP response respectively following the same sequence of operations as demonstrated in the previous example.