Embedded LDAP Server Replication

Hi,
I am new to weblogic, and trying to figure out how the master LDAP server, maintained in the domain’s Administration Server, is replicated to Managed Server in the domain.
I recently installed weblogic and during testing found that, user login to deployed application is denied, if Administrator Server is down.
According to this document: http://docs.oracle.com/cd/E12840_01/wls/docs103/secmanage/ldap.html
I understand that each Managed Server maintains a copy of LDAP server and user authentication can be taken care by this in the absence of Administrator server.
However it's not happening.
Do I have to make any configuration changes? Any pointers on this will be appriciated.
Error Message:
An invalid User Name or Password was entered
Thank You,
Deepak

Ensure that the managed server is running with "Managed Server Independence Enabled" flag checked.
It can be checked on console via Environment --> Servers --> <ServerName> --> Configuration --> Tuning
For more information, please check
http://docs.oracle.com/cd/E14571_01/web.1111/e13708/failures.htm#START169
The above flag is required for the managed server to use the local LDAP repository.
Arun

Similar Messages

Petstore - unable to connect to embedded LDAP Server

I have installed the Petstore 1.3.1 02 demo on a Weblogic 8.1 server on Windows XP. After running the Configuration wizard, when trying to start the PetStore Administration Sever using the startPetStoreWebLogic.cmd file, I receive the following error message:
The WebLogic Server did not start up properly.
weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement Engine unable to connect to the embedded LDAP server
netscape.ldap.LDAPException: error result (50)
An LDAPException with error result 50, according to the API Specification, means insufficient access rights, but as I am doing everything according to the readme, I don't know what the problem is.
Has anybody had the same problem or knows what to do to solve this?
Thanks very much!

Hi,
By removing the encrypted 'Credential' for the
EmbeddedLDAP entry in config.xml workaround it,
it went on but the real problem is with the
deployment of the 4 ears inside applications dir.
Would appreciate of anyone could enlighten.
jchintk
####<Jan 28, 2005 2:59:31 PM SGT> <Debug> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
     Module: customer-ejb.jar     Error: [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:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:31 PM SGT> <Error> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application appsdirpetstore_ear.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
     Module: customer-ejb.jar     Error: [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:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
     Module: customer-ejb.jar     Error: [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:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Application Poller> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149400> <Activating application: appsdirsupplier_ear>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Deployer> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149038> <A deployment task with ID 1 for application appsdirsupplier_ear is being initiated.>
####<Jan 28, 2005 2:59:34 PM SGT> <Warning> <DRS> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-002506> <The current version 0 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 1 for a one-phase update.>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <preparing application appsdirsupplier_ear on myserver>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <failed application appsdirsupplier_ear on myserver>
####<Jan 28, 2005 2:59:34 PM SGT> <Warning> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application appsdirsupplier_ear.>
####<Jan 28, 2005 2:59:34 PM SGT> <Debug> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 1
     Module: supplierpo-ejb.jar     Error: [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:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:34 PM SGT> <Error> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application appsdirsupplier_ear.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 1
     Module: supplierpo-ejb.jar     Error: [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:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 1
     Module: supplierpo-ejb.jar     Error: [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:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:38 PM SGT> <Info> <Application Poller> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149400> <Activating application: appsdirpetstoreadmin_ear>
####<Jan 28, 2005 2:59:38 PM SGT> <Info> <Deployer> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149038> <A deployment task with ID 2 for application appsdirpetstoreadmin_ear is being initiated.>
####<Jan 28, 2005 2:59:38 PM SGT> <Warning> <DRS> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-002506> <The current version 0 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 2 for a one-phase update.>
####<Jan 28, 2005 2:59:55 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <preparing application appsdirpetstoreadmin_ear on myserver>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module admin of application appsdirpetstoreadmin_ear is transitioning from unprepared to prepared on server myserver.>
####<Jan 28, 2005 2:59:56 PM SGT> <Warning> <HTTP> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-101304> <Webapp: ServletContext(id=12397950,name=admin,context-path=/admin), the role: administrator defined in web.xml has not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149060> <Module admin of application appsdirpetstoreadmin_ear successfully transitioned from unprepared to prepared on server myserver.>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module asyncsender-ejb.jar of application appsdirpetstoreadmin_ear is transitioning from unprepared to prepared on server myserver.>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <EJB> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-010008> <EJB Deploying file: asyncsender-ejb.jar>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <EJB> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-010087> <The EJB deployment named: asyncsender-ejb.jar is being recompiled within the WebLogic Server. Please consult the server logs if there are any errors. It is also possible to run weblogic.ejbc as a stand-alone tool to generate the required classes. The generated source files will be placed in C:\bea\user_projects\domains\petstore\.\myserver\.wlnotdelete\EJBCompilerCache\283hhgsoep72.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149061> <Module asyncsender-ejb.jar of application appsdirpetstoreadmin_ear failed to transition from unprepared to prepared on server myserver.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module admin of application appsdirpetstoreadmin_ear is transitioning from prepared to unprepared on server myserver.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149060> <Module admin of application appsdirpetstoreadmin_ear successfully transitioned from prepared to unprepared on server myserver.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <failed application appsdirpetstoreadmin_ear on myserver>
####<Jan 28, 2005 3:00:02 PM SGT> <Info> <Application Poller> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149400> <Activating application: appsdiropc_ear>
####<Jan 28, 2005 3:00:02 PM SGT> <Info> <Deployer> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149038> <A deployment task with ID 3 for application appsdiropc_ear is being initiated.>
####<Jan 28, 2005 3:00:00 PM SGT> <Warning> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application appsdirpetstoreadmin_ear.>
####<Jan 28, 2005 3:00:06 PM SGT> <Debug> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for asyncsender-ejb.jar
     Module: asyncsender-ejb.jar     Error: Exception preparing module: EJBModule(asyncsender-ejb.jar,status=NEW)
Unable to deploy EJB: AsyncSenderEJB from asyncsender-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'jms/QueueConnectionFactory' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
     at weblogic.ejb20.deployer.EnvironmentBuilder.addJMSConnectionFactoryRef(Lweblogic.management.descriptors.ejb11.ResourceRefMBean;Ljava.util.Map;)V(EnvironmentBuilder.java:439)
     at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(Ljava.util.Collection;Ljava.util.Map;)V(EnvironmentBuilder.java:226)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(Ljavax.naming.Context;Lweblogic.ejb20.interfaces.BeanInfo;Ljava.lang.String;Ljava.lang.String;)Ljavax.naming.Context;(EJBDeployer.java:379)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(Lweblogic.ejb20.interfaces.BeanInfo;Lweblogic.ejb20.interfaces.DeploymentInfo;Lweblogic.management.configuration.EJBComponentMBean;Ljavax.naming.Context;)Ljavax.naming.Context;(EJBDeployer.java:1172)
     at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;)V(EJBDeployer.java:943)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1345)
     at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3142)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1583)
     at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1227)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1070)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2513)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2463)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 3:00:06 PM SGT> <Error> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 2 for the application appsdirpetstoreadmin_ear.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for asyncsender-ejb.jar
     Module: asyncsender-ejb.jar     Error: Exception preparing module: EJBModule(asyncsender-ejb.jar,status=NEW)
Unable to deploy EJB: AsyncSenderEJB from asyncsender-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'jms/QueueConnectionFactory' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
     at weblogic.ejb20.deployer.EnvironmentBuilder.addJMSConnectionFactoryRef(Lweblogic.management.descriptors.ejb11.ResourceRefMBean;Ljava.util.Map;)V(EnvironmentBuilder.java:439)
     at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(Ljava.util.Collection;Ljava.util.Map;)V(EnvironmentBuilder.java:226)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(Ljavax.naming.Context;Lweblogic.ejb20.interfaces.BeanInfo;Ljava.lang.String;Ljava.lang.String;)Ljavax.naming.Context;(EJBDeployer.java:379)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(Lweblogic.ejb20.interfaces.BeanInfo;Lweblogic.ejb20.interfaces.DeploymentInfo;Lweblogic.management.configuration.EJBComponentMBean;Ljavax.naming.Context;)Ljavax.naming.Context;(EJBDeployer.java:1172)
     at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;)V(EJBDeployer.java:943)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1345)
     at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3142)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1583)
     at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1227)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1070)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2513)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2463)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for asyncsender-ejb.jar
     Module: asyncsender-ejb.jar     Error: Exception preparing module: EJBModule(asyncsender-ejb.jar,status=NEW)
Unable to deploy EJB: AsyncSenderEJB from asyncsender-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'jms/QueueConnectionFactory' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
     at weblogic.ejb20.deployer.EnvironmentBuilder.addJMSConnectionFactoryRef(Lweblogic.management.descriptors.ejb11.ResourceRefMBean;Ljava.util.Map;)V(EnvironmentBuilder.java:439)
     at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(Ljava.util.Collection;Ljava.util.Map;)V(EnvironmentBuilder.java:226)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(Ljavax.naming.Context;Lweblogic.ejb20.interfaces.BeanInfo;Ljava.lang.String;Ljava.lang.String;)Ljavax.naming.Context;(EJBDeployer.java:379)
     at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(Lweblogic.ejb20.interfaces.BeanInfo;Lweblogic.ejb20.interfaces.DeploymentInfo;Lweblogic.management.configuration.EJBComponentMBean;Ljavax.naming.Context;)Ljavax.naming.Context;(EJBDeployer.java:1172)
     at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;)V(EJBDeployer.java:943)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1345)
     at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3142)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1583)
     at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1227)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.ma

Embedded LDAP Server or relational database

Hi,
I'm pretty new to this subject, but I do have a question. Here is the situation.
I need to set up a login portal (in weblogic 8.1) for a webapplication. Customers
(in the future) can login into a secure part of the website, where they can modify
their personal settings and information. We are talking about < 100.000 users.
Now I was thinking of using the embedded LDAP server to set up the authorisation
and identification, but because 2 variables are needed to see if it is a customer
of the company, I am also looking into the possibility of using a relation database
(oracle) to set up the username - password authentication table.
Can somebody tell me the (dis)advantages of using LDAP instead of the relational
database (oracle)? Or give me advise which authorisation method is the best one?
Your help is needed!
Thanks in advance,
Hans
the customer more information is needed to

Ensure that the managed server is running with "Managed Server Independence Enabled" flag checked.
It can be checked on console via Environment --> Servers --> <ServerName> --> Configuration --> Tuning
For more information, please check
http://docs.oracle.com/cd/E14571_01/web.1111/e13708/failures.htm#START169
The above flag is required for the managed server to use the local LDAP repository.
Arun

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

[Security:090314]Entitlement Engine unable to connect to the embedded LDAP server

          I rebuilt the server and I still can't start cluster server but got a different
          error message. Any thoughts? (Migrating from Weblogic 6.1 to 8.1)
          =============================================================================
          LD_LIBRARY_PATH is:
          /usr/openwin/lib
          /usr/dt/lib
          /usr/lib
          /usr/local/lib
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris/oci920_8
          /opt/rv/lib
          /bin/Solaris <not found>
          /opt/BPARun1.0_A0/lib
          =============================================================================
          CLASSPATH is:
          /export/opt/weblogic/8.1_SP2/weblogic81/server
          /opt/rv/java/rvjpro.jar
          /opt/rv/java/ssmbrvclient.jar
          /opt/rv/java/tibrvj.jar
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/weblogic_sp.jar
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/weblogic.jar
          /xenv/iona/sun4/5.x/6.0/asp/6.0/lib/asp-corba.jar
          /work2/gx80747/src/Orbix6_config/etc/domains/GFINetEnv
          :$
          at weblogic.security.service.RoleManager.<init>(RoleManager.java:98)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.doRole(SecurityServiceManagerDelegateImpl.jav
          a:512)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegat
          eImpl.java:408)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.
          java:697)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelega
          teImpl.java:730)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl
          .java:873)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:719)
          at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:820)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
          at weblogic.Server.main(Server.java:32)
          Reason: weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement
          Engine unable to connect
          to the embedded LDAP server
          Cannot instantiate weblogic.entitlement.data.ldap.EData
          null


          I rebuilt the server and I still can't start cluster server but got a different
          error message. Any thoughts? (Migrating from Weblogic 6.1 to 8.1)
          =============================================================================
          LD_LIBRARY_PATH is:
          /usr/openwin/lib
          /usr/dt/lib
          /usr/lib
          /usr/local/lib
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris/oci920_8
          /opt/rv/lib
          /bin/Solaris <not found>
          /opt/BPARun1.0_A0/lib
          =============================================================================
          CLASSPATH is:
          /export/opt/weblogic/8.1_SP2/weblogic81/server
          /opt/rv/java/rvjpro.jar
          /opt/rv/java/ssmbrvclient.jar
          /opt/rv/java/tibrvj.jar
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/weblogic_sp.jar
          /export/opt/weblogic/8.1_SP2/weblogic81/server/lib/weblogic.jar
          /xenv/iona/sun4/5.x/6.0/asp/6.0/lib/asp-corba.jar
          /work2/gx80747/src/Orbix6_config/etc/domains/GFINetEnv
          :$
          at weblogic.security.service.RoleManager.<init>(RoleManager.java:98)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.doRole(SecurityServiceManagerDelegateImpl.jav
          a:512)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegat
          eImpl.java:408)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.
          java:697)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelega
          teImpl.java:730)
          at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl
          .java:873)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:719)
          at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:820)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
          at weblogic.Server.main(Server.java:32)
          Reason: weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement
          Engine unable to connect
          to the embedded LDAP server
          Cannot instantiate weblogic.entitlement.data.ldap.EData
          null

Portal 7 and embedded LDAP server

I searched for this on support but nothing much came up on Portal 7, so here
goes:
We're thinking of moving to LDAP for user authentication. LDAP 2 is
supported by the current Portal. What LDAP version is supported by the
embedded LDAP server that comes with WLS? Can I convert sooner or later?
Do I have to wait on something?
Should I put off putting my users into LDAP 2 (OpenLDAP) or wait and use the
embedded LDAP?
Thanks,
Steve

Ture,
Can use LDAP for UUP without using it for authentication/authorization? If so,
how, or at least can you kindly point to a document that descrips how?
Thanks
Ture Hoefner <[email protected]> wrote:
Hello Steve,
I think you may be confusing the LDAP v2 specification with the WLS
6.x, 7.x
V2 LdapRealm. The "V2" in "V2 LdapRealm" does not have anything to do
with the
LDAP v2 spec. It is just version 2 of the LdapRealm (
http://e-docs.bea.com/wls/docs70/secmanage/security6.html#1071872 )
Portal
doesn't really care which LDAP server you are using (and it works with
both the
original LdapRealm and the V2 LdapRealm).
When using Portal with LDAP, there are three things you can use it
for:
1) authentication/authorization, using WLS security framework, and/or
2) read-only Unified User Profile (UUP) via LdapPropertyManager in
ldapprofile.jar to get user properties from LDAP, and/or
3) read/write UUP via your own custom EntityPropertyManager to get/set
user
properties from LDAP.
If you are using LDAP for authentication/authorization, then just follow
instructions from WLS for configuring it. Your Portal app is a J2EE
app that
will use this service from your WLS app server.
If you are using LDAP for a UUP then it doesn't really matter which LDAP
server
you use, as long as it really follows the LDAP spec. Portal just uses
JNDI to
search for attributes in the LDAP server and provides them to you as
user
properties.
Steve Lewis wrote:
I searched for this on support but nothing much came up on Portal 7,so here
goes:
We're thinking of moving to LDAP for user authentication. LDAP 2 is
supported by the current Portal. What LDAP version is supported bythe
embedded LDAP server that comes with WLS? Can I convert sooner orlater?
Do I have to wait on something?
Should I put off putting my users into LDAP 2 (OpenLDAP) or wait anduse the
embedded LDAP?
Thanks,
Steve--
Ture Hoefner
BEA Systems, Inc.
4001 Discovery Drive
Suite 340
Boulder, CO 80303
www.bea.com

Wiki server to share the embedded LDAP server

Hi all,
I know ,after installing Oracle Discussions, it must also be configured to use the same Identity Store as WebCenter Spaces. I suppose Oracle Wiki and Blog ware also need to be configured to share the same Identity Store(such as the embedded LDAP) .But I cant find some documents about it .
when I requested the Spaces Wiki page, I got a login prompt from Wiki. I want know how to config the Wiki/Blog Server to share the Embedded LDAP server .
Thanks for your help.
Best
Sunny.Zhang
Edited by: Sunny.Zhang on 2009-11-24 上午10:46

I read at documentation there´s no way to use ldap as authentication source for wiki and blog, did you find a way to do that??
thx!!!

Change the credential in embedded LDAP server

when i try to change the password credential of embedded server, server was not taking the change.
Any idea what could be the reason...
Thanks in advance,
Srini

You can use JNDI to modify the data in the embedded LDAP server. http://e-docs.bea.com/wls/docs81/secmanage/ldap.html#1100263 will get you started...
Mike
Weblogic/J2EE Security Blog: http://monduke.com

Can I use your Embeded LDAP Server?

Hi,
WebLogic Server 7.0 and 8.1 comes with an embedded LDAP Server?
I have an application that requires iPlanet Directory Server for 7000 entries.
Can I use the embedded LDAP Server to put my own entries and use it?
Regards,
Shanmugavel R P

Are these videos on mozilla.org somewhere? Please see the last section of the following page, on "Site Licensing": http://www.mozilla.org/about/legal.html

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

Second posting : Usage of embedded Portal LDAP server -

Hi All,
How to configure many instances of WLP 8.1 to use only one of it's embedded LDAP
server??
What i mean by this is that, suppose there are 5 instances of Portal, by default,all
of thse use their own LDAP servers.
But i want to configure in such a way that all 5 instances use any one of the
embedded LDAP of one of these 5 instances.
How to configure this ??
TIA, Prashanth Bhat.

Prashanth,
By default, all instances of WLP enterprise apps use the same embedded
LDAP if they are within the same domain, since everything in the same
domain shares a single security realm. Of course, a security realm can
aggregate multiple LDAP servers via the addition of security providers.
I'm not aware of any easy way to share one domain's embedded LDAP
with another domain's security realm (if that is what you're asking). It
may be possible to expose it via a read only, custom atn provider you
would have to write.
-Phil
"Prashanth " <[email protected]> wrote in message
news:[email protected]..
>
Hi All,
How to configure many instances of WLP 8.1 to use only one of it'sembedded LDAP
server??
What i mean by this is that, suppose there are 5 instances of Portal, bydefault,all
of thse use their own LDAP servers.
But i want to configure in such a way that all 5 instances use any one ofthe
embedded LDAP of one of these 5 instances.
How to configure this ??
TIA,
Prashanth Bhat.

Can't connect to weblogic embedded LDAP from an init block

Hi
I am trying to use weblogic's embedded LDAP directory in an OBIEE RPD initialisation block, using 10g security model in OBIEE 11g. I need the internal user, BISystemUser, to be validated by an init block in the rpd, but I am not able to configure the weblogic LDAP in an init block, as it is done with AD, for example.
I am following the instructions on "Viewing the Contents of the Embedded LDAP Server from an LDAP Browser" section of this document, http://docs.oracle.com/cd/E21764_01/web.1111/e13707/ldap.htm#i1104934 and I am getting: "LDAP bind failure: Can't connect to LDAP server". Weblogic is up and running, I can connect to its console, OBIEE, etc.
I am using this settings on OBIEE:
Hostname: localhost (I've tried using the actual hostname)
Base DN: dc=bifoundation_domain
Bind DN: cn=Admin
Port: 7001
(I've already reset LDAP's Admin password to a known value).
The curious thing is that I can connect to the same LDAP using the same settings with LDAPExplorerTool2 opensource tool.
Does anyone have an idea what else is missing?
Thank you.

i also have this problem..do u have any solution?

How many entries is embedded LDAP of weblogic 8.1 capable to store ? let's assume we use default LDAP schema being defined in schema.core.xml

"ming qin" <[email protected]> wrote in message news:[email protected]..
I would like to have entries as users.There are a few issues that arise as the number of users increases. The
first is management
of all these users. Will you be able to load/update/manage all of the users
via the WLS console?
You can certainly use external LDAP tools to manage the data in the WLS
embedded LDAP
server, but using an external LDAP server may offer better tools for
management than those
offered in WLS.
The second is performance. Since the ldap server embedded within WLS uses
in-memory
indices, the time to load the indices and the memory required for storing
them increases as
the number of users increases. 20-50K seems to have reasonable performance.
The last is extensibility. The WLS default authenticator stores user,
description, and password.
You may have different requirements and want to store additional
information.

Portal and Netscape LDAP server integration

Hi,
I am trying to integrate Netscape LDAP server (6.0) with portal server 7, but
having lots of trouble doing that.
I've followed the instructions in the developer guide and completed the following
steps:
1. added a CustomRealm named defaultLDAPRealmForNetscapeDirectoryServer in config.xml
and modified the entries to fit my environment.
2. Deployed ldapprofile.jar and customized the env variables.
After these two steps, nothing happened. Then I did the third step:
3. added a iPlanet Authenticator to the realm CompatibilityRealm, which is my
default realm for the server.
However, after step 3, I wasn't able to boot weblogic server. Please note I have
create two users, system and weblogic in my LDAP server.
I copied the stack trace below. Any suggestions will be greatly appreciated.
Weiguo
C:\prog\bea\user_projects\portalDemoDomain>"C:\prog\bea\jdk131_03\bin\java" -hotspot
-Xms128m -Xmx128m -XX:MaxPermSize=128m -Dcommerce.properties="C:\prog\bea\weblogic700\portal\weblogiccommerce.properties"
-Dweblogic.Name=portalDemoServer
-Dbea.home="C:\prog\bea" -Dweblogic.management.username= -Dweblogic.management.p
assword= -Dweblogic.ProductionModeEnabled=true -Dweblogic.management.discover=fa
lse -Djava.security.policy=="C:\prog\bea\weblogic700\server\lib\weblogic.policy"
weblogic.Server
<Nov 4, 2002 1:18:45 PM EST> <Info> <Security> <090065> <Getting boot identity
from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
Starting WebLogic Server...
<Nov 4, 2002 1:19:06 PM EST> <Notice> <Management> <140005> <Loading configuration
C:\prog\bea\user_projects\portalDemoDomain\.\config.xml>
<Nov 4, 2002 1:19:21 PM EST> <Notice> <Security> <090093> <No configuration data
was found on server portalDemoServer for realm CompatibilityRealm.>
<Nov 4, 2002 1:19:21 PM EST> <Notice> <Security> <090082> <Security initializing
using realm CompatibilityRealm.>
<Nov 4, 2002 1:19:21 PM EST> <Critical> <WebLogicServer> <000364> <Server failed
during initialization. Exception:java.lang.SecurityException: Authentication for
user weblogic denied
java.lang.SecurityException: Authentication for user weblogic denied at
weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1166)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)
>
<Nov 4, 2002 1:19:21 PM EST> <Emergency> <WebLogicServer> <000342> <Unable to
in
itialize the server: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user weblogic denied
java.lang.SecurityException: Authentication for user weblogic denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1166)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.SecurityException: Authentication for user weblogic denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1166)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user weblogic denied
java.lang.SecurityException: Authentication for user weblogic denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1166)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)

Thanks a lot Scott. I followed your instructions and got it working to a certain
degree. I am pretty happy about the results.
There are still a few issues:
1. I had to create groups and users in my directory server in order to boot up
and logon to the server. This is expected, but is it possible to export these
user/group settings from the embedded LDAP server so that I can import them into
my directory server? Currently, the only way is manual and it's error prone. A
lot of trial and error has to happen to get there.
2. It seems that using Netscape LDAP server only allows read-only access. This
means we have to create new users/groups outside of the portal server and one
other side effect is self-registration is impossible, unless we use custom security
providers. Is this assessment correct? Since LDAP integration is so important,
wouldn't it be nice if BEA have that built-in and all we need to do is to switch
to and configure it?
3. I got duplicate users and groups in compatibility security. Obviously, one
set is from my LDAP server and the other is from the embedded one. I tried to
remove to embedded LDAP authenticator, but the duplicates are still there. How
can I get rid of the duplicates - I only want the ones from my LDAP server?
Thanks again Scott.
Weiguo
Scott Dunbar <[email protected]> wrote:
Weiguo,
WLP 7.0 uses a compatibility realm only and will not work with the
custom realm that you created for the Netscape directory server.
Configuring an LDAP compatibility realm isn't too bad and its
configuration is much like 4.0. However, it can be hard to configure
initially from the console. One way is to shut your server down and
modify config.xml directly - but make sure you make a backup copy first!
Then add something like:
<CachingRealm BasicRealm="myRealm" CacheCaseSensitive="true"
Name="wlcsCachingRealm"/>
<CustomRealm
ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));
user.dn=ou=people,dc=beasys,dc=com;
server.principal=uid=dirmanager,ou=people,dc=beasys,dc=com;
membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));
group.filter=(&(cn=%g)(objectclass=groupofuniquenames));
server.host=somehost.beasys.com;
group.dn=ou=groups,dc=beasys,dc=com"
Name="myRealm" Password="your_password_here"
RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
will enable your LDAP server. After this is setup it will be much
easier to configure via the console. Obviously you'll need to update
the parameters above for your configuration.
Weiguo Wang wrote:
Hi,
I am trying to integrate Netscape LDAP server (6.0) with portal server7, but
having lots of trouble doing that.
I've followed the instructions in the developer guide and completedthe following
steps:
1. added a CustomRealm named defaultLDAPRealmForNetscapeDirectoryServerin config.xml
and modified the entries to fit my environment.
2. Deployed ldapprofile.jar and customized the env variables.
After these two steps, nothing happened. Then I did the third step:
3. added a iPlanet Authenticator to the realm CompatibilityRealm, whichis my
default realm for the server.
However, after step 3, I wasn't able to boot weblogic server. Pleasenote I have
create two users, system and weblogic in my LDAP server.
I copied the stack trace below. Any suggestions will be greatly appreciated.
Weiguo
C:\prog\bea\user_projects\portalDemoDomain>"C:\prog\bea\jdk131_03\bin\java"-hotspot
-Xms128m -Xmx128m -XX:MaxPermSize=128m -Dcommerce.properties="C:\prog\bea\weblogic700\portal\weblogiccommerce.properties"
-Dweblogic.Name=portalDemoServer
-Dbea.home="C:\prog\bea" -Dweblogic.management.username= -Dweblogic.management.p
assword= -Dweblogic.ProductionModeEnabled=true -Dweblogic.management.discover=fa
lse -Djava.security.policy=="C:\prog\bea\weblogic700\server\lib\weblogic.policy"
weblogic.Server
<Nov 4, 2002 1:18:45 PM EST> <Info> <Security> <090065> <Getting bootidentity
from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
Starting WebLogic Server...
<Nov 4, 2002 1:19:06 PM EST> <Notice> <Management> <140005> <Loadingconfiguration
C:\prog\bea\user_projects\portalDemoDomain\.\config.xml>
<Nov 4, 2002 1:19:21 PM EST> <Notice> <Security> <090093> <No configurationdata
was found on server portalDemoServer for realm CompatibilityRealm.>
<Nov 4, 2002 1:19:21 PM EST> <Notice> <Security> <090082> <Securityinitializing
using realm CompatibilityRealm.>
<Nov 4, 2002 1:19:21 PM EST> <Critical> <WebLogicServer> <000364> <Serverfailed
during initialization. Exception:java.lang.SecurityException: Authenticationfor
user weblogic denied
java.lang.SecurityException: Authentication for user weblogic deniedat
weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1166)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)
<Nov 4, 2002 1:19:21 PM EST> <Emergency> <WebLogicServer> <000342><Unable to
in
itialize the server: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user weblogicdenied
java.lang.SecurityException: Authentication for user weblogic denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1166)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)
The WebLogic Server did not start up properly.
Exception raised:
java.lang.SecurityException: Authentication for user weblogic denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1166)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user weblogicdenied
java.lang.SecurityException: Authentication for user weblogic denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1166)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)
scott dunbar bea systems,
inc.
[email protected] boulder, co
303 998 2125 usa

WebLogicServer Embedded LDAP Error!!

Hi,
In the weblogic server environment I am facing the below issue while starting the admin server.
<Error> <EmbeddedLDAP> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372840341006> <BEA-171500> <The embedded LDAP Configuration file: 'Oracle\Middleware\wlserver_10.3\server\lib\adaptertypes.prop' was not found and the embedded LDAP server has not been started. To resolve the problem, ensure that weblogic.home is defined correctly (it should have a lib subdirectory that contains this file).>
<Critical> <WebLogicServer> <AdminServer> <main> <<WLS Kernel>> <> <> <1372840341022> <BEA-000386> <Server subsystem failed. Reason: weblogic.ldap.EmbeddedLDAPException: Could not find configuration files - see log file for more information
weblogic.ldap.EmbeddedLDAPException: Could not find configuration files - see log file for more information
at weblogic.ldap.EmbeddedLDAP.validateVDEConfigFiles(EmbeddedLDAP.java:936)
at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:255)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
The adaptertypes.prop file is not available in the Oracle\Middleware\wlserver_10.3\server\lib location.
Please advise me on how to resolve this issue..
Thanks

BEA-171500
Error: The embedded LDAP Configuration file: fileName was not found and the embedded LDAP server has not been started. To resolve the problem, ensure that weblogic.home is defined correctly (it should have a lib subdirectory that contains this file).
Description
The lib directory contains the configuration files required for the embedded LDAP server. If those files are missing or the appropriate directory cannot be found, then the embedded LDAP server cannot initialize.
Cause
The embedded LDAP server cannot find the specified file. This file is installed as part of the installation process. Most likely, the default directory is not the server root directory and the lib subdirectory cannot be found.
Action
Set the default directory to the server root directory or set the location of the embedded LDAP server configuration files via the weblogic.EmbeddedLDAPConfigDirectory system property.
As suggested in the Action plan for error code 171500,try setting up EmbeddedLDAPConfigDirectory system property in the server start-up script or in setDomainEnv.sh script.
You can set the same as JAVA_OPTIONS in the script.
e.g.
JAVA_OPTIONS="-Dweblogic.EmbeddedLDAPConfigDirectory=/home/mwhome1/wlserver_10.3/server/lib ${JAVA_OPTIONS}"
export JAVA_OPTIONS
Hope this helps!!
Thanks,
Vijaya

Embedded LDAP Server Replication

Similar Messages

Maybe you are looking for