In fact, I’m wondering if the extension can run on this setup at all, given what looks like JSF incompatibility issues with my Tomcat 6 setup. The README file for the extension tells me to go grab Facelets 1.1.14, which seems to be packaged with servlet 2.4. Tomcat 6.x works with Servlet 2.5. Is that going to be a problem?

Plus, I’m getting JSF related classloader problems, when I install the jsf-impl.jar file for the JSF 1.2_04-p02 api that comes with Facelets 1.1.4. catalina.out reports this:

java.lang.LinkageError: loader constraint violation: when resolving interface method “javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;” the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature
at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1570)

Like I said, I have doubts that I can make this work on Tomcat 6 without updating various components that support this extension, which may lead me into a whole slew of other problems.

So my question for you, Hubert, is …should this work? I don’t want to spin my wheels on something that is never going to work, and I’m too ignorant to know that yet :-)

Thx in advance.

You will find the jar files for the various releases (and client, server, signature and test)
here: http://download.java.net/maven/2/com/sun/jersey/contribs/jersey-oauth/

Cheers,
Hubert

Where is the jersey Oauth library, the actual jar file. It is not available as part of jersey-1.1.4 bundle or archived zip file.

Thanks
–Mahesh

Interesting, I need to check on Express Build 8. I can
attest though that this works fine on the latest OpenSSO
releases since this is what we use for our OpenID testing.
As for Apache DS, yes it’s a nice ldap editor although
I think it does not work very well with the latest
OpenDS (2.0)…

I have noticed that in that version you also have to change ou=SelfWriteAttributes,ou=default,ou=default,ou=OrganizationConfig,ou=1.0,ou=sunEntitlementIndexes,ou=services,o=sunamhiddenrealmdelegationservicepermissions,ou=services,dc=opensso,dc=java,dc=net.

BTW. Apache Directory Studio is an excellent LDAP editor for doing this kind of stuff.

Hubert

Cheers,
Hubert

## Variables used below ..
ds_installpath == where Directory server will be deployed
suffix == root suffix for LDAP tree in DS instance
ds_instance == path to DS instance, usually /var/opt/$something
dscc_instance == path to DSCC instance, usually $ds_installpath/var/dscc6/dcc/ads
sges_installpath == where sges will be deployed, usually /opt/SUNWappserver
hostname == hostname of our host

1) download software:
download from sun.com DSEE.6.3.1.Solaris-Sparc-full.tar.gz and sges_ee-2_1-solaris-sparc-ml.bin

2) install Directory Server 6.3:
you need to unpack archives .. there will be ds6.3 and ds6.3.1-patch ..

## we need install first ds6.3
cd $ds63_unpacked/DSEE_ZIP_Distribution
./dsee_deploy install -i $ds_installpath –no-cacao

## then install patch
cd $ds_631-patch_unpacked
./dsee_deploy install -i $ds_installpath –no-cacao

3) Configure our new DS:

## create dscc instance:
cd $ds_installpath/dscc6/bin
./dsccsetup ads-create ## you’ll be prompted for passwd

## you can optionally create normal instance
cd $ds_installpath/ds6/bin
./dsadm create $ds_instance
./dsadm start $ds_instance
./dsconf create-suffix -h localhost -p 389 dc=$suffix

## and register it into our dscc one:
cd $ds_installpath/dscc6/bin
./dsccreg add-server -h localhost –description “muehehe” $ds_instance

## add ds/dscc instances as smf services:
cd $ds_installpath/ds6/bin
./dsadm stop $ds_instance
./dsadm enable-service $ds_instance
./dsadm stop $dscc_instance
./dsadm enable-service $dscc_instance
svcs -a | grep ds: ## prints out a service names, then use `svcadm enable $svc` to enable them

## OPTIONAL STEPS:
## disable cacao and smcwebserver as far as we don’t like them ;)
smcwebserver disable; smcwebserver stop
cacaoadm disable; cacaoadm stop

## heal freshly installed DS, which is already molested by cacao
cd $ds_installpath/dscc6/bin
./dsccsetup cacao-unreg

## check, if cacao deployed with ds6 is not running and if yes, use
kill -11 `pgrep cacao` ## it doesn’t deserves anything better than be segfaulted

4) install GlassFish Enterprise Server:
go where you store sges_ee-2_1-solaris-sparc-ml.bin and if it’s already not, chmod +x it

## just begin installation, you’ll be asked for few questions
./sges_ee-2_1-solaris-sparc-ml.bin -tmpdir /var/tmp/sso -console

5) configure newly installed sges:

## create domain and configure it for deploying dscc controlcenter
mkdir $sges_domaindir
cd $sges_installpath/bin
./asadmin create-domain –domaindir $sges_domaindir –adminport 4848 –user admin dscc

## append following in $sges_domaindir/dscc/config/server.policy

// Permissions for Directory Service Control Center
grant codeBase “file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/dscc/-”
{
permission java.security.AllPermission;
};

## then end the process of configuration
./asadmin start-domain –domaindir $sges_domaindir –user admin dscc
cp $ds_installpath/var/dscc6/dscc.war $sges_domaindir/dscc/autodeploy

6) check if all services are running:

## admin iface for GlassFish
https://$hostname:4848

## our Directory Server Control Center
http://$hostname:8080/dscc

7) enjoy !!