Weblogic.security.cache.debug property for wls 6.1

Hi,
how can I set the weblogic.security.cache.debug property that worked with wls
5.1. with the new 6.1 version ?
Thanks a milion!

With database concurrency, there is one instance per primary key per
transaction.
So if tx-1 calls pk 'Rob' and tx-2 calls pk 'Rob', they'll each have their own
instance.
-- Rob
levi wrote:
From weblogic ejb spec, it is said that for WLS 6.1 the default locking
services is Database locking now. The container will defer locking services
to the underlying database.
My question is in WLS6.1, for a single row of data record stored in the
underlying database, how many entity beans for this specific record in a
single WebLogic container can have? I know that in WLS5.1, there's only 1
entity bean instance for a specific record.
If in WLS6.1 there's still only 1 entity bean instance for a data record,
how does the container deal with the case in which multiple clients try to
update this entity bean concurrently (and at this time the container use
database locking service)?
Thanks,
Levi

Similar Messages

  • Weblogic.security.X509 alternative in WLS 9.1

    Hi All
    We have setup IIS 5.0 with 2 way SSL for client connection. We have also configured IIS weblogic proxy for Weblogic 9.1 using iisproxy.dll. The connection between IIS and WebLogic 9.1 is HTTP based. We are trying to get the client certificate in Weblogic 9.1 using the following code
    java.security.cert.X509Certificate certs [];
    certs = (java.security.cert.X509Certificate [])
    request.getAttribute("javax.servlet.request.X509Certificate");
    However the returned certificates are NULL.
    We have also enabled Client Cert Proxy and Weblogic Plug-in in Weblogic 9.1 configuration.
    We are trying to migrate from weblogic 8 to 9.1 and our previous code was as follows
    weblogic.security.X509 [] certs = (weblogic.security.X509[])req.getAttribute("javax.net.ssl.peer_certificates");
    This code work fine with the same IIS setup. Since weblogic.security.X509 is removed in WLS 9.1 we are forced to change our code.
    Please help!
    Message was edited by:
    rmkandan

    hi
    Currently I am using
    req.getHeader("WL-Proxy-Client-Cert")
    to get the client certificate and then i do the following to get the X509 cert format
         if (pemCert != null && pemCert.length() > 0 ){
              pemCertBuff.append("-----BEGIN CERTIFICATE-----");
              pemCertBuff.append(pemCert);
              pemCertBuff.append("-----END CERTIFICATE-----");
         System.out.println("CertificateUtil:getFingerPrint: pemCertBuff --"+pemCertBuff.toString());
         X509Certificate certs = null;
         try {
              CertificateFactory cf = CertificateFactory.getInstance("X.509");
              ByteArrayInputStream bis = new ByteArrayInputStream(pemCertBuff.toString().getBytes());
              weblogic.security.PEMInputStream pemIs = new weblogic.security.PEMInputStream(bis);
              BufferedInputStream bufis = new BufferedInputStream(pemIs);
              certs = (X509Certificate)cf.generateCertificate(bufis);
         } catch (CertificateException e) {
              // TODO Auto-generated catch block
              e.printStackTrace();
         } catch (IOException e) {
              // TODO Auto-generated catch block
              e.printStackTrace();
    And I am able to get the certificate, but I need to know is there any other elegant way to get the certificate as we did using weblogic.security.X509 class?
    Please help!!
    Message was edited by:
    rmkandan

  • Weblogic Security Propagation

    Hi,
    I am trying to propagate Custom principal from thick client to WLS server 8.1 sp3. I use Authenticate.authenticate() at client side login module (jar at client side is weblogi.jar; i have my own Authentication provider at the server domain) and everything works fine. But once the user does a logout and re-login (application does not exit) the old security attribute inside the subject get propagated again not the new one.
    I don't have access to main thread which means Security.runAs is not vaiable for me.
    options i tired :
    1) subject.getPrincipals().clear; subject = null;
    2) weblogic.security.authenticatePushSubject system property, in which case, first call after login propagated the correct Subject amd from the next call onwards it went back to the old Subject.
    3) Authenticate.logout() in the logout of my LoginModule
    nothing works.
    is there any other way to ensure that old Subject is removed and new subject is pushed to the stack.
    Any known solution to this?
    thanks in advance
    Raj

    solved it.
    used SwingUtils.invokelater() at client side to make sure that login happens in event queue +
    weblogic.security.authenticatePushSubject to true +
    clearing all contexts and principals at logout
    made sure that new subject is available for further calls.
    only worry is , when bea is going to deprecate the weblogic.security.authenticatePushSubject property....
    sorry for disturbing busy minds
    thanks
    Raj

  • Weblogic.security.X509 API

    Hello All,
    Is the API documentation for the weblogic.security.X509 class, or for
    that matter the entire package, documented somewhere?
    Thanks,
    Dan
    [dan.vcf]

    Hello All,
    I would like a client java program to communicate with a WLS over a t3s
    connection with two-way SSL.
    We have generated certificates for browsers that work fine for the two-way SSL.
    I have access to the base 64 encoded certificate that the java client program
    can use. I am assuming I need a private key also for use in the
    setSSLClientCertificate(InputStream[] chain) method for decryption of data
    coming to to the client. For a WLS server, this is no problem.
    Question(s): Am I correct in this private key assumption? If I do need the
    private key, how could I get it.
    Thanks
    [dan.vcf]

  • How to use weblogic.Admin to set JMS ErrorDestination property on WLS 7?

    This thread is talking about using weblogic.Admin to set the ErrorDestination property.
              http://forums.bea.com/bea/thread.jspa?threadID=200036378&messageID=202187327&start=0
              We run the script against the WLS 7.0 server, script get 'OK' result but it didn't work (property wasn't set). Some error is reported in the admin.log on the server.
              We also run the scipt against the WLS 8 server. It worked perfectly.
              Does anyone know whether this works at all on WLS 7?

    The reason we are using weblogic.Admin is that we are using conf2admin to generate the scripts. weblogic.Admin seems to be the only option for WLS7. Thanks for your suggestion and will definitely check out WLST.
              The full error message is:
              ####<Aug 27, 2004 8:55:20 AM NZST> <Emergency> <Management> <rbd1> <admin> <ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <141067> <The value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue specified for the ErrorDestination attribute is not valid. MBean: n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue. Method: setAttributes. Exception: javax.management.InvalidAttributeValueException: BeanShell Interpreter threw exception while evaluating (((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value)))) on value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue, getLegalCheck() for attribute ErrorDestination of MBean "n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue", Sourced file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : Method Invocation weblogic.management.configuration.JMSLegalHelper.legalErrorDestination : at Line: 1 : in file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : weblogic .management .configuration .JMSLegalHelper .legalErrorDestination ( self , value )
              Target exception: java.lang.NullPointerException
              .>
              javax.management.InvalidAttributeValueException: BeanShell Interpreter threw exception while evaluating (((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value)))) on value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue, getLegalCheck() for attribute ErrorDestination of MBean "n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue", Sourced file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : Method Invocation weblogic.management.configuration.JMSLegalHelper.legalErrorDestination : at Line: 1 : in file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : weblogic .management .configuration .JMSLegalHelper .legalErrorDestination ( self , value )
              Target exception: java.lang.NullPointerException
                   at weblogic.management.internal.DynamicMBeanImpl.checkAttributeValueIsLegal(DynamicMBeanImpl.java:1517)
                   at weblogic.management.internal.DynamicMBeanImpl.prepareForModification(DynamicMBeanImpl.java:1440)
                   at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1004)
                   at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:353)
                   at weblogic.management.internal.DynamicMBeanImpl.setAttributes(DynamicMBeanImpl.java:827)
                   at com.sun.management.jmx.MBeanServerImpl.setAttributes(MBeanServerImpl.java:1475)
                   at weblogic.management.internal.RemoteMBeanServerImpl.setAttributes(RemoteMBeanServerImpl.java:905)
                   at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
                   at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
                   at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
                   at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
                   at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
                   at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

  • Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user  denied

    Hi,
    when I want to start managed server :
    <Sep 5, 2014 4:56:12 PM GST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user  denied
    weblogic.security.SecurityInitializationException: Authentication for user  denied
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
            at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
            at weblogic.security.SecurityService.start(SecurityService.java:141)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            Truncated. see log file for complete stacktrace
    Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User  javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
            at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
            at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            Truncated. see log file for complete stacktrace
    >
    <Sep 5, 2014 4:56:12 PM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Sep 5, 2014 4:56:12 PM GST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Sep 5, 2014 4:56:12 PM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Thanks

    Never mind, the correct command is:
    wls:/nm/IDMDomain> pr=makePropertiesObject("username=weblogic;password=weblogic0");
    wls:/nm/IDMDomain> nmStart('AdminServer',props=pr);
    It would be interesting however to have a list of all names of environmental variables that we can possibly set.
    Cheers.

  • Debug-Mode for Security Realm

    Hi,
    then i try start the server with the debug mode i get the following
    exception:
    Starting WebLogic Server ....
    <Tue Oct 24 17:45:33 GMT+02:00 2000> <Info> <Management> <Loading
    configuration file .\config\virtHoDomain\config.xml...>
    Unable to dump log: Fatal initialization exception
    Throwable: java.lang.StackOverflowError
    java.lang.StackOverflowError
    at java.util.Collections$SynchronizedMap.get(Collections.java:1433)
    at
    weblogic.kernel.ResettableThreadLocal.currentStorage(ResettableThreadLocal.j
    ava:100)
    at
    weblogic.kernel.ResettableThreadLocal.get(ResettableThreadLocal.java:35)
    at
    weblogic.transaction.internal.TransactionManagerImpl.getOrCreateThreadProp(T
    ransactionManagerImpl.java:844)
    at
    weblogic.transaction.internal.TransactionManagerImpl.getTransaction(Transact
    ionManagerImpl.java:359)
    at weblogic.transaction.TxHelper.getTransaction(TxHelper.java:34)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:156)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:145)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:138)
    at weblogic.logging.LogManager.log(LogManager.java:93)
    at weblogic.logging.LogOutputStream.debug(LogOutputStream.java:80)
    at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:775)
    at weblogic.security.acl.Security.getCurrentUser(Security.java:238)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:161)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:145)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:138)
    at weblogic.logging.LogManager.log(LogManager.java:93)
    at weblogic.logging.LogOutputStream.debug(LogOutputStream.java:80)
    at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:775)
    at weblogic.security.acl.Security.getCurrentUser(Security.java:238)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:161)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:145)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:138)
    at weblogic.logging.LogManager.log(LogManager.java:93)
    I even get that exeception if try to initialize the
    weblogic.logging.LogManager in a commun class.
    I think this is a bug.

    Hi Lars Klippert
    Sorry for the late reply. First of all, thank you for uncovering an untested part of ServerDebug MBean. The Debug Mode for Security Realms currently works for fileRealm but doesnot work for alternate realms(e.g., LDAP realm). We're in the process of fixing this in the future releases(may not be Beta Refresh but will definitely be fixed in GA). I'm attaching a working config.xml(with fileRealm) and the only change you've to make to your config.xml is
    <Server
    <ServerDebug
    DebugSecurityRealm="true"
    Name="myserver"
    />
    </Server>
    If you're debugging a fileRealm then I belive, this serves your purpose. But if you're debugging a Security Realm other than fileRealm and this is blocking you, plz let us know so that this will be fixed with a higer priority. Thanks again for uncovering this. We will let you know as soon as this is fixed.
    regards
    "Lars Klippert" <[email protected]> wrote:
    Hi,
    Part from config.xml:
    <Server ...>
    <ServerDebug Name="virtHoServer" DebugSecurityRealm="false"/>
    </Server>
    Part from my start-script:
    %JAVA_HOME%\bin\java.exe -ms16m -mx64m -classpath
    %CLASSPATH% -Dweblogic.Domain=virtHoDomain -Dweblogic.Name=virtHoServer -Dja
    va.security.policy==.\lib\weblogic.policy weblogic.Server
    As you can see i enable the debug-mode in the config.xml.
    I also get the exception then i disable the debug-modus and
    initialize the weblogic.logging.LogOutputStream by hand.
    For our EntityBeans we have developed a custom error logger
    that uses the weblogic.logging.LogOutputStream and it works
    fine. Maybe the error only acccours if two or more
    weblogic.logging.LogOutputStreams are active...
    With the 5.1.0 version of the server everything works fine.
    Thanks
    "Paul Ferwerda" <[email protected]> schrieb im Newsbeitrag
    news:[email protected]...
    How exactly are you starting "the server with debug mode"?
    Thanks,
    Paul
    Lars Klippert wrote:
    Hi,
    then i try start the server with the debug mode i get the following
    exception:
    Starting WebLogic Server ....
    <Tue Oct 24 17:45:33 GMT+02:00 2000> <Info> <Management> <Loading
    configuration file .\config\virtHoDomain\config.xml...>
    Unable to dump log: Fatal initialization exception
    Throwable: java.lang.StackOverflowError
    java.lang.StackOverflowError
    at
    java.util.Collections$SynchronizedMap.get(Collections.java:1433)
    at
    weblogic.kernel.ResettableThreadLocal.currentStorage(ResettableThreadLocal.j
    ava:100)
    at
    weblogic.kernel.ResettableThreadLocal.get(ResettableThreadLocal.java:35)
    at
    weblogic.transaction.internal.TransactionManagerImpl.getOrCreateThreadProp(T
    ransactionManagerImpl.java:844)
    at
    weblogic.transaction.internal.TransactionManagerImpl.getTransaction(Transact
    ionManagerImpl.java:359)
    atweblogic.transaction.TxHelper.getTransaction(TxHelper.java:34)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:156)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:145)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:138)
    at weblogic.logging.LogManager.log(LogManager.java:93)
    atweblogic.logging.LogOutputStream.debug(LogOutputStream.java:80)
    atweblogic.security.acl.CachingRealm.getUser(CachingRealm.java:775)
    atweblogic.security.acl.Security.getCurrentUser(Security.java:238)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:161)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:145)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:138)
    at weblogic.logging.LogManager.log(LogManager.java:93)
    atweblogic.logging.LogOutputStream.debug(LogOutputStream.java:80)
    atweblogic.security.acl.CachingRealm.getUser(CachingRealm.java:775)
    atweblogic.security.acl.Security.getCurrentUser(Security.java:238)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:161)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:145)
    at
    weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:138)
    at weblogic.logging.LogManager.log(LogManager.java:93)
    I even get that exeception if try to initialize the
    weblogic.logging.LogManager in a commun class.
    I think this is a bug.

  • OWSM security for a OSB service- authenticate from weblogic security realms

    Hello,
    I have a requirement to add security to a OSB service.
    The user details are configured in weblogic security realms. lets say there are ten different users.
    I need to protect my osb service using OWSM policy & the policy should be configured to authenticate the user from realms.
    I am new to OWSM & wondering if this is possible?
    Can the experts please direct me to any docs or steps?
    Thanks
    Ganesh

    Hi,
    Thanks for the links.
    I followed the blog and configured it using oracle/wss_username_token_service_policy.
    Now my requirement is to send the username,password from proxy to business and to the BPEL. (the bpel needs this username /password & and in header)
    The issue I am facing is the proxy service is not sending the soap header details to business service.
    I dont want to make the proxy as passthrough. (ie set Process WS-Security Header to NO)
    I have to authorize on proxy level and then send the same credential details to business service?
    So the question is, how can I retrieve the header after osb process it?
    Can anyone please help me here?
    Thanks
    Ganesh

  • Weblogic.security.SecurityInitializationException: Authentication for user

    Folks,
    I've newly installed Weblogic server on my home laptop.
    I can't startup the weblogic server.
    Errors are
    Now, I know the location of the boot.properties file the server accesses, because if I delete and restart the server it asks for userid/password.
    If that file does not exists it gives the following error
    weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    So, I thought the best way is to RECOVER the password and tried following the steps
    1. At the command line, change directory to the domain and run the setEnv script to set the PATH and CLASSPATH.
    2. cd <domain_home>/security
    3. mv DefaultAuthenticatorInit.ldift DefaultAuthenticatorInit.ldift_BKP
    4. run java weblogic.security.utils.AdminAccount <tempadmin> <temppassword> ./
    -above command will Create a new DefaultAuthenticatorInit.ldift
    4. cd <domain_home>/servers/<AdminServer>/data/ldap
    5. mv DefaultAuthenticatormyrealmInit.initialized DefaultAuthenticatormyrealmInit.initialized_BKP
    6. Restart the Admin Server.
    7. Login with new username/password
    The question is how do I run Step 4) above? Like what is the Java home, or jar file that has the weblogic.security.utils.AdminsAccount class?
    Thanks
    Ravi

    The class "weblogic.security.utils.AdminAccount" is part of weblogic.jar
    And JAVA_HOME would be the java installation directory, for example "D:\Middleware\wls1036\jdk160_29\bin"
    So, for example, the same command can be read as
    D:\Middleware\wls1036\jdk160_29\bin\java -cp D:\Middleware\wls1036\wlserver_10.3\server\lib\weblogic.jar weblogic.security.utils.AdminAccount <tempadmin> <temppassword> .
    OR
    Another option for you is to just run setDomainEnv to set the JAVA_HOME and CLASSPATH variables for us.
    For windows open a command prompt and run,
    <domain_home>/bin/setDomainEnv.cmd
    For linux run,
    . <domain_home>/bin/setDomainEnv.sh {Remember the dot and space, ". ", at the beginning are very important for a open shell with the environment variables set}
    After running the above command, then cd <domain_home>/security (step 2)
    Now, after doing the above, you can directly run the command in step 4
    java weblogic.security.utils.AdminAccount <tempadmin> <temppassword> ./
    Arun

  • Weblogic.security.SecurityInitializationException: Authentication for user system denied

    Reason: weblogic.security.SecurityInitializationException: Authentication for user system denied
    I tried my user name.But server didn't start.PLz help me and tell me what i have to do.
    Thanks

    Hi,
    The admin server is also able to start the managed server. The easiest way is
    to use a script. The command of starting a managed server is not much different
    from the one for the admin server. Just make sure that you reference the admin
    server URL (eg. http://localhost:7001). The more production environment way of
    managing managed server is to use the notemanger. See the admin guide for more
    infos.
    Which version are you using?
    Kai
    "hari" <[email protected]> wrote:
    >
    Hi!Kai..
    I tried with system/weblogic....but same error.Actually i created domain
    and managed
    server in existing domain throgh config.sh
    But the admin server is running properly.But the manager is not starting,user
    authentication problem is coming.When i was created domain..i created
    a user.I
    started admin server with that user...but manged server is not starting.Plz
    help
    me.

  • Tool for WLS 9.1 / Weblogic Realtime development?

    I'm looking for a Dev environment to do EJB development for the WLS 9.1 / Realtime server. My understanding is that BEA Workshop is going to be the tool going forward, ultimately replacing the Weblogic Workshop that comes with WebLogic Platform 8.1.
    I've downloaded the eval copy, but I don't see there how to create EAR or EJB projects. Is the correct tool to use? I will eventually want to create webapps with that EAR, but I need a tool now to use for WLS 9.1.
    Thanks,
    Gary

    Gary,
    If you are interested in the beta of our BEA Workshop for WebLogic ? It
    will be the combined M7 and WebLogic code lines on top of Eclipse.
    I will contact you directly via email. We'd love your feedback on this.
    br
    Gary Mui wrote:
    Hi Ram,
    Yes, that would be true for 8.1, and is in fact what we're using now. But I'm trying to see what I can use for WLS 9.1 which as far as I understand, Weblogic Workshop does not support. Basically I'm looking for a Weblogic Workshop equivalent for WLS 9.1 and was wondering if BEA Workshop was it. So for now, I guess I'm stuck with just a text editor and the supplied ant scripts that come with WLS 9.1?
    Thanks for your input, but unfortunately, I'm still a little unsure of what best to use to develop with BEA's latest app server.
    Thanks,
    Gary

  • [svn] 4286: Bug: BLZ-282: added property name to debug info for Map serialization

    Revision: 4286
    Author: [email protected]
    Date: 2008-12-10 18:29:26 -0800 (Wed, 10 Dec 2008)
    Log Message:
    Bug: BLZ-282: added property name to debug info for Map serialization
    checkintests: pass
    Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-282
    Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Input.java

    Guo,
    I see a question mark in the sql statement, instead of the Oracle-style bind parameter notation which would be ":1". Can you change your VO to use Oracle-Style bind params and see whether it works?
    Steven Davelaar,
    JHeadstart Team.

  • Weblogic Error when Starting AdminServer for OracleBI

    Hi all,
    I have the following error over Oracle BI 11.1.1.7 with Weblogic server. I was trying to integrate LDAP Authentication and the server refuse to start.
    Regards,
    VG
    ####<03-Jul-2013 11:09:29 o'clock IST> <Error> <Security> <OMEG6116> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372846169940> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: Premature end of file.>
    ####<03-Jul-2013 11:09:29 o'clock IST> <Critical> <WebLogicServer> <OMEG6116> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1372846169943> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: Premature end of file.
    weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: Premature end of file.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: oracle.security.jps.config.JpsConfigurationException: Premature end of file.
    at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.initDefaultConfiguration(XmlConfigurationFactory.java:436)
    at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.getDefaultConfiguration(XmlConfigurationFactory.java:338)
    at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.getConfiguration(XmlConfigurationFactory.java:160)
    at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.<init>(JpsContextFactoryImpl.java:112)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at java.lang.Class.newInstance0(Class.java:355)
    at java.lang.Class.newInstance(Class.java:308)
    at oracle.security.jps.util.JpsUtil.newInstance(JpsUtil.java:190)
    at oracle.security.jps.JpsContextFactory$1.run(JpsContextFactory.java:74)
    at oracle.security.jps.JpsContextFactory$1.run(JpsContextFactory.java:72)
    at oracle.security.jps.JpsContextFactory.getContextFactory(JpsContextFactory.java:71)
    at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2955)
    at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2950)
    at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2950)
    at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3228)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at java.lang.Class.newInstance0(Class.java:355)
    at java.lang.Class.newInstance(Class.java:308)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1343)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1024)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:879)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: org.xml.sax.SAXParseException: Premature end of file.
    at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
    at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
    at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
    at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
    at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
    at com.sun.org.apache.xerces.internal.jaxp.validation.StreamValidatorHelper.validate(StreamValidatorHelper.java:144)
    at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:111)
    at javax.xml.validation.Validator.validate(Validator.java:127)
    at oracle.security.jps.internal.common.util.XmlSchemaValidationUtil$1.run(XmlSchemaValidationUtil.java:132)
    at oracle.security.jps.internal.common.util.XmlSchemaValidationUtil.doValidation(XmlSchemaValidationUtil.java:124)
    at oracle.security.jps.internal.common.util.XmlSchemaValidationUtil.doValidation(XmlSchemaValidationUtil.java:99)
    at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.initDefaultConfiguration(XmlConfigurationFactory.java:418)
    at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.getDefaultConfiguration(XmlConfigurationFactory.java:338)
    at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.getConfiguration(XmlConfigurationFactory.java:160)
    at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.<init>(JpsContextFactoryImpl.java:112)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at java.lang.Class.newInstance0(Class.java:355)
    at java.lang.Class.newInstance(Class.java:308)
    at oracle.security.jps.util.JpsUtil.newInstance(JpsUtil.java:190)
    at oracle.security.jps.JpsContextFactory$1.run(JpsContextFactory.java:74)
    at oracle.security.jps.JpsContextFactory$1.run(JpsContextFactory.java:72)
    at oracle.security.jps.JpsContextFactory.getContextFactory(JpsContextFactory.java:71)
    at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2955)
    at oracle.security.jps.internal.policystore.PolicyUtil$3.run(PolicyUtil.java:2950)
    at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2950)
    at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3226)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:383)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at java.lang.Class.newInstance0(Class.java:355)
    at java.lang.Class.newInstance(Class.java:308)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1343)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    >

    Solved,
    checked in the domain_name\config\fmwconfig for zero byte files and found that the jps-config.xml was empy.
    Regards

  • Weblogic security: coping URL into other tab

    Hi,
    We have two Weblogic servers on two phisically different locations.
    First of them, WLS A, have perfect security. When you login into any application that is deployed on it, and try:
    - copy URL into another tab or browser window, you are getting returned at login page
    - when you close browser (without logout), and try to start application from history, you are getting login page, again
    So, URL that you have when you enter the application is absolutely useless. Closing the browser, or tab with application have practicaly same meaning as logout.
    Second of them, WLS B, have not that security. When you login into any application that is deployed on it, and:
    - copy URL into another tab or browser window, you are getting application without need to login! So that URL can be very dangerous, because it is possible to misuse it, if the user don't make logout
    - closing browser without logout: it is possible to find out the URL in history and go back into application without login!
    It is obvious that the problem is some setting on weblogic server. We tried to compare the settings on WLS A and WLS B but we have not found the setting that we have search for. The programmer that have found and set that property on WLS A working not more in our company.
    Can anybody help, we will be very greatful!
    Thanks,

    Hi,
    The authenticate method would take the user and the password details from the environment
    (env) that is passed and after successful authentication would populate the subject with
    the principals (i.e user, group the user belongs to ..)
    It should work with any user that is defined in the WLS not just weblogic/weblogic.
    Do you have any other users defined and which group do they belong to?
    Vimala
    Khalid Rizvi wrote:
    I am playing (learning) with weblogic.security.auth.login.UsernamePasswordLoginModule
    as a LoginModule using JAAS based authentication. Surprisingly, the only userid
    and password combination acceptable is uid=weblogic, pw=weblogic combination.
    I went through and looked at the example code under
    http://e-docs.bea.com/wls/docs70/security/cli_apps.html#1042212. I found that
    the UsernamePasswordLoginModule.login calls into
    if (url != null) {
    Environment env = new Environment();
    env.setProviderUrl(url);
    env.setSecurityPrincipal(username);
    env.setSecurityCredentials(password);
    try {
    Authenticate.authenticate(env, subject);
    Seems like UsernamePasswordLoginModule only is a router, as it instantiates an
    instance of Environemt using the userid and password and passes this Environemtn
    instance (env) to Authenticate.authenticate along with the empty Subject instance.
    I read about that the Subject instance will be filled in with Principals by the
    WL Server.
    My question is that firstly,
    1. As Authenticate.authenticate is not passed in the uid and pw, will it pick
    those from the env?
    2. Secondly, why does it only accept uid=weblogic & pw=weblogic.
    I will appreciate if some one can put me in the right direction.
    Khalid R. Rizvi
    508-641-1192
    [email protected]

  • JVM options for WLS

    Where can I find a complete list of available JVM options for WLS?
    For example -Dweblogic.security.SSL.protocolVersion is not listed anywhere

    Where can I find a complete list of available JVM options for WLS?
    For example -Dweblogic.security.SSL.protocolVersion is not listed anywhere
    That is NOT a JVM options as I just explained in your other thread - see that thread for details.
    JVM options
    That "-Dxxx" syntax means you are specifying a system property on the Java command-line when launching Java.
    That property can now be accessed in the Java app
    You can make up and use ANYTHING you want when you write your own apps - those command line entries will just get added to the standard/default System properties as I explain in your other thread.
    Consult the WebLogic documentation (or onliine help if WLS has such a thing) for info on the system properties that have been defined for WLS.

Maybe you are looking for