Database Reference
In-Depth Information
Role
Location
Entity
Example
A BPEL process as a final worker wants to
deliver a message to its final destination/
ESB.
Composition subcontroller,
Dispatcher, and Mediator
EBF,
EBS
The TP Endpoint URLs could be as fol-
lows: File, JMS, HTTP, and FTP
ESB wants to deliver a message to SCA or to
the Endpoint. A URL as a variable is re-
turned.
Lookup type 3: The service wants to perform data transformation/validation:
Role
Location
Entity
Example
URL to XSLT
Dispatcher and Mediator EBS
XQuery String The ESB Service resolves parameters for transformation/Enrichment
Lookup type 4: The service is looking for Endpoint particulars ( bindingTemplate in
the tModel notation):
Role
Location
Entity
Example
Dispatcher and Medi-
ator
Object (EBO/
SDO)
ESB is looking for the Endpoints' particulars (Transport, Proxy, Port, and Username/
Password).
EBS
Lookup type 5: The service is looking for an internal task's parameters:
Role
Location
Entity
Example
WSIF invocation, similar to Oracle E-Business Suite SOA Gateway realization; see the
Metadata definition section at http://docs.oracle.com/cd/E18727_01/doc.121/e12169/
T511175T513090.htm .
Object
(EBO/
EBM)
Service
participant
EBF
Java callout from BPEL or Mediator to obtain the additional object's parameters.
Lookup type 6: The service is making a decision(s):
Role
Location
Entity
Example
BPEL uses the Rule Engine to get a value (any value in-
cluding true or false ) or an object.
Dispatcher, Mediator,
Service-participant
EBF,
EBS
Object (EBO/SDO), TP
Endpoint URL
The ESB Service is looking for another service.
Search WWH ::




Custom Search