problem installing JCR/ECM on WLS 9.1

[Alberto.Lagna@xxxxxxxxxxxxxxxxx]

Hi all,

1) I'm trying to deploy ECM on a BEA
WLS 9.x server.
My starting point is to try to install
JCR on WLS and then add the additional WARs, JARs and resources.

is this the proper way? Did someone
succeed to do that?


2) I have some problem even installing
JCR 1.0 on BEA WLS 9.1 on windows 2000.
I carefully followed the readme I found
in the exoJCR-1.0-weblogic-ear.zip.
I also configured my created realm with
the default Adjudication and Certification Path: it was not documented
in the readme but it was needed otherwise WLS was complaining.

after the reboot of the server I got
the following

<29-set-2006 17.11.27 CEST> <Warning>
<Connector> <BEA-190155> <Compliance checking/validation
of the resource adapter D
:\Programmi\bea-wls-9.1\weblogic91\samples\domains\wl_server\.\servers\examplesServer\tmp\_WL_user\jcr-weblogic.ear\ccz8
ih\exo-jcr.connectors.localadapter-1.0.rar
resulted in the following warnings:
The ra.xml <resourceadapter-class>
class 'org.exoplatform.connectors.jcr.adapters.local.JcrResourceAdapter'
should imple
ment java.io.Serializable but does not.>
<29-set-2006 17.11.27 CEST> <Warning>
<WorkManager> <BEA-002919> <Unable to find a WorkManager
with name exo-jcr.connect
ors.localadapter-1.0.rar. Dispatch policy
exo-jcr.connectors.localadapter-1.0.rar will map to the default WorkManager
fo
r the application jcr-weblogic.ear>
StandaloneContainer initialized using:
 file:/D:/Programmi/bea-wls-9.1/weblogic91/samples/domains/wl_server/servers/exam
plesServer/tmp/_WL_user/jcr-weblogic.ear/ccz8ih/APP-INF/classes/conf/standalone/configuration.xml
<29-set-2006 17.11.48 CEST> <Warning>
<Connector> <BEA-190155> <Compliance checking/validation
of the resource adapter D
:\Programmi\bea-wls-9.1\weblogic91\samples\domains\wl_server\.\servers\examplesServer\tmp\_WL_user\jcr-weblogic.ear\ccz8
ih\exo-jcr.connectors.rmiadapter-1.0.rar
resulted in the following warnings:
The ra.xml <resourceadapter-class>
class 'org.exoplatform.connectors.jcr.adapters.rmi.JcrRmiResourceAdapter'
should impl
ement java.io.Serializable but does
not.>
<29-set-2006 17.11.48 CEST> <Warning>
<WorkManager> <BEA-002919> <Unable to find a WorkManager
with name exo-jcr.connect
ors.rmiadapter-1.0.rar. Dispatch policy
exo-jcr.connectors.rmiadapter-1.0.rar will map to the default WorkManager
for th
e application jcr-weblogic.ear>
bindName: rmirepository
remoteName: //localhost:9999/repository
!!! BINDING ERROR: java.rmi.ConnectException:
Connection refused to host: localhost; nested exception is:
        java.net.ConnectException:
Connection refused: connect

Then I set my created realm (I called
exo-domain) the default realm and got the following

<29-set-2006 17.16.26 CEST> <Critical>
<Security> <BEA-090470> <Inconsistent security configuration,
the exo-domain secu
rity realm has been configured to use
security data in deployment descriptors but no DeployableRoleMapper has
been confi
gured with deployment enabled.>
<29-set-2006 17.16.26 CEST> <Critical>
<Security> <BEA-090470> <Inconsistent security configuration,
the exo-domain secu
rity realm has been configured to use
security data in deployment descriptors but no DeployableAuthorizer has
been confi
gured with deployment enabled.>
<29-set-2006 17.16.26 CEST> <Critical>
<WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.security.service.SecurityServiceRuntimeException:
[Security:090411]Security Realm [exo-domain] improperly confi
gured
...
Caused by: weblogic.management.utils.ErrorCollectionException:
[Security:090519]The realm exo-domain is not properly con
figured. Follow the directions in the
following errors to correctly configure the realm.
        [Security:090592]The
realm exo-domain does not have a cert path builder configured. To correct
the problem, sele
ct one of the realm"s cert path
providers as the realm"s cert path builder.
        at weblogic.security.internal.RealmValidatorImpl.validate(RealmValidatorImpl.java:53)
....
... 9 more

If I don't set the exo-domain realm
as the default one WLS is not complaining.
The realm has no user and groups. If
I try (through the WLS console) to create a user I get the following

java.lang.NullPointerException at com.bea.console.actions.security.users.createuser.CreateUser.isUniqueName(CreateUser.java:252)
at com.bea.console.actions.security.users.createuser.CreateUser.finish(CreateUser.java:186)
at 
....

even if I'm sure the user I'm creating
is not present on the system.

Any ideas?
ciao & thanks
Alberto