Application Ear file deployment on Oracle 9ias(9.0.3)

Hi,
I'm trying to deploy an application (JSP + BC4J) under Oracle 9ias using the Enterprise Manager (EM).
No error occurs during the process but I can not load the application with internet explorer.
the following message appears : "Not Found
The requested URL /AgatteWF/index.jsp was not found on this server."
Deploying the application under OC4J standalone with the same ear file works fine.
Does anyone got that problem ?
Any help is welcome
regards

Hi
I already had a look to the log files.
They don't show any error.
the webcontext is correct but index.jsp is not placed under the "WEB_INF" directory.
I don't think that's the reason of the problem 'cause i succeeded once to deploy the same application under the IAS.
I made the same operations i did before (creating a new oc4j instance under IAS after having dropped the old one, deploying the application, creating the data source...)
But i don't know why it doesn't work this time.

Similar Messages

  • Error after deploying in oracle 9ias

    Hi,
    I built a Struts app with Jdeveloper (win 2000) and deploy it (using a ear file) first on Oracle 9ias (win 2000) and on oracle 9ias (LINUX).
    When I submit my first form, I've got this error under oracle 9ias(LINUX):
    [INFO] PropertyMessageResources - -Initializing, config='org.apache.struts.action.ActionResources', returnNull=true
    org.xml.sax.SAXParseException: file:/data/9ias920/j2eehome/j2ee/home/applications/test/test/WEB-INF/struts-config.xml<Line 5, Column 14>: XML-0148: (Error) Invalid element 'form-beans' in content of 'struts-config', expected elements '[message-resources, plug-in]'.
         at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:166)
         at oracle.xml.parser.v2.XMLError.flushErrors(XMLError.java:134)
         at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:263)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:141)
         at org.apache.commons.digester.Digester.parse(Digester.java:1495)
         at org.apache.struts.action.ActionServlet.initApplicationConfig(ActionServlet.java:860)
         at org.apache.struts.action.ActionServlet.init(ActionServlet.java:455)
         at javax.servlet.GenericServlet.init(GenericServlet.java:44)
         at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:1673)
         at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4006)
         at com.evermind.server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2204)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:585)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
         at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
    [ERROR] Digester - -Parse Error at line 5 column 14:
    Everything looks ok in struts-config.xml. Could anybody help me?

    Hi,
    I built a Struts app with Jdeveloper (win 2000) and deploy it (using a ear file) first on Oracle 9ias (win 2000) and on oracle 9ias (LINUX).
    When I submit my first form, I've got this error under oracle 9ias(LINUX):
    [INFO] PropertyMessageResources - -Initializing, config='org.apache.struts.action.ActionResources', returnNull=true
    org.xml.sax.SAXParseException: file:/data/9ias920/j2eehome/j2ee/home/applications/test/test/WEB-INF/struts-config.xml<Line 5, Column 14>: XML-0148: (Error) Invalid element 'form-beans' in content of 'struts-config', expected elements '[message-resources, plug-in]'.
         at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:166)
         at oracle.xml.parser.v2.XMLError.flushErrors(XMLError.java:134)
         at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:263)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:141)
         at org.apache.commons.digester.Digester.parse(Digester.java:1495)
         at org.apache.struts.action.ActionServlet.initApplicationConfig(ActionServlet.java:860)
         at org.apache.struts.action.ActionServlet.init(ActionServlet.java:455)
         at javax.servlet.GenericServlet.init(GenericServlet.java:44)
         at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:1673)
         at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4006)
         at com.evermind.server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2204)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:585)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
         at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
    [ERROR] Digester - -Parse Error at line 5 column 14:
    Everything looks ok in struts-config.xml. Could anybody help me?

  • Error while deploying an ear file in the Oracle Application Server

    Hi,
    There was an existing ear deployed in the the oracle application server - 10g. We had to include some customizations so we rebuild the ear file with the new changes and tried redeploying the ear using the EM console. Getting the below error while deploying the same. Any pointers to the same would be helpful.
    Error
    An error occurred when processing the data submitted. Find the appropriate field and enter the correct information as noted next to each field.
    Archive Location - Failed in uploading archive. Invalid archive file: Jar file resourceadapter-rar.rar is missing a standard deployment located at META-INF/ra.xml
    We have not modified anything in the ra.xml nor have touched the resourceadapter-rar.rar

    Hello
    did you configure the startweblogic file as mentioned in the admin guide ?

  • Error while deploying .ear file on the oracle 10g Application server

    While deploying the ITS.ear or any other .ear file thru the application server console the screen shows the deploying screen continuously without any errors.The screen shows uploading the .ear file without any errors.Can somebody help me out it 's very urgent
    Thanks in advance.

    Hello,
    I asked you about the amount of AS instances because currntly I'm working on a clustering issue likewise. Nevertheless, your issue looks like a browser cache problem, have you tried different browsers to perform your deployment tasks? what about ant tasks?
    hope it helps,
    RB

  • Sort order in Java application (oc4j container) -- ear file deployment

    I have a Java application deploy in Oracle OC4J container (EAR file).
    In my Java application (jsp), I have a SQL statement who return data but the
    sort order is wrong. The letters "é" and all characters with accents
    appears at the end of the result.
    I tried many things to change the sort order (NLS parameters in database
    and OAS10g parameter files).
    When I use SQL*plus on database server, that's working.
    The sort order is wrong when I use the java application.
    Somebody can tell me what and where is the NLS parameters to change ?
    Thanks
    Robin

    Robin,
    I'm only guessing, but it could either be related to the java locale or the CHARSET attribute of the HTML header -- and nothing to do with the NLS parameters.
    Maybe you should try the Globalization Support forum?
    Good Luck,
    Avi.

  • Deploying junitee outside of the application ear file

    I have an application that is deployed within an ear file, and I have junitee tests
    within a war file, called test.war. I would like to not have to place the test.war
    within the ear file because the ear may be release code but I still want to test
    it using the junitee tests. Instead I would like to optionally add the test.war
    to the application context and not the ear file. How would I go about doing that?
    I tried to deploy the test.war from the weblogic console, and hand editing the
    config.xml, and adding the test.war as a module to the application.xml (within
    the ear file).
    In all cases when I try to then use classes within the ear file I get ClassNotFoundExceptions.
    Probably because Weblogic is not including the test.war as part of the same application.
    Thank in advance for any help.
    -Fazle

    I'd probably have 2 build targets, debug and production. Your debug
    target could include the unit test war file.
    -- Rob
    Fazle Khan wrote:
    I have an application that is deployed within an ear file, and I have junitee tests
    within a war file, called test.war. I would like to not have to place the test.war
    within the ear file because the ear may be release code but I still want to test
    it using the junitee tests. Instead I would like to optionally add the test.war
    to the application context and not the ear file. How would I go about doing that?
    I tried to deploy the test.war from the weblogic console, and hand editing the
    config.xml, and adding the test.war as a module to the application.xml (within
    the ear file).
    In all cases when I try to then use classes within the ear file I get ClassNotFoundExceptions.
    Probably because Weblogic is not including the test.war as part of the same application.
    Thank in advance for any help.
    -Fazle

  • 9iAS version 1 EAR file deployment and UNIX directory permissions

    We are running version 1.0.2.2 of OC4J, the deployment
    directory seems to need world read/write to enable the
    EAR file to deploy. The 9iAS admin user is part of the
    group that owns the EAR file (and respective deployment
    directory) but still cannot write to the
    directory when permissions are set with chmod 755.
    Thank you for any suggestions.

    One thing to try is in the JAR deployment profile for the EJB - stand on the File Groups node and click new to add a library group and make sure it includes the libraries/jar you added to your project.
    If this doesn't help then you might want to try and cross post this on the OC4J forum:
    OC4J

  • Incremental Fix - After J2EE EAR File Deployment

    Oracle 9iAS 9.0.3.1 (MiddleTier)
    Oracle 9ias 9.0.2.3 (Infrastructure)
    Hi! We were successful in deploying a full J2EE/Struts based application as an EAR file through Enterprise Manager Web Site.
    After the deployment, if we wanted to fix a issue in the module within the application, we just want to replace that Java Source File, without re-deploying the entire application. Is there an Oracle recommended approach for this?
    I know we could do this with ANT but, Is this Oracle Supported incremental deployment approach..? Are they any other ways of doing this without re-deploying the whole application.
    Your thoughts/help is greatly appreciated.
    Thanks
    RK

    Oracle 9iAS 9.0.3.1 (MiddleTier)
    Oracle 9ias 9.0.2.3 (Infrastructure)
    Hi! We were successful in deploying a full J2EE/Struts based application as an EAR file through Enterprise Manager Web Site.
    After the deployment, if we wanted to fix a issue in the module within the application, we just want to replace that Java Source File, without re-deploying the entire application. Is there an Oracle recommended approach for this?
    I know we could do this with ANT but, Is this Oracle Supported incremental deployment approach..? Are they any other ways of doing this without re-deploying the whole application.
    Your thoughts/help is greatly appreciated.
    Thanks
    RK

  • Ear file deployment and jar libaries

    I am creating a simple ejb application that uses some jar libraries. The ejb app builds fine but when i try to deploy the application, it cannot find the dependent classes although i am including the jar libs in the ear file. I tried including the jars-libs in root as well as in app-inf/lib directory. I also made sure that i have the right jar-libs. What am i missing ?
    Here is what i see on the console when i try to deploy on Oracle App server:
    Nov 29, 2006 1:31:51 PM] Unpacking TestWithLib.ear
    [Nov 29, 2006 1:31:52 PM] Done unpacking TestWithLib.ear
    [Nov 29, 2006 1:31:52 PM] Initialize C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\TestWithLib.ear ends...
    [Nov 29, 2006 1:31:52 PM] Starting application : TestWithLib
    [Nov 29, 2006 1:31:52 PM] Initializing ClassLoader(s)
    [Nov 29, 2006 1:31:52 PM] Initializing EJB container
    [Nov 29, 2006 1:31:52 PM] Loading connector(s)
    [Nov 29, 2006 1:31:52 PM] Starting up resource adapters
    [Nov 29, 2006 1:31:52 PM] Processing EJB module: ejb1.jar
    [Nov 29, 2006 1:31:52 PM] Operation failed with error: com/xyz/ClassName

    One thing to try is in the JAR deployment profile for the EJB - stand on the File Groups node and click new to add a library group and make sure it includes the libraries/jar you added to your project.
    If this doesn't help then you might want to try and cross post this on the OC4J forum:
    OC4J

  • Ear file deploys on oc4j standalone, not on ias using the ent.appl.manager

    We added security constraints to our web.xml, and this works when we deploy it on a standalone OC4J. Deploying this ear on the ias with the Enterprise application Manager: after choosing the ear-file, giving it a name and pushing the next button we get a nullpointer-exception.
    After removing the security constraints the deployment works. Any ideas????
    Eelco

    To be complete, here's the web.xml:
    <?xml version="1.0"?>
    <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
    <!-- This file contains the configuration for a web-application.-->
    <web-app>
    <distributable />
    <display-name>Laris Application</display-name>
    <description>Laris Application</description>
    <env-entry>
         <description>Database connection string</description>
         <env-entry-name>dbconnect</env-entry-name>
         <env-entry-value>jdbc:oracle:thin:&lt;user&gt;&lt;pwd&gt;@&lt;host&gt;:&lt;port&gt;:&lt;sid&gt;</env-entry-value>
         <env-entry-type>java.lang.String</env-entry-type>
    </env-entry>
    <env-entry>
         <description>Dtd locatie string</description>
         <env-entry-name>dtd_url</env-entry-name>
         <env-entry-value>http://&lt;host&gt;:&lt;port&gt;/laris/dtd/</env-entry-value>
         <env-entry-type>java.lang.String</env-entry-type>
    </env-entry>
    <servlet>
    <servlet-name>LarisController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>StartLarisService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>PortaalController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>PortaalService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>InvoerenAanspraakController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>InvoerenAanspraakService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>ControlerenAanspraakController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>ControlerenAanspraakService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>BeoordelenAanspraakController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>BeoordelenAanspraakService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>BeslissenAanspraakController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>BeslissenAanspraakService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>BehandelenAanspraakController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>BehandelenAanspraakService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>CommunicatieGeneratorController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>CommunicatieGeneratorService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>KruisjestabelController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>KruisjestabelService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>CitesController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>LarisService.xml</param-value>
    </init-param>
    </servlet>
    <servlet>
    <servlet-name>BaBoSSController</servlet-name>
    <servlet-class>oracle.clex.process.controller.HttpServletController</servlet-class>
    <init-param>
    <param-name>cle-service-descriptor</param-name>
    <param-value>LarisService.xml</param-value>
    </init-param>
    </servlet>
    <servlet-mapping>
    <servlet-name>LarisController</servlet-name>
    <url-pattern>Default/StartIt</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>PortaalController</servlet-name>
    <url-pattern>Portaal/StartIt</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>InvoerenAanspraakController</servlet-name>
    <url-pattern>Portaal/InvoerenAanspraak/StartIt</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>ControlerenAanspraakController</servlet-name>
    <url-pattern>Portaal/ControlerenAanspraak/StartIt</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>BeoordelenAanspraakController</servlet-name>
    <url-pattern>BeoordelenAanspraak/Eenvoudig/StartIt</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>BeslissenAanspraakController</servlet-name>
    <url-pattern>Beslissen/VaststellenBeslissing/StartIt</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>BehandelenAanspraakController</servlet-name>
    <url-pattern>Behandelen/AdministratiefControleren/StartIt</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>CommunicatieGeneratorController</servlet-name>
    <url-pattern>Informeren/CommunicatieGenerator/StartIt</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>KruisjestabelController</servlet-name>
    <url-pattern>Kruisjestabel/Kruisjestabel/StartIt</url-pattern>
    </servlet-mapping>
    <!-- security roles -->
    <security-role>
         <role-name>sr_manager</role-name>
    </security-role>
    <security-role>
         <role-name>sr_developer</role-name>
    </security-role>
    <!-- security constraints -->
    <security-constraint>
    <web-resource-collection>
    <url-pattern>cabo/*</url-pattern>
    <url-pattern>jheadstart/*</url-pattern>
    <url-pattern>help/*</url-pattern>
    <url-pattern>laris/*</url-pattern>
    <url-pattern>images/*</url-pattern>
    <url-pattern>uix/*</url-pattern>
    </web-resource-collection>
    <!-- authorization -->
    <!-- <auth-constraint>
    <role-name>sr_developer</role-name>
    </auth-constraint> -->
    </security-constraint>
    <security-constraint>
    <web-resource-collection>
    <url-pattern>Default/*</url-pattern>
    <url-pattern>Portaal/*</url-pattern>
    <url-pattern>Informeren/*</url-pattern>
    <url-pattern>Behandelen/*</url-pattern>
    <url-pattern>Beslissen/*</url-pattern>
    <url-pattern>BeoordelenAanspraak/*</url-pattern>
    <!-- volgende is wel gewenst (in 1 keer alles beveiligen), maar werkt niet
    <url-pattern>*</url-pattern> geeft error bij createmarlinbeanpag
    <url-pattern>*/*</url-pattern> beveiligt gewoon niet
    <url-pattern>./*</url-pattern> beveiligt niet alles
    <url-pattern>./*/*</url-pattern> beveiligt niet(s)
    <url-pattern>../*</url-pattern> beveiligt niets
    -->
    </web-resource-collection>
    <!-- authorization -->
    <auth-constraint>
    <role-name>sr_developer</role-name>
    </auth-constraint>
    </security-constraint>
    <!-- de volgende security constraint is niet zozeer voor de administrator
    maar om er voor te zorgen dat bovenstaande constraint de toegang
    beperkt tot alleen het gedefinieerde -->
    <security-constraint>
    <web-resource-collection>
    <url-pattern>/*</url-pattern>
    </web-resource-collection>
    <auth-constraint>
         <role-name>sr_administrator</role-name>
    </auth-constraint>
    </security-constraint>
    <!-- authentication -->
    <login-config>
         <auth-method>BASIC</auth-method>
    </login-config>
    </web-app>

  • How do I convert an war file to ear file, deploying weblogic apps

    Problem Description: I have a war file from a legacy application that needs to be migrated to weblogic. To migrate this application to weblogic, we need a ear file. Reading weblogic doc. it says we needs to use ant utility on an exploded web content application folder/ directory to create the ear file. I need to covert the existing war file to ear file , if it is doable or create one from the scratch. I need to know how to do that in weblogic. Please let me know if you have any hints .
    Thanks

    HI,
    Please try the following to convert your WAR file into an EAR exploded archieve:
    *1).* Create a Directory in your file system.
    Example:
    /home/apps/MyFirstEAR
    *2).* Place the WAR file inside the above Directory. (Suppose your WAR file name is test.war)
    Example:
    /home/apps/MyFirstEAR/test.war
    *3).* Now create a "META-INF" directory inside "/home/apps/MyFirstEAR" directory
    *4).* Now create an "application.xml" file like following inside "/home/apps/MyFirstEAR/META-INF" directory:
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.4">
    <description>Test EAR Example</description>
    <display-name>TestEAR Example</display-name>
    <module>
    <web>
    <web-uri>test.war</web-uri>
    <context-root>test</context-root>
    </web>
    </module>
    </application>
    *5).* Your EAR is ready now you can deploy the "MyFirstEAR" directory in the WebLogic Server.
    NOTE: if you want to place the "test.war" file also as an exploaded format content inside the EAR then you need to extract the test.war file and then in place of the test.war you can have "test" directory at the same place.
    You need to change the "application.xml" file like below in that case:
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.4">
    <description>Test EAR Example</description>
    <display-name>TestEAR Example</display-name>
    <module>
    <web>
    <font color=red> <web-uri>test</web-uri> </font><br>
    <context-root>test</context-root>
    </web>
    </module>
    </application>
    For more information on an EAR application structure you can refer to : http://middlewaremagic.com/weblogic/?p=1952
    Thanks
    Jay SenSharma
    http://middlewaremagic.com/weblogic (Middleware Magic Is Here)

  • Error during ear file deployment

    Hi,
    I am getting the error while trying to deploy ear file using SDM.
    The error log is
    Starting Deployment of MyzipBean
    Aborted: development component 'MyzipBean'/'sap.com'/'localhost'/'2008.06.13.17.44.31'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/MyzipBean.. Reason: Incorrect application sap.com/MyzipBean:Bean MyzipBean: can not find method ejbCreate()  in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean MyzipBean: can not find method ejbCreate()  in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/MyzipBean:Bean MyzipBean: can not find method ejbCreate()  in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean MyzipBean: can not find method ejbCreate()  in ejb-class myzip.MyzipBean. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.
    What could be the reason?
    Thanks,
    Jaishankar

    Hi,
    1. Restart the upgrade
    2. When it shows the error above open callSdmViaSapinst.log and search for the application that can't be deployed
    3. If application is STOPPED start it
    4. Undeploy the application if it is STARTED
    5. Press the "Retry" button in the error message dialog box from the
    upgrade
    6. If it fails again for another application go to 2.
    Please refer SAP NOte 851590. I don't know if it work for u, as i have given this , it seems for Upgrade as you are developing.
    Look into this thread also
    Unable to deploy a module into XI Server
    Regards
    Aashish Sinha
    Edited by: Aashish Sinha on Jun 13, 2008 3:20 PM
    Edited by: Aashish Sinha on Jun 13, 2008 3:28 PM

  • Running a J2EE application (ear file)

    I am new to J2EE. I have created a EnpDtls Servlet simply to greet a person by name - like sample application. But i am unable to see it in on web (localhost:8080). What should i give as url to view the application? I am using J2EE 1,4 Application Server 8.2 from SUN. and jsdk 1.5
    I can see my html file under Context Root i.e localhost:8080/EmpDtlsCx. But what should be the url to see the class file of my sevlet.
    Servlet is : EmpDtls.class
    ContextRoot : /EmpDtlsCx
    Web Display : EmpDtlsWebDsp
    EAR file : EmpDtlsEar
    I have used deploytool. I can also see the Application in Admin console (localhost:4848) -> Enterprise Application. But there also the Admin console does not give any otion of launch as it gives for Web Application. Please note that the verifier option in Admin consoile also passes of sucessfully.
    The deployment descriptors: application.xml, sun-application.xml are under <J2ee INSTALLDIR>/domains/domain1/applications/j2ee-apps/EmpDtlsEar/ - the name of the EAR file.
    Should i get ContextRoot as folder name ?
    Could anyone help in solving my problem ?
    The structure of directories and files is as follows
       EmpDtlsEar
       |
       |____ META-INF
       |                |
       |                |____ application.xml
       |                |____ sun-spplication.xml
       |                |____ sun-j2ee-ri.project
       |                |____ MANIFEST.MF
       |
       |____ war-ic.war
                       |
                       |____ EmpDtls.html
                       |
                       |____ META-INF
                       |                  |
                       |                  |__ MANIFEST.MF
                       |
                       |____ WEB-INF
                                         |
                                         |__ web.xml
                                         |
                                         |__ sun-web.xml
                                         |
                                         |__ sun-jee-ri.project
                                         |
                                         |__ classes
                                                  |
                                                  |__ EmpDtls.class
    thanks in advance
    tshot

    Ok, you have your servlet defined, but now you should map it using mapping tags. Try editing your web.xml file as follows (adding mapping):
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.4" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
      <display-name>EmpDtlsWarDisp</display-name>
      <servlet>
        <display-name>EmpDtlsWebDisp</display-name>
        <servlet-name>EmpDtlsWebComp</servlet-name>
        <servlet-class>tshot.EmpDtls</servlet-class>
      </servlet>
      <servlet-mapping>
        <servlet-name>EmpDtlsWebComp</servlet-name>
        <url-pattern>/EmpDtls</url-pattern>
      </servlet-mapping>
    </web-app>Note the adding of "tshot." in front of your EmpDtls in your servlet-class tag.
    This means you need to create a directory in your src location called "tshot", move your EmpDtls.java into the new directory, and then edit that java file, placing the following line at the top of it:
    package tshot;Once you have re-built and re-deployed this you should be able to access your servlet at:
    http://localhost:8080/EmpDtlsCx/EmpDtls
    Refactoring is a term used to mean you've decided to change the name of a variable, method or some alteration of your java file such as changing package names (or adding to a package in this case) whereby the results may or may not affect other classes which depend on this class. Typically, nowadays refactoring is usually done by selecting a refactoring command from a menu item or button within an IDE (Integrated Development Environment) whereby the IDE performs all of the dependancy checking for you and copies the change to affected areas where necessary. Thus, all you need to do is choose the right refactoring operation and click "Ok" in most cases. In the old days, you would have to keep track of all affected areas and manually edit where necessary, based on your imposed change.

  • Wl 8.1 sp1 .ear file deployment problems

    I am Unable to deploy ear file in WL8.1 SP1. See the error below..
    This ear fie is successfully deployed on WL6.1 SP3
    IF i remove the componenet on which this error is thrown, the same error appears
    on other componenet...
    Can somebody explain what would cause this?
    Exception thrown is:-->
    Exception:weblogic.management.ApplicationException: prepare failed for MorningMDB.jar104
    Module: MorningMDB.jar104 Error: Exception preparing module: EJBModule(MorningMDB.jar104,status=NEW)
    Unable to deploy EJB: MorningMDB from MorningMDB.jar: [EJB:011026]The EJB container
    failed while creating the java:/comp/env namespace for this EJB deployment. javax.naming.NameAlreadyBoundException:
    UserTransaction is already bound; remaining name 'app/ejb/MorningMDB/jar#MorningMDB/comp'
    at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:333) at
    weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291) at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:298)
    at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359) at weblogic.ejb20.deployer.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:619)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:385)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1110)
    at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:922) at
    weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2634)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    5. The LOg of Activities:-->
    [Deployer:149033]preparing application lpapp on wls1
    [Deployer:149033]failed application lpapp on wls1
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application
    lpapp on wls1.:
    Exception:weblogic.management.ApplicationException: prepare failed for MorningMDB.jar104
    Module: MorningMDB.jar104 Error: Exception preparing module: EJBModule(MorningMDB.jar104,status=NEW)
    Unable to deploy EJB: MorningMDB from MorningMDB.jar:
    [EJB:011026]The EJB container failed while creating the java:/comp/env namespace
    for this EJB deployment.
    javax.naming.NameAlreadyBoundException: UserTransaction is already bound; remaining
    name 'app/ejb/MorningMDB/jar#MorningMDB/comp'
    at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:333)
    at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291)
    at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:298)
    at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359)
    at weblogic.ejb20.deployer.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:619)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:385)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1110)
    at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:922)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2634)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    I can give you the skeleton..
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application
    1.2//EN' 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
    <application>
    <display-name>Application</display-name>
    <description>Application description</description>          
    <module>
         <web>
              <web-uri>mywar.war</web-uri>
              <context-root>mywar</context-root>
              </web>
    </module>
         <module>
              <ejb>myejbs.jar</ejb>
    </module>
    </application>
    "skv" <[email protected]> wrote:
    >
    Unfortunately I can't.
    But I can answer your questions. I have also open a case with bea and
    so far no
    luck.
    Also the ear file take an awful lot of time to deploy. THe ear file
    I have currently
    contains 106 jar file (ejb's) and the deployment continues forever (>
    than 25
    minutes) and the status in console Shows 'In progress'
    Rob Woollen <[email protected]> wrote:
    Strange. Can you show me the contents of your EAR file (ie the file
    layout) and your application.xml?
    -- Rob
    skv wrote:
    I am Unable to deploy ear file in WL8.1 SP1. See the error below..
    This ear fie is successfully deployed on WL6.1 SP3
    IF i remove the componenet on which this error is thrown, the sameerror appears
    on other componenet...
    Can somebody explain what would cause this?
    Exception thrown is:-->
    Exception:weblogic.management.ApplicationException: prepare failedfor MorningMDB.jar104
    Module: MorningMDB.jar104 Error: Exception preparing module: EJBModule(MorningMDB.jar104,status=NEW)
    Unable to deploy EJB: MorningMDB from MorningMDB.jar: [EJB:011026]TheEJB container
    failed while creating the java:/comp/env namespace for this EJB deployment.javax.naming.NameAlreadyBoundException:
    UserTransaction is already bound; remaining name 'app/ejb/MorningMDB/jar#MorningMDB/comp'
    at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:333)at
    weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291)at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:298)
    at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359)at weblogic.ejb20.deployer.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:619)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:385)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1110)
    at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:922)at
    weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2634)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) atweblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    5. The LOg of Activities:-->
    [Deployer:149033]preparing application lpapp on wls1
    [Deployer:149033]failed application lpapp on wls1
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deployapplication
    lpapp on wls1.:
    Exception:weblogic.management.ApplicationException: prepare failedfor MorningMDB.jar104
    Module: MorningMDB.jar104 Error: Exception preparing module: EJBModule(MorningMDB.jar104,status=NEW)
    Unable to deploy EJB: MorningMDB from MorningMDB.jar:
    [EJB:011026]The EJB container failed while creating the java:/comp/envnamespace
    for this EJB deployment.
    javax.naming.NameAlreadyBoundException: UserTransaction is alreadybound; remaining
    name 'app/ejb/MorningMDB/jar#MorningMDB/comp'
    at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:333)
    at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291)
    at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:298)
    at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359)
    at weblogic.ejb20.deployer.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:619)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:385)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1110)
    at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:922)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2634)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

  • Adapter Module .ear file deployed

    Hi All,
    I have an adapter module deployed long back on my dev server.
    I want to retrive the same file from dev and deploy in on Quality server.
    Can you let me know the path where this .ear file will be present on the SAP XI server.
    Thx in advance
    Ravijeet

    Hi Ravijeet,
    We run under i5/OS (unix like) but I found my deployed Adapter Module under:
    DX1 is the instance name.
    sap.com is the vendor specified in the EJB module.
    EOLConvertBean is my adapter module
    /usr/sap/dx1/DVEBMGS70/j2ee/cluster/apps/sap.com/EOLConvertBeanEAR                                                     
    /usr/sap/dx1/DVEBMGS70/j2ee/cluster/apps/sap.com/EOLConvertBeanEAR/EJBContainer/applicationjars/EOLConvertBean.jar     
    Hope it helps.
    Martin
    Edited by: Martin Lavoie Rousseau on Nov 4, 2010 2:41 PM

Maybe you are looking for