Application.xml file?

What is the use of the Application.xml file in enterprise application> If we not specified it...what will happen?
Thanks,
R.

The application.xml file specifies metadata about the Java EE application as a whole. The main pieces of information are the list of modules(ejb-jar, .war, application client, etc.) in the .ear. It was required for J2EE 1.4 and earlier but is optional in Java EE 5, where the module type is derived based on the contents of the modules themselves.
--ken                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Similar Messages

  • Can I unzip the .ipa file and edit the application.xml file

    I want to modify the below info to also have an additional string value of 2, which somewhere along the line tells something somewhere that the app can run on the ipad. Is there some info in the compiled application that will error out if I modify this document?
    <InfoAdditions>
    - <![CDATA[ <key>UIDeviceFamily</key><array><string>1</string></array> ]]>
    </InfoAdditions>
    into this
    <InfoAdditions>
    - <![CDATA[ <key>UIDeviceFamily</key><array><string>1</string><string>2</string></array> ]]>
    </InfoAdditions>

    you can change the file extension to zip, unzip it, find the application.xml file in one of the subdirectories, edit it, rezip the files, change the file extension to ipa and install.

  • Non-default system-application.xml file?

    There's mention in the OC4J documentation regarding specifying a non-default system-application.xml file; however, I cannot find the string defining it in any of the OC4J files, nor in the documentation though I might have missed it in that.
    I am attempting to have multiple instances run out of the same ORACLE_HOME, and I'd like to point the logs to separate places per instance. Every other one is pretty clear (defined in the customized server.xml), this one with its logging parameter I cannot find a method for keeping a separate log file per instance other than simply creating multiple oracle or at least j2ee homes. Short cut for keeping things consistent for many settings and deployments, though may not be feasible for a running environment.
    Any information or points in the right direction would be appreciated. Thanks,
    Geoff

    You can modify the <log> tag in system-application.xml to rotate the system log file.
    System application is a key internal component that is critical to OC4J startup, the system-application.xml file should not be modified except for the <jazn> and <log> tags.
    You can modify the <jazn> tag as needed to specify changes to the security provider, the location of the OC4J security configuration file (system-jazn-data.xml), or both. For more information about <jazn> and the system-jazn-data.xml file, see the Oracle Containers for J2EE Security Guide.
    There's no reference of system-application.xml in other config files.
    -Frances

  • Air plugin for dreamweaver breaks application.xml file

    the air plugin for  dreamweaver breaks the application.xml file when the version is  changed from 2.0 to 2.7
    How to fix this?

    Hi Roberto,
    I'm sorry I don't know the answer to this one, but I'll ask around.  Have you checked out the dreamweaver forum?
    Chris

  • EAR proects deploys but has no application.xml file!

    Hello,
    I working my through a Web Logic tutorial and the very first step is to create a the application projects like this:
    # Select File > New > Project.
    # In the New Project dialog, open the node Workshop Quick Start Applications and select WebLogic/Beehive Web Application.
    Click Next.
    # In the Application Name field, enter CustomerCare.
    Next to Domain home click the Browse button. Browse to <BEA_HOME>/workshop_10.3/samples/domains/workshop. Click OK.
    Click Finish.
    The applications are create and I can deploy the ear project, but it doesn't contain an application.xml file and I don't understand how this can work. Can someone enlighten me please.

    The applications are create and I can deploy the ear project, but it doesn't contain an application.xml file and
    I don't understand how this can work. Can someone enlighten me please.
    The wizard created three projects: CustomerCare, CustomerCareEAR and CustomerCareSharedCode. I'm assuming
    that the project is being deployed is an EAR.The CustomerCareEAR is an EAR project in your application. The application.xml file will be located in CustomerCareEAR/EarContent directory.
    I'm not entirely sure where the project is getting deployed to. I thought it would be to <BEA HOME>\user_projects,
    but I can't see an EAR or directory structure in there that would suggest that this is the deployment directory.
    As I am deploying the project from within Eclipse it is possible (perhaps) that eclipse is deploying the project directly
    from my workspace - but I can't be sure.The deployment does not use user_projects directory. It happens largely directly from the Eclipse workspace with assistance of a few temporary directories. The structure of deployment is not something that you need to be concerned about.
    If you want to see what the EAR will look like when you are done, export an EAR archive using the wizard under File -> Export. Point the wizard at CustomerCareEAR project.
    - Konstantin
    - Konstantin

  • Editing my application.xml file

    The server hosting our FMS does not have space to adequately store the media files over time.  I have since connected a 500GB external drive to the server.  This drive is mapped as the Z drive.  I am not exactly sure how I need to edit my application.xml for all http requests to point to this external drive.  Below is a small sample of the file.  How would I correctly edit this file?  Would I just add a line that says <Streams>/;${Z:\VOD_DIR}</Streams> ???  Do I need to delete either of the below lines?
    - <Application>
    - <StreamManager>
    - <VirtualDirectory>
    - <!-- Specifies application specific virtual directory mapping for recorded streams.   -->
    <Streams>/;${VOD_COMMON_DIR}</Streams>
    <Streams>/;${VOD_DIR}</Streams>
    </VirtualDirectory>
    </StreamManager>

    It doesn't seem to work.  Does this only apply to rtmp:// ???  Because we are only using http:// to view our media.
    My current application.xml looks like the below.  I can still play all media located in the webroot\vod directory but not from the external drive.  Do I need to delete <Streams>/;${VOD_COMMON_DIR}</Streams> and <Streams>/;${VOD_DIR}</Streams> ???  The Z drive is the external hard drive.  Did I add the entry correctly?
    <Streams>/;Z:\vod</Streams>
    <Streams>/;${VOD_COMMON_DIR}</Streams>
    <Streams>/;${VOD_DIR}</Streams>

  • Application.xml in ear file

    Hi
    When we deploy to ear file the application.xml file is created with the following root tag:
    <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee">
    Previously (Jdev10.1.2) it was created with only:
    <application>
    We are running on an older app server which does not accept the new tag. Any way to set up 10.1.3 to deploy the same tag as the previous version?
    If I manually edit the ear file and change the application.xml file, it runs fine on the older app server. We do not want this manual intervention.
    Thank you

    Does setting a target platform in the deployment profile that points to a 10.1.2 application server works?
    Also you can create a 1.3 application.xml using New->deployment descriptor->J2EE deployment descriptor wizard

  • WebLogic 10.3 , ear file, application.xml only finds first context root

    I just can't find out what this is. I have two web service projects (JAX-WS) and am trying to put them in an .ear file to deploy to WebLogic 10. Normally, this is done by creating an .ear with both projects .war files in it and an application.xml file in the META-INF directory that defines the context-root for each .war file. However, nothing I do for WebLogic 10 seems to work, it only see's the first context-root and sets that same context-root for both web services. I have verified this by switching the order in the application.xml file. Also, this exact same .ear file deploys to the Sun Enterprise Server (Glassfish) and acts correctly. Using a weblogic.xml file in each .war and deploying them individually they end up having the correct context root, just not from an .ear using application.xml. I even tried deleting the application.xml file and just having the weblogic.xml files in each .war define the context root and it still only came up with one context root for both. It's as if only one context root is allowed in an .ear for WebLogic 10, which can't be correct as we are doing this on WebLogic 9.2 (JAX-RPC) with multiple .war files in an ear.

    Hi,
    Try to increase severity of the server logging to avoid more logging.
    Avoid Debugs and and info and better select the severity to notice which will avoid more logging.
    Regards,
    Kal

  • Deploy given EAR file having application.xml and change context-root

    hi
    Please consider deploying a given EAR file on WebLogic Server 10.3.5 (part of JDeveloper 11.1.1.6.0) and changing the context-root for its web-module.
    For example an EAR file with only a web-module (ReviewContextRootFirstApp.ear [1]) or an EAR file with a web-module and an ejb-module (ReviewContextRootSecondApp.ear [2]).
    Given documentation appendix B section "context-root" [3] saying
    "... A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml. ..."
    and documentation section "Typical Deployment Configuration Workflows" [4] saying
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. However, if an application is deployed as a library, you can either change the context-root through an weblogic-application.xml file or use the deployment plan to change the context-root in an weblogic-application.xml file. "
    Some observed behaviour:
    - scenario (sc1) : deploy ReviewContextRootFirstApp.ear without deployment plan, results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc2) : deploy ReviewContextRootFirstApp.ear with deployment plan fa-plan.xml (tries to configure "/rcrfaweb11"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc3) : deploy ReviewContextRootSecondApp.ear without deployment plan, results in context-root "/rcrsaweb" (as in application.xml)
    - scenario (sc4) : deploy ReviewContextRootSecondApp.ear with deployment plan sa-plan.xml (tries to configure "/rcrsaweb21"), results in context-root "/rcrsaweb" (as in application.xml)
    The blog post "Defining the context root of a web application in Oracle WebLogic server" [5] by Silviu Leahu in its section "Defining the context root in deployment plan" suggests to
    "Remove the META-INF/application.xml DD from the EAR"
    - scenario (sc5) : remove application.xml from ReviewContextRootFirstApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan fa-plan.xml, results in context-root "/rcrfaweb11" (as in fa-plan.xml)
    - scenario (sc6) : remove application.xml from ReviewContextRootSecondApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan sa-plan.xml, results in context-root "/rcrsaweb21" (as in sa-plan.xml)
    One could expect that using a deployment plan (like in scenario's (sc2) and (sc4)) would allow to configure/change the context-root, whithout having to make changes to the EAR file to make this possible. (Somewhat like "Figure 4-2 Single Deployment Plan Workflow")
    Only in scenario's (sc5) and (sc6) I see something close to what I would like to achieve, but there the application.xml file has been removed from the EAR file.
    So ...
    - (q1) Is it impossible to change the context-root at deploy-time for a web-module in a given EAR file that includes an application.xml file, without changing the EAR file?
    - (q2) Is working with EAR files that don't have an application.xml file a supported approach (to change the context-root at deploy-time)?
    Seems like a simple goal, but I must be missing something that is required to achieve it.
    - [1] ReviewContextRootFirstApp/deploy/ReviewContextRootFirstApp.ear in the ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [2] ReviewContextRootSecondApp/deploy/ReviewContextRootSecondApp.ear in the (same) ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [3] http://docs.oracle.com/cd/E21764_01/web.1111/e13712/weblogic_xml.htm#WBAPP623
    - [4] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [5] http://blog.leahu.net/it/2011/01/04/defining-the-context-root-of-a-web-application-in-oracle-weblogic-server/
    many thanks
    Jan Vervecken

    Thanks for your reply René van Wijk.
    René van Wijk wrote:
    You can use deployment plans in order to change the context-root ...That is what I tried and describe in scenario's (sc2), (sc4), (sc5) and (sc6) in this forum thread.
    Because the application.xml file (in the "given EAR file"), added by JDeveloper 11.1.1.6.0 when deploying to an EAR file, doesn't have id attributes on its application/module elements, I first tried a different XPath expression:
    "/application/module/web[web-uri/text()="WebProject.war"]/context-root"
    But, that didn't work.
    Although the "given EAR file" does not have the suggested id attributes, I tried adding a deployment descriptor application.xml file that does have such id attributes [2], allowing an XPath expression like the one suggested:
    "/application/module[id="WebProject"]/web/context-root"
    - scenario (sc7) : deploy ReviewContextRootFirstApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan fa-plan-application-xml-with-id.xml (tries to configure "/rcrfaweb14"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc8) : deploy ReviewContextRootSecondApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan sa-plan-application-xml-with-id.xml (tries to configure "/rcrsaweb24"), results in context-root "/rcrsaweb" (as in application.xml)
    So, it does not seem to work.
    ... you have to use a variable assignment in the right part of the deployment plan (in this case the application.xml) ...My observations I describe above (that it does not seem to work) seem to confirm the Oracle documentation [1] I referred to in this forum thread before:
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. ... "
    ... By using an xpath expression, you can define which part of the xml has to be changed. ...The values for the deployment-plan xpath elements seem to be "peculiar".
    Although it should not be a problem in an XPath expression, using single quotes (like module[id='WebProject'] ) instead of double quotes (like module[id="WebProject"] ) results in:
    "java.lang.AssertionError: Attributes must be defined as name value pairs, eg, name="value" -- [id='WebProject']"
    Because an XPath predicate expression would use an "@" to refer to an attribute, I also tried to replace what you suggested module[id="Web"] with something like module[@id="Web"] but that also did not make a difference.
    - [1] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [2] http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.02.zip
    regards
    Jan Vervecken

  • Error-page tag not valid in global-web-application.xml ?

    Hi!
    From what I understand about the global-web-application.xml file in Oracle's documentation, the content of the web-app tag should be inherited to all web application as a web.xml content.
    One of the web.xml tags is error-page, which contains the page url for the standard return codes (404, 500, and so on).
    If I put the error-page on the web.xml inside a web application, it works as expected.
    But if I don't put this tag inside the web applicaction, but in the global-web-applicacion.xml (web-app) tag, it doesn't work.
    We are testing the 404 error page, but I don't know if it is because the application server can't find the error page or because the global-web-application.xml isn't being inherited correctly.
    Where is this file supposed to be looked for? Or the only way to do this is by writing the configuration on all web applications?
    We are using 9.0.3
    Franco Catrin L.
    TUXPAN

    Just refreshing... Does anyone have any idea?
    Daniel.

  • Application.xml over-written when deploying JDeveloper 10.1.3.2

    Hi all,
    I created a Web Application that contains JSF, EJB, and Toplink. I have a ViewController project, a Model project, and a Deployment project. The ViewController obviously contains my JSPs, etc, the Model my EJBs and server code, and deployment profiles for each. The Deployment project contains a deployment profile for creating the EAR file for the other two projects.
    When the EAR is created (or if I deploy to stand-alone OC4J) the application.xml is generated without an module/EJB tag containing my EJB jar. Therefore when the server starts up it does not find any of my EJBs.
    If I manually modify the application.xml in a created EAR file and then deploy it manually, everything works great. So, I tried to create an application.xml file in my Deployment project (and I tried in my ViewController project, too), but it ends up getting over-written and changed to still not have the module/EJB tag. Can someone explain to me how to stop JDeveloper from overriding this file or how to get JDeveloper to include this tag set when creating the application.xml?
    Thanks,
    Mike

    JDeveloper 10.1.3.2 supports J2EE 1.4 in which the web.xml does not include the
    <taglib> element. Remove the <taglib> element from the web.xml. Specify the http uri in the <%@ taglib prefix='srp' uri='' %>
    Add the taglib JAR file to project libraries.

  • Error while importing xml file in calc manager

    Hi All,
    I am having trouble in importing the xml file for calc manager. I have used the rules migrator utility to convert the .rle file into XML. Now when I import this xml file in the calc manager it gives me the following error- "An invalid application 'XML file name' was found on object Main_Global". Please let me know how should I import the xml file in calc manager and get it deployed. Thakns in advance for the help.
    -Kamran

    Hi All,
    I am having trouble in importing the xml file for calc manager. I have used the rules migrator utility to convert the .rle file into XML. Now when I import this xml file in the calc manager it gives me the following error- "An invalid application 'XML file name' was found on object Main_Global". Please let me know how should I import the xml file in calc manager and get it deployed. Thakns in advance for the help.
    -Kamran

  • How to include custom application.xml in JDev9i project

    Can anybody explain to me how to include a custom application.xml file when deploying to an .ear file? I need to include application wide security roles, and I can't see where in Jev9i how to do this.
    After searching this forum, I see that jdev9i can't include the orion-application.xml, but I want to include just the standard J2EE application.xml. Is this possible?
    Thanks,
    matt

    The standard application.xml file unfortunately can't be customized in JDev 9.0.2. The reasons why this capability was left out of JDev 9.0.2 are same reasons why the other EAR-level XML files were excluded. The OTN thread
    Re: Regarding 11i and E-business suite
    has a summary of those reasons, which you've probably seen. We know this is an area in need of improvement and will be adding this functionality in the JDev 9.0.3 release. Until then, you'll have to go with a work-around like an Ant build file, batch file, Java application, or some other kind of script.
    Below is a sample Java application which can be used to insert <security-role> elements into an EAR file's application.xml. Modify the main() method to customize for your purposes, and put xmlparserv2.jar on the classpath (in a JDev project, add the "Oracle XML Parser v2" library):
    package mypackage4;
    import java.io.*;
    import java.util.*;
    import java.util.zip.*;
    import oracle.xml.parser.v2.*;
    import org.w3c.dom.*;
    import org.xml.sax.SAXException;
    public class PostProcessEAR
    public static void main( String[] args ) throws IOException
    final String earFile = "C:\\temp\\myapp.ear";
    final PostProcessEAR postProcess = new PostProcessEAR( earFile );
    postProcess.addSecurityRole( null, "first_role" );
    postProcess.addSecurityRole( "Description for the second role", "second_role" );
    postProcess.commit();
    System.out.println( "Done." );
    private final File _earFile;
    private final ArrayList _securityRoles = new ArrayList();
    public PostProcessEAR( String earFile )
    _earFile = new File( earFile );
    public void addSecurityRole( String description, String roleName )
    if ( roleName == null )
    throw new IllegalArgumentException();
    _securityRoles.add( description );
    _securityRoles.add( roleName );
    * Write out modified EAR file.
    public void commit() throws IOException
    if ( _securityRoles.size() == 0 )
    return;
    final ZipFile zipFile = new ZipFile( _earFile );
    final Enumeration entries = zipFile.entries();
    final File outFile = new File( _earFile.getAbsolutePath() + ".out" );
    final ZipOutputStream out = new ZipOutputStream( new BufferedOutputStream( new FileOutputStream( outFile ) ) );
    while ( entries.hasMoreElements() )
    final ZipEntry entry = (ZipEntry) entries.nextElement();
    final InputStream in = zipFile.getInputStream( entry );
    if ( "META-INF/application.xml".equals( entry.getName() ) )
    final XMLDocument modifiedApplicationXml = insertSecurityRoles( in );
    final ByteArrayOutputStream byteOutput = new ByteArrayOutputStream();
    modifiedApplicationXml.print( byteOutput );
    final int numBytes = byteOutput.size();
    entry.setSize( numBytes );
    if ( entry.getMethod() == ZipEntry.STORED )
    entry.setCompressedSize( numBytes );
    final CRC32 crc32 = new CRC32();
    crc32.update( byteOutput.toByteArray() );
    entry.setCrc( crc32.getValue() );
    out.putNextEntry( entry );
    byteOutput.writeTo( out );
    else
    // Copy all other zip entries as they are.
    out.putNextEntry( entry );
    copy( in, out );
    in.close();
    out.close();
    private XMLDocument insertSecurityRoles( InputStream in ) throws IOException
    final DOMParser domParser = new DOMParser();
    domParser.setAttribute( DOMParser.STANDALONE, Boolean.TRUE );
    try
    domParser.parse( in );
    final XMLDocument doc = domParser.getDocument();
    final Element docElem = doc.getDocumentElement();
    final Iterator iter = _securityRoles.iterator();
    while ( iter.hasNext() )
    final String desc = (String) iter.next(); // might be null
    final String roleName = iter.next().toString(); // must not be null
    final Element securityRoleElem = doc.createElement( "security-role" );
    if ( desc != null )
    securityRoleElem.appendChild( createPcdata( doc, "description", desc ) );
    securityRoleElem.appendChild( createPcdata( doc, "role-name", roleName ) );
    docElem.appendChild( securityRoleElem );
    return doc;
    catch ( SAXException e )
    e.printStackTrace();
    return null;
    private Element createPcdata( XMLDocument doc, String elemName, String pcdata )
    final Element elem = doc.createElement( elemName );
    elem.appendChild( doc.createTextNode( pcdata ) );
    return elem;
    private final byte[] buffer = new byte[4096];
    private void copy( InputStream in, OutputStream out ) throws IOException
    while ( true )
    final int bytesRead = in.read( buffer );
    if ( bytesRead < 0 )
    break;
    out.write( buffer, 0, bytesRead );

  • 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

  • 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

Maybe you are looking for