In certain scenarios it is necessary to understand how Oracle WebCenter Content services are executed and which parameters are passed, so that developers can use JAVA, SOAP, and WSDL’s to integrate with external 3rd party systems.
An example of this is the use of Remote Intradoc Client (RIDC) where developers would code additional functionalities and request data using a JAVA API. In this scenario it becomes necessary to get the service details, parameters, and result sets so that the same functionality could be used in the API.
This article details the various ways this can be achieved so that developers can use this as a reference for development activities.
Generally, there are 3 ways integrations can be performed with WebCenter Content (WebCenter Content):
- SOAP WSDL’s
For all 3 languages there are inbuilt mechanisms in WebCenter Content which can be utilized to get the service details.
- Use IsJava=1
When developing using the RIDC API for WebCenter Content, we need to be able to see what the format or structure of service call is. This can be achieved by appending ‘&IsJava=1’ to the end of the service URL and refreshing the browser.
“&IsJava=1’ will return the same ASCII serialized response as RIDC would receive.
- Use of IsSOAP=1
Developing with SOAP or WSDLs which can be easily consumed by external applications is another common way to integrate with WebCenter Content. For this to be accomplished, we need to understand the format and structure of the SOAP request and response. This is achieved by appending ‘&IsSoap=1’ to the end of the service URL and refreshing the browser.
‘&IsSoap=1’ will return a soap response in the browser.
- Use of IsJSon=1
With jQuery and AJAX becoming popular, there are requirements to have components developed using these frameworks. For these components to be developed, we would need to pass the response and details to the component in the JSON format. This is achieved by appending ‘&ISJSon=1’ at the end of service URL and refreshing the browser.
‘&IsJSon=1’ will return a JSON response in the browser.
- In addition to these options, another method to get details related to page construct, result sets, and IDOC script execution etc. is to append ‘&IsPageDebug=1’ to the end of the URL and refresh the browser.
This will add an Icon on the right-hand bottom corner of the page which can be expanded to view the various available sections.
In addition to the aforementioned out of the box mechanisms, modern day browsers provide a very convenient mechanism to capture the service related details.
With Google Chrome Developer Tools (launched as F12 or Control + Shift + I) – navigate to Network Tab. Tick the checkbox ‘Preserve Log’ to make sure that all the activity for actions and sequences are captured and saved to the pane.
From the WebCenter Content console, execute either a Check-in, Search, Delete, or Folder Addition etc. and all the details for the services and the responses, parameters etc. are captured in the Network Pane.
From the Network Pane, select or highlight any requests starting with ‘idcplg?’ and open a side-pane which holds all the details related to that service. Scrolling to the end of HEADERS section shows the Query String Parameters which holds the values of the service and the parameters that has been passed to execute it successfully.
If you need further assistance please feel free to contact us directly.