Foglight Cartridge for WebLogic version 4.4.3 Foglight version 4.1 July 2007 2007 Quest Software, Inc. ALL RIGHTS RESERVED. About the WebLogic Cartridge Supported Platforms Installation Resolved Issues Known Issues General Information Quest X-Agent Support Policy Global Operation About Quest Software, Inc. About the WebLogic Cartridge Thank you for purchasing or evaluating Foglight for J2EE. This document contains the list of supported platforms, notes on installing Foglight, notes on this version of Foglight, general notes, and a list of known problems. The Foglight Cartridge for WebLogic lets you to continuously monitor your WebLogic Application Servers using any of five Foglight Agents that provide 24x7 monitoring to help you detect and resolve performance problems in your application server infrastructure and the applications running in that infrastructure. The WebLogic Cartridge contains the following agents: The WebLogic6 Agent collects and monitors runtime metrics from instances of BEA WebLogic Server 1. The agent collects performance data on the application server and deployed applications, including JVM usage, JMS, EJB, and JDBC metrics. The agent includes standard Foglight graph and table views. In addition, the agent includes a number of rules to notify application and system administrators of performance problems for diagnosis and resolution. The WebLogicPortal Agent collects and monitors instances of BEA WebLogic Portal. The agent collects performance related metrics from your portal server, such as response time, access count, memory utilization, and many more. The agent provides standard Foglight graph and table views, as well as a number of configurable rules used to notify system administrators of any performance related problems. The WLDomain Agent monitors the state of each cluster and standalone managed server in the entire WebLogic domain. Only one WLDomain Agent should be created for a given WebLogic Domain. This agent is configured to communicate with a servlet running on the WebLogic Administration Server. The RequestTime Agent provides triage data for service requests on individual WebLogic servers using Quest PerformaSure bytecode instrumentation. The RequestTime Agent provides request response times for service requests organized by request type and J2EE service tier. The RequestTime Agent is compatible with Quest PerformaSure and may be used to record PerformaSure sessions. The J2EEMemory Agent provides memory analysis data on J2EE production environments. This data is particularly useful in helping to assess the potential for memory leaks and Out of Memory failures that can impact system performance. The J2EEMemory Agent for WebLogic uses Quest PerformaSure bytecode instrumentation to provide performance data for individual service requests that run within a single WebLogic Application Server instance. 1 If you are running WebLogic Server v.6.1, you must have the version of the WebLogic Server that includes J2EE 1.3 features. - 1 -
Supported Platforms For information about the supported platforms, please login to Quest SupportLink's Downloads & Updates area using the following link: http://questsupportlink.quest.com/support_download/downloads.asp. Then follow these steps: 1 Select Foglight in the Product Family drop-down. 2 Select your Cartridge from the list. 3 Select the version you are looking for. 4 Select the SupportedPlatformsAndServers-PM.pdf document. Please note the following: This version of the Foglight Cartridge for WebLogic is supported on Foglight Management Server v.4.1.1a, 4.1.2, 4.1.3, 4.2.1a, 4.2.2, and 4.2.3. WebLogic 6.1.[0-7] requires the version of WebLogic Server 6.1 that includes J2EE 1.3 features. See the Getting Started Guide for more information. In certain common configurations on Windows, the WebLogic 7.0 or 8.1 server may be required to run under JDK1.4.1 due to Hotspot internal errors in earlier versions. If you are running Windows, see Known Issues on page 3. J2EEMemory Agent makes use of the jvmstat technology to collect some of its metrics (such as Garbage Collection information for different generation spaces). The Agent populates the J2EEMemory State table (JMEM_State) with this information. However, the jvmstat technology is only available in the Sun JVM v 1.4.2 and higher and in the HP JVM 5.0. If you are running with a Sun JVM 1.4.0 or 1.4.1, or a BEA JRockit JVM, the J2EE Memory Agent will collect generic JVM metrics only, populating only the TotalFree, TotalFreePercent, TotalSize, TotalUsed and TotalUsedPercent fields in the J2EEMemory State table. All other fields will be empty. If you are using a Sun JVM 1.4.2 or higher or the HP JVM 5.0 then all fields will be populated. The following platforms are no longer supported: WebLogic 5.1.[9-13] AIX 4.3.3 Solaris 7 This list is subject to changes, and represents only the platforms for which support was discontinued at the release time. For complete information on platforms that are supported by the Foglight Cartridge for WebLogic, please refer to the above URL. Installation For detailed installation and configuration instructions, please refer to the Getting Started Guide. The installer files for this release are: WebLogic_V41_U_012345p.sh for Solaris WebLogic_V41_W_678910p.exe for Windows If installing the Cartridge on a Solaris platform, you must set the DISPLAY environment variable to point to a valid display device. This variable is used by the Compare and Update Utility which lets you migrate existing Agent rules and views to the current version. The installation process requires this variable to be set even if you choose not to migrate the Cartridge. For more information about the Compare and Update Utility, see the Getting Started Guide. - 2 -
Resolved Issues PR# CR# Case ID Description 62043 534740-1 StackOverflow errors occur when instrumenting WebLogic Server 9.2.1 with JRockit JVM 1.5.0_10. This issue also applies to the following instrumented application servers: JBoss Application Server, Oracle Application Server, and Tomcat Server. 61960 527948-1 Deadlock detected when starting an instrumented WebLogic Server. This issue also applies to the following instrumented application servers: JBoss Application Server, Oracle Application Server, Tomcat Server, and WebSphere Application Server. 58419 511321-1 Instrumented WebLogic Server 8.1.6 with the DST release of JRockit JDK1.4.2 fails to start. This issue also applies to the following instrumented application servers: JBoss Application Server, Oracle Application Server, and Tomcat Server. 55284 485261-1 Incorrect metrics from weblogic.servlet.fileservlet. Known Issues This section lists known issues in the Foglight Cartridge for WebLogic, version 4.4.3. Installation Issues PR 39351 / CR 95629 - If client is in (D)own or (T)imeout state, cartridge install loops indefinitely If a Foglight client cannot be updated during the cartridge update, the Foglight Server logs a similar message until the installation process is stopped, which causes the Foglight Server to loop the installation. This issue has been fixed in the coming release. ================================================================= Clients not yet reported updated with WebLogic_V41_U_051213p" (W)aiting (U)pdating (D)own (T)imeout (H)ost down (F)ailed rd-aix05.sitraka.com(u) rd-rhas21-02(d) l2000-cs.sitraka.com(d) PR 42670 / CR 130937 - sethoststate not updating Windows Clients After installing the cartridge on the Foglight Server, when you run the sethoststate command to update monitored hosts manually, Windows-based clients may not be updated as expected. This issue is being investigated by Quest Software. PR 43278 / CR 133714 - sethoststate not updating monitored hosts In some cases, running the sethoststate command does not update monitored hosts as expected. This issue will be fixed in a future release. - 3 -
PR 45801 / CR 148741 - Windows Client installer reports error In some cases, the Foglight Windows Client installer reports the following error: Open file failed DBVARS This causes the installation process to go into an infinite loop, and the installation must be cancelled. This issue is being investigated by Quest Software. PR 45916 / CR 149543 - Foglight Client installer reports an error on RedHat AS v.3.0 The installation of the Foglight Client may fail on RedHat AS v.3.0. This issue is being investigated by Quest Software. PR 45934 / CR 149598 - Foglight Client installer fails on a box running Linux kernel v.2.6 when using SSH The Foglight Client installer may fails when using SSH, and the monitored host is running on a Linux kernel v.2.6. This issue is being investigated by Quest Software. Foglight Issues CR 98132 - Soft limit data cap entry is not followed, hard limit is then followed If a single entry is left in the data cap list, the data cap setting is ignored. This issue is being investigated by Quest Software. CR 123962 - <FGLHOME>config\weblogic not backed up When you run a cold backup, the <FGLHOME>config\weblogic directory is not being backed up. Workaround: After the cold backup process is complete, copy <FGLHOME>\archive\weblogic to the config directory of the cold backup location. This will prevent loss of data when performing a restore operation. PR 41112 / CR 98130 - Modifying or adding rules does not take effect In some cases, creating or modifying rules on the Foglight Server does not take effect. This issue will be fixed in a future release. PR 42662 / CR 104787, CR 0110539 - Column headings and data in Data Browser are swapped When you open a table using the Data Browser, the table columns and data appear to be swapped. This issue will be fixed in a future release. CR0153683 - Foglight Management Server (FMS) binaries fail in Solaris 10 zones The Foglight Operations Console (FOC) uses the fglsys process to populate the database. However, when the FOC monitors a Foglight Management Server that runs in a Solaris 10 zone, the fglsys process fails on startup, and generates a core file. This may affect systemrelated metrics that are collected by the Cartridge, such as disk metrics or similar. This issue is being investigated by Quest Software. WLDomain Agent Issues PR 50481 - Cloned WLDomain Agents not firing alerts Cloned WLDomain Agents do not fire alerts properly when managed servers are down, but the default WLDomain Agent works properly. Workaround: Restart the Foglight Management Server. WebLogic6 Agent Issues PR 50347 - On Linux, adding Agents to WebLogic Server 8.1.5 using HTTPS causes the application server to crash On Red Hat Enterprise Linux 4 and SUSE Linux Enterprise Server 8 and 9, adding Agents to WebLogic 8.1.5 that are configured to HTTPS can cause the application server to crash. This is caused by a bug in JRockit (reported by BEA). The solution is to upgrade to Web Logic Server 8.1.6, which contains a fixed version of JRockit. - 4 -
PR 46009 - ClassName in Entity Beans appears as unknown The ClassName field in the Entity Beans table (WLS6_EntityBeans) is displayed as unknown, while the other fields in the table appear correctly. This issue is being investigated by Quest Software. PR 46011 - ClassName in Session Stateful Beans appears as unknown The ClassName field in the Session Stateful Beans table (WLS6_SessionStatefulBeans) is displayed as unknown, while the other fields in the table appear correctly. This issue is being investigated by Quest Software. PR 46013 - ClassName in Message Driven Beans appears as unknown The ClassName field in the Message Driven Beans table (WLS6_MessageDrivenBeans) is displayed as unknown, while the other fields in the table appear correctly. This issue is being investigated by Quest Software. PR 46101, PR 47385 - Modified in Application Deployment appears as unknown The Modified field in the Application Deployment table (WLS6_ApplicationDeployment) is displayed as unknown, while the other fields in the table appear correctly. This issue is being investigated by Quest Software. WebLogicPortalAgent Issues PR 43257 / CR 110539 - Framework data appears in WLP Service Table in real time When you open the WLP Service Table (WLP_Service) in the WebLogicPortal Data Browser, framework data appears in real time instead of service data. This issue will be fixed in a future release. Foglight Monitoring Application Issues PR 45789 - Deployment script for Foglight Monitoring Application may not detect standalone servers When there are clusters in a setup, the deployment script for the Foglight Monitoring Application does not detect standalone servers that are not a part of a cluster. This issue is being investigated by Quest Software. WebLogic 6.1 + Issues Hotspot internal errors on Windows 2000 or Windows NT When the WebLogic 7.0 administrative server runs under JDK1.3.1_8 (or earlier) on Windows 2000 or Windows NT and also supports user code that is being monitored by Foglight, Hotspot internal errors may occur. The BEA trouble ticket for this problem is 411059. The currently known workaround is to use JDK1.4.1_02. that this version of the JDK is only supported on Service Pack 2 of WebLogic 7.0, not by earlier service packs, so a WebLogic upgrade may also be required. This configuration is used by many of the WebLogic samples, in many development environments, and some production environments. JMX MBean InstanceNotFoundException error Due to a BEA WebLogic defect (Case 375513, CR 092877), the JMX MBean for a managed server is not destroyed when the server is deleted from the WebLogic configuration. Consequently, the Foglight WebLogic6 servlet running in the WebLogic Administration server will continue to attempt to interrogate the (now defunct) managed server, resulting in an InstanceNotFoundException, which is logged by WebLogic as an error. The only workaround suggested by BEA is to restart the WebLogic Administration server after deleting a managed server. - 5 -
Windows startup script weblogic unrecognized property warning If the WebLogic server startup script does not specify the WebLogic username/password, the following warning may be emitted by the WebLogic server during startup: Connecting to.....<warning> <Management> <141087> <Unrecognized property: classloader.preprocessor> <ClassLoader><I>Pre-processor com.quest.eflex.instrument.tools.instrumentor.classloader.wl6classfilepreprocessor loaded and initialized The warning message is benign and should be ignored. BEA-100061 warning for non-serializable ClassDataAttribute You will receive the following warning the first time a Foglight servlet sessions is created:... <Warning> <HTTP Session> <localhost> <MedRecServer> <ExecuteThread: '2' for queue: 'foglight'> <weblogic> <> <BEA- 100061> <Web application: ServletContext(id=5463428,name=Foglight_WebLogic_6_1,context-path=/Foglight_WebLogic_6_1) tried to place a non-serializable attribute: com.quest.foglight.agents.eflex.classdataattribute into the session: 2BcUr14zN2Fj4gl3HKEoug1r08PmsjrQkLZ2jNnMt21y2SZ3dMge!1100405657!1052859476064. This attribute will be lost upon redeployment. This message is logged only once per session.> This warning is technically accurate and occurs because of a BEA WebLogic defect (Case 414052, CR106230). However, this warning is only applicable if session persistence is enabled and because it is not enabled you can ignore this warning. WebLogic 7.0.5 on RedHat AS 2.1 with Sun JDK runs out of memory When the WebLogic 7.0.5 server runs on RedHat AS 2.1 under the Sun 1.3.1 VM, it reports an Out of Memory error, and logs an error message similar to the following: <Jun 16, 2005 1:25:30 PM EDT> <Error> <HTTP> <101017> <[ServletContext(id=1806483,name=console,context-path=/console)] Root cause of ServletException java.lang.outofmemoryerror Workaround: Add the -XX:MaxPermSize=128m parameter to the extenv.(sh cmd) script to prevent Out of Memory errors. PR 52030 / Case 453597-1 - InvalidAttributeValueException/getFullPath() error with WebLogic 8.1 For WebLogic Server 8.1 SP1-SP3, the Application.FullPath attribute may not be available. It is available for WebLogic Server 8.1 SP4 and above. Workaround: The workaround is to upgrade to WLS 8.1 SP4 or above. If you are unable to upgrade, the following alternative workaround is available: In the weblogic_server.properties file in the.war file, change the line Application.FullPath=uri to Application.Path=uri This problem is also documented in the Quest Support Knowledgebase solution 21609. Information about this solution is available at the following URL: http://support.quest.com/esupport/solution.asp?waid=268466262&itemid=21609-6 -
PR 49018 - WebLogic 8.1.5 core dumps In some cases, BEA WebLogic 8.1.5 on RHAS 3.0 on Itanium generates a core dump file when DES ciphers are used with SSL: -----------... at weblogic/kernel/executethread.run(executethread.java:183)@0x30eb0f90 at java/lang/thread.startthreadfromvm(unknown Source)@0x304611b0 --- End of stack trace Additional information is available in: /workspace/lab/weblogic815/weblogic81/server/bin/jrockit.32609.dump /workspace/lab/weblogic815/weblogic81/server/bin/core If you see this dump, please open a support case with BEA and supply as much information as you can on your system setup and the program you were running. You can also search for solutions to your problem at http://forums.bea.com in the forum jrockit.developer.interest.general. Extended, platform specific info: libc release: 2.3.2-stable Elf headers: libc ehdrs: EI: 7f454c46020101000000000000000000 ET: 3 EM: 50 V: 1 ENTRY: 0x2ac30 PHOFF: 0x40 SHOFF: 0x2a8ca8 EF: 0x10 HS: 64 PS: 56 PHN; 8 SS: 64 SHN: 65 STIDX: 64 libpthread ehdrs: EI: 7f454c46020101000000000000000000 ET: 3 EM: 50 V: 1 ENTRY: 0x7160 PHOFF: 0x40 SHOFF: 0x26020 EF: 0x10 HS: 64 PS : 56 PHN; 7 SS: 64 SHN: 35 STIDX: 34 libjvm ehdrs: EI: 7f454c46020101000000000000000000 ET: 3 EM: 50 V: 1 ENTRY: 0x69ee0 PHOFF: 0x40 SHOFF: 0x5a39c0 EF: 0x10 HS: 64 PS: 56 PHN; 4 SS: 64 SHN: 25 STIDX: 22 ===== END DUMP =============================================================== General Information Database Changes The following table indicates the agents for which the database schema has changed in the releases between v.4.0 and 4.4.3. For more information, see the Getting Started Guide. Agent Cartridge Release 4.0 4.1 4.3 4.3.1 4.3.5 4.4 4.4.1 4.4.2 4.4.3 WebLogic6 WebLogicPortal WLDomain RequestTime J2EEMemory - 7 -
Creating an Agent-Specific Debug Log For technical support issues, you may be asked to configure the cartridge to create a debug log. To enable a debug log, do the following on the Foglight Server. WebLogic6 and WLDomain Agents: 1 Create a file called <agentname>_errvars@<mycomputer> in FGLHOME/World Where <agentname> is the name of the agent and <MyComputer> is the location of the monitored host. For example: Weblogic_ERRVARS@PROD105955 2 Within the file, create the following entries: FILE=$AbsolutePath\<agentname>log.txt SIZE=10M METHOD=file SEVERITY=fatal,stat,error,warn,info,debug CORE=no Where <agentname> is the name of the agent. 3 Stop the Agent. 4 Restart the Agent. 5 Administer any tests for debugging. 6 Stop the Agent. The debug log appears in the <AbsolutePath> directory (see Step 2). To stop debugging, remove the debug file you created from the FGLHOME/World directory. WebLogicPortal, RequestTime and J2EEMemory Agents: Agent-specific error logging is not supported by the RequestTime and J2EEMemory Agents. To gather debug information, you must change the settings in the FGLHOME/World/Errvars file: 1 Make a backup copy of the FGLHOME/World/Errvars file. 2 Edit the original FGLHOME/World/Errvars file. 3 Within the file, set the file variable to a physical path name: FILE=$AbsolutePath\log.txt 4 Set the METHOD variable to FILE: METHOD=file 5 Set the SEVERITY variable: SEVERITY=fatal,stat,error,warn,info,debug 6 Stop the Agent. 7 Restart the Agent. 8 Administer any tests for debugging. 9 Stop the Agent. The debug log appears in the <AbsolutePath> directory (see Step 3). To stop debugging, restore the backup copy of the Errvars file. - 8 -
Configuring HTTPS Support The WebLogic Cartridge includes the support for application servers that use SSL security (the HTTPS protocol). On Unix machines, the HTTPS support is enabled through the use of the OpenSSL ssl library. This library uses a pseudo-random number generator for data encription tasks, and requires random information to feed the generator. To do that, the library reads random data from the following files: /dev/random /dev/urandom /var/run/egd-pool /dev/egd-pool /etc/egd-pool /etc/entropy In addition to the above sources, the library also uses the device pointed to the environment variable $RANDFILE or $HOME/.rnd if either if those variables are set. If none of these sources exist, the generator will not function properly, and the HTTPS support will not be available. This is a known problem on HP-UX 11i machines. To overcome the problem, HP provides the following tools: /dev/random and dev/urandom or libraries/tools. This tool includes a random data device which is installed to /opt/openssl/prngd/prngd. If you choose this option, you should set $RANDFILE to that location. For information on how to configure the HTTPS support, see the Getting Started Guide. Quest X-Agent Support Policy The Quest X-Agent is a customizable agent that can be used to support environments that are not officially supported (a complete list of supported platforms can be found by contacting Quest Technical Support). In the event that part of your Java Enterprise environment is not supported by Quest Technical Support, you can choose to work with Quest Consulting to create a Custom Agent Integration based on the X-Agent that supports your specific application server, JVM and OS combination. The X-Agent is validated for specific JVM/OS combinations only the list of supported platforms can be found by contacting your Quest Sales representative. If you want to use the Quest Application Management Solution for a currently unsupported application server environment you can purchase a Custom Agent Integration for your specific application server provided it is running on a validated JVM/OS combination. The creation of a Custom Agent Integration will involve two phases of work between Quest Consulting and your organization: Scoping Phase: Quest Consulting will determine the exact versions of application server, JVM and OS and see if the application server can take advantage of X-Agent instrumentation. Implementation Phase: Assuming that the X-Agent instrumentation is compatible with your application server Quest Consulting will scope an engagement to complete a Custom Agent Integration. While Quest Technical Support will support the X-Agent instrumentation itself, the Custom Agent Integration will be supported through Quest Consulting. Quest Software, Inc owns any Intellectual Property for the code, templates, documentation or other deliverables used in the creation of the Custom Agent Integration. - 9 -
Global Operation This section contains information about installing and operating this product in non-english or non-ascii configurations, such as those needed by customers outside the USA. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation. This product was not enabled for international operation. Only U.S. English configurations of this product and U.S. English datasets are fully supported. Support for non-ascii characters and/or non-english configurations may work appropriately, but these configurations have not been tested and this product should be used with caution in these environments. For specific support information, contact Quest customer support. About Quest Software, Inc. Quest Software, Inc. delivers innovative products that help organizations get more performance and productivity from their applications, databases and infrastructure. Through a deep expertise in IT operations and a continued focus on what works best, Quest helps more than 18,000 customers worldwide meet higher expectations for enterprise IT. Quest Application Advantage lets organizations deliver, manage and control complex application environments. Only Quest provides the deepest understanding of the application from end user to database. Quest Software can be found in offices around the globe and at www.quest.com. Contacting Quest Software Email: info@quest.com Mail: Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA Web site: www.quest.com Refer to our Web site for regional and international office information. Contacting Quest Support Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com From SupportLink, you can do the following: Quickly find thousands of solutions (Knowledgebase articles/documents). Download patches and upgrades. Seek help from a Support engineer. Log and update your case, and check its status. View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/global Support Guide.pdf - 10 -
2007 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc. If you have any questions regarding your potential use of this material, please contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com email: legal@quest.com Refer to our Web site for regional and international office information. Trademarks Quest, Quest Software, the Quest Software logo, Aelita, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, InTrust, IT Dad, JClass, JProbe, LeccoTech, LiveReorg, NBSpool, NetBase, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLab Tuner, SQLab Xpert, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, Toad, T.O.A.D., Tag and Follow, Vintela, Virtual DBA, and XRT are trademarks and registered trademarks of Quest Software, Inc. Other trademarks and registered trademarks used in this guide are property of their respective owners. Third Party Contributions Foglight software includes 1996 Expect software (freeware). Expect and its documentation are copyrights and trademarks of Don Libes, Associates. This product includes software developed by the OpenSSL Project Copyright (c) 1998-2003 The OpenSSL Project. All rights reserved. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). Portions of the code in this package were distributed by Carnegie Mellon University. 1989, 1991, 1992, Carnegie Mellon University. All rights reserved. Portions of this product were obtained from the ucd-snmp package written by Wes Hardaker at the University of California, Davis copyright 1996, 1998-2000. Copyright 2001-2002, Networks Associates Technology, Inc. All rights reserved. Portions of this code are also copyright 2001-2002, Cambridge Broadband Ltd. All rights reserved. Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Foglight software includes Info-ZIP. Info-ZIP is provided "as is" without warranty of any kind, express or implied. In no event shall Info-ZIP or it's contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software. All other trademarks and registered trademarks used in this document are property of their respective owners. Disclaimer The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. World Headquarters, 5 Polaris Way, Aliso Viejo, CA 92656 email: info@quest.com Refer to our Web site www.quest.com for regional and international office information. Foglight Cartridge for WebLogic - Release s Release Date - July 2007 Cartridge Version - 4.4.3 Foglight Version - 4.1-11 -