[quote=jclingan]Oracle Access Manager integration requires Oracle GlassFish
Server. It will not work with GlassFish Server Open Source Edition. Which
version are you using? Also, GlassFish Server 3.1.1 is not supported on
Windows 2003, so we have not tested the combination you are referring to.
However, Windows 2008 R2 is supported in 64-bit mode. Hope this helps. On Jan
10, 2012, at 1:39 PM, forums_at_java.net wrote: > Hi, > > I got GlassFish 3.1.1
working on Windows 2003 64-bit, with JDK 1.6 build 30 > (64-bit), and I've
been trying to get the integration with OAM working using > this: > >
http://docs.oracle.com/cd/E18930_01/html/821-2435/gklem.html#scrolltoc [1] >
> I got through all of the steps, but after that, when I try to restart >
GlassFish, I am seeing a NoClassDefFoundException in the server.log (this is
> transcribed, as it's running on a VM, and copy-paste doesn't work): > >
[org.apache.catalina.connector.CoyoteAdapter]...PWC3989: An exception or >
error occurred in the container during the request processing >
java.lang.NoClassDefFoundError: > > Could not initializae class
com.oblix.access.ObConfig > > at
com.sun.glassfish.oamsam.OAMAuthenticatorSAM.initialize(OAMAuthenticatorSA >
M.java:424) > > at
com.sun.enterprise.security.jmac.config.GFServerConfigProvider.createModul >
eInfo(GFServerConfigProvider.java:234) > > One of the things I'm trying to
determine is if this integration is viable > with GlassFish (and Java)
running on 64-bit Windows, so I was wondering, > would something like the
above be cause by incompatibility between the OAM > JARs (which are, I
believe, 32-bit Java) and the 64-bit Java/GlassFish? > > Or, is it something
else? The procedures are somewhat involved, and I've > gone over them several
times, double-checking, but it's still possible that I > messed something up
:(... > > Thanks, > > Jim > > > > > [1]
http://docs.oracle.com/cd/E18930_01/html/821-2435/gklem.html#scrolltoc > > --
> > [Message sent by forum member 'jimcpl'] > > View Post:
http://forums.java.net/node/882238 > >[/quote]
Hi,
FYI, I'm running the ogs version (3.1.1).
Also, FYI, I also found another message in the server.log, and
"unsatisfiedLinkError". From some other (non-related) work that I did
awhile ago, that's something to do with native (JNI)? The stacktrace for
that also references Obconfig in it, so I'm thinking that the
ObConfig-related error I poste earlier may be a side-effect of the
"unsatisfiedLinkError".
Am I 'dead in the water" with this effort (I understand about Win2K3 64-bit
non-support, per your comments)?
Jim
--
[Message sent by forum member 'jimcpl']
View Post: http://forums.java.net/node/882238