Databases Reference
In-Depth Information
It's also a good practice to specify a corresponding value for the
Java EE Web
Application Name
(for example,
ListingBC-webapp)
.
Once deployed, the WSDL for the Service Data Object is located at:
http://<hostname>:<port>/<webcontextroot>/<webservicename>?wsdl
Here,
hostname
represents the name of the machine on which the SOA server is
running and
port
represents the port number. The
webcontextroot
is the value
we have just configured, and the
webservicename
is the value we specified when
creating the service interface.
Registering SDO with SOA infrastructure
At this point we can deploy the SDO and invoke it from a composite via SOAP over
HTTP, just as we would for any other web service. However, we also want to bind
the SDO to a BPEL entity variable so that we can access it as if it were a local variable
within the transactional context of the BPEL process.
When invoking an SDO via a BPEL Entity variable, the BPEL process will require
the SDO to participate in its transaction. To do that, we need to invoke the SDO via a
protocol such as RMI, which will allow the propagation of the transactional context
between the two components.
To enable the SDO to be invoked via RMI, we need to configure an appropriate
ADF
Application Lifecycle Listener
to register the SDO as an RMI service. Additionally,
we must also configure the SDO to use a JDBC data source, which can participate in
a distributed transaction.
Registering the ListingSDO as an RMI service
Within the
Application Resources
section of the
Application Navigator
,
expand the
Descriptors
|
META-INF
folder structure and open the
weblogic-application.xml
ile.
Select the
Listeners
tab, and click the green plus sign to add a new listener circled;
set the
Class
to
oracle.jbo.client.svc.ADFApplicationLifecycleListener
, but don't
specify any value for
JAR Path
and
Run-As Principle
.
