Logging with Weblogic 10.3

Hello,
I am wondering how to manipulate the server logging with WebLogic 10.3. I get an error while deploying and I need further information for the packages concerning the named queries and for that I need to turn up the log level for this packages. Do I need to manipulate the config/logging.xml or which file?
Thank you

If you are deploying via the WebLogic admin console, here's the reference to configure logging level:
Administration Console Online Help - [View and configure logs|http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/logging/ConfigureAndViewLogs.html]
If deploying from command line, try including the -debug flag?
(weblogic.Deployer Command-Line Reference - [Common Arguments|http://download.oracle.com/docs/cd/E12840_01/wls/docs103/deployment/wldeployer.html#wp1010461])

Similar Messages

  • Using Java Logging with WebLogic 8.1

    Hello,
    I am having problems getting custom Handlers to load using the Java 1.4 Logging
    API. Apparently, the custom Handlers are loaded using the System classpath, not
    the applications classpath. This is not a viable option for us, does anyone know
    of a workaround for this?
    Thank you,
    Josh

    Hello Staffan,
    I've just sent to you the code source for this class. By the way I didn't try changing the swing JVM.
    Dom
    Hi,
    This looks like a bug to me. Does it matter which JVM
    you use for the swing application?
    To be able to find out more about the problem it
    would be great if we could look at the class files
    for
    com.dexia.sofaxis.prestations.business.TypeElementMate
    riel and all it's superclasses and interfaces. Please
    contact me offline at sta_larsen(at)hotmail (yes, I
    work for BEA, but I don't like spam...).
    Regards,
    /Staffan

  • Logging to weblogic.log

     

    hi
    i need couple of clarifications with regard to implementation of logging with
    weblogic.
    a) Is logging implemented using JMS? ( Is logging asynchronous?)
    b) I am wondering if i can use logging api into some helper classes that wouldn't
    be run in weblogic server. If weblogic server is a pre-requisite, then i will
    not be able to use this logging api in these classes.
    Thanks
    Rob Woollen <[email protected]> wrote:
    From server-side code (ie servlets or EJB). do
    LogServiceDef log = T3Services.getT3Services().log();
    to get the log, and then you can use log.inform(), log.debug, or
    log.error as appropriate.
    See
    http://www.weblogic.com/docs45/classdocs/weblogic.common.LogServicesDef.html
    -- Rob
    Rob Woollen
    Software Engineer
    BEA WebLogic
    [email protected]
    Vinny Carpenter wrote:
    Hi there. I have a cluster of WebLogic 4.5.1 servers running under
    Solaris 2.6. My application consists of two EJB's and a couple of
    servlets as front end. As part of the application logging process,I
    output certain text using System.out.println and System.err.printlnthat
    are typically displayed on the console.
    How can I redirect those messages to the machine's weblogic.log file??
    Is there a logging mechanism that will allow me to do that?? thanks
    --Vinny

  • Integration of Commons Logging framework with Weblogic

    Hi,
    We are trying to use Apache commons logging framework and trying to publish log mesages in Weblogic so that messages can be seen through console and all the Logging configurations can be managed from Admin console. I tried using the below steps:
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/logging/config_logs.html#using_commons
    But these does not seems to be working for User defined handlers. I am able to see the logs in the default odl-handler file but not able to log the messages through the handlers defined by me.
    Can anyone help me on this.
    Regards,
    Anuj

    Hi,
    We are able to see reports through Workspace. We are facing problem after
    integrating Hyperion Interactive Reporting with Weblogic Portal. we are able to see the sections like Query,Report,Results but we are not able to see the content after selecting any one of the section mentioned above.
    System Configuration:
    Hyperion Interactive Reporting 9.3.1
    App Server: Weblogic server 9.2
    Web Server: Apache 2.0.52
    Database: Oracle 9.0.1.
    Operating System: Windows 2003 with SP1
    Browser: I.E 6.0
    With Workspace everything is working fine. After Integration we are facing problem.
    Regards,
    S.Suresh.

  • 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.

  • EJB 3.0 MDB deployment issue with weblogic 10.0

    Hi there,
    I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
    After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
    weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
    Unable to deploy EJB: MessageBean from Message.jar:
    [EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         Truncated. see log file for complete stacktrace
    [EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
         at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
         Truncated. see log file for complete stacktrace
    >
    Any help really appreciated. It's too urgent.
    Thanks in advance,
    Piyush

    here is the code for my bean.
    package com.ups;
    import java.util.logging.Logger;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.EJBException;
    import javax.ejb.MessageDriven;
    import javax.ejb.MessageDrivenContext;
    import javax.jms.JMSException;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import javax.jms.TextMessage;
    * Message-Driven Bean implementation class for: MessageBean
    @MessageDriven(
              activationConfig = { @ActivationConfigProperty(
                        propertyName = "destinationType", propertyValue = "javax.jms.Queue"
    public class MessageBean implements MessageListener {
         private MessageDrivenContext mdc;
    * Default constructor.
    public MessageBean() {
    // TODO Auto-generated constructor stub
    * @see MessageListener#onMessage(Message)
    public void onMessage(Message message) {
         TextMessage tmsg = null;
    try {
    tmsg = (TextMessage) message;
    System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
    System.out.println ("The onMessage() is called");
    } catch (JMSException e) {
    e.printStackTrace( );
    mdc.setRollbackOnly( );
    catch (Throwable th) {
    th.printStackTrace();
    public void ejbRemove( )throws EJBException{
         System.out.println("ejbRemove() is executed >>>>>>>");
    I have configured my JMS Distributed queue in the Weblogic.
    If possible please provide more details so that I can get rid of this error as soon as possible.
    Thanks for reply.
    Piyush

  • Security violation exception with Weblogic cluster installation on OIm 9.1

    Hi,
    I have OIM9.1 installed on weblogic 8.1 SP4 in clustered environment, which more often than not seems to work fine. But some time I get following exception on server console/log file which causes certain provisioning task to be rejected...
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: javax.ejb.AccessLocalException: [EJB:010160]Security Violation: User: 'xelsysad
    m' has insufficient permission to access EJB: type=<ejb>, application=Xellerate, module=xl
    DataObjectBeans.jar, ejb=tcFormInstanceOperations, method=create, methodInterface=LocalHom
    e, signature={}.
    at weblogic.ejb20.internal.MethodDescriptor.checkMethodPermissionsLocal(MethodDesc
    riptor.java:486)
    at weblogic.ejb20.internal.StatelessEJBLocalHome.create(StatelessEJBLocalHome.java
    :80)
    at com.thortech.xl.ejb.beans.tcFormInstanceOperations_2j82mm_LocalHomeImpl.create(
    tcFormInstanceOperations_2j82mm_LocalHomeImpl.java:93)
    ... 126 more
    ERROR,19 Dec 2008 14:20:03,752,[XELLERATE.APIS],Class/Method: tcBaseUtilityClient/getLocal
    Interface encounter some problems: {1}
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.in
    Problem is, I get this exception only 4 out of 6 times (when it is least expected). I have googled, and tried all possible means but have't been able to resolve it. One more thing I am sure of is, it only comes with Weblogic installation not with Jboss. So there should be some configuration issue with weblogic installation.
    Any suggestions would be useful...

    No Response???
    Where are the good guys??

  • 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 use commons.logging in weblogic (8.1)?

    Greetings,
    I'm trying to use commons.logging framework to manage the logs of my
    application. With Weblogic I will use an implementation that works with
    weblogic.logging package but with other J2EE products I'll use another
    native log implementations or frameworks (for instance, for jboss I will
    use log4j).
    1) I created a class WeblogicLogger which implements the Log interface::
    public final class WeblogicLogger implements Log {
    I packaged this class in a jar file with a properties file,
    commons-logging.properties, which has the property setting my class
    below has the default logger:
    org.apache.commons.logging.Log=pt.ptinovacao.weblogic.logging.WeblogicLogger
    2) My sample code has the following code:
    import org.apache.commons.logging.Log;
    import org.apache.commons.logging.LogFactory;
    private static final Log log = LogFactory.getLog(
    LogTimeStartHandler.class.getName());
    something(){
    log.info(this.getClass()+" test log");
    3) I added the commons-logging jars and my jar with my custom wrapper
    weblogic logger in ${WL_HOME}/common/bin/commEnv.sh:
    WEBLOGIC_CLASSPATH=
    (...)${CLASSPATHSEP}${WL_HOME}/server/lib/weblogiclogger.jar${CLASSPATHSEP}${WL_HOME}/server/lib/commons-logging-api.jar${CLASSPATHSEP}${WL_HOME}/server/lib/commons-logging.jar
    However, my loggings still not appear in my weblogic server. Did I miss
    something?
    thanks,
    Pedro Salazar

    Did you manage to get this working?
    If yes ... what did you do?
    I am having the same problem implementing commons-logging with log4j

  • Application logging in weblogic 7.0

    Just wanted to put a question out there as to how everyone else is doing application
    logging. I want to provide a standardized error level logging capability to my
    application developers, and I DO NOT want to use the weblogic logging as it appears
    that it only can write to the server log - I worry about apps filling this filespace.
    I tried ServletContext logging, and contrary to other implementations, it also
    goes to the server log. According to the specs, it should go to a file that matches
    up with the context name.
    Is log4j the way to go?

    Thanks for the feedback, anyone else that ones to chime in on log4j shoot.
    Were looking now at how to leverage/intergate/avaliablate log4j within WLS.
    Cheers
    mbg
    "Jon Mountjoy" <[email protected]> wrote in message
    news:[email protected]..
    Hi Mark,
    I am curious about how log4j didn't work in a cluster, and what about
    weblogic's logging was superior to log4j?Well, I didn't exactly say that it didn't work in a cluster ;-) I
    implied that it didn't work beautifully in a cluster :-)
    These are the advantages that I see to WebLogic's logging:
    a) Distributed logging is a no-brainer
    b) Integration with WebLogic's own notifications
    WL:If you want to log in a cluster, then using WebLogic's logging is
    simple and effective - it all works out of the box. You get a nice
    domain log and all the underlying distribution is done for you.
    Log4J: If you want to log in a cluster using Log4J, then as far as I
    know you have to do some work (not much, just some) - which you don't
    have to do using WL. AFAIK, to get the same functionality you have to
    use SocketAppenders, and then have your administration server (or
    whichever server you want to hold the domain log) run a socketnode.
    Advantages: You have lots of nifty log4j features, more portable.
    Disadvantages: More setup, more administration, no integration with WL
    notifications.
    To me the greatest advantage is the integration with WebLogic's own
    notifications. Logging is not just about debugging info, but also
    manageability. I want to see all important information consolidated.
    Of course, I can write code to get this - perhaps writinng a
    notification listener for WL messages and converting them to Log4J
    messages. Hmm, perhaps if WL let me write my own 'appender' instead of
    their default 'send a JMX event' I could get nice clean integration.
    The nice thing about Log4J is that it's feature set is far richer, and
    its more 'portable' if you are willing to do the integration work with
    each app server.
    Regards,
    Jon

  • How to configur log4j logging for weblogic 10.1

    Hi,
    I am tried to set log4j logging for my application running in weblogic 10.1. I set a log4j.properties file and loaded the properties by a servlet. Where its load the properties files and configure it by PropertyConfigurator.
    The same logic has worked out in websphere. But in weblogic, it is not working. I set the server logging and domain logging to Log4j in Admin console. Now it is writing all the log statements.
    If i write a property for a package to Error level and root level is Debug. Its not working, all debug statements are getting written.
    Can you please tell me the steps to configure log4j logging in weblogic 10.1.
    Thanks & Regards,
    Nasrin.N

    Did you manage to get this working?
    If yes ... what did you do?
    I am having the same problem implementing commons-logging with log4j

  • Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

    Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
    A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
    Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
    * Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
    * Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
    The guide can be downloaded here:
    http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
    To help internet searches locate this document, the table of contents is reproduced below:
    Introduction
    1.1. Prerequisites...................................................................... 8
    1.2. Applicable Versions............................................................ 8
    1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
    1.4. JSF Portlet Support Roadmap ........................................... 9
    1.5. Whitepaper Structure ....................................................... 10
    1.6. Look Before You Leap ..................................................... 10
    1.7. For More Information........................................................ 10
    Part 1: Converting JSF Applications into Portlets
    2. IDE Support for JSF Portlets Chapter ...................................... 12
    2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
    2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
    3. Introduction to JSF Portlets Chapter ........................................ 18
    3.1. Creating Your First JSF Portlet......................................... 18
    3.2. Essentials of JSF Portlet Views........................................ 21
    3.3. WebLogic Portal Artifacts................................................. 22
    4. Configuring JSF within WebLogic Portal Chapter..................... 24
    4.1. JSF Library Modules in WebLogic Server ........................ 24
    4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
    4.3. JSF Configuration Settings............................................... 27
    4.4. Configuring JSF 1.2 ......................................................... 29
    4.5. Building an Unsupported JSF Implementation Library Module 31
    4.6. Faces Configuration is Web Application Scoped.............. 31
    5. Navigation within a JSF Portlet Chapter................................... 33
    5.1. Navigating within a Portlet with the JSF Controller ........... 33
    5.2. Redirects.......................................................................... 34
    6. Namespacing Chapter ............................................................. 35
    6.1. Namespacing Managed Bean Names.............................. 35
    6.2. Client ID Namespacing with the View and Subview Components 35
    6.3. Client ID Namespacing with the WLP NamingContainer .. 36
    7. Logging, Iterative Development, and Debugging Chapter ........ 39
    7.1. Logging............................................................................ 39
    7.2. Iterative Development ...................................................... 39
    7.3. Debugging ....................................................................... 40
    8. Custom JavaScript Chapter ..................................................... 42
    8.1. DOM Manipulation within a JSF ....................................... 42
    8.2. Form Validation within a JSF Portlet ................................ 45
    9. Preparing JSF Portlets for Production Chapter ........................ 46
    9.1. Configuration.................................................................... 46
    9.2. Performance and Scalability............................................. 47
    9.3. Security............................................................................ 49
    9.4. Localization...................................................................... 50
    Part 2: Interacting with the Portal Environment
    10. Native Bridge Architecture Chapter ...................................... 54
    10.1. Container Architecture Overview.................................. 54
    10.2. Container Architecture.................................................. 54
    10.3. Container Interactions .................................................. 55
    11. Interportlet Communication Chapter .................................... 56
    11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
    11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
    11.3. Notifications ................................................................. 60
    11.4. Comparison of the IPC Approaches ............................. 60
    12. Scopes Chapter ................................................................... 62
    12.1. Conceptual Scopes for Standard JSF Applications ...... 62
    12.2. Conceptual Scopes for Portal Applications................... 63
    12.3. Implementation Patterns for Portal Scopes .................. 63
    13. State Sharing Patterns Chapter ........................................... 66
    13.1. State Sharing Concepts ............................................... 66
    13.2. HttpSession Versus HttpServletRequest ...................... 66
    13.3. Base Code for HttpSession Patterns ............................ 67
    13.4. Single Portlet Pattern ................................................... 68
    13.5. Multiple Portlet Patterns ............................................... 69
    14. Rendering Lifecycles Chapter .............................................. 77
    14.1. WLP and JSF Lifecycles .............................................. 77
    14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
    14.3. Accessing WLP Context Objects from JSF Managed Beans 78
    15. Portal Navigation Chapter .................................................... 80
    15.1. Programmatically Constructing JSF Portlet URLs ........ 80
    15.2. Changing the Active Portal Page.................................. 80
    15.3. Redirects within a Portal............................................... 83
    16. Ajax Enablement Chapter .................................................... 85
    16.1. Ajax in JSF Portlets...................................................... 85
    16.2. Partial Page Rendering Pattern.................................... 85
    16.3. Stateless API Request Pattern ..................................... 86
    16.4. Portlet Aware API Request Pattern .............................. 87
    16.5. Controlling the WLP Ajax Framework........................... 91
    17. Additional WLP Features Chapter........................................ 93
    17.2. Portlet Container Features ........................................... 93
    17.3. Portal Container Features ............................................ 98
    18. Example: Implementing a Login Portlet Chapter .................. 99
    18.1. Login Portlet Motivation................................................ 99
    18.2. Login Portlet Design..................................................... 99
    18.3. Login Portlet Implementation...................................... 101
    Part 3: Integrating Third Party Libraries
    19. Integration Overview Chapter............................................. 111
    19.1. Types of Libraries....................................................... 111
    19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
    20. Using the Facelets View Technology Chapter.................... 113
    20.1. Introduction to Facelets .............................................. 113
    20.2. Configuring Facelets Support ..................................... 113
    21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
    21.1. What is Apache MyFaces Tomahawk? ...................... 115
    21.2. Support for Tomahawk in WLP................................... 115
    21.3. Tomahawk Component List........................................ 116
    21.4. Installing and Configuring Tomahawk......................... 119
    21.5. Resolving the Duplicate ID Issue................................ 120
    21.6. Referring to Resources .............................................. 120
    21.7. forceId Attribute.......................................................... 124
    21.8. File Upload................................................................. 125
    22. Using the Apache Beehive Navigation Controller Chapter . 126
    22.1. Apache Beehive Page Flow ....................................... 126
    22.2. JSF and Page Flows .................................................. 126
    22.3. Configuring the JSF Integration with Page Flows ....... 127
    Appendices
    23. Appendix 1: Consolidated List of Best Practices ................ 130
    24. Appendix 2: Known Issues and Workarounds.................... 132
    24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
    24.2. CR342124: IllegalStateException due to duplicate client-id 132
    24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
    24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
    24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
    25. Appendix 3: The JSFPortletHelper Class ........................... 135
    26. Appendix 4: The CleanupPhaseListener Class .................. 147

    Hi Peter!
    First, I wish to thank you for the great work.
    We followed your whitepaper and managed to deploy a JSF portlet on WLS.
    But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
    An error occurred while trying to refresh the provider. (WWC-43190)
    An error occurred during the call to the WSRP Provider:
    java.rmi.RemoteException: serialization error: serialization error:
    unexpected null value for literal data; nested exception is:
    serialization error: serialization error: unexpected null value for literal data
    com.sun.xml.rpc.encoding.SerializationException: serialization error:
    serialization error: unexpected null value for literal data
    com.sun.xml.rpc.encoding.SerializationException: serialization error:
    unexpected null value for literal data
    Java stack trace from root exception:
    unexpected null value for literal data
    at
    oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
    at
    com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
    at
    com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
    at
    oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
    at
    com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
    at
    com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
    at
    com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
    at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
    at
    oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
    at
    oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
    Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
    Thank you and best regards,
    PaKo

  • Problem in developing jasper report in BEA workspace studio version 1.1 with weblogic server 10.0

    Hi! all,
    Myself developing a jasperReport in BEA workspace studio 1.1 and always getting the below mentioned exception, though i have run the same code in NetBeans successfully with the same jar file.
    Even i have added weblogic.jar, wllog4j.jar, classes12.jar, commons-beanutils-1.8.0.jar, commons-collections-2.1.1.jar, commons-digester-1.7.jar, commons-javaflow-20060411.jar, commons-logging-1.0.4.jar, iText-2.1.7.jar, jasperreports-3.7.1.jar, jasperreports.jar, jasper-jdt-6.0.13.jar, jasper-compiler-jdt.jar, jasper-compiler.jar, jasper-runtime.jar, jasperreports-3.5.1.jar, jasperreports-2.0.5.jar in the WEB-INF/lib directory as well as build path. please help me.Thanks in advance.
    ==============================================================
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/logging/WLLogRecord : weblogic/logging/LogEntry
         at java.lang.ClassLoader.findBootstrapClass(Native Method)
         at java.lang.ClassLoader.findBootstrapClass0(ClassLoader.java:891)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:301)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
         at weblogic.logging.commons.LogFactoryImpl.getInstance(LogFactoryImpl.java:21)
         at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
         at org.apache.commons.digester.Digester.<init>(Digester.java:304)
         at net.sf.jasperreports.engine.xml.JRXmlDigester.<init>(JRXmlDigester.java:62)
         at net.sf.jasperreports.engine.xml.JRXmlDigesterFactory.createDigester(JRXmlDigesterFactory.java:980)
         at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:203)
         at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:168)
         at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:152)
         at net.sf.jasperreports.engine.JasperCompileManager.compileReport(JasperCompileManager.java:150)
         at com.generateJasperReport.test.GasperReportNew.main(GasperReportNew.java:38)
    ==============================================================================
    My Code is..........................
    ============================
    package com.generateJasperReport.test;
    import java.sql.Connection;
    import java.sql.DriverManager;
    import java.sql.ResultSet;
    import java.util.HashMap;
    import java.util.Map;
    //import weblogic.logging.LogEntry;
    import net.sf.jasperreports.engine.JRException;
    import net.sf.jasperreports.engine.JRResultSetDataSource;
    import net.sf.jasperreports.engine.JasperCompileManager;
    import net.sf.jasperreports.engine.JasperExportManager;
    import net.sf.jasperreports.engine.JasperFillManager;
    import net.sf.jasperreports.engine.JasperPrint;
    import net.sf.jasperreports.engine.JasperReport;
    import net.sf.jasperreports.view.JasperViewer;
    public class GenerateJasperReport {
         static JRResultSetDataSource jrds = null;
         static ResultSet rs = null;
         public static Connection connectDB() {
              Connection jdbcConnection = null;
              try {
                   Class.forName("oracle.jdbc.driver.OracleDriver");
                   jdbcConnection = DriverManager.getConnection(
                             "jdbc:oracle:thin:@192.161.5.35:1521:abc",
                             "xyz", "pqr");
              } catch (Exception ex) {
                   String connectMsg = "Could not connect to the database: "
                             + ex.getMessage() + " " + ex.getLocalizedMessage();
                   System.out.println(connectMsg);
              return jdbcConnection;
         public static void main(String[] args) throws JRException {
              Connection con = connectDB();
              JasperReport jasperReport=null;
              System.out.println("666666666666666666");
              String reportSource = "E:\\Pintu\\Project\\Bea Project\\workspace\\GenerateJasperReport\\src\\com\\generateJasperReport\\jrxmlFile\\JasperReportGeneration.jrxml";
              String reportDest = "E:\\Pintu\\Project\\Bea Project\\workspace\\GenerateJasperReport\\src\\com\\generateJasperReport\\output\\JasperReportGeneration.pdf";
              System.out.println("555555555555555");
              Map <String,String>parammap = new HashMap<String,String>();
              parammap.put("ReportTitle", "PDF JasperReport");
              System.out.println("444444444444444");
              try {
                   try{
                        jasperReport = JasperCompileManager
                             .compileReport(reportSource);
                   }catch(JRException e){e.printStackTrace();}
                   System.out.println("ssssssssssssss");
                   JasperPrint jasperPrint = JasperFillManager.fillReport(
                             jasperReport, parammap, con);
                   System.out.println("vvvvvvvvvvvvvvv");
                   JasperExportManager.exportReportToPdfFile(jasperPrint, reportDest);
                   System.out.println("kkkkkkkkkkkkkkkkkkk");
                   JasperViewer.viewReport(jasperPrint);
                   System.out.println("gfrfrrrertfewrw");
              } catch (Exception ex) {
                   ex.printStackTrace();
    ===========================================================

    Thanks for the information. It makes so much more sense to do the configuration from within PFR instead of WLS but the engineer insisted I could just do everything from within the WLS config wizard. I'm very relieved that someone has had success with this.
    Am I supposed to do the configuration wizard in WLS before doing the Configure Classic Interface from PFR?
    Since we're only going to be using the PC for the developer, I wasn't sure how much of the Web Logic Server needed to be configured.
    The Oracle engineer said to choose 'Oracle Ent. Mgr' and 'Oracle Classic 11g' from the WLS Config Wizard which I did - but now I have a choice on the 'Optional Configuration' page to choose 'Administration Server', 'Managed Servers', 'Deployments and Services' and 'RDMBS Security Store'. I'm not sure if I'm supposed to choose any of these. I want to be able to talk to the Solaris server that is going to be my application server via WLS and I'm not sure if I need any of these.
    In your environment, are you developing 11g forms on a PC but hosting on another platform? I have a Windows 7 64 bit machine but was told I had to set up a 32bit XP VM on my Win7 machine to use Forms and Reports for development.

  • Using log4j v.1.2 with Weblogic 7.0

    I try to use logging pissibilities of Log4j with Weblogic 7.0 using com.bea.logging.WeblogicAppender
    class from logtoolkit.jar.
    When I use Weblogic's version of Log4j (v. 1.1.3), all is OK. When I try to use
    current version of Log4j (v.1.2.6), I receive java.lang.NoSuchFieldError: priority
    at com.bea.logging.WeblogicAppender.append(Unknown Source)
         at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
         at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)
         at org.apache.log4j.Category.callAppenders(Category.java:187)
         at org.apache.log4j.Category.forcedLog(Category.java:372)
         at org.apache.log4j.Category.info(Category.java:674)
         at com.mydomain.framework.log.Log4JLogger.logInfo(Log4JLogger.java:73)
    There is configuration file:
    <log4j:configuration>
    <appender name="WeblogicAppender" class="com.bea.logging.WeblogicAppender">
         <layout class="org.apache.log4j.PatternLayout"></layout>
    </appender>
    <root>
    <priority value ="debug" />
    <appender-ref ref="WeblogicAppender"/>
    </root>
    </log4j:configuration>
    Does anybody know this problem?

    Try changing "priority" to "level".
    Kevin

  • Using StoneBeat WebCluster load balancing with WebLogic

              Hi,
              I have done some testing of WebLogic Server with my company's StoneBeat WebCluster
              distributed load balancing software. This might be one more option to consider
              as a load balancing solution for WLS. It is advanced in the sense that load balancing
              is really dynamic, there are no single-points of failure (distributed architecture)
              and there is a very good, configurable test subsystem that runs on each cluster
              node to check for overload situations, HW/OS failures, ...
              In the initial testing, the WebCluster load balancing works with WebLogic replication,
              although there are some cases that need mroe consideration (please see below).
              I had to get a patch to WLS6SP1 on NT to make WLS' multicast work when there are
              several NICs on the cluster nodes.
              However, there is one case which causes problems:
              - I have 3 cluster nodes
              - P: 2, S: 3 (SessionServlet = 1)
              - 2: offline - P: 3, S: 1 (SessionServlet = 2; WebCluster randomly selected a
              new node to handle the connection)
              - 2: online - P: 2, S: ? (SessionServlet = 3, WebCluster redistributes the load
              when a node goes online)
              - 2: offline
              - P: 3, S: 1 (__SessionServlet = 1__) NB!
              The log messages show that when node 2 comes back online it retrieves the replica
              from the secondary (node 1) and not from the primary (node 3). After a while (5-6
              minutes), node 3 tries to update the replica on node 1. Node 1 considers this
              a stale update request and removes the Primary 16... (node name) and then the
              secondary for 16... (the replicated object). Then there's a message (still on
              node 1) that it is unable to find object 16... Back on node 3 the primary for
              16... is removed.
              From the WLS6 documentation (under the discussion of using replication with external
              HW load balancing solutions) I thought that this case would have been handled:
              - it is stated that after the failure of a node, if the HWLB box sends the next
              request to a node where there is no replica, WLS is able to retrieve the replica
              - to be fair, this is what happens: when node 2 came back online, it retrieved
              the replica from node 1 (the secondary) - I suppose that there is an assumption
              that if a request arrives to a node without a replica, the primary __must have
              failed__
              Is there any way to get around this problem?
              Admittedly, WebCluster has a problem in that the stickyness of connections is
              not perfect: - when a node goes online, a connection that was correctly persisted
              (based on either source-ip or source-network address) may be moved to a new node
              since the load is redistributed. Our load balancing is very dynamic, but doesn't
              maintain a list of who is connected to which node when resistribution takes place
              Regards,
              Frank Olsen
              Stonesoft
              

    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

Maybe you are looking for