Deploying a Web Application in a Cluster

When accessing our web app through a cluster, the weblogic servers fail to recognize the servlets as registered in the web.xml file, but recognize them fine when registered in the cluster's weblogic.properties file. We had previously tested the app in a non-clustered enviroment and everything worked fine from the web.xml file. So... does anyone have any experience with this problem, or does anyone have any suggestions. All help is appreciated.Thanks,Chad

Chad Griffith wrote:
          > When accessing our web app through a cluster, the weblogic servers fail to recognize the servlets as registered in the web.xml file, but recognize them fine when registered in the cluster's weblogic.properties file.
          I am not quite sure I understand. Could you elaborate what you mean here?
          - Prasad
          > We had previously tested the app in a non-clustered enviroment and everything worked fine from the web.xml file. So... does anyone have any experience with this problem, or does anyone have any suggestions. All help is appreciated.Thanks,Chad
          Cheers
          - Prasad

Similar Messages

Error trying to deploy a jsp application in a cluster

          Iam getting the following error when I tried deploy my jsp app. in a cluster with
          two servers(one administrative and one managed). I have no problem with the administrative
          server. But the managed server through this exception. The message saying web.xml
          is not found doesn't make much sense because
          1. The first server could find it.
          2. I could open the temporary war file created by weblogic and examined the web.xml
          file
          Could not find Web application "D:\bea\wlserver6.0\.\config\mydomain\applications\.wl_temp_do_not_delete_myserver2\wl_local_comp31497.war">
          java.io.FileNotFoundException: WEB-INF/web.xml XML file not found in jar file
               at weblogic.servlet.internal.dd.DescriptorLoader.getInputSource(DescriptorLoader.java:206)
               at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:177)
               at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:468)
               at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
               at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
               at weblogic.j2ee.Application.addComponent(Application.java:126)
               at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:283)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:109)
               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:562)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
               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:437)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
               at $Proxy22.addWebDeployment(Unknown Source)
               at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:985)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:269)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:233)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:194)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:158)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
               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:437)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
               at $Proxy0.updateDeployments(Unknown Source)
               at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2299)
               at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:240)
               at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:122)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
               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:437)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
               at $Proxy8.start(Unknown Source)
               at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:435)
               at weblogic.management.Admin.startApplicationManager(Admin.java:1030)
               at weblogic.management.Admin.finish(Admin.java:491)
               at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
               at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
               at weblogic.Server.main(Server.java:35)
          Any ideas ?
          Thanks,
          Ravi


          Ravi wrote:
          > Hello Viresh,
          >
          > The application Iam trying to deploy is not in the ear form. It is in the exploded
          > form. It works fine on the administrative server where it is physically located.
          > The problem is only with the second server. I have noticed that the entire directory
          > on the application is being compressed to a .war file and uploaded to the other
          > server in the cluster.
          That's true. Several customers have asked to keep the deployment in it's original form instead of compressing
          it in .war file. Currently there's a known issue with engg.
          > I even examined the WEB-INF/web.xml file it is complaining
          > about. But I couldn't find any error. This doesn't happen with the sample applications
          > that came with weblogic.
          I followed the sequence you described and tried to deploy the webapp on managed servers. I do not get the errors
          that you are seeing below. Could you tell us how are you deploying the webapp on managed server?
          Also would you mind sending your webapp? i will see if i can deploy your webapp in my environment..
          BTW, is this with SP1 or without SP1?
          Kumar
          >
          >
          > Thank you for your post,
          > Ravi.
          >
          > Viresh Garg <[email protected]> wrote:
          > >
          > >Ravi:
          > >A few questions:
          > >1. Are you trying to deploy an archive or an exploaded application.
          > >2. Are you trying to deploy a web application as an enterprise application
          > >of the WAR file part of an enterprise archive(.ear)?
          > >3. Are you deploying the application from applications directory, if
          > >Yes, remove it from applications directory, create a new web application
          > >in any other directory, define the correct application/component Admin
          > >mbeans and then choose targets ( you can do it via console too) and
          > >see
          > >if you run into same problems
          > >
          > >Thanks
          > >Viresh Garg
          > >Principal Developer Relations Engineer
          > >BEA Systems
          > >Ravi wrote:
          > >
          > >> Iam getting the following error when I tried deploy my jsp app. in
          > >a cluster with
          > >> two servers(one administrative and one managed). I have no problem
          > >with the administrative
          > >> server. But the managed server through this exception. The message
          > >saying web.xml
          > >> is not found doesn't make much sense because
          > >> 1. The first server could find it.
          > >> 2. I could open the temporary war file created by weblogic and examined
          > >the web.xml
          > >> file
          > >>
          > >> Could not find Web application "D:\bea\wlserver6.0\.\config\mydomain\applications\.wl_temp_do_not_delete_myserver2\wl_local_comp31497.war">
          > >>
          > >> java.io.FileNotFoundException: WEB-INF/web.xml XML file not found in
          > >jar file
          > >> at weblogic.servlet.internal.dd.DescriptorLoader.getInputSource(DescriptorLoader.java:206)
          > >> at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:177)
          > >> at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:468)
          > >> at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
          > >> at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
          > >> at weblogic.j2ee.Application.addComponent(Application.java:126)
          > >> at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
          > >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:283)
          > >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:109)
          > >> 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:562)
          > >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
          > >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
          > >> 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:437)
          > >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          > >> at $Proxy22.addWebDeployment(Unknown Source)
          > >> at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:985)
          > >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:269)
          > >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:233)
          > >> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:194)
          > >> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:158)
          > >> at java.lang.reflect.Method.invoke(Native Method)
          > >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
          > >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
          > >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
          > >> 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:437)
          > >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          > >> at $Proxy0.updateDeployments(Unknown Source)
          > >> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2299)
          > >> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:240)
          > >> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:122)
          > >> at java.lang.reflect.Method.invoke(Native Method)
          > >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
          > >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
          > >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
          > >> 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:437)
          > >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          > >> at $Proxy8.start(Unknown Source)
          > >> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:435)
          > >> at weblogic.management.Admin.startApplicationManager(Admin.java:1030)
          > >> at weblogic.management.Admin.finish(Admin.java:491)
          > >> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
          > >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
          > >> at weblogic.Server.main(Server.java:35)
          > >>
          > >> Any ideas ?
          > >> Thanks,
          > >> Ravi
          > >

How to Deploy a web Application

Can Any one tell me the right procedure to Deploy A web Application on the server.
I have made the application using Html,Servlets,JSP,Java beans,web.xml
now I have lots of html,java class file
At this moment I have put all the classes file in \WEB-INF\CLASSES DIRECTORY, and the HTML file And the JSP in \WEB-INF directory
But it make the whole classes and WEB-INF directory populated with files.
Now Should I make a jar or war file and put on the
Can Anyone tell me the Correct method of deployment

http://ant.apache.org/manual/CoreTasks/war.html

Problems about deploying Oracle web application (Forms, Reports)

I am going to deploy Oracle web applications (Forms and Reports) and plan to use the same server machine for both Application web server and Database server.
1. How can I enable SSL (for data encryption) on Application web server for Oracle Forms ?
2. Since both Application web server and Database server will use the same machine, do I still need Oracle Advanced Security for data transmission between Application web server and Database server if data encryption for transmission is required ?
3. Can I user Oracle Forms to call Oracle Report on web as I did in Client/Server in the past ?
Experts like you may have come across such problems. Would you please give me some opinions/ideas ?
Regards,
Richard

1. check the paper about the Forms servlet architecture on otn forms section for SSL tips.
3. Check the reports and forms integration paper on otn too.

Deploying a web application on Sun One app server 7

Hi,
I am not able to deploy a web application on sun one server using Sun java studio.
I have created Jsp, Servlet, Session bean and entity bean.
When I am creating a web_module in the directory where JSP are kept, it is giving me error "directory is already mounted.
I have already created EJB modules for both the Session and entity bean.
Can some one tell me the cause / solution of this problem.

Hi Amol,
Thank you very much for replying my question. The contents in my application.xml are:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>testwsapp</display-name>
<description>J2EE Application testwsapp</description>
<module>
<web>
<web-uri>testws_War.war</web-uri>
<context-root>testws</context-root>
</web>
<alt-dd>testws_War.xml</alt-dd>
</module>
</application>
The contents in jaxrpc-ri-runtime.xml are:
<?xml version="1.0" encoding="UTF-8"?>
<endpoints xmlns='http://java.sun.com/xml/ns/jax-rpc/ri/runtime' version='1.0'>
<endpoint
name='testws'
interface='contactws.testwsGenServer.testwsRPC'
implementation='contactws.testwsGenServer.testwsRPCBean'
tie='contactws.testwsGenServer.testwsRPC_Tie'
model='null'
wsdl='/WEB-INF/testws.wsdl'
service='{urn:testws/wsdl}Testws'
port='{urn:testws/wsdl}testwsRPCPort'
urlpattern='/testws'
</endpoint></endpoints>
I tried to access and check the web service using:
http://servername:port/testws/testws
The first testws is contextroot named and the second testws is url pattern, which was exactly like what you mentioned but I got "404 Not Found" error.
By the way, using the same ear to deploy to Windows Sun ONE App. Server 7 env. and then using the same url, I can access the web service. I am wondering if there is any special for deploying Web Service on Unix Sun ONE app. Server 7 env. or I missed something?
I hope I can hear from you soon.
Thank you again,
Jackie

Problem deploying a web application (war)

Hello,
I am having a problem deploying a web application in Tomcat.
Here is what happens:
-I copied the war file into the webapps directory.
-I started Tomcat.
-Tomcat automatically expanded the war file into a directory of the same name.
The problem is that I get the following error: "The requested resource (/jadmin) is not available." when I try to access my web application
Can anyone please help?
Thanks in advance,
Balteo.

Hi,
check the Tomcat log file <tomcat_dir>/logs/localhost_log.yyyy-mm-dd.txt and see if there is an error corresponding to the deployement of the (/jadmin) context.

Packagin and Deploying Fusion Web Application

Hi,
I have created a Fusion web application which has Model and ViewController projects.
I have created a deployment profiles as below for each project.
1) Model - Which creates an "ADF Library Jar File"
2) ViewController - Which creates a "War" file.
I see that in the WAR file of ViewController contains the Model Projects - Entity Objects, ViewObjects and classes .
So for deploying my Web Applications is WAR file of ViewController is enough or Should I create a EAR file which has both #1 and #2
Thanks
Ajay

You sure can do in JDev. Select menu Application->'Application Properties', in the dialog select Deployment and the define a new EAR deployment profile. It's pretty easy to follow the instructions in the dialog and your are done.
Timo

Deployment of Web application containing only Servlets

I want to deploy my web application on Weblogic which contains only servlets
          and html files.
          All I know is that I have to write the DTD file. Once i am done with the DTD
          file i do not how the further steps to deploy my web application.
          can somebody point out the steps or some site where i can get any help. Is
          this documented anywhere?
          thanks in advance,
          Nitin


Hi
          You don't write DTD file. It's in weblogic installation.
          You must write a web.xml file and weblogic.xml file. See how to do this in
          the documento "Write Web Applications" of WebLogic 5.1
          nitin <[email protected]> escribió en el mensaje de noticias
          [email protected]..
          > I want to deploy my web application on Weblogic which contains only
          servlets
          > and html files.
          >
          > All I know is that I have to write the DTD file. Once i am done with the
          DTD
          > file i do not how the further steps to deploy my web application.
          >
          > can somebody point out the steps or some site where i can get any help. Is
          > this documented anywhere?
          >
          > thanks in advance,
          > Nitin
          >
          >

Deployment of Web application

Using: WebLogic 6.1 SP3 (J2EE 1.3)
I have an application which consists of an EJB JAR file and a WAR file which I used to deploy to JBoss and Tomcat respectively. They are working fine in that environment. I want to deploy this application to WebLogic 6.1 SP3.
1. I generated another JAR file which can be deployed to WebLogic using ejbc (after adding weblogic-ejb-jar.xml file). It went fine and I moved this JAR to weblogic/config/examples/applications folder. I saw in the log file that the EJB's in that JAR file were successfully deployed.
2. The problem happened when I moved the WAR file to weblogic/config/examples/applications folder. It tried to deploy the web application, but threw an error. These are the messages from the log.
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101053> <[HTTP examplesServer] Loading web app: cronus>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101060> <[examplesServer] Loading "cronus" from directory: "d:\bea\weblogic61\wlserver6.1\config\examples\applications\cronus">
<Warning> <J2EE> <europa> <examplesServer> <main> <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1 is of a non-final version of the appropriate specification. It is subject to change in future releases once the specification becomes finalized. This may cause application code developed for BEA WebLogic Server 6.1 that uses the new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in future releases of BEA WebLogic Server.>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101031> <[WebAppServletContext(4192856,cronus,/cronus)] extracting classfiles to d:\bea\weblogic61\wlserver6.1\config\examples\applications\cronus\WEB-INF\_tmp_war_cronus:>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101032> <[WebAppServletContext(4192856,cronus,/cronus)] extracted classfiles successfully...>
<Info> <HTTP Session> <europa> <examplesServer> <main> <system> <> <100037> <Creating SessionContext of type: memory for webapp: /cronus>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101047> <[WebAppServletContext(4192856,cronus,/cronus)] registering classpath servlet with initArgs 'null'>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101047> <[WebAppServletContext(4192856,cronus,/cronus)] registering getior servlet with initArgs 'null'>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101047> <[WebAppServletContext(4192856,cronus,/cronus)] registering tunneling servlets with initArgs 'wl-dispatch-policy=direct'>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101047> <[WebAppServletContext(4192856,cronus,/cronus)] registering JSPServlet with initArgs '[JspConfig: verbose=true,packagePrefix=jsp_servlet,-compiler=d:\bea\weblogic61\jdk131/bin/javac,compileFlags=,workingDir=d:\bea\weblogic61\wlserver6.1\config\examples\applications\cronus\WEB-INF\_tmp_war_cronus,pageCheckSeconds=1,superclass=weblogic.servlet.jsp.JspBase,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
<Error> <Management> <europa> <examplesServer> <main> <system> <> <141042> <Error deploying application d:\bea\weblogic61\wlserver6.1\config\examples\applications\cronus: java.lang.reflect.UndeclaredThrowableException>
My web app directory structure is like this
cronus -----------------------> JSP files
WEB-INF ---------------> web.xml
lib ----------------------> all the JAR files (including EJB JAR and JSTL implementation and other reusable JARs)
classes --------------> all the servlet/web app classes
tlds --------------------> TLD files
Any suggestions on how can I fix this?
I appreciate your help.
Thanks.
Velmurugan.
[att1.html]

I tried to deploy the web application in exploded format. But I got the same error.
"Vel Periasamy" <[email protected]> wrote in message news:[email protected]...
Using: WebLogic 6.1 SP3 (J2EE 1.3)
I have an application which consists of an EJB JAR file and a WAR file which I used to deploy to JBoss and Tomcat respectively. They are working fine in that environment. I want to deploy this application to WebLogic 6.1 SP3.
1. I generated another JAR file which can be deployed to WebLogic using ejbc (after adding weblogic-ejb-jar.xml file). It went fine and I moved this JAR to weblogic/config/examples/applications folder. I saw in the log file that the EJB's in that JAR file were successfully deployed.
2. The problem happened when I moved the WAR file to weblogic/config/examples/applications folder. It tried to deploy the web application, but threw an error. These are the messages from the log.
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101053> <[HTTP examplesServer] Loading web app: cronus>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101060> <[examplesServer] Loading "cronus" from directory: "d:\bea\weblogic61\wlserver6.1\config\examples\applications\cronus">
<Warning> <J2EE> <europa> <examplesServer> <main> <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1 is of a non-final version of the appropriate specification. It is subject to change in future releases once the specification becomes finalized. This may cause application code developed for BEA WebLogic Server 6.1 that uses the new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in future releases of BEA WebLogic Server.>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101031> <[WebAppServletContext(4192856,cronus,/cronus)] extracting classfiles to d:\bea\weblogic61\wlserver6.1\config\examples\applications\cronus\WEB-INF\_tmp_war_cronus:>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101032> <[WebAppServletContext(4192856,cronus,/cronus)] extracted classfiles successfully...>
<Info> <HTTP Session> <europa> <examplesServer> <main> <system> <> <100037> <Creating SessionContext of type: memory for webapp: /cronus>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101047> <[WebAppServletContext(4192856,cronus,/cronus)] registering classpath servlet with initArgs 'null'>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101047> <[WebAppServletContext(4192856,cronus,/cronus)] registering getior servlet with initArgs 'null'>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101047> <[WebAppServletContext(4192856,cronus,/cronus)] registering tunneling servlets with initArgs 'wl-dispatch-policy=direct'>
<Info> <HTTP> <europa> <examplesServer> <main> <system> <> <101047> <[WebAppServletContext(4192856,cronus,/cronus)] registering JSPServlet with initArgs '[JspConfig: verbose=true,packagePrefix=jsp_servlet,-compiler=d:\bea\weblogic61\jdk131/bin/javac,compileFlags=,workingDir=d:\bea\weblogic61\wlserver6.1\config\examples\applications\cronus\WEB-INF\_tmp_war_cronus,pageCheckSeconds=1,superclass=weblogic.servlet.jsp.JspBase,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
<Error> <Management> <europa> <examplesServer> <main> <system> <> <141042> <Error deploying application d:\bea\weblogic61\wlserver6.1\config\examples\applications\cronus: java.lang.reflect.UndeclaredThrowableException>
My web app directory structure is like this
cronus -----------------------> JSP files
WEB-INF ---------------> web.xml
lib ----------------------> all the JAR files (including EJB JAR and JSTL implementation and other reusable JARs)
classes --------------> all the servlet/web app classes
tlds --------------------> TLD files
Any suggestions on how can I fix this?
I appreciate your help.
Thanks.
Velmurugan.
[att1.html]

Deployment of Web Application when the managed Server is down .....

Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

This is currently being fixed in 7.0 line, contact [email protected] and reference
CR110687
Cheers
mbg
"Selvamohan Neethiraj" <[email protected]> wrote in message news:[email protected]..
Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

Please help, how to guide the user to deploy a web application easily.

hello,
i have created an application which creates a new web application every time it is run. now i am writing the documentation of it and dont know which web server the client may have so i have to write / show to the user general steps that he should follow to deploy the web application after it has been created.
i have written that the user should deploy the web app by making the following entry into the server.xml file (for tomcat)
<Context path="/webappname" docBase="webapppath"></Context>
it is not compulsary that the user should place the web application in the webapps directory of the server hence the above webapppath is used.
now i want to indicate to him where and before / after which tag and under which host name etc the above line should be added in a manner that he is able to do it properly.
please anyone can help me how to do it.

i would like to know if there is any way without Java web start.
it has to be set manually.
i.e every user should make this entry in the server.xml so that the context is set.

Deploy JRC web application on Sun Solaris

<p>Hi everyone,</p><p>How can i deploy my web application including the JRC on a Sun solaris OS?.</p><p>Can anyone help me?</p><p> Thanks</p>

<p>This is pretty easy.</p><p>1. Get a Java Application Server running on Sun Solaris</p><p>2. Create a WAR file containing the JRC. (WAR files for Solaris are no different than windows)</p><p><a href="http://technicalsupport.businessobjects.com/KanisaSupportSite/search.do?cmd=displayKC&docType=kc&externalId=c2014756&sliceId=&dialogID=14310478&stateId=1%200%2014312298">CLICK HERE for instructions to make a war file</a> </p><p>3. Deploy that WAR file to the App server on the Sun Solaris Box. </p><p>Rob Horne<br /><a href="/blog/10">Rob's blog - http://diamond.businessobjects.com/blog/10</a></p>

How to deploy my web application .war file into SAP netweaver Engine

Hi All,
I want to deploy web application which is developped using JAVA web technology into SAP netweaver Engine.
I tried to deploy .war file through SDM but it complained the following error
"Error loading archive
C;\Document and Settings\cr1adm\Desktop\MyProject.war
(server side name is: F:\usr\sap\JR1\JC01\SDM\program\temp\MyProject.war)
com.sap.sdm.util.sduread.IIIFormattedSduFileException: The information about development component found in the manifest is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
attribute keylocation missing
attribute keyname is missing
attribute keyvendor is missing
attribute keycounter is missing
(F:\usr\sap\JR1\JC01\SDM\program\temp\MyProject.war)"
Can any one please suggest how to deploy external web application into SAP netweaver engine.
Is there any procedure to follow to do this.
your inputs will be highly appreciated...
Thanks in advance
JM

You may need to convert the .war archive to SDA/SCA file format before deploying it to SAP Netweaver Engine.
Check out the below SAP NOTE if it is usefull.
Note 1223957 - Usage of NetWeaver Packaging Tool.
Apart from SDM you can also deploy the files through telnet...
Note 859444 - How to deploy libraries on J2EE Engine 6.40
1)Connect to telnet as below
Start --> Run
telnet hostname/ip address portno
Ex: telnet xxx.xx.xx.x 5<Instance no>08
2)Login with administrator id:
Use the below command to deploy the files.
deploy <directory path to the SDAs location> version_rule=all on_prerequisite_error=stop on_deploy_error=stop
Example: deploy E:\usr\sap\trans\EPS\in\VCBASE03_0-10006939.SCA version_rule=all on_prerequisite_error=stop on_deploy_error=stop.
Also have a look at this note which talks about the error you are getting.
Note 1171457 - IllFormattedSduManifest/SduFileException during deployment
Hope it helps.
Edited by: Khaiser Khan Mohammed on Nov 7, 2010 12:17 PM

Deploying Java Web Application (WAR-File) into a cluster environment

Hi,
we have a web application which has to read from and write to the file system.
Since a short time we have a cluster environment (2 parallel servers) and since thisa time we have the problem, that files are worked double in the cluster. The application is working on both servers now and so we have this problem.
Does anybody know how we have to deploy the application correctly in a cluster environment or do we have to change anything in our source code of the application?
I didn't find any documentation about this.
At the moment we have deployed the application on one of the two servers only, but I think there must be a better way to solve this problem.
Thanks for your replies.
Regards
Thorsten

Hi,
I think first you need to wrap it into an EAR file, then you can deploy it.
As far as I know standalone deployment of WAR is deprecated as of 640.
similar threads:
How to deploy .war on NWDI
Deploying an existing WAR file into the Portal
Hopefully this tutorial also gives some idea:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/70/13353094af154a91cbe982d7dd0118/frameset.htm
Regards,
Ervin

Problem While Deploying Java Web Application(Struts,Hiber) on NetWeaver 7.3

Hi
Fortunately i had a requirement to deploy my project JAVA (Struts, Hiber, DOJO)web application build as war file using Eclipse 3.4 on SAP Net Weaver 7.3
Its showing in the Deployed Components List of NetWeaver ...
When i tried to open the home page i found an exception ...
The following is the log file content ... Hope its something related to hibernate ...
>deploy s:\usr\sap\trans\EPS\in\LMSDemo.war on_deploy_error=stop
Converting s:\usr\sap\trans\EPS\in\LMSDemo.war to sda
s:\usr\sap\trans\EPS\in\LMSDemo.war has been successfully converted to sda
Deploy settings:
life_cycle=bulk
on_deploy_error=stop
on_prerequisite_error=stop
version_rule=lower
workflow=normal
If there is an offline deployment, Telnet connection to host may be lost, but th
e result can be seen using get_result command
Processing deployment operation, wait...
===== PROGRESS START =====
Deploying JavaEE_LMSDemo (sda) ...
Deployment of JavaEE_LMSDemo (sda) finished.
===== PROGRESS END =====
===== DEPLOY RESULT =====
sdu id: JavaEE_LMSDemo
sdu file path: [S:\usr\sap\N73\J10\j2ee\cluster\server0\temp\tcbldeploy_contro
ller\archives\31\263890545832850\SDA\LMSDemo.war]
version status: NEW
deployment status: Warning
description: [
1. Warning exception has been returned while the [] was starting. Warnings:[
Warning occurred on server 102466650 during startApp of JavaEE/LMSDemo : com.sap
.ASJ.web.000607 (Failed in component: JavaEE/LMSDemo, ) Initialization of servle
t action failed. Check init() method of servlet. Error is: [javax.servlet.Unav
ailableException: org/slf4j/LoggerFactory]
===== END DEPLOY RESULT =====
===== Summary - Deploy Result - Start =====
Type | Status : Count
> SCA(s)
> SDA(s)
- Warning : [1]
Type | Status : Id
> SCA(s)
> SDA(s)
- Warning : JavaEE_LMSDemo,
===== Summary - Deploy Result - End =====
>
Does anyone knows this ..

In your deploy message it says that it can't initialize your servlet because it is missing a java class from the logging framework that is used by hibernate. It might also be possible that that logging framework ([SL4J|http://www.slf4j.org/]) is configured to use a logger that is not available in your Netweaver 7.3 installation. Maybe check the documentation of sl4j for details. There is also a [document|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/bf0d57db-0c01-0010-6fa3-83503981eed4] about Hibernate on Netweaver but that was back when Hibernate did not use sl4j. Probably you just need to add the sl4j library to your libs.

Deploying a Web Application in a Cluster

Similar Messages

Maybe you are looking for