How to invoke web services in sequence in ESB?

Question

Is there any way to invoke multiple services (web, adapter) in a sequence using only the ESB? (I don't want to bring in BEPL).
Something like this:
Read File using File Adapter into schema
|
v
Invoke database adapter to retrieve data and use it to enrich schema
|
v
Invoke web service to retrieve more data and use it to enrich schema
|
v
Send enriched schema to a final web service to perform some operation.
Thanks in advance.

Answer 1

From a technical standpoint, all I want to do is move data from point a to endpoints b, c, and d, and then move the reply or the fault from one of endpoints b, c, or d (whichever one the request went to) back to a.
The "business logic" along the way is at 3 places:
(1). To enrich the data that's being moved. The enriching data is in a database someplace. The logic that determines what that data is in the database is in the original data (message).
Something like this:
//Based on values in the original message, get some row
If OriginalData.Body.field1 = X and OriginalData.SOAPHeader.field2 = y then retrieve Database.Row Z from the database
then
//Enrich the original message with the data from the retrieved row
OriginalData.Body.field3 = Database.Row Z.field9
(2). To decide where to move the data, i.e. b, c, or d. The decision to route the data dynamically retrieved from a web service.
Something like this:
Rule 1: If OriginalData.Body.field3 = A and OriginalData.SOAPHeader.field1= B then move data to endpoint b.
Rule 2: Or If OriginalData.Body.field2 = C and OriginalData.SOAPHeader.field4= C then move data to endpoint c.
Rule 3: Or If OriginalData.Body.field5 = C and OriginalData.SOAPHeader.field6= C then move data to endpoint d.
... and more combinations.
So, send web service the enriched data and it applies rules Rule 1, and it sends back "b". Send web service the enriched data and it applies rules Rule 2, and it sends back "c". Send web service the enriched data and it applies rules Rule 3, and it sends back "d". In this way, adding new rules to the web service lets the customer dynamically "grow" new endpoints.
(3). To transform the data from the format of point a to one of the formats of endpoints b, c, or d. The decision to transform the schema of the data is taken based on the outcome of the business logic applied in (2) above.
This is a sample use case that my customer is using to compare Oracle's ESB capabilities with other vendors', and I have to work within specific boundaries.
So, as I stated in my first post, I cannot use BPEL. All I have to establish is whether Oracle can do this using ESB.