Introduction It seams to be a lot of interest about my previous article, regarding Oracle JET optimization techniques. In this second post of the same journey I would like to continue with the optimization. As I mention in the previous article it is possible by using the Require JS Optimizer, to reduce the requests to […]
Introduction In my last article, I shown you how you could run a Node project using Oracle JET. In this post I would use the project as a basis and talk about another interesting topic, optimization. There are many aspects how HTML based client-server applications should be optimized, but mostly comes down to two key […]
Introduction Now that Oracle JET is released, you may look for simple way to start playing with the framework, not only on the UI side but also using some mock-up REST APIs and probably build something more realistic. In this article I would like to show you a simple way to use Oracle JET in […]
Introduction This articles promotes the paper published by A-Team which steps you through the development lifecycle of a sample task flow in WebCenter Portal Builder. The document shows how to develop and test a task flow in JDeveloper, then describes how to deploy, redeploy, and use the task flow in WebCenter Portal, as well as […]
Unable to See Coherence MBean in Enterprise Manager Configured for WebCenter Portal Content Presenter
Introduction After configuring Coherence Cache for WebCenter Portal Content Presenter customer was not able to see the Coherence MBeans in the Enterprise Manager. Futher investigation revealed that the issue was due to configuration in WebLogic Server. Main Article After configuring Coherence Cache for WebCenter Portal Content Presenter customer was not able to see the Coherence […]
Introduction During performance tuning it was noticed that SSL Handshake was taking place for each static request. Further investigation revealed that the problem was due to OHS SSL configuration, which unfortunately by default is wrongly included when OHS was installed. Main Article During performance tuning A-Team identified that in same cases SSL handshake was required […]
Introduction WebCenter Portal defines default parameters for portlets usage, which are very well suited for most of the cases. If the portal is under high load or performance test, portlets consumed from the portal could throw intermittently unavailable exceptions. In the portal log error message states that the queue is full and the pool is not […]
Introduction Performance Analysis of a Portal application is an area that is usually time consuming, since the typical portal is made up of numerous distinct task flows. The traditional approach relies on testing task flows in isolation and trying to gauge the performance impact each task flow makes to a page. With WebCenter Portal 18.104.22.168 […]
This guide aims to give you complete configuration overview for how to configure Coherence Cache for Oracle WebCenter Portal Framework Application using the Content Presenter Task Flow.
This document is intended for WebCenter Portal Application administrators who have to improve performance by configuring Coherence cache for Content Presenter.
For more information about the Coherence Cache for Content Presenter have a look at the following link:
The Content Presenter and the Content Management Interoperability Service (CMIS) are delivered out of the box with in-memory Coherence cache. This cache is NOT enabled by default. You can enable it by adding the file content-coherence-cache-config.xml to the application class path of the WebCenter Portal Application. This guide describes how to configure the cache when you deploy applications based on WebCenter Portal Framework.
The Content Coherence Configuration file below uses the distributed cache mode in combination with local cache mode depending on the type of objects to be cached. Here the example Coherence cache file to use for the configuration:
<!DOCTYPE cache-config SYSTEM “cache-config.dtd”>
The cache entries are described in the following documentation:
NOTE: You have to put this file into the application classpath. If you use the file in the managed server class path or node manager class path it will NOT work.
Step by Step Installation Process
Step 1: Create JAR file with the Coherence Cache Config file
Create JAR file which contains the example content-coherence-cache-config.xml shown above. For how to create JAR files follow the tutorial from the Java documentation here:
You will use this JAR file to put it inside your WebCenter Portal Framework Application. As mention above this works only if this JAR file is part of the WebCenter Portal Framework Application class path.
Step 2: Create WebCenter Application EAR Lib folder
To put the created JAR file into the APP-INF/lib you have to update your project settings:
·From the JDeveloper WebCenter Portal Application Project click on Application->Application Properties.
·From the new window select Deployment. From the deployment profile select the EAR profile you want to use and then click on Edit button.
· From the new window select File Groups and then click on New button. From the new opened window select Packaging and type a name for the file group as shown bellow. Then click OK to add your new packaging file group. Click then OK again the save the changes.
·Create the APP-INF/lib folder into your project. Go to the file system where you create the WebCenter Portal Application Project as shown bellow
·<!–[endif]–>You have to create the APP-INF/lib folder under the src/ folder:
·<!–[endif]–>Inside the newly created APP-INF/lib folder you can place your JAR file with the Coherence Cache configurations.
·<!–[endif]–>To make sure that the file will be picked go back to JDeveloper and open the Application Properties again by clicking on Application->Application Properties and then click on Deployment. Select the EAR Profile which you used to add the Packaging File Group and click on Edit button. Inside the new window you should see that your APP-INF/lib folder is selected and inside there, there is also the JAR file you copied.
·<!–[endif]–>WebCenter Portal Framework Application is ready for deployment now. Redeploy your application and bounce(load your application one in an browser) to make sure that the configurations are loaded.
Step 3: Check your configuration
NOTE: You have to open your application once to make sure that the Coherence Configuration is loaded.
Make sure that you open the application once in the browser then open your <managed_server>_diagnosting.log file and search for coherence inside. If you see message like this:
[APP: AviTrustSamplePortal#V2.0] Unable to load Coherence configuration file content-coherence-cache-config.xml. Using in-memory (local) caches.
… then it means that your application did not find the configuration file. The reason for that is that the JAR file was not inside the application classpath. In this case you may used the Managed Server Classpath which is not working. You have to place the JAR file inside the application classpath as described above.
If you don’t see the message above you can go for the next step and look for the Coherence configuration inside the MBean.
To do so open your Enterprise Manager and go to the application configuration like shown bellow:
Then from the Application Deployment click on the System MBean Browser to have a look in the MBeans. Inside the MBean Tree search for the word <coherence>:
You should be able to see the configurations as shown above.
Another very good why to check if the cache works is to have a look inside the WCC request audit. It shows if queries were fired against the Content Server.
To do so login as Administrator to WCC.
After you login in as administrator select System Audit Information and from the Active Sections select only system and requestaudit as well as Full Verbose Tracing checkbox.
Click on Update button to update the configuration.
After that click from the upper right menu on View Server Output to trace the Content Presenter queries to the Content Server.
If you open a example page where the content presenter is used, like this:
You can see after that in the audit log the queries used by the content presenter to get the information:
Refresh the page by click on F5 or just the browser refresh button. There’re should be no new queries visible in the audit log anymore, since the content presenter should use the coherence cache now:
Step 4: Configuration for Cluster Environment
If you run your application in cluster environment you have to make sure that the coherence configuration works inside the cluster. If you have two managed servers in one cluster you can configure following parameters in the startup arguments. If Node Manager is used to start the Managed Servers, you can put the argument in the Server Start argument option.
NOTE: If the two server are running on the same physical machine, you have to make sure that they use different ports.
My college Yannick already wrote very good article about how to configure Java Object Cache in clustered environment you can find HERE.
There are two things on top of that, I would like to share regarding the Java Object Cache: which managed server needs JOC and the second one is how to verify if JOC is running.
The documentation section here, says that the JOC should be configured on all servers running Oracle Web Service Manager OWSM and Oracle WebCenter Portal’s Spaces application. The tricky part here is where the OWSM runs. The application you have to look after in your WebLogic Administration Console is the “wsm-pm”
If you click on the application and then go to the target tab…
…you will see there all managed servers targeting this application. Those are the servers for which you have to configure JOC. By default the wsp-pm does not runs on all those servers but only on the utilities, spaces and custom portal. If you want to secure web services from other custom application or existing web services like for example from UCM, you have to target this application to the according managed server which runs the application. After that you would need to extend your JOC configuration to cover this server as well.
Next important step is how to validate that the JOC runs?
First option will be to have a look inside the diagnostic log file from your managed server (<managed_server_name-diagnostig.log>) and search inside for JOC. After you configure JOC you have to restart the managed servers and you should see something like that:
[2013-03-14T14:17:57.685+01:00] [WC_CustomPortal] [NOTIFICATION]  [oracle.as.cache.Lifecycle] [tid: [STANDBY].ExecuteThread: ‘2’ for queue: ‘weblogic.kernel.Default (self-tuning)’] [ecid: 0000Jpd36SXFw000jzwkno1HGSrd000002,0] [APP: wsm-pm] JOC is initialized from oracle.mds.internal.cache.JOCCacheProvider.createNamedCacheInternal, ver=22.214.171.124.0, distribute=true, vid=1, coordinator=0, discover list=[[localhost:9991] segID=1, SSL]
This message appears only if the wsm-pm application targets the managed server into which log file you look.
Another possibility to verify the JOC is to use CacheWatcher as described HERE. The issue here is that the ORACLE_HOME is not clear to everyone, since there is also modules folder inside the middleware folder. If you as classpath the middleware modules folder, you will get following error message:
Exception in thread “main” java.lang.NoClassDefFoundError: oracle.ias.cache.CacheUtil
In that case, make sure that your classpath goes to oracle_common/modules folder, to get this running:
./java -classpath “/u01/app/oracle/product/Middleware/oracle_common/modules/oracle.javacache_11.1.1/
oracle.ias.cache.CacheUtil watch -config=
If you want to learn more about the JOC how it works or how to monitor it, follow this link HERE.