Deploying Enterprise application in exploded format

ewsgroup: to weblogic.developer.interest.webserver
For simplification and to make changes easier
we want to deploy our EJB's
and web application in exploded format.
I created the following directory structure
in my home area:
Application/
deploy/
META-INF/
application.xml
web/
jsps, html
WEB-INF/
*.xml
classes/
servlet
.class files
lib/
ejb/
META-INF/
*.xml
com/ .... directory
structure for EJB.
I deployed the application using the admin
console and referencing
myhome/application/deploy. This results in
the following error in the log:
<Dec 18, 2001 5:25:46 PM MST> <Error> <HTTP>
<[web] Error reading
Web application "/myhome/application/deploy/web"
java.net.ConnectException: Tried all: '1' addresses,
but could not connect
over HTTP to server : 'java.sun.com', port:
'80'
None of my WLS servers are configured to use
port 80. This particular
server is configured to listen on port 7009.
Any help or insight would be greatly appreciated.

I think I ran into the same problem with using the localhost address on our
application. Are you using the ip of one of your managed servers?
Are you upgrading or using WLS 6.1 SP1 ..by the way?
"Terry Jahelka" <[email protected]> wrote in message
news:3c20c99e$[email protected]..
>
For simplification and to make changes easier we want to deploy our EJB'sand web
application
in exploded format.
I created the following directory structure in my home area:
Application/
deploy/
META-INF/
application.xml
web/
jsps, html
WEB-INF/
*.xml
classes/
servlet .class files
lib/
ejb/
META-INF/
*.xml
com/ .... directory structure for EJB.
I deployed the application using the admin console and referencingmyhome/application/deploy.
This results in the following error in the log:
<Dec 18, 2001 5:25:46 PM MST> <Error> <HTTP> <[web] Error reading Webapplication
"/myhome/application/deploy/web"
java.net.ConnectException: Tried all: '1' addresses, but could not connectover
HTTP to server
: 'java.sun.com', port: '80'
None of my WLS servers are configured to use port 80. This particularserver
is configured
to listen on port 7009.
Any help or insight would be greatly appreciated.

Similar Messages

  • Deploying application in Exploded format

    For simplification and to make changes easier we want to deploy our EJB's and web
    application
    in exploded format.
    I created the following directory structure in my home area:
    Application/
    deploy/
    META-INF/
    application.xml
    web/
    jsps, html
    WEB-INF/
    *.xml
    classes/
    servlet .class files
    lib/
    ejb/
    META-INF/
    *.xml
    com/ .... directory structure for EJB.
    I deployed the application using the admin console and referencing myhome/application/deploy.
    This results in the following error in the log:
    <Dec 18, 2001 5:25:46 PM MST> <Error> <HTTP> <[web] Error reading Web application
    "/myhome/application/deploy/web"
    java.net.ConnectException: Tried all: '1' addresses, but could not connect over
    HTTP to server
    : 'java.sun.com', port: '80'
    None of my WLS servers are configured to use port 80. This particular server
    is configured
    to listen on port 7009.
    Any help or insight would be greatly appreciated.

    I think I ran into the same problem with using the localhost address on our
    application. Are you using the ip of one of your managed servers?
    Are you upgrading or using WLS 6.1 SP1 ..by the way?
    "Terry Jahelka" <[email protected]> wrote in message
    news:3c20c99e$[email protected]..
    >
    For simplification and to make changes easier we want to deploy our EJB'sand web
    application
    in exploded format.
    I created the following directory structure in my home area:
    Application/
    deploy/
    META-INF/
    application.xml
    web/
    jsps, html
    WEB-INF/
    *.xml
    classes/
    servlet .class files
    lib/
    ejb/
    META-INF/
    *.xml
    com/ .... directory structure for EJB.
    I deployed the application using the admin console and referencingmyhome/application/deploy.
    This results in the following error in the log:
    <Dec 18, 2001 5:25:46 PM MST> <Error> <HTTP> <[web] Error reading Webapplication
    "/myhome/application/deploy/web"
    java.net.ConnectException: Tried all: '1' addresses, but could not connectover
    HTTP to server
    : 'java.sun.com', port: '80'
    None of my WLS servers are configured to use port 80. This particularserver
    is configured
    to listen on port 7009.
    Any help or insight would be greatly appreciated.

  • J2ee application in  exploded format in oracle 10g

    sorry: folder structure is like this:
    test_app
    --META-INF
    -----application.xml     
    --test_web
    -----pages
    -------welcome.jsp
    -----WEB-INF
    -------web.xml
    -------lib
    -------src     
    Regards,
    Roopa.
    Message was edited by:
    user447401

    Roopa, it looks like there is no problem with the deployment of your application in exploded format. Have you accessed http://server-ipaddress:7778/test_app/pages/welcome.jsp? Any problem access http://server-ipaddress:7778/j2ee/, the default home page of the default-web-app ?
    When you say the url http://server-ipaddress:7778/test_app is not working, what is the error message if any on the browser, on server console, in the server.log and http-web-access.log of ORACLE_HOME/j2ee/home/log/, ORACLE_HOME/j2ee/home/application-deployments/test_app/application.log?

  • How to deploy enterprise application OTA?

    Hello, I am Sungwoo Bae.
    I am slightly new to enterprise program, Because I was mainly developing apps for appstore.
    Before iOS4 is released, I deployed simple in-house application and certifacate using iTunes.
    But our client feel uncomfortable about deployment way which require to use their PC and iTunes.
    With relese of iOS4, I heard there is new way to deploy application OTA from my colleague.
    I was searching web to find that way, but I can't find.
    It is true that there is new way to deploy device configuration, but I cannot find about in-house application anywhere.
    I also tried to get apple's support, but I couldn't get the desired answer.
    Is there something I missed?
    Please let me know if there is any way of deploying enterprise application OTA.
    Thanks.
    Sungwoo Bae.

    For that feature, you need to setup MDM (Mobile Device Management), and some of Apple Engineers told me that MDM infos are only available for Enterprise Program subscriber....Apparently, it does not.....
    Any info about MDM is really welcomed from Apple that sold this feature as a major new feature for iOS 4.
    David

  • Deploy web application with exploded directory format

    I am quite new with Oracle9iAS Containers for J2EE. Currently, my project is not using EJB, only JSP and Servlets. I want to deploy the war file with exploded directory format. I don't want to use the default web application directory j2ee/home/default-web-app. The "Using Oracle9iAS Containers for J2EE" get start documentation only explained how to deploy J2ee application. What about the web application without EJB jar file? Anybody knows how to do that. Please let me know.
    Thanks in advance.

    Though you don't have ejbs, you can still use the ear file format. This would be most convenient way of deploying.
    Use of a tool like Ant is recommended if you are not using JDeveloper.
    Also, you can findinfo on deploying using a exploded directory
    http://otn.oracle.com/docs/tech/java/oc4j/htdocs/getstart.htm#1027810
    But recommed having ear file as it is convenient. If you want to see an example of use of Ant and deploying using ear file
    check out one of the recently posted how-tos E.g. http://otn.oracle.com/tech/java/oc4j/htdocs/how-to-servlet-events.html

  • Help redeploying an application in exploded format

    Hi,
    I am trying to redeploy my application that has been deployed in exploded
    format,
    but it doesn't seem to be working.
    I am following the steps presented in the Admin guide as follows:
    1. I have an empty file named REDEPLOY in the directory where my exploded
    application resides.
    2. I make my changes to my application & compile. The .class files end up
    in a different folder than
    my exploded deployment directory.
    3. I copy the updated .class files to the exploded deployment directory.
    4. Touch the REDEPLOY file to update its timestamp.
    But my new changes are not seen. (Of course they are seen if I restart the
    server).
    My environment is W2K; WL6.1, SP1.
    Any ideas?
    Thanks,
    Beth

    The REDEPLOY file is inside the WEB-INF directory and we still couldn't get
    it to work.
    Our Web Application resides outside the Weblogic Home directory and we are
    compiling
    directly into this directory now (the original message stated we were
    compiling to a different
    directory, then copying the .class files).
    We were able to get the hot redeploy working by using the Weblogic Console
    and unchecking &
    rechecking the check box that said whether or not the application was
    deployed- the current environment
    that this is working is WL6.1 (we backed out the Service Pack for a
    different reason). We did
    find that we do need to shut down any existing browser sessions; but as long
    as we start a new browser
    session we don't need to restart the WL server and all the new changes are
    picked up.
    Even though the hot redeploy is working for us without touching the REDEPLOY
    file, I'm
    still curious if we are missing something here about how this works. If
    anyone has any ideas,
    I'd like to hear them.
    Thanks,
    Beth
    "Mihir Kulkarni" <[email protected]> wrote in message
    news:[email protected]..
    The REDEPLOY file should be inside the WEB-INF directory of the exploded
    webapp.
    http://e-docs.bea.com/wls/docs61////webapp/deployment.html#138990
    - mihir
    Beth wrote:
    Hi,
    I am trying to redeploy my application that has been deployed in
    exploded
    format,
    but it doesn't seem to be working.
    I am following the steps presented in the Admin guide as follows:
    1. I have an empty file named REDEPLOY in the directory where myexploded
    application resides.
    2. I make my changes to my application & compile. The .class files endup
    in a different folder than
    my exploded deployment directory.
    3. I copy the updated .class files to the exploded deploymentdirectory.
    4. Touch the REDEPLOY file to update its timestamp.
    But my new changes are not seen. (Of course they are seen if I restartthe
    server).
    My environment is W2K; WL6.1, SP1.
    Any ideas?
    Thanks,
    Beth

  • Where to find out deployed enterprise applications?

    Hi experts,
    I've made DC of type Web Module (let's call it WM) and packed it in DC of type Enterprise application (let's call it EA). Can I see EA in the portal (in the PCD or somewhere else)? And how can I access it? My Web Module contains of simple JSP files. What is the correct way to access them? I'm using EP 7.2

    Hi Musaka,
    > Can I see EA in the portal (in the PCD or somewhere else)?
    No (or: very probably not, as I can't say it 100% for your version... see below...). Keep in mind that the portal itself is a web application. You can integrate other web apps (also deployed on the same server) via the AppIntegrator.
    > I'm using EP 7.2
    ?! This does not exist officially - are you with SAP and using some alpha version?!
    Hope it helps
    Detlev

  • Error at deploying Enterprise Application Archives

    Hi,
    I am running CE 7.1 SR5 and I have tried to deploy the EAA. All program incl. XML is ok and should have no errors.
    However, I get the errorlog as seen below. It will not deploy; any help is appreciated:
    Start of File:
    --- Deploying file(s):
         C:\Documents and Settings\Peter C. Sandgaard\workspace\EmployeeEar\EmployeeEar.ear
    --- Status:
         Deploy Exception.
    --- Description:
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           0
    Failed deployments:                1
    ~~~~~~~~~~~~~~~~~~~
    An error occurred while deploying the deployment item 'sap.com_EmployeeEar'.; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.com_EmployeeEar. Cannot deploy it.
    1. File:C:\Documents and Settings\Peter C. Sandgaard\workspace\EmployeeEar\EmployeeEar.ear
         Name:EmployeeEar
         Vendor:sap.com
         Location:localhost
         Version:2009.02.12.00.43.50
         Deploy status:Aborted
         Version:NEW
         Description:
              1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.com/EmployeeEar application.
    ERRORS:
    Fields Properties Check: The persistent field 'serialVersionUID' in class 'com.sap.demo.entity.Employee' tagged as 'id' should be protected, package or private visibility and should not be final or static, file: EmployeeEjb.jar#META-INF/persistence.xml, column 0, line 0, severity: error * Fields Properties Check: The field 'serialVersionUID' in class 'com.sap.demo.entity.Employee' is tagged 'id', but is not persistent field according to the specification, file: EmployeeEjb.jar#META-INF/persistence.xml, column 0, line 0, severity: error
    Hint: 1) Given application file is not valid one.
    --- Exception:
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: An error occurred while deploying the deployment item 'sap.com_EmployeeEar'.; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.com_EmployeeEar. Cannot deploy it.
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:836)
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
         at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
         at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:122)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: An error occurred while deploying the deployment item 'sap.com_EmployeeEar'.; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.com_EmployeeEar. Cannot deploy it.
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:187)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:48)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:178)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:77)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:726)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.com_EmployeeEar. Cannot deploy it.
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:102)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:93)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:59)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:158)
         ... 18 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.server.validate.jlin.JLinValidationException: [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.com/EmployeeEar application.
    ERRORS:
    Fields Properties Check: The persistent field 'serialVersionUID' in class 'com.sap.demo.entity.Employee' tagged as 'id' should be protected, package or private visibility and should not be final or static, file: EmployeeEjb.jar#META-INF/persistence.xml, column 0, line 0, severity: error * Fields Properties Check: The field 'serialVersionUID' in class 'com.sap.demo.entity.Employee' is tagged 'id', but is not persistent field according to the specification, file: EmployeeEjb.jar#META-INF/persistence.xml, column 0, line 0, severity: error
    Hint: 1) Given application file is not valid one.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4605)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:299)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:91)
         ... 21 more
    Caused by: com.sap.engine.services.deploy.server.validate.jlin.JLinValidationException: [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.com/EmployeeEar application.
    ERRORS:
    Fields Properties Check: The persistent field 'serialVersionUID' in class 'com.sap.demo.entity.Employee' tagged as 'id' should be protected, package or private visibility and should not be final or static, file: EmployeeEjb.jar#META-INF/persistence.xml, column 0, line 0, severity: error * Fields Properties Check: The field 'serialVersionUID' in class 'com.sap.demo.entity.Employee' is tagged 'id', but is not persistent field according to the specification, file: EmployeeEjb.jar#META-INF/persistence.xml, column 0, line 0, severity: error
    Hint: 1) Given application file is not valid one.
         at com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl.exec(JLinPluninImpl.java:95)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.validateApplication(DeployUtilTransaction.java:346)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:234)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:201)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:411)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2528)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:350)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:297)
         ... 22 more
    End of file

    I re-installed.

  • Unable to deploy Web App in Exploded format

    Using WLS 6.1 sp2, I am unable to deploy a web application successfully using the
    web app "ora" from http://www.thejspbook.com/examples.jspbook.zip. I've moved
    the /ora directory under the /WEB-INF/applications directory.
    The error I am getting is:
    java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException:
    Distributed Management [1 exceptions]
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:543)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy9.addDeployment(Unknown Source)
         at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
         at $Proxy18.setTargets(Unknown Source)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
         at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Distributed update exception
    - remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
    - remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
    - actionName: addDeployment
    - params: [Ljava.lang.Object;@10c03e
    - signature: [Ljava.lang.String;@3d4a20
    Distributed update exception
    - remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
    - remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
    java.lang.StringIndexOutOfBoundsException: String index out of range: -1
         at java.lang.String.substring(String.java:1525)
         at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:476)
         at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:232)
         at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3415)
         at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3384)
         at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
         at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:815)
         at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
         at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
         at weblogic.j2ee.Application.addComponent(Application.java:163)
         at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
         at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy34.addWebDeployment(Unknown Source)
         at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy9.addDeployment(Unknown Source)
         at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
         at $Proxy18.setTargets(Unknown Source)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
         at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.j2ee.DeploymentException: Could not load ora - with nested exception:
    [java.lang.StringIndexOutOfBoundsException: String index out of range: -1]
         at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:431)
         at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
         at weblogic.j2ee.Application.addComponent(Application.java:163)
         at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
         at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy34.addWebDeployment(Unknown Source)
         at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy9.--------------- nested within: ------------------
    weblogic.management.console.utils.SetException: An error occurred while updating
    Targets-Server on Proxy for efs-developer3:Application=ora,Name=ora,Type=WebAppComponent
    - with nested exception:
    [java.lang.reflect.InvocationTargetException - with target exception:
    [weblogic.management.DistributedManagementException: Distributed Management [1
    exceptions]]]
         at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:151)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Any help is appreciated.
    Thanks,
    Dennis

    you are probably using a older version of 6.1. please use the latest service pack. Service Packs are mostly bug fix releases and they are safe to be upgraded even on production systems. Please note - we always recommend using the latest service pack
    http://www.sun.com/download/products.xml?id=47d5d3eb

  • Error while deploying enterprise application on weblogic 11gr1(10.3.3)

    Hi folks,
    I got an error while starting an .ear file(ALRuleBean).
    weblogic.management.ManagementException: [Deployer:149188]No application named 'ALRuleBean' exists for operation start. Operation can not be performed until server is restarted.
    Please help me.

    Hi,
    Probably you have made some changes and trying to start the application.
    Can you try to restart the servers where the application has been targeted and start the server.
    If possible provide us the complete stack trace from the server logs, which will help us to know what exacting issue is.
    Good Day!!
    ~Ashish

  • Deploying web application in OAS Release 3 (10.1.3.1.0) in exploded format

    How to deploy a web application in exploded format in OAS server.

    Refer these:
    http://download.oracle.com/docs/cd/B31017_01/web.1013/b28221/depapp003.htm#JIEJB00906
    http://download.oracle.com/docs/cd/B31017_01/migrate.1013/b31269/servlets_weblogic.htm#i1018012
    Thanks
    Shail

  • J2ee Web application exploded format in oracle 10g

    Hi,
    I am trying to develop a simple j2ee application in Exploded Format
    in oracle 10g AS. i have created a new OC4J instance called
    TestOC4j for this. A .war file works fine in this instance.
    I have placed the application under applications directory of TestOC4j.
    I have made entries in server.xml, oc4j_mod.conf,
    default-web-site.xml,http-web-site.xml and application.xml in META-INF
    of the application.
    The application get deployed with no errors.gets created in
    application-deployments too.
    But the url http://server-ipaddress:7778/test_app is not working.
    Please help.
    The folder struture is as follows:
    test_app
    --META-INF
    -----application.xml
    --test_web
    -----pages
    -------welcome.jsp
    -----WEB-INF
    -------web.xml
    -------lib
    -------src
    The entries in server.xml is as follows:
    <application name="test_app" path="../applications/test_app" auto-start="true" />
    <web-site path="./http-web-site.xml" />
    The entries in application.xml is as follows :
    <module>
    <web>
    <web-uri>test_web</web-uri>
    <context-root>/test_app</context-root>
    </web>
    </module>
    The entries in default-web-site.xml is as follows:
    <web-app application="test_app" name="test_web" load-on-startup="true" root="/test_app" />
    The entries in http-web-site.xml is as follows:
    <web-app application="test_app" name="test_web" load-on-startup="true" root="/test_app" />
    The entries in oc4j_mod.conf is as follows:
    Oc4jMount /test_app TestOC4j
    Oc4jMount /test_app/* TestOC4j
    Regards,
    Roopa

    Roopa, it looks like there is no problem with the deployment of your application in exploded format. Have you accessed http://server-ipaddress:7778/test_app/pages/welcome.jsp? Any problem access http://server-ipaddress:7778/j2ee/, the default home page of the default-web-app ?
    When you say the url http://server-ipaddress:7778/test_app is not working, what is the error message if any on the browser, on server console, in the server.log and http-web-access.log of ORACLE_HOME/j2ee/home/log/, ORACLE_HOME/j2ee/home/application-deployments/test_app/application.log?

  • Bug in deploying in exploded format

              when i deploy my whole application in exploded format..the welcome page is not
              picking up from the web.xml file.is it a bug? if anybody knows,i would be appreciated
              if you reply me soon
              thanks
              Seri
              

    [att1.html]
              

  • Deploying Weblogic 8 EAR in exploded format

    Hello,
    Sorry, was lil away from WLS...
    Is there a way I can deploy EAR in the exploded directory structure which means all the WARs included in
    the EAR also need to be in exploded structure.
    Thanks

    I'm not sure I understand exactly what you want to know.
    You can deploy applications via the WebLogic Console, the command-line
    utility weblogic.Deployer, or the ant-task wldeploy.
    Any of these should work fine with an exploded ear.
    -- Rob
    A B wrote:
    Sorry Rob, I did not see the answer..
    What do I need to do to deploy WLS8 ear in exploded format?
    Thanks

  • Getting error while deploying the Enterprise application

    iam getting the Error while i deploying enterprise application which contain the EJB  methods.
    that Error iam getting like follow.
    java.rmi.RemoteException: Cannot deploy application sap.com/Energy_eap.. Reason: Incorrect application sap.com/Energy_eap:Error in the remote interface com.bean.Stateless_bean of bean Stateless_beanBean: No corresponding business method in the bean class com.bean.Stateless_beanBean was found for method Insert.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/Energy_eap:Error in the remote interface com.bean.Stateless_bean of bean Stateless_beanBean: No corresponding business method in the bean class com.bean.Stateless_beanBean was found for method Insert.Error in the remote interface com.bean.Stateless_bean of bean Stateless_beanBean: No corresponding business method in the bean class com.bean.Stateless_beanBean was found for method view.
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)

    Hello,
    based on the exception message there is a missing method in your ejb (insert)
    take a look at the signature of the method and the visibilty (public) - and look for typos
    regards franz
    ...close thread if question is answered

Maybe you are looking for