Deploying applications on the Admin Server

Hi there
I have recently moved to a new project team who have been deploying their applications to the admin server. They have been doing this for years with no issues.
I was always led to believe that the best practice was to keep the admin server completely separate. And I always deployed to a managed server (or a cluster of servers).
Does anyone know of any specific reasons why applications should not be deployed to an admin server.
Thanks in advance.

Typically, you want your managed servers to focus on applications, and the admin server to focus on management of the servers. If you have your heavy load applications deployed to the admin server, then that impacts both your applications and the management of those applications.
If your applications are deployed to the managed server, and not the admin server, you can recycle applications remotely just through the admin server console. If you need to restart the application, and it's running on the admin server, then you'll have to take additional steps to get the server running again.

Similar Messages

  • Deployment problem to the managed server in 11.1.1.1..

    Our deployment problem still continue. We can deploy at last one application to the admin server.
    We can see ADF domain ans jsf libs in deployment list
    But for managed server following error occurs.
    Even we tried small new application.
    But error is the same.
    An error occurred during activation of changes, please see the log for details.
    weblogic.management.DeploymentException:
    oracle.mds.lcm.weblogic.WLLifecycleListener
    Failure occurred in the execution of deployment request with ID '1247067738026' for task '16'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) 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.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) 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)
    Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: oracle.jsp.next, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 for Application Application1_application1
    Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.1.0 for Application Application1_application1

    last error we take is (we are not even use MDS customisation)
    Failure occurred in the execution of deployment request with ID '1247124709107' for task '2'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) 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.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) 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)

  • Does NodeManager make the Admin Server restart at reboot?

    I have been trying to run both my Admin server and SOA Suite using the Node Manager based on this article:
    http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
    When I reboot, the soa_server1 (managed server) starts up but the AdminServer does not.
    Am I missing something? Is this not something the NodeManager is supposed to support?
    Thanks for quick replies,
    Jeremy

    It depends on how you have deployed your application on Weblogic. Generally, organizations do not have any of their applications on the Admin server. They generally use a clustered set of managed servers to have their applications deployed on them. From the security perspective also, the Admin server is preferred to be kept down as this prevents unauthorized users from gaining access to the Admin console and making changes on them. However, before keeping the Admin server down, you must make sure that none of your application components are deployed on the Admin server or make use of the Admin server.
    Edited by: Smithan John on Jun 8, 2010 1:33 PM

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

  • Deploying application to the web with Developer Server

    Hi everyone,
    Does anyone out there has any notes or step-by-step configuration
    guide on deploying application on the web with Developer Server
    only (not with OAS)? I know that you can use it with Microsoft
    IIS 3.0 or 4.0 (as the web server) but don't know how to set it
    up. Appreciate if someone out there could help. Thanks.
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Pedro Diaz Robles ([email protected]):
    I need exeperience comments and guidelines experience for deploying Forms in the WEB.<HR></BLOCKQUOTE>
    Be more specific !!

  • How can i deploy two different versions of the same application on the same server??

    I have two different versions of an application. One is a released version. And another version under development. I need to port this version of the application to the same server. I'm using the same classes and packages(except for some new ones). Is it sufficient if i change the name of my ear(application name). Or should i change my code also.

    Hi
    You can repackage the new versions of ear,jar and war with different names. I hope that should work well.
    Cheers
    -pradeep

  • Problem while Deploying application in weblogic admin console

    Hi all,
    Recently i got an issue while deploying application through weblogic admin console,
    I have logged in the weblogic console and clicked on the deployment option, i got the page of install the application, then i have click the install option, i was getting the page of blank white screen. checking the log file of the admin server i cannot find any error. The admin server was running state was ok. before many times i have done deploying application in the same weblogic admin console.
    My weblogic 10.3 was running in windows 2008 r2
    Kindly need a help to resolve this problem ASAP.
    Regards,
    Rakhi

    Hi sir,
    thanks for ur reply.. but while troubleshooting on this issue i am facing another problem,
    The weblogic server is running on windows os box, i have stop the weblogic admin server from the windows services and again started the weblogic admin server, the server was running in proper state and i have open the console and try the same thing clicking on the deployment and install options but the same issue i faced. getting the white blank screen, while trying to refresh the page i cannot get the weblogic console waiting for long time also. again after restarting the server i can get the weblogic console.
    Then i have tried in another way, i removed the window services and started the weblogic server from command prompt,after starting the server i have opened the admin console and click on the deployment and install option, it is working fine. i tried the same for many times its working fine. but while starting from windows services the problem i was facing same as blank white screen,
    Kindly give me a perfect resolution on this issue. because i was so confused on this part.
    Regards,
    Rakhi..

  • Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager" error while starting the Admin server

    Hi,
              I installed weblogic 12.1.2.0.0 with RHEL5.6.  After the installation, I tried to post the following class path in setDomainEnv.sh file under the domain home directory,
    POST_CLASSPATH="/prosun/jasper/jasperreports-3.6.0.jar:/prosun/jasper/commons-digester-1.7.jar:/prosun/jasper/log4j-1.2.15.jar:/prosun/jasper/org.apache.commons.beanutils_1.6.jar:/prosun/jasper/org.apache.commons.collections_3.1.jar:/prosun/jasper/org.apache.commons.logging_1.0.4.jar:/prosun/jasper/iText-2.1.0.jar:/prosun/jasper/groovy-all-1.5.5.jar"
    While i am  trying to start the Admin server, the server didn't started and following exception is reported in nohup.out file.  Please help me to resolve this issue.
    The above library jars are required for our applications.
    Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager"
    java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
    java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
    at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)       
    at java.security.AccessController.doPrivileged(Native Method)
    at java.util.logging.LogManager$1.run(LogManager.java:186)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    at java.util.logging.LogManager.<clinit>(LogManager.java:176)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:483)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:452)
    at java.util.logging.LogManager$1.run(LogManager.java:186)
    at weblogic.kernel.KernelLogManager.createClientLogger(KernelLogManager.java:44)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.kernel.KernelLogManager.access$000(KernelLogManager.java:17)       
    at java.util.logging.LogManager.<clinit>(LogManager.java:176)
    at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:20)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:483)
    at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:26)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:452)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at weblogic.kernel.KernelLogManager.createClientLogger(KernelLogManager.java:44)       
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at weblogic.kernel.KernelLogManager.access$000(KernelLogManager.java:17)       
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:20)     
    at java.lang.reflect.Method.invoke(Method.java:601)
    at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:26)
    at weblogic.logging.MessageLogger.log(MessageLogger.java:96)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at weblogic.logging.MessageLogger.log(MessageLogger.java:111)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:52)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)       
    at weblogic.security.SecurityLogger.logDisallowingCryptoJDefaultJCEVerification(SecurityLogger.java:13444)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at weblogic.security.utils.SecurityUtils.turnOffCryptoJDefaultJCEVerification(SecurityUtils.java:81)   
    at weblogic.logging.MessageLogger.log(MessageLogger.java:96)
    at weblogic.Server.main(Server.java:70)at weblogic.logging.MessageLogger.log(MessageLogger.java:111)
    at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:52)
    Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager"
    java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
    at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    at java.util.logging.LogManager$1.run(LogManager.java:186)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.util.logging.LogManager.<clinit>(LogManager.java:176)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:483)
    at java.util.logging.Logger.getAnonymousLogger(Logger.java:452)
    at weblogic.kernel.KernelLogManager.createClientLogger(KernelLogManager.java:44)
    at weblogic.kernel.KernelLogManager.access$000(KernelLogManager.java:17)
    at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:20)
    at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:26)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    Regards,
    Anand Krishnan

    hi, you should not do nothing with user root.
    please, don't use root again for weblogic administration.
    list all files with root permissions:
    move to Middleware Home, example: cd /u01/app/oracle/Middleware
    find . -user root
    if there are files with root permissions, change it to oracle:oinstall
    I saw this:
    Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager"
    java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
    Please check in DOMAIN_HOME/bin/setDomainEnv.sh file if exist this:
    JAVA_OPTIONS="-Djava.util.logging.manager=oracle.core.ojdl.logging.ODLLogManager ${JAVA_OPTIONS}"
    export JAVA_OPTIONS
    MWCONFIG_CLASSPATH=${FMWCONFIG_CLASSPATH}${CLASSPATHSEP}${COMMON_COMPONENTS_HOME}/modules/oracle.odl_11.1.1/ojdl.jar
    export FMWCONFIG_CLASSPATH
    if exist, replace for:
    JAVA_OPTIONS="${JAVA_OPTIONS}"
    export JAVA_OPTIONS
    if not existe, its necesary for you to use /prosun/jasper/org.apache.commons.logging_1.0.4.jar in your classpath?. If it isn't necesary delete it, and restart the AdminServer.

  • ORABPEL-10585 exception raised when starting the admin server

    Greetings,
    Have installed Oracle SOA Suite 11gR1 with WebLogic 10.3. Starting the admin application server raises the following exception:
    <Mar 30, 2012 5:30:33 PM CEST> <Error> <oracle.bpm.services.organization> <BEA-000000> <Exception
    exception.70692.type: error
    exception.70692.severity: 2
    exception.70692.name: Error while granting BPMOrganizationAdmin role to SOAOperator.
    exception.70692.description: Error occured while granting the application role BPMOrganizationAdmin to application role SOAOperator.
    exception.70692.fix: In the policy store, please add SOAOperator role as a member of BPMOrganizationAdmin role, if it is not already present.
    ORABPEL-10585
    Service error.
    Internal Error; Service error occurs in JpsProvider in method getIdentityStore().
    Refer to the log file that is configured for oracle.soa.services.identity for more details on this error and contact Oracle Support Services
    at oracle.tip.pc.services.identity.jps.JpsProvider.getIdentityStore(JpsProvider.java:379)
    at oracle.tip.pc.services.identity.jps.JpsProvider.init(JpsProvider.java:352)
    at oracle.tip.pc.services.identity.jps.JpsProvider.<init>(JpsProvider.java:316)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getInstance(JpsProvider.java:328)
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:292)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01520: Cannot initialize identity store.
    at oracle.security.jps.internal.idstore.util.IdentityStoreUtil.getIdentityStoreFactory(IdentityStoreUtil.java:168)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmFactory(AbstractIdmIdentityStore.java:174)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.initStore(AbstractIdmIdentityStore.java:124)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmStore(AbstractIdmIdentityStore.java:110)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getIdentityStore(JpsProvider.java:377)
    at oracle.tip.pc.services.identity.jps.JpsProvider.init(JpsProvider.java:352)
    at oracle.tip.pc.services.identity.jps.JpsProvider.<init>(JpsProvider.java:316)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getInstance(JpsProvider.java:328)
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:292)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    >
    <Mar 30, 2012 5:30:33 PM CEST> <Error> <oracle.bpm.common> <BEA-000000> <Exception
    BPM-70692
    Exception
    exception.70692.type: error
    exception.70692.severity: 2
    exception.70692.name: Error while granting BPMOrganizationAdmin role to SOAOperator.
    exception.70692.description: Error occured while granting the application role BPMOrganizationAdmin to application role SOAOperator.
    exception.70692.fix: In the policy store, please add SOAOperator role as a member of BPMOrganizationAdmin role, if it is not already present.
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:324)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused By: ORABPEL-10585
    Service error.
    Internal Error; Service error occurs in JpsProvider in method getIdentityStore().
    Refer to the log file that is configured for oracle.soa.services.identity for more details on this error and contact Oracle Support Services
    at oracle.tip.pc.services.identity.jps.JpsProvider.getIdentityStore(JpsProvider.java:379)
    at oracle.tip.pc.services.identity.jps.JpsProvider.init(JpsProvider.java:352)
    at oracle.tip.pc.services.identity.jps.JpsProvider.<init>(JpsProvider.java:316)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getInstance(JpsProvider.java:328)
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:292)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01520: Cannot initialize identity store.
    at oracle.security.jps.internal.idstore.util.IdentityStoreUtil.getIdentityStoreFactory(IdentityStoreUtil.java:168)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmFactory(AbstractIdmIdentityStore.java:174)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.initStore(AbstractIdmIdentityStore.java:124)
    at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmStore(AbstractIdmIdentityStore.java:110)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getIdentityStore(JpsProvider.java:377)
    at oracle.tip.pc.services.identity.jps.JpsProvider.init(JpsProvider.java:352)
    at oracle.tip.pc.services.identity.jps.JpsProvider.<init>(JpsProvider.java:316)
    at oracle.tip.pc.services.identity.jps.JpsProvider.getInstance(JpsProvider.java:328)
    at oracle.bpm.bpmn.engine.runtime.DeploymentDescriptorUtil.grantBPMOrganizationAdminRoleToSOAOperator(DeploymentDescriptorUtil.java:292)
    at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.stateChanged(BPMNServiceEngine.java:578)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListeners(FabricLifecycle.java:46)
    at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(FabricLifecycle.java:29)
    at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshImpl.java:118)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy294.postDeployInit(Unknown Source)
    at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:555)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    >
    I noticed it has something to do with security so I need to mention I modified the boot.properties file such that to have the same credentials used upon the domain creation.
    Many thanks in advance for your help.
    Kind regards,
    Nicolas

    scanzano,
    I was wondering if you ever received and answer to this question, becuase I am faced with the same problem when I attempt a signon to the 'admin server' I receive the following message:
    type Status report
    message Invalid direct reference to form login page
    description The request sent by the client was syntactically incorrect (Invalid direct reference to form login page).
    This is displayed as an "HTTP Status 400 - Invalid direct reference to form login page!!??" It appears that this message has been around for a while so I'm wondering if this issue will ever get resolved??

  • Trying to run the SOA/BPM managed server withOUT running the Admin server

    (This is for demo/development purposes... Using 11.1.1.4 in Windows 7 with 4gb)
    Because of memory constrains I am trying to run the BPM/workspaces application without needing the Admin to be running.
    When they both run, I can use the credentials I create with the Admin server but the response time is prohibitive and all my memory is used...
    It seems to run much faster when only the bpm managed server is running but then I cannot login ...
    So my question is simply: Whats the easiest way to set it up so I can use credentials elsewhere without requiring the admin server to be running?
    ( I could connect to an OID instance I have outside this server or the seeded demo they refer to in other posts ... but do these also require the admin server to be running???)
    aTdHvAaNnKcSe ! (thanks IN advance)
    Claudio
    Edited by: clichten on Aug 20, 2011 9:35 AM

    I don't know if what you want is possible. Only did a suggestion that works fine for me. I'm running SOA Suite and BPM Suite 11.1.1.5 on WLS 10.3.5
    Configure a new WLS domain and see if the BPM Dev template is available in your version.
    I've tuned my startup script (setSOADomainEnv.cmd) as follows:
    set JAVA_OPTIONS=%JAVA_OPTIONS%
    set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
    set PORT_MEM_ARGS=-Xms1536m -Xmx1536m
    if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
    set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
    set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
    Use visualvm that's available from your jdk/bin directory to monitor your jvm and optimize it accordingly
    Regards,
    Melvin

  • Errors & warnings when using the Admin Server Console - Help Needed

    hi,
    i just installed weblogic 12c and created a new domain which contains an adminServer and managedServer under
    one cluster.
    after finishing the installation, i started the Admin Server and afterwards started the admin server console.
    and i got the next warning and errors.
    the warning look like this:
    <20:00:35 IST 23/03/2012> <Warning> <Munger> <BEA-2156203> <A version attribute
    was not found in element "web-app" in the deployment descriptor C:\Oracle\Middle
    ware\user_projects\domains\base_domain\servers\AdminServer\tmp\_WL_internal\cons
    oleapp\jxhze9\console-ext\sipserver-console-ext\WEB-INF\web.xml. A version attri
    bute is required, but this version of the WebLogic Server will assume that the l
    atest version is used. Future versions of WebLogic Server will reject descriptor
    s that do not specify the Java EE version. To eliminate this warning, add an app
    ropriate "version=" to element "web-app" in the deployment descriptor.>
    the errors look like this:
    <20:01:51 IST 23/03/2012> <Error> <netuix> <BEA-423158> <No content found at con
    tentUri = /PortalConfig/security/providers/AuthenticatorConfigCommon.portlet.>
    what is the problem? anyone knows?

    If you want to have an weblogic environment with one domain having server spread across different physical machines , then you will have to perform the installations of the weblogic server separately on all the machines . Also make sure that the version of the Weblogic server you are installing is same across the machines and the directory structure is also exactly same.
    In short you will have to perform the below steps :
    1 : install the weblogic server on all the machines with exactly same version and same dir structure .
    2 : Create domain on MachineA providing all the details of the Managed Server and different machine hostnames.
    3 : Start the Admin Server on machineA and then shut down it.
    4 : execute the WLST pack command on MachineA creating a domain template JAR file.
    5 : copy the create jar file on all the Machines ( B , C , D ) you have to distribute your domain.
    6 : Execute the WLST unpack command on all the machines ( B , C , D ) .
    7 : Execute the WLST nmEnroll () command on all the machines ( B, C , D ).
    8 : Start the Managed Servers on all the machines ( B , C , D )

  • BEA-141151 The admin server could not be reached at ...

    I have been at this for 3 days now... I created a new ManagedServer, but I'm not able to make it connect to the Admin server.
    The Admin server is running and listening on port 5306. I can connect to the Admin Console (web).
    I can also connect to the Admin server via WLST, using this command: connect('operator','operator01','t3://localhost:5306')
    However, when I try to run the managed server from a script, it does not see the Admin server. This is the command I run:
    java -Dweblogic.Name=ManSer1 -Dweblogic.management.server=t3://localhost:5306 -Dweblogic.RootDirectory=<path to my domain> weblogic.Server
    This is the error I get:
    <BEA-141151> <The admin server could not be reached at http://localhost:5306.>
    I believe it's trying to connect using "http", because I've never actually connected in the past. Here is a website explaining this: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13749/weblogicserver.htm#i1031832
    Note: Regardless of which protocol you specify, the initial download of a Managed Server's configuration is over HTTP or HTTPS. After the RMI subsystem initializes, the server instance can use the T3 or T3S protocol.
    I'm not sure what else to try... Firewalls are not in play, since this is traffic moving around on the local machine. I'm running on SunOS. Weblogic is version 9.2 MP3.
    Appreciate any help.

    Is the NodeManager , AdminServer running ?The NodeManager is not running. Is it required?
    Also, I haven't closed the command prompt.
    I noticed the issue when I tried to deploy my project. Connected to Localhost/7001 but in the deploy project window, I dont see any soa_server instance
    running. Also, in the console the soa_server status is shutdown.

  • How to upgrade the Admin Server to WLS 9.2.3 while Managed on 9.2.2

    HI,
    I have a WLS 9.2.2 domain with Admin and 2 Managed instances clustered. Admin and Managed Servers are on different machines.
    I want to upgrade only the Admin Server to WLS 9.2 MP3 while all my Managed Servers are in WLS 9.2 MP2.
    Can any one provide me the detailed steps on how to upgrade only the Admin server to WLS 9.2 MP3?
    And I read in the Weblogic documentation that this supported. But could not find any detailed steps on how to upgrade only the Admin server to the Major version.
    Thanks in Advance.

    Hi
    1. "And I read in the Weblogic documentation that this supported". Can you please provide the link or documenation that exactly says that this is Supported ???
    2. As far as I know, one of the basic requirements for Weblogic Cluster with managed servers across different remote machines is, all the machines, Admin and Managed Servers machines should have Exact Same Version (including Service Pack) of WLS deployed. Right now I do not have this link on top of my head. But this is the only Supported and one basic requirement for Weblogic Cluster.
    Since WLS uses all Shared Modules and each Shared module do have like Implementation and Specification Version. If you upgrade admin server domain, most probably config.xml file will be upgraded with all modules version as 10.0.2.3 (something like that). This means when you restart Managed Servers, they will get a new copy of config.xml file from admin server machine. So now on Managed Servers all these modules (10.0.2.3 etc) should exist on their local machines. This is just my thought.
    Thanks
    Ravi Jegga

  • How to start the admin server on another WLS machine?

    Hi,
              I have a weblogic cluster with 2 weblogic machines: machineA and machineB.
              The cluster contains 4 managed servers (2 on each WLS machine)
              The admin server runs on machineA (standalone).
              I have a file backup of the domain directory on machineA.
              Suppose machineA crashes.
              How can I start the admin server on machineB?
              Kind regards,
              Pieter

    Thanks for your reply,
              I know how to (re)start the admin server on machineA. But in this case I want to start the admin server on machineB.
              The documentation says:
              Restarting an Administration Server on Another Machine
              If a machine crash prevents you from restarting the Administration Server on the same machine, you can recover management of the running Managed Servers as follows:
              Install the WebLogic Server software on the new administration machine (if this has not already been done).
              Make your application files available to the new Administration Server by copying them from backups or by using a shared disk. Your application files should be available in the same relative location on the new file system as on the file system of the original Administration Server.
              Make your configuration and security data available to the new administration machine by copying them from backups or by using a shared disk. For more information, refer to Directory and File Backups for Failure Recovery.
              Restart the Administration Server on the new machine.
              Simply starting the admin server on the other machine does not work because it tries to start the admin server on the ip address of the old machine.
              Edited by [email protected] at 05/10/2007 7:47 AM

  • Newbie cluster question: where does the admin server live?

    Hello, I'm looking at clustering for our application where I work, and so I'm reading through the cluster-related documentation for 11g. I have a sort of an architecture question: where should the admin server be started? Hypothetically speaking, if you have two nodes for your cluster, would the AdminServer run on a 3rd box which sort of stood in front of the two nodes?
    Thanks much -

    The ideal situation would be for your admin server to be separate from the machines hosting your managed server. This allows you to control access to the admin server, eliminate the performance impact if you have the admin + managed on the same host, and limits impact if youir #1 host fails, etc.
    But companies may be unwilling to invest in a distinct (3rd) host just for the admin server, especially if you have multiple environments ( prod, testing, dev, etc. ).
    So usually the admin winds up sharing the host with a managed server.

Maybe you are looking for