I cann't deploy SRDemoSampleADFBC sample on Tomcat

I'm using Apache Tomcat 5.5.16 and I'm trying to deploy SRDemoSampleADFBC sample but I getting folowing error trace:
INFO: Deploying web application archive SRDemoSampleADFBC.war
Apr 10, 2006 12:54:41 PM org.apache.tomcat.util.digester.Digester endElement
SEVERE: End event threw exception
java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.apache.tomcat.util.IntrospectionUtils.callMethod1(IntrospectionUtils.java:898)
 at org.apache.tomcat.util.digester.SetNextRule.end(SetNextRule.java:192)
 at org.apache.tomcat.util.digester.Rule.end(Rule.java:228)
 at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1057)
 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1310)
 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:328)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:295)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
 at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1561)
 at org.apache.catalina.startup.ContextConfig.applicationWebConfig(ContextConfig.java:351)
 at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1034)
 at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:260)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4118)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
 at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:809)
 at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:698)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1112)
 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
 at org.apache.catalina.core.StandardService.start(StandardService.java:450)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.lang.IllegalArgumentException: Invalid <url-pattern> faces/app/management/* in security constraint
 at org.apache.catalina.core.StandardContext.addConstraint(StandardContext.java:1971)
 ... 40 more
Apr 10, 2006 12:54:41 PM org.apache.catalina.startup.ContextConfig applicationWebConfig
SEVERE: Parse error in application web.xml file at jndi:/localhost/SRDemoSampleADFBC/WEB-INF/web.xml
java.lang.IllegalArgumentException: Invalid <url-pattern> faces/app/management/* in security constraint
 at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2725)
 at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2751)
 at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1060)
 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1310)
 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:328)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:295)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
 at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1561)
 at org.apache.catalina.startup.ContextConfig.applicationWebConfig(ContextConfig.java:351)
 at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1034)
 at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:260)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4118)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
 at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:809)
 at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:698)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1112)
 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
 at org.apache.catalina.core.StandardService.start(StandardService.java:450)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Apr 10, 2006 12:54:41 PM org.apache.catalina.startup.ContextConfig applicationWebConfig
SEVERE: Occurred at line 91 column 25
Can somebody give me some hints?

Hi,
I have same and resolution with your information.
But after we have other problem when see page SRWelcome.jsp we have this error :
Failed to checkout SRService application module. Ensure your datasource name is SRDemo [case-sensitive!] and that connection settings are properly defined for a database with the SRDEMO schema installed. See server log for more exception details...
Where is problem ?
Regards,
Alfredo Queiros

Similar Messages

Issues in Deploying the Sample code

Hi,
I downloaded BusinessObjects Enterprise Java SDK Sample Code from SDK Developer Library. I unzipped the content to a folder(Sample) in tomcat/webapps. Now when I launched the application using the following url http://localhost:8080/Sample/start.jsp
I am getting the following error.
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
Only a type can be imported. com.crystaldecisions.sdk.exception.SDKException resolves to a package
Generated servlet error:
Only a type can be imported. com.crystaldecisions.sdk.framework.CrystalEnterprise resolves to a package
Generated servlet error:
Only a type can be imported. com.crystaldecisions.sdk.framework.IEnterpriseSession resolves to a package
Generated servlet error:
Only a type can be imported. com.crystaldecisions.sdk.framework.ISessionMgr resolves to a package
An error occurred at line: 36 in the jsp file: /start.jsp
Generated servlet error:
ISessionMgr cannot be resolved to a type
An error occurred at line: 36 in the jsp file: /start.jsp
Generated servlet error:
CrystalEnterprise cannot be resolved
     org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:512)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Please let me know whether I have to do any configuration to make this application running.
Thanks and Regards,
Subbu S

You can find the neccessary jar files here:
C:Program FilesBusiness ObjectsCommon4.0javalib
Check the developer guide for guidance on exactly which jars are required:
https://www.sdn.sap.com/irj/boc/sdklibrary
BusinessObjects Enterprise Java SDK > Developer Guide > Setting up the development environment > Web application setup > JAR files needed for deployment of Business Objects Software

Jar not loaded Error when deploying weblogic.jar in tomcat

Hi experts,
This time i have one more problem,
i have deployed my application in tomcat such that when tomcat starts my java program also gets started, for my java program i had to use a weblogic library which is in "web-inf / lib / weblogic.jar" . but when i start tomcat i get error like
INFO: validateJarFile (C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\MyApp\WEB-INF\lib\weblogic.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Dec 4, 2006 8:27:18 PM org.apache.catalina.core.StandardPipeline registerValve
INFO: Can't register valve org.apache.catalina.core.StandardContextValve@1362012
org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@1bc82e7 for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category) (Caused by org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@1bc82e7
for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category))
 at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
what could be the problem in loading weblogic.jar
my platform configuations are
TOMCAT 5.5
OS - windows 2000

 have u done the servlet naminga and mapping in the web.xml file??
 Kumar Allamraju <[email protected]> wrote:
 ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 ><html>
 >Have you registered the servlet in web.xml?
 >--
 > Kumar
 >Deepak Balakrishna wrote:
 ><blockquote TYPE=CITE>Hi.
 >I am having trouble deploying a servlet to WLS 6.1
 >a) The name of the servlet is HaServlet and it's duly noted in web.xml
 > b) I created a directory
 > config/examples/applications/cluster-servlet/WEB-INF
 > c) Added web.xml under WEB-INF/. web.xml was created using the weblogic
 > DDInit CLI
 > d) Added the servlet classfile (HaServlet.class) under
 > WEB-INF/classes/samples/cluster/servlet/.
 > e) Tried to access it by http://host:port/cluster-servlet/HaServlet
 >I get
 > Error 404--Not Found
 >What am I missing? I also tried restarting the app server to no avail.
 >Thx,
 > - deepak</blockquote>
 ></html>
 >

Problem with packageing and deploying a sample application

HI,
I have tried to download and install the server in my system. I am able to deploy a sample application using autodeploy utility.
But when i tried to package a new sample application and deploy i am getting 404 error. For application server i have used 7070 port and not the default 8080 port will this a problem to package & deploy sample application provided with this software.
The error is as below:
HTTP Status 404 - /hello1
type Status report
message /hello1
description The requested resource (/hello1) is not available.
Sun-Java-System/Application-Server

Btw, verify that the url you are trying to access is correct. For instance, assuming you deploy app. without --contextroot option. By default, the url is http://<host>:<port>/<web module name>/<value of url-pattern in web.xml> if your app contains servlet. If your app has jsp then it's http://<host>:<port>/<web module name>/<value of url-pattern in web.xml>/<name of jsp>

Problem to deploy ADF application on tomcat server

Hi all,
i 'm using this tutorial link to deploy adf application on tomcat server.
https://blogs.oracle.com/dana/entry/how_to_deploy_a_11g_adf_applic_1
but when i have run my application i have got following error
java.sql.SQLException: invalid arguments in call
log-
Jul 29, 2013 11:35:16 AM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_04-b07-FCS) for context '/TestApacheApp_ViewController_webapp1'
Jul 29, 2013 11:35:19 AM oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack contextInitialized
SEVERE: ADFConnection mbean not registered for defaultApplicationName.
Jul 29, 2013 11:35:19 AM oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack contextInitialized
SEVERE:
oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
at oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack.contextInitialized(ADFConnectionLifeCycleCallBack.java:82)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:515)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1231)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1471)
at org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:243)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:857)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:565)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1509)
at java.lang.Thread.run(Thread.java:662)
Jul 29, 2013 11:35:19 AM oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack contextInitialized
SEVERE: Failed to register config mbean for defaultApplicationName.
Jul 29, 2013 11:35:19 AM oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack contextInitialized
SEVERE:
oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
at oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack.contextInitialized(ADFConfigLifeCycleCallBack.java:79)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:515)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1231)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1471)
at org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:243)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:857)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:565)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1509)
at java.lang.Thread.run(Thread.java:662)
Jul 29, 2013 11:35:19 AM oracle.bc4j.mbean.BC4JConfigLifeCycleCallBack contextInitialized
SEVERE: Not able to get Deployment Name
Jul 29, 2013 11:35:28 AM oracle.adfinternal.controller.state.ControllerState initializeRequest
WARNING: ADFc: Deserialization of session state detected but ADF scope HA support is not enabled. Please enable ADF scope HA support in the adf-config.xml file to ensure correct functioning of your applicaiton.
Jul 29, 2013 11:35:28 AM oracle.adf.share.http.ServletADFContext initialize
WARNING: Found wrong applictionScope sticking to oldContext for oldApplication defaultApplicationName, while the current one is null
Jul 29, 2013 11:35:28 AM oracle.jbo.uicli.mom.CpxUtils$Visitor logMainApplicationCpx
INFO: jndi:/localhost/TestApacheApp_ViewController_webapp1/WEB-INF/classes/com/in/jagran/view/DataBindings.cpx
Jul 29, 2013 11:35:28 AM oracle.adf.share.jndi.MDSBackingStore documentExists
INFO: MDS-00013: no metadata found for metadata object "/META-INF/connections.xml"
Jul 29, 2013 11:35:32 AM oracle.adf.share.http.ServletADFContext initialize
WARNING: Found wrong applictionScope sticking to oldContext for oldApplication defaultApplicationName, while the current one is null
Jul 29, 2013 11:35:33 AM oracle.adf.share.http.ServletADFContext initialize
WARNING: Found wrong applictionScope sticking to oldContext for oldApplication defaultApplicationName, while the current one is null
Jul 29, 2013 11:35:47 AM org.apache.coyote.http11.Http11AprProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8086
Jul 29, 2013 11:35:47 AM org.apache.coyote.ajp.AjpAprProtocol pause
INFO: Pausing Coyote AJP/1.3 on ajp-8009
Jul 29, 2013 11:35:48 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Jul 29, 2013 11:35:48 AM org.apache.coyote.http11.Http11AprProtocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8086
Jul 29, 2013 11:35:48 AM org.apache.coyote.ajp.AjpAprProtocol destroy
INFO: Stopping Coyote AJP/1.3 on ajp-8009

There is no guideline I know of as this depends on the app itself.
What you should do is to deploy the application onto a test server and check the metrics of the app over a defined period of time with a defined amount of traffic.
Timo

Error targeting server for the EJB module while deploying the sample banking application

I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
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 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 $Proxy11.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 $Proxy68.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:2495)
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)

The deployment process invokes javac internally to compile some generated classes.
Do you have javac installed and in the path?
Seth
Scott Springer wrote:
I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
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 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 $Proxy11.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 $Proxy68.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:2495)
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)

How to deploy EAR file in Tomcat?

Is we can deploy ear file in tomcat?
Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
But samethink I have tried EAR file. But it is not working.
Is we can deploy EAR file or not?
If not plz give reason.

Hi
Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
The Tomcat Servlet/JSP Container
The Apache Tomcat 5.5 Servlet/JSP Container
 Apache Logo
Links
* Docs Home
Contents
* Contents
* Introduction
* Installation
* Deployment
* Source Code
* Processes
* Example App
Application Developer's Guide
Deployment
 Printer Friendly Version
print-friendly
version
Background
Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
Standard Directory Layout
To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
* *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
* /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
* /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
* /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
Shared Library Files
Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
* $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
* $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
* The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
* An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
Web Application Deployment Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
Tomcat Context Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
Deployment With Tomcat 5
In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
* Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
* Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
* Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
* Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
* Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
Copyright © 1999-2006, Apache Software Foundation

It´s possible deploy ADF Demo in Tomcat 6 ???

Hi.
I deploy the ADF Demo (http://www.oracle.com/technetwork/developer-tools/adf/downloads/index.html), in Weblogic 10.3.3.
But I´m triying to deploy the war demo, in tomcat. But i can´t.
It´s possible deploy this application??. I Think that is possible because it´s a war proyect.
Thanks

It may be possible, but it's not supported. If you have a search of the forums, you can find people who have, with varying degrees of success, managed to deploy ADF projects to Tomcat.
John

Deploying war file on Tomcat: file path problem

Hello all,
i am using my eclipse ide for automatically deploy my webapplication to Tomcat. For Database connectivity i configured hibernate. To configure hibernate i am using the following code:
package de.wfm.hibernate.hibernateUtil;
import org.hibernate.HibernateException;
import org.hibernate.Session;
import org.hibernate.SessionFactory;
import org.hibernate.cfg.Configuration;
public class ESDBFactory {
     private static SessionFactory sf;
     private static Session session = null;
     private static String pathToCfgFile = "de\\"
                         + "wfm\\hibernate\\hibernateUtil\\esdb.cfg.xml";
     public static synchronized Session getSession() throws HibernateException {
          if (session==null) {
               if (sf==null) {
                    sf = new Configuration()
                         .configure(pathToCfgFile).
                         buildSessionFactory();
          session = sf.openSession();
          return session;
}When i use this in the ide all is fine. But when i export my application to a war file and deploy it on Tomcat i got the exception:
2006-07-28 10:06:10 StandardWrapperValve[Urlaubsplanung Servlet]: Servlet.service() for servlet Urlaubsplanung Servlet threw exception
javax.faces.FacesException: #{User.doLogin}: javax.faces.el.EvaluationException: org.hibernate.HibernateException: de\wfm\hibernate\hibernateUtil\esdb.cfg.xml not foundHow to avoid this? What do i have to do to set the file path correctly?
Regards,
ak

hmm.. ic
The .war file when drop in the webapps dir and u restart tomcat, it auto create a dir with your .war filename and the content of .war file is copied to there.
Am i rite to say so?
And wat about the web.xml?
If i need to add users and password how can I accomplished it in tomcat web.xml?
Last but not least, thanks for taking the time to reply. :D

Error in Weblogic server while deploying a sample cartridge

hi all
I am getting below error while deploying a sample cartridge to the web logic.
####<Jun 27, 2012 4:32:40 PM GMT+05:30> <Warning> <cartridgemanagement> <ww021006> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1340794960399> <BEA-000000> <adapter.CartridgeManagementAdapterFactoryRegistry: Cannot locate adpater oracle.communications.sce.cartridgemanagement.adapter.OSM>
####<Jun 27, 2012 4:32:43 PM GMT+05:30> <Error> <cartridgemanagement> <ww021006> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1340794963321> <BEA-000000> <ws.CartridgeManagementWSPortImpl: While trying to lookup 'oracle.communications.sce.cartridgemanagement.adapter.OSM' didn't find subcontext 'sce'. Resolved 'oracle.communications'>
####<Jun 27, 2012 4:32:43 PM GMT+05:30> <Info> <cartridgemanagement> <ww021006> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1340794963743> <BEA-000000> <ws.CartridgeManagementWSPortImpl: getCartridgeList>
####<Jun 27, 2012 4:32:43 PM GMT+05:30> <Warning> <cartridgemanagement> <ww021006> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1340794963899> <BEA-000000> <adapter.CartridgeManagementAdapterFactoryRegistry: Cannot locate adpater oracle.communications.sce.cartridgemanagement.adapter.Activation>
####<Jun 27, 2012 4:32:44 PM GMT+05:30> <Info> <cartridgemanagement> <ww021006> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1340794964149> <BEA-000000> <ws.CartridgeManagementWSPortImpl: getCartridgeList>
####<Jun 27, 2012 4:32:44 PM GMT+05:30> <Warning> <cartridgemanagement> <ww021006> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1340794964305> <BEA-000000> <adapter.CartridgeManagementAdapterFactoryRegistry: Cannot locate adpater oracle.communications.sce.cartridgemanagement.adapter.Inventory>
####<Jun 27, 2012 4:32:45 PM GMT+05:30> <Info> <cartridgemanagement> <ww021006> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1340794965508> <BEA-000000> <ws.CartridgeManagementWSPortImpl: getCartridgeList>
####<Jun 27, 2012 4:32:45 PM GMT+05:30> <Warning> <cartridgemanagement> <ww021006> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1340794965649> <BEA-000000> <adapter.CartridgeManagementAdapterFactoryRegistry: Cannot locate adpater oracle.communications.sce.cartridgemanagement.adapter.OSM>

issue is resolved now.

Is it possible to deploy Web Services to Tomcat?

Good day,
Can anybody tell me or it is possible to deploy Web Services to Tomcat 5.5.x ? It is possble for ADF, so I was wondering or it is possble for Web Services.
I tried to deploy it with the following libraries:
J2EE (excluding the servlet.jar using the filter, while this package is already present in Tomcat)
Oracle SOAP
Struts Runtime
JSP Runtime
and manually added as library:
wsserver.jar
wsdl.jar
WebServicesHtmlXmlWizard.jar
The situation at this moment is that after deployment, and execution by the a http browser the http request screens shows up as expected (I have been used Embedded stubs), but after sending I get a:
28-Sep-2005 11:03:36 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet MyWebService1 threw exception
java.lang.NoClassDefFoundError: oracle/aurora/ncomp/java/ClassNotFound
     at oracle.j2ee.ws.StatelessJavaRpcWebService.getGenerator(StatelessJavaRpcWebService.java:28)
     at oracle.j2ee.ws.RpcWebService.generateWrapperClass(RpcWebService.java:461)
     at oracle.j2ee.ws.RpcWebService.generate(RpcWebService.java:414)
     at oracle.j2ee.ws.RpcWebService.getWrapper(RpcWebService.java:532)
     at oracle.j2ee.ws.RpcWebService.doGetRequest(RpcWebService.java:631)
     at oracle.j2ee.ws.BaseWebService.doGet(BaseWebService.java:1173)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Unknown Source)
Any sugestions? Or is there a different behaviour between Oracle en Tomcat version caused by modifications from the apache source.
I should appreciate it to get some more details about this issue.

JDeveloper will only directly support deployment of web services to an Apache 2.2 Web Server.

Error message Deploying the sample HRapp using OBE

I a novice to 9ias and I am using the OBE documents to get hands on on the Oracle 9ias. I tried to deploy the sample hrweb following the OBE document and encountered the error below. I need some help as to what to do next to correct this situation.
On installation, I have the J2EE and webcache on one host and the infrastructure and database on another host.
Here is the error message:
Deployment failed: Nested exception Root Cause: Error loading web-app 'hrweb' at D:\Oracle9iAS\j2ee\home\applications\__hrapp\hrweb: Unknown assembly tag in file:/D:/Oracle9iAS/j2ee/home/applications/__hrapp/hrweb/: <ejb-local-ref>; nested exception is: java.lang.InstantiationException: Error loading web-app 'hrweb' at D:\Oracle9iAS\j2ee\home\applications\__hrapp\hrweb: Unknown assembly tag in file:/D:/Oracle9iAS/j2ee/home/applications/__hrapp/hrweb/: <ejb-local-ref>. Error loading web-app 'hrweb' at D:\Oracle9iAS\j2ee\home\applications\__hrapp\hrweb: Unknown assembly tag in file:/D:/Oracle9iAS/j2ee/home/applications/__hrapp/hrweb/: <ejb-local-ref>; nested exception is: java.lang.InstantiationException: Error loading web-app 'hrweb' at D:\Oracle9iAS\j2ee\home\applications\__hrapp\hrweb: Unknown assembly tag in file:/D:/Oracle9iAS/j2ee/home/applications/__hrapp/hrweb/: <ejb-local-ref>

Hi,
<ejb-local-ref> tag is used to reference an entity bean that has a local home and local interface. <ejb-local-ref> tag is supported in EJB 2.0 and later versions. Looking at the error message it appears that the container you are using does not support EJB 2.0.
Which version of 9iAS are you using?
Thanks

Deploying oracle forms in tomcat

dear all,
i developed a small application using oracle Forms 10g that it s okay under OC4J and i d like to deploy it in a tomcat container installed as a standalone web server or in apache web server , can you lead me to a blueprint document that shows how can I achieve that?
thanks in advance

than u sir for the reply,rihgtnow the application i developed can be accessed by a browser located on in a remote site whithout any form runtime installed on the client,but at the central site where the formas reside , the OC4j container is running to listen to the client request.
thanks again

[Sun Federation Manager] Error deploying a sample

Hi all,
I'm currently working on the sun java system federation manager and I simply try to deploy a sample, as written in the readme file. The readme.txt tells that :
1. Update sp1Metadata.xml (available in <sample_xml_dir>)
The following assumptions are made in sp1Metadata.xml.
a. IDP1_PROTO is the protocol for IDP1, eg. http.
b. IDP1_HOST is the hostname for IDP1, eg. www.idp1.com.
c. IDP1_PORT is the port for IDP1, eg. 58080.
d. IDP1_DEPLOY_URI is the deploy URI for IDP1, eg. /federation.
e. SP1_SECURITY_KEY is the certificate alias for SP1.
f. IDP1_SECURITY_KEY is the certificate alias for IDP1.
Update above values in sp1Metadata.xml as per your deployment. SP1_SECURITY_KEY and IDP1_SECURITY_KEY are required only when you want to enable xml digital signature signing. If the keystore has not been configured yet, remove the iplanet-am-certificate-alias attribute value pair from the XML file.
2. Load sp1Metadata.xmlusing following command.
<begin_dir>/bin/amadmin -i <war_dir> -u amadmin -w <amadmin password> -t <sample_xml_dir>/sp1Metadata.xml
First step : no problem :)
Second step : I get this error :
Error 9: Operation failed: Can't find ressource for bundle java.util.PropertyResourceBundle, key invalidconfigfile
java.util.MissingResourceException: Can't find ressource for bundle java.util.PropertyResourceBundle, key invalidconfigfile
and I didn't find why this error is thrown :( I'm working on a Windows XP SP2 station with NetBeans 5.5 RC2 + Enterprise Pack 5.5 Beta.
Thanks for the help
Best regards !
@++

I am now working on deployment of sun one access manager. I have deployed as a single war in application server. But i am not able to see the access manager console as it shows file not found exception, Can anyone help me to resolve?
Log Entry Detail
DetailsTimestamp: Mar 22, 2007 19:20:51.435
Log Level: SEVERE
Logger: javax.enterprise.system.container.web
Name-Value Pairs: _ThreadID=12;
Record Number: 544
Message ID: WebModule[amserver]Exception starting filter amSetupFilter java.lang.ClassNotFoundException
Complete Message
com.sun.identity.setup.AMSetupFilter at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1447) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1228) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:215) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:312) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:83) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3881) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4531) at com.sun.enterprise.web.WebModule.start(WebModule.java:241) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:827) at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:125) at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:147) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:809) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1254) at com.sun.enterprise.web.HttpServiceWebContainer.loadWebModule(HttpServiceWebContainer.java:821) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:987) at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:160) at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:238) at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:918) at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:905) at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:427) at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139) at com.sun.enterprise.ee.admin.mbeans.ServerRuntimeMBean.forwardEvent(ServerRuntimeMBean.java:64) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:308) at com.sun.enterprise.admin.runtime.BaseRuntimeMBean.invoke(BaseRuntimeMBean.java:389) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1341) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:595)

Deploying JSC projects in Tomcat

If we deploy JSC projects in Tomcat we have to access the server.xml and tomcat-install-directory/shared/lib. Many web hosting providers do not allow access to these. This makes JSC project deployment in Tomcat very challenging.
Are there sny alternative ways to deploy JSC projects without accessing Tomcat locations (server.xml and shared/lib folder) except the webapps folder. For example, can I put the jstl.jar and standard.jar someware inside my JSC project? Can I do some changes in my web.xml instead of modifying server.xml?
Any advice is very much appreciated.
Thank you very much.

You can get around the server.xml changes. You will have to create a context.xml
look at
 
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html
http://tomcat.apache.org/tomcat-5.0-doc/deployer-howto.html#Context%20descriptors
 
for instance. I believe that context.xml has to go into <webapp>/META-INF directory. But I did not find a reference right now.
The only question I have, would be if Tomcat would share DataSources from different webapps when they are configured in the context.xml, instead of the global context.
I hope that helps a bit.
Thanks,
-- Marco

I cann't deploy SRDemoSampleADFBC sample on Tomcat

Similar Messages

Maybe you are looking for