App-v management server

Hi,
Anybody works with app-v management server?
Does it work the same way as App-v 4.6 management server? I preferred that concept: deploy an application to a user: it appears, remove it from a group: it dissapears.
App-v 5.0 with sccm 2012 (which we use now) lacks this possibility which I fail to understand.
Can we intergrate the management server with SCCM 2012?
Pls advise.
J.
Jan Hoedt

I believe apps are removed automatically when using the management server.
SCCM however does not. There is a workaround however:
http://www.vroom.cc/wordpress/index.php/uninstall-appv-5-0-package-automatically-from-an-user-based-collection
And a slightly different (better?) way:
http://sccmentor.wordpress.com/2013/11/15/creating-a-user-collection-based-on-users-not-in-a-ad-user-group
Dan Gough - UK App-V MVP
Blog: packageology.com
Twitter: @packageologist
LinkedIn

Similar Messages

  • App-v management server or SCCM 2012 integration?

    Hi,
    We are using App-V 5.0 integrated within SCCM 2012 for a while now but aren't happy with it.
    Hope was that in some update of sccm 2012 it would improve but it does not. That's why the idea arises to use the Ap-V management server again.
    Below a comparison of the two options, I was wondering what your opinion on this matter is.
    App-V via SCCM 2012:
    Pro:
    Full integration with SCCM 2012
    Contra:
    Dependency on SCCM 2012 client (when SCCM client doens’t work, App-V doesn’t work either)
    Slow responstimes before package arrives at user (SCCM needs to scan AD groups, SCCM client needs a policy refresh)
    App-V Management server:
    Pro:
    Deploy is also possible to computers as from App-V 5.0 management server
    http://virtualvibes.co.uk/enabling-computer-based-targeting-in-app-v-5-0/
    “the fact that we can now target machines instead of users when publishing packages”
    Fast respsonsetime: deploy & uninstall
    Automatic uninstall when user/computer isn’t member of AD group anymore
    Contra:
    Extra server needed
    Note: the migration from SCCM to the App-V Management server should be transparent, right? Unpublish existing packages via SCCM, publish via management server
    Please advise.
    J.
    Jan Hoedt
    Jan Hoedt

    How many data centres and sites are these RDS servers and desktops deployed across?
    If you read Rory's blog post, you'll get a sense of what the App-V Full Infrastructure's down sides are across multiple sites/DCs.
    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
    answer your question). This can be beneficial to other community members reading the thread.
    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
    Twitter:
    @stealthpuppy | Blog:
    stealthpuppy.com |
    The Definitive Guide to Delivering Microsoft Office with App-V

  • App-V Management server 5.0: deploy to pc?

     
    Hi,
    In App-V 4.6 management server, we deploy to users, I cannot see an option there either to deploy to computers (the tab “Access permissions” shows “Add and select the user groups”). Now we don’t have App-V 5.0 management server yet but
    we do have SCCM 2012 with App-V (not liking the integration at all, specifically for the reason of unpublishing App-v packages:
    http://henkhoogendoorn.blogspot.be/2013/07/configmgr-2012-sp1-with-app-v-50.html). So my question: can you deploy App-V packages with App-v 5.0 management server to computers? If no, is it documented somewhere?
    Thanks.
    J.
    Jan Hoedt

    Hi Jan,
    Yes you can use the App-V 5.0 Management Server to publish to computers aswell as users. The Management server console supports specifying a computer group for targeting. Make sure you enable global publishing on the client side too:
    http://virtualvibes.co.uk/enabling-computer-based-targeting-in-app-v-5-0/

  • Deploying BEA Portal App in Managed Server problems....

    Hello,
    I have a BEA portal application (exploded EAR) that I want to deploy in a managed server. I first created a regular portal domain (8.1 SP4). I then created a managed server via the console. When I went to deploy my portal application (in the console), I received an error indicating that the application was a Split Development Directory and that I would have to run the wlpackage Ant task against the application first. I ran the wlpackage ant task and it seemingly worked.
    I then used the wldeploy Ant task to deploy it in the managed server but got an error indicating that it could not find a JNDI name from one of the data sources. I went back to the console and targeted/deployed all of the default Connection Pools & Data Sources to the managed server thinking that was the reason the deploy failed.
    When I ran the wldeploy again I got the following error:
    Module: content.jar Error: Exception activating module: EJBModule(content.jar, status=PREPARED)
    Unable to deploy EJB: ValueBean from content.jar
    java.sql.SQLException: javax.naming.NameNotFoundException: While trying to lookup 'portalFrameworkPool; contentDataSource;weblogic.jdbc.jts.commercialPool' didn't find subcontext 'portalFrameworkPool;contentDataSource;weblogic' Resolved ; remaining name 'portalFrameworkPool;contentDataSource;weblogic/jdbc/jts/commercialPool'
    Has anyone run into this? Am I not suppose to deploy a portal application in a managed server?
    Any help would be greatly appreciated.
    Thanks - Peter Len

    Problem solved.......
    After targeting all the data sources and poolers to the managed server, I restarted the main domain but did not restart the managed server. After restarting the managed server all was well.
    Thanks - Peter

  • Deployment on managed server

    Problem deploying app on managed server:
    testEAR.ear is built using wlpackage ant task, but it still causes the exception
    while deploying
    on managed server:
    Exception:weblogic.management.ApplicationException: Application testEAR is packaged
    using
    the WebLogic Split Development Directory structure. The Split Development Directory
    structure
    can only be used in development environments with a single WebLogic Server. If
    you wish to
    deploy this application to a separate managed server or cluster, use the wlpackage
    ant task to
    create an exploded or archived EAR.
    build.xml part:
    <taskdef name="wlpackage" classname="weblogic.ant.taskdefs.build.WLPackageTask"
    classpathref="task.classpath"/>
    <target name = "package" description = "Create exploded or arhived AER" depends
    = "build">
         <wlpackage srcdir="test" destdir="." toFile="testEAR.ear"/>
    </target>
    Ant doesn't alerts any errros.
    What is the problem?

    Can you show me the output of jar tvf testEAR.ear?
    Also, please show me the Application snippet from your config.xml
    -- Rob
    vinni wrote:
    Problem deploying app on managed server:
    testEAR.ear is built using wlpackage ant task, but it still causes the exception
    while deploying
    on managed server:
    Exception:weblogic.management.ApplicationException: Application testEAR is packaged
    using
    the WebLogic Split Development Directory structure. The Split Development Directory
    structure
    can only be used in development environments with a single WebLogic Server. If
    you wish to
    deploy this application to a separate managed server or cluster, use the wlpackage
    ant task to
    create an exploded or archived EAR.
    build.xml part:
    <taskdef name="wlpackage" classname="weblogic.ant.taskdefs.build.WLPackageTask"
    classpathref="task.classpath"/>
    <target name = "package" description = "Create exploded or arhived AER" depends
    = "build">
         <wlpackage srcdir="test" destdir="." toFile="testEAR.ear"/>
    </target>
    Ant doesn't alerts any errros.
    What is the problem?

  • How to setup WebLogic Admin Server and Managed Server

    Hi,
    I working to setup a Weblogic admin and managed server but fail.
    May i know the correct steps to setup the system ?
    Tx.

    TX. I will proceed to upload more logs here later.
    Anyway I notice that after i follow the guide to setup the admin and managed server, I only able to access the web apps on admin server. I can not access web apps for managed server.
    I setup the admin server using port 7001 and managed server using port 7003 based on oracle guide.
    I found weird here. when I browse to http://adminserver:7001/apps, it works. But when i browse to http://managedserver:7003/apps it does not work.
    But funny thing is when i browse to http://adminserver:7003/apps, it works.
    I confuse that which configuration I have done is incorrect and have this result???
    besides that I notice that in the nodemanager setting...the listening address is set to localhost and it works. If i configure it to IP address, it will give me errors.
    Edited by: Wilson78 on Dec 22, 2008 12:29 PM

  • How to implement a singleton class across apps in a managed server}

    Hi ,
    I tried implementing a singleton class , and then invoking the same in a filter class.
    Both are then deployed as a web app (war file) in a managed server.
    I created a similar app , deployed the same as another app in the same managed server .
    I have a logger running which logs the singleton instances as well.
    But am getting two instances of the singleton class in the two apps - not the same .
    I was under the impression that , a singleton is loaded in the class loader level , and since all apps under the same managed server used the same JVM , singleton will only get initialized once.
    Am i missing something here ? or did i implement it wrong..?
    public class Test
       private static Test ref ;
       private DataSource X; 
       static int Y;
       long Z ;  
       private Test ()
          // Singleton
           Z= 100 ;
       public static synchronized Test getinstance()  throws NamingException, SQLException
          if(ref == null)
             ref = new Test() ;        
             InitialContext ic = new InitialContext();
             ref.X = (DataSource)ic.lookup ("jdbc/Views");
          return ref ;       
       public Object clone()throws CloneNotSupportedException
           throw new CloneNotSupportedException();
       public int sampleMethod (int X) throws SQLException
    public final class Filter implements Filter
         public void doFilter(ServletRequest request, ServletResponse response,FilterChain chain) throws IOException, ServletException
              try
                   Test ref = Test.getinstance();
                   log.logNow(ref.toString());
    }Edited by: Tom on Dec 8, 2010 2:45 PM
    Edited by: Tom on Dec 8, 2010 2:46 PM

    Tom wrote:
    Hi ,
    I tried implementing a singleton class , and then invoking the same in a filter class.
    Both are then deployed as a web app (war file) in a managed server.
    I created a similar app , deployed the same as another app in the same managed server .
    I have a logger running which logs the singleton instances as well.
    But am getting two instances of the singleton class in the two apps - not the same .Two apps = two instances.
    Basically by definition.
    >
    I was under the impression that , a singleton is loaded in the class loader level , and since all apps under the same managed server used the same JVM , singleton will only get initialized once. A class is loaded by a class loader.
    Any class loader that loads a class, by definition loads the class.
    A VM can have many class loaders. And far as I know every JEE server in existance that anyone uses, uses class loaders.
    And finally there might be a problem with the architecture/design of a JEE system which has two applications but which is trying to solve it with a singleton. That suggests a there might be concept problem with understanding what an "app" is in the first place.

  • How to create 2 Work Manager Apps on SMP Server (Agentry)

    Hi All,
    I encountered a problem with my SMP 2.3 SP3 in combination with Agentry  6.1.. and Work Manager 6.0.
    I have an already working version of WorkManger on my SMP Server on port 7003, but whenever I create another WorkManager version on a different port e.g. 7005 the SMP/Agentry Server displays the status STARTING but never finishes this processs state.
    The version of both Work Manager instances is the same, with the exception that the section [ANGEL Front End Ports] in the file Agentry.ini contains once the port 7003 and in the other file e.g. 7005.
    Has anyone a encountered a similar problem or is able to create two different WorkManager versions on the same AgentryServer?
    Regards,
    Thomas

    Hello Steve,
    thanks for your quick reply, the listenOn Port is at both applications the same I will fix that in a few seconds.
    the entry nonStandardJavaOptions is at both apps empty.
    the startup.log of the second application:
    14:16:58 03/19/2014: Starting server (64-bit Windows)
    14:16:58 03/19/2014: Administration client command port is 55086, status port is 55087
    14:16:58 03/19/2014: Looking for initial status connection...
    14:17:04 03/19/2014: Event: 0, 30, Admin client 10.33.160.94:55094 authenticated successfully.
    14:17:04 03/19/2014: Event: 0, 27, Admin client 10.33.160.94:55094 has connected
    14:17:04 03/19/2014: Reading system ini file.
    14:17:04 03/19/2014: ID: SAP Work Manager Server v6.0.0.0, Name: ???, Location: ???
    14:17:04 03/19/2014: Starting log file.
    14:17:04 03/19/2014: Loading message groups.
    14:17:04 03/19/2014: Starting threads.
    14:17:04 03/19/2014:    1 initial threads.  Threads will auto-scale.
    14:17:04 03/19/2014: Starting Server: Agentry v6.1.3.10212
    14:17:04 03/19/2014: Event: 0, 2, System Startup
    14:17:04 03/19/2014: Loading 1 front ends
    14:17:04 03/19/2014: Loading front end from angelvine.dll
    14:17:04 03/19/2014: ANGEL Front End: reading init files.
    14:17:04 03/19/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212
    14:17:04 03/19/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.
    14:17:04 03/19/2014: Event: 0, 2, Key pair loaded successfully.
    14:17:04 03/19/2014: Starting Server Agent.
    14:17:04 03/19/2014: Agentry: Starting threads.
    14:17:04 03/19/2014:    1 initial threads.  Threads will auto-scale.
    14:17:04 03/19/2014: Agentry: Adding messages.
    14:17:04 03/19/2014: Event: 1, 4, Agentry v6.1.3.10212
    14:17:04 03/19/2014: Loading 1 agents
    14:17:04 03/19/2014: Loading agent from ag3.dll
    14:17:04 03/19/2014: Starting Server
    14:17:04 03/19/2014: Server: reading ini file
    14:17:04 03/19/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll
    14:17:04 03/19/2014: SystemConnection-2: Reading configuration information.
    14:17:04 03/19/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.
    14:17:04 03/19/2014: HTTP-XML Back End: Initialized.
    14:17:04 03/19/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll
    14:17:05 03/19/2014: Initializing 1-Java from ag3javabe.dll
    14:17:05 03/19/2014: SystemConnection-1: Reading configuration information.
    14:17:05 03/19/2014: SystemConnection-1: Setting name to 'Java Back End'.
    14:17:05 03/19/2014: Java Back End: Initialized.
    14:17:05 03/19/2014: Java Back End: Java Virtual Machine loaded.
    14:17:08 03/19/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10200
    14:17:08 03/19/2014: Event: 23, 101, Java Back End: AJAPI JAR version 6.1.3.10200 does not match the version of the Agentry Server
    14:17:08 03/19/2014: Java Back End: Initialized.
    14:17:08 03/19/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.6.0_22, AJAPI version 5.0 build 6.1.3.10200)) from ag3javabe.dll
    14:17:08 03/19/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"
    14:17:08 03/19/2014: Event: 20, 152, Loading Production application definitions for default localization

  • Is it possible to Manage iOS apps with Lion Server

    I was wondering if anyone knows whether or not it's possible to manage (add and remove) iOS apps using Lion Server, specifically apps available via the app store rather than apps built for internal use? I can't seem to see a way of doing it using profile manager but was wondering if I was maybe missing something?
    Thanks

    The answer to this would appear to be no.

  • Problem: Deploy a web app from a managed server - Can someone answer:  Is this a bug?!

    We're running 6.0sp2 on both AIX and RedHat. Deploying or redeploying
    a web app to the managed server fails, works fine on the Admin server.
    War's work fine in the 'applications' dir. The browser fails with a
    404 on the managed server, with the following error in the log:
    ####<Aug 9, 2001 4:58:45 PM GMT> <Error> <J2EE> <szuinet5> <ect2>
    <ExecuteThread: '11'
    for queue: 'default'> <system> <> <160001> <Error deploying application
    DefaultWebApp
    ect2: Cannot deploy WebAppServletContext(4320491,DefaultWebAppect2) on
    ect2 because
    WebAppServletContext(2930053,DefaultWebApp_ect2) is already registered
    for path >
    Are we missing the point here? Or, is this a known bug? Also, we are
    not in a position to jump onto v6.1 at this time.
    Thanks in advance.

    Hi,
    Yes..it's a bug. I had the same problem and it has been reported to support
    but no indication if it's fixed.
    Rgds,
    E-Wan
    ppower wrote:
    We're running 6.0sp2 on both AIX and RedHat. Deploying or redeploying
    a web app to the managed server fails, works fine on the Admin server.
    War's work fine in the 'applications' dir. The browser fails with a
    404 on the managed server, with the following error in the log:
    ####<Aug 9, 2001 4:58:45 PM GMT> <Error> <J2EE> <szuinet5> <ect2>
    <ExecuteThread: '11'
    for queue: 'default'> <system> <> <160001> <Error deploying application
    DefaultWebApp
    ect2: Cannot deploy WebAppServletContext(4320491,DefaultWebAppect2) on
    ect2 because
    WebAppServletContext(2930053,DefaultWebApp_ect2) is already registered
    for path >
    Are we missing the point here? Or, is this a known bug? Also, we are
    not in a position to jump onto v6.1 at this time.
    Thanks in advance.

  • Installing App-V 5.0 Management Server

    I'm attempting to install the App-V 5.0  Management Server and DB on a 2012 R2 VM, and I'm running into an interesting issue. The local SQL server, as well as the required .NET/IIS roles, have been installed already. When I launch the installer, I get
    to the "Management Server Configuration" screen without issue.
    Upon filling in the admin account, as well as the site name/port, I'm getting an "Active Directory information could not be retrieved. Please refer to the logs at [user_temp_path] for more information" error. Upon opening the App-V install
    logs, I don't see any new information:
    AppvUX: Active Directory information could not be retrieved. Please refer to the logs at [user_temp_path] for more information.
    AppvUX: The specified directory service attribute or value does not exist.
    There is also nothing of use in the Event Logs. I've also googled these error snippets for a day or two without finding anything helpful.
    I initially thought it was a permission issue, but the account I'm using to install has full administrative privileges on the server, as well as read access to all of Active Directory, so I'm not entirely sure that's the case. Just to make sure that it wasn't
    a machine-specific problem, I tested access to AD via both AdFind as well as using the ADUC snapin. I don't seem to have any issue querying AD from this box, EXCEPT for through the App-V installer.
    For completeness' sake, since App-V 5.0, supports Server 2008 R2 and up, I also tested this on a 2008 R2 and vanilla 2012 VM -- same error at the same point. At this juncture I'm fairly perplexed as to what the underlying issue is.
    Any ideas? Thanks in advance.

    Though I'm not sure if it reall would solve that issue, you could try to use my App_V SQL prep script from http://kirxblog.wordpress.com/2013/12/30/remote-db-for-app-v-5-revised/
    It would allow you to specify a group that should get 'full' access to the App-V database, and you could add your installing user and the App-V server's
    computer account to that group. (don't forget to restart the App-V server after adding it to the group).
    Falko
    Twitter
    @kirk_tn   |   Blog
    kirxblog   |   Web
    kirx.org   |   Fireside
    appvbook.com

  • Workshop App Works on Admin but Not On Managed Server

    Hi all, I have a very simple test Workshop App that works fine on an Admin server
    but not on a Managed Server. I have all the JMS and JDBC resources that the apps
    need, the console does not complain, they deploy fine, but for some reason I get
    exceptions when deployed to the Managed server but works fine on the Admin server.
    What's the difference between both servers? I start one with startWebLogic.cmd
    and the other one with startManageWebLogic.cmd in the same domain directory. The
    only resource that I have not been able to target to the managed server is WSStoreForwardInternalJMSServercgServer
    which I have no idea what it is or if it matters. Some portions of the app works
    when deployed to the managed server so I know it has deployed fine and some simple
    pages compile and work fine but when using certain JAR files in the lib directory
    I get weird exceptions on the managed server and not on the Admin server.
    I'd appreciate any help.
    Thanks, Jose

    Hi all, I have a very simple test Workshop App that works fine on an Admin server
    but not on a Managed Server. I have all the JMS and JDBC resources that the apps
    need, the console does not complain, they deploy fine, but for some reason I get
    exceptions when deployed to the Managed server but works fine on the Admin server.
    What's the difference between both servers? I start one with startWebLogic.cmd
    and the other one with startManageWebLogic.cmd in the same domain directory. The
    only resource that I have not been able to target to the managed server is WSStoreForwardInternalJMSServercgServer
    which I have no idea what it is or if it matters. Some portions of the app works
    when deployed to the managed server so I know it has deployed fine and some simple
    pages compile and work fine but when using certain JAR files in the lib directory
    I get weird exceptions on the managed server and not on the Admin server.
    I'd appreciate any help.
    Thanks, Jose

  • Problem when we created the managed server to configure different ports.

    I am trying to configure different ports for admin console and my communication service as we can’t share admin port to the outside world.
    So that only admin can access admin console using admin port.
    And out side clients can access my webapplication using different port.
    For this i have created the managed server in weblogic.and I deployed the application on managed server.
    Now admin server is running on 8001 port and my Communication Service application is running on 7001 port.
    But when I tried to configure MBeans related to myCommunicationServiceApplication those were disapper on admin console. And the other wlng services are appearing on admin console.
    1. Since my application deployed on managed server MBeans registration happened from myapplication hence it’s disappear on admin console.
    Now If I want to configure Mbeans (related to my communication service) how can I configure it?
    2. My communication service using configurationStore module and other wlng services.
    When I tried to start my application on managed server I got the below error:
    <Apr 28, 2009 12:22:44 PM IST> <Error> <Deployer> <BEA-149231> <dscp11166.TechMahindra.com> <Unable to set the activation state to true for the application 'wlng_nt_qualcomm_active_mediation [Version=1.0]'.
    com.bea.wlcp.wlng.api.storage.configuration.ConfigurationException: Configuration store module is not available.
    3. I tried to target all wlngResources to manged server by editing config.xml file.
    Then all wlng services disappears on admin console. If this is the case how can I configure container/account services on wlng?
    I have created the Basicweblogic domain.
    Below is the config.xml for reference.
    "QualcommServer" is managed server name.
    Can any one please suggest me how to configure this kind of scenarios?
    <server>
    <name>AdminServer</name>
    <machine>new_Machine_1</machine>
    <listen-port>8001</listen-port>
    <default-iiop-user>weblogic</default-iiop-user>
    <default-iiop-password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</default-iiop-password-encrypted>
    <listen-address>localhost</listen-address>
    </server>
    <server>
    <name>QualcommServer</name>
    <machine>new_Machine_1</machine>
    <listen-address>localhost</listen-address>
    <server-start>
    <java-vendor>Sun</java-vendor>
    <java-home>C:\Program Files\Java\jdk1.6.0</java-home>
    <class-path>C:\bea\wlng400\server\lib\weblogic.jar;C:\bea\wlng_pds400\lib\wlng\wlng.jar</class-path>
    <bea-home>C:\bea</bea-home>
    <username>weblogic</username>
    <password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</password-encrypted>
    </server-start>
    </server>
    <embedded-ldap>
    <name>managedserver</name>
    <credential-encrypted>{3DES}9q80YuFJueVVJxoWduJA1OGhbqk14EpgQWWyTrzlmxo=</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.0.1.0</configuration-version>
    <app-deployment>
    <name>wlng_nt_session#4.0</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>C:\bea\wlng400/applications/wlng_nt_session.ear</source-path>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>interceptors</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>C:\bea\wlng400/applications/interceptors.ear</source-path>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>wlng_prm</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>C:\bea\wlng400/applications/wlng_prm.ear</source-path>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>wlng_nt_qualcomm_active_mediation#1.0</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>servers\AdminServer\upload\wlng_nt_qualcomm_active_mediation.ear</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <machine>
    <name>new_Machine_1</name>
    <node-manager>
    <name>new_Machine_1</name>
    <listen-address>localhost</listen-address>
    </node-manager>
    </machine>
    <jms-server>
    <name>JMSServer-AdminServer</name>
    <target>AdminServer</target>
    </jms-server>
    <jms-system-resource>
    <name>WLNGJMSResource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jms/wlng-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <custom-resource>
    <name>networktier</name>
    <target>AdminServer</target>
    <descriptor-file-name>custom/nt.xml</descriptor-file-name>
    <resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngTierResource</resource-class>
    <descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean</descriptor-bean-class>
    </custom-resource>
    <custom-resource>
    <name>wlng-edr</name>
    <target>AdminServer</target>
    <descriptor-file-name>custom/wlng-edr.xml</descriptor-file-name>
    <resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngEdrResource</resource-class>
    <descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngEdrBean</descriptor-bean-class>
    </custom-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <jdbc-system-resource>
    <name>wlng.datasource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jdbc/wlng-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>wlng.localTX.datasource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jdbc/wlng-localTX-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    Thanks,
    Srinu Babu P

    Dear Nariharan,
    Today I faced a simlar issue, and this SAP Note helped me fix it: 1966807 - Duplication of AET table records in change processing
    In my case, cardinality of AET table was 1:1, and I was getting duplicate PARENT_ID every time when trying to create a subsequent service request for my activity.
    Regards,
    Andrew

  • Error in Starting OER Managed server on WEBLOGIC 11g..Linux OEL 4.7

    Hi All,
    While starting the OER managed server from linux server kde console we are getting started with the the following error ..
    Pls provide any pointers in resolving the issue...
    <Jun 22, 2010 8:35:19 PM IST> <Warning> <HTTP> <BEA-101369> <ServletContext@32289202[app:oer module:/oer path:/oer spec-version:null]: The encoding jsp-descriptor param has been deprecated. Consider declaring the encoding in the jsp-configelement (web.xml) or as a page directive (pageEncoding) instead.>
    Jun 22, 2010 8:35:22 PM oracle.as.jmx.framework.LoggerHelper log
    SEVERE: Error when parsing mbeans.xml file.
    java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl cannot be cast to javax.xml.parsers.DocumentBuilderFactory
    at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
    at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
    at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
    at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
    at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
    at oracle.as.jmx.framework.wls.
    Regards,
    Ramnath

    Hi,
    Thanks for the input but modifying xercesImpl jar version did not work out
    Extact error I am getting:
    <Sep 30, 2010 6:37:11 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Sep 30, 2010 6:37:15 PM IST> <Warning> <HTTP> <BEA-101369> <ServletContext@167504850[app:oer module:/oer path:/oer spec-version:null]: The encoding jsp-descriptor param has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.>
    Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
    SEVERE: Error when parsing mbeans.xml file.
    java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
         ... 1 more
    Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
    WARNING: Error parsing MBean descriptor file "/u01/app/ora11g/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/mbeans/webservices.mgmt-mbeans.xml".
    java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
         ... 1 more
    Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
    SEVERE: Error when parsing mbeans.xml file.
    java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
         at java.lang.Thread.run(Thread.java:619)
    Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
    WARNING: Error parsing MBean descriptor file "/u01/app/ora11g/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/mbeans/soa-mbeans.xml".
    java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
         ... 1 more
    Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
    SEVERE: Error when parsing mbeans.xml file.
    java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
         ... 1 more
    Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
    WARNING: Error parsing MBean descriptor file "/u01/app/ora11g/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/mbeans/dfw_mbeans.xml".
    java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
         ... 1 more
    Sep 30, 2010 6:37:32 PM oracle.as.jmx.framework.LoggerHelper log
    SEVERE: Error when parsing mbeans.xml file.
    java.lang.InstantiationException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:227)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:305)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:988)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:983)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
         at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:123)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.parseSource(ApplicationMBeans.java:174)
         at oracle.as.jmx.framework.generic.spi.config.ApplicationMBeans.<init>(ApplicationMBeans.java:146)
         at oracle.as.jmx.framework.generic.spi.BaseJMXFrameworkProviderImpl.getConfigObjectMBeanAssociationInfo(BaseJMXFrameworkProviderImpl.java:196)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2380)
         at oracle.as.jmx.framework.PortableMBeanFactory.getConfigObjectMBeanAssociationInfo(PortableMBeanFactory.java:2310)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseAndRegister(ComponentMBeans.java:153)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.parseDescriptors(ComponentMBeans.java:206)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerDomainLevelMBeans(ComponentMBeans.java:291)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:312)
         at oracle.as.jmx.framework.wls.spi.ComponentMBeans.registerMBeans(ComponentMBeans.java:306)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2$1.run(JMXFrameworkProviderImpl.java:990)
         at oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl$2.run(JMXFrameworkProviderImpl.java:996)
         ... 1 more
    INITIALIZING EXTERNAL EVENTING
    running in single server mode
    Intializing Thinkmap Server. Version: 2.6.051122173836X
    Thinkmap Server initialized.
    OER: Asset Preload completed: 8929ms
    <Sep 30, 2010 6:37:56 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Sep 30, 2010 6:37:57 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Sep 30, 2010 6:37:58 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Sep 30, 2010 6:37:58 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.195.79:7101 for protocols iiop, t3, ldap, snmp, http.>
    <Sep 30, 2010 6:37:58 PM IST> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "oer_server1" for domain "base_domain" running in Development Mode>
    <Sep 30, 2010 6:38:00 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Sep 30, 2010 6:38:00 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

  • Unable to start the managed server on OBIEE11.1.1.6.0, Oracle RTD exception

    Hi
    I am unable to start the Managed server on OBIEE 11.1.1.6.0 , as it is giving the following exception
    "[bi_server1] [NOTIFICATION] [] [oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor] [tid: RTD_Worker_9] [userId: <anonymous>] [ecid: 0000JxpZwaCDkZ__xPWByW1Hm1HW000001,1:23440] [APP: OracleRTD#11.1.1] [WSM_POLICY_NAME: oracle/wss_username_token_client_policy] Recipient Alias property not configured in the policy. Defaulting to encrypting with signers certificate.
    Here I am providing the bi_server1.log, bi_server1.out log,bi_server1-diagnostic.log
    Please suggest me workaround to resolve this issue,
    thanks in advance
    Pavan
    bi_server1.log
    ==========
    ####<Jun 24, 2013 12:41:40 PM AST> <Info> <WebLogicServer> <10.11.34.111> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1372066900822> <BEA-000000> <WebLogic Server "bi_server1" version:
    WebLogic Server 10.3.5.0  Fri Apr 1 20:20:06 PDT 2011 1398638  Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
    ####<Jun 24, 2013 12:41:40 PM AST> <Notice> <Log Management> <10.11.34.111> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1372066900902> <BEA-170019> <The server log file /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/logs/bi_server1.log is opened. All server side log events will be written to this file.>
    ####<Jun 24, 2013 12:41:40 PM AST> <Info> <Log Management> <10.11.34.111> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1372066900906> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Jun 24, 2013 12:41:40 PM AST> <Info> <Diagnostics> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066900981> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901098> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901098> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901099> <BEA-002622> <The protocol "http" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901099> <BEA-002622> <The protocol "https" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901100> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901101> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901102> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901102> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901106> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901107> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901109> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901109> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901109> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <RJVM> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901133> <BEA-000570> <Network Configuration for Channel "bi_server1"
    Listen Address   :9704
    Public Address   N/A
    Http Enabled   true
    Tunneling Enabled  false
    Outbound Enabled  false
    Admin Traffic Enabled  true>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901212> <BEA-002609> <Channel Service initialized.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901243> <BEA-000415> <System has file descriptor limits of - soft: 4,096, hard: 4,096>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901243> <BEA-000416> <Using effective file descriptor limit of: 4,096 open sockets/files.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901244> <BEA-000406> <PosixSocketMuxer was built on Jan 10 2008 23:07:45>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901301> <BEA-000436> <Allocating 4 reader threads.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901302> <BEA-000446> <Native IO Enabled.>
    ####<Jun 24, 2013 12:41:41 PM AST> <Info> <IIOP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901427> <BEA-002014> <IIOP subsystem enabled.>
    ####<Jun 24, 2013 12:41:47 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066907382> <BEA-090894> <Successfully loaded the OPSS Policy Provider using oracle.security.jps.internal.policystore.JavaPolicyProvider.>
    ####<Jun 24, 2013 12:41:47 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066907849> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Jun 24, 2013 12:41:48 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066908041> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_LVk1d2v3EBrlDS/rSIpIRiGgLnM=>
    ####<Jun 24, 2013 12:41:48 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066908346> <BEA-090516> <The RoleMapper provider has preexisting LDAP data.>
    ####<Jun 24, 2013 12:41:48 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066908755> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    ####<Jun 24, 2013 12:41:49 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909006> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
    ####<Jun 24, 2013 12:41:49 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909180> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server bi_server1 for security realm myrealm.>
    ####<Jun 24, 2013 12:41:49 PM AST> <Notice> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909181> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Jun 24, 2013 12:41:49 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909747> <BEA-002622> <The protocol "[iiop, ldap, http, https, ldaps, cluster-broadcast, admin, iiops, t3s, cluster-broadcast-secure, snmp, t3]" is now configured.>
    ####<Jun 24, 2013 12:41:49 PM AST> <Info> <XML> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909759> <BEA-130036> <Initializing XMLRegistry.>
    ####<Jun 24, 2013 12:41:49 PM AST> <Info> <messaging.interception> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909771> <BEA-400000> <Initializing message interception service>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <Store> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910180> <BEA-280008> <Opening the persistent file store "_WLS_bi_server1" for recovery: directory=/app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/data/store/default requestedWritePolicy="Direct-Write" fileLockingEnabled=true driver="wlfileio3".>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <Store> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910314> <BEA-280009> <The persistent file store "_WLS_bi_server1" (fb352aa7-3e6f-4655-b314-8b2cf7d9caa3) has been opened: blockSize=4,096 actualWritePolicy="Direct-Write(read-buffered)" explicitIOEnforced=false records=109.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910462> <BEA-001135> <Initializing the JDBC service.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910473> <BEA-001137> <Initialization complete.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910474> <BEA-001138> <Resuming the JDBC service.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910474> <BEA-001140> <Resume complete.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <Connector> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910507> <BEA-190000> <Initializing J2EE Connector Service......>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <Connector> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910510> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910593> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910637> <BEA-040090> <Deployed 8 default connection factories.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910638> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory2" with its JNDI name "weblogic.jms.XAConnectionFactory2" is started.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910638> <BEA-040407> <Default connection factory "MessageDrivenBeanConnectionFactory" with its JNDI name "weblogic.jms.MessageDrivenBeanConnectionFactory" is started.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910639> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory" with its JNDI name "weblogic.jms.XAConnectionFactory" is started.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910639> <BEA-040407> <Default connection factory "DefaultConnectionFactory" with its JNDI name "weblogic.jms.ConnectionFactory" is started.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910639> <BEA-040407> <Default connection factory "QueueConnectionFactory" with its JNDI name "javax.jms.QueueConnectionFactory" is started.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910640> <BEA-040407> <Default connection factory "TopicConnectionFactory" with its JNDI name "javax.jms.TopicConnectionFactory" is started.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910640> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory0" with its JNDI name "weblogic.jms.XAConnectionFactory0" is started.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910640> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory1" with its JNDI name "weblogic.jms.XAConnectionFactory1" is started.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910641> <BEA-040306> <JMS service is active now.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <HTTP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910680> <BEA-101128> <Initializing HTTP services.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <HTTP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910697> <BEA-101135> <bi_server1 is the default Web server.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <HTTP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910697> <BEA-101052> <[HttpServer (defaultWebserver) name: bi_server1] Initialized>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <HTTP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910700> <BEA-101129> <Initializing the Web application container.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910746> <BEA-180046> <INFO: Logging service enabled.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910749> <BEA-180046> <INFO: TC Configuration Helper instantiated!>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910750> <BEA-180046> <INFO: TC Task Manager instantiated!>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910753> <BEA-180046> <INFO: TC security service instantiated!>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910756> <BEA-180046> <INFO: TC Outbound routing service instantiated!>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910758> <BEA-180046> <INFO: TC Transaction service instantiated!>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <WebService> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910770> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <WebService> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910771> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMX> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910888> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://10.11.34.111:9704/jndi/weblogic.management.mbeanservers.runtime .>
    ####<Jun 24, 2013 12:41:50 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910904> <BEA-000256> <Invoking oracle.jrf.wls.JRFStartup.main(null)>
    ####<Jun 24, 2013 12:41:51 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066911658> <BEA-000256> <Invoking oracle.security.jps.wls.JpsWlsStartupClass.main(null)>
    ####<Jun 24, 2013 12:41:51 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066911696> <BEA-000256> <Invoking oracle.core.ojdl.weblogic.ODLConfiguration.main(null)>
    ####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912880> <BEA-000256> <Invoking oracle.jrf.AppContextStartup.main(null)>
    ####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912883> <BEA-000256> <Invoking oracle.as.jmx.framework.wls.spi.StartupListener.main(null)>
    ####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912942> <BEA-000256> <Invoking oracle.j2ee.ws.server.WebServiceServerStartup.main(null)>
    ####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912956> <BEA-000256> <Invoking oracle.ias.cache.Startup.main(null)>
    ####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912959> <BEA-000256> <Invoking oracle.dms.wls.DMSStartup.main(null)>
    ####<Jun 24, 2013 12:41:53 PM AST> <Info> <Management> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066913225> <BEA-141278> <Java entropy configuration is: System property "java.security.egd= null"; JRE's java.security file property "securerandom.source= null"; Assumed Blocking Config= true; JDK version= 1.6.0; Operating System= AIX.>
    ####<Jun 24, 2013 12:41:53 PM AST> <Info> <Management> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066913226> <BEA-141279> <Detected BLOCKING java entropy configuration. This is the most secure setting, but may cause performance issues on machines with few sources of entropy.>
    ####<Jun 24, 2013 12:41:53 PM AST> <Info> <Management> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066913228> <BEA-141187> <Java system properties are defined as follows:
    EPM_ORACLE_HOME = /app1/orabi/Oracle/Middleware/Oracle_BI1
    EPM_ORACLE_INSTANCE = novalue
    EPM_REG_PROPERTIES_PATH = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig
    HYPERION_HOME = /app1/orabi/Oracle/Middleware/Oracle_BI1
    XDO_FONT_DIR = /app1/orabi/Oracle/Middleware/Oracle_BI1/common/fonts
    bi.oracle.home = /app1/orabi/Oracle/Middleware/Oracle_BI1
    com.ibm.cpu.endian = big
    com.ibm.oti.configuration = scar
    com.ibm.oti.jcl.build = 20110622_1654
    com.ibm.oti.shared.enabled = false
    com.ibm.oti.vm.bootstrap.library.path = /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64
    com.ibm.oti.vm.library.version = 24
    com.ibm.vm.bitmode = 64
    common.components.home = /app1/orabi/Oracle/Middleware/oracle_common
    domain.home = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1
    em.oracle.home = /app1/orabi/Oracle/Middleware/oracle_common
    epm.useApplicationContextId = false
    file.encoding = utf-8
    file.separator = /
    hyperion.home = /app1/orabi/Oracle/Middleware/Oracle_BI1
    ibm.signalhandling.rs = false
    ibm.signalhandling.sigchain = true
    ibm.signalhandling.sigint = true
    ibm.system.encoding = ISO8859-1
    igf.arisidbeans.carmlloc = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig/carml
    igf.arisidstack.home = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig/arisidprovider
    java.assistive = ON
    java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
    java.awt.headless = true
    java.awt.printerjob = sun.print.PSPrinterJob
    java.class.path = /app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/app1/orabi/Oracle/Middleware/Oracle_BI1/bifoundation/jdbc/jdk16/bijdbc.jar::/app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java6_64/lib/tools.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/app1/orabi/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/app1/orabi/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/app1/orabi/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.dms_11.1.1/dms.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jmx_11.1.1/jmxframework.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jmx_11.1.1/jmxspi.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.odl_11.1.1/ojdl.jar:/app1/orabi/Oracle/Middleware/oracle_common/soa/modules/commons-cli-1.1.jar:/app1/orabi/Oracle/Middleware/oracle_common/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar:/app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java6_64/lib/tools.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/app1/orabi/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/app1/orabi/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/app1/orabi/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/app1/orabi/Oracle/Middleware
    java.class.version = 50.0
    java.compiler = j9jit24
    java.endorsed.dirs = /usr/java6_64/jre/lib/endorsed
    java.ext.dirs = /usr/java6_64/jre/lib/ext
    java.fullversion = JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr9-20110624_85526 (JIT enabled, AOT enabled)
    J9VM - 20110624_085526
    JIT  - r9_20101028_17488ifx17
    GC   - 20101027_AA
    java.home = /usr/java6_64/jre
    java.io.tmpdir = /tmp/
    java.jcl.version = 20110530_01
    java.library.path = /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64/j9vm:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/../lib/ppc64:/app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/native:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/native:/usr/java6_64/jre/lib/ppc64/j9vm:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/../lib/ppc64:/app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/native:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/native:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64:/usr/lib:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64:/usr/lib:/usr/lib
    java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
    java.naming.factory.url.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
    java.protocol.handler.pkgs = oracle.mds.net.protocol|weblogic.net
    java.runtime.name = Java(TM) SE Runtime Environment
    java.runtime.version = pap6460sr9fp2-20110627_03 (SR9 FP2)
    java.security.policy = /app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Sun Microsystems Inc.
    java.specification.version = 1.6
    java.util.logging.config.class = oracle.core.ojdl.logging.LoggingConfiguration
    java.util.prefs.PreferencesFactory = java.util.prefs.FileSystemPreferencesFactory
    java.vendor = IBM Corporation
    java.vendor.url = http://www.ibm.com/
    java.version = 1.6.0
    java.vm.info = JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr9-20110624_85526 (JIT enabled, AOT enabled)
    J9VM - 20110624_085526
    JIT  - r9_20101028_17488ifx17
    GC   - 20101027_AA
    java.vm.name = IBM J9 VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Sun Microsystems Inc.
    java.vm.specification.version = 1.0
    java.vm.vendor = IBM Corporation
    java.vm.version = 2.4
    javax.management.builder.initial = weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
    javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
    javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
    javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
    javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
    jrf.version = 11.1.1
    jrockit.optfile = /app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt
    jxe.current.romimage.version = 15
    jxe.lowest.romimage.version = 15
    oracle.biee.search.bisearchproperties = /app1/orabi/Oracle/Middleware/Oracle_BI1/bifoundation/jee/BISearchConfig.properties
    oracle.core.ojdl.logging.applicationcontextprovider = oracle.core.ojdl.logging.WlsApplicationContextImpl
    oracle.core.ojdl.logging.componentId = bi_server1
    oracle.core.ojdl.logging.config.file = /app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.ovd_11.1.1/templates/ovd-logging.xml
    oracle.core.ojdl.logging.usercontextprovider = oracle.core.ojdl.logging.WlsUserContextImpl
    oracle.deployed.app.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/tmp/_WL_user
    oracle.deployed.app.ext = /-
    oracle.domain.config.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig
    oracle.ecsf.configuration.class = oracle.biee.search.services.BISearchServiceConfiguration
    oracle.ecsf.security.service = oracle.biee.search.security.BISearchSecurityService
    oracle.notification.filewatching.interval = 2000
    oracle.security.jps.config = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig/jps-config.xml
    oracle.server.config.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig/servers/bi_server1
    org.apache.commons.logging.Log = org.apache.commons.logging.impl.Jdk14Logger
    org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
    org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
    org.xml.sax.driver = weblogic.xml.jaxp.RegistryXMLReader
    org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
    os.arch = ppc64
    os.encoding = ISO8859-1
    os.name = AIX
    os.version = 6.1
    path.separator = :
    platform.home = /app1/orabi/Oracle/Middleware/wlserver_10.3
    rtd.instanceName = RTD_bi_server1
    server.group = obi
    sun.arch.data.model = 64
    sun.boot.class.path = /usr/java6_64/jre/lib/ppc64/default/jclSC160/vm.jar:/usr/java6_64/jre/lib/annotation.jar:/usr/java6_64/jre/lib/beans.jar:/usr/java6_64/jre/lib/java.util.jar:/usr/java6_64/jre/lib/jndi.jar:/usr/java6_64/jre/lib/logging.jar:/usr/java6_64/jre/lib/security.jar:/usr/java6_64/jre/lib/sql.jar:/usr/java6_64/jre/lib/ibmorb.jar:/usr/java6_64/jre/lib/ibmorbapi.jar:/usr/java6_64/jre/lib/ibmcfw.jar:/usr/java6_64/jre/lib/rt.jar:/usr/java6_64/jre/lib/charsets.jar:/usr/java6_64/jre/lib/resources.jar:/usr/java6_64/jre/lib/ibmpkcs.jar:/usr/java6_64/jre/lib/ibmcertpathfw.jar:/usr/java6_64/jre/lib/ibmjgssfw.jar:/usr/java6_64/jre/lib/ibmjssefw.jar:/usr/java6_64/jre/lib/ibmsaslfw.jar:/usr/java6_64/jre/lib/ibmjcefw.jar:/usr/java6_64/jre/lib/ibmjgssprovider.jar:/usr/java6_64/jre/lib/ibmjsseprovider2.jar:/usr/java6_64/jre/lib/ibmcertpathprovider.jar:/usr/java6_64/jre/lib/ibmxmlcrypto.jar:/usr/java6_64/jre/lib/management-agent.jar:/usr/java6_64/jre/lib/xml.jar:/usr/java6_64/jre/lib/jlm.jar:/usr/java6_64/jre/lib/javascript.jar
    sun.boot.library.path = /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64
    sun.io.unicode.encoding = UnicodeBig
    sun.java.command = weblogic.Server
    sun.java.launcher = SUN_STANDARD
    sun.jnu.encoding = ISO8859-1
    user.country = US
    user.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1
    user.home = /home/orabi
    user.language = en
    user.name = orabi
    user.timezone = Asia/Riyadh
    vde.home = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/data/ldap
    weblogic.MaxMessageSize = 50000000
    weblogic.Name = bi_server1
    weblogic.ProductionModeEnabled = true
    weblogic.ReverseDNSAllowed = false
    weblogic.alternateTypesDirectory = /app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1
    weblogic.classloader.preprocessor = weblogic.diagnostics.instrumentation.DiagnosticClassPreProcessor
    weblogic.ext.dirs = /app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath
    weblogic.home = /app1/orabi/Oracle/Middleware/wlserver_10.3/server
    weblogic.jdbc.remoteEnabled = false
    weblogic.management.clearTextCredentialAccessEnabled = ********
    weblogic.management.discover = false
    weblogic.management.server = http://10.11.34.111:7001
    weblogic.nodemanager.ServiceEnabled = true
    weblogic.security.SSL.enableJSSE = true
    weblogic.security.SSL.ignoreHostnameVerification = true
    weblogic.security.TrustKeyStore = DemoTrust
    weblogic.system.BootIdentityFile = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/data/nodemanager/boot.properties
    wls.home = /app1/orabi/Oracle/Middleware/wlserver_10.3/server
    wlw.iterativeDev = false
    wlw.logErrorsToConsole = false
    wlw.testConsole = false
    xdo.server.config.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/bipublisher
    >
    ####<Jun 24, 2013 12:41:53 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066913766> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls_internal">
    ####<Jun 24, 2013 12:41:54 PM AST> <Notice> <WebLogicServer> <10.11.34.111> <bi_server1> <main> <<WLS Kernel>> <> <> <1372066914573> <BEA-000365> <Server state changed to STANDBY>
    ####<Jun 24, 2013 12:41:54 PM AST> <Notice> <WebLogicServer> <10.11.34.111> <bi_server1> <main> <<WLS Kernel>> <> <> <1372066914579> <BEA-000365> <Server state changed to STARTING>
    ####<Jun 24, 2013 12:41:54 PM AST> <Info> <SAFService> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914605> <BEA-281003> <SAF Service has been initialized.>
    ####<Jun 24, 2013 12:41:54 PM AST> <Info> <SAFService> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914612> <BEA-281002> <SAF Service has been started.>
    ####<Jun 24, 2013 12:41:54 PM AST> <Info> <WseeCore> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914622> <BEA-220502> <The Wsee Service is starting>
    ####<Jun 24, 2013 12:41:54 PM AST> <Info> <Deployer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914743> <BEA-149209> <Resuming.>
    ####<Jun 24, 2013 12:41:54 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914823> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls9_async_response">
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916264> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls_cluster_internal">
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916333> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls_deployment_internal">
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916428> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "EPMSystemRegistry">
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916440> <BEA-001177> <Creating Connection Pool named EPMSystemRegistry, URL = jdbc:oracle:thin:@ebspocapp:1521/EBPRD, Properties = user=DEV_BIPLATFORM;oracle.net.CONNECT_TIMEOUT=10000;.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <Common> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916455> <BEA-000626> <Free resources in pool "EPMSystemRegistry" will be tested every "300" seconds.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916577> <BEA-001124> <Created Connection Pool named EPMSystemRegistry.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916591> <BEA-001174> <Creating Data Source named EPMSystemRegistry, JNDI Name = jdbc/EPMSystemRegistry.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916642> <BEA-001512> <Data Source EPMSystemRegistry has been successfully created.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916644> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bip_datasource">
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916652> <BEA-001177> <Creating Connection Pool named bip_datasource, URL = jdbc:oracle:thin:@ebspocapp:1521/EBPRD, Properties = user=DEV_BIPLATFORM;oracle.net.CONNECT_TIMEOUT=10000;.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <Common> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916654> <BEA-000626> <Free resources in pool "bip_datasource" will be tested every "300" seconds.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916655> <BEA-001124> <Created Connection Pool named bip_datasource.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916656> <BEA-001174> <Creating Data Source named bip_datasource, JNDI Name = jdbc/bip_datasource.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916676> <BEA-001512> <Data Source bip_datasource has been successfully created.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916678> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "mds-owsm">
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916687> <BEA-001177> <Creating Connection Pool named mds-owsm, URL = jdbc:oracle:thin:@ebspocapp:1521/EBPRD, Properties = SendStreamAsBlob=true;user=DEV_MDS;oracle.net.CONNECT_TIMEOUT=10000;.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <Common> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916688> <BEA-000626> <Free resources in pool "mds-owsm" will be tested every "300" seconds.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916690> <BEA-001124> <Created Connection Pool named mds-owsm.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916691> <BEA-001174> <Creating Data Source named mds-owsm, JNDI Name = jdbc/mds/owsm.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916726> <BEA-001512> <Data Source mds-owsm has been successfully created.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916728> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "rtd_datasource">
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916735> <BEA-001177> <Creating Connection Pool named rtd_datasource, URL = jdbc:oracle:thin:@ebspocapp:1521/EBPRD, Properties = user=DEV_BIPLATFORM;oracle.net.CONNECT_TIMEOUT=10000;.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <Common> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916736> <BEA-000626> <Free resources in pool "rtd_datasource" will be tested every "300" seconds.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916738> <BEA-001124> <Created Connection Pool named rtd_datasource.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916740> <BEA-001174> <Creating Data Source named rtd_datasource, JNDI Name = SDDS.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916757> <BEA-001512> <Data Source rtd_datasource has been successfully created.>
    ####<Jun 24, 2013 12:41:56 PM AST> <Info> <Store> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916922> <BEA-280008> <Opening the persistent file store "BipJmsStore" for recovery: directory=/app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/BipJmsStore requestedWritePolicy="Direct-Write" fileLockingEnabled=true driver="wlfileio3".>
    ####<Jun 24, 2013 12:41:57 PM AST> <Info> <Store> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917017> <BEA-280009> <The persistent file store "BipJmsStore" (68f997df-e4a0-4eb1-9497-8d994726f787) has been opened: blockSize=4,096 actualWritePolicy="Direct-Write(read-buffered)" explicitIOEnforced=false records=16.>
    ####<Jun 24, 2013 12:41:57 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917027> <BEA-040321> <JMSServer "BipJmsServer" is resuming.>
    ####<Jun 24, 2013 12:41:57 PM AST> <Info> <Messaging> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917092> <BEA-282003> <The messaging kernel BipJmsServer will use up to 536,870,912 bytes of memory before paging begins>
    ####<Jun 24, 2013 12:41:57 PM AST> <Info> <Messaging> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917115> <BEA-282001> <The messaging kernel BipJmsServer is beginning recovery of its persistent state>
    ####<Jun 24, 2013 12:41:57 PM AST> <Info> <Messaging> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917158> <BEA-282002> <The messaging kernel BipJmsServer has recovered 0 persistent messages>
    ####<Jun 24, 2013 12:41:57 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917200> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "BipJmsResource">
    ####<Jun 24, 2013 12:41:57 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917408> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Burst.Job.Q" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921006> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Burst.Report.Q" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921044> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.Email.Q" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921063> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.File.Q" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921078> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.FTP.Q" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921091> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.Print.Q" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921107> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.WebDAV.Q" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921125> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.Fax.Q" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921143> <BEA-040406> <Distributed destination "BipJmsResource!BIP.System.T" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921170> <BEA-040108> <User connection factory "BipJmsResource!BIP.JMS.CF" is started.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921185> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "Module-FMWDFW">
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <Diagnostics> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921232> <BEA-320114> <Initializing the Diagnostics Harvester.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <Diagnostics> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921241> <BEA-320117> <The Harvester is being disabled because there are no Harvestable types configured specified.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <Diagnostics> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921245> <BEA-320119> <The Harvester is now in a inactive state.>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921715> <BEA-160151> <Registered library Extension-Name: UIX, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (WAR).>
    ####<Jun 24, 2013 12:42:01 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921841> <BEA-160151> <Registered library Extension-Name: adf.oracle.businesseditor, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Jun 24, 2013 12:42:02 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066922111> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (EAR).>
    ####<Jun 24, 2013 12:42:02 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066922334> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain.webapp, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
    ####<Jun 24, 2013 12:42:02 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066922391> <BEA-160151> <Registered library Extension-Name: bithirdparty, Specification-Version: 11.1.1 (JAR).>
    ####<Jun 24, 2013 12:42:02 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <13

    Hi,
    I tried starting the server from the console as well as from command prompt. Here I am giving the command below.
    nohup ./startManagedWebLogic.sh bi_server1 t3://machineIP:portNo > bis1_startup.log &
    But each time I got the same exception.
    Korandla

Maybe you are looking for