The UTL_DBWS package is for the rarefied developer; that is, someone
who is very deep into Java Web services and using DII (Dynamic
Invocation Interface). The DBWS in the package name represents
database Web services, and what the package does is provide a
wrapper on top of the Java DII. Instead of using Java-specific calls
to static invocations, Oracle uses
UTL_DBWS to
provide a means of using a dynamic
invocation interface.
Sounds pretty simple, right?
MOSC note 428775.1, "DBWS Callout Utilities User's Guide for RDBMS
10.1 or 10.2," takes the developer through the setup steps to install
UTL_DBWS Callout Utilities. In general, one will need to have Java
installed and configured in the database, have JPublisher installed,
and have access to an OC4J instance on the computer, which can be
obtained via the OC4J version of Application Server. In essence, the
database is being turned into a Web service consumer.
Installing Java and checking
UTL_DBWS
status (around 20,000 SYS-owned Java
objects) is documented quite well in Oracle's documentation and
elsewhere on the Internet. Look for "How to Reload the JVM" on
MOSC or start with note 472937.1, "Information On Installed
Database Components and Schemas" and look under the first section.
Installing JPublisher comes from installing SQLJ.
If not installed, it can be
obtained with the installation CD/download used to install Oracle in
the first place. At the end, "jpub" should be found when entering this
executable at the command line.
Next, get the appropriate Web services callout utility from Oracle.
Use J2SE 1.3.x or Oracle 9.2, and 1.4.x for releases 1 and 2 of 10g
(and also works for 11g). By this point, these details probably
pertain to the five or six people who use this package. There is not
much in the way of documentation, so aside from OTN and MOSC, a
specialized book such as Oracle Database Programming Using Java and
Web Services (Elsevier Digital Press, 2006) would be in order.