Connectivity with Weblogic

can we access Weblogic beans from Oracle Java Stored procs
Currently I am using RMI for achieving teh connectivity....Anyother options...to make life easier..
null

I don't have any experience with this, you may want to repost your question in the Oracle8i JVM forum here on OTN.
Thanks,
Rob
null

Similar Messages

  • Crystal Report 9 connectivity with WebLogic 10.3.5

    Hello,
    Is the Crystal Report 9 certified with WebLogic 10.x? Currently WebLogic 8.x is in use. Trying to upgrade the WebLogic.
    Thanks

    What does this have to do with Database Connectivity?
    An I doubt it, CR 9 is about 8 or 9 years old well before 10.3 was released. Check the Platforms PDF's for more info.
    Don

  • Which edition of DB2 Connect neccessary for connection with WebLogic 6.1

    Hi!
    Who can tell me, which editions of DB2 Connect work together with WebLogic
    6.1?
    - the hardware-related Personal Edition
    - the Enterprise Edition run on an extra server, which works as a gateway
    between DB2 and its clients.
    - the CAE-Client (Client Application Enabler)
    We would prefer the Personal Edition - if possible - does anyone has
    experiences? IBM can not give us this neccessary information.
    Thanks
    Marita

    Hi Marita,
    WebLogic will work with any JDBC 2.0 compatible driver.
    Generally, a gateway would add some overhead. You could
    setup a WebLogic connection pool using the simplest way
    and see if it satisfy your needs.
    Regards,
    Slava Imeshev
    "Marita León Ohl" <[email protected]> wrote in message
    news:[email protected]..
    Hi!
    Who can tell me, which editions of DB2 Connect work together with WebLogic
    6.1?
    - the hardware-related Personal Edition
    - the Enterprise Edition run on an extra server, which works as a gateway
    between DB2 and its clients.
    - the CAE-Client (Client Application Enabler)
    We would prefer the Personal Edition - if possible - does anyone has
    experiences? IBM can not give us this neccessary information.
    Thanks
    Marita

  • JNDI Provider Connection With Weblogic 8.1

    Hi all,
    I am using SUN ONE Studio V 5.0 update 1 with weblogic 8.1 integrated with it.
    Today I have added weblogic.jar in the classpath of the project.
    Now I went to "runtime tab" and installed a jndi provider with factoryname and url successfully.
    I tested the provider successfully :)
    But when I tried to connect it to the service it failed.
    IDE thrown a NPE and error message in dialog appears, says "TimeOut value is too short to connect".
    There is no option for setting this timeout value.
    Could any one pls help me regarding this. How can I get connected to JNDI service given by WL 8.1 ?
    Has anyone also faced such problem ?
    My server is up and smiling on me.
    I am adding that error message fully....
    java.lang.NullPointerException
         at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGenerator.java:785)
         at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:758)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:803)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:790)
         at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
         at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootServiceStub.java:50)
         at weblogic.security.acl.internal.Security.authenticate(Security.java:152)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:597)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:534)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:336)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:80)
         at org.netbeans.modules.jndi.JndiDirContext.<init>(JndiDirContext.java:47)
         at org.netbeans.modules.jndi.JndiDataType$1$Connector.checkContextValidity(JndiDataType.java:211)
         at org.netbeans.modules.jndi.JndiDataType$1$Connector.run(JndiDataType.java:169)
         at java.lang.Thread.run(Thread.java:534)
    --------------- nested within: ------------------
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Failed to generate class for weblogic.common.internal.RMIBootServiceImpl_811_WLStub ] - with nested exception:
    [java.lang.NullPointerException]
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:807)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:790)
         at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
         at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootServiceStub.java:50)
         at weblogic.security.acl.internal.Security.authenticate(Security.java:152)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:597)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:534)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:336)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:80)
         at org.netbeans.modules.jndi.JndiDirContext.<init>(JndiDirContext.java:47)
         at org.netbeans.modules.jndi.JndiDataType$1$Connector.checkContextValidity(JndiDataType.java:211)
         at org.netbeans.modules.jndi.JndiDataType$1$Connector.run(JndiDataType.java:169)
    [catch] at java.lang.Thread.run(Thread.java:534)
    one this more, if u see help then it is written that WL plugin will work only with jdk 1.3.1 and not with 1.4 but my plugin works successfully. What does it mean ?
    My userdir is : C:\Utility\Dir4j, when I installed the provider for connecting to JNDI service of WL, then IDE created a dir C:\Utility\Dir4j\system\JNDI folder and created weblogic_jndi_WLInitialContextFactory.impl file under it.
    Because I added that weblogic.jar file on my FSystem thats' why It created it under my userdir.
    Pls Help
    Sanjeev

    Hi Sanjeev :
    I am running into the same problem . Could you please be kind enough to tell me how you fixed the problem. I followed your solution but I am still running into the same problem.
    Basically my WebStart application should be getting a connection from the Connection pool making a t3 call to a Weblogic server.
    Thanks in advance .

  • Generic Connection with weblogic.jdbc.sqlserver.SQLServerDriver

    Hi,
        I am able to setup the SQLServer Generic connection in jdeveloper no issue with that, but i am trying the same in the server with jython as follows:
    ods =  OracleDataSource();
    ods.setURL("jdbc:weblogic:sqlserver://MY_HOST:PORT;DatabaseName=MY_DBNAME");
    ods.setUser(argDBUser);
    ods.setPassword(argDBPassword);
    con = ods.getConnection(); // at this point
    And i am getting "Invalid Oracle URL specified"
    If you have encountered such issue. I will greatly be thankful, for you input.
    Please let me know what i have missed or wrong.
    jdev 11.1.1.6
    Thanks

    test test wrote:
    Hi,
    I am just writing a test program in Eclipse and tried to connect to MS SQL Server. I added weblogic.jar to project lib. But it complaints ClassNotFound: weblogic.jdbc.sqlserver.SQLServerDriver. where is it?
    Found out I have to have wlbase.jar wlclient.jar wlutil.jar wlsqlserver.jar.You need wlbase, wlutil, wlsqlserver, and weblogic jars.
    Joe

  • Ldap connection with weblogic console and authentification with java

    Hello,
    I want that my web application use ldap authentification for users and that all parameters (host, port, base, ...) are configured by weblogic console.
    I managed to do it by security-->realms-->.... , but now, I want to perform authentification in my java code.
    I don't know how realized it because I don't know how use my ldap connection in java code without redefine parameters into my code...
    can anyone help me please?
    thanks a lot for your help.

    Hey,
    on a windows server system you have to put the target system CA Certificate in the local Trusted System Certificate Store of Microsoft Server. Then the connection should work.
    On a Java System you have to put the CA in the Key Storage of the SAP System.
    I think on Unix you could use the SAPCRYPTOLIB to place the CA in  the abap system.
    Kind regards,
    Sven Walter

  • Lost connection with db, restarting Weblogic

    hi,
    we have an server with oracle and whenever the connection
    with the db is lost for any reason and then comes again in a while the weblogic needs to be restarted again.
    i would love if someone could give me a tip of what excactlly weblogic is "loosing" from the connection or how i may run a script or anything so this to work automatically(mean to startup weblogic again).
    thanks anyway for reading my problem.

    Hi,
    Along with enabling "Test Reserved connections", also ensure refresh connections is enabled. Test Reserved Connections tests the connection only when a client makes a request while refresh connections ensures that all unreserved connections are also tested.
    -Jagan

  • WebLogic 9.2:  Oracle:  Can longer connect with a Good Data Source

    Hi;
    I have WebLogic 9.2 set up on my computer as a development tool. Yesterday I was able to connect to the test database on our test server with the JNDI/Database resource "abc" just fine.
    For some reason, it simply stopped working this morning.
    I got this error message when trying to connect with the webapp I use:
    *+<Jul 28, 2011 4:48:14 PM EDT> <Notice> <Stdout> <000000> <Exception in getPersonIdByEmail(String emailAddress) - statementDB14>+*
    +java.sql.SQLException: Cannot obtain connection: driverURL = jdbc:weblogic:pool:nsd, props = {EmulateTwoPhaseCommit=false, connectionPoolID=abc, jdbcTxDataSourcourceName=abc}.+*
    Nested Exception: java.lang.RuntimeException: Failed to Generate Wrapper Class*
    at weblogic.utils.wrapper.WrapperFactory.createWrapper(WrapperFactory.java:213)
    at weblogic.jdbc.wrapper.JDBCWrapperFactory.getWrapper(JDBCWrapperFactory.java:173)
    at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:247)
    at weblogic.jdbc.pool.Driver.connect(Driver.java:164)
    at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:647)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:137)
    I got this error message when using a Test JSP I have for doing a simple database connection using that Database Resource ( "abc")
    *+<Jul 28, 2011 4:52:06 PM EDT> <Error> <HTTP> <BEA-101020> <[weblogic.servlet.internal.WebAppServletContext@507c6d - appName: 'mainWebApp', name: 'mainWebApp',  context-path: ''] Servlet failed with Exception+*
    java.lang.NullPointerException*
    at jsp_servlet._test.__testjndiweblogic._jspService(__testjndiweblogic.java:145)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    Truncated. see log file for complete stacktrace
    Any ideas on how I can fix whatever is wrong?
    Thanks in advance
    Edited by: 872921 on Jul 28, 2011 2:14 PM

    Hi Joe;
    I appreciate you taking time to answer my question.
    By client do you mean my JRE? I one JRE set in my JAVA_HOME, and two in the weblogic install. How can I tell which is WebLogic using? So, you are basically saying make sure my Oracle JDBC drivers wherever they are in WebLogic should match what I have in my JRE?
    I'll give that a shot when I get into work tomorrow.
    I am puzzled because it has been working fine for weeks and I haven't changed anything.

  • Client Code not connecting to WebLogic 8.1 with Mutual Authentication

    I am trying to connect to a WebLogic 8.1 web services application. The weblogic instance has mutual authentication enabled, so the client needs to send a certificate when it does an SSL handshake with the server. I am trying to connect with standalone Java JUnit tests. Both the web services and the JUnit tests are using Apache Axis 1.4.0. I've obtained what I believe to be the appropriate certificates from the weblogic administrator that configured the mutual authentication. There is a certificate for the machine I'm trying to connect to, and two other certificates in the chain (three certificates all together, including the root). I've tried several different methods of putting those three certificates in keystores and trust keystores, reading in those keystores in my java code, and connecting to the web services, and I always end up with the same error in the WebLogic server logs. "Certificate chain receved from <ip address> was incomplete."
    Here is an example of my code:
    I initialize like so:
         Properties tempProperties = // (here is where I obtain my properties from a properties file... code removed for security reasons)
         System.setProperty("javax.net.ssl.trustStore", tempProperties.getProperty("trust.keystore.file"));
         System.setProperty("javax.net.ssl.trustStorePassword", tempProperties.getProperty("trust.keystore.password"));
         System.setProperty("javax.net.ssl.trustStoreType", "jks");
         System.setProperty("javax.net.ssl.keyStore", tempProperties.getProperty("keystore.file"));
         System.setProperty("javax.net.ssl.keyStorePassword", tempProperties.getProperty("keystore.password"));                         System.setProperty("javax.net.ssl.keyStoreType", "jks");
         System.setProperty ( "java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol" );
         Security.addProvider ( new com.sun.net.ssl.internal.ssl.Provider ( ) );
    I bind to the appropriate port and locate the service, etc. using auto-generated methods descendant from Apache Axis. No matter what I try, I get the same results. The client says: main, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    The server log says: Certificate chain received from <ip address> was incomplete.
    I've even tried implementing a custom SSL handler as described here http://alweb.homeip.net/dw0rm/dblog/?p=38, and I can verify by stepping into my code that everything gets initialized and set up correctly, and that all three certificates in the chain that I need are obtained from my keystore, but I still get the same error on the client and the server. I've enabled ssl handshake debugging on my client and I can see the whole certificate chain being output to the debug console.
    Any idea what I might be doing wrong?

    My guess would be that the server is not able to validate your certificate. Make sure that the CA for your certificate is trusted by WLS.
    I always like to debug something like this by add -Djavax.net.debug=ssl to both the client and server. It should give you a complete picture of what is going on.
    Edited by: joshbregmanoracle on May 20, 2009 8:49 PM

  • Weblogic Connection with Oracle JMS AQ errors

    Hi All,
    I am a newbie with SOA 11g and I am trying to do a simple test case for a use case of connecting Oracle AQ JMS with Weblogic and using it in my SOA 11g process. I am trying to publish something to my queue that I created but I am getting this error in the weblogic / soa log files pasted below :
    The steps I followed exactly are this :
    1) Created a Database Queue called DemoInqueue using the following scripts :
    exec dbms_aqadm.create_queue_table ( queue_table=> 'DemoInQueue', queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers=> FALSE, compatible=> '8.1');
    COMMIT;
    exec dbms_aqadm.create_queue(queue_name=> 'DemoInQueue', queue_table=> 'DemoInQueue');
    COMMIT;
    exec dbms_aqadm.start_queue('DemoInQueue');
    COMMIT;
    2) Created a Data Source in weblogic server : Called it using the JNDI name : jdbc/oracle/jms Driver Class Name : oracle.jdbc.xa.client.OracleXADataSource (I tested the connection it works fine)
    3) Created a JMS Module (JMSTestModule) and then Created a New Summary of Resource for it ( AQServer) and chose option Foregin Server.
    Under General Tab, I gave "oracle.jms.AQjmsInitialContextFactory" as the JNDI Initial Context Factory and Under JNDI Properties I put in "datasource=jdbc/oracle/jms" as I created the above datasource.
    Under Connection Factores I created a new "ForeignConnectionFactory-0". Under Configuration I gave Local JNDI name as "jms/DemoCF" and remote JNDI Name as "XAQueueConnectionFactory" (I have also tried with
    QAConnectionFactory but no difference )
    Under Destinations I created a new "ForeignDestination-0" with local JNDI name as "jms/DemoInQ" and Remote JNDI Name as "Queues/DemoInQueue" (Because my Queue name is that)....
    4) I restarted the Weblogic Server then went to SOA suite and tried a very simple process Hello world added a JMS adpater....Inside the adpater I selected OEMS (Advanced Queueing), App server my weblogic server,
    operation as ProduceMessage and when I hit Browse I was able to see my AQServer ForeignDestination-0 Queue. I selected it and under destination name it populated "jms/DemoInQ" but under JNDI name it also
    populated "eis/aqjms/Queue" I left that as is and deployed my process and tried invoking it. It failed with the error message below.....I also tried modifying the JNDI name to something else...in Jdev..but the results
    are the same....
    Are these steps correct ? Am I missing something here.?
    I followed all the blogs and forums in this site and I think I did all the steps...but if anyone can help me I would really appreciate it...
    Here is the error stack below :
    <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437281> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    ####<Dec 1, 2010 2:07:17 PM EST> <Warning> <Connector> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437296> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    SOA LOG.....
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.adapter> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <JCABinding=> [default/HelloWorldComposite!1.0*soa_25f514de-3db3-4bed-9144-44d83dacbe10.Publishmessage]:Produce_Message One-way operation Produce_Message() failed>
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.bpel.engine.ws> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <<WSInvocationManager::invoke> got FabricInvocationException
    oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
    Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue.
    JCA Binding Component is unable to create an outbound JCA (CCI) connection.
    HelloWorldComposite:Publishmessage [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.

    Thanks for passing along the link.
    The part about Oracle's documentation not mentioning the JmsAdapter configuration was a real sticking point for me - I was having the same problem as the original poster until I updated that deployment as the link outlined.
    Also, towards the end of that link the author mentions running in to problems getting their composite to successfully bind to the queue definitions that were created in WebLogic.
    I attempted post my solution to this on the original site, but I'm not sure if it got through - so I'll add the details of what worked for me here:
    Connection Factory:
    Local JNDI: aqjms/JMSTest_Connection_Factory
    Remote JNDI: XAQueueConnectionFactory
    Destination:
    Local JNDI: aqjms/JMSTest_Queue
    Remote JNDI: Queues/JMSTest_Queue
    Outbound Connection Pool:
    Name: eis/aqjms/JMSTest_Queue
    Connection Factory: aqjms/JMSTest_Connection_Factory
    JDeveloper Composite:
    Destination Name: aqjms/JMSTest_Queue
    JNDI Name: eis/aqjms/JMSTest_Queue
    Cheers,
    - Nathan

  • How to connect websocket with weblogic.

    Hi,
    Can anyone tell how to connect websocket of html5 with weblogic server. Currently i am doing this thing with webbit NettyWebServer.
    thanks in advance

    Hi Shajon --
    Unfortunately, we're not permitted to give specific release dates/estimates - the best I can offer is that FMW 12c (which will contain WLS 12.1.2) is due to ship in CY 2013.
    I can probably provide you with the GlassFish chat example we have running on WLS (v.minor changes in API) to give you a sense of what it looks like.
    -steve-

  • Weblogic 5.1 connectivity with oracle 8i

     

    You can use the Oracle Thin Driver to access Oracle 8.1.6. Our Oracle JDBC driver
    (a type 2 driver that relies on the Oracle OCI library) does not yet support
    Oracle 8.1.6.
    Abraham Oommen wrote:
    Please help me understand this better. Does this mean that 8.1.6 is not
    supported as of now? Or can I get alternative JDBC drivers from elsewhere? I
    am about to begin installation of 8.1.6 with Weblogic Commerce Server 2.0 and
    App Server 5.1 and I was curious if this was a road block that I should avoid.
    Michael Girdley wrote:
    I would guess that you are using Oracle 8.1.6 with our driver. I would
    recommend either using Oracle 8.1.5 with our driver or using the Oracle thin
    driver -- has noted in our documentation.
    The platform support page and certification page for WebLogic Server is
    located at:
    http://www.weblogic.com/docs51/platforms/index.html
    This page has the latest and greatest information on the platforms that
    WebLogic is certified and supported on.
    Thanks,
    Michael
    Michael Girdley
    Product Manager, WebLogic Server & Express
    BEA Systems Inc
    amani <[email protected]> wrote in message news:[email protected]..
    Dear all friends,
    When I use dbping Oracle scott tiger i receive the following error:
    Java.sql.SQLException :System.loadlibrary threw
    java.lang.unsatisfiedlinkerror with the message 'no weblogicOci36 in
    java.library.path'
    at weblogic.jdbcbase.Oci.Driver.connect <Driver.java:116>
    at java.sql.DriverManager.getConnection <DriverManager.java;457>
    at java.sql.DriverManager.getConnection<DriverManager.java:106>
    at utils.dbping.main<dbping.java.156>

  • JMX Connectivity with the Adminstration Server - Weblogic 9.x

    When using the java naming provider url in Managed Server startup script, or in server start tab when using node manager, or loading it from properties file (for deployment) we see below JMX Warning message in Managed Server startup log saying JMX connectivity exception with Admin Server. This is BUG in Weblogic 9.x release and there is CR open on this issue.
    <May 19, 2009 10:35:25 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.149.181.55:20001
    for protocols iiop, t3, ldap, http.>
    <May 19, 2009 10:35:25 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ManagedServer1_1
    " for domain "wls923_domain1" running in Production Mode>
    <May 19, 2009 10:35:25 AM EDT> <Notice> <Log Management> <BEA-170027> <The server initialized the domain log broadcaster
    successfully. Log messages will now be broadcasted to the domain log.>
    <May 19, 2009 10:35:25 AM EDT> <Warning> <JMX> <BEA-149509> <Unable to establish JMX Connectivity with the Adminstration
    Server AdminServer at service:jmx:t3://AdminServer:20000/jndi/weblogic.management.mbeanservers.domainruntime.
    java.io.IOException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.m
    beanservers'
    at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:151)
    at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
    at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:326)
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnec
    tion(RegisterWithDomainRuntimeService.java:199)
    Truncated. see log file for complete stacktrace
    javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblog
    ic.management.mbeanservers'; remaining name 'domainruntime'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    Truncated. see log file for complete stacktrace
    >
    <May 19, 2009 10:35:26 AM EDT> <Notice> <Cluster> <BEA-000102> <Joining cluster Cluster1 on 239.192.23.2:7001>
    - - Tarun

    When using the java naming provider url in Managed Server startup script, or in server start tab when using node manager, or loading it from properties file (for deployment) we see below JMX Warning message in Managed Server startup log saying JMX connectivity exception with Admin Server. This is BUG in Weblogic 9.x release and there is CR open on this issue.
    <May 19, 2009 10:35:25 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.149.181.55:20001
    for protocols iiop, t3, ldap, http.>
    <May 19, 2009 10:35:25 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ManagedServer1_1
    " for domain "wls923_domain1" running in Production Mode>
    <May 19, 2009 10:35:25 AM EDT> <Notice> <Log Management> <BEA-170027> <The server initialized the domain log broadcaster
    successfully. Log messages will now be broadcasted to the domain log.>
    <May 19, 2009 10:35:25 AM EDT> <Warning> <JMX> <BEA-149509> <Unable to establish JMX Connectivity with the Adminstration
    Server AdminServer at service:jmx:t3://AdminServer:20000/jndi/weblogic.management.mbeanservers.domainruntime.
    java.io.IOException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.m
    beanservers'
    at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:151)
    at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
    at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:326)
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnec
    tion(RegisterWithDomainRuntimeService.java:199)
    Truncated. see log file for complete stacktrace
    javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblog
    ic.management.mbeanservers'; remaining name 'domainruntime'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    Truncated. see log file for complete stacktrace
    >
    <May 19, 2009 10:35:26 AM EDT> <Notice> <Cluster> <BEA-000102> <Joining cluster Cluster1 on 239.192.23.2:7001>
    - - Tarun

  • Problem connecting to Weblogic Server

    I have a JMS application for which I am trying to create a connection factory for Oracle ESB (Weblogic). I added the wlfullclient.jar to my classpath and start the application. I receive the following error in my application's log?
    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jms.connection.oracle' defined in ServletContext resource [WEB-INF/spring/context-oracle.xml]: Invocation of init method failed; nested exception is javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
         at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
         at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
         at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
         at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
         at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
         at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269)
         ... 87 more
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at org.springframework.jndi.JndiTemplate.createInitialContext(JndiTemplate.java:137)
         at org.springframework.jndi.JndiTemplate.getContext(JndiTemplate.java:104)
         at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:86)
         at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:153)
         at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178)
         at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95)
         at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105)
         at org.springframework.jndi.JndiObjectTargetSource.afterPropertiesSet(JndiObjectTargetSource.java:96)
         at org.springframework.jndi.JndiObjectFactoryBean$JndiObjectProxyFactory.createJndiObjectProxy(JndiObjectFactoryBean.java:284)
         at org.springframework.jndi.JndiObjectFactoryBean$JndiObjectProxyFactory.access$000(JndiObjectFactoryBean.java:273)
         at org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiObjectFactoryBean.java:176)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1369)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
         ... 97 more
    Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
         at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387)
         at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:247)
         at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:46)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
         ... 113 more
    Is this the correct JAR to add and if so how can I resolve this problem?

    Exception that you shows clearly says your enviroment does not find weblogic.jndi.WLInitialContextFactory class, this class is inside weblogic.jar, wlclient.jar, etc, however. If you only has added wlclient and wljmsclient probably there are missing some libraries that your application requires, I suggest try with weblogic.jar instead of wlclient.jar + wljmsclient.jar.
    If this works, maybe you are not building your wlfullclient.jar correctly.

  • Has anyone used JAAS with WebLogic?

    Has anyone used JAAS with Weblogic? I was looking at their example, and I have a bunch of questions about it. Here goes:
    Basically the problem is this: the plug-in LoginModule model of JAAS used in WebLogic (with EJB Servers) seems to allow clients to falsely authenticate.
    Let me give you a little background on what brought me to this. You can find the WebLogic JAAS example (to which I refer below) in the pdf: http://e-docs.bea.com/wls/docs61/pdf/security.pdf . (I believe you want pages 64-74) WebLogic, I believe goes about this all wrong. They allow the client to use their own LoginModules, as well as CallBackHandlers. This is dangerous, as it allows them to get a reference (in the module) to the LoginContext's Subject and authenticate themselves (i.e. associate a Principal with the subject). As we know from JAAS, the way AccessController checks permissions is by looking at the Principal in the Subject and seeing if that Principal is granted the permission in the "policy" file (or by checking with the Policy class). What it does NOT do, is see if that Subject
    has the right to hold that Principal. Rather, it assumes the Subject is authenticated.
    So a user who is allowed to use their own Module (as WebLogic's example shows) could do something like:
    //THEIR LOGIN MODULE (SOME CODE CUT-OUT FOR BREVITY)
    public class BasicModule implements LoginModule
    private NameCallback strName;
    private PasswordCallback strPass;
    private CallbackHandler myCB;
    private Subject subj;
             //INITIALIZE THIS MODULE
               public void initialize(Subject subject, CallbackHandler callbackHandler, Map sharedState, Map options)
                      try
                           //SET SUBJECT
                             subj = subject;  //NOTE: THIS GIVES YOU REFERENCE
    TO LOGIN CONTEXT'S SUBJECT
                                                     // AND ALLOWS YOU TO PASS
    IT BACK TO THE LOGIN CONTEXT
                           //SET CALLBACKHANDLERS
                             strName = new NameCallback("Your Name: ");
                             strPass = new PasswordCallback("Password:", false);
                             Callback[] cb = { strName, strPass };
                           //HANDLE THE CALLBACKS
                             callbackHandler.handle(cb);
                      } catch (Exception e) { System.out.println(e); }
         //LOG THE USER IN
           public boolean login() throws LoginException
              //TEST TO SEE IF SUBJECT HOLDS ANYTHING YET
              System.out.println( "PRIOR TO AUTHENTICATION, SUBJECT HOLDS: " +
    subj.getPrincipals().size() + " Principals");
              //SUBJECT AUTHENTICATED - BECAUSE SUBJECT NOW HOLDS THE PRINCIPAL
               MyPrincipal m = new MyPrincipal("Admin");
               subj.getPrincipals().add(m);
               return true;
             public boolean commit() throws LoginException
                   return true;
        }(Sorry for all that code)
    I tested the above code, and it fully associates the Subject (and its principal) with the LoginContext. So my question is, where in the process (and code) can we put the LoginContext and Modules so that a client cannot
    do this? With the above example, there is no Security. (a call to: myLoginContext.getSubject().doAs(...) will work)
    I think the key here is to understand JAAS's plug-in security model to mean:
    (Below are my words)
    The point of JAAS is to allow an application to use different ways of authenticating without changing the application's code, but NOT to allow the user to authenticate however they want.
    In WebLogic's example, they unfortunately seem to have used the latter understanding, i.e. "allow the user to authenticate however they want."
    That, as I think I've shown, is not security. So how do we solve this? We need to put JAAS on the server side (with no direct JAAS client-side), and that includes the LoginModules as well as LoginContext. So for an EJB Server this means that the same internal permission
    checking code can be used regardless of whether a client connects through
    RMI/RMI-IIOP/JEREMIE (etc). It does NOT mean that the client gets to choose
    how they authenticate (except by choosing YOUR set ways).
    Before we even deal with a serialized subject, we need to see how JAAS can
    even be used on the back-end of an RMI (RMI-IIOP/JEREMIE) application.
    I think what needs to be done, is the client needs to have the stubs for our
    LoginModule, LoginContext, CallBackHandler, CallBacks. Then they can put
    their info into those, and everything is handled server-side. So they may
    not even need to send a Subject across anyways (but they may want to as
    well).
    Please let me know if anyone sees this problem too, or if I am just completely
    off track with this one. I think figuring out how to do JAAS as though
    everything were local, and then putting RMI (or whatever) on top is the
    first thing to tackle.

    Send this to:
    newsgroups.bea.com / security-group.

Maybe you are looking for