REALM and WL6

Question

PS: Here is the "ppsldaprealm.properties" and the
"weblogic.properties" files:
***** ppsldaprealm.properties ****************************************
# Properties for the LDAP realm used for user authentication.
com.nortel.pps.api.ldaprealm.factory=\
     com.sun.jndi.ldap.LdapCtxFactory
com.nortel.pps.api.ldaprealm.authentication=\
     simple
com.nortel.pps.api.ldaprealm.principal=\
     cn=dmanager
com.nortel.pps.api.ldaprealm.credential=\
     dmanager
com.nortel.pps.api.ldaprealm.root=\
     o=ISPServer Services Inc., c=US
# Properties for the LDAP directory
com.nortel.pps.api.directory.hostname=\
     47.128.208.226
com.nortel.pps.api.directory.port=\
     889
# Properties for the INA database
com.nortel.pps.api.database.hostname=\
     47.128.208.226
com.nortel.pps.api.database.port=\
     80
***** weblogic.properties ****************************************
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8
characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.security.realmClass=\
     com.nortel.pps.api.util.ldap.LdapRealm
# ADMINISTRATOR PROPERTIES
weblogic.administrator.name=Preside Policy Services
weblogic.httpd.session.cookie.name=PresidePolicyServices
# PRESIDE POLICY SERVICES EJB PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# Deploys EJBeans.
weblogic.ejb.deploy=\
     EJBs/ppsejb.jar
weblogic.system.nativeIO.enable=false
# DocumentRoot configuration
# The documentRoot is by default set to this directory; change
# as desired. FileServlet, SSIServlet, PageCompileServlet
# and JSPServlet use it.
weblogic.httpd.documentRoot=public_html/
# Servlet reload properties
# Put servlets and classes they depend on below this directory to take
# advantage of dynamic reloading. (WebLogic classes don't belong
# here, and NO directories can be both in your system/environment
# CLASSPATH and in the servlet classpath.) WebLogic checks for
modified
# servlets every reloadCheckSecs and reloads servlets and classes they
# depend on as needed. If reloadCheckSecs is set to -1, classes will
# never be reloaded.
weblogic.httpd.servlet.classpath=\
     webgui/ppswebgui.jar
weblogic.httpd.servlet.reloadCheckSecs=1
# WEBLOGIC JSP PROPERTIES
# Sets up automatic page compilation for JSP. Adjust init args for
# directory locations and uncomment to use.
weblogic.httpd.register.*.jsp=\
weblogic.servlet.JSPServlet
weblogic.httpd.initArgs.*.jsp=\
pageCheckSeconds=-1,\
compileCommand=D:/javasoft/jdk1.3/bin/javac,\
workingDir=public_html,\
verbose=true
# PRESIDE POLICY SERVICES SERVLET REGISTRATIONS
# Set ACLs for these as desired
weblogic.httpd.register.PPSFrontComponent=\
     com.nortel.pps.webgui.base.FrontComponent

Answer 1

Alain,
It looks like you're using a custom realm which needs
to be ported to WLS 6.0. Please consult the
WLS 6.0 documentation on how to implement a custom realm.
One trick you could try is:
1) create a custom realm via the console
2) set the custom realm's realmclassname to the
classname of your custom realm (get this from
your old weblogic.properties file)
3) use the console to set this custom realm as
the active realm - that is:
a) make a caching realm
b) make the caching realm use this custom realm
c) make the realm use the caching realm
4) copy your custom realm's properties file to the
directory you boot WLS from in each of your servers
(like you had to do in WLS 5.1)
5) Boot wls (making sure your custom realm is in
the classpath) - hopefully everything will just work.
If not, you'll need to port your custom realm
(which you should do anyway)
-Tom Moreau