Return to main navigation Page
This topic discusses Web Services 2.0. For information on Web Services 1.0, see Web Services 1.0.
Web Services refers to a communication system for applications to talk and exchange data, such as over the World Wide Web. By using Web Services, an application can publish its function or message and receive functions and messages from other applications
Typical components of a web service are:
This interface describes:
- The location of the SOAP service
- The nature of messages exchanged,such as
- Characteristics like null allowed, minimum occurrences, and so on
CPQ Cloud uses Web Services versions 1.0 and 2.0. Different features are available depending on which version of Web Services you are using.
To discover which version of Web Services you are using:
Click Web Services under Integration Platform.
The Web Services version number is shown under Web Service Version, on the upper left-hand corner of the page.
If you have a new installation of CPQ Cloud, or have upgraded to 2014 R2, version 2.0 will be listed.
Even if your installation has been using Web Services 1.0, you can use the features of Web Services 2.0 concurrently.
Features in this version of Web Services include:
|Web Services 1.0||Web Services 2.0|
|Clustering||No clustering support||Supports clustering|
|Authentication||Use CPQ Cloud customer security SOAP headers||Use standard-based authentication|
|End points||No unique end points||Each service and its WSDL have unique end points. WSDL can be accessed at runtime via its URL.|
CPQ Cloud Web Services v2.0 supports clustering, which can further improve scalability and responsiveness of CPQ Cloud for enterprise deployments. Requests don't have to go to a certain node in the server and can be load-balanced.
Every SOAP call to Web Services v1.0 by another system requires a login SOAP call to establish a session, and a logout call to close the session. Web Services v2.0 includes the user/pass in the payload header, making the service stateless and eliminating the need for login and logout calls.
Eliminating these calls with stateless Web Services reduces complexity and increases the performance of integrations with CPQ Cloud.
CPQ Cloud Web Services 2.0 supports the following two industry standards for authentication:
CPQ Cloud Web Services 2.0 can be invoked using the Web Services Security UsernameToken elements for authentication. As of CPQ Cloud release 2014 R2, the password support is limited to the PasswordText type.
In the absence of WSEE headers, the HTTP basic authentication standard is also accepted.
CPQ Cloud also supports OAuth, another form of authentication. For more information, see OAuth 2.0 Secure Login Functionality.
If you are using Web Services 1.0, see An Overview of SOAP APIs and Web Services 1.0 for information on Session ID authentication.
In Web Services 1.0, the SOAP Server URL was always
With Web Services 2.0, each Web Service has its own unique end points, listed below:
The Security Web Service is not needed for Web Services 2.0, so there is no longer a Security tab on the Web Services Test page.
For example, for a Commerce Process with the variable name oraclecpqo, the SOAP Web Service URL is:
The URL of the WSDL is the URL of the corresponding Web Service, appended with “?WSDL”. Using the same process, the URL is
Each Web Service also has its own namespace. For example, the namespace for the above Commerce Web Service is uniquely identified as:
Click Web Services in the Integration Platform section.
The Web Services Test page appears.
Notice the SOAP Services URL field, which contains information that was previously in the SOAP XML for the API.
Change the Web Service Version to 2.0 and examine the SOAP Services URL field .
Now it is
This reflects the unique end points in Web Services 2.0.
To learn more about these technologies, refer to the table below: