Monitoring a running weblogic server

I am aware of the facilities provided by the weblogic console for monitoring
a running server but we would like to develop our own Java app that could
report statistics, take snapshots, etc. and also alert us when something we
consider worrying occurs.
I presume the console uses an API to get its information - is this API
published?
Does this apply to 5.x as well as 6.x?
We would like to monitor the following, if there is an API we can use does
it give us all this information:
heap utilisation
bean pool size and utilisation
bean passivation count
connection pool size and utilisation
TIA
Ed

I believe there's a serverinfo.zip in the alpha code section on the dev center as
well. It does some admin work with the 5.1 apis. That being said, officially
I don't believe we ever exposed these APIs, so YMMV.
-- Rob
Tom Barnes wrote:
Ed,
For 6.x, there is useful JMX sample code at the "Developer Center":
http://developer.bea.com:80/index.jsp.
Don't know about 5.1, but there might be something for that as well.
Tom
Ed Barrett wrote:
Rob,
Many thanks for your timely response.
Is you did not expose the API I presume it must be there. So maybe you
can't answer this but can anyone else point me at the classes, etc. I should
look at in 5.x to get the same sort of information.
Rob - please don't take this as being untoward or cheeky - just if someone
else has gone to the problem of finding this out and willing to share the
information I would appreciate it.
Cheers
Ed
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]..
In 6.x, the API is JMX, and it is exposed. I don't believe we exposed theAPI
in 5.1 or earlier. (It wasn't JMX.)
-- Rob
Ed Barrett wrote:
I am aware of the facilities provided by the weblogic console for
monitoring
a running server but we would like to develop our own Java app thatcould
report statistics, take snapshots, etc. and also alert us when somethingwe
consider worrying occurs.
I presume the console uses an API to get its information - is this API
published?
Does this apply to 5.x as well as 6.x?
We would like to monitor the following, if there is an API we can usedoes
it give us all this information:
heap utilisation
bean pool size and utilisation
bean passivation count
connection pool size and utilisation
TIA
Ed

Similar Messages

  • Running Weblogic Server 7.0 SP4 using JDK 1.4

    Is it possible to run Weblogic Server 7.0 SP4 with a different JRE than the one
    that ships with 7.0 SP4. I am having issues with a bug in JDK 1.3.1 which when
    I run under JBuilder X using 1.4 is not there. ANy help as to how I go about
    doing this would be welcomed.
    Thanks
    Justin

    Yes,
    The JDK is just the Sun JDK...nothing special. You may upgrade minor versions quite safely by dowloading later one at Sun website and pointting your "JAVA_HOME" at it.
    I would not jump to 1.4, as changes in java language may impact.

  • Running Weblogic Server 10.3.3 in Debug  mode

    Hi to all,
    Here i got a problem after installing Oracle Identity Manager 11g R3,to solve the issue i need to run WebLogic Server 10.3.3 in Debug mode.
    Can any suggest how to run WebLogic Server 10.3.3 in Debug mode.
    Here i find a solution to run in debug mode,but no difference in log files before and after changing debug mode.
    Enable Debugging on the WebLogic Server
    To start WebLogic Server in debug mode, you will need to modify the startWebLogic.cmd script in the <WLS-root>\wlserver_10.0\samples\domains\wl_server directory. <WLS-root> is the directory in which WebLogic 10.0.1 was installed into.
    In the startWebLogic.cmd script, specify the JAVA OPTIONS with:
    set JAVA_OPTIONS=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=n
    Let me know if u have any questions,
    Thanks and Ragards,
    Satish

    Greg,
    I cam across this issue too. It looks like there is a bug in sample script provided by weblogic documentation. We should not use ADMIN_URL as they mentioned in the script.
    Remove it and try. For more info. please see this link helps:
    http://ananthkannan.blogspot.com/2009/10/weblogic-server-instance-as-window.html
    Thanks.
    Ananth

  • How to run weblogic server in backgroud?

    I just installed weblogic60sp1 on Aix.
    how can i start weblogic server in backgroud?
    Ron

    Hi Kartheek,
    If you're new to running WebLogic as a Windows service, you'll probably find it a bit tricky at first. I found troubleshooting problems, especially start-up and process-crashes, awkward at first. If you have time, you may want to check these out:
    [ http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html|http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html]
    [http://e-docs.bea.com/wls/docs81/adminguide/winservice.html|http://e-docs.bea.com/wls/docs81/adminguide/winservice.html]
    -Jones

  • How to run weblogic server in background process on Windows XP 2002 ?

    Hi,
    I have installed weblogic server 9.2 in Windows XP 2002, I want to start my weblogic server and instances in background and keep running .
    Can anybody please provide information on the same ?
    Thanks in Advance,
    Kartheek.

    Hi Kartheek,
    If you're new to running WebLogic as a Windows service, you'll probably find it a bit tricky at first. I found troubleshooting problems, especially start-up and process-crashes, awkward at first. If you have time, you may want to check these out:
    [ http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html|http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html]
    [http://e-docs.bea.com/wls/docs81/adminguide/winservice.html|http://e-docs.bea.com/wls/docs81/adminguide/winservice.html]
    -Jones

  • Minimum memory reuuirment to run weblogic server 5.1.0

    Hi
    What is the minimum memory reuuirment to run wl on nt?
    Y.L.

    Hi Yi,
    You can check the requirements page online at
    http://www.weblogic.com/docs51/platforms/index.html#winnt
    I'd imagine that these requirements are mostly for development work. If the
    WebLogic Server resides and is for production level, then there are other
    matters to add to the equation, such as how many users to you plan to
    support, among others.
    Nelson Paiva
    WLCS Developer Relations Engineer
    <Customer
    What is the minimum memory reuuirment to run wl on nt?
    </Customer>

  • Error while running weblogic server in jdeveloper

    starting weblogic with Java version:
    Error: Could not create the Java Virtual Machine.
    Error: A fatal exception has occurred. Program will exit.
    Unrecognized option: -jrockit
    Starting WLS with line:
    C:\PROGRA~1\Java\JDK17~1.0\bin\java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Users\DELL\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Users\DELL\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.domain.config.dir=C:\Users\DELL\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Users\DELL\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Users\DELL\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Users\DELL\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Users\DELL\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\servers\DefaultServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\Users\DELL\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\oracle\store\gmds -DUSE_JAAS=false -Djps.policystore.hybrid.mode=false -Djps.combiner.optimize.lazyeval=true -Djps.combiner.optimize=true -Djps.auth=ACC -Doracle.core.ojdl.logging.usercontextprovider=oracle.core.ojdl.logging.impl.UserContextImpl -noverify -Doracle.webcenter.analytics.disable-native-partitioning=false -Doracle.webcenter.tagging.scopeTags=false -Djrockit.codegen.newlockmatching=true -Dportlet.oracle.home=E:\Oracle\Middleware\jdeveloper -Dwc.oracle.home=E:\Oracle\Middleware\jdeveloper -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
    Error: Could not create the Java Virtual Machine.
    Error: A fatal exception has occurred. Program will exit.
    Unrecognized option: -jrockit
    Process exited.
    JDeveloper version -11.1.1.6.0
    Window 7 64bit os
    Please help.
    Regards,
    Shrikant1988

    I have reinstall changed the class path in environment variable and getting below error
    *** Using port 7101 ***
    C:\Users\DELL\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\bin\startWebLogic.cmd
    [waiting for the server to complete its initialization...]
    \Java\jdk1.6.0_38 was unexpected at this time.
    Process exited.
    Regards,
    Shrikant1988

  • How to run Weblogic Server 8.1 in Win 98/Red Hat Linux

    I've receieved the Weblogic Server 8.1 Evaluation version. I've installed it successfully. But while I try to start the Weblogic Server the progress bar shows the completion of the server start but the indicator does not turn green. What might be the reason.Same is the problem with Red hat Linux 8.0 ? Please send in the solution

    Joydeep,
    WebLogic Platform 8.1 is not supported on Win 98 and Red Hat 8.0. Please
    refer to the following url for more information.
    http://e-docs.bea.com/platform/docs81/support/supp_plat.html#1048419
    Regards,
    Raj Alagumalai
    WebLogic Workshop Support
    "Joydeep Paul" <[email protected]> wrote in message
    news:3f4e9723$[email protected]..
    I've receieved the Weblogic Server 8.1 Evaluation version. I've installedit successfully. But while I try to start the Weblogic Server the progress
    bar shows the completion of the server start but the indicator does not turn
    green. What might be the reason.Same is the problem with Red hat Linux 8.0 ?
    Please send in the solution

  • Running weblogic server and workshop on 2 different machines

    hi all,
    My computer cannot handle both the server and workshop running on it, at the same time.
    1) installed weblgic server, created domain on computer A.
    2) mapped the domain\source code(working in dev mode) on computer A to computer B.
    3) I open up the .work file in the mapped drive from workshop on computer B.
    Problem:
    Computer B never completes "Scanning .. source...", very processor intensive.
    Any help, very much appreciated.
    Novice!

    Workshop is a pig and the scanning thing spikes my CPU everytime (1.8Ghz P4 and 1G memory). Please make it better.

  • Attaching strace to running WebLogic Server using jrockit

    Hi all,
    We are running WLS 8.1 sp4 on Linux using jrockit. As you know jrockit on Linux spawns several proccesses. I'm trying to use strace to monitor traffic in the hopes of solving a socket timeout issue. I have tried the following command:
    strace -p 12742 -f -r -t
    However, that doesn't see to be the correct pid. Does anyone know how to attach strace to a running WLS using jrockit on Linux?
    pat

    Yes,
    The JDK is just the Sun JDK...nothing special. You may upgrade minor versions quite safely by dowloading later one at Sun website and pointting your "JAVA_HOME" at it.
    I would not jump to 1.4, as changes in java language may impact.

  • Multiple instances of weblogic server 6.1 running on the same machine

    Hi,
    I need to run two instances of weblogic server 6.1 running on the same
    machine. I need one for development and the other one running the live
    applications. I need two instances to be independent of each other. I am
    running weblogic server as an NT service. So I need two servers to start
    from the service so they are independent of each other.
    Thanks
    Madhu

    Hi.
    You can create new servers in your domain via the console. Be sure they are
    listening to different ports, however. If your NT machine supports more than
    1 IP address then you could alternatively bind each server to a different
    address.
    I'm not sure if this answers your question?
    Regards,
    Michael
    m holur wrote:
    Hi,
    I need to run two instances of weblogic server 6.1 running on the same
    machine. I need one for development and the other one running the live
    applications. I need two instances to be independent of each other. I am
    running weblogic server as an NT service. So I need two servers to start
    from the service so they are independent of each other.
    Thanks
    Madhu--
    Developer Relations Engineer
    BEA Support

  • Is it possible to run  EJB (  Weblogic server 7.0) on win XP professional

    Hi,
    i am using win XP Professional platform. Is it possible to run EJB (WEBLOGIC SERVER 7.0) on this platform. IF not what are the other plug in needed to run WEBLOGIC SERVER on WIN XP Prof ?.

    Yes, though currently BEA hasn't certified it for XP.

  • Performance Measuring of Weblogic Server

    I do performance testing for our own software applications. So far our web
    servers have been WIN NT running IIS 4. Now, our development group have
    started to work with WebLogic.
    I have never worked with Weblogic and I feel a little in the dark. Where
    could I find information on how to do Performance monitoring for a WebLogic
    Server?
    Any information would be appreciated.
    Francisco

    I suggest contacting their technical support.
    Thanks,
    Michael
    Michael Girdley
    Product Manager, WebLogic Server & Express
    BEA Systems Inc
    Eran Shtiegman <[email protected]> wrote in message
    news:8fr11d$mq0$[email protected]..
    Thanks,
    I downloaded the product, but still haven't got it to work with WLS ...
    Has anybody gotten the current version to work with WLS ?
    Thanks,
    Eran
    "Ron Anderson" <[email protected]> wrote in message
    news:[email protected]..
    Try http://www.wilytech.com/
    The product is Introscope.
    ron
    Eran Shtiegman wrote:
    Are you sure that is the right link ? It points to a static webpage
    of
    a
    financial consulting company ...
    What is this product ?
    Eran
    "Michael Girdley" <[email protected]> wrote in message
    news:8fgc33$c9b$[email protected]..
    First, I suggest looking at the information located in the WebLogicconsole.
    Second, as of version 5.1.0, we have a clean integration with a very
    nice
    product from the folks at http://www.wileytech.com (I believe that
    is
    the
    right URL :-) that will likely help you.
    Thanks,
    Michael
    Michael Girdley
    Product Manager, WebLogic Server & Express
    BEA Systems Inc
    Francisco Kendall-Montes <[email protected]> wrote in message
    news:8fep2k$hun$[email protected]..
    I do performance testing for our own software applications. So
    far
    our
    web
    servers have been WIN NT running IIS 4. Now, our development
    group
    have
    started to work with WebLogic.
    I have never worked with Weblogic and I feel a little in the dark.Where
    could I find information on how to do Performance monitoring for aWebLogic
    Server?
    Any information would be appreciated.
    Francisco

  • Weblogic server 10.0.1 stop all request when memory drop and grow again

    We are running weblogic server 10.0.1 on window server 2003 with a custom applicaiton . our heap size is set to 1024MB min and max. Usually it is running normally, but at some ocassion, we find the webogic process memory drop to 80K and then grow gradually( from the task window). During this period, the server stops all requests until the process memory reach about 1000MB as we look at the server console. It starts process again and accept requests. After the requests are cleared, the server resume normal. Is it a full GC or window sever memory allocation when its memory is low? I cannot figure out this issue.
    Much appreciated if there is any advices.
    Keith

    First of all, when you go to monitor tab you see all the threads from self tuning thread pool. This includes all the threads in the server, not only the ones allocated to your workmanager.
    This is how i think its working...
    1) All your threads are hung..you have 300 hogging threads , that reaches your max thread constraints on your work manager.. weblogic is not going to allow any more requests from that work set to take up threads.. and capacity is both executing and queued requests..you got 150 pending requests and 300 hogging.. so a total of 450, your capacity.
    2) Its not 631 threads, its 631 requests, weblogic must be reporting all the threads in the queue at the time you monitored it.
    3) The reason for one cluster to go down would be that those servers in that cluster were waiting for some resource. As you have different applications in the two clusters...there must be some resource that cluster1 uses which was not available. you can see what those threads were doing by getting thread dumps when this happens.

  • Embedded WebLogic Server

    Hi, everybody.
    First of all, i apologize for my poor writing skills in English. My native language is Portuguese.
    Is it possible to start an WebLogic Server 10.0+ inside a running JVM? Tricks like start weblogic.Server in a new JVM, using the appropriate -D switches (system properties and policy file), won't work for me.
    I need to start WL in the same JVM (an Embedded WebLogic Server instance) like Tomcat (http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/catalina/startup/Embedded.html) or Jetty (http://docs.codehaus.org/display/JETTY/Embedding+Jetty).
    I've already tried to set System.setProperty() properly and run weblogic.Server.main(new String[0]), but WebLogic fails silently. It's impossible to debug it because the source code is closed.
    Is there any suggestion or workaround to do it?
    Some context: I'm working with an open source general API to start Embeddable Web Containers/Application Servers and i'm trying to develop/use WL's implementation. The host contains a regular WebLogic installation and i'm able to start WebLogic invoking "java -cp appropriate_class_path weblogic.Server" from any directory: WebLogic just asks about context.xml and do its magic.
    Thanks in advance.
    Best regards,
    Daniel.

    Another difference I noticed between these 2 approaches (java -cp weblogic.jar vs. new URLClassLoader()): When weblogic.jar is specified using -cp, the system property java.class.path is changed to include a lot of WebLogic jars.
    Is there any bootstrap log that i can enable to understand what is happening?
    Thanks.
    == java -cp . RunWL2 ==
    java.class.path = C:\tmp\test_wl
    == java -cp .;weblogic.jar RunWL2 ==
    java.class.path = C:\tmp\test_wl;C:\bea2\modules\com.bea.core.weblogic.workmanager_1.4.0.0.jar;C:\bea2\modules\com.bea.core.utils_1.4.0.0.jar;C:\bea2\modules\com.bea.core.utils.full_1.4.0.0.jar;C:\bea2\modules\features\weblogic.server.modules.L10N_10.3.0.0.jar;C:\bea2\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\bea2\modules\com.bea.core.descriptor.j2ee_1.1.0.0.jar;C:\bea2\modules\com.bea.core.descriptor.j2ee.binding_1.1.0.0.jar;C:\bea2\modules\com.bea.core.descriptor.wl_1.1.0.0.jar;C:\bea2\modules\com.bea.core.descriptor.wl.binding_1.1.0.0.jar;C:\bea2\modules\com.bea.core.datasource6_1.4.0.0.jar;C:\bea2\modules\com.bea.core.datasource6.binding_1.4.0.0.jar;C:\bea2\modules\com.bea.core.beangen_1.4.0.0.jar;C:\bea2\modules\com.bea.core.descriptor.settable.binding_1.4.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.accessor_1.1.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.accessor.binding_1.1.0.0.jar;C:\bea2\modules\com.bea.core.management.core_2.3.0.0.jar;C:\bea2\modules\com.bea.core.management.core.binding_2.3.0.0.jar;C:\bea2\modules\com.bea.core.ejbgen_1.0.0.0.jar;C:\bea2\modules\org.apache.ant.patch_1.1.0.0_1-6-5.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-xslp.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-xalan1.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-weblogic.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-vaj.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-trax.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-swing.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-stylebook.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-starteam.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-nodeps.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-netrexx.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-launcher.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-junit.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-jsch.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-jmf.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-jdepend.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-javamail.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-jai.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-icontract.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-commons-net.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-commons-logging.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-resolver.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-regexp.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-oro.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-log4j.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-bsf.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-apache-bcel.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-antlr.jar;C:\bea2\modules\org.apache.ant_1.6.5\lib\ant-all.jar;C:\bea2\modules\com.bea.core.repackaged.apache.bcel_5.2.1.0.jar;C:\bea2\modules\com.bea.core.repackaged.jdt_3.2.2.0.jar;C:\bea2\modules\com.bea.core.apache.commons.collections_3.2.0.jar;C:\bea2\modules\com.bea.core.apache.commons.lang_2.1.0.jar;C:\bea2\modules\com.bea.core.apache.commons.pool_1.3.0.jar;C:\bea2\modules\com.bea.core.apache.dom_1.0.0.0.jar;C:\bea2\modules\com.bea.core.apache.logging_1.0.0.0.jar;C:\bea2\modules\org.apache.openjpa_2.2.0.0_1-1-0.jar;C:\bea2\modules\com.bea.core.xml.xmlbeans_1.0.0.0_2-4-0.jar;C:\bea2\modules\com.bea.core.logging_1.4.0.0.jar;C:\bea2\modules\com.bea.core.bea.opensaml_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.bea.opensaml2_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.monitoring.harvester.api_2.1.0.0.jar;C:\bea2\modules\com.bea.core.monitoring.harvester.jmx_2.1.0.0.jar;C:\bea2\modules\com.bea.adaptive.harvester.utils_1.2.0.0.jar;C:\bea2\modules\com.bea.mbean.typing.util_1.2.0.0.jar;C:\bea2\modules\javolution_3.7.19.0.jar;C:\bea2\modules\joda.time_1.2.1.0.jar;C:\bea2\modules\com.bea.core.xml.staxb.buildtime_1.3.0.0.jar;C:\bea2\modules\com.bea.core.xml.staxb.runtime_1.3.0.0.jar;C:\bea2\modules\com.bea.core.annogen_1.2.0.0.jar;C:\bea2\modules\com.bea.core.kodo_1.0.0.0_4-2-0.jar;C:\bea2\modules\com.bea.core.kodo.integration_1.3.0.0.jar;C:\bea2\modules\com.bea.core.kodo.integration.binding_1.3.0.0.jar;C:\bea2\modules\com.bea.core.kodo.integration.tools_1.2.0.0.jar;C:\bea2\modules\com.bea.core.process_5.4.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.stax_1.4.0.0.jar;C:\bea2\modules\com.bea.core.xml.beaxmlbeans_1.0.0.0_2-4-0.jar;C:\bea2\modules\com.bea.core.repackaged.aspectj.aspectjweaver_5.1.0.jar;C:\bea2\modules\com.bea.core.repackaged.apache.commons.logging_1.2.0.jar;C:\bea2\modules\com.bea.core.repackaged.springframework.spring_2.0.3.jar;C:\bea2\modules\com.bea.core.repackaged.springframework.pitchfork_1.1.0.0_1-0.jar;C:\bea2\modules\com.bea.core.common.security.i18n_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.xacml_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.saml2.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.engine.impl_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.engine.api_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.api_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.impl_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.jdkutils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.saml2_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.saml2.manage_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.providers.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.saml.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.xacmlproviders.utils_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.common.security.providers.env_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.certj_1.0.0.0.jar;C:\bea2\modules\com.bea.core.ldapjdk_1.0.0.0.jar;C:\bea2\modules\com.bea.core.apache.commons.net_1.0.0.0_1-4-1.jar;C:\bea2\modules\com.bea.core.weblogic.saaj_1.3.0.0.jar;C:\bea2\modules\glassfish.el_2.1.0.jar;C:\bea2\modules\glassfish.jaxb_2.1.6.jar;C:\bea2\modules\glassfish.jaxb.xjc_2.1.6.jar;C:\bea2\modules\glassfish.jaxws.resolver_2.1.3.jar;C:\bea2\modules\glassfish.jaxws.fastinfoset_2.1.3.jar;C:\bea2\modules\glassfish.jaxws.rt_2.1.3.jar;C:\bea2\modules\glassfish.jaxws.mimepull_1.0.144.jar;C:\bea2\modules\com.bea.core.woodstox_1.0.0.0_3-2-4.jar;C:\bea2\modules\glassfish.jaxws.tools_1.0.0.0_2-1-3.jar;C:\bea2\modules\glassfish.stax.ex_1.0.0.0_1-2.jar;C:\bea2\modules\glassfish.xmlstreambuffer_0.5.221.jar;C:\bea2\modules\com.bea.core.apache.oro_1.0.0.0_2-0-8.jar;C:\bea2\modules\javax.activation_1.1.0.0_1-1.jar;C:\bea2\modules\javax.annotation_1.1.jar;C:\bea2\modules\javax.interceptor_1.0.jar;C:\bea2\modules\javax.ejb_3.0.1.jar;C:\bea2\modules\javax.jdo_2.0.1.jar;C:\bea2\modules\javax.enterprise.deploy_1.2.jar;C:\bea2\modules\javax.jms_1.1.1.jar;C:\bea2\modules\javax.jsp_1.1.0.0_2-1.jar;C:\bea2\modules\javax.jws_2.0.jar;C:\bea2\modules\javax.mail_1.1.0.0_1-1.jar;C:\bea2\modules\javax.management.j2ee_1.0.jar;C:\bea2\modules\javax.persistence_1.0.0.0_1-0.jar;C:\bea2\modules\javax.resource_1.5.1.jar;C:\bea2\modules\javax.security.jacc_1.0.0.0_1-1.jar;C:\bea2\modules\javax.servlet_1.0.0.0_2-5.jar;C:\bea2\modules\javax.transaction_1.0.0.0_1-1.jar;C:\bea2\modules\javax.xml.bind_2.1.1.jar;C:\bea2\modules\javax.xml.registry_1.0.0.0_1-0.jar;C:\bea2\modules\javax.xml.soap_1.3.1.0.jar;C:\bea2\modules\javax.xml.stream_1.1.1.0.jar;C:\bea2\modules\javax.xml.ws_2.1.1.jar;C:\bea2\modules\javax.xml.rpc_1.2.1.jar;C:\bea2\modules\monfox.dsnmp.agent_1.0.0.0_4-6-5.jar;C:\bea2\modules\com.bea.core.jsafe_3.5.0.jar;C:\bea2\modules\com.bea.core.serp_1.14.2.0.jar;C:\bea2\modules\com.bea.core.apache_1.2.0.0.jar;C:\bea2\modules\com.bea.core.beaninfo_1.4.0.0.jar;C:\bea2\modules\com.bea.core.descriptor_1.4.0.0.jar;C:\bea2\modules\com.bea.core.repackaged.asm_3.0.jar;C:\bea2\modules\com.bea.core.repackaged.asm.commons_3.0.jar;C:\bea2\modules\com.bea.core.repackaged.asm.tree_3.0.jar;C:\bea2\modules\com.bea.core.repackaged.asm.util_3.0.jar;C:\bea2\modules\com.bea.core.diagnostics.core_2.1.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.logging_1.1.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.query_1.0.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.instrumentor_1.3.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.notifications_1.1.0.0.jar;C:\bea2\modules\com.bea.core.diagnostics.snmp_1.1.0.0.jar;C:\bea2\modules\com.bea.core.i18n_1.4.0.0.jar;C:\bea2\modules\com.bea.core.i18n.generator_1.3.0.0.jar;C:\bea2\modules\com.bea.core.i18n.tools_1.1.0.0.jar;C:\bea2\modules\com.bea.core.management.jmx_1.1.0.0.jar;C:\bea2\modules\com.bea.core.mbean.maker_1.3.0.0.jar;C:\bea2\modules\com.bea.core.mbean.support_1.3.0.0.jar;C:\bea2\modules\com.bea.core.messaging.kernel_1.4.0.0.jar;C:\bea2\modules\com.bea.core.resourcepool_1.4.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.socket.api_1.0.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.rmi.client_1.4.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.security.wls_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.weblogic.lifecycle_1.1.0.0.jar;C:\bea2\modules\com.bea.core.store_1.4.0.0.jar;C:\bea2\modules\com.bea.core.store.gxa_1.4.0.0.jar;C:\bea2\modules\com.bea.core.store.admintool_1.1.0.0.jar;C:\bea2\modules\com.bea.core.store.jdbc_1.1.0.0.jar;C:\bea2\modules\com.bea.core.transaction_2.5.0.0.jar;C:\bea2\modules\com.bea.core.utils.agent_1.0.0.0.jar;C:\bea2\modules\com.bea.core.utils.classloaders_1.4.0.0.jar;C:\bea2\modules\com.bea.core.utils.compiler_1.0.0.0.jar;C:\bea2\modules\com.bea.core.utils.expressions_1.3.0.0.jar;C:\bea2\modules\com.bea.core.utils.wrapper_1.3.0.0.jar;C:\bea2\modules\com.bea.core.timers_1.4.0.0.jar;C:\bea2\modules\com.bea.core.workarea_1.4.0.0.jar;C:\bea2\modules\com.bea.core.xml.weblogic.xpath_1.1.0.0.jar;C:\bea2\modules\com.bea.core.jatmi_1.2.0.3.jar;C:\bea2\modules\com.bea.core.weblogic.security_1.0.0.0_5-0-2-0.jar;C:\bea2\modules\com.bea.core.weblogic.security.auth_1.0.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.security.digest_1.0.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.security.identity_1.1.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.security.logger_1.1.0.0.jar;C:\bea2\modules\com.bea.core.nodemanager.plugin_1.2.0.0.jar;C:\bea2\modules\com.bea.core.jmspool_1.4.0.0.jar;C:\bea2\modules\com.bea.core.compat.wl.90_1.1.0.0.jar;C:\bea2\modules\com.bea.core.http.pubsub.mbean_1.2.0.0.jar;C:\bea2\modules\com.bea.core.weblogic.web.api_1.2.0.0.jar;C:\bea2\modules\com.bea.core.redef_1.1.0.0.jar;C:\bea2\modules\com.bea.core.redefagent_1.1.0.0.jar;C:\bea2\modules\com.bea.core.redef.binding_1.1.0.0.jar;C:\bea2\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\bea2\wlserver_10.3\server\lib\schema\weblogic-domain-binding.jar;C:\bea2\wlserver_10.3\server\lib\schema\diagnostics-binding.jar;C:\bea2\wlserver_10.3\server\lib\schema\diagnostics-image-binding.jar;C:\bea2\wlserver_10.3\server\lib\wlcipher.jar;C:\bea2\wlserver_10.3\server\lib\webservices.jar;C:\bea2\wlserver_10.3\server\lib\xmlx.jar;C:\bea2\wlserver_10.3\server\lib\ojdbc6.jar;C:\bea2\wlserver_10.3\server\lib\jconn2.jar;C:\bea2\wlserver_10.3\server\lib\jconn3.jar;C:\bea2\wlserver_10.3\server\lib\jConnect.jar;C:\bea2\wlserver_10.3\server\lib\EccpressoAsn1.jar;C:\bea2\wlserver_10.3\server\lib\EccpressoCore.jar;C:\bea2\wlserver_10.3\server\lib\EccpressoJcae.jar;C:\bea2\wlserver_10.3\server\lib\mysql-connector-java-commercial-5.0.3-bin.jar;C:\bea2\wlserver_10.3\server\lib\wlbase.jar;C:\bea2\wlserver_10.3\server\lib\wlutil.jar;C:\bea2\wlserver_10.3\server\lib\wlsqlserver.jar;C:\bea2\wlserver_10.3\server\lib\wldb2.jar;C:\bea2\wlserver_10.3\server\lib\wlsybase.jar;C:\bea2\wlserver_10.3\server\lib\wloracle.jar;C:\bea2\wlserver_10.3\server\lib\wlinformix.jar;C:\bea2\wlserver_10.3\server\lib\wlw-langx.jar;C:\bea2\wlserver_10.3\common\lib;C:\bea2\modules\com.bea.cie.plugin-wizard_2.1.2.0.jar;C:\bea2\modules\com.bea.cie.plugin_2.1.0.0.jar;C:\bea2\modules\com.bea.cie.comdev_5.9.0.0.jar;C:\bea2\modules\com.bea.cie.xmldh_2.2.0.0.jar;C:\bea2\modules\com.bea.cie.gpr_2.8.0.0.jar;C:\bea2\modules\com.bea.cie.gpr-impl_2.8.0.0.jar;C:\bea2\modules\com.bea.cie.wizard_5.6.0.0.jar;C:\bea2\wlserver_10.3\common\lib\oxy-cci.jar;C:\bea2\modules\com.bea.cie.config_5.2.0.0.jar;C:\bea2\modules\com.bea.cie.wlw-plaf_5.2.0.0.jar;C:\bea2\modules\com.bea.cie.common-plugin_2.2.0.0.jar;C:\bea2\wlserver_10.3\common\lib\pdev.jar;C:\bea2\wlserver_10.3\server\lib\wlw-system.jar;C:\bea2\wlserver_10.3\server\lib\jcom.jar;C:\bea2\wlserver_10.3\server\lib\weblogic.jar

Maybe you are looking for