OSB deployment on managed server

Hello,
We have a OSB clustered environment where managed servres and admin server reside on separate machines. OSB admin server does not have access to database (The architecture does not allow Admin server to connect to DB). As far as my understanding OSB applications/projects have to be targeted on Admin server for deployment even the SB console is accessible via admin server.
How can we use the Oracle OSB WLST deployment scripts for target on the managed servers currently this works only when pointed to the Admin sserver.
If WLSTscript is pointed to the managed server the deployment script throws exception stating 'cannot start Mbean server'
Your help on this greatly appreciated.
Thanks,
P

Hi Prashant,
OSB apps don't have to be necessary targeted to Admin server. In our project OSB apps are targeted to OSB managed server.
I think reason why you can't deploy it in your case is that there are no OSB components deployed in Admin server. Those components are
deployed to admin server during the installation even if you choose install OSB to separate OSB managed server (they are deployed to both admin and OSB managed servers). I think that's OSB design issue.
During our deployment we recreate domain including OSB apps every time from scratch. It works fine.
Regards,
Milan

Similar Messages

  • Migrate osb deployment from Admin Server to Managed Server

    Hi,
    I had create the OSB Development environment.
    Configuration was such that OSB was deployed to Admin Server.
    However, I have a new requirement, wish to deploy OSB to a Managed Server and no longer Admin Server, to reduce the load on Admin Server and for future high availability plans.
    I have created a Managed Server for OSB deployment. I was of the opinion that I should just simply use the console for deploying OSB to the newly created Managed Server.
    However, I seemed to have missed some steps and therefore OSB was not working.
    Kindly help me.
    Lammeki

    bobm53 wrote:
    Hi,
    look at this:
    http://www.oracle.com/technetwork/database/migration/sqlserver-095136.html
    About expected results from such db migration, I can only say that because all IDM objects (forms, wf, customizations etc) are stored on its waveset db, at the end of db migration, you should have same functionalities. Obviously you need to change (with lhconsole) the db iDM should refer to. This information is stored in a special (encrypted) xml file.
    HTHAnd don't forget that you also need to replace your JDBC driver (jar file) with the oracle JDBC driver and ensure it is in the classpath that LH and the appserver need.

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

  • Bea 9.2 : deployment to managed server failed (J2EE:160149)

    Hi,
    I am trying to deploy portal application to managed server instance. When i am deploying it to an admin server, deployment is fine but when i am deploying to managed server instance, it fails with following error:
    ********* log start ************
    [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: wlp-groupspace-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-collab-portlets-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-framework-full-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-commerce-tools-support-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-tools-support-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-webdav-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-tools-admin-app-lib, Specification-Version: 9.2, Implementation
    ********* log end **************
    Can you note that the it was fine when deployment was done to admin server.
    I am not sure whether i have set up the managed server instance in the proper way. This is what i did to set up managed server instance before deployment
    (1) create weblogic domain
    (2) create managed server listening at port 8001. (admin is at 7001)
    (3) created machine and in the node manager added the managed server to the machine just created.
    (4) started node manager through script, started admin server and started managed server by
    startManagedWebLogic.cmd managedserver admin_url
    => No errors so far. but now when i try to deploy portal application to managed server instance, it fails.
    Any pointers???
    (ps : can a moderator help me to move this message to the portal forum instead of here..thanx)
    Edited by tamugrg13 at 03/25/2007 8:09 PM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    don't worry about this. i have resolved this by deploying into a cluster. looks like BEA doesn't support non-clustered deployment to managed server instances.

  • How to deploy osb projects into managed server in weblogic

    i am new to osb
    i have a doubt
    i created a managed server in weblogic admin console, it was running fine ,but i need to know how to deploy my osb projects in that new manged server.As of now it is deployed in http://localhost:7001/sbconsole

    I think you need to extend the domain instead of creating the managed instance manually through Admin console. By default when you create a domain using OSB domain template, it deploys all of the applications needed automatically to all the instances. If you are trying to do it manually, then you need to follow the documentation to see which applications need to be deployed to use OSB services.
    http://docs.oracle.com/cd/E23943_01/doc.1111/e15017/configure_osb.htm#BGBFGBFF
    To deploy a project, Login to SB console http://<admin>:<port>/sbconsole > System Administration > Export/Import Resources.

  • OSB 10gR3 - Starting Managed server on remote machine

    I have 2 Windows 2003 Enterprise machines.
    I have OSB 10gR3 installed on both with Node Manager running on default port, on both.
    I create the servicebustutorial domain and start the admin server on the first machine.
    On the second machine, I use the WLST to
    <ul><li>connect('weblogic','password','t3://xxx.xxx.xxx.xxx:7001') # connect to admin server on first machine
    </li>
    <li>nmEnroll('c:/bea/wlserver_10.3/common/nodemanager') # make node manager visible
    </li>
    <li>nmEnroll('c:/bea/user_projects/domains/servicebustutorial') # enroll in the servicebustutorial</li>
    </ul>
    Now, I don't know if this is the correct thing to do.
    Back on the first machine, I create a new machine to represent the second Windows box.
    I can see the node manager on the second machine using the machine monitoring page.
    I then create a new server that is assigned to the new machine.
    I can attempt to start the new server on the second machine.
    The Server directory appears in the servers directory on the second windows box.
    Log files appear on the second box but the config.xml is not there, and thus, the server fails to start.
    I would have thought that the server config would have propogated from the admin server, is this a wrong assumption?
    What am I doing wrong?
    Thanks, in advance.
    ...Lyall

    Thanks for replying.
    I login as a local administrator on the machine that WebLogic runs. All operations are performed using that login (starting admin server, starting node manager).
    I changed permissions on C:\BEA, all the way down, localadmin group has full control, everywhere.
    I tried changing nodemanager C:\bea\wlserver_10.3\common\nodemanager\nodemanager.properties LogLevel to DEBUG but then NodeManager refuses to start, so I returned it back to INFO.
    I set debug on the Managed Server I am trying to setup, as you suggested.
    I even updated the NodeManager and Server boot.properties files to be cleartext and Deleted the LDAP directory within the Managed Server (as I assume it's re-created if it does not exist)
    Wow, heaps comes out, but the following may be relevant.
    In particular, this single line, causes concern.
    bq. ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE \\ ExecuteThread: '0' for queue: 'weblogic.kernel.Default \\ (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; \\ &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;[Security:090295 |http://forums.oracle.com//]caught unexpected exception&gt;
    It's an unexpected exception but it's not an Error and only reported as a Debug! I could be climbing up the wrong tree, but the following log output is what immediately precedes the login failure.
    bq.      ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820219&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.LoginModuleWrapper.wrap ClassLoader=java.net.URLClassLoader@1f0e58&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820219&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.LoginModuleWrapper.wrap ControlFlag=LoginModuleControlFlag: required&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820219&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.JAASLoginServiceImpl.login created LoginContext&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820219&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.JAASLoginServiceImpl.login ThreadContext ClassLoader Current=sun.misc.Launcher$AppClassLoader@124dfc&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820234&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.LoginModuleWrapper.initialize LoginModuleClassName=weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820234&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.LoginModuleWrapper.initialize ClassLoader=java.net.URLClassLoader@1f0e58&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820234&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.LoginModuleWrapper.initialize created delegate login module&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820234&gt; &lt;BEA-000000&gt; &lt;LDAP ATN LoginModule initialized&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820234&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.LoginModuleWrapper.initialize delegated&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820234&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.LoginModuleWrapper.login&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820250&gt; &lt;BEA-000000&gt; &lt;LDAP Atn Login&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820250&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.CallbackHandlerWrapper.handle&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820250&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[0] will be delegated&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820250&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[0] will use NameCallback to retrieve name&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820250&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[1] will be delegated&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820250&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.CallbackHandlerWrapper.handle will delegate all callbacks&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820250&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.CallbackHandlerWrapper.handle delegated callbacks&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820250&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.CallbackHandlerWrapper.handle got username from callbacks[0], UserName=weblogic&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820250&gt; &lt;BEA-000000&gt; &lt;LDAP Atn Login username: weblogic&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820281&gt; &lt;BEA-000000&gt; &lt;new LDAP connection to host 134.251.218.157 port 7001 use local connection is true&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820281&gt; &lt;BEA-000000&gt; &lt;created new LDAP connection LDAPConnection { ldapVersion:2 bindDN:""}&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;connection succeeded&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;getConnection return conn:LDAPConnection { ldapVersion:2 bindDN:""}&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;authenticate user:weblogic&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;getDNForUser search("ou=people,ou=myrealm,dc=Tester", "(&(uid=weblogic)(objectclass=person))", base DN & below)&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;[Security:090295|http://forums.oracle.com/forums/]caught unexpected exception&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.LoginModuleWrapper.commit&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;LDAP Atn Abort&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;com.bea.common.security.internal.service.LoginModuleWrapper.commit delegated, returning false&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityAtn&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.authenticate authenticate failed for user weblogic&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityUserLockout&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.isLocked(weblogic)&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityUserLockout&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820297&gt; &lt;BEA-000000&gt; &lt;weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic)&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityUserLockout&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820312&gt; &lt;BEA-000000&gt; &lt;weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic) UserLockout Login failure for user in realm myrealm&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityUserLockout&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820312&gt; &lt;BEA-000000&gt; &lt;weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.getInvaliLoginUsersHighCount()&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityUserLockout&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820312&gt; &lt;BEA-000000&gt; &lt;weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic) User weblogic has 1 failures in realm myrealm&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityUserLockout&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820312&gt; &lt;BEA-000000&gt; &lt;weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImplUserLockout InvalidLogin Record GC not needed&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityUserLockout&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820312&gt; &lt;BEA-000000&gt; &lt;weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic) UserLockout About to multicast login failure for user SecurityMessage realm:myrealm record:SecurityMulticastRecord: origin: Strategic realmName: myrealm seqnum: 1 timestamp: Mar 6, 2009 8:50:20 PM username: weblogic nextSeqNo:1&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Debug&gt; &lt;SecurityUserLockout&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820312&gt; &lt;BEA-000000&gt; &lt;weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImplUserLockout Can't create multicastSession because ClusterServices are unavailable&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Critical&gt; &lt;Security&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820312&gt; &lt;BEA-090402&gt; &lt;Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.&gt; \\     ####&lt;Mar 6, 2009 8:50:20 PM CST&gt; &lt;Critical&gt; &lt;WebLogicServer&gt; &lt;osb-strat&gt; &lt;Strategic&gt; &lt;Main Thread&gt; &lt;&lt;WLS Kernel&gt;&gt; &lt;&gt; &lt;&gt; &lt;1236334820312&gt; &lt;BEA-000386&gt; &lt;Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted. \\     weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted. \\     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source) \\     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source) \\     at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source) \\     at weblogic.security.SecurityService.start(SecurityService.java:141) \\     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) \\     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) \\     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) \\     &gt;

  • Partition not found- While deploying to managed server

    We are using 11gR1. We have configured a soa managed server. While deploying Sales demo application in BPM Studio, we set up connection to the Admin Server and when we test the connection it is successful. During the last step of deployment, where the SOA managed server is prompted, SOA server is listed properly but we get a message saying that partition is not available.
    We went to EM and found that there is a default partition, we also created a new partition and restarted both the servers. But still we face the same error. The Log gives the following information:
    <Error> <RepositoryPartitionModel.class> <BEA- 000000> <Getting Partitions>
    Is this a product bug or are we missing out on anything.
    Venkat

    Hi venkat,
    I am also having the same problem. Were you able to find out the solution for this issue. I currently manually deploy the GUI EAR from the admin console and the SAR file from the EM.
    Thanks,

  • Server Hangs when I tried to Access web Application that deployed in Managed Server

              Hai All!
              Here is my problem ! I started Admin Server and Managed server in a same machine.
              I deployed HttpClusterServlet in web.xml of Managed server. When i started servers
              they start fine and says Clustering started.... But when i tried to Access index.jsp
              that is in Managed Server default web application ..Nothing happens. It neither
              throws exception nor shows the desired page.. Seems to be Browser hang and server
              hang. At this stage i am unable to access Admin console also.(I can access before
              i tried index.jsp of managed server).. It seems to be Hang Allover..
              Pls suggest me how to come out of this hanging...
              Rgds
              Manohar
              

    See my answer to your last post. The short answer is that the HttpClusterServlet is
              likely to be the problem and not the cluster. You can try one of the web server plugins
              or a hardware load balancer as a temporary workaround. You should file a case with
              support too...
              Manu Kar wrote:
              > Hai All!
              >
              > Here is my problem ! I started Admin Server and Managed server in a same machine.
              > I deployed HttpClusterServlet in web.xml of Managed server. When i started servers
              > they start fine and says Clustering started.... But when i tried to Access index.jsp
              > that is in Managed Server default web application ..Nothing happens. It neither
              > throws exception nor shows the desired page.. Seems to be Browser hang and server
              > hang. At this stage i am unable to access Admin console also.(I can access before
              > i tried index.jsp of managed server).. It seems to be Hang Allover..
              >
              > Pls suggest me how to come out of this hanging...
              >
              > Rgds
              > Manohar
              

  • Unable to deploy to managed server - ExceptionInInitializerError

    I have a development/integration environment that lives on a single HP-UX server: two Weblogic domains, each containign an admin server and several managed servers. The machine is running a node manager process, and the node manager plus all servers are started via a WLST Python script (as recommended in the documentation).
    I have a seriously annoying issue whereby I cannot deploy any application, or data source, to a managed server unless that server is shut down. I get an 'ExceptionInInitializerError' any time I try. I can shut down the target server, install the deployment using the console, then start the server, and everything works great. Any insight is greatly appreciated.
    Version: Weblogic 10.3.0.0
    OS: HP-UX B.11.23 U ia64
    Stacktrace:
    ####<Nov 2, 2010 11:58:17 AM EDT> <Warning> <Deployer> <borg.abc.virginia.gov> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288713497985> <BEA-149004> <Failures were detected while initiating deploy task for application 'pta'.>
    ####<Nov 2, 2010 11:58:17 AM EDT> <Warning> <Deployer> <borg.abc.virginia.gov> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1288713497985> <BEA-149078> <Stack trace for message 149004
    java.lang.Exception: java.lang.ExceptionInInitializerError
         at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.includePrepareFailure(AdminRequestStatus.java:1418)
         at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.signalCancelFailed(AdminRequestStatus.java:1266)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.signalCancelCompletion(AwaitingCancelResponses.java:126)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.doCancelCompletionCheck(AwaitingCancelResponses.java:112)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.receivedCancelFailed(AwaitingCancelResponses.java:97)
         at weblogic.deploy.service.internal.adminserver.AdminRequestImpl.receivedCancelFailed(AdminRequestImpl.java:503)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveCancelFailedMsg(CommonMessageReceiver.java:295)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:779)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.ExceptionInInitializerError
         at weblogic.management.mbeans.custom.Domain.lookupTarget(Domain.java:247)
         at weblogic.management.configuration.DomainMBeanImpl.lookupTarget(DomainMBeanImpl.java:6139)
         at weblogic.deploy.internal.TargetHelper.lookupTargetMBeans(TargetHelper.java:183)
         at weblogic.management.deploy.DeploymentData.getAllTargetedServers(DeploymentData.java:413)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isTargetListContainsCurrentServer(AbstractOperation.java:644)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isDeploymentRequestValidForCurrentServer(AbstractOperation.java:854)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:206)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.NullPointerException
         at weblogic.management.mbeans.custom.AttributeAggregator.<init>(AttributeAggregator.java:36)
         at weblogic.management.mbeans.custom.Domain$TARGETAGGREGATOR.<clinit>(Domain.java:239)
         at weblogic.management.mbeans.custom.Domain.lookupTarget(Domain.java:247)
         at weblogic.management.configuration.DomainMBeanImpl.lookupTarget(DomainMBeanImpl.java:6139)
         at weblogic.deploy.internal.TargetHelper.lookupTargetMBeans(TargetHelper.java:183)
         at weblogic.management.deploy.DeploymentData.getAllTargetedServers(DeploymentData.java:413)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isTargetListContainsCurrentServer(AbstractOperation.java:644)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isDeploymentRequestValidForCurrentServer(AbstractOperation.java:854)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:206)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Nov 2, 2010 11:58:18 AM EDT> <Error> <Console> <borg.abc.virginia.gov> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1288713498054> <BEA-240003> <Console encountered the following error java.lang.Exception: java.lang.ExceptionInInitializerError
         at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.includePrepareFailure(AdminRequestStatus.java:1418)
         at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.signalCancelFailed(AdminRequestStatus.java:1266)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.signalCancelCompletion(AwaitingCancelResponses.java:126)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.doCancelCompletionCheck(AwaitingCancelResponses.java:112)
         at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCancelResponses.receivedCancelFailed(AwaitingCancelResponses.java:97)
         at weblogic.deploy.service.internal.adminserver.AdminRequestImpl.receivedCancelFailed(AdminRequestImpl.java:503)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveCancelFailedMsg(CommonMessageReceiver.java:295)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:779)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.ExceptionInInitializerError:
         at weblogic.management.mbeans.custom.Domain.lookupTarget(Domain.java:247)
         at weblogic.management.configuration.DomainMBeanImpl.lookupTarget(DomainMBeanImpl.java:6139)
         at weblogic.deploy.internal.TargetHelper.lookupTargetMBeans(TargetHelper.java:183)
         at weblogic.management.deploy.DeploymentData.getAllTargetedServers(DeploymentData.java:413)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isTargetListContainsCurrentServer(AbstractOperation.java:644)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.isDeploymentRequestValidForCurrentServer(AbstractOperation.java:854)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:206)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    >
    Thanks,
    Chris

    Hi Chris,
    Did you manage to get a solution to this error, as I am facing the same issue.
    Thanks in advance,
    Pranav

  • Adminconsole deployment on managed server

    can we deploy the Admin Console application on Weblogic Managed Servers?
    Thanks in advance.
    Bhanu.

    can we deploy the Admin Console application on Weblogic Managed Servers?Not sure what you mean, but on Fusion Middleware Control you have a link to the Admin Console for each server.

  • Deployment of Web Application when the managed Server is down .....

    Part of our installation, we want to deploy our web application on to a managed server.
    So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
    But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
    We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
    Can anyone help to deploy web application on to a managed server when the managed server is down ?
    Thanks,
    Selva-
    [att1.html]

    This is currently being fixed in 7.0 line, contact [email protected] and reference
    CR110687
    Cheers
    mbg
    "Selvamohan Neethiraj" <[email protected]> wrote in message news:[email protected]..
    Part of our installation, we want to deploy our web application on to a managed server.
    So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
    But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
    We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
    Can anyone help to deploy web application on to a managed server when the managed server is down ?
    Thanks,
    Selva-
    [att1.html]

  • WSM Managed server starts in ADMIN Mode after upgrade to 11.1.1.7

    We have just upgraded our 11g SOA Cluster environment from 11.1.1.4 to 11.1.1.7. The issue is after the upgrade, our WSM servers are starting to ADMIN state with following error.
    <Sep 25, 2013 7:14:35 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@381802823[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
    at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
    Our cluster environment has one Admin Server, and two of each OSB, WSM and SOA managed servers. As our WSM servers are not coming up, we are not able to start our SOA servers too.
    Thank You

    Same issue here :-)), Just playing around with policies configuration, the server was running just fine, I wanted to check if the policies are applicable during runtime even the WSM managed server is down. After restart, it started in ADMIN mode, well the solution is straight. It is exactly telling that the dms application is missing the jstl library reference
    <Error> <Deployer> <iwpdcdevsoaa.iwater.ie> <WLS_WSM1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <bcfaf10ec8fbdfc2:-26d85d29:1429ffae24c:-8000-0000000000000003> <1385663491675> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@384044243[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
            at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:416)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:494)
            at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
            at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    >
    So search for "jstl" within the weblogic console in search bar, it is type of library, click on it and target it to the managed server where OWSM is running as weel. It was root cause in my case, somehow the library was not targeted to our WLS_WMS1 managed server. Now the server is back in RUNNING mode. Of course apply this in case of problem with SOA servers, target it to the cluster or exact nodes and it should work.
    Still I don't know how the issue has been crated, I don't think that somebody removed it from deployment. Rather I think that somebody was applying patch or some artifacts to OSB or SOA managed server and this library was required as well, but as soon as we have separated WSM cluster, it was maybe assuming that it is running within OSB or SOA clusters and therefore didn't target the WSM cluster automatically. But this is just the idea :-))
    Ladislav

  • 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

  • War not running on managed server but run on admin

    Hi,
    WLS 10.3.1 , application deploy on admin runs successfully but doesnot runs when deployed on managed server.
    netstat show when access via browser the managed server show connection status as FIN_WAIT_2 but established when accessing via admin.
    any idea why?
    Thanks in advance.

    Hi,
    To understand your problem can you let us know
    - If you are using any proxy between the client and WLS.
    - Is this happing with only one managed servers or all the managed servers.
    - What is the basic difference with you try to access the same application when it is deployed on Admin sever and Managed server.
    - Does the response comes from the server (MS) after sometime or its stuck and you do not get any response, and if you do not get it then what do you error do you get if any.
    Regards,
    Ravish Mody

  • Cannot contact MANAGED SERVER in a CLUSTER

    I have configured a BEA CLUSTER (8.1 Sp2) on a SUN CLUSTER.
              If I try to contact a Managed Server using a browser from my PC, (using httpt or https as well) it does not responde until I put a "ping" to this Managed Server's IP ADDRESS using a DOS console.
              Someone can help me?
              Stefano

    How do you contact managed server using browser?
              what is the request (URL) that you sent through browser?
              For the request to be successful you should have an application deployed on managed server.
              -Vijay

Maybe you are looking for

  • WAR or JSP to serve HTML in JAR file?

    Hi, I want to keep a few hundred static help files in a JAR when I install my appliation on the server to ease installation and management. But what is the best way to serve them up? What litle I know about WARs seems to imply I can have HTML files i

  • App.Xaml cannot be edited in design view(Visual Studio 2012 for Window Store).

     App.Xaml cannot be edited in design view(Visual Studio 2012 for Window Store).

  • Error After client copy

    Hi all, I did a client copy in ECC IDES  with client 800 as source client.As per the logs , copy is successful.The profile usedf is SAP_ALL.After the copy we logged into the new client which was created and it looked good. Checked the Logs in SCC3 an

  • Error 1935 - An error occured during the installation assembly

    Every time I try to download Acrobat Reader 8.1.2 I get the following error message: Error 1935 - An error occured during the installation assembly. I have Microsoft Vista - Internet Explorer 7. I have a Dell computer.

  • Why Does Java not see 0 or 1 as false and true

    hello, all other languages i have worked with see a 0 and 1 as a true or false value for instance...in perl this would be the case if ( 0 ) same of javas if ( false ) or if ( 1 ) same as javas if ( true ) same with javascript im am asking if there is