It's All About the Platform.

A Walkthrough Example Execution of the Generic Soap Service (IDCWS)

Guest Author


This blog post is a walkthrough of an example web service call to the IDCWS web service in Oracle Webcenter Content and follows on from the introduction in the previous post. Using Jdeveloper WSDL Proxy Generation Class Functionality we take the IDCWS wsdl and generate the Web Service Proxy classes. Following this we construct a SOAP request and execute that against Webcenter Content.

As already mentioned in the Introduction post the Generic Soap Service is a wrapper for executing IdcServices, the services through which operations are performed on Webcenter Content. Therefore the Generic Soap Service only has one operation called the GenericSoapOperation that takes parameters releated to the desired IdcService and the operation executed. Please note that the parameters are defined by the IdcService rather than the GenericSoapOperation. The response can then be retrieved and processed.


Here is the walkthrough video:


In our example I have chosen to execute the GET_SEARCH_RESULTS IdcService. I have specified a query text of 'hello' and also a dSecurityGroup of ‘PersonalSpaces’. I have previously checked in a document into this security group so that it will appear in our Search Results.

As you may have seen in the video, the user credentials are stored in the GenericSoapPortClient Java class. The username and password are encrypted and added to the Authorization http request header to authenticate against Webcenter Content using Basic Authentication security. The credentials are protected by SSL encryption during the transmission from client to server over https in a Fusion Applications SaaS environment. Depending on the policy configuration on the Fusion Applications SaaS environment, various other authentication methods can be used. SAML is an example but would require help from Oracle Support to create the relevant security files in the Fusion Applications SaaS environment.

SOAP Envelope

So here is the SOAP request that is constructed by the Java code in the video:

  <ucm:GenericRequest webKey="cs">
    <ucm:Service IdcService="GET_SEARCH_RESULTS">
        <ucm:Field name="QueryText">hello</ucm:Field>



We have covered how to execute the IDCWS web services using Java. In this example we used the IdcService called GET_SEARCH_RESULTS however any IdcService that the user has access to in the UI can also be accessed through this web service. For further details on what services can be executed please see the Webcenter Content Services Reference Guide.

Further Reading

Here are some web links for further information on this subject

Join the discussion

Comments ( 1 )
  • Pooja Wednesday, October 26, 2016

    Hi Peter,

    If I want to call GET_SEARCH_RESULTS service (or a custom service) as WS(/idcws/GenericSoapPort) from SOAPUI for testing purpose, is it mandatory to provide <wsse:Security> (and set up WS security/policy)? Can i only set Basic Authentication header (with user credentials) and call the service?

    I tried and got this error -


    Please suggest.

    P.S. I do not have OWSM enabled.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.