Newbie: orion-application.xml in both deployment and applications dirs

Okay,
I am using OAS 10.1.2.2 and have deployed an OC4J instance with a web application. The web application that I deployed (from a .war file) was installed normally but for some reason I have an orion-application.xml file in both the +/application-deployments/webappname/+ and the +/applications/webappname/META-INF/+ directories. They look almost identical with the differences noted below:
applications directory version:
This file has a complete definition for the jazn provider but is missing a reference to the principals.xml file.
jazn section looks like this:
     <jazn provider="LDAP" location="ldap://ldap.server.edu:389">
          <property name="ldap.user" value="cn=username" />
          <property name="ldap.password" value="!password" />
          <property name="ldap.cache.session.enable" value="false"/>
          <property name="ldap.cache.realm.enable" value="false"/>
          <property name="ldap.cache.policy.enable" value="false"/>
          <property name="jaas.username.simple" value="true" />
          <jazn-web-app auth-method="SSO"/>
     </jazn>
application-deployments directory version:
It points to a principals.xml file and gives a generic definition for the jazn provider (specifies provider="LDAP" and a default-realm but no location attribute in the jazn tag).
jazn section looks like this:
     <jazn provider="LDAP" default-realm="whidbey1">
          <jazn-web-app auth-method="SSO"/>
          <property name="jaas.username.simple" value="true" />
     </jazn>
I assume the one defined in the +/applications/webappname/META-INF+ is the proper one since it has all the detailed OID connection information. However, are both needed? If so, why? If not, which one is being used and why would there be two of them?
I've checked all the documentation and have found several references to it being installed in one or the other place but not both.
Any help you can provide would be much appreciated.

Hi,
The difference between these files is this:
The one in the applications/ tree is the one that comes packaged in your ear file. This is a way to package your deployment preferences. At deployment time, enterprise manager extracts this file to configure your deployment.
The one in the application-deployments directory is the one that is actually in use.
LDAP connection from OC4J containers is specified on the container level, because this is container-level security. This means that using the enterprise manager, you configure your container to connect to the LDAP (enterprise manager, tab administration, item Identity Management). In the orion-application.xml, you no longer need the details because they are stored on container level. So these are removed when deploying your application, leaving only what you see.
The configuration parameters you specify can be added as container startup parameters using -Dparam=value.
Regards,
Jeroen van Veldhuizen

Similar Messages

  • Use Sign.xml and Encrypt.xml for both request AND response within WSDL?

    Hi,
    ALSB: 2.6
    I was wandering if it's possible to use abstract outof the box WS-Policy file within WSDL file to specify encryption
    (Encrypt.xml) and digital signature(Sign.xml) with X509 for both request and response???
    So far, it only works for either request or response BUT not both. i.e. within WSDL file
    <!-- following WSDL works for encrypting and signing request with X509 in test console -->.....
    <wsdl:binding name="DexService2Soap" type="tns:DexService2Soap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
        <wsdl:operation name="Message">
                <soap:operation soapAction="urn:moe:dex:dexservice:2.0.0/Message" style="document" />
                              <wsdl:input>
                               <!-- WS-Policy file applied here -->
                             <wsp:Policy>
                                            <wsp:PolicyReference URI="policy:Sign.xml"/>
                                            <wsp:PolicyReference URI="policy:Encrypt.xml"/>
                                       </wsp:Policy>
                                     <soap:body use="literal" />
                               </wsdl:input>
                             <wsdl:output>
                                  <soap:body use="literal" />
                               </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
               Or
    <!-- following WSDL works for encrypting and signing response with X509 in test console -->
    <wsdl:binding name="DexService2Soap" type="tns:DexService2Soap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
        <wsdl:operation name="Message">
                <soap:operation soapAction="urn:moe:dex:dexservice:2.0.0/Message" style="document" />
                              <wsdl:input>
                                     <soap:body use="literal" />
                               </wsdl:input>
                             <wsdl:output>
                                       <!-- WS-Policy file applied here -->
                                       <wsp:Policy>
                                            <wsp:PolicyReference URI="policy:Sign.xml"/>
                                            <wsp:PolicyReference URI="policy:Encrypt.xml"/>
                                       </wsp:Policy>
                                  <soap:body use="literal" />
                               </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
    But not both
    <!-- following WSDL doesn't work for encrypting and signing both response and request with X509 in test console -->
    <wsdl:binding name="DexService2Soap" type="tns:DexService2Soap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
        <wsdl:operation name="Message">
                <soap:operation soapAction="urn:moe:dex:dexservice:2.0.0/Message" style="document" />
                              <wsdl:input>
                                        <!-- WS-Policy file applied here -->
                                       <wsp:Policy>
                                            <wsp:PolicyReference URI="policy:Sign.xml"/>
                                            <wsp:PolicyReference URI="policy:Encrypt.xml"/>
                                       </wsp:Policy>
                                     <soap:body use="literal" />
                               </wsdl:input>
                             <wsdl:output>
                                       <!-- WS-Policy file applied here -->
                                       <wsp:Policy>
                                            <wsp:PolicyReference URI="policy:Sign.xml"/>
                                            <wsp:PolicyReference URI="policy:Encrypt.xml"/>
                                       </wsp:Policy>
                                  <soap:body use="literal" />
                               </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
    ...      Instead, I got error message like
    <15/01/2008 10:15:04 AM NZDT> <Error> <ALSB Security> <BEA-387023> <An error ocurred during web service security inbound response processing [error-code: Fault
    , message-id: 3917705281899426819-4368b1eb.117762cff6e.-7fdb, proxy: DexServiceX509-Stub/Proxy Services/DexServiceX509-ProxyService, operation: Message]
    --- Error message:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode>
    <faultstring>Failed to get token for tokenType: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3</faultstring></soapenv:Fa
    ult></soapenv:Body></soapenv:Envelope>
    weblogic.xml.crypto.wss.WSSecurityException: Failed to get token for tokenType: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#
    X509v3
    at weblogic.xml.crypto.wss.SecurityBuilderImpl.addEncryption(SecurityBuilderImpl.java:308)
    at weblogic.wsee.security.wss.SecurityPolicyDriver.processConfidentiality(SecurityPolicyDriver.java:280)
    at weblogic.wsee.security.wss.SecurityPolicyDriver.processOutbound(SecurityPolicyDriver.java:75)
    at weblogic.wsee.security.wss.SecurityPolicyDriver.processOutbound(SecurityPolicyDriver.java:64)
    at weblogic.wsee.security.WssServerHandler.processOutbound(WssServerHandler.java:86)
    Truncated. see log file for complete stacktrace
    >
    <15/01/2008 10:15:24 AM NZDT> <Error> <com.bea.weblogic.kernel> <000000> <Failed to build CertPath
    java.security.cert.CertPathBuilderException: [Security:090603]The certificate chain is invalid because it could not be completed. The trusted CAs did not inclu
    de CN=x509,OU=x509,O=x509,L=Wellington,ST=Wellington,C=NZ.
    at weblogic.security.providers.pk.WebLogicCertPathProviderRuntimeImpl$JDKCertPathBuilder.engineBuild(WebLogicCertPathProviderRuntimeImpl.java:669)
    at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194)
    at com.bea.common.security.internal.legacy.service.CertPathBuilderImpl$CertPathBuilderProviderImpl.build(CertPathBuilderImpl.java:67)
    at com.bea.common.security.internal.service.CertPathBuilderServiceImpl.build(CertPathBuilderServiceImpl.java:86)
    at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
            Truncated. see log file for complete stacktrace
    >
    <15/01/2008 10:15:24 AM NZDT> <Error> <ALSB Security> <BEA-387022> <An error ocurred during web service security inbound request processing [error-code: Fault,
    message-id: 3917705281899426819-4368b1eb.117762cff6e.-7fd8, proxy: DexServiceX509-Stub/Proxy Services/DexServiceX509-ProxyService, operation: null]
    --- Error message:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><soapenv:Fault xmlns:wsse="http://docs.oasis-open.or
    g/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><faultcode>wsse:InvalidSecurityToken</faultcode><faultstring>Security token failed to validate. weblo
    gic.xml.crypto.wss.SecurityTokenValidateResult@3c5347b[status: false][msg [
      Version: V1
      Subject: CN=x509, OU=x509, O=x509, L=Wellington, ST=Wellington, C=NZ
      Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
      Key:  Sun RSA public key, 1024 bits
      modulus: 13052787793731294943682394984664645854838424340012907077330623....
      The 'System Error Handler' from 'Invocation Trace' in ALSB test console is something like
    [pre]     
    $fault:
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
         <con:errorCode>BEA-386201</con:errorCode>
         <con:reason>
              A web service security fault
              occurred[{http://schemas.xmlsoap.org/soap/envelope/}Server][Failed
              to get token for tokenType:
              http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3]
         </con:reason>
         <con:details>
              <err:WebServiceSecurityFault
                   xmlns:err="http://www.bea.com/wli/sb/errors">
                   <err:faultcode
                        xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
                        soapenv:Server
                   </err:faultcode>
                   <err:faultstring>
                        Failed to get token for tokenType:
                        http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3
                   </err:faultstring>
              </err:WebServiceSecurityFault>
         </con:details>
         <con:location>
              <con:path>response-pipeline</con:path>
         </con:location>
    </con:fault>
    So is this a feature not supported in ALSB 2.6 yet or am I missing something dead simple?
    Thanks in advance
    Sam

    Instead of specifying policies for input and output separately you could place the policy reference only once in the operation element. Maybe will this solve your problem...
    http://e-docs.bea.com/alsb/docs26/security/ws_policy.html#wp1061166

  • Orion-web.xml access-mask not working

    Hi, I am trying to restrict access to a specific application via the orion-web.xml descriptor. This would be OC4J in OAS 10.1.3.4.
    I have done this in the GUI by using the "Advanced Deployment Plan Editing -> Edit Deployment Plan" option. I thought this would be safer than editing the files by hand. The application deploys successfully, and in orion-web.xml of my deployed application, this translates into:
    <orion-web-app
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-web-10_0.xsd"       
            deployment-version="10.1.3.4.0"
            deployment-time="1241707803607"
            jsp-cache-directory="./persistence"
            jsp-cache-tlds="standard"
            jsp-taglib-locations=""
            temporary-directory="./temp"
            context-root="MyApp"
    schema-major-version="10" schema-minor-version="0" >
            <access-mask default="deny">
                    <ip-access  ip="127.0.0.1" mode="allow" netmask="255.255.255.255" />
                    <ip-access  ip="192.168.0.100" mode="allow" netmask="255.255.255.255" />
                    <ip-access  ip="192.168.0.101" mode="allow" netmask="255.255.255.255" />
            </access-mask>
            <!-- Uncomment this element to control web application class loader behavior.
                    <web-app-class-loader search-local-classes-first="true"  include-war-manifest-class-path="true" />
            -->
            <resource-ref-mapping name="jdbc/myDB" location="jdbc/myDB" />
            <web-app>
            </web-app>
    </orion-web-app>This looks OK to my eyes, but unfortunately it doesn't restrict any access at all. I have restarted the specific application, and I have also restarted the entire OC4J. No access is restricted; I can pull up the application from any IP address. My intention was to restrict access only to the 2 IP addresses (and localhost by IP) listed above.
    I have reviewed multiple metalink articles on this topic:
    Note 438493.1 - How to Restrict access for EM Database Control only from Specific Hosts / IPs
    Note 178665.1 - How to Restrict Access to OC4J to Specific Hosts or IP Addresses
    Note 311137.1 - How to restrict access to EM website based on IP Addresses/Domain Names
    None of them seem to indicate that I have done anything wrong.
    If anyone has any feedback on this topic, identifies a problem with my config, or has knowledge of a product bug, please respond to this thread.
    Many thanks in advance for your feedback.

    were you able to resolve this?

  • Integrating orion-application.xml deployment with JDeveloper?

    Hi all,
    I am trying to create JAAS secured web/ear application but haven't found the
    way to integrate the orion-application.xml file in the JDeveloper
    deployment process. An alternative would be to insert orion-application.xml tags
    into orion-web.xml and copy this one to the usual WEB-INF along with web.xml
    another possibility would be directly copying orion-application.xml to the
    %J2EE_HOME%\application-deployments\MyApp\orion-application.xml after deployed
    in the OC4J Server, but would be lot easier just having JDeveloper deploy it
    automatically, what is the way to do it?
    Regards,
    Giovanni

    See http://forums.oracle.com/forums/message.jsp?id=978411&gid=315684

  • OC4J orion-application.xml - elements and attributes

    Hi. i read in oracle docs sentense like this: "Each property maps to an element attribute in the orion-application.xml descriptor." These properties are from deployment plan and i need to know what is the name of the element in orion-application.xml wich is mapped to webSiteBinding property (from deployment plan).

    I just did a quick test of this, and it seems to work for me.
    I used the following XML:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <Employees xmlns="
    http://www.foo.com/Employees">
    <Employee Id="001">
    <LastName>Davis</LastName>
    <FirstName>Kirk</FirstName>
    </Employee>
    <Employee Id="002">
    <LastName></LastName>
    <FirstName>James</FirstName>
    </Employee>
    <Employee Id="003">
    <FirstName>Anthony</FirstName>
    </Employee>
    <Employee>
    </Employee>
    </Employees>
    With the XPath "/Employees/Employee" I got rows in the data
    set and things displayed fine in my page. Changing it to
    "/employees/employee" caused the data set to have no rows which I
    would expect since things should be case sensitive.
    Can you provide me with some sample XML and XPath that
    doesn't work?
    Thanks!
    --== Kin ==--

  • Orion-application.xml gets overwriten when deploying with admin_client.jar

    Hi,
    I am trying to deploy an ear in OC4J 10.1.3.3.0. The ear contains a META-INF folder with a application.xml and a orion-application.xml files.
    When running the admin-client command line, the deployment overwrittes the orion-application.xml file.
    I really don't know how to solve this problem.
    What else could I do?

    Greetings,
    The file orion-application.xml is an oc4j-specific file. If you do not create this yourself it will be created during deployment of your application.
    Reference for additional information:
    "OCA Oracle Application Server 10g Administrator Exam Guide"
    This is an Oracle Press book and treats the topic very thoroughly.
    -Michael

  • Customized orion-application.xml

    Configuration:
    Jdeveloper 9i Release 2 Production Version
    I have a customized orion-application.xml file under <project-directory>/src/META-INF directory. I would like to package this along with my application.
    How do I include it in my Deployment Profile (.ear)?
    TIA,
    Ranga

    Another OTN thread on this topic:
    http://forums.oracle.com/forums/message.jsp?id=988554
    The middle of that thread (read the beginning to get the full context) has an answer relevant to your question here.
    ------ begin quoted --------------------------------------------------------------------
    Hello,
    JDeveloper 9.0.2 is limited in this area unfortunately. For the use case you are describing, there are two work-arounds:
    1) Use an Ant build file (or any other script) as you mentioned.
    2) Do your testing in the embedded OC4J server instead of an external OC4J server. You should then be able to make manual changes to the orion-application.xml file used by the embedded server -- it's in the Workspace directory and has a name like "Workspace1-oc4j-app.xml".
    We were expecting users to use Oracle Enterprise Manager (OEM) to configure production J2EE applications, since JDeveloper is a development tool whereas OEM is the real server administration tool. For some time, we've debated internally on the JDev team whether that kind of feature separation across Oracle products makes sense. It's clear that developers like you need to perform some administration tasks in the course of testing a production app, so we focused on allowing that for JDeveloper's integrated OC4J server ("embedded OC4J") and left the administration of an external OC4J server to OEM.
    For future JDeveloper releases, we will probably have an increasing level of direct support for OC4J administration, but to what extent we will pursue that is still in discussion.
    For 9.0.3, I've filed bug 2392697 to track the issue you are reporting (with reference to this OTN thread) to make sure that it is resolved properly for the 9.0.3 release.
    ------ end quoted -----------------------------------------------------------------------

  • Autocreate-tables="false" orion-application.xml

    using oc4j standalone(9.0.3). CMP2.0. jeveloper(9.0.3).
    The jdeveloper Domain UML entity diagram and generated
    entity beans are deployed with default tables generated. The EJB2.0 Dev Guide(9.0.3), says to copy the generated orion-ejb-jar.xml from the deployment directory to the source meta-inf directory to prevent the tables from being re-genrated in the database. However the EJB2.0 Howtos say to set autocreate-tables="false" in orion-application.xml to do this.
    Do I need the orion-application.xml file in the application ear file in addition to the orion-ejb-jar.xml? So far I've been able to deploy and run without any orion files, and I would rather keep them to a minimum

    "Self I said..."
    Got frostbite waiting for a reply. I tried deploying
    with just the orion-ejb-jar.xml in the application ear file. Table were not created, so it looks like I can go with just one orion file for now. I can leave the orion-application.xml with autocreate=false, out of the ear file, for now anyways.

  • Orion-application.xml

    I am packaging an application for deployment. Using JDeveloper, I created an orion-application.xml and it was placed in src/META-INF. When I deploy to an ear file, I see that my orion-application.xml is packaged. However, when I deploy it to my stand-alone OC4J instance, a new, default orion-applicaiton.xml is created and mine is nowhere to be found. I see no errors reported in any of the logs about any possible syntax errors with mine. Anyone know what I may have done wrong? Thanks!

    Did you check how the EAR was formed by your JDeveloper? There should be an orion-application.xml file with in META-INF dir starting from the root of your ear file check for this.
    Any how when it you deploy to standalone oc4j, it modifies your packaged orion-application.xml file a little bit i.e it addes the items to it and then deployes.
    The items that gets added to orion-application.xml before it gets deployed is as follows.
    <namespace-access>
              <read-access>
                   <namespace-resource root="">
                        <security-role-mapping>
                             <group name="jazn.com/administrators"/>
                        </security-role-mapping>
                   </namespace-resource>
              </read-access>
              <write-access>
                   <namespace-resource root="">
                        <security-role-mapping>
                             <group name="jazn.com/administrators"/>
                        </security-role-mapping>
                   </namespace-resource>
              </write-access>
         </namespace-access>
    </orion-application>
    -Mallik

  • Orion-application.xml location

    Hi,
    I am building an EAR file in JDeveloper 10.1.3.4 and then deploying it on 10G server. I need to add the orion-application.xml file to my EAR file. Where should I put it relatively to the home directory of my web application?
    This file already exists on the server in application-deployments/<app_name> directory, however it was copied there manually.
    thanks in advance

    You have to put it in the META-INF of the EAR. The directory where the application.xml resides.
    --olaf                                                                                                                                                                                                                   

  • Setup meta-inf/orion-application.xml through jdeveloper

    Hi,
    I have a bc4j application. I don't want to use the default orion-application.xml file.
    I created a new one and put that under a new folder named meta-inf.
    In project properties, I created a new file groups named meta-inf and defined my new meta-inf folder.
    when the project gets deployed, doesn't have my custom orion-application.xml file.
    it is still using the default one.
    Any idea?
    thanks,
    Setare

    Hi,
    you can only have one orion-application.xml in a project and it need to be in the specified location. You can change the default with your file, but this is what you can do.
    If you don't believe, open the deployment profile of your application, which is the part creating teh WAR and EAR file, and add a new File Group pointing to this directory (note that the directory must be under the SRC folder of the project
    Frank

  • Application Deployment and Data Source

    I have a application and I am using data source for connection to database.
    When I deploy to the application server, it is not taking the data source name defined in the apps server. I use the same data source name defined in the apps server.
    Following is my orion-application.xml properties. Could some one tell what could be the problem or am I missing something?
    ******XML Properties*****
    <?xml version = '1.0'?>
    <!DOCTYPE orion-application PUBLIC "-//ORACLE//DTD OC4J Application runtime 9.04//EN" "http://xmlns.oracle.com/ias/dtds/orion-application-9_04.dtd">
    <orion-application deployment-version="9.0.4.1.0" default-data-source="jdbc/ProdCoreDS" treat-zero-as-null="true">
         <web-module id="HR_W" path="HR_W.war"/>
         <persistence path="persistence"/>
         <principals path="principals.xml"/>
         <jazn provider="XML" location="jazn-data.xml"/>
         <log>
              <file path="application.log"/>
         </log>
         <namespace-access>
              <read-access>
                   <namespace-resource root="">
                        <security-role-mapping>
                             <group name="jazn.com/administrators"/>
                        </security-role-mapping>
                   </namespace-resource>
              </read-access>
              <write-access>
                   <namespace-resource root="">
                        <security-role-mapping>
                             <group name="jazn.com/administrators"/>
                        </security-role-mapping>
                   </namespace-resource>
              </write-access>
         </namespace-access>
    </orion-application>

    Sorry, but this can be loads of different reasons, e.g. type-o's, application property files, wrong data-source definition, etc. Can't you get any clues from standard out en standard error logs of the container?

  • 10.1.3 - OEM Deployment generating invalid orion-web.xml

    Hi,
    I've playing around with OracleASjms resource adapters, JMS Connector, etc - with some good results. I noticed that one of my test applications, when deployed (via OEM) gets an orion-web.xml which is not according to the XML schema and am wondering whether this is designed behavior.
    In my servlet I'm using some logical names for javax.jms.ConnectionFactory and javax.jms.Destination, which I specify in the web.xml. Deploying the ear file I get the change to resolve environment references to 'physical' JNDI locations. I map the logical javax.jms.ConnectionFactory to an OracleASjms resource adapter connection factory (which in turn is pointing to an JMS ConnectionFactory) and the javax.jms.Destination I map to an OracleASjms Administered resource.
    The applications deploys and works fine, however I have a question with respect to the orion-web.xml that Oracle is generating based. More specifically I see (<....> are replaced with actual values):
       <message-destination-ref-mapping
             name="<logical name>"
             location="<OracleAsjms/Administerered Object>"/>The element message-destination-ref-mapping isn't declared in the XML schema for orion-web.xml, but still it works, how come?

    http://www.oracle.com/technology/oracleas/schema/index .html
    http://www.oracle.com/technology/oracleas/schema/orion-web-10_0.xsd
    Thanks, jvissers. It seems that orion-web-10_0.xsd is outdated. It is probably that it was posted for the 10.1.3 preview. When the 10.1.3 production release is available, at least that schema is not updated. Hmm, all things that are changing but kept at different places are just very susceptible to inconsistency. Hmm, OracleAs team should probably make automated tests to make sure that they are in sync. (I am just thinking loudly). Let me try to communicate to someone who can further take care of this matter of outdated schemas. Thanks again, jvissers.
    Where did you look?Inside my oc4j installation! oc4j will not go to the web to download the oc4j-specific schemas in case of need. The orion-web-10_0.xsd is at OC4J_HOME/j2ee/home/lib/schemas.jar!META-INF/orion-web-10_0.xsd. That is where I looked. So the orion-web.xml generated by OEM is indeed valid.

  • Best Practice to Setup an application to work with both oracle and db2 db

    Hi,
    We have an application that currently supports both oracle and db2 databases . It is currently using JPA with eclipselink as backend mechanism and we want to move to ADFBc as our backend . So what is best practice to do this?
    I came across an old post in https://groups.google.com/forum/#!topic/adf-methodology/UlJZSTu14Io that states to create two different model projects to support oracle and db2 .
    Is this still the standard ? Is there a way that we could work around rather than creating multiple projects?
    How do i get the view controller to work with multiple model projects if this is the case?
    Thank you.

    Thanks for the response .
    The problem is i would have the same schema on both the databases (both in oracle and db2) .
    I don't see a scenario where i want both the application model projects at the same time . What i meant is , Application will either be deployed with Oracle DB or DB2 but not with both on a production environment .
    So is there a way where i just change the connection parameters alone rather having two different models ?
    If i have to use two model projects ,  would it be possible say i built the view controller for Oracle , and use it for DB2 if i make sure the BC objects names are similar between model projects and switch just the model jar based on the deployment environment ?
    -Sam

  • Data source for application using both pooled and non pooled connections

    Hi guys.
    I am integrating Oracle's connection pooling into an existing application that had formerly used dbConnectionBroker. It looks like this task should be quite straightforward. However, for consistency, I would also like to replace other Connection logic within the application to use Oracle classes. This will involve using OracleDataSource to obtain a Connection object. ( without pooling ).
    So in this case, the application will use both pooled and non pooled Oracle connections. They will be connecting to the same database. The question I have is in regard to the use of data-sources.xml.
    Are there any special considerations for the required attribute values within data-sources.xml under this scenario ?
    Help will be greatly appreciated.
    Regards.
    Steve.

    Hi Steve -
    It should be feasible for you to define a single datasource using multiple location entries to indicate what sort of pooling behaviour you wish to use.
    If you lookup and use the "location" attribute, you will receive a javax.sql.DataSource object which will not provide connection pooling.
    If you lookup and use the "ejb-location" attribute you will receive a DataSource object that will support connection pooling operations.
    Note that this is using the emulated datasource approach, and transaction support is limited to a single resource (one database) for these datasources - you won't get 2PC support for transactions.
    If you need a transaction to span two separate resources (ie two databases in same tx) then you will need to use the non-emulated datasource approach.
    There is a chapter in the J2EE Services Guide which describes the datasource model we have with OC4J. This might provide you with some more useful information. See Chapter 11 - http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/a97690/ds3.htm#1004903
    cheers
    -steve-

Maybe you are looking for