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

Sending the Client Name in Stateful Web Services


A stateful Web service request execution involves:

  1. Stateful login. A one time operation, which covers both login with username and password as well as SSO login.
  2. Stateful request execution. Multiple request operations using the session ID returned by the login operation.

For a stateful request, the following considerations apply:

  • If the stateful request requires tracking of the client name, then it must be specified in the stateful login operation.
  • If a client name is specified in a stateful request execution, then it is ignored.
  • All the stateful requests executed with the session ID returned by the stateful login request are displayed in the Web Services Utilization page with the client name specified in the login operation.

Stateful Login

The login operation can be a HTTP request or a SOAP over HTTP request (R16 compatibility mode).

When the stateful login is a HTTP request, the client name is sent as the HTTP header parameter X-ClientName.

For a login with username and password:

GET http://<servername>:<portno>/Services/Integration?command=login

Http Header:

username: <username>

password: <password>

X-ClientName: Oracle Corporation, Web Services On Demand Guide

For an SSO login:

GET http://<servername>:<portno>/Services/

Integration?command=ssologin&odSsoToken=[Token Value]

X-ClientName: Oracle Corporation, Web Services On Demand Guide

Oracle Web Services On Demand Guide, Version 21.0 (Oracle CRM On Demand Release 33) Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices.