Code to read the adfc-config.xml parameters from managed bean in ADF

The sample code to  read the adfc-config.xml parameters from managed bean in ADF is as follows

# Get the adf context object and get the config object from there
ADFContext adfContext = ADFContext.getCurrent();
ADFConfig adfConfig = adfContext.getADFConfig();

# Read the details of adfc-config.xml in the form of a MAP
Map configurationMap = adfConfig.getConfigObject("http://xmlns.oracle.com/adfm/config");
Long rowLimit =(Long)configurationMap.get("jbo.row.limit");  

ADF JavaScript Partitioning for better performance

What is JS Partitioning?
By default ADF framework downloads a bunch of Java Script libraries on each page load and we should consider to bucket the JS library calls to reduce the number of calls made. By default all ADF pages need the boot.js and core.js files to operate.

Additionally, JS files are downloaded either combined as partitions or one for each component (if no partition is defined).

Why should we implement it?
ADF is smart enough to download only the javaScripts belonging to the components rendered on the page. If individual JS files are downloaded, however, then there will be lot of network traffic per page, slowing down the page performance. The solution is to use JavaScript Partitions.

How to implement it?
The exact procedure is to create the java script partitions xml file with the name adf-js-partitions.xml file in WEB-INF and configure the partitions as needed. More documentation can be found here

Change the Oracle SOA BPEL properties at runtime

Often it is useful to be able to set properties influencing behavior of a BPEL process after it has been deployed. Of course, a danger with changing settings at runtime is that they also need to be applied to the development branch in order to avoid the changes to be overwritten at redeployment of a process. Oracle provides several mechanisms of changing settings of a BPEL process at runtime.

Implementation details can be found here

How to obtain the list of exposed SOAP HTTP endpoints in OSB

http://javaoraclesoa.blogspot.com/2014/10/oracle-service-bus-obtaining-list-of.html#more

Unable to get the Action Executor [WSM-02353] : AdminServer Log

Error observed in Admin log

AdminServer-diagnostic.log:[2014-07-16T10:40:43.681+02:00] [AdminServer] [ERROR] [WSM-02353] [oracle.wsm.resources.policymanager] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: admin] [ecid: bf57ca3361a7ecd1:-39746f30:1473e26749c:-8000-000000000000026a,0] [APP: em] Unable to get the Action Executor.

Solution

1. Create the user OracleSystemUser
2. Create the Group OracleSystemGroup
3. assign OracleSystemGroup group to OracleSystemUser
4. Restart Console and managed Server Try again.