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

Similar Messages

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

  • 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

  • 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

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

  • XML publisher with jdeveloper

    Hi all,
    I'm wondering if there is an API of XML Publisher for using with jdeveloper for development a reporting system. After I have run queries in database, I want to present tuples in a formatted fashion in PDF, RTF document etc. There are open source facilities like jasper reports etc, if XML publisher facilitates my reporting part of my system, I want to plan reporting development via XML Publisher!
    So, How I can integrate XML Publisher with jdeveloper? Is there any API documentation?
    best regards...
    --barisk                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    XML Publisher ships with 2 XDK parsers a 9i version for backward compatibility and 10g version - you can switch at runtim using the properties. However, you have to make sure that the XML Publisher versions of the libraries are used and not the ones coming with i.e. jdeveloper version or oc4j version that you are using. You should use the version shipped with XML Publisher, because these versions are thoroughly tested with XML Publisher.
    See the deployment notes in the install document:
    Oracle OC4J Deployment Notes
    The version of the XML Parser shipped with Oracle OC4J is incompatible with XML Publisher. When you create an XML Publisher application for OC4J you need to configure the system to use the XML Publisher version of the XML Parser. This can be accomplished by setting an orion-web.xml configuration file with the following content:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <orion-web-app>
    <web-app-class-loader search-local-classes-first="true" />
    </orion-web-app>

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

  • Restart of OC4J required ? If orion-application.xml changes

    Hello,
    If i make a change in the orion-application.xml, basically i am interested in changing the JAZN LDAP configuration settings --- do i need to restart the OC4J ?
    If yes, where is this mentioned in the documentation ?
    Does the answer (yes / no) apply to all versions (10g minor versions) of OC4J.
    Please confirm.
    Thanks in advance.
    Warm Regards
    AB

    Hi Deepak,
    I fully agree with you that changes in the orion-application.xml require a restart.
    Infact, when i do that practically, a message is displayed on the OEM console that the changes have been saved to the XML file but for the changes to take effect, i need to restart my container.
    Agreed.
    But where is it specifically mentioned in the official documentation ?
    In the link you forwarded, there is not a single mention about orion-application.xml
    Every statement over there talks about jazn.xml
    I even checked the documentation for orion-application.xml, there too i could not locate that statements like you gave "any change to the jazn configuration (either in jazn.xml or otherwise) will need a restart."

  • Integration of custom identity services with JDeveloper BPEL designer

    Hi,
    I'd like to know if a custom user repository plugin will cause the 'Identity Lookup Dialog' (Step 6 of Human Workflow Wizard to generate a user task) to utilize the list of users and groups from a third party provider, when used as the Custom Identity Service provider.
    I'd like to have the custom list of users and groups at 'design time' of the BPEL process itself, as well as process runtime. Is this possible?
    This is with respect to both BPEL PM v10.2.0.2 and v 10.1.3.1.0.
    Regards,
    Vineet

    ok, thank you for the reply.
    But the installation of the Oracle BPEL Process Manger for Developers which includes the JDeveloper and the BPEL Designer doesn't come with 10.1.3.1.0?
    I have to install the JDeveloper and the BPEL Process Manager seperate?
    Thx

  • Missing data-sources.xml deploying war with jdeveloper 9i RC

    When deploying a war file to an OC4J 1.0.2.2.1 server and error reports during the deployment that data-sources.xml is missing in the application-deployments/xxxx directory. Only the orion-application.xml file is present - which references a data-sources.xml file in the same directory. The problem is : it isn't there.
    When I copy the xml files from the applications/xxxx directory to the application-deployments/xxxx directory and redeploy the war file everything works fine.
    Is this a configuration issue or a bug ? Anyway, can somebody tell me how I can work around this problem ?
    Thanks !

    this is a bug and you have already found the workaround.

  • Orion-ejb-jar ignored by JDeveloper deploying to OC4J

    orion-ejb-jar.xml is ignored by JDeveloper 903 when deploying to external OC4J 903. Specific mappings like those below are lost:
    <entity-deployment name="RequestEJB" copy-by-value="false" data-source="jdbc/OracleDS" exclusive-write-access="false" table="REQUEST">
    <primkey-mapping>
    <cmp-field-mapping name="requestid" persistence-name="REQUESTID" persistence-type="NUMBER(9)"/>
    </primkey-mapping>
    <cmp-field-mapping name="requestid" persistence-name="REQUESTID" persistence-type="NUMBER(9)"/>
    <cmp-field-mapping name="requestuser" persistence-name="REQUESTUSER" persistence-type="VARCHAR2(30)"/>
    <cmp-field-mapping name="requestlabel" persistence-name="REQUESTLABEL" persistence-type="VARCHAR2(12)"/>
    <cmp-field-mapping name="requestdate" persistence-name="REQUESTDATE" persistence-type="DATE"/>
    <cmp-field-mapping name="isurgent" persistence-name="ISURGENT" persistence-type="VARCHAR2(1)"/>
    </entity-deployment>
    Instead, JDeveloper creates a new orion-ejb-jar.xml with different table name:
              <entity-deployment name="RequestEJB" location="RequestEJB" local-wrapper="RequestHome_EntityHomeWrapper421" table="RequestEJB_modulab_Proj_n76ccv" data-source="jdbc/OracleDS" exclusive-write-access="false" locking-mode="optimistic" update-changed-fields-only="true" delay-updates-until-commit="true" min-instances-per-pk="0" max-instances-per-pk="50" disable-wrapper-cache="true">
                   <primkey-mapping>
                        <cmp-field-mapping name="requestid" persistence-name="requestid" />
                   </primkey-mapping>
                   <cmp-field-mapping name="requestuser" persistence-name="requestuser" />
                   <cmp-field-mapping name="requestlabel" persistence-name="requestlabel" />
                   <cmp-field-mapping name="requestdate" persistence-name="requestdate" />
                   <cmp-field-mapping name="isurgent" persistence-name="isurgent" />
                   <finder-method query="">
                        <!-- Generated SQL: "select RequestEJB_modulab_Proj_n76ccv.requestid from RequestEJB_modulab_Proj_n76ccv -->
                        <method>
                             <ejb-name>RequestEJB</ejb-name>
                             <method-name>findAll</method-name>
                             <method-params>
                             </method-params>
                        </method>
                   </finder-method>
              </entity-deployment>
    orion-ejb-jar is placed at the META-INF folder. Why does JDeveloper ignore it? It does not ignore orion-application.xml nor orion-web.xml. Must I configure project or deployment profiles not to overwrite orion-ejb-jar?

    I believe that it is not JDeveloper issue but OC4J one. It does not pick up new orion-ejb-jar.xml if you re-deploy bean(s). It should deploy your orion-ejb-jar.xml when you're deploying yor application for the first time (so there is not orion-ejb-jar.xml in deployments directory). If you want OC4J to pick changes up remove orion-ejb-jar.xml from $OC4J_HOME/application-deployments/<application>/<Bean>.jar/ and then deploy it either manually or with JDeveloper. I hope it will help.

  • Deployment of JDeveloper Application

    Hi Gurus;
    i have a question for u people, first understand the use case:
    1. I have an application developed in Jdeveloper
    2. Application comprises on hundreds of .jspx pages and business components.
    3. Database is used Oracle 11g.
    4. Application is deployed on Weblogic Server.
    Problem :
    A user requests to make some changes in some .jspx form which is currently the part of deployed application. too many users are working with application.
    i make the changes in .jspx form and at this point i want to upload this form in weblogic however the application deployed is packaged. please guide me how i can deploy the new form. is there a need to redeploy the application? if so what will be the status of connected and working users?

    What type of authentication are you using for your application? If you configure the following
    <jazn provider="XML" location="../../config/jazn-data.xml" default-realm="jazn.com" persistence="ALL"></jazn>in orion-application.xml then your users need to exist in the referenced jazn-data.xml file, but it's more usual on 10gAS to configure something like this
    <jazn provider="LDAP">
        <jazn-web-app auth-method="SSO"/>
      </jazn>In which case the users need to exist in the OID.
    Hope this helps a little!
    Matthew

Maybe you are looking for