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.

Similar Messages

Weblogic Portal & LDAP Server

Hi,
I'm currently working on a portal project, where i will need to integrate WLP
8.1 w/ existing LDAP server(like Sun One Directory). I want to know how to..
1. integrate WLP 8.1 w/ existing LDAP directory server (Sun One Directory). If
so can WLP can be configured to use Sun One for authorization?
2. If not possible, is WL LDAP server full LDAP v3 compliant? is there a way to
synchronize WL LDAP w/ Sun One Directory?
Thanks in advance,
Venki

hi venki..
in fact i m facing the same issue..
if u ve made any progress in this regard..please let me know
any help will be appreciated..
thnks

Usage of external LDAP server with Portal

Hi All,
We are in a situation to use external LDAP server with WLP 8.1. These are the
constraints we have to deal with:
1. Only read is allowed from this LDAP server.
2. This would be used for authentication purpose
If thats the case, how can we use Visitor Entitlements/Delegated Admin and Group
creation using Portal Admin tool since this will write to the configured LDAP
server.
Can somebody answer my question:
1. Can we use external LDAP server - just for authetication (I know this is possible
by using JAAS LoginModule, but I just want to get confirmed on this ) and
2. Use default and embedded LDAP server for all others like Group/Visitor Entitlements/DAs.
Any relevant pointers are also welcome.
TIA,
Prashanth Bhat.

Thanks for th ereply. Some of your answers are not clear. Can you pls eloborate
on this?? Pls see my comments below.
"Johnson" <[email protected]> wrote:
>
Phil,
Can I use embedded LDAP for production?
Thanks
Lawrence
"Phil Griffin" <BEA> wrote:
"Prashanth " <[email protected]> wrote in message
news:[email protected]..
Hi All,
We are in a situation to use external LDAP server with WLP 8.1. Theseare
the
constraints we have to deal with:
1. Only read is allowed from this LDAP server.
2. This would be used for authentication purpose
If thats the case, how can we use Visitor Entitlements/Delegated Adminand
Group
creation using Portal Admin tool since this will write to the configuredLDAP
server.
Can somebody answer my question:
1. Can we use external LDAP server - just for authetication (I knowthis
is possible
by using JAAS LoginModule, but I just want to get confirmed on this) and
>
You can add the external LDAP server just for authentication, but in
versions through
8.1 SP2 WLP will want to verify the user exists (via the UserReaderMBean)
during
the login process (this check has been removed in SP3). A work around
is to
duplicate
the user in a provider that does impl UserReaderMBean.
Prashanth : You mean to say we have to duplicate the User in embedded LDAP server
also??
>>
2. Use default and embedded LDAP server for all others like Group/VisitorEntitlements/DAs.
>
Yes, the default/embedded LDAP can still be used for DA/visitor
entitlements. In the current
release, the Portal Admin Tools can only be configured to use a single
authentication provider
while forming entitlements. In SP3, all configured providers are
listed/usable by the tools.Prashanth : How can we configure Portal Admin tool to use authentication provider
for entitlements??
>>
Any relevant pointers are also welcome.
TIA,
Prashanth Bhat.

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

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

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

Steps for portal and Microsoft LDAP server integration

Hi,
Could any one guide me steps for portal and Microsoft LDAP server integration. Need it urgently.
Thanks in advance.
Regards,
Niraj

Please don't cross post in multiple forums..

How can portal use two different LDAP Server in UME

Hi,
My question is Can UME in portal be configured for multiple LDAP sources.Currently i have a setting in portal
as follows:
Server Name : Abcd
port : 1234
user : CN=" ",Ou=" ",Ou=" ",Dc=AD,Dc=my company,Dc=com
password :
user path : DC=AD,Dc=My company,Dc=Com
group Path : same as user path
I want to configure one more LDAP server to my portal UME,how can give values for that in above sttings.I even want these current settings to be enabled.
Do anyone have idea on this.
Thanks and Regards
Rani A

Hi again ,
I know it can be done. But how urgent is this for you.
I can get back to you in couple of days, me lil busy today.
cheers,
Anu...

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

Posting to an embedded jetty server

Hello,
I have the following piece of code based on Jakarta commons httpClient which i am using to Post data to an embedded jetty server in my swing application.
import org.apache.commons.httpclient.*;
import org.apache.commons.httpclient.methods.*;
import org.apache.commons.httpclient.params.HttpMethodParams;
import java.io.*;
public class HttpClientTutorial {
private static String url = "jetty_server_url";
public static void main(String[] args) {
    // Create an instance of HttpClient.
    HttpClient httpClient = new HttpClient();
      PostMethod postMethod = new PostMethod(url);
     String name = "Muna";
      postMethod.setRequestBody(name);
        try {
            int responseCode = httpClient.executeMethod(postMethod);
        } catch (IOException ex) {
            ex.printStackTrace();
        try {
            String responseBody = postMethod.getResponseBodyAsString();
        } catch (IOException ex) {
            ex.printStackTrace();
}The line private static String url = "jetty_server_url"; should actually be the url of the jetty server. My problem is that i do not know how to make the jetty server receive the data posted by the previous code. I can altleast instantiate a jetty server as in below:
import org.mortbay.jetty.Server;
public class Step1Driver {
     private static final String LISTEN_ADDY = "localhost:7504" ;
     public static void main( final String[] args ) {
            final Server service = new Server() ;
        try {
            service.start() ;
        } catch (Exception ex) {
            ex.printStackTrace();
               System.out.println( "Server started" ) ;
} But do no know how to make the jetty server receive the data.
Any guidance or sample code will be much appreciated.
Edited by: Antananarivo on Sep 28, 2007 9:17 AM

This is an iWeb 09 forum.
If you want further help, then I would suggest that you go and post this in the Mac OS Server forum. Click on Support and you will see the list of support forums available and scroll to the bottom of the page and find the Mac OS Server Snow Leopard 10.6 forum.
Your post really has nothing to do with iWeb itself, but posting to your server - so this post would be better in the server forum.

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

Role of LDAP server in portal

HI
Can any one tell me what is the role of LDAP server in portal
Thanks
shashank

Hi Shashak,
if you use the LDAP Server as UME User Store, the security policy from the LDAP server is enforced. This means that if the data source has defined its own security policy, there is no standard interface to pass on any error messages received from the data source to the UME user in the same level of detail and in the correct language. The user only receives a very generic error message. Therefore, you would need to adapt the Portal security policy accordingly. You can find some further information under http://help.sap.com/saphelp_nw04/helpdata/en/7f/c52442ad9f5133e10000000a155106/frameset.htm.
More general information on LDAP integration you can find under http://help.sap.com/saphelp_nw04/helpdata/en/3b/68ff407765ed6fe10000000a1550b0/frameset.htm.
Best regards,
Joerg

[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

How to configaration in LDAP Server in portal?

Hi Experts,
I configare the LDAP Server in portal , but is not configare plz send me docs
Regards,
Chandu

Hi Check this out.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/setting%2bup%2ban%2bldap%2bfor%2bthe%2bportal
Have a look at these BLOGS which tells you step step by approach to integrate LDAP with SAP EP.
Novell eDirectory 8.8 as UME Data Source for EP : Part I
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2937. [original link is broken]
UME Data Source: LDAP
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/setting%2bup%2ban%2bldap%2bfor%2bthe%2bportal
Windows Integrated Authentication via Kerberos on an LDAP data source -
NTLM with LDAP
Browse these links.
UME Data Source: LDAP
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/setting%2bup%2ban%2bldap%2bfor%2bthe%2bportal
Check these:
https://wiki.sdn.sap.com/wiki/display/HOME/ConfigureLDAPand+EP
http://help.sap.com/saphelp_nw04/helpdata/en/cc/cdd93f130f9115e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d1d13f7fb44c21e10000000a1550b0/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e1959b90-0201-0010-849c-d2b1d574768b
You can refer to the following weblinks for the same
HELP.SAP.COM
http://help.sap.com/saphelp_nw70/helpdata/EN/4e/4d0d40c04af72ee10000000a1550b0/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e1959b90-0201-0010-849c-d2b1d574768b
FORUMS
LDAP Server settings for Configuring Multiple LDAP in Portal UME.
LDAP Configuration - Multiple domains
EP7 - Multiple LDAP sample file
SAP Note
736471 UME Configuration of multiple LDAP data sources

Storing Portal Roles in LDAP server

Hi,
I want to use an LDAP server for user authentication to my portal. The documents I got from help.sap.com says about keeping an LDAP server for storing normal user attributes and the portal db for storing roles. Is there any way to store thr portal roles also in the LDAP server and retreive them for authentication. Please help
Thanks,
Ranjith

Hi Ranjith,
There is no way to store the roles in the LDAP. They are kept in the portal DB. Also, portal roles aren't used for authentication like roles are in R/3. They are used mainly for determining what a user can see in the portal.
The authentication in the portal is based on the user id and password. when you log on to the portal. You will be assigned a role(s) for what you can see in the portal. The actual authentication to application come from the back end systems. For example, even if you have a portal role that lets you have access to a transaction in R/3, if you don't have the back end authorization you won't be able to get at the data.
I hope this helps
John

Second posting : Usage of embedded Portal LDAP server -

Similar Messages

Maybe you are looking for