Oracle UCM Web Services

Using Oracle UCM Web Services 12-3

12.2 Oracle UCM Web Services

Oracle UCM provides two types of web services: a general generic JAX-WS based web service, and a native SOAP based web service. The two types of web services reside in two different context roots. The context root is the primary identifier in the URL for accessing the web services. The context roots follow: ■ idcws - Use this context root for general access to an Oracle Content Server instance through any regular web services client. ■ idcnativews - The Remote IDC client RIDC uses the native web services. It is recommended that you do not develop custom client against these services. The following table describes the Oracle UCM web service in the idcws context root. The following table describes the Oracle UCM web services in the idcnativews context root. Oracle UCM Web Service Descriptions GenericSoapService This service uses a generic format similar to HDA for its SOAP format. It is almost identical to the generic SOAP calls that you can make to Oracle Content Server when you set IsSoap=1. Details of the format can be found in the published WSDL at idcwsGenericSoapPort?WSDL. You can apply WS-Security to GenericSoapService through WS-Policy. Oracle Content Server supports Oracle Web Services Manager OWSM policies for Security Assertion Markup Language SAML and username-token. As a result of allowing WS-Security policies to be applied to this service, streaming Message Transmission Optimization Mechanism MTOM is not available for use with this service. Very large files greater than the memory of the client or the server cannot be uploaded or downloaded. Oracle UCM Web Services Descriptions IdcWebRequestService This is the general Oracle UCM service. Essentially it is a normal socket request to Oracle Content Server, wrapped in a SOAP request. Requests are sent to Oracle Content Server using streaming Message Transmission Optimization Mechanism MTOM in order to support large files. Streaming MTOM and WS-Security do not mix. As a result, do not apply WS-Security to this service, because it will break the streaming file support. In order to achieve security, you must first log in using the IdcWebLoginService, then use the same JSESSIONID received from that service in the next call to IdcWebRequestService as a cookie. IdcWebLoginService This service is solely for adding security to IdcWebRequestService calls. There are no parameters for this service; it simply creates a session. The important field to retrieve is the JSESSIONID for future calls to IdcWebRequestService. If you want to use WS-Security with IdcWebRequestService, then apply it here. Oracle Content Server supports Oracle Web Services Manager OWSM policies for Security Assertion Markup Language SAML and username-token. 12-4 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management

12.3 Installation and Configuration