Embedded weblogic configuration

I'm developing an app that pre-authenticates the user using an apache module and then apache proxies the request to weblogic. I'm using the mod_wl_22.so plugin.
After digging around in the weblogic documentation, I think I need to set the "enforce-valid-basic-auth-credentials" element to false in weblogic's config.xml file. I don't know where that is for the embedded server in JDev 11g.
Does anyone know where that configuration file is?

The location of the Integrated Weblogic server(aka embedded) configuration is in oracle_home\jdeveloper\system\system.11.1.1.0.xx.xx.xx\DefaultDomain. This is the location of the JDeveloper created domain. You can also access the Integrated Weblogic server configuration by launching the Weblogic server console @ http://localhost:7101/console once you've started the server from within Jdeveloper.

Similar Messages

Embedded weblogic admin console will not start

Hi Forum members,
I'm using JDeveloper Studio Edition Version 11.1.1.0.2 and trying to start the WebLogic admin console for
JDeveloper's embedded WebLogic Server.
The admin login screen appears, but after entering userid and password, the admin console crashes.
The log entries are below; thanks for your assistance.
<Nov 4, 2009 12:44:55 PM PST> <Error> <netuix> <BEA-423103> <[consolehelp] Deployment descriptor /WEB-INF/netuix-config.xml malformed.>
<Nov 4, 2009 12:44:55 PM PST> <Error> <netuix> <BEA-423443> <Exception while initializing SingleFileServlet: [javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument].
javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument
     at com.bea.netuix.util.ThrowServletException.throwServletException(ThrowServletException.java:28)
     at com.bea.netuix.servlets.manager.AppDescriptor.loadDescriptor(AppDescriptor.java:1053)
     at com.bea.netuix.servlets.manager.SingleFileServlet.reinitInternal(SingleFileServlet.java:124)
     at com.bea.netuix.servlets.manager.SingleFileServlet.initInternal(SingleFileServlet.java:84)
     at com.bea.netuix.servlets.manager.SingleFileServlet.access$100(SingleFileServlet.java:48)
     Truncated. see log file for complete stacktrace
java.lang.NoClassDefFoundError: Could not initialize class com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument
     at com.bea.netuix.servlets.manager.types.netuix_config.WeblogicPortalAppDocument$Factory.parse(WeblogicPortalAppDocument.java:533)
     at com.bea.netuix.servlets.manager.AppDescriptor.loadConfig(AppDescriptor.java:670)
     at com.bea.netuix.servlets.manager.AppDescriptor.loadDescriptor(AppDescriptor.java:1040)
     at com.bea.netuix.servlets.manager.SingleFileServlet.reinitInternal(SingleFileServlet.java:124)
     at com.bea.netuix.servlets.manager.SingleFileServlet.initInternal(SingleFileServlet.java:84)
     Truncated. see log file for complete stacktrace
>
<Nov 4, 2009 12:45:24 PM PST> <Error> <netuix> <BEA-423540> <No IPreferenceStore implementation has been registered in WEB-INF/netuix-config.xml. See the javadoc for com.bea.portlet.prefs.spi.IPreferenceStore for information on how to configure a preference store. Using a no-op store as a default.>
<Nov 4, 2009 12:45:57 PM PST> <Error> <netuix> <BEA-423203> <The included control tree for URI [PortalConfig/snmp/Snmp.book] is invalid.
com.bea.netuix.nf.UIControlException: Error creating tree from uri [PortalConfig/snmp/Snmp.book].
     at com.bea.netuix.servlets.controls.content.ValidatedContent.validateContent(ValidatedContent.java:91)
     at com.bea.netuix.servlets.manager.SingleFileProcessor.getMergedControlFromFile(SingleFileProcessor.java:358)
     at com.bea.netuix.servlets.manager.UIServletInternal.processStream(UIServletInternal.java:272)
     at com.bea.netuix.servlets.manager.UIServletInternal.getTree(UIServletInternal.java:230)
     at com.bea.netuix.servlets.manager.UIServletInternal.createUIContext(UIServletInternal.java:105)
     Truncated. see log file for complete stacktrace
com.bea.netuix.nf.UIControlException: One or more validation error(s) occurred during parsing [PortalConfig/snmp/Snmp.book]. The error(s) were: [Parser Error...
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'netuix:meta'. One of '{"http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0":toggleButton, "http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0":content}' is expected.
     at com.bea.netuix.servlets.controls.content.ValidatedContent.validateContent(ValidatedContent.java:80)
     at com.bea.netuix.servlets.manager.SingleFileProcessor.getMergedControlFromFile(SingleFileProcessor.java:358)
     at com.bea.netuix.servlets.manager.UIServletInternal.processStream(UIServletInternal.java:272)
     at com.bea.netuix.servlets.manager.UIServletInternal.getTree(UIServletInternal.java:230)
     at com.bea.netuix.servlets.manager.UIServletInternal.createUIContext(UIServletInternal.java:105)
     Truncated. see log file for complete stacktrace
>
<Nov 4, 2009 12:46:26 PM PST> <Warning> <netuix> <BEA-423319> <A default encoding was not found for webapp [console]. You can set a default encoding for portals in netuix-config.xml. Defaulting to [UTF-8].>
<Nov 4, 2009 12:46:27 PM PST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@3ee3a0 - appName: 'consoleapp', name: 'console', context-path: '/console', spec-version: '2.5', request: weblogic.servlet.internal.ServletRequestImpl@13442f1[
GET /console/console.portal HTTP/1.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.14) Gecko/2009082707 (CK-zz) Firefox/3.0.14
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://127.0.0.1:7101/console/login/LoginForm.jsp
Cookie: JSESSIONID=jWpJKxnS1N3pd3ryQRGShJF7qbkZt2KrP9DdTPCphJh9vwvyJndL!662735321; ADMINCONSOLESESSION=5012KxnLnRNpnk679vWrWSbX2SXrhv0nqN11JcwGzJvhbjNy7L4R!662735321
]] Root cause of ServletException.
java.lang.NoClassDefFoundError: Could not initialize class schemacom_bea_xml.system.sF6C6DB196AAE83D234595A687AE0370E.TypeSystemHolder
     at sun.misc.Unsafe.ensureClassInitialized(Native Method)
     at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
     at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
     at java.lang.reflect.Field.acquireFieldAccessor(Field.java:918)
     at java.lang.reflect.Field.getFieldAccessor(Field.java:899)
     Truncated. see log file for complete stacktrace

The Fusion Middleware is installed on my Windows XP laptop. To start my admin server, I use the Windows start button and navigate to "Oracle Fusion Middleware 11.1.1.0.2" -> "User Projects" -> "base-domain" -> "Start Admin Server for WebLogic Server Domain" menu item.
After the admin server is running, I use the Windows start button and navigate to "Oracle Fusion Middleware 11.1.1.0.2" -> "User Projects" -> "base-domain" -> "Admin Server Console" menu item.
A web browser pops up and after a few minutes, the login screen appears. After logging in, the admin console return a error screen. The log file contains the previous posted entries.

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

BPM Configuration Error on Weblogic Configuration

Hi,
I try to configure BPM Directory and always get error on wlst.sh command
weblogic.common.resourcepool.ResourceSystemException: Cannot load driver class: weblogic.jdbcx.oracle.OracleDataSource
My system spec:
- Solaris SPARC 64
- Weblogic 10.3.0.0 using JRockit 1.6.0_16
- BPM 10gR3
The configuration error in weblogic configuration.
Really need help here..
Thanks
Regards,
Eric Wijaya

Hi Eric,
Just checking: Are you using BPM 10.3.2?
Do you mean the BPM Directory Configuration?Yes, I'm talking about the directory configuration and the engine configuration too.
I've configure the BPM Directory to use BPM's Oracle Driver Version:10,11 which is selected by default by the BPM Configuration Wizard but still got the jdbc driver error. If you are using 10.3.2, you will see that there is another driver called: "Oracle Driver Version:10,11" (without BPM!!). You must use that driver. (if you install the latest 10.3.2 HF, that driver is the default one).
If you don't have that driver, then you are using an older version than 10.3.2. Please migrate to 10.3.2.
Hope this helps,
Ariel

Embedded LDAP configuration in Portal

Hi,
I am currently working on WL10.1MP1, and need to know the probable files involved in Embedded LDAP Configuration in the domain.
Can anyone let me know.
Regards
Lakshmi

Hi Lakshmi,
Default configurations are part of config.xml, security.xml and ldif files in security folder and files in data/LDAP folder in Admin Server.
Vishnu

How to backup weblogic configuration

I have experimentally determined that it is possible to lose the weblogic configuration, the stuff that defines WLS_FORMS
and WLS_REPORTS etc. Since it was not clear how this happened, I would like to know if I can back up that configuration
stuff and say put it back should this occur again? Where does that go?

Ok the final answer is at least in weblogic 10.3.4:
(and archive configuration files is not enabled by default. )
Archive configuration files
Each time you activate changes in the Administration Console using the Console's Change Center, WebLogic Server archives the previously-effective set of configuration files (including the central configuration file, config.xml).
To configure how many archive files are retained:
1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the left pane of the Console, under Domain Structure, select the domain name.
3. Select Configuration > General and click Advanced at the bottom of the page.
4. In the Archive Configuration Count field, enter the number of archive files to retain.
5. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).
Result
After you reach the maximum number of archive files, older archive files will be discarded. For more information, see Managing Configuration Changes.

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

Embedding WebLogic Application Server 10.3

Are there any whitepapers or information related to embedding WLS Server into an application? Our software is used by varying sized companies and it would be beneficial for us to embed the appserver and database server within our installation routine and not expose the management to the smaller end user shops. I guess I am just looking for some information to get me started so I understand complexities involved. Right now we are just reselling under the ASFU agreement and install and configure the appserver separately (though through silent installs, JMX, JSR-88). Embedding would save time for our implementation teams as well as minimize overhead and decision making on the part of the end user :)

I believe there is an entire team at Oracle dedicated to assisting ISV's with bundling WebLogic Server. I strongly recommend that you contact your local account team.
http://www.oracle.com/us/corporate/contact/index.htm
If you need assistance finding out who that is email me at my username @oracle.com and let me know where you are located and what type of application you have.

BPM for Weblogic configuration is failed

1, I install BPM for Weblogic.
2, I create a domain for weblogic using config tool and start it.
3, I create a new directory.
However, the configuration is failed.
The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
The log is as follows:
For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear, to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear, to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed. at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48) at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185) at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536) at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429) 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.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160) at org.python.core.PyMethod.__call__(PyMethod.java:96) at org.python.core.PyObject.__call__(PyObject.java:248) at org.python.core.PyObject.invoke(PyObject.java:2016) at org.python.pycode._pyx17.deploy$8(<iostream>:223) at org.python.pycode._pyx17.call_function(<iostream>) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:404) at org.python.core.PyFunction.__call__(PyFunction.java:184) at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:256) at org.python.core.PyFunction.__call__(PyFunction.java:169) at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyCode.call(PyCode.java:14) at org.python.core.Py.runCode(Py.java:1135) at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167) at weblogic.management.scripting.WLST.main(WLST.java:129) 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 weblogic.WLST.main(WLST.java:29)
Exiting WebLogic Scripting Tool.
<Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
Do you want to cancel this wizard?

Hi,
Thanks for your reply. I change the file and reconfigure the BPM for weblogic. However, it is still failed in 70-72%.
-------------------log message-------------------------------
TO_MSG PATH=/root/bea/wlserver_10.3/server/bin:/root/bea/modules/org.apache.ant_1.6.5/bin:/root/bea/jrockit_160_05/jre/bin:/root/bea/jrockit_160_05/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
TO_MSG
TO_MSG Your environment has been set.
TO_MSG
TO_MSG CLASSPATH=/root/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/jrockit_160_05/lib/tools.jar:/root/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/root/bea/wlserver_10.3/server/lib/weblogic.jar:/root/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/root/bea/wlserver_10.3/server/lib/webservices.jar:/root/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/root/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/root/OraBPMwlHome/lib/fuego.boot.jar:/root/OraBPMwlHome/bin/./:/root/OraBPMwlHome/bin/./lax.jar::/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbembedded57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbtools57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar
TO_MSG
TO_MSG Initializing WebLogic Scripting Tool (WLST) ...
TO_MSG
TO_MSG Welcome to WebLogic Server Administration Scripting Shell
TO_MSG
TO_MSG Type help() for help on available commands
TO_MSG
TO_MSG Starting server BPMServer
TO_MSG Please see the server log files for startup messages available at /root/weblogic3/bpm
TO_MSG Starting weblogic server ...
TO_MSG WLST-WLS-1249792014056: [WARN ] -XX:MaxPermSize=256m is not a valid VM option. Ignoring
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ26￥ﾈﾆ58￧ﾧﾒ CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00￧ﾧﾒ CST> <Info> <Management> <BEA-140013> </root/weblogic3/bpm/config/config.xml not found>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00￧ﾧﾒ CST> <Info> <Management> <BEA-141254> <Generating new domain directory in /root/weblogic3/bpm>
TO_MSG .....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ12￧ﾧﾒ CST> <Info> <Management> <BEA-141255> <Domain generation completed in 12,326 milliseconds.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ13￧ﾧﾒ CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15￧ﾧﾒ CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ16￧ﾧﾒ CST> <Notice> <Log Management> <BEA-170019> <The server log file /root/weblogic3/bpm/servers/BPMServer/logs/BPMServer.log is opened. All server side log events will be written to this file.>
TO_MSG ...WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ24￧ﾧﾒ CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
TO_MSG ....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34￧ﾧﾒ CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "BPMServer" for domain "bpm" running in Development Mode>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
TO_MSG Server started successfully.
TO_MSG Started Server. Trying to connect to the server ...
TO_MSG Connecting to t3://localhost.localdomain:7001 with userid weblogic ...
TO_MSG Successfully connected to Admin Server 'BPMServer' that belongs to domain 'bpm'.
TO_MSG
TO_MSG Warning: An insecure protocol was used to connect to the
TO_MSG server. To ensure on-the-wire security, the SSL port or
TO_MSG Admin port should be used instead.
TO_MSG
TO_MSG Location changed to edit tree. This is a writable tree with
TO_MSG DomainMBean as the root. To make changes you will need to start
TO_MSG an edit session via startEdit().
TO_MSG
TO_MSG For more help, use help(edit)
TO_MSG
TO_MSG Starting an edit session ...
TO_MSG Started edit session, please be sure to save and activate your
TO_MSG changes once you are done.
TO_MSG creating mbean of type JMSServer ...
TO_MSG creating mbean of type JMSSystemResource ...
TO_MSG creating mbean of type SubDeployment ...
TO_MSG creating mbean of type Queue ...
TO_MSG creating mbean of type Topic ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type Server ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Realm ...
TO_MSG creating mbean of type RoleMapper ...
TO_MSG creating mbean of type CredentialMapper ...
TO_MSG creating mbean of type CertPathProvider ...
TO_MSG creating mbean of type Authorizer ...
TO_MSG creating mbean of type Adjudicator ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG setting attributes for mbean type JMSServer
TO_MSG setting attributes for mbean type JMSSystemResource
TO_MSG setting attributes for mbean type SubDeployment
TO_MSG setting attributes for mbean type Queue
TO_MSG setting attributes for mbean type Topic
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type Server
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type DefaultIdentityAsserter
TO_MSG setting attributes for mbean type SecurityConfiguration
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type EmbeddedLDAP
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type Domain
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type JDBCXAParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG Saving all your changes ...
TO_MSG Saved all your changes successfully.
TO_MSG Your edit session is not stopped, you can continue your edits.
TO_MSG Activating all your changes, this may take a while ...
TO_MSG The edit lock associated with this edit session is released
TO_MSG once the activation is completed.
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute InternalAppsDeployOnDemandEnabled on weblogic.management.configuration.DomainMBeanImpl@fffe8220([bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@1759a12([bpm]/Log[bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute ListenAddress on weblogic.management.configuration.ServerMBeanImpl@2ddd7637([bpm]/Servers[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@2df105fa([bpm]/Servers[BPMServer]/Log[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.WebServerLogMBeanImpl@2df106e5([bpm]/Servers[BPMServer]/WebServer[BPMServer]/WebServerLog[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG
TO_MSG The following non-dynamic attribute(s) have been changed on MBeans
TO_MSG that require server re-start:
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Log,Server=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Server
TO_MSG Attributes changed : ListenAddress
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Log
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Domain
TO_MSG Attributes changed : InternalAppsDeployOnDemandEnabled, ProductionModeEnabled
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=WebServerLog,Server=BPMServer,WebServer=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG Activation completed
TO_MSG Creating a user ...
TO_MSG
TO_MSG Created user successfully
TO_MSG Deploying application from /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ01￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ08￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine [archive: /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear], to BPMServer .>
TO_MSG .................Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ29￥ﾈﾆ48￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 08-workspace-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ30￥ﾈﾆ45￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 09-feeds-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ00￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 06-workspaceadmin-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ31￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 07-papiws-wls103-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear], to BPMServer .>
TO_MSG ..WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48￧ﾧﾒ CST> <Error> <HTTP> <BEA-101220> <Error occurred while setting document root for "weblogic.servlet.internal.WebAppServletContext@30302d0 - appName: '07-papiws-wls103-XAFDIDS.ear', name: 'papiws', context-path: '/papiws', spec-version: '2.5'" to "/root/weblogic3/bpm/servers/BPMServer/tmp/_WL_user/07-papiws-wls103-XAFDIDS.ear/f0r1c0/papiws.war".>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48￧ﾧﾒ CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249792304208' for task '5'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'papiws''
TO_MSG WLST-WLS-1249792014056: weblogic.application.ModuleException: Failed to load webapp: 'papiws'
TO_MSG WLST-WLS-1249792014056:      at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
TO_MSG WLST-WLS-1249792014056:      Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: java.io.IOException: Error opening file
TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.open(Native Method)
TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.<init>(ZipFile.java:117)
TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.<init>(ZipFile.java:133)
TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.classloaders.ZipClassFinder.<init>(ZipClassFinder.java:23)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.io.ArchivedWar$WebInfClassesFinder.<init>(ArchivedWar.java:290)
TO_MSG WLST-WLS-1249792014056:      Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: >
TO_MSG WLST-WLS-1249792014056: java.io.FileNotFoundException: /root/weblogic3/bpm/config/config.xml (Too many open files)
TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.open(Native Method)
TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.FileUtils.writeToFile(FileUtils.java:115)
TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.Fil

Weblogic Configuration with Apache 2.2

Hi ,
I am getting the below error configured weblogic 10.3.5 with apache 2.2
<HTML>
<HEAD>
<TITLE>Weblogic Bridge Message
</TITLE>
</HEAD>
<BODY>
<H2>Failure of server APACHE bridge:</H2><P>
<hr>Your content length exceeded INT_MAX<hr> </BODY>
</HTML>
Thanks,

http://middlewaremagic.com/weblogic/?p=7795 (see the load balancing section)

InitialContext for iPlanet/WebLogic configuration

I am using iPlanet 4.1 as my webserver along with WebLogic 6.1. I was
under the impression that you can use the default contructor for
creating an InitialContext which is required to locate the EJB's if you
are an internal client, such as a servlet.
refer to: http://e-docs.bea.com/wls/docs61/ejb/EJB_design.html#1011066
However I get the following error when I create the InitialContext using
the default constructor:
javax.naming.NoInitialContextException: Need to specify class name in
environment or system property, or as an applet parameter, or in an
application resource file: java.naming.factory.initial
If I create the Initial context as follows, everything is fine:
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, "t3://localhost:7001");
InitialContext ic = new InitialContext(h);
Is iPlanet not considered a local client? If so, is there a way to to
configure it within the Web Container as a local client so the default
InitialContext constructor can be used?
Thanks in advance.
- Rich

More specifically which do I copy over?
mod_wl128_20.so
mod_wl128_22.so
mod_wl_20.so
mod_wl_22.so

EAS - Weblogic Configuration Problems

I have bothe Shared Services and Essbase installed under 64bit AIX. They are on separate lpars. I have started to have problems when working on the outline that require me to start and stop the application (right click on the application start - stop...) before I make even the smallest changes to the outline. The outline is an ASO cube. I have upped the cache memory to 100 Mb. Occasionally when I save the outline and during it's restructuring, the outline completely blanks out and I have to re-edit it again, losing all of my changes. The outline is about 65MB in size. There are very few MDX scripts and most of the calculations are not very complex. The problem is worse when I use the web based console versus the windows installed client console. Does someone have any experience tuning Weblogic and Essbase under AIX? I know that Weblogic can be a beast unto itself. Sometimes an error message is thrown, and sometimes no message is thrown. I don't have the error message, but it was related to a memory issue, hence my concern that Weblogic and shared services may need some tuning. Thanks for everyone's help.
Paul

hmm... it's very very difficult to answer your question.. ;-)
but probably you mean the configuration console???
http://yourhost:yourport/console (e.g. http://localhost:7001/console)
then enter username and password you choosed when installing weblogic.
cheers

Deleting WebLogic Configuration Template

Hi All
I want to delete a Configuration Template that I created on my Windows desktop. We have procedures to create templates and I could not find the same for deleting templates. Is there any specific way to delete a template? I guess deleting the Executable Jar under C:\Oracle\Middleware\user_templates is not the solution
Please let me know. Thanks in advance
chrs0302

Hi chrs0302,
I believe by deleting the jar file which had been created in should be the solution. However do let us know if you are facing any issues after doing that.
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…

Weblogic configuration doubts regarding multiple authenticators

We are trying to configure multiple authenticators in weblogic.
One default authenticator which holds weblogic's boot user id & password.
The authenticator configured to talk to active directory server.
I'm able to see Active Directory users in weblogic user list (i.e. examples --> security --> realms --> myrleam --> users)
The control flag on both authentication provides is set to OPTIONAL.
But when i try to use one of the user from active directory for authentication 'm getting invalid user id / password. (the sample program which i've written tries to create JNDI context using the user name & password)
I'm using weblogic 8.1
any help highly appreciated.
TIA
Girish

Set the JAAS Control Flag to SUFFICIENT for both authenticators. For more information
you can see information on JAAS (http://java.sun.com/products/jaas/overview.html)
or look at:
http://edocs.bea.com/wls/docs81/secmanage/providers.html#1187595
-Craig
Girish Pradhan <[email protected]> wrote:
We are trying to configure multiple authenticators in weblogic.
One default authenticator which holds weblogic's boot user id & password.
The authenticator configured to talk to active directory server.
I'm able to see Active Directory users in weblogic user list (i.e. examples
--> security --> realms --> myrleam --> users)
The control flag on both authentication provides is set to OPTIONAL.
But when i try to use one of the user from active directory for authentication
'm getting invalid user id / password. (the sample program which i've
written tries to create JNDI context using the user name & password)
I'm using weblogic 8.1
any help highly appreciated.
TIA
Girish

Weblogic configuration

Hi all,
I am trying to configure weblogic and am facing some problems, please help me.
so far i have achieved moderate success. I have been able to run the sample jsp's and servlets, but am not able to know where to put my servlets and JavaBeans, I mean which directory for my own servlets and beans. please tell me whatever changes
I need to make in weblogic.policy / weblogic.properties file.</p>
do i need to register each servlet that i write, ie, into the weblogic.properties file, and how can I do that, as this is what it seems from the online docs.
how should I shut down the server, till now I shut it using by pressing ctrl-c, tell me how to do it normally. i wasn't able to find any inf on it. what I got is that I need to write some custom shutdown file for this. how can I do that?
I had tried to take help from online docs at the ://www.weblogic.com/docs51/resources.html,
but even after trying very hard for abt 2-3 days I still am not able to know these things even got confused it's very vast over there.<br>
My o/s is win nt 4.0.
TIA
regards
Pradeep

Hi,
See I�ll tell you the way I placed my ejbs, servlets and supporting classes
I think the easiest way would be the following
1) Place all your servlets in myserver/servletclasses
2) Place your homeinterface,remoteinterace and Pk classes in myserver/ clientclasses
3) Place all your javascript file in myserver/ public_html
And yes ofcourse you have to register each of your serlvet in weblogic.properties file in the following way
Open your weblogic.properties file find the following text
# USER-WRITTEN AND DEMO SERVLET REGISTRATIONS
# Set ACLs for these as desired
register your servlet in this way
weblogic.httpd.register.�servletname with which you�ll be calling it�=com.myPackage.servlet.�servlet class file name�

Embedded weblogic configuration

Similar Messages

Maybe you are looking for