Skip to main content

WebCenter Portal Framework 11g Application migration to WCP 12c

As we all know Portal Framework Technology, a technical masterpiece which was used to create and deploy Portal Framework Applications was available in Oracle WebCenter Portal 11g and have been removed by Oracle starting 12c release. (12.2.1.0.0).

So this means starting 12c release development of custom portal applications are deprecated. However, most of the WebCenter Portal API's are still supported by Oracle as they are needed to develop custom navigations or taskflows.

With the availability of these API's can i run a 11g application in 12c?
- No and also depends on the features you're using.
- You may be able to run it on server but you can't get it compiled on JDeveloper 12.2.1.x

As Portal Framework Technology have been discontinued also the extension for JDeveloper to support Portal Framework applications development have been removed as well so the applications developed in 11g tend to fail with multiple compilation errors due to missing libraries. There's no official fix from Oracle for this issue as of now. However here's a quick work around I am using to get my Portal Framework App compiled in JDeveloper 12.2.1.x and I also tested this on server and this works fine for me.

Workaround:

   In Brief, the fix is to get the missing jars from 12c server or virtual box provided by oracle and add them to the JDeveloper project. But the JDev will not give you the direct list of libraries missing so you may have to skim through manually or here are few steps of automation I have used:

- Compile Portal and dependent libraries.
- Export the log with compilation errors of missing packages.
- Once you have the log for all projects consolidate the log.
- After consolidation I wrote a shell script to search and copy for jars based on missing package names.
- Once the jars are available copy them to any local or your middleware home folder.
- Add the jars to your project

This should solve your Portal projects compilation issues in JDev 12.2.1.x.

Happy Coding ✌ 😃

Comments

Popular posts from this blog

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...

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 ...

Set BIND VARIABLE and EXECUTE QUERY programmatically in ADF

A very common scenario in ADF is to set a bind variable and execute query programmatically within AMImpl/ VOImpl classes. Here's a simple way to do this: To set bind variable for all rowsets:       ViewObjectImpl someVO = this.getSomeViewObject();       VariableValueManager vMngr = someVO.ensureVariableManager();        vMngr.setVariableValue("DefinedBindVariable",value);        someVO,executeQuery(); To set bind variable for default rowset:          ViewObjectImpl someVO = this.getSomeViewObject();          someVO.setNamedWhereClauseParam("DefinedBindVariable",value);          someVO,executeQuery();