Skip to main content

MDS setting for testing PDef business components using AM tester

In case if you want to test the ADF Model project containing PDef  business components outside of the container using AM tester, you can use the following MDS setting in adf-config.xml. See metadata-path  entry in the below snippet, this entry sets MDS repository path to D:\my_mds_repo. Note that, when you deploy this app as web app, container will not use this path. If you don't know what a PDef object is, see this post http://www.jobinesh.com/2011/08/long-living-dynamic-business-components.html

<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
 <mds-config version="11.1.1.000" xmlns="http://xmlns.oracle.com/mds/config">
  <persistence-config>
   <metadata-namespaces>
    <namespace path="/sessiondef" metadata-store-usage="mdsRepos"/>
    <namespace path="/persdef" metadata-store-usage="mdsRepos"/>
    <namespace path="/xliffBundles" metadata-store-usage="mdsRepos"/>
   </metadata-namespaces>
   <metadata-store-usages>
    <metadata-store-usage id="mdsRepos" deploy-target="true" default-cust-store="true">
     <!-- Note the following entry gets overwritten during deployment -->
     <metadata-store class-name="oracle.mds.persistence.stores.file.FileMetadataStore">
      <property name="metadata-path" value="D:\my_mds_repo"/>
      <property name="partition-name" value="demo"/>
     </metadata-store>
    </metadata-store-usage>
   </metadata-store-usages>
  </persistence-config>
  <cust-config>
   <match path="/">
    <customization-class name="oracle.adf.share.config.SiteCC"/>
   </match>
  </cust-config>
 </mds-config>
</adf-mds-config>

Comments

Popular posts from this blog

How to set Bind Variable Values at runtime ?

In this post I'm sharing a couple of approaches for programmatically setting bind variables values at run time. This post is an attempt to explain 'When to use what ?'[ In case if you are familiar with 'Bind Variables' in ADF BC, please refer Section 5.10, Working with Bind Variables in Fusion Developer's Guide ]

1. Set the Bind Variable value using RowSet::setNamedWhereClauseParam(...)

You can use use the setNamedWhereClauseParam(...) method on the ViewObject interface (which extends oracle.jbo.RowSet) to set the value for bind variables. Please note this sets the value on default RowSet. In other words, this doesn't have any effect on the secondary RowSets that you/system generates.
ViewObject vo = am.findViewObject("EmployeesView1"); vo.setNamedWhereClauseParam("bindVarDeptId", new Number(10)); vo.executeQuery();
2. Set the Bind Variable value using ViewObject's VariableValueManager::setVariableValue(...)

VariableValueManager Ma…

Happy New Year 2018 !

We can't go back and change the beginning, but we always can start where we are and change the ending. Believe in yourself and you will be unstoppable!

Wishing you and your family a very happy new year 2018 !!!