RDBMSRealm problem

Hi Everyone,
I am implementing an EJB application with Weblogic5.1, RDBMSRealm security realm. My application requires user and group select/delect/update dynamically for "users" and "groupmembers" tables in the database. It is my understanding that I can implement it by creating a custom realm based on Weblogic RDBMSRealm example. My question is
when I try to connect the "users" and "groupmembers" tables, I have to do it through EJB entity bean as normal entity bean---table match in the EJB application, or it is not allowed to implement it through EJB entity bean, or either way above is ok?
Thanks a lot.
-John

John Wang wrote:
>
My question is when I try to connect the "users" and "groupmembers" tables, I have to do it through EJB
entity bean as normal entity bean---table match in the EJB application, or it is not allowed to implement
it through EJB entity bean, or either way above is ok?The container is going to use your security realm in order to enforce
security on EJB method calls (among other things) and using EJB to
implement its own security would be a bit circular. (This is also a
reason you have to use a connection pool separate from the one used by
the rest of the application). I haven't tried this but it may be
possible to have two different ejb-name entries (and two different JNDI
names) for the same User bean in the XML deployment descriptor(s) where
one of the beans would not have any method level security. Perhaps in
the latter case the container would not call the realm and you would be
able to use the same bean with different security. Security would be
compromised in this case if you let clients other than the server access
your unsecured bean.
Alexander Petrushko
mailto:[email protected]
Consulting Services available

Similar Messages

  • RDBMSRealm problem: users logged out when using WLS console

    I have implemented RDBMSRealm for Oracle mapping it to our database tables on WLS
    6.0 SP2. It works fine except a strange problem: if users are logged in on a web
    application with FORM authentication each time an adminstrator uses the WLS console
    clicking on an item (for example "Servers" or "EJB", not only on "Security") all
    the users are logged off and the login form is presented to them. Does anybody
    experienced the same problem? Is there somebody that knows a solution?
    Romano

    Interesting, Thanks.
    I'll give this a try.
    Also, while enabling user switching and turning of the "lock on screensaver" option, I noticed the "Log out after [] minutes of activity" option in the Security preferences, which if this does what I think it does, may be my only problem.
    If this turns out to be true, i've just had a major "DOH!" moment :/
    I'll try this first and post back my results.
    Message was edited by: carl-g

  • Solution to rdbmsrealm problem

    I posted on this group with a problem getting acls for connection pools with
    the rdbms realm a couple of days ago, someone replied they were having the
    same problem.
    Having searched the newsgroup archives, a solution to the problem is to
    alter the method in RDBMSGroup from
    protected Class getUserClass() { return RDBMSUser.class;}
    to
    protected Class getUserClass() { return weblogic.security.acl.User.class; }
    (with thanks to Chuck H. Zhao where/whoever he may be)
    I've tried this and things appear to work now
    Terry

    Thanks for following up and re-posting the solution to the newsgroup !!!
    I have made this change and it has corrected the problem for me as well.
    Thanks again
    Steve
    "Terry" <[email protected]> wrote in message
    news:39c2300f$[email protected]..
    I posted on this group with a problem getting acls for connection poolswith
    the rdbms realm a couple of days ago, someone replied they were having the
    same problem.
    Having searched the newsgroup archives, a solution to the problem is to
    alter the method in RDBMSGroup from
    protected Class getUserClass() { return RDBMSUser.class;}
    to
    protected Class getUserClass() { returnweblogic.security.acl.User.class; }
    >
    (with thanks to Chuck H. Zhao where/whoever he may be)
    I've tried this and things appear to work now
    Terry

  • Problems with RDBMSRealm/WL 5.1

    We migrated our EJB-application from BEA Weblogic 4.5.1 / JDK 1.1.7 to Weblogic 5.1/JDK 1.2 . We use the RDBMSRealm for managing users, groups and acls. During the migration process we converted the txt-deployment descriptors
    of our EJBs to xml (with the DDConverter tool). An original 4.5.1 txt-DD looks like this:
    (SessionDescriptor
    beanHomeName edbau.Admin
    enterpriseBeanClassName de.tlc.edbau.ejb.sb.admin.AdminBean
    homeInterfaceClassName de.tlc.edbau.ejb.sb.admin.AdminHome
    remoteInterfaceClassName de.tlc.edbau.ejb.sb.admin.Admin
    isReentrant false
    (accessControlEntries
    ; DEFAULT [admin manager]
    ); end accessControlEntries
    (controlDescriptors
    (DEFAULT
    transactionAttribute TX_REQUIRED
    ); end isolationLevel
    ); end controlDescriptors
    (environmentProperties
    ; realmName "my.realm"
    ; homeClassName
    ; ejbObjectClassName
    maxBeansInFreePool 20
    maxBeansInCache 1000
    idleTimeoutSeconds 600
    ); end environmentProperties
    ; Session Bean specific properties
    stateManagementType STATELESS_SESSION
    sessionTimeout 60; seconds
    ; end Session Bean specific props
    ); end SessionDescriptor
    The DDConverter created the following xml-DD (ejb-jar.xml):
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
         <ejb-name>edbau.Admin</ejb-name>
         <home>de.tlc.edbau.ejb.sb.admin.AdminHome</home>
         <remote>de.tlc.edbau.ejb.sb.admin.Admin</remote>
         <ejb-class>de.tlc.edbau.ejb.sb.admin.AdminBean</ejb-class>
         <session-type>Stateless</session-type>
         <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
         <method>
         <ejb-name>edbau.Admin</ejb-name>
         <method-intf>Remote</method-intf>
         <method-name>*</method-name>
         </method>
         <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    Everything seemed to work fine; then I tried to start a test client (the login was done with a user,
    which existed in the RDBMSRealm).
    The result of that test client was:
    method Security violation: insufficient permission to access method
    java.rmi.RemoteException: Security violation: insufficient permission to access
    method
    at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.j
    ava:76)
    at de.tlc.edbau.ejb.sb.admin.AdminBeanEOImpl_WLStub.getAllBEOEBR(AdminBe
    anEOImpl_WLStub.java:480)
    at de.tlc.edbau.ejb.sb.admin.AdminBeanEOImpl_ServiceStub.getAllBEOEBR(Co
    mpiled Code)
    at de.tlc.edbau.ejb.test.ADMINTester.main(Compiled Code)
    I didnt specify any permissions for this bean. So I read in weblogic-doc:
    Assigning method permissions
    The steps that follow describe how to limit access to individual EJB method calls by assigning method-level permissions.
    Default method permissions in WebLogic Server
    If you specify no method-level permissions for an EJB (there is no method-permission stanza in ejb-jar.xml), WebLogic Server provides "guest" access to all EJB methods in the .jar file. This ensures that EJB methods have some default access permission when deployed on WebLogic Server.
    If you want to specify method-level permissions you must do so for all methods in all EJBs stored in the .jar file. If you specify method permissions for even a single EJB method, WebLogic Server denies access for any methods that do not have permissions defined in the ejb-jar file.
    After reading the weblogic-doc, i didnt understand why I got the upper mentioned exception ??
    Finally (to have a workaround), I used the Deployer-Tool (5.1) to create the roles and users,
    which were already defined in the RDBMSRealm (in the according tables). For testing purposes, all
    roles (groups) had all permissions for all EJBs.
    So my question: Is it really necessary to define all users/groups(roles) in the database and do
    the same in the DD of our application ? This might cause huge administration problems ! What is the
    clean solution for that problem ?
    Thanx for your help !
    Mike

    Try to restore it... I'm hating this iOS 5.1, everything was working much better before it was released. I shouldn't have upgraded...

  • Problem creating user in RDBMS realm Using com.bea.wlpi.rdbmsrealm.RDBMSRealm

    Hi,
    I am currently using WLI 2.0 SP2 installation. Here is a very unusual thing I
    noticed. Can somebody tell me what is going on ???
    1 : I have set up the security realm as indicated in the config.xml file. As far
    as I understand, the caching realm entry has attribute pointing to the wlpiRDBMSRealm,
    which is a RDBMS implementation from the WLI 2.0 SP2 distribution.
    2: I start the server, open the WLS console, and create a new user through the
    console. I get no error message and it seems to work fine. ( I also click on the
    save it to database link, and it returns with msg that cache is refreshed ).
    3: I see an entry in the fileRealm.properties file, but no record is inserted
    in the WLSUSER table in the database.
    Since the RDBMS realm (from WLI distribution) is defined as basic
    realm implementation, should it not insert entry into the database, instead of
    the file realm.
    Is this a general problem ( any RDBMS realm ) or is it specific to the WLI ?
    Is there anything that I have not configured here that is causing this behavior
    Is it just refreshing the cache instead of inserting record in DB ?
    Why should it insert entry into fileRealm.properties ?
    Thanks,
    Girish
    [noaa1.zip]

    Hi,
    I turned on the caching realm through the WLS Console, (Security).
    After this I get a very unusual error, which seems to be comming
    from the RDBMS implementation class (from WLI 2.0 SP2 distribution).
    Here is the msg that I get while WLS server boots (the WLS server boots ok, but
    WLPI does not initialize) ....
    Unable to initialize WebLogic Process Integrator:
    SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
    autocommit is OFF.
    at c8e.k.j.l_(Unknown Source)
    at c8e.k.j.l_(Unknown Source)
    at c8e.k.j.j_(Unknown Source)
    at c8e.k.n.checkIfClosed(Unknown Source)
    at c8e.k.n.movePosition(Unknown Source)
    at c8e.k.n.movePosition(Unknown Source)
    at c8e.k.n.next(Unknown Source)
    at com.bea.wlpi.rdbmsrealm.RDBMSDelegate.getGroup(RDBMSDelegate.java:425)
    at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:235)
    at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
    at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
    at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
    at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
    at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
    at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
    at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
    at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
    at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.Kernel.execute(Kernel.java:250)
    at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
    at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
    at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
    <Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <WebLogic Server started>
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    com.bea.wlpi.rdbmsrealm.RDBMSException: caught SQL exception - with nested exception:
    [SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
    autocommit is OFF.]
    at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:242)
    <Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <ListenThread listening
    on port 7101>
    at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
    at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
    at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
    at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
    at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
    at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
    at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
    at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
    at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
    at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.Kernel.execute(Kernel.java:250)
    at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
    at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
    at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "Girish Gupte" <[email protected]> wrote:
    >
    >
    >
    Hi,
    I am currently using WLI 2.0 SP2 installation. Here is a very unusual
    thing I
    noticed. Can somebody tell me what is going on ???
    1 : I have set up the security realm as indicated in the config.xml file.
    As far
    as I understand, the caching realm entry has attribute pointing to the
    wlpiRDBMSRealm,
    which is a RDBMS implementation from the WLI 2.0 SP2 distribution.
    2: I start the server, open the WLS console, and create a new user through
    the
    console. I get no error message and it seems to work fine. ( I also click
    on the
    save it to database link, and it returns with msg that cache is refreshed
    3: I see an entry in the fileRealm.properties file, but no record is
    inserted
    in the WLSUSER table in the database.
    Since the RDBMS realm (from WLI distribution) is defined as basic
    realm implementation, should it not insert entry into the database, instead
    of
    the file realm.
    Is this a general problem ( any RDBMS realm ) or is it specific to the
    WLI ?
    Is there anything that I have not configured here that is causing this
    behavior
    Is it just refreshing the cache instead of inserting record in DB ?
    Why should it insert entry into fileRealm.properties ?
    Thanks,
    Girish

  • Problem w. newUser(): WLS6.0, RDBMSRealm

    Hi,
    I'm trying to create a new user with the RDBMSRealm. The user is created, but not
    saved in the Cloudscape db (the name apperas in the console but disappears at restart).
    Does anybody know why..? Am I doing something wrong? I'm using the following code:
    RDBMSRealm rdbms = (RDBMSRealm)Security.getCurrentUser().getRealm();
    User created = rdbms.newUser("zapa", "zapa", null);
    Any help greatly appreciated!
    Regards,
    Rolle

    "Seshadri" <[email protected]> wrote:
    >
    Have a bit of a problem with the cloudscape rdbms security realm shipped
    with weblogic
    6.1
    I am trying the sample rdbmsrealm secuirty example in WLS6.1 SP2.
    I changed the class RDBMSRealm.java to add a public method say
    display();
    From my jsp page I have
    RDBMSRealm realm = new RDBMSRealm();
    realm.display();
    realm.getUser("jason").getName();
    When I run this I am able to access the display method, but
    the call to getUser fails with
    <Feb 27, 2002 12:58:11 PM PST> <Error> <HTTP> <[WebAppServletContext(5278096,for
    mauth,/formauth)] Servlet failed with Exception
    ERROR 40XL1: A lock could not be obtained within the time requested
    at c8e.c_.b.newException(Unknown Source)
    at c8e._g.g.lockObject(Unknown Source)
    at c8e._g.f.zeroDurationlockObject(Unknown Source)
    at c8e.as.r.lockRecordForRead(Unknown Source)
    at c8e.s.h.lockPositionForRead(Unknown Source)
    at c8e.s.d.fetchRows(Unknown Source)
    at c8e.w.g.fetchNextGroup(Unknown Source)
    at c8e.h.h.e(Unknown Source)
    at c8e.h.h.getNextRowCore(Unknown Source)
    at c8e.h.z_.getNextRow(Unknown Source)
    at c8e.k.n.movePosition(Unknown Source)
    at c8e.k.n.movePosition(Unknown Source)
    at c8e.k.n.next(Unknown Source)
    at examples.security.rdbmsrealm.RDBMSDelegate.getUser(RDBMSDelegate.java
    :270)
    In my JSP page when I
    weblogic.security.acl.CachingRealm realm =
    (weblogic.security.acl.CachingRealm) weblogic.security.acl.Security.getRealm();
    realm.getUser() works, But I am not able to access/find display()
    realm.display();
    Any suggestions would help. Thanks
    Seshadri
    <CachingRealm BasicRealm="defaultRDBMSRealmForCloudscape" Name="defaultCachingRealm"/>
    <Realm CachingRealm="defaultCachingRealm" FileRealm="wl_default_file_realm"
    Name="wl_default_file_realm"/>

  • Database connection problem from RDBMSRealm

    Hi Everyone,
    I am implementing an application with Weblogic5.1, RDBMSRealm, Merant type 4 JDBC driver and SQL server 7.0. When I am starting
    the Weblogic server, I am getting an error as described as follows. Can anyone there give me a clue?
    As you see, I am using Merant Spy JDBC driver (for debugging).
    With this kind of driver, any JDBC calls to database server
    in the code will be displayed.
    As you know, there are a quite number of "prepareStatement" from RDBMSRealm. When the weblogic server is starting, they have to be initialized. I don't understand why it needs to make a connection for each "prepareStatement"?, and why it is still in connection mode after it is initialized?
    Thanks a lot.
    -John
    Thu Jan 18 16:01:00 EST 2001:<I> <System Props> weblogic.system.home = Ppg
    Thu Jan 18 16:01:00 EST 2001:<I> <System Props> weblogic.system.name = PpgServer
    Thu Jan 18 16:01:00 EST 2001:<I> <WebLogicServer> Loaded License : D:/weblogic/license/WebLogicLicense.xml
    Thu Jan 18 16:01:00 EST 2001:<I> <WebLogicServer> Server loading from weblogic.class.path. EJB redeployment enabled.
    registerDriver: driver[className=com.merant.datadirect.jdbc.sqlserver.SQLServerDriver,com.merant.datadirect.jdbc.sqlserver.SQLServerDriver@d071d920]
    skipping: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@fdd92d]
    spy>> Connection accepted by SQLServer
    spy>> OK (Connection[1])
    getConnection returning driver[className=com.merant.jdbcspy.SpyDriver,com.merant.jdbcspy.SpyDriver@cee1d920]
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT U_NAME, U_PASSWORD FROM users WHERE U_NAME = ?
    spy>> OK (PreparedStatement[1])
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries WHERE A_NA..
    spy>> OK (PreparedStatement[2])
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT U_NAME, U_PASSWORD FROM users
    spy>> OK (PreparedStatement[3])
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT GM_GROUP, GM_MEMBER FROM groupmembers ORDER BY GM_GROUP
    spy>> OK (PreparedStatement[4])
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries ORDER BY A..
    spy>> java.sql.SQLException: [MERANT][SQLServer JDBC Driver][SQLServer]Login fa..
    java.sql.SQLException: [MERANT][SQLServer JDBC Driver][SQLServer]Login failed. The maximum simultaneous user count of 5 licenses for this 'Standard Edition' server has been exceeded. Additional licenses should be ob
    tained and installed or you should upgrade to a full version.
    at com.merant.datadirect.jdbc.base.BaseExceptions.getException(BaseExceptions.java:72)
    at com.merant.datadirect.jdbc.sqlserver.tds.TDSRequest.processErrorToken(TDSRequest.java:401)
    at com.merant.datadirect.jdbc.sqlserver.tds.TDSRequest.processReplyToken(TDSRequest.java:1571)
    at com.merant.datadirect.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(TDSLoginRequest.java:549)
    at com.merant.datadirect.jdbc.sqlserver.tds.TDSRequest.processTokensInReply(TDSRequest.java, Compiled Code)
    at com.merant.datadirect.jdbc.sqlserver.tds.TDSRequest.processReply(TDSRequest.java:1661)
    at com.merant.datadirect.jdbc.sqlserver.SQLServerImplConnection.open(SQLServerImplConnection.java:98)
    at com.merant.datadirect.jdbc.base.BaseConnection.getNewImplConnection(BaseConnection.java:405)
    at com.merant.datadirect.jdbc.base.BaseConnection.getImplConnection(BaseConnection.java:333)
    at com.merant.datadirect.jdbc.base.BaseStatement.getImplConnection(BaseStatement.java:1223)
    at com.merant.datadirect.jdbc.base.BaseStatement.getImplStatement(BaseStatement.java:1241)
    at com.merant.datadirect.jdbc.base.BasePreparedStatement.<init>(BasePreparedStatement.java:63)
    at com.merant.datadirect.jdbc.base.BaseConnection.prepareStatement(BaseConnection.java:960)
    at com.merant.jdbcspy.SpyConnection.prepareStatement(Unknown Source)
    at com.bea.ppg.rdbmsrealm.RDBMSDelegate.prepare(RDBMSDelegate.java:116)
    at com.bea.ppg.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:187)
    at com.bea.ppg.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:912)
    at weblogic.utils.reuse.Pool.getInstance(Pool.java:57)
    at com.bea.ppg.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:115)
    at com.bea.ppg.rdbmsrealm.RDBMSRealm.getPermission(RDBMSRealm.java:515)
    at weblogic.security.acl.CachingRealm.getPermission(CachingRealm.java:1698)
    at weblogic.security.acl.CachingRealm.setupAcls(CachingRealm.java, Compiled Code)
    at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:706)
    at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:564)
    at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1750)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:99)
    at weblogic.Server.main(Server.java:65)
    at weblogic.Server.main(Server.java:55)
    Unable to initialize server: com.bea.ppg.rdbmsrealm.RDBMSException: realm initialization failed, Connection.prepareStatement() failed on statement "SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries ORDER BY A
    _NAME, A_PRINCIPAL", - with nested exception:
    [java.sql.SQLException: [MERANT][SQLServer JDBC Driver][SQLServer]Login failed. The maximum simultaneous user count of 5 licenses for this 'Standard Edition' server has been exceeded. Additional licenses should be o
    btained and installed or you should upgrade to a full version.]
    fatal initialization exception
    com.bea.ppg.rdbmsrealm.RDBMSException: realm initialization failed, Connection.prepareStatement() failed on statement "SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries ORDER BY A_NAME, A_PRINCIPAL", - with
    nested exception:
    [java.sql.SQLException: [MERANT][SQLServer JDBC Driver][SQLServer]Login failed. The maximum simultaneous user count of 5 licenses for this 'Standard Edition' server has been exceeded. Additional licenses should be o
    btained and installed or you should upgrade to a full version.]
    at com.bea.ppg.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:210)
    at com.bea.ppg.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:912)
    at weblogic.utils.reuse.Pool.getInstance(Pool.java:57)
    at com.bea.ppg.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:115)
    at com.bea.ppg.rdbmsrealm.RDBMSRealm.getPermission(RDBMSRealm.java:515)
    at weblogic.security.acl.CachingRealm.getPermission(CachingRealm.java:1698)
    at weblogic.security.acl.CachingRealm.setupAcls(CachingRealm.java, Compiled Code)
    at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:706)
    at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:564)
    at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1750)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:99)
    at weblogic.Server.main(Server.java:65)
    at weblogic.Server.main(Server.java:55)
    D:\weblogic>goto finish
    D:\weblogic>cd Ppg
    D:\weblogic\Ppg>ENDLOCAL
    D:\weblogic\Ppg>

    John, this should be fairly easy to correct. Make sure that you are closing
    your prepared statements after you finish with then. Even if you have 3
    connections open and you don't close your statements, more connections will
    be opened to take care of need.
    Hope that this helps.
    Paul
    "John Wang" <[email protected]> wrote in message
    news:[email protected]...
    >
    All SQL server connections come from the code itself. As you see in themessage output, everytime when the server is initalizing a
    "prepareStatement(String sql)" which comes from RDBMSRealm, it is making a
    connection. When it starts the sixth, it is broken. In other words, to make
    the server start with RDMBSRealm, I have to have the number of SQL server
    licence at least the same as the number of "prepareStatement(String sql)" in
    RDBMSRrealm realm. Is my understanding correct here? Why is it still in
    connection mode after one "prepareStatement" is initialized? Any ideas?
    >
    Thanks.
    -John
    "Pete Cressman" <[email protected]> wrote:
    The same error? Hmm... the trace says:
    java.sql.SQLException: [MERANT][SQLServer JDBC Driver][SQLServer]Login
    failed. The maximum simultaneous user count of 5 licenses for this 'Standard
    Edition' server has been exceeded. Additional licenses should be obtained
    and installed or you should upgrade to a full version.
    >>
    Find out who is making so many connections. Sorry, that's the best I cansuggest. Good luck.
    >>
    "John Wang" <[email protected]> wrote:
    Hi Pete,
    Thanks for your help.
    As you suggested, I modified the value DEFAULT_POOL_SIZE = 2 or 1 and
    compiled it again. When I run, it still gave me the same error message. What
    could it be wrong?
    >>>
    -John
    "Pete Cressman" <[email protected]> wrote:
    RDBMSDelegates are pooled by RDBMSRealm. The connection in each
    RDBMSDelegate is held open until the class is disposed. the default pool
    size is 6. Your license is limited to 5 connections total. Modify the code
    in RDBMSRealm so DEFAULT_POOL_SIZE = 2 or 3.
    >>>>
    "John Wang" <[email protected]> wrote:
    Hi Everyone,
    I am implementing an application with Weblogic5.1, RDBMSRealm, Merant
    type 4 JDBC driver and SQL server 7.0. When I am starting
    the Weblogic server, I am getting an error as described as follows.Can anyone there give me a clue?
    >>>>>
    As you see, I am using Merant Spy JDBC driver (for debugging).
    With this kind of driver, any JDBC calls to database server
    in the code will be displayed.
    As you know, there are a quite number of "prepareStatement" fromRDBMSRealm. When the weblogic server is starting, they have to be
    initialized. I don't understand why it needs to make a connection for each
    "prepareStatement"?, and why it is still in connection mode after it is
    initialized?
    >>>>>
    Thanks a lot.
    -John
    Thu Jan 18 16:01:00 EST 2001:<I> <System Props> weblogic.system.home =Ppg
    Thu Jan 18 16:01:00 EST 2001:<I> <System Props> weblogic.system.name =PpgServer
    Thu Jan 18 16:01:00 EST 2001:<I> <WebLogicServer> Loaded License :D:/weblogic/license/WebLogicLicense.xml
    Thu Jan 18 16:01:00 EST 2001:<I> <WebLogicServer> Server loading fromweblogic.class.path. EJB redeployment enabled.
    registerDriver:driver[className=com.merant.datadirect.jdbc.sqlserver.SQLServerDriver,com.me
    rant.datadirect.jdbc.sqlserver.SQLServerDriver@d071d920]
    skipping:driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@fdd92d]
    spy>> Connection accepted by SQLServer
    spy>> OK (Connection[1])
    getConnection returningdriver[className=com.merant.jdbcspy.SpyDriver,com.merant.jdbcspy.SpyDriver@c
    ee1d920]
    >>>>>
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT U_NAME, U_PASSWORD FROM users WHERE U_NAME = ?
    spy>> OK (PreparedStatement[1])
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentriesWHERE A_NA..
    spy>> OK (PreparedStatement[2])
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT U_NAME, U_PASSWORD FROM users
    spy>> OK (PreparedStatement[3])
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT GM_GROUP, GM_MEMBER FROM groupmembers ORDER BYGM_GROUP
    spy>> OK (PreparedStatement[4])
    spy>> Connection[1].prepareStatement(String sql)
    spy>> sql = SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentriesORDER BY A..
    spy>> java.sql.SQLException: [MERANT][SQLServer JDBCDriver[SQLServer]Login fa..
    java.sql.SQLException: [MERANT][SQLServer JDBC Driver][SQLServer]Login
    failed. The maximum simultaneous user count of 5 licenses for this 'Standard
    Edition' server has been exceeded. Additional licenses should be ob
    tained and installed or you should upgrade to a full version.
    atcom.merant.datadirect.jdbc.base.BaseExceptions.getException(BaseExceptions.j
    ava:72)
    atcom.merant.datadirect.jdbc.sqlserver.tds.TDSRequest.processErrorToken(TDSReq
    uest.java:401)
    atcom.merant.datadirect.jdbc.sqlserver.tds.TDSRequest.processReplyToken(TDSReq
    uest.java:1571)
    atcom.merant.datadirect.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(T
    DSLoginRequest.java:549)
    atcom.merant.datadirect.jdbc.sqlserver.tds.TDSRequest.processTokensInReply(TDS
    Request.java, Compiled Code)
    atcom.merant.datadirect.jdbc.sqlserver.tds.TDSRequest.processReply(TDSRequest.
    java:1661)
    atcom.merant.datadirect.jdbc.sqlserver.SQLServerImplConnection.open(SQLServerI
    mplConnection.java:98)
    atcom.merant.datadirect.jdbc.base.BaseConnection.getNewImplConnection(BaseConn
    ection.java:405)
    atcom.merant.datadirect.jdbc.base.BaseConnection.getImplConnection(BaseConnect
    ion.java:333)
    atcom.merant.datadirect.jdbc.base.BaseStatement.getImplConnection(BaseStatemen
    t.java:1223)
    atcom.merant.datadirect.jdbc.base.BaseStatement.getImplStatement(BaseStatement
    .java:1241)
    atcom.merant.datadirect.jdbc.base.BasePreparedStatement.<init>(BasePreparedSta
    tement.java:63)
    atcom.merant.datadirect.jdbc.base.BaseConnection.prepareStatement(BaseConnecti
    on.java:960)
    at com.merant.jdbcspy.SpyConnection.prepareStatement(UnknownSource)
    atcom.bea.ppg.rdbmsrealm.RDBMSDelegate.prepare(RDBMSDelegate.java:116)
    atcom.bea.ppg.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:187)
    atcom.bea.ppg.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java
    :912)
    at weblogic.utils.reuse.Pool.getInstance(Pool.java:57)
    atcom.bea.ppg.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:115)
    atcom.bea.ppg.rdbmsrealm.RDBMSRealm.getPermission(RDBMSRealm.java:515)
    atweblogic.security.acl.CachingRealm.getPermission(CachingRealm.java:1698)
    atweblogic.security.acl.CachingRealm.setupAcls(CachingRealm.java, Compiled
    Code)
    atweblogic.security.acl.CachingRealm.<init>(CachingRealm.java:706)
    atweblogic.security.acl.CachingRealm.<init>(CachingRealm.java:564)
    atweblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1750)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:99)
    at weblogic.Server.main(Server.java:65)
    at weblogic.Server.main(Server.java:55)
    Unable to initialize server: com.bea.ppg.rdbmsrealm.RDBMSException:realm initialization failed, Connection.prepareStatement() failed on
    statement "SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries ORDER BY
    A
    _NAME, A_PRINCIPAL", - with nested exception:
    [java.sql.SQLException: [MERANT][SQLServer JDBCDriver[SQLServer]Login failed. The maximum simultaneous user count of 5licenses for this 'Standard Edition' server has been exceeded. Additional
    licenses should be o
    btained and installed or you should upgrade to a full version.]
    fatal initialization exception
    com.bea.ppg.rdbmsrealm.RDBMSException: realm initialization failed,Connection.prepareStatement() failed on statement "SELECT A_NAME,
    A_PRINCIPAL, A_PERMISSION FROM aclentries ORDER BY A_NAME, A_PRINCIPAL", -
    with
    nested exception:
    [java.sql.SQLException: [MERANT][SQLServer JDBCDriver[SQLServer]Login failed. The maximum simultaneous user count of 5licenses for this 'Standard Edition' server has been exceeded. Additional
    licenses should be o
    btained and installed or you should upgrade to a full version.]
    atcom.bea.ppg.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:210)
    atcom.bea.ppg.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java
    :912)
    at weblogic.utils.reuse.Pool.getInstance(Pool.java:57)
    atcom.bea.ppg.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:115)
    atcom.bea.ppg.rdbmsrealm.RDBMSRealm.getPermission(RDBMSRealm.java:515)
    atweblogic.security.acl.CachingRealm.getPermission(CachingRealm.java:1698)
    atweblogic.security.acl.CachingRealm.setupAcls(CachingRealm.java, Compiled
    Code)
    atweblogic.security.acl.CachingRealm.<init>(CachingRealm.java:706)
    atweblogic.security.acl.CachingRealm.<init>(CachingRealm.java:564)
    atweblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1750)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:99)
    at weblogic.Server.main(Server.java:65)
    at weblogic.Server.main(Server.java:55)
    D:\weblogic>goto finish
    D:\weblogic>cd Ppg
    D:\weblogic\Ppg>ENDLOCAL
    D:\weblogic\Ppg>

  • ACL failure with RDBMSRealm removed user session

    When using RDBMSRealm, the user's session gets invalidated when the user do
              not have access to certain pages. When I try this behaviour without enabling
              the realm and setting the user groups and password in weblogic.properties, I
              don't have this problem. Is this a bug?
              Basically, what we need is a way so that we can differentiate a user who
              hasn't logged in and one who does not have access rights to the resource -
              without the realm, we were able to get the remoteUser to check whether there
              is a remote user and if yes, then the login page will show a "No access"
              message rather than the login form.
              I am using sp5 and form-based authentication in a web-app.
              

    When using RDBMSRealm, the user's session gets invalidated when the user do
              not have access to certain pages. When I try this behaviour without enabling
              the realm and setting the user groups and password in weblogic.properties, I
              don't have this problem. Is this a bug?
              Basically, what we need is a way so that we can differentiate a user who
              hasn't logged in and one who does not have access rights to the resource -
              without the realm, we were able to get the remoteUser to check whether there
              is a remote user and if yes, then the login page will show a "No access"
              message rather than the login form.
              I am using sp5 and form-based authentication in a web-app.
              

  • Recursion Problem with custom realms built on EJB's

    Hello there,
    We have developed a web-app which uses authentication on a derivative of
    RDBMSRealm, except that instead of RDBMSDelegate we have created our
    'EJBDelegate' to do all of our database dirtywork. Unfortunately there
    appears to be a problem that after a certain length of time some
    security check happens in the EJB layer, which calls getUser(), which
    calls the EJB layer, and I am stuck in an infinite recursive loop.
    Ideal solution - I disable security for the EJB's entirely as we view
    web-app level security as sufficient.
    Any ideas on where I might find such a setting?
    Thanks much,
    Daniel Wabyick
    Server Applications Engineer
    Fluid, Inc.
    http://www.fluid.com

    Hi Tony,
    i got the same problem as described on :
    Use of "displaytag" on WebAS 6.4
    Did you already found a solution how to deal with this displaytag-tld problem?
    hope to hear from you. thx in advance,
    lars

  • How to use connection pool with RDBMSRealm

    I am having a problem with the RDBMSRealm. The problem is that the connection defined in the .realm_properties file times out after 1 hour. My solution was to use the connection pool defined in the weblogic.properties file, but the realm_proprties are read before the connection pool is created so it did'nt work.Is there anyway of controling the order of which WLS reads various properties?If no, is there any way of setting "autorefresh" on the connection defined in the .realm_properties file?I'am using WLS 5.1, S.P 8, WIN2000 and Sybase. It works fine except for the timeout.Please help-Marius

    I've been struggling to find a way to use a weblogic connection
    pool or datasource nicely, and have failed with whatever I've tried.
    There is a chicken and egg problem here. The connection pool needs
    security to initialize itself, and security needs a connection
    pool. So that will not work.
    I've tried the follwing, which almost worked. Weblogic falls
    back to the default realm if your custom realm returns null for
    any user or group requests. So if your custom realm is not capable
    of reading info from the database, return null. The default realm
    will take over, and allow the connection pool to initialize if
    you allow everybody (or users defined in the weblogic.properties
    file) access to the pool. Then define a datasource which points
    to the pool.
    After the server starts, security can then use JNDI to look up
    the datasource, and all seems well. However, in some instances
    (it seems like calls for a bean), where security and jndi can get
    into infinite loops where jndi performs a security check when doing
    the lookup, so they both end up asking each other for information.
    So if anyone knows how to successfully use a connection pool or
    DataSource in a custom realm, I would love to know how.
    For you, I would suggest you don't try and use a connection pool,
    but figure out how to refresh your connection. You can do it manually
    by taking your connection, checking if it's valid before using
    it, if not, then open a new one.
    -d-
    Marius <[email protected]> wrote:
    I am having a problem with the RDBMSRealm. The problem
    is that the connection defined in the .realm_properties
    file times out after 1 hour. My solution was to use the
    connection pool defined in the weblogic.properties file,
    but the realm_proprties are read before the connection
    pool is created so it did'nt work.Is there anyway of
    controling the order of which WLS reads various properties?If
    no, is there any way of setting "autorefresh" on the
    connection defined in the .realm_properties file?I'am
    using WLS 5.1, S.P 8, WIN2000 and Sybase. It works fine
    except for the timeout.Please help-Marius

  • Java.lang.SecurityException while using RDBMSRealm in 5.1

    Hi,
    We are in the process of migrating our application from Weblogic 4.5.1
    to Weblogic 5.1. When we try to set up RdbmsRealm as the delegate realm
    for the server and start the server, we get the following exception:
    java.lang.SecurityException: User "system" does not have Permission
    "read" based on ACL "weblogic.workspace.system".
    at weblogic.security.acl.Security.logAndThrow(Security.java:372)
    at weblogic.security.acl.Security.checkPermission(Security.java:254)
    at
    weblogic.workspace.server.Workspace.checkPermission(Workspace.java:1169)
    at weblogic.workspace.server.Workspace.checkRead(Workspace.java:1174)
    at weblogic.workspace.server.Workspace.fetch(Workspace.java:208)
    at
    weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:243)
    at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java,
    Compiled Code)
    at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
    at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
    at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, Compiled
    Code)
    at
    weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
    The database has aclentries that grant read, write and reserve
    permissions on weblogic.workspace.system to everyone. It is not clear
    why the server still complains that user 'system' does not have
    permissions. Is 'system' user not a part of everyone group by default? (
    We are using the same acls we were using with Weblogic 4.5.1 ). Does
    'everyone' group have all the users in it by default? Or has it changed?
    Any suggestions welcome.
    Thanks and Regards
    Suresh B

    Either try setting weblogic.allow.read.weblogic.workspace=system
    Or add the system user to the group 'everyone' in the database you use for
    RDBMSRealm (Hmm, not sure if this will work or not.
    If you are implementing a custom realm then you need to explicitly state
    which members are in the 'everyone' group.
    (I've recently had a similar problem . I actually chose a different
    solution, by overriding the isMember(user) method in RDBMSGroup to always
    return true if the group's name is 'everyone' - I had to override the method
    anyway, for other reasons. If anyone as any input on why this is a really
    bad idea please feel free to tell me)
    terry
    BSuresh <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    weblogic.allow.read.weblogic.workspace=everyone
    weblogic.allow.write.weblogic.workspace=everyone
    weblogic.allow.read.weblogic.workspace.system=everyone
    weblogic.allow.write.weblogic.workspace.system=everyone
    I tried having the above entries in the weblogic.properties file but theserver
    complains that weblogic.workspace acl is defined both in the delegate andbackup
    realm. And the result remains the same - java.lang.SecurityException.User
    "system" does not have Permission "read" based on ACL
    "weblogic.workspace.system".
    Thanks
    Suresh.B
    KNK wrote:
    Try setting the "read" and "write" permissions explicitly in
    weblogic.properties file.
    weblogic.allow.read.weblogic.workspace=everyone
    weblogic.allow.write.weblogic.workspace=everyone
    -- KNK --
    A ten thousand miles journey begins with a single step. That single stephas
    to be taken from where you are, worries are no solution to any problem.
    "BSuresh" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    We are in the process of migrating our application from Weblogic 4.5.1
    to Weblogic 5.1. When we try to set up RdbmsRealm as the delegate
    realm
    for the server and start the server, we get the following exception:
    java.lang.SecurityException: User "system" does not have Permission
    "read" based on ACL "weblogic.workspace.system".
    at weblogic.security.acl.Security.logAndThrow(Security.java:372)
    at weblogic.security.acl.Security.checkPermission(Security.java:254)
    at
    weblogic.workspace.server.Workspace.checkPermission(Workspace.java:1169)
    >>>
    at weblogic.workspace.server.Workspace.checkRead(Workspace.java:1174)
    at weblogic.workspace.server.Workspace.fetch(Workspace.java:208)
    at
    weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:243
    at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java,
    Compiled Code)
    at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
    at
    weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
    at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, Compiled
    Code)
    at
    weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
    >>>
    The database has aclentries that grant read, write and reserve
    permissions on weblogic.workspace.system to everyone. It is not clear
    why the server still complains that user 'system' does not have
    permissions. Is 'system' user not a part of everyone group by default?(
    We are using the same acls we were using with Weblogic 4.5.1 ). Does
    'everyone' group have all the users in it by default? Or has itchanged?
    >>>
    Any suggestions welcome.
    Thanks and Regards
    Suresh B

  • Problems configuring Platform Domain with MS Sql Server

    Hi,
    We are having problems configuring a Platform Domain with MS Sql Server 2000.
    We are using Weblogic version 7.0.0.2. These are the steps we followed
    1.We manually created a database called TestDB and created a user account called
    "system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
    the TestDB created.
    2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
    SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
    in this file.
    3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
    and modified the RDBMS realm properties to point to the database.
    4. ran the create_db script and it seemed to have run fine looking at the log
    file.
    5. I then tried to start the BEA Server instance and I get the following error.
    I am also attaching the config.xml file for reference.
    Appreciate any help/suggestions. Thanks in Advance.
    Vikram
    <Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
    ating a database connection for the realm.
    java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
    at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
    193)
    at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
    at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
    02)
    at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
    69)
    at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
    elegate.java:962)
    at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
    at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
    at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at weblogic.security.acl.Realm.getRealm(Realm.java:87)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >
    <Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    in
    itialize the server: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    Reason: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    [config.xml]

    Try removing the server section from the SchemaProperties line.
    Preferrably do not use localhost or hostnames in the server
    configuration file.
    <RDBMSRealm
    Name="wlcsRealm"
    DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
    DatabasePassword="weblogic"
    DatabaseURL="jdbc:weblogic:mssqlserver4:yourIPAddress:1433"
    RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"
    SchemaProperties="user=system;password=weblogic"/>
    Also consider ...
    If you have a new Portal database created in SQL Server?
    Does the user system have the Portal database as his default database?
    -- Jim
    Vikram wrote:
    Hi,
    We are having problems configuring a Platform Domain with MS Sql Server 2000.
    We are using Weblogic version 7.0.0.2. These are the steps we followed
    1.We manually created a database called TestDB and created a user account called
    "system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
    the TestDB created.
    2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
    SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
    in this file.
    3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
    and modified the RDBMS realm properties to point to the database.
    4. ran the create_db script and it seemed to have run fine looking at the log
    file.
    5. I then tried to start the BEA Server instance and I get the following error.
    I am also attaching the config.xml file for reference.
    Appreciate any help/suggestions. Thanks in Advance.
    Vikram
    <Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
    ating a database connection for the realm.
    java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
    at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
    193)
    at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
    at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
    02)
    at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
    69)
    at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
    elegate.java:962)
    at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
    at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
    at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at weblogic.security.acl.Realm.getRealm(Realm.java:87)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    in
    itialize the server: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    Reason: Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
    DBMSException: An error occured creating a database connection for the realm.]
    java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
    on: An error occured creating a database connection for the realm.]
    at weblogic.security.acl.Realm.getRealm(Realm.java:94)
    at weblogic.security.acl.Realm.getRealm(Realm.java:65)
    at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
    a:353)
    at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
    itialize(AuthorizationProviderImpl.java:72)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1875)
    at weblogic.security.service.AuthorizationManager.initialize(Authorizati
    onManager.java:206)
    at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
    nager.java:127)
    at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
    eManager.java:1613)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
    rityServiceManager.java:1426)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
    rviceManager.java:1365)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
    urityServiceManager.java:1487)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1207)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <Domain Name="epmsDomain">
    <Log
    FileName="logs/wl-domain.log"
    Name="epmsDomain"
    />
    <!-- Configuration Wizard Cluster and Admin/Managed Node support -->
    <Server
    Name="platformServer"
         ListenAddress="localhost"
    ListenPort="7501"
    NativeIOEnabled="true"
    TransactionLogFilePrefix="logs/"
    >
    <SSL
    Name="platformServer"
    ListenPort="7502"
    Enabled="true"
    ServerCertificateChainFileName="ca.pem"
    ServerCertificateFileName="democert.pem"
    ServerKeyFileName="demokey.pem"
    />
    <Log
    FileName="logs/weblogic.log"
    />
    <WebServer
    DefaultWebApp="splashPage"
    LogFileName="./logs/access.log"
    LoggingEnabled="true"
    Name="platformServer"
    />
    </Server>
    <!-- WLP Pool -->
    <JDBCConnectionPool
    Name="commercePool"
    DriverName="weblogic.jdbc.mssqlserver4.Driver"
    URL="jdbc:weblogic:mssqlserver4:localhost:1433"
    Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Password="weblogic"
    InitialCapacity="20"
    MaxCapacity="20"
    CapacityIncrement="1"
    RefreshMinutes="0"
    ShrinkingEnabled="false"
    Targets="platformServer"
    TestConnectionsOnReserve="false"
    TestTableName="WEBLOGIC_IS_ALIVE"
    />
    <!-- WLI Pool -->
    <JDBCConnectionPool
    CapacityIncrement="2"
    DriverName="weblogic.jdbc.mssqlserver4.Driver"
    InitialCapacity="8"
    LoginDelaySeconds="1"
    MaxCapacity="36"
    Name="wliPool"
    Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Password="weblogic"
    RefreshMinutes="0"
    ShrinkPeriodMinutes="15"
    ShrinkingEnabled="true"
    Targets="platformServer"
    URL="jdbc:weblogic:mssqlserver4:localhost:1433"
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="false"
    JNDIName="weblogic.jdbc.jts.commercePool"
    Name="commercePool"
    PoolName="commercePool"
    Targets="platformServer"
    />
    <JDBCDataSource
    JNDIName="weblogic.jdbc.pool.commercePool"
    Name="commercePool"
    PoolName="commercePool"
    Targets="platformServer"
    />
    <JDBCDataSource
    JNDIName="WLAI_DataSource"
    Name="WLAI_DataSource"
    PoolName="wliPool"
    Targets="platformServer"
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="true"
    JNDIName="com.bea.wlpi.TXDataSource"
    Name="TXDataSource"
    PoolName="wliPool"
    Targets="platformServer"
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="true"
    JNDIName="WLCHub.DS"
    Name="WLCHub.DS"
    PoolName="wliPool"
    Targets="platformServer"/>
    />
    <!-- Configure WebLogic Workshop to run in Platform domain -->
    <JDBCTxDataSource
         EnableTwoPhaseCommit="true"
    JNDIName="cgDataSource"
    Name="cgDataSource"
    PoolName="commercePool"
    Targets="platformServer"/>
    <JDBCTxDataSource
    EnableTwoPhaseCommit="true"
    JNDIName="cgSampleDataSource"
    Name="cgSampleDataSource"
    PoolName="commercePool"
    Targets="platformServer"/>
    <JMSConnectionFactory JNDIName="weblogic.jws.jms.QueueConnectionFactory"
    Name="cgQueue" Targets="platformServer"/>
    <JMSJDBCStore ConnectionPool="commercePool" Name="cgJDBCStore" PrefixName="WEBLOGIC"/>
    <JMSServer Name="cgJMSServer" Store="cgJDBCStore" Targets="platformServer">
    <JMSQueue JNDIName="jws.queue" Name="cgJWSQueue" StoreEnabled="default"/>
    </JMSServer>
    <JTA Name="epmsDomain" TimeoutSeconds="3600"/>
    <!-- End: Configure WebLogic Workshop to run in Platform domain -->
    <!-- WLP DATASYNC -->
    <JDBCConnectionPool
    Name="dataSyncPool"
    DriverName="weblogic.jdbc.mssqlserver4.Driver"
    URL="jdbc:weblogic:mssqlserver4:localhost:1433"
    Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Password="WEBLOGIC"
    InitialCapacity="1"
    MaxCapacity="5"
    CapacityIncrement="1"
    RefreshMinutes="0"
    ShrinkingEnabled="false"
    TestConnectionsOnReserve="false"
    TestTableName="WEBLOGIC_IS_ALIVE"
    Targets="platformServer"/>
    />
    <JDBCTxDataSource
    EnableTwoPhaseCommit="false"
    JNDIName="weblogic.jdbc.jts.dataSyncPool"
    Name="dataSyncPool"
    PoolName="dataSyncPool"
    Targets="platformServer"/>
    />
    <!-- General Config -->
    <Security
    GuestDisabled="false"
    Name="epmsDomain"
    PasswordPolicy="wl_default_password_policy"
    Realm="wl_default_realm"
    CompatibilityMode="true"
    />
    <PasswordPolicy
    Name="wl_default_password_policy"
    />
    <Realm
    Name="wl_default_realm"
    CachingRealm="wlcsCachingRealm"
    FileRealm="wl_default_file_realm"
    />
    <CachingRealm
    BasicRealm="wlcsRealm"
    CacheCaseSensitive="true"
    Name="wlcsCachingRealm"
    />
    <RDBMSRealm DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
    DatabasePassword="weblogic"
    DatabaseURL="jdbc:weblogic:mssqlserver4:localhost:1433"
    SchemaProperties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
    Name="wlcsRealm"
    RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"/>
    <FileRealm
    Name="wl_default_file_realm"
    />
    <StartupClass
    ClassName="com.beasys.commerce.ebusiness.security.KeyBootstrap"
    FailureIsFatal="false"
    Name="KeyBootstrap"
    Targets="platformServer"
    />
    <!-- WLI configuraion for Platform -->
    <JMSConnectionFactory Name="WLI_B2B_TopicFactory"
    JNDIName="com.bea.wli.b2b.server.TopicConnectionFactory"
    AllowCloseInOnMessage="true"
    UserTransactionsEnabled="true"
    Targets="platformServer"
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="true"
    JNDIName="com.bea.wli.b2b.rosettanet.QueueConnectionFactory"
    Name="RNQueueFactory"
    Targets="platformServer"
    UserTransactionsEnabled="true"
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="false"
    DefaultDeliveryMode="Persistent"
    DefaultPriority="4"
    DefaultTimeToLive="0"
    JNDIName="com.bea.wlai.JMSConnectionFactory"
    MessagesMaximum="10"
    Name="WLAI_JMSConnectionFactory"
    OverrunPolicy="KeepOld"
    UserTransactionsEnabled="true"
    Targets="platformServer"/>
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="true"
    JNDIName="com.bea.wlpi.TopicConnectionFactory"
    Name="wlpiFactory"
    Targets="platformServer"
    UserTransactionsEnabled="true"
    />
    <JMSConnectionFactory
    AllowCloseInOnMessage="true"
    JNDIName="com.bea.wlpi.QueueConnectionFactory"
    Name="wlpiQueueFactory"
    Targets="platformServer"
    UserTransactionsEnabled="true"
    />
    <JMSJDBCStore
    ConnectionPool="wliPool"
    Name="JMSWLIStore"
    PrefixName="PBPUBLIC"
    />
    <JMSServer Name="WLIJMSServer"
    Targets="platformServer"
    TemporaryTemplate="TemporaryTemplate"
    Store="JMSWLIStore">
    <JMSTemplate Name="TemporaryTemplate"/>
    <!-- B2B -->
    <JMSQueue Name="WLI_B2B_RNEncoderQueue"
    JNDIName="com.bea.wli.b2b.rosettanet.EncoderQueue"/>
    <JMSTopic Name="WLI_B2B_Topic"
    JNDIName="com.bea.wli.b2b.server.B2BTopic"/>
    <JMSQueue Name="WLI_B2B_OutboundQueue"
    JNDIName="com.bea.b2b.OutboundQueue"/>
    <!-- BPM -->
    <JMSTopic Name="wlpiEvent"
    JNDIName="com.bea.wlpi.EventTopic"/>
    <JMSQueue Name="WLI_BPM_Timer"
    JNDIName="com.bea.wli.bpm.TimerQueue"
    StoreEnabled="true"
    Template="WLI_JMSTemplate"/>
    <JMSQueue Name="WLI_BPM_Event"
    JNDIName="com.bea.wli.bpm.EventQueue"
    StoreEnabled="true"
    Template="WLI_JMSTemplate"/>
    <JMSQueue Name="WLI_BPM_ValidatingEvent"
    JNDIName="com.bea.wli.bpm.ValidatingEventQueue"
    StoreEnabled="true"
    Template="WLI_JMSTemplate"/>
    <JMSTopic Name="WLI_BPM_Error"
    JNDIName="com.bea.wli.bpm.ErrorTopic"/>
    <JMSTopic Name="WLI_BPM_Audit"
    JNDIName="com.bea.wli.bpm.AuditTopic"/>
    <JMSTopic Name="WLI_BPM_Notify"
    JNDIName="com.bea.wli.bpm.NotifyTopic"/>
    <!-- AI -->
    <JMSQueue Name="WLAI_ASYNC_REQUEST_QUEUE"
    JNDIName="com.bea.wlai.ASYNC_REQUEST_QUEUE"/>
    <JMSQueue Name="WLAI_ASYNC_RESPONSE_QUEUE"
    JNDIName="com.bea.wlai.ASYNC_RESPONSE_QUEUE"/>
    <JMSQueue Name="WLAI_EVENT_QUEUE"
    JNDIName="com.bea.wlai.EVENT_QUEUE"/>
    <JMSTopic Name="WLAI_EVENT_TOPIC"
    JNDIName="com.bea.wlai.EVENT_TOPIC"/>
         <!-- App View control -->
         <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_ASYNC_RESPONSE_QUEUE" Name="WLAI_WORKSHOP_ASYNC_RESPONSE_QUEUE"/>
         <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_EVENT_QUEUE" Name="WLAI_WORKSHOP_EVENT_QUEUE"/>
    <!-- WLI -->
    <JMSQueue Name="WLI_FailedEvent"
    JNDIName="com.bea.wli.FailedEventQueue"
    StoreEnabled="true"/>
    <JMSTemplate Name="WLI_JMSTemplate"
    ErrorDestination="WLI_FailedEvent"
    RedeliveryDelayOverride="60000"
    RedeliveryLimit="10"/>
    </JMSServer>
    <JMSJDBCStore Name="JMSWLIStore"
    ConnectionPool="wliPool"
    PrefixName="platformServer"/>
    <!-- Distributed queue/topic configuration for WLI components -->
    <!-- End WLI configuraion for Platform -->
    <!--===========================================================================-->
    <!-- Configure the J2EE enterprise applications supporting the Platform -->
    <!--===========================================================================-->
    <!-- The enterprise application containing the WLS-based Tax and Payment WebService -->
    <Application
    Deployed="true"
    Name="taxWSApp"
    Path="C:/bea/user_projects/epmsDomain/beaApps/taxWSApp"
    TwoPhase="true"
    >
    <EJBComponent
    Name="tax"
    URI="tax.jar"
    Targets="platformServer"
    />
    <WebAppComponent
    Name="tax-webservice"
    URI="tax-ws"
    Targets="platformServer"
    />
    </Application>
    <Application
    Deployed="true"
    Name="paymentWSApp"
    Path="C:/bea/user_projects/epmsDomain/beaApps/paymentWSApp"
    TwoPhase="true"
    >
    <EJBComponent
    Name="payment"
    URI="payment.jar"
    Targets="platformServer"
    />
    <WebAppComponent
    Name="payment-edit webservice"
    URI="pay-ws"
    Targets="platformServer"
    />
    </Application>
    <!-- The enterprise application containing the installed/online links documentation -->
    <Application
    Deployed="true"
    Name="wlpDocsApp"
    Notes=""
    Path="C:/bea/weblogic700/portal/lib"
    TwoPhase="true"
    >
    <WebAppComponent
    IndexDirectoryEnabled="false"
    Name="wlpDocs"
    Targets="platformServer"
    URI="wlpDocs.war"
    ServletReloadCheckSecs="300"
    />
    </Application>
    <!-- The enterprise application containing the WLP components -->
    <Application
    Deployed="true"
    Name="portalApp"
    Notes=""
    Path="C:/bea/user_projects/epmsDomain/beaApps/portalApp"
    TwoPhase="true"
    >
    <ApplicationConfiguration
    Name="portalApp"
    Targets="platformServer"
    URI="META-INF/application-config.xml"
    />
    <EJBComponent
    Name="events"
    Targets="platformServer"
    URI="events.jar"
    />
    <EJBComponent
    Name="pipeline"
    Targets="platformServer"
    URI="pipeline.jar"
    />
    <EJBComponent
    Name="property"
    Targets="platformServer"
    URI="property.jar"
    />
    <EJBComponent
    Name="rules"
    Targets="platformServer"
    URI="rules.jar"
    />
    <EJBComponent
    Name="usermgmt"
    Targets="platformServer"
    URI="usermgmt.jar"
    />
    <EJBComponent
    Name="customer"
    Targets="platformServer"
    URI="customer.jar"
    />
    <EJBComponent
    Name="ebusiness"
    Targets="platformServer"
    URI="ebusiness.jar"
    />
    <EJBComponent
    Name="portal"
    Targets="platformServer"
    URI="portal.jar"
    />
    <EJBComponent
    Name="campaign"
    Targets="platformServer"
    URI="campaign.jar"
    />
    <EJBComponent
    Name="catalogws"
    Targets="platformServer"
    URI="catalogws.jar"
    />
    <EJBComponent
    Name="document"
    Targets="platformServer"
    URI="document.jar"
    />
    <EJBComponent
    Name="ejbadvisor"
    Targets="platformServer"
    URI="ejbadvisor.jar"
    />
    <EJBComponent
    Name="mail"
    Targets="platformServer"
    URI="mail.jar"
    />
    <EJBComponent
    Name="placeholder"
    Targets="platformServer"
    URI="placeholder.jar"
    />
    <WebAppComponent
    Name="toolSupport"
    Targets="platformServer"
    URI="toolSupport"
    ServletReloadCheckSecs="300"
    />
    <WebAppComponent
    Name="tools"
    Targets="platformServer"
    URI="tools"
    ServletReloadCheckSecs="300"
    />
    <WebAppComponent
    Name="datasync"
    Targets="platformServer"
    URI="datasync"
    ServletReloadCheckSecs="300"
    />
    <WebAppComponent
    Name="splashPage"
    Targets="platformServer"
    URI="splashPage"
    ServletReloadCheckSecs="300"
    />
    <!-- The enterprise application containing the WLP P13N Console components -->
    </Application>
    <Application
    Deployed="true"
    TwoPhase="true"
    StagedTargets="platformServer"
    Name="p13nConsoleApp"
    Path="C:/bea/weblogic700/portal/lib"
    >
    <WebAppComponent
    Name="p13nConsole"
    ServletReloadCheckSecs="300"
    Targets="platformServer"
    URI="p13nConsole.war"
    />
    </Application>
    <!-- The enterprise application containing the WLI components -->
    <Application Deployed="true" LoadOrder="900" Name="EAI" Path="C:/bea/weblogic700/samples/workshop/wlai/ear/" TwoPhase="true">
    <EJBComponent
    DeploymentOrder="100"
    Name="repository-ejb.jar"
         Targets="platformServer"
    URI="repository-ejb.jar"/>
    <EJBComponent Name="WLI-B2B Startup"
    DeploymentOrder="200"
    Targets="platformServer"
    URI="b2b-startup.jar"/>
    <EJBComponent DeploymentOrder="300" Name="b2b-rosettanet.jar" Targets="platformServer" URI="b2b-rosettanet.jar"/>
    <WebAppComponent DeploymentOrder="400" Name="b2b.war" Targets="platformServer" URI="b2b.war"/>
    <WebAppComponent DeploymentOrder="500" Name="b2bconsole.war" Targets="platformServer" URI="b2bconsole.war"/>
    <EJBComponent DeploymentOrder="600" Name="WLI-AI Server" Targets="platformServer" URI="wlai-server-ejb.jar"/>
    <WebAppComponent DeploymentOrder="700" Name="wlai" Targets="platformServer" URI="wlai.war"/>
    <EJBComponent DeploymentOrder="800" Name="WLI-AI Async Processor" Targets="platformServer" URI="wlai-asyncprocessor-ejb.jar"/>
    <EJBComponent DeploymentOrder="900" Name="WLI-AI Event Processor" Targets="platformServer" URI="wlai-eventprocessor-ejb.jar"/>
    <EJBComponent DeploymentOrder="1000" Name="wlpi-ejb.jar" Targets="platformServer" URI="wlpi-ejb.jar"/>
    <EJBComponent DeploymentOrder="1100" Name="wlpi-master-ejb.jar" Targets="platformServer" URI="wlpi-master-ejb.jar"/>
    <EJBComponent DeploymentOrder="1200" Name="wlpi-mdb-ejb.jar" Targets="platformServer" URI="wlpi-mdb-ejb.jar"/>
    <EJBComponent DeploymentOrder="1300" Name="WLXTEJB.jar" Targets="platformServer" URI="WLXTEJB.jar"/>

  • AclOwner not owner error when implementing RDBMSRealm

    I am implementing a RDMBSRealm on WL6.1sp1. When I add an ACL/permission and
    grant it to a group, I got an error.
    I tried the example RDBMSRealm. I found out that adding groups and acls are
    actually persisted into the fileRealm,
    Only adding users are persisted to the database. What did I miss? Any
    suggestions will be appreciated.
    java.lang.InternalError: aclOwner not owner
         at
    weblogic.security.acl.internal.FileRealm.setPermission(FileRealm.java:871)
         at weblogic.security.acl.CachingRealm.setPermission(CachingRealm.java:1985)
         at
    weblogic.management.internal.RemoteRealmManagerImpl.grantPermission(RemoteRe
    almManagerImpl.java:270)
         at weblogic.management.configuration.Acl.grantPermission(Acl.java:72)
         at
    weblogic.management.console.actions.realm.DoAclPermissionFormAction.perform(
    DoAclPermissionFormAction.java:120)
         at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
    rvlet.java:167)
         at
    weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
    let.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
         at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2456)
         at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2039)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.management.configuration.RealmException: Acl.grantPermission - with
    nested exception:
    [java.lang.InternalError: aclOwner not owner]
         at weblogic.management.configuration.Acl.grantPermission(Acl.java:74)
         at
    weblogic.management.console.actions.realm.DoAclPermissionFormAction.perform(
    DoAclPermissionFormAction.java:120)
         at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
    rvlet.java:167)
         at
    weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
    let.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
         at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2456)
         at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2039)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Console Release Build6.1.1.0Server Release Build6.1.1.0Server BuildWebLogic
    Server 6.1 SP1 09/18/2001 14:28:44 #138716 All Server Product
    VersionsWebLogic Server 6.1 SP1 09/18/2001 14:28:44 #138716 WebLogic XML
    Module 6.1 SP1 09/18/2001 14:43:02 #138716

    Hey,
    Are you guys trying to add functionality to the RDBMSRealm so that you can edit
    ACLs in the database, using the WebLogic Console management tools? In other
    words, is your final goal to be able to create (or remove) an ACL in your
    console, and have the changes persisted to the database? I don't quite
    understand what the problem is, based on the description. If you could
    elaborate it would help me to understand what's going on.
    Thanks
    Joe Jerry
    K Wong wrote:
    I tried "unperson". Same error. Do I need to create this user "unperson" in
    my db users table and put it "Administration" group?
    The problem seems to be raised from weblogic...setPermission. I wish I could
    debug into this code or at least System.out.println some contents.
    "Marek Sz." <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    in oryginal example aclOwner is defined in RDBMSDelegate :
    * This is the bogus owner associated with all ACLs found in the
    * database.
    protected Principal aclOwner = new User("unperson");
    Ty to use this Principal.
    Regards
    Marek Sz.
    K Wong wrote:
    I am implementing a RDMBSRealm on WL6.1sp1. When I add an ACL/permission
    and
    grant it to a group, I got an error.
    I tried the example RDBMSRealm. I found out that adding groups and aclsare
    actually persisted into the fileRealm,
    Only adding users are persisted to the database. What did I miss? Any
    suggestions will be appreciated.
    java.lang.InternalError: aclOwner not owner
    at
    weblogic.security.acl.internal.FileRealm.setPermission(FileRealm.java:871)
    atweblogic.security.acl.CachingRealm.setPermission(CachingRealm.java:1985)
    at
    weblogic.management.internal.RemoteRealmManagerImpl.grantPermission(RemoteRe
    almManagerImpl.java:270)
    atweblogic.management.configuration.Acl.grantPermission(Acl.java:72)
    at
    weblogic.management.console.actions.realm.DoAclPermissionFormAction.perform(
    DoAclPermissionFormAction.java:120)
    at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
    rvlet.java:167)
    at
    weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
    let.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2456)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2039)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.management.configuration.RealmException: Acl.grantPermission -with
    nested exception:
    [java.lang.InternalError: aclOwner not owner]
    atweblogic.management.configuration.Acl.grantPermission(Acl.java:74)
    at
    weblogic.management.console.actions.realm.DoAclPermissionFormAction.perform(
    DoAclPermissionFormAction.java:120)
    at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
    rvlet.java:167)
    at
    weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
    let.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2456)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2039)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Console Release Build6.1.1.0Server Release Build6.1.1.0ServerBuildWebLogic
    Server 6.1 SP1 09/18/2001 14:28:44 #138716 All Server Product
    VersionsWebLogic Server 6.1 SP1 09/18/2001 14:28:44 #138716 WebLogicXML
    Module 6.1 SP1 09/18/2001 14:43:02 #138716

  • Problems in starting up Connection Pools in SQLServer7

    Hi
    We are running both Commerce and Personlaization Server 3.5 with an SQL erver
    7 backend. I recently migrated the database from Cloudscape to SQL Server and
    added the following entry into my weblogicCommerce.properties file
    <I>
    # ---------------SQL Server ----------------------#
    commerce.usermgmt.RDBMSRealm.driver=weblogic.jdbc.mssqlserver4.Driver
    commerce.usermgmt.RDBMSRealm.dbUrl=jdbc:weblogic:mssqlserver4:wlcsDatabase@WEBLOGICSRVR01:1433
    commerce.usermgmt.RDBMSRealm.dbUser=sa
    commerce.usermgmt.RDBMSRealm.dbPassword=mcpassword
    </I>
    After doing this, the commercePool (Connection Pool) that comes with the installation
    of the Commerce server did not work and came up with some java exceptions i.e.
    <I>
    Could not create pool connection. The DBMS driver exception was:
    java.sql.SQLException: Can't open a socket on none:1433. Check host and port num
    ber and make sure the security manager allows this connection. You can also try
    running the SocketApplet (java.net.UnknownHostException: none).
    at weblogic.jdbcbase.mssqlserver4.BaseConnection.prepareConnection(BaseC
    onnection.java:176)
    at weblogic.jdbc.mssqlserver4.Driver.newConnection(Driver.java:32)</I>
    Can any one give me an idea on what I need to do to resolve this problem?
    Thanx

    hii..did u change the startup and bea/wlcs/bin/win32/set-environment.cmd
    files where u need to change the classpath related with SQL Server.After
    that you will have to change JDBC setting thru console using
    http://ip:7501/console/index.jsp
    Do that and hope it will work.
    Rajesh
    "Bola Taylor" <[email protected]> wrote in message
    news:3b724a71$[email protected]..
    >
    Hi
    We are running both Commerce and Personlaization Server 3.5 with an SQLerver
    7 backend. I recently migrated the database from Cloudscape to SQL Serverand
    added the following entry into my weblogicCommerce.properties file
    <I>
    # ---------------SQL Server ----------------------#
    commerce.usermgmt.RDBMSRealm.driver=weblogic.jdbc.mssqlserver4.Driver
    commerce.usermgmt.RDBMSRealm.dbUrl=jdbc:weblogic:mssqlserver4:wlcsDatabase@W
    EBLOGICSRVR01:1433
    commerce.usermgmt.RDBMSRealm.dbUser=sa
    commerce.usermgmt.RDBMSRealm.dbPassword=mcpassword
    </I>
    After doing this, the commercePool (Connection Pool) that comes with theinstallation
    of the Commerce server did not work and came up with some java exceptionsi.e.
    >
    <I>
    Could not create pool connection. The DBMS driver exception was:
    java.sql.SQLException: Can't open a socket on none:1433. Check host andport num
    ber and make sure the security manager allows this connection. You canalso try
    running the SocketApplet (java.net.UnknownHostException: none).
    atweblogic.jdbcbase.mssqlserver4.BaseConnection.prepareConnection(BaseC
    onnection.java:176)
    atweblogic.jdbc.mssqlserver4.Driver.newConnection(Driver.java:32)</I>
    >
    >
    Can any one give me an idea on what I need to do to resolve this problem?
    Thanx

  • Using RDBMSRealm as backup realm and filerealm as primary realm

    I want to use filerealm as primary realm and RDBMSRealm as backup realm in
    my custom realm. How can I do that?
    Or how can I get access to filerealm from RDBMSRealm so that I can call
    filerealm.getUser() before I try to get it from database.
    Thank you.
    Tero Järvinen.

    What I've done does set the RDBMSRealm as the default realm.
    What had me worried and doubting this was that if there is an authentication
    problem, the console still says that there was a problem in "realm
    weblogic" -- a little misleading.
    "fnord" <[email protected]> wrote in message
    news:[email protected]..
    >
    I could have sworn that setting the RealmClass in weblogic.properties set
    the default realm for the server (or for the cluster in the
    weblogic.properties in mycluster), as this seemed to be how it worked with
    our test cases....
    Now that I've set up a webapp on its own and am trying to test our beansin
    it, it appears that the beans/webapp are trying to use the weblogic realm.
    Here's the error:
    principal: 1234
    javax.naming.AuthenticationException. Root exception is
    java.lang.SecurityException:
    Authentication for user 1234 denied in realm weblogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:183)
    Here's what I have in weblogic.properties:
    weblogic.security.realmClass=examples.security.rdbmsrealm.RDBMSRealm
    Should this set the RDBMSRealm as the default realm, or do I have to domore
    to set the RDBMSRealm as the default for the webapp?
    thanks,
    John Stotler

Maybe you are looking for

  • Podcast episodes not showing up in iTS

    We have recently changed our URL. We were able to successfully publish episode 4 with the redirect but for some reason episode 5 never showed up. episode6 is now up and we need these to show up in the store. FEED URL: http://www.texastribune.org/feed

  • Has Photoshop CS5 Extended added a "Behind" and "Clear" in MODE drop down box?

    Hi Guys, I am not sure what just happened with my PS. Was downloading and installing some custom patterns and brushes from the net last night. And when I went to try them out I noticed the drop down box had 2 new added effects ( Behind and Clear ) wh

  • Vector charts in PDF?

    I would like to have vector charts in my PDF, so that their quality doesn't change when zoomed. How do I create such charts?

  • I think my phone is stolen

    hello, i bough a blackberry 8520 , from a guy, he didnt said from where he got it ... but i think it is stolen, i cant use the aplications (blackberry app world) ... i am from romania , with orange carrier ... i have the blackberry option activated (

  • Import RAW files only

    I have a Nikon D60, and took all of my pictures from last week's vacation using the RAW+Basic option. Is there a way to import just the RAW files so I don't have to go through and delete all of the JPEG duplicates?