First, create a new user in the database for creating the stored procedures as SOAP messages:

SQL>CREATE USER SOAPDEMO;

Now, set the default catalogue/qualifier for the new user to the WS catalogue where we will create procedures to be used as SOAP objects:

SQL>USER_SET_QUALIFIER ('SOAPDEMO', 'WS');

Now create a new virtual host definition, using the vhost_define() , so that we can find our SOAP objects later at a desired location.

SQL>VHOST_DEFINE (vhost=>'*ini*',lhost=>'*ini*',lpath=>'/services',ppath=>'/SOAP/',soap_user=>'SOAPDEMO');

If the mapping already exists, producing an error in the call above, and is not being used, then you can remove it using the command:

SQL>VHOST_REMOVE (vhost=>'*ini*',lhost=>'*ini*',lpath=>'/services')

	Note:
	*ini* is a special indicator telling Virtuoso to take the default values from its initialization file.

Now create a simple SOAPTEST procedure and grant the appropriate privileges to the SOAPDEMO user:

SQL> create procedure
  WS.SOAPDEMO.SOAPTEST (in par varchar)
{
  return (upper(par));
};

SQL> grant execute on WS.SOAPDEMO.SOAPTEST to SOAPDEMO;

Now test this new SOAP object's availability by using soap_client() . This function would normally return a vector representation of the SOAP object but since we know the dimensions of the object ahead of time we can pin-point the entry using the aref() function as follows:

SQL> select aref(aref(
        soap_client (url=>sprintf ('http://localhost:%s/services', server_http_port ()),
        operation=>'SOAPTEST', parameters=>vector('par', 'demotext')), 1), 1);
callret
VARCHAR
_______

DEMOTEXT

The actual SOAP object looks more like:

(("SOAPTESTResponse" ) (("CallReturn" ) "DEMOTEXT" ) )

which was generated in a Virtuoso server log for debugging purposes using the dbg_obj_print() function.

Procedures that exist under the WS.SOAPDEMO namespace and have been granted execution to the new SOAPDEMO user are now available as SOAP services and described by WSDL in this example, Virtuoso would publish them from the URL:

http://example.com/services/services.wsdl

which will yield the following WSDL description:

<?xml version='1.0'?>
<definitions
 targetNamespace='services.wsdl'
 xmlns:xsd='http://www.w3.org/1999/XMLSchema'
 xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
 xmlns:tns ='services.wsdl'
 xmlns ='http://schemas.xmlsoap.org/wsdl/'
 name='VirtuosoSOAP'>
        <message name='SOAPTEST'>
                <part name='par' type='xsd:string'/>
        </message>
        <message name='SOAPTESTResponse'>
                <part name='CallReturn' type='xsd:string'/>
        </message>
        <portType name='SOAPPortType'>
                <operation name='SOAPTEST'>
                        <input message='tns:SOAPTEST' name='SOAPTEST'/>
                        <output message='tns:SOAPTESTResponse' name='SOAPTESTResponse'/>
                </operation>
        </portType>
        <binding name='SOAPBinding' type='tns:SOAPPortType'>
                <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/>
                <operation name='SOAPTEST'>
                        <soap:operation soapAction='urn:openlinksw.com:virtuoso_soap_schema#SOAPTEST'/>
                        <input>
                                <soap:body use='encoded' namespace='urn:openlinksw.com:virtuoso_soap_schema' encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' />
                        </input>
                        <output>
                                <soap:body use='encoded' namespace='urn:openlinksw.com:virtuoso_soap_schema' encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' />
                        </output>
                </operation>
        </binding>
        <service name='SOAPService'>
                <port name='SOAPPort' binding='tns:SOAPBinding'>
                        <soap:address location='http://example.com/services'/>
                </port>
        </service>
</definitions>

	See Also:
	The Testing Web Services (VSMX) section describes Virtuoso's ability to also automatically generate a test page for your SOAP services, simply by replacing services.wsdl with services.vsmx in the URL.