WebLogic Server vs Embedded Servlet Engine

We have licensing for WebLogic Server, and I was wondering if there were any benefits to using it over the embedded servlet engine for hosting Collaboration 4.5 or Publisher 6.4?

hi.
WebLogic Express supports the following:
Servlets, JSP, JDBC, JNDI, JTA, JAAS, JAXP, RMI, and clustering. You
can build a cluster of WLExpress instances.
Hope this helps,
Michael
Laurent PAILLARD wrote:
What are the differences between Server and Express. I've read that
Express does not implement EJB, JMS and two-phase commit protocol for
transaction. Nothing is said about clustering. As Servlet session can
be clustered, I wish to know if I can build a cluster with 2 Weblogic
Express instances.--
Michael Young
Developer Relations Engineer
BEA Support

Similar Messages

BPM engine deployment issue on Weblogic server

Hello,
I read all threads related to this issue, but I am getting mad.
Yesterday:
I have successfully deployed BPM 10.3.1 + certified WLS 10.3.0 on Linux Redhat + Oracle
I have successfully created a BPM configuration with the BPM Admin configuration wizard.
I could successfully access to BPM workspace admin and BPM workskape.
Today:
I have restarted weblogic server and BPM, the engine is not starting, with an error raised in another thread. Below is the most detailed message:
[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
ParseError at [row,col]:[5,148]
Message: Tried all: '1' addresses, but could not connect over HTTP to server: 'www.bea.com', port: '80'..
weblogic.application.ModuleException: Exception preparing module: EJBModule(engine-soapocengine.jar)
[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
ParseError at [row,col]:[5,148]
Message: Tried all: '1' addresses, but could not connect over HTTP to server: 'www.bea.com', port: '80'.
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
My server is not connected to the Internet, and will probably not. But it could not access the internet yesterday (before restart) neither...
a reply to another thread says that a patch coprrects this issue. which one is it? please note I cannot download it from the server... I have downloaded all public patches for WLS 10.3 for Linux (ZIP files), but the BSU tool refused to detect them... how should I proceed?
Thank you for your help
Hervé

Hi,
I have downloaded weblogic from oracle downloads 2 weeks back. i thought all the patches would be installed?? But am facing the same issue when deploying engine ear..
Do you think I need to install the above patch ???
A month back I downloaded ( might be by March) Weblogic. I was not facing any issue. But with the new download am facing the issue.
Kindly suggest.
Thanks,
Charan

Error in Calling Weblogic EJB's from JRun servlet engine

I am using servlets in Jrun engines to callEJB's running on a WebLogic Server. I have included "c:\weblogic\classes" in Jrun classpath. But i am getting the following error. Does any body have any idea what this may be??javax.servlet.ServletException: com/sun/java/util/collections/ArrayListjava.lang.NoClassDefFoundError: com/sun/java/util/collections/ArrayListat weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:193)at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:148)at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123)at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:668)at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)at javax.naming.InitialContext.init(InitialContext.java:222)at javax.naming.InitialContext.(InitialContext.java:198)

First off, wrong forum section.
Check if your JNDI name is correctly placed for the bean you're calling -- check j2ee-engine.xml for that. Check the EJB container if the ear file you deployed is there and updated.
Try placing "localejbs/JNDI name" on your lookup parameter.
Regards,
Jan

How to use java security in a servelt with weblogic as a servlet engine?

Hi,
i want to use standard java security with a user defined permission in
servlet with wls 5.1 (Win nt) as a servelt engine.
WL-Home: f:\weblogic
Server: f:\weblogic\elan
Servlet: f:\weblogic\elan\elan\ServletGropsTest.class
The Servlet is registered in weblogic.properties:
weblogic.httpd.register.elan.ServletGropsTest=elan.ServletGropsTest
i've added this to the weblogic.policy:
grant codebase "file:f:/weblogic/elan/elan/" {
permission java.security.AllPermission;
The servlet code is:
SecurityManager m = System.getSecurityManager();
if (m != null) m.checkPermission(new AndisPermission("x","y"));
WLS throws the permission-exception:
Do Jul 18 11:54:54 GMT+02:00 2002:<E> <ServletContext-General> Servlet
failed with Exception
java.security.AccessControlException: access denied
(elan.AndisPermission x y)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java,
Compiled Code)
at java.lang.Exception.<init>(Exception.java, Compiled Code)
at java.lang.RuntimeException.<init>(RuntimeException.java,
Compiled Cod
at elan.ServletGropsTest.doGet(ServletGropsTest.java, Compiled
Code)
can anyone help?
regards
Andy

ran_t wrote:
...I am using java 1.3.Why are you using an utterly obsolete version of Java?
My program using log4j jar.
When i put the log4j.jar in a path that include spaces like "c:\Program files\",Try it as c:\Program%20files\

Standalone servlet engine without HTTP server

Hello
Is it possible to somehow make a standalone program that can parse jsp pages and work with servlets.
What I'm imagining is something like this:
1. My application wants to open a jsp page.
2. My application sends the jsp to the servlet/jsp engine (Catalina?)
3. Catalina parses the jsp.
4. Catalina sends the jsp back to my application
5. My application displays the page in a briwser.
This way I could work without a HTTP server.
Maybe the engine is not called Cataline?
Thanks in advance

You mean you want to test and develop your servlets/jsps without >servlet container (HTTP/server)? No I do not wish to develop servlets/jsps without a servlet container, but I wish to develop it without an HTTP Server.
This way one application could parser/compile jsp/servlets and display them in an embedded browser.
This is meant to be used in a 1 tier application.
So the only tier existing needs to be both browser and application server.
I mean to make an application where it is very easy to change the GUI, that is how it is in JSP/servlets. But I don't want the 2/3 tier model, rather I want a standalone application, where the GUI is made in JSP/servlets.
Best regards
Klaus

Embedded WebLogic Server

Hi, everybody.
First of all, i apologize for my poor writing skills in English. My native language is Portuguese.
Is it possible to start an WebLogic Server 10.0+ inside a running JVM? Tricks like start weblogic.Server in a new JVM, using the appropriate -D switches (system properties and policy file), won't work for me.
I need to start WL in the same JVM (an Embedded WebLogic Server instance) like Tomcat (http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/catalina/startup/Embedded.html) or Jetty (http://docs.codehaus.org/display/JETTY/Embedding+Jetty).
I've already tried to set System.setProperty() properly and run weblogic.Server.main(new String[0]), but WebLogic fails silently. It's impossible to debug it because the source code is closed.
Is there any suggestion or workaround to do it?
Some context: I'm working with an open source general API to start Embeddable Web Containers/Application Servers and i'm trying to develop/use WL's implementation. The host contains a regular WebLogic installation and i'm able to start WebLogic invoking "java -cp appropriate_class_path weblogic.Server" from any directory: WebLogic just asks about context.xml and do its magic.
Thanks in advance.
Best regards,
Daniel.

Another difference I noticed between these 2 approaches (java -cp weblogic.jar vs. new URLClassLoader()): When weblogic.jar is specified using -cp, the system property java.class.path is changed to include a lot of WebLogic jars.
Is there any bootstrap log that i can enable to understand what is happening?
Thanks.
== java -cp . RunWL2 ==
java.class.path = C:\tmp\test_wl
== java -cp .;weblogic.jar RunWL2 ==
java.class.path = C:\tmp\test_wl;C:\bea2\modules\com.bea.core.weblogic.workmanager_1.4.0.0.jar;C:\bea2\modules\com.bea.core.utils_1.4.0.0.jar;C:\bea2\modules\com.bea.core.utils.full_1.4.0.0.jar;C:\bea2\modules\features\weblogic.server.modules.L10N_10.3.0.0.jar;C:\bea2\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\bea2\modules\com.bea.core.descriptor.j2ee_1.1.0.0.jar;C:\bea2\modules\com.bea.core.descriptor.j2ee.binding_1.1.0.0.jar;C:\bea2\modules\com.bea.core.descriptor.wl_1.1.0.0.jar;C:\bea2\modules\com.bea.core.descriptor.wl.binding_1.1.0.0.jar;C:\bea2\modules\com.bea.core.datasource6_1.4.0.0.jar;C:\bea2\modules\com.bea.core.datasource6.binding_1.4.0.0.jar;C:\bea2\modules\com.bea.core.beangen_1.4.0.0.jar;C:\bea2\modules\com.bea.core.descriptor.settable.binding_1.4.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.accessor_1.1.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.accessor.binding_1.1.0.0.jar;C:\bea2\modules\com.bea.core.management.core_2.3.0.0.jar;C:\bea2\modules\com.bea.core.management.core.binding_2.3.0.0.jar;C:\bea2\modules\com.bea.core.ejbgen_1.0.0.0.jar;C:\bea2\modules\org.apache.ant.patch_1.1.0.0_1-6-5.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-xslp.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-xalan1.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-weblogic.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-vaj.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-trax.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-swing.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-stylebook.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-starteam.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-nodeps.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-netrexx.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-launcher.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-junit.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-jsch.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-jmf.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-jdepend.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-javamail.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-jai.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-icontract.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-commons-net.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-commons-logging.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-resolver.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-regexp.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-oro.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-log4j.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-bsf.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-bcel.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-antlr.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-all.jar;C:\bea2\modules\com.bea.core.repackaged.apache.bcel_5.2.1.0.jar;C:\bea2\modules\com.bea.core.repackaged.jdt_3.2.2.0.jar;C:\bea2\modules\com.bea.core.apache.commons.collections_3.2.0.jar;C:\bea2\modules\com.bea.core.apache.commons.lang_2.1.0.jar;C:\bea2\modules\com.bea.core.apache.commons.pool_1.3.0.jar;C:\bea2\modules\com.bea.core.apache.dom_1.0.0.0.jar;C:\bea2\modules\com.bea.core.apache.logging_1.0.0.0.jar;C:\bea2\modules\org.apache.openjpa_2.2.0.0_1-1-0.jar;C:\bea2\modules\com.bea.core.xml.xmlbeans_1.0.0.0_2-4-0.jar;C:\bea2\modules\com.bea.core.logging_1.4.0.0.jar;C:\bea2\modules\com.bea.core.bea.opensaml_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.bea.opensaml2_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.monitoring.harvester.api_2.1.0.0.jar;C:\bea2\modules\com.bea.core.monitoring.harvester.jmx_2.1.0.0.jar;C:\bea2\modules\com.bea.adaptive.harvester.utils_1.2.0.0.jar;C:\bea2\modules\com.bea.mbean.typing.util_1.2.0.0.jar;C:\bea2\modules\javolution_3.7.19.0.jar;C:\bea2\modules\joda.time_1.2.1.0.jar;C:\bea2\modules\com.bea.core.xml.staxb.buildtime_1.3.0.0.jar;C:\bea2\modules\com.bea.core.xml.staxb.runtime_1.3.0.0.jar;C:\bea2\modules\com.bea.core.annogen_1.2.0.0.jar;C:\bea2\modules\com.bea.core.kodo_1.0.0.0_4-2-0.jar;C:\bea2\modules\com.bea.core.kodo.integration_1.3.0.0.jar;C:\bea2\modules\com.bea.core.kodo.integration.binding_1.3.0.0.jar;C:\bea2\modules\com.bea.core.kodo.integration.tools_1.2.0.0.jar;C:\bea2\modules\com.bea.core.process_5.4.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.stax_1.4.0.0.jar;C:\bea2\modules\com.bea.core.xml.beaxmlbeans_1.0.0.0_2-4-0.jar;C:\bea2\modules\com.bea.core.repackaged.aspectj.aspectjweaver_5.1.0.jar;C:\bea2\modules\com.bea.core.repackaged.apache.commons.logging_1.2.0.jar;C:\bea2\modules\com.bea.core.repackaged.springframework.spring_2.0.3.jar;C:\bea2\modules\com.bea.core.repackaged.springframework.pitchfork_1.1.0.0_1-0.jar;C:\bea2\modules\com.bea.core.common.security.i18n_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.xacml_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.saml2.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.engine.impl_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.engine.api_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.api_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.impl_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.jdkutils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.saml2_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.saml2.manage_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.providers.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.saml.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.xacmlproviders.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.providers.env_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.certj_1.0.0.0.jar;C:\bea2\modules\com.bea.core.ldapjdk_1.0.0.0.jar;C:\bea2\modules\com.bea.core.apache.commons.net_1.0.0.0_1-4-1.jar;C:\bea2\modules\com.bea.core.weblogic.saaj_1.3.0.0.jar;C:\bea2\modules\glassfish.el_2.1.0.jar;C:\bea2\modules\glassfish.jaxb_2.1.6.jar;C:\bea2\modules\glassfish.jaxb.xjc_2.1.6.jar;C:\bea2\modules\glassfish.jaxws.resolver_2.1.3.jar;C:\bea2\modules\glassfish.jaxws.fastinfoset_2.1.3.jar;C:\bea2\modules\glassfish.jaxws.rt_2.1.3.jar;C:\bea2\modules\glassfish.jaxws.mimepull_1.0.144.jar;C:\bea2\modules\com.bea.core.woodstox_1.0.0.0_3-2-4.jar;C:\bea2\modules\glassfish.jaxws.tools_1.0.0.0_2-1-3.jar;C:\bea2\modules\glassfish.stax.ex_1.0.0.0_1-2.jar;C:\bea2\modules\glassfish.xmlstreambuffer_0.5.221.jar;C:\bea2\modules\com.bea.core.apache.oro_1.0.0.0_2-0-8.jar;C:\bea2\modules\javax.activation_1.1.0.0_1-1.jar;C:\bea2\modules\javax.annotation_1.1.jar;C:\bea2\modules\javax.interceptor_1.0.jar;C:\bea2\modules\javax.ejb_3.0.1.jar;C:\bea2\modules\javax.jdo_2.0.1.jar;C:\bea2\modules\javax.enterprise.deploy_1.2.jar;C:\bea2\modules\javax.jms_1.1.1.jar;C:\bea2\modules\javax.jsp_1.1.0.0_2-1.jar;C:\bea2\modules\javax.jws_2.0.jar;C:\bea2\modules\javax.mail_1.1.0.0_1-1.jar;C:\bea2\modules\javax.management.j2ee_1.0.jar;C:\bea2\modules\javax.persistence_1.0.0.0_1-0.jar;C:\bea2\modules\javax.resource_1.5.1.jar;C:\bea2\modules\javax.security.jacc_1.0.0.0_1-1.jar;C:\bea2\modules\javax.servlet_1.0.0.0_2-5.jar;C:\bea2\modules\javax.transaction_1.0.0.0_1-1.jar;C:\bea2\modules\javax.xml.bind_2.1.1.jar;C:\bea2\modules\javax.xml.registry_1.0.0.0_1-0.jar;C:\bea2\modules\javax.xml.soap_1.3.1.0.jar;C:\bea2\modules\javax.xml.stream_1.1.1.0.jar;C:\bea2\modules\javax.xml.ws_2.1.1.jar;C:\bea2\modules\javax.xml.rpc_1.2.1.jar;C:\bea2\modules\monfox.dsnmp.agent_1.0.0.0_4-6-5.jar;C:\bea2\modules\com.bea.core.jsafe_3.5.0.jar;C:\bea2\modules\com.bea.core.serp_1.14.2.0.jar;C:\bea2\modules\com.bea.core.apache_1.2.0.0.jar;C:\bea2\modules\com.bea.core.beaninfo_1.4.0.0.jar;C:\bea2\modules\com.bea.core.descriptor_1.4.0.0.jar;C:\bea2\modules\com.bea.core.repackaged.asm_3.0.jar;C:\bea2\modules\com.bea.core.repackaged.asm.commons_3.0.jar;C:\bea2\modules\com.bea.core.repackaged.asm.tree_3.0.jar;C:\bea2\modules\com.bea.core.repackaged.asm.util_3.0.jar;C:\bea2\modules\com.bea.core.diagnostics.core_2.1.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.logging_1.1.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.query_1.0.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.instrumentor_1.3.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.notifications_1.1.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.snmp_1.1.0.0.jar;C:\bea2\modules\com.bea.core.i18n_1.4.0.0.jar;C:\bea2\modules\com.bea.core.i18n.generator_1.3.0.0.jar;C:\bea2\modules\com.bea.core.i18n.tools_1.1.0.0.jar;C:\bea2\modules\com.bea.core.management.jmx_1.1.0.0.jar;C:\bea2\modules\com.bea.core.mbean.maker_1.3.0.0.jar;C:\bea2\modules\com.bea.core.mbean.support_1.3.0.0.jar;C:\bea2\modules\com.bea.core.messaging.kernel_1.4.0.0.jar;C:\bea2\modules\com.bea.core.resourcepool_1.4.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.socket.api_1.0.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.rmi.client_1.4.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.security.wls_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.weblogic.lifecycle_1.1.0.0.jar;C:\bea2\modules\com.bea.core.store_1.4.0.0.jar;C:\bea2\modules\com.bea.core.store.gxa_1.4.0.0.jar;C:\bea2\modules\com.bea.core.store.admintool_1.1.0.0.jar;C:\bea2\modules\com.bea.core.store.jdbc_1.1.0.0.jar;C:\bea2\modules\com.bea.core.transaction_2.5.0.0.jar;C:\bea2\modules\com.bea.core.utils.agent_1.0.0.0.jar;C:\bea2\modules\com.bea.core.utils.classloaders_1.4.0.0.jar;C:\bea2\modules\com.bea.core.utils.compiler_1.0.0.0.jar;C:\bea2\modules\com.bea.core.utils.expressions_1.3.0.0.jar;C:\bea2\modules\com.bea.core.utils.wrapper_1.3.0.0.jar;C:\bea2\modules\com.bea.core.timers_1.4.0.0.jar;C:\bea2\modules\com.bea.core.workarea_1.4.0.0.jar;C:\bea2\modules\com.bea.core.xml.weblogic.xpath_1.1.0.0.jar;C:\bea2\modules\com.bea.core.jatmi_1.2.0.3.jar;C:\bea2\modules\com.bea.core.weblogic.security_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.weblogic.security.auth_1.0.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.security.digest_1.0.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.security.identity_1.1.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.security.logger_1.1.0.0.jar;C:\bea2\modules\com.bea.core.nodemanager.plugin_1.2.0.0.jar;C:\bea2\modules\com.bea.core.jmspool_1.4.0.0.jar;C:\bea2\modules\com.bea.core.compat.wl.90_1.1.0.0.jar;C:\bea2\modules\com.bea.core.http.pubsub.mbean_1.2.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.web.api_1.2.0.0.jar;C:\bea2\modules\com.bea.core.redef_1.1.0.0.jar;C:\bea2\modules\com.bea.core.redefagent_1.1.0.0.jar;C:\bea2\modules\com.bea.core.redef.binding_1.1.0.0.jar;C:\bea2\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\bea2\wlserver_10.3\server\lib\schema\weblogic-domain-binding.jar;C:\bea2\wlserver_10.3\server\lib\schema\diagnostics-binding.jar;C:\bea2\wlserver_10.3\server\lib\schema\diagnostics-image-binding.jar;C:\bea2\wlserver_10.3\server\lib\wlcipher.jar;C:\bea2\wlserver_10.3\server\lib\webservices.jar;C:\bea2\wlserver_10.3\server\lib\xmlx.jar;C:\bea2\wlserver_10.3\server\lib\ojdbc6.jar;C:\bea2\wlserver_10.3\server\lib\jconn2.jar;C:\bea2\wlserver_10.3\server\lib\jconn3.jar;C:\bea2\wlserver_10.3\server\lib\jConnect.jar;C:\bea2\wlserver_10.3\server\lib\EccpressoAsn1.jar;C:\bea2\wlserver_10.3\server\lib\EccpressoCore.jar;C:\bea2\wlserver_10.3\server\lib\EccpressoJcae.jar;C:\bea2\wlserver_10.3\server\lib\mysql-connector-java-commercial-5.0.3-bin.jar;C:\bea2\wlserver_10.3\server\lib\wlbase.jar;C:\bea2\wlserver_10.3\server\lib\wlutil.jar;C:\bea2\wlserver_10.3\server\lib\wlsqlserver.jar;C:\bea2\wlserver_10.3\server\lib\wldb2.jar;C:\bea2\wlserver_10.3\server\lib\wlsybase.jar;C:\bea2\wlserver_10.3\server\lib\wloracle.jar;C:\bea2\wlserver_10.3\server\lib\wlinformix.jar;C:\bea2\wlserver_10.3\server\lib\wlw-langx.jar;C:\bea2\wlserver_10.3\common\lib;C:\bea2\modules\com.bea.cie.plugin-wizard_2.1.2.0.jar;C:\bea2\modules\com.bea.cie.plugin_2.1.0.0.jar;C:\bea2\modules\com.bea.cie.comdev_5.9.0.0.jar;C:\bea2\modules\com.bea.cie.xmldh_2.2.0.0.jar;C:\bea2\modules\com.bea.cie.gpr_2.8.0.0.jar;C:\bea2\modules\com.bea.cie.gpr-impl_2.8.0.0.jar;C:\bea2\modules\com.bea.cie.wizard_5.6.0.0.jar;C:\bea2\wlserver_10.3\common\lib\oxy-cci.jar;C:\bea2\modules\com.bea.cie.config_5.2.0.0.jar;C:\bea2\modules\com.bea.cie.wlw-plaf_5.2.0.0.jar;C:\bea2\modules\com.bea.cie.common-plugin_2.2.0.0.jar;C:\bea2\wlserver_10.3\common\lib\pdev.jar;C:\bea2\wlserver_10.3\server\lib\wlw-system.jar;C:\bea2\wlserver_10.3\server\lib\jcom.jar;C:\bea2\wlserver_10.3\server\lib\weblogic.jar

How to terminate the "process" running in weblogic server by servlet

hi all !!
i have executed a external command from servlet but i am not getting the output untill i logoff the weblogic server.
now i want to kill the process running in my server by servlet code.how could i do this? here is my code ,it is executing the command but not giving output untill i logoff the server.
                 Runtime rt = Runtime.getRuntime();
                 Process proc = rt.exec("var.bat");
                 proc.wait(60);
                 proc.destroy();Thanks and Regards
Allwyn

hey !
anybody is here?????

WebLogic Server 9.2 Windows - javax.servlet.ServletException: [HTTP:101250]

Hi,
I am using BEA WebLogic Server 9.2
When I deployed my [ear] apllication (Struts 1, Java 1.4, EJB2) I get this error:
Message icon - Error javax.servlet.ServletException: [HTTP:101250][weblogic.servlet.internal.WebAppServletContext@11c2137 -
appName: 'test-ear', name: 'TEST', context-path: '/TEST']: Servlet class de.general.TestActionServlet for servlet action could not be loaded because a class on which
it depends was not found in the classpath . java.lang.NoClassDefFoundError:
org/apache/struts/action/ActionServlet.
Please help me in this ClassLoader problem,
Regards

Hi
you can set the classpath struts.jar in setDomainEnv.cmd
you can get this file in your root domain under the bin directory.
set classpath=%classpath%;/struts.jar;

Weblogic.server.ServiceFailureException:com- embedded LDAP error

Hi
While starting teh weblogic server, I am getting error as
weblogic.server.ServiceFailureException: Error initialisng embedded LDAP server - with nested exception
java.lang.ClassCastException:com.octetstring.vde.backend.BackendRoot
the server is not started (I have installed it as a window service in Win2k)
Any help on this ?

there are few different ways to fix this. I do this frequently
--Delete the data folder and boot the server it will fix the issue. You will lose all the users information (except admin user) need to recrate any ohter users you created.make sure backup data folder
-- Second get the data folder from domain_bak folder
Hope this will fix your problem
Thanks
ksr
Edited by: ksr11 on Nov 24, 2010 10:33 AM

How to run Servlet in weblogic server ?

Hi ,
I am new to J2ee Tech.
how to run a simple servlet program in weblogic server?
mainly i want know how to give the address in ID.
Now i am using htt:\\localhost :7001\Sample\HelloServlet
but it is not working
Please give me the steps
Thanks
Merlin Rosina

Hi ,
I am new to J2ee Tech.
how to run a simple servlet program in weblogic server?
mainly i want know how to give the address in ID.
Now i am using htt:
localhost :7001\Sample\HelloServlet
but it is not working
Please give me the steps

Load servlet on startup in a cluster WebLogic Server 6.1

I try to load my servlet on startup of Bea WebLogic Server 6.1 (SP 3) cluster.
          This load failed.
          Can you help me?
          Tank's!


HOw did you specified the load-on-startup? and what error you get
          upon startup/deployment time?
          Kumar
          Giulia Esposito wrote:
          > I try to load my servlet on startup of Bea WebLogic Server 6.1 (SP 3) cluster.
          > This load failed.
          >
          > Can you help me?
          >
          > Tank's!
          >

Upgrade EclipseLink in Embedded WebLogic Server (JDeveloper 11.1.1.2.0)

Currently I am using JDeveloper 11.1.1.2.0 for my project, which comes with EclipseLink v1.2 pre-installed. However, my project requires to use latest EclipseLink version 2.0. I added EclipseLink 2.0 into Libraries and Classpath setting in project property. However, when I ran my app by using embedded WebLogic Server, my app is still using the old EclipseLink v1.2. I already tried to copy EclipseLink 2.0 jar file into DefaultDomain/lib directory and ear library directory. But embedded weblogic server still using old version from modules directory. Could anyone tell me how I could solve this issue. Thanks!

WebLogic comes pre-configured with TopLink's provided EclipseLink Library as a system module. You cannot upgrade this to 2.0 in a support fashion. The next release of WebLogic will include EclipseLink 2.0(.x).
If you want to test your application's use of EclipseLink 2.0 using JPA 1.0 application managed EntityManagers you can package the 2.0 library in your EAR and use the filtered classloader config setup in the weblogic-application.xml to ensure the packaged library is used instead of the system module.
Doug

Weblogic 8.1 & Embedded LDAP server

Hi,
Is it possible to store user attributes alongwith username & password in the Weblogic 8.1 Embedded LDAP Server?.
We have about 6 user profile attributes along with the username & password. Does weblogic's embedded LDAP Server
support this feature.
Any help will be appreciated.
thanx,
Vishwa

Hi Vishwap,
Did you ever found out how to manipulate additional information in the embedded LDAP server?
I am in critical need to do the same.
Thanks in advance for your comments.
Zi

How to add SIP servlets pluggins to OEPE for Oracle weblogic server 10.3.4

Please procide the solution to :
Is it possible to add SIP servlets pluggins to OEPE for Oracle weblogic server 10.3.4.0 or OCCAS(Oracle communication Converged Application Server)??
As Its not their by default.
Please do the needfull...

This forum is for Oracle WebLogic Communication Services. Please direct your question to one of the WebLogic Server forums or to OCCAS forum/support.
- Dev

Servlet in WebLogic Server 6.0

          I am trying to run a servlet from WebLogic Server 6.0
          Copied servlet class file into the following directory:
          config/mydomain/applications/
          DefaultWebApp_myserver/
          WEB-INF/classes
          Modified the web.xml file located in the config/mydomain/applications/
          DefaultWebApp_myserver/
          WEB-INF/ directory
          <web-app>
          <servlet>
          <servlet-name>
          CustLogin
          </servlet-name>
          <servlet-class>
          lawson.servlet.CustLogin
          </servlet-class>
          <init-param>
          <param-name>url</param-name>
          <param-value> http:/localhost:7001/CustLogin/custaddr.html</param-value>
          </init-param>
          </servlet>
          <servlet-mapping>
          <servlet-name>
          CustLogin
          </servlet-name>
          <url-pattern>
          /CustLogin/*
          </url-pattern>
          </servlet-mapping>
          </web-app>
          Run servlet from a Web browser with URL:
          http://localhost:7001/CustLogin
          Servlet Exception
          <<Error> <HTTP> <saluki2> <myserver> <ExecuteThread-11> <> <> <101018>
          <[WebAppServletContext(944251,DefaultWebApp_myserver)] Servlet
          failed with ServletException>
          javax.servlet.ServletException: Servlet class: 'lawson.servlet.CustLogin'
          could not be resolved - a class upon which this class depends wasn't
          found


Deepak,
          Are all the classes used by CustLogin in System Classpath or under
          web-inf\classes directory?
          Kumar.
          Deepak wrote:
          > I am trying to run a servlet from WebLogic Server 6.0
          >
          > Copied servlet class file into the following directory:
          > config/mydomain/applications/
          > DefaultWebApp_myserver/
          > WEB-INF/classes
          >
          > Modified the web.xml file located in the config/mydomain/applications/
          >
          > DefaultWebApp_myserver/
          > WEB-INF/ directory
          >
          > <web-app>
          >
          > <servlet>
          > <servlet-name>
          > CustLogin
          > </servlet-name>
          > <servlet-class>
          > lawson.servlet.CustLogin
          > </servlet-class>
          > <init-param>
          > <param-name>url</param-name>
          > <param-value> http:/localhost:7001/CustLogin/custaddr.html</param-value>
          >
          > </init-param>
          > </servlet>
          >
          > <servlet-mapping>
          > <servlet-name>
          > CustLogin
          > </servlet-name>
          > <url-pattern>
          > /CustLogin/*
          > </url-pattern>
          > </servlet-mapping>
          > </web-app>
          >
          > Run servlet from a Web browser with URL:
          > http://localhost:7001/CustLogin
          >
          > Servlet Exception
          >
          > <<Error> <HTTP> <saluki2> <myserver> <ExecuteThread-11> <> <> <101018>
          > <[WebAppServletContext(944251,DefaultWebApp_myserver)] Servlet
          > failed with ServletException>
          > javax.servlet.ServletException: Servlet class: 'lawson.servlet.CustLogin'
          > could not be resolved - a class upon which this class depends wasn't
          > found
          >

WebLogic Server vs Embedded Servlet Engine

Similar Messages

Maybe you are looking for