Will BEA release an IDE with WebLogic Server 10 in march?

Hi
Thank you for reading my post.
Can some one tell me whether bea release an IDE with its new version of Weblogic server 10 in March?
Thanks

Have you seen the Web Services tutorial:
http://e-docs.bea.com/workshop/docs92/ws_platform/introduction/conWorkshopTutorials.html
What specific features would you like to see, relative to EE5. We're
working on support for EE5 annotations, but what are you most interested?
br
legolas wood wrote:
can you please give me some links to workshop feature matrix ?
specially i am looking at what does it provide to ease web service development based on jee 5 standards and what does it provide in term of soa development.
thanks

Similar Messages

WLS :: Will Vista web client work with Weblogic Server 8.1.6 over SSL?

Hello,
I have installed 51-2 bit SSL cert on weblogic 7 and found that the secure site doesn't work on Vista web client.
Weblogic gives error in handshaking and says algorithm is not supported.
Vista web client uses some algorithms which were not supported by weblogic 7.
So would like to know if would Vista web client work with Weblogic Server 8.1.6 over SSL?
Any information in this regard would be helpful.
Thanks in Advance.

can you use the following debug flags in the weblogic server as java_options and paste the complete ssl handshake exception here.
-Dweblogic.StdoutDebugEnabled=true
-Dssl.debug=true
thanks,
sandeep

BEA Workshop for WebLogic Platform9.2 can use with weblogic server 9.1?

Wanted to know whether BEA Workshop for WebLogic Platform9.2 can be used with weblogic server 9.1?. If it cannot be used then which ide we need to use to build the j2ee application to deploy on to weblogic server 9.1

try http://edelivery.oracle.com
accept the licenses and in the next screens
"Select a Product Pack" select Oracle BEA
and your platform (i.e. Windows)
then select the media pack you want
i.e. "BEA WebLogic Media Pack for Linux x86"
and voila!
"WebLogic Platform 10.2 for Microsoft Windows (32-bit)"
(in the Platform includes WebLogic Server, Workshop for WebLogic, WebLogic Portal and WebLogic Integration)
./ydes

Enabling SSO with Weblogic Server

Hi,
Can someone please forward some documention on enabling SSO with Weblogic server for different applications using the admin console.
Is enabling SSO only possible programmatically??
Is there an external server amongst the Weblogic Platform that maintains this SSO information??
Regards,
Mukta

Pradeep,
Here are some questions for you.
1. what version of Weblogic App Server you are using?
2. Is it a weblogic Portal or a Java application deployed
on a Weblogic App Server?
3. You have mentioned that the users are stored in a table. Is it a database table ?
Anyway see the following link as a starting point?
http://e-docs.bea.com/wls/docs81/jconnector/security.html#1216783
If the customer has lot of other web applications that they want to integrate you can look at third party authentication solutions (Ex: Siteminder). But if it is a few or limited applications then custom solution would be more appropriate from the cost perspective.
Hope this can be a starting point.
-Regards
-Venkat Malempati

MQSeries as a Transactional Resource Manager with Weblogic Server

          I am trying to setup the example given in the BEA white paper:
          Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          Version 1.
          October 25, 2001.
          I followed the instructions given in the documents, but when i run client program
          >java MQClient t3://localhost:7001 "MQSeries test"
          I received the following exception below. Does anyone how what is the reason for
          this exception(s) and how i can solve the problem? My MQSeries Server and Weblogic
          6.1 sp2 are installed on seperate NT machines. I installed the MQSeries classes
          for java and the MQSeries classes for Java Message Service on the weblogic
          server machine.
          sending: "MQSEries test"
          Exception in thread "main" java.rmi.ServerError: A error occurred the server; ne
          sted exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          [java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          at $Proxy1.bridgeWLS2MQS(Unknown Source)
          at MQClient.main(MQClient.java:54)


The point is that over TCPIP the MQ XA connection factory is not available.
          The MQ shared memory/JNI driver is required to access it, which limits
          access to those processes that are on the same box as the MQ q manager.
          This is an MQ series limitation.
          Douglas WF Acheson wrote:
          > Hello,
          >
          > If memory server me correct, default connection to MQ Series is through
          > JNI calls and shared memory. You have to change the protocol to TCPIP when
          > connection to the queue manager on another box (do not know much about XA
          > with MQ Series); that is when you connect to MQ Series vi JMS on another
          > box you must do something like the following:
          >
          > qcf = new MQQueueConnectionFactory() ;
          > qcf.setHostName(hostName) ;
          > qcf.setPort(port) ;
          > qcf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) ;
          > qcf.setQueueManager(qManagerName) ;
          >
          > Then when you create you queues, sesions etc. you are point at the correct Q
          > manager.
          >
          > Hope this helps ...
          >
          > Douglas WF Acheson
          >
          > "Raja Mukherjee" <[email protected]> wrote in message
          > news:[email protected]...
          > > On a closer look at the original post (sorry for missing that, it was
          > early
          > > in the morning), you would not be able to use XA if your QM and WLS are in
          > > different boxes. Check on this newsgroup, there are several posts on this
          > > subject. The whitepaper, if I recall correctly, installs both MQ and WLS
          > on
          > > the sames box. This is a MQSeries limitation not WLS.
          > >
          > > .raja
          > >
          > >
          > > "ibrahim Nehme" <[email protected]> wrote in message
          > > news:[email protected]...
          > > >
          > > > I am trying to setup the example given in the BEA white paper:
          > > > Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          > > > Version 1.
          > > > October 25, 2001.
          > > > I followed the instructions given in the documents, but when i run
          > client
          > > program
          > > >
          > > > >java MQClient t3://localhost:7001 "MQSeries test"
          > > > I received the following exception below. Does anyone how what is the
          > > reason for
          > > >
          > > > this exception(s) and how i can solve the problem? My MQSeries Server
          > and
          > > Weblogic
          > > > 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries
          > > classes
          > > > for java and the MQSeries classes for Java Message Service on the
          > weblogic
          > > > server machine.
          > > > ---------------------------------------
          > > > sending: "MQSEries test"
          > > > Exception in thread "main" java.rmi.ServerError: A error occurred the
          > > server; ne
          > > > sted exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > <<no stack trace available>>
          > > > --------------- nested within: ------------------
          > > > weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          > > > [java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ]
          > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          > > > at $Proxy1.bridgeWLS2MQS(Unknown Source)
          > > > at MQClient.main(MQClient.java:54)
          > >
          > >

Jsf with weblogic server 6.1

Hi, Any help would be appreciated. I am trying to use jsf with weblogic server 6.1 and wlintegration 2.1 I tried to deploy the samples provided with jwsdp-1.2 When I start the guess number sample I get the following error message:
Duke's number: 3
<25-Jun-03 16:03:40 BST> <Error> <HTTP> <[WebAppServletConte
xt(57758238,examplesWebApp,/examplesWebApp)] Root cause of S
ervletException
javax.servlet.jsp.JspException: Cannot find FacesContext
at javax.faces.webapp.UIComponentTag.doStartTag(UICo
mponentTag.java:269)
at jsp_servlet._jsf_45_guessnumber._faces.__greeting
._jspService(__greeting.java:123)
at weblogic.servlet.jsp.JspBase.service(JspBase.java
:27), etc.
I updated the web.xml file, created the faces directory under my examplesWebApp active domain with the jsp files, it finds the UserNumberBean class but it still crashes with the above.
One problem I was having while deploying it that Weblogic Server did not allow me to copy jsf-api.jar, jstl.jar,etc under web-inf/lib.
So I added all required jar files under bea root/config/samples/lib and updated startWeblogic.cmd
Please help with how to deploy correctly the samples:
Botond

Thanks bill.
I checked my weblogic server 6.1,it limited to j2ee1.2 features only.So I changed it supporting j2ee1.3 features.Now my JSF example is working normally.
But I found a new question soon.
I writed some letter in Chinese in jsp page .And I got some errors in weblogic.
<2003-10-14 01:47:57> <Error> <HTTP> <101019> <[ServletContext(id=6480502,name=jaction,conte
xt-path=/jaction)] Servlet failed with IOException
java.io.IOException: javax.servlet.jsp.JspException: The taglib validator rejected the page: "org.xm
l.sax.SAXParseException: An invalid XML character (Unicode: 0xb8) was found in the CDATA section., "
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:124)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:356)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:214)
at weblogic.servlet.jsp.JspStub.checkForReload(JspStub.java:149)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:538)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:364)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:312)
at com.sun.faces.context.ExternalContextImpl.dispatchMessage(ExternalContextImpl.java:298)
at com.sun.faces.lifecycle.ViewHandlerImpl.renderView(ViewHandlerImpl.java:53)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:89)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:185)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:169)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:5517)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:31
56)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
I donnot know what is the matter.And how to correct?
thanks again.
Yanger

(266758030) Q SYNCH-12 Does Workshop work with WebLogic Server 6.1?

(266758030) Q<SYNCH-12> Does Workshop work with WebLogic Server 6.1? (asked by Noel
Fuentes)
A<SYNCH-12> (by Adam Fitzgerald): No, Web Services in WebLogic Server 6.1 are different
from those available in WebLogic Server 7.0. WebLogic Workshop is a WLS 7.0 tool.

Rick,
You may want to look at the Alteon and F5 configuration we have on edocs.
Take a look at the following URLs for a possible solution
http://edocs.bea.com/wls/docs61/cluster/alteon.html#591902
http://edocs.bea.com/wls/docs61/cluster/bigip.html#591902
Chuck Nelson
DRE
BEA Technical Support

Error while deploying application with WebLogic server

Hi,
I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
"There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
Plz help me.
Thx

I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
Cheers!

How to know report server name in oracle forms and reports with weblogic server 10.3.5

Hello Experts, I am new in oracle forms and reports.I have installed Oracle forms 11g with weblogic server 10.3.5 at windows 7.Forms and reports are working well.But I want to call a report from an oracle form button press trigger. For This I need to know the my report server name which i dont know.Please tell me how can I know my report server name.

I want to call a report from an oracle form button press trigger. For This I need to know the my report server name
You can find the name of the standalone reports server in $ORACLE_INSTANCE/config/ReportsServerComponent.
Or you can use Fusion Middleware Control Console, normally at http://<machine name>:7001/em

ClassCircularityError in JAAS Authorization with Weblogic Server 10.3

We are implementing JAAS authorization in which roles and policies are stored in a custom JAAS policy file and users are stored in the embedded LDAP server provided by Weblogic. We are facing problem is authorizing users using the custom policy created.
We have implemented the JAAS authentication service with weblogic server 10g R3 and user's information stored in embedded LDAP server provided WLS. Given below are the details of implementation for JAAS Authorization:
Following are the custom classes created:
1. Custom Principal Class
public class Principal implements java.security.Principal, java.io.Serializable {
private String name;
public Principal() {
name = "";
public Principal(String newName) {
name = newName;
public boolean equals(Object o) {
if (o == null)
return false;
if (this == o)
return true;
if (o instanceof Principal) {
if (((Principal) o).getName().equals(name))
return true;
else
return false;
else
return false;
public int hashCode() {
return name.hashCode();
public String toString() {
return name;
public String getName() {
return name;
2. Custom Permission Class
public class ActionPermission extends Permission {
     public ActionPermission(String name) {
          super(name);
     @Override
     public boolean equals(Object obj) {
          if ((obj instanceof ActionPermission)
                    && ((ActionPermission) obj).getName().equals(this.getName())) {
               return true;
          } else {
               return false;
     @Override
     public String getActions() {
          return "";
     @Override
     public int hashCode() {
          return this.getName().hashCode();
     @Override
     public boolean implies(Permission permission) {
          if (!(permission instanceof ActionPermission)) {
               return false;
          String thisName = this.getName();
          String permName = permission.getName();
          if (this.getName().equals("*")) {
               return true;
          if (thisName.endsWith("*")
                    && permName.startsWith(thisName.substring(0, thisName
                              .lastIndexOf("*")))) {
               return true;
          if (thisName.equals(permName)) {
               return true;
          return false;
Following are the configuration changes:
1. Added custom policy to weblogic.policy.
grant Principal com.scotia.security.authorization.Principal "test" <User defined in the embedded LDAP server of WLS>{
permission com.scotia.security.authorization.permission.ActionPermission "viewScreen";
2. Set the java security manager in startWeblogic.cmd file.
%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.manager -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %PROXY_SETTINGS% %SERVER_CLASS%
3. Set Realm "Security Model" to "Custom Roles and Policies".
Right now we are facing the given below exception:
java.lang.ClassCircularityError: com/scotia/security/authorization/THORPrincipal
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:247)
     at sun.security.provider.PolicyFile.addPermissions(PolicyFile.java:1381)
     at sun.security.provider.PolicyFile.getPermissions(PolicyFile.java:1268)
     at sun.security.provider.PolicyFile.getPermissions(PolicyFile.java:1231)
     at sun.security.provider.PolicyFile.getPermissions(PolicyFile.java:1167)
     at sun.security.provider.PolicyFile.implies(PolicyFile.java:1122)
     at weblogic.security.service.WLSPolicy.implies(Unknown Source)
     at java.security.ProtectionDomain.implies(ProtectionDomain.java:213)
     at java.security.AccessControlContext.checkPermission(AccessControlContext.java:301)
     at java.security.AccessController.checkPermission(AccessController.java:546)
     at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
     at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
     at java.io.File.exists(File.java:731)
     at weblogic.utils.classloaders.DirectoryClassFinder.getSource(DirectoryClassFinder.java:36)
Please help if anyone has some clue regarding this exception. We tried checking the jdk version used by eclipse and weblogic and found it to be same.

1. Custom Principal Class
public class Principal implements java.security.Principal, java.io.Serializable {Rename it. You are asking for trouble naming a class after an interface it implements.
java.lang.ClassCircularityError: com/scotia/security/authorization/THORPrincipalWhat's that class? You haven't shown us.

When will apple release an update with bug fixes for ios 6?

when will apple release an update with bug fixes for ios 6?

When indeed. I purchased iPhone 5 64gb and have so far experienced the following issues/Bugs
1. Flash on camera out of sync
2. Cannot connect to some WIFI Bluetooth drvices
3. Missing Album Artwork on iTunes album view
4. Buggy and confused maps/satnav
5. iMessage comes and goes
6. Battery Life *****

HTTP Tunneling and Load Balancing with Weblogic Server 6.1

We use T3 for Java client to application server communication (Weblogic Server
6.1) and keep the session open for the life of the client. We many customers
using this with load balancers and all works fine. We have just started to use
BEA's HTTP tunneling and I have a question concerning how this will work with
load balancers. Since the single T3 connection has been replaced with a series
of stateless HTTP connections, does the BEA tunneling code put session information
in the HTTP header? If so, what information does it place in the header. If
it does we should be able to use that to make sure that the load balancer always
sends HTTP requests with that session to the same application server.
Thanks!
Rick

Rick,
You may want to look at the Alteon and F5 configuration we have on edocs.
Take a look at the following URLs for a possible solution
http://edocs.bea.com/wls/docs61/cluster/alteon.html#591902
http://edocs.bea.com/wls/docs61/cluster/bigip.html#591902
Chuck Nelson
DRE
BEA Technical Support

Warning BEA-2156203 JEE5 Version in Weblogic Server 10.3.6

Hi, when I start the Weblogic Admin Server for studio domain, there appears the below warning:
<27-nov-2013 13H34' CET> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\OEID_Installers\endecastudio\endeca-portal-weblogic-3.1.14220.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
<27-nov-2013 13H34' CET> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in
C:\Oracle\Middleware\user_projects\domains\endeca_studio_domain\servers\AdminServer\tmp\_WL_user\endeca-portal-weblogic-3\diq5s7/METAINF/application.xml.
A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
Wls: 10.3.6
JEE: 7u40
Windows x64
I know that this same error appears when the JEE version is JEE6 and that is a bug which is fixed by the patch:
11720907: SU Patch [2IE6]: <A VERSION ATTRIBUTE WAS NOT FOUND IN ELEMENT PERSISTENCE ..>
Exist any patch for JEE7? or this warning is solved by other way?

Hi Julia,
I'm using java 7 upgrade 40.
It is better if I uninstall java version 7 and install version 6 upgrade 43?
I supposed that it was better install the lastest java version, but if you tell me that is better use version 6, I will do it
Mercy

How to start developing forms with weblogic server???

I am a beginner. I saw someone working on developer 6i and I love the ease so I come to oracle. BUT now I find this weblogic server for desktop applications (forms) too.
1. Please recommend me a book for developing desktop applications in weblogic server.
2. Is it possible to use Mysql as database while developing forms in weblogic server?
Many thanks

I am a beginner. I saw someone working on developer 6i and I love the ease so I come to oracle. BUT now I find this weblogic server for desktop applications (forms) too.You have to keep in mind that Oracle Developer Suite 6i (Forms/Reports) is over 10 years old and was primarily a Client/Server development environment. Yes, a Forms 6i application could be deployed to the web, but infrastruction has changed many times in the 10+ years since Forms 6i was introduced.
1. Please recommend me a book for developing desktop applications in weblogic server.Are you talking about an Oracle Forms application deployed through the WebLogic application server? If so, take a look at Developing Oracle Forms Applications or Oracle9i Developer: Developing Web Applications with Forms Builder. These are older books, but they will give you the basics of Oracle Forms development. Once you have the basics of Forms Development, then you can refer to the product documentation for specifics on the particular version of Forms you are using:
Oracle Forms 10g Online Book - Contents or <a href="http://download.oracle.com/docs/cd/E12839_01/index.htm>Oracle Fusion Middleware Documenation LIbrary</a> and select the Portal, Forms, Reports and Discoverer option.
{quote2. Is it possible to use Mysql as database while developing forms in weblogic server?{quote
You can use MySQL with your web app only if you are not using Oracle Forms! Oracle Forms will only communicate with an Oracle Database. There are methods available to access data from non-Oracle database, but they involved linking your Oracle Database to the non-Oracle database and accessing the data through the Oracle Database.
Hope this helps,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

How write rmi-iiop over ssl with weblogic server 6.1 - No server found

//New
Hello,
I have written an appication like this:
- An EJB server running on Weblogic server 6.1
(named: BankServerHome)
-A java client calling the BankServer.
Platform: windows 2000 - jdk1.3
Now I want to secure the communication with SSL protocol.
I have done this:
-generate a key peer with weblogic service named certificate.
-send the CSR to a CA and place the answer into the weblogic
server certificate directory.
-update path for ServerCertificateChainFileName,
ServerCertificateFileName, ServerKeyFileName into config.xml.
-launch weblogicServer
     -> server certificate is recognized
     -> listening port 7001 and 7002.
(-stop weblogicServer!)
At now, all is all right, errors come hereafter:
Then I follow the guideline "Programming weblogic Security" (version of 30/07/2001).
"To use RMI over IIOP over SSL with a Java client, do the following:
2. Extend the java.rmi.server.RMISocketFactory class to handle SSL socket
connections. Be sure to specify the port on which WebLogic Server listens for
SSL connections. For an example of a class that extends the
java.rmi.server.RMISocketFactory class, see Listing 4-22.
3. Run the ejbc compiler with the -d option.
4. Add your extension of the java.rmi.server.RMISocketFactory class to the
CLASSPATH of the Java client.
5. Use the following command options when starting the Java client:
-xbootclasspath/a:%CLASSPATH%
-Dorg.omg.CORBA.ORBSocketFactoryClass=implementation of java.rmi.server.RMISocketFactory
-Dssl.certs=directory location of digital certificate for Java client
-Dssl.key=directory location of private key for Java client"
At step 3. I found into documentation that -d is linked to a directory name.
When I run ejbc with this option -d I have the message:
"ERROR: You must specify an output directory or jar with the -d option to weblogic.ejbc."
% So what option can I use to run ejbc for secure usage?
At step 5. Whatever I write for -Dorg.omg.CORBA.ORBSocketFactoryClass,
this pointed class is not instanciated.
Then I can not create a socket with my client.
The folowing exception is raised:
javax.naming.CommunicationException [Root exception is java.net.ConnectException:
No server found at T3S://localhost:7002]
So, my questions are:
% Why -Dorg.omg.CORBA.ORBSocketFactoryClass must be known by the client and not
the server?
My java client part, managing connection is:
-------------------BEGIN OF CONNECTION MANAGER-------------------
Properties env = new Properties ();
// Shouldn't have to do this, but for now you must
if ( factory.equals ("weblogic.jndi.WLInitialContextFactory") ) {
env.put ("java.naming.provider.url", "t3s://localhost:7002");
InitialContext context = new InitialContext (env);
BankSessionServerHome bssh = (BankServerHome) context.lookup("BankServerHome");
BankServer = bssh.create();
-------------------END OF CONNECTION MANAGER-------------------
I have also try
env.put ("java.naming.provider.url", "corbaloc:iiop://localhost:7002");
but it throws the following error
javax.naming.InvalidNameException: url does not conatin !!!
% What is the code for the java client allowing connection with the ejb?
% And better, can I have a sample example for rmi-iiop over ssl?
(...wlserver6.1\samples\examples\iiop\ejb\stateless\rmiclient\client.java do not
speak ssl!)
Any help will be appreciate from you...
Best Regards.
Oliver

"oliver" <[email protected]> writes:
The SSL support is poorly doc'd right now. We have fixed this and
updated the way you do things in SP2. Please either wait for SP2 or
contact support.
andy
I have written an appication like this:
- An EJB server running on Weblogic server 6.1
(named: BankServerHome)
-A java client calling the BankServer.
Platform: windows 2000 - jdk1.3
Now I want to secure the communication with SSL protocol.
I have done this:
-generate a key peer with weblogic service named certificate.
-send the CSR to a CA and place the answer into the weblogic
server certificate directory.
-update path for ServerCertificateChainFileName,
ServerCertificateFileName, ServerKeyFileName into config.xml.
-launch weblogicServer
     -> server certificate is recognized
     -> listening port 7001 and 7002.
(-stop weblogicServer!)
At now, all is all right, errors come hereafter:
Then I follow the guideline "Programming weblogic Security" (version of 30/07/2001).
"To use RMI over IIOP over SSL with a Java client, do the following:
2. Extend the java.rmi.server.RMISocketFactory class to handle SSL socket
connections. Be sure to specify the port on which WebLogic Server listens for
SSL connections. For an example of a class that extends the
java.rmi.server.RMISocketFactory class, see Listing 4-22.
3. Run the ejbc compiler with the -d option.
4. Add your extension of the java.rmi.server.RMISocketFactory class to the
CLASSPATH of the Java client.
5. Use the following command options when starting the Java client:
-xbootclasspath/a:%CLASSPATH%
-Dorg.omg.CORBA.ORBSocketFactoryClass=implementation of java.rmi.server.RMISocketFactory
-Dssl.certs=directory location of digital certificate for Java client
-Dssl.key=directory location of private key for Java client"
At step 3. I found into documentation that -d is linked to a directory name.
When I run ejbc with this option -d I have the message:
"ERROR: You must specify an output directory or jar with the -d option to weblogic.ejbc."
% So what option can I use to run ejbc for secure usage?
At step 5. Whatever I write for -Dorg.omg.CORBA.ORBSocketFactoryClass,
this pointed class is not instanciated.
Then I can not create a socket with my client.
The folowing exception is raised:
javax.naming.CommunicationException [Root exception is java.net.ConnectException:
No server found at T3S://localhost:7002]
So, my questions are:
% Why -Dorg.omg.CORBA.ORBSocketFactoryClass must be known by the client and not
the server?
My java client part, managing connection is:
-------------------BEGIN OF CONNECTION MANAGER-------------------
Properties env = new Properties ();
// Shouldn't have to do this, but for now you must
if ( factory.equals ("weblogic.jndi.WLInitialContextFactory") ) {
env.put ("java.naming.provider.url", "t3s://localhost:7002");
InitialContext context = new InitialContext (env);
BankSessionServerHome bssh = (BankServerHome) context.lookup("BankServerHome");
BankServer = bssh.create();
-------------------END OF CONNECTION MANAGER-------------------
I have also try
env.put ("java.naming.provider.url", "corbaloc:iiop://localhost:7002");
but it throws the following error
javax.naming.InvalidNameException: url does not conatin !!!
% What is the code for the java client allowing connection with the ejb?
% And better, can I have a sample example for rmi-iiop over ssl?
(...wlserver6.1\samples\examples\iiop\ejb\stateless\rmiclient\client.java do not
speak ssl!)
Any help will be appreciate from you...
Best Regards.
Oliver

Will BEA release an IDE with WebLogic Server 10 in march?

Similar Messages

Maybe you are looking for