Oracle Web Services On Demand Guide > Overview of Web Services On Demand > Web Service Client Name Identification >

Sending the Client Name in Stateless Web Services Requests

Every stateless Web service request that requires tracking of the client name must include the <ClientName> element in the SOAP header, with the namespace "urn:crmondemand/ws" (or the namespace might be defined at the root level). This is shown in the following example:

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Header>

<wsse:Security>

<wsse:UsernameToken>

wsse:Username>USERNAME</wsse:Username>

<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password</wsse:Password>

</wsse:UsernameToken>

</wsse:Security>

<ClientName xmlns="urn:crmondemand/ws">Oracle Corporation, Web Services On Demand Guide</ClientName>

</soap:Header>

<soap:Body>

<AccountQueryPage_Input xmlns="urn:crmondemand/ws/ecbs/account/10/2004">

<ListOfAccount xmlns="urn:/crmondemand/xml/account/">

<Account>

   <AccountName>LIKE 'a1'</AccountName>

   <Location/>

</Account>

</ListOfAccount>

</AccountQueryPage_Input>

</soap:Body>

</soap:Envelope>

A stateless request execution might or might not result in an explicit login operation in Oracle CRM On Demand, as follows:

• If a stateless request execution results in explicit login, then two entries are created in the Web Services Utilization page. Both the entries for this request, that is, the login and operation execution, show the client name specified in the SOAP request.
• If a stateless request execution does not result in explicit login, then a single entry is created in the Web Services Utilization page, and it has the client name specified in the SOAP request.