RIDC API to access WebCenter Content

Fix: Missing RIDC libs issue for 12c

Earlier (prior to 12c) all the Webcenter Extensions use to be shipped and installed to JDeveloper by just installing Webcenter Extensions to that specific version of JDeveloper but with the latest 12c (12.2.1.3) release there are lot of missing parts in the extensions.

After installing extension you pretty much get features to skin the applications and to add, manage custom task-flows. Few of my current applications which are in the process of migration heavily use Webcenter Content I must say all of our content pretty much sits there so upon working my way through documents i found a fix which I got confirmed from the official support team as well to use it.

FIX:

Get the extension with name "oracle.ucm.ridc-jdev.zip" from the below location in WebCenter Content Server:

$MW_HOME/oracle_common/ucm/Distribution/RIDC/jdev

Install the extension to Jdeveloper as below:

Help -> Updates

Once the extension is installed you can use the RIDC API's to access Content Server services.

Happy Coding ✌

Comments

Spring Boot - RestTemplate PATCH request fix

In Spring Boot, you make a simple http request as below: 1. Define RestTemplate bean @Bean public RestTemplate restTemplate () { return new RestTemplate (); } 2. Autowire RestTemplate wherever you need to make Http calls @Autowire private RestTemplate restTemplate ; 3. Use auto-wired RestTemplate to make the Http call restTemplate . exchange ( "http://localhost:8080/users" , HttpMethod . POST , httpEntity , String . class ); Above setup works fine for all Http calls except PATCH. The following exception occurs if you try to make a PATCH request as above Exception: I / O error on PATCH request for \ "http://localhost:8080/users\" : Invalid HTTP method: PATCH ; nested exception is java . net . ProtocolException : Invalid HTTP method: PATCH Cause: Above exception happens because of the HttpURLConnection used by default in Spring Boot RestTemplate which is provided by the standard JDK HTTP library. More on this at this bug Fix: This can b...

Settings.xml for Maven, JFrog

For development and deployment of applications we always use an artifactory in real-time world to host artifacts needed for your build and also as a target to deploy artifacts generated in the build process. For Maven, to communicate with artifactory we need a settings.xml file which is usually located at "/User/rake/.m2/settings.xml" this file consists of how to authenticate to the artifactory servers and authorizations to read/ write to different locations like release, snapshots e.t.c... Settings.xml can be generated using the artifactory you're using which in my case is JFrog , but here's a sample settings file for your reference incase you're feeling lazy☺ <?xml version="1.0" encoding="UTF-8"?> <settings xsi:schemaLocation= "http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns= "http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi= "http://www.w3.org/2001/XM...

RADUS#4 - Caching the response in REST API's

Caching in spring boot app: Caching can be used to provide a performance boost to your application users by avoiding the business logic processing involved again and again, load on your DB, requests to external systems if the users request data that's not changed frequently Different types of caching: We'll be focusing more on in-memory caching in this post i listed other options available to have an idea. In-memory caching You'll have a key-value data stores that stores the response of the request after it is served for the first time There are multiple systems like Redis, Memcached that do this distributed caching very well By default Spring provides concurrent hashmap as default cache, but you can override CacheManager to register external cache providers. Database caching Web server caching Dependencies needed: Maven < dependency > < groupId > org . springframework . boot </ groupId > < artifactId > spring - boot - starter - cache ...

Rake's Artifacts

Search This Blog