JMS Migration without admin server

Does anyone know if there is a way to migrate the JMS service if the admin
          server is down?
          Cheers,
          SB

I don't think you can migrate a JMS server when the admin server is down.
          You have to use one of the administration tools, such as the administration
          console, command line interface, or JMX. For either of these, you need to
          have the admin server running (see the System Administration Tools section
          at http://edocs.bea.com/wls/docs70/adminguide/overview.html#1040321).
          Dongbo
          Stanley Beamish wrote:
          > Does anyone know if there is a way to migrate the JMS service if the admin
          > server is down?
          >
          > Cheers,
          > SB

Similar Messages

Possible to run soa suite without admin server?

Hi,
I'm wondering if it is possible to run the SOA components on a managed server without the admin server running. I intended to shutdown the admin server in production but when I do that I get errors in my (managed) soa server. I believe this was possible previously. Why does it need the admin server?
version is 10.3.3

Hi,
do you mean in weblogic domain without running admin server you were able to run managed(soa) servers???
Without admin server how Managed servers gets start?
Though there is a concept in weblogic server called MSI mode,in that case managed servers can be running withut admin server, but very first time you have to start Admin server followed by Managed servers.
Thanks,
Deba

Programmatically start/stop applications without admin server connection

I know I can programmatically start/stop an application through WebLogic's deployment API, but the call needs to go through admin server. I was wondering if there's a way for an application to start/stop another application on the same managed server when the admin server is down. I remember a managed server could be started without an admin server (unless it's started for the first time). So I suppose there must be some way to programmatically start/stop local applications without an admin server as well.
Thank you for your help in advance.

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

Starting Managed Servers without admin Server

dear All
i have a Weblogic Server contains the following
Admin Server
LoadBalancer Server
Cluster Contains Server1 & Server2
and every thing is fine, but i have the following problem : while starting any Node from Cluster or LoadBalancer Server using startManagedWebLogic.cmd without starting up admin server, i am getting the following error in my log
Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-00056: Failed to create identity store service instance idstore.ldap.provider:idstore.ldap. Reason: weblogic.security.service.SecurityServiceRuntimeException: Invalid host or port for admin server..     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getIdStoreConfig(LdapIdentityStoreProvider.java:195)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.access$300(LdapIdentityStoreProvider.java:70)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:242)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:114)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:70)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)
     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:798)
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:792)
     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:792)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:289)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:283)
     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:261)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1020)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:879)
     at weblogic.security.SecurityService.start(SecurityService.java:142)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)

Isn't this exactly what the admin service is used for?
I think you need to start the admin server before starting the other servers.
Timo

Deploy without admin server running

Is it possible to perform deployments on managed nodes without having the admin server running?
Currently we are performing deployments using wldeploy ant tasks and we check for admin server availability.

Is it possible to perform deployments on managed nodes without having the admin server running?
Currently we are performing deployments using wldeploy ant tasks and we check for admin server availability.

Can Managed Server self-tuning its performance without Admin Server?

I have an web application deployed on a managed server.
My observation is:
- If the Admin Server is not running, the application will keep accepting incoming external http requests and delayed the processing of them.
- If the Admin Server is running, the application will start the processing soon after the incoming requests arrive.
Can any body explain the reason behind it? Only default work manager is used in the above case.
Thanks

This seems a strange behaviour.
How is structured the application (app/webApp/ejbs/...)?
How is targetted ? The target is only on the managed instance?
Bye
Mariano

Stop managed server without node manager and admin server

What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AM

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

Error while starting Admin Server

Hello Everyone,
I am trying to start Admin server and getting this error:
<Jan 6, 2012 12:08:11 PM> <INFO> <NodeManager> <Server output log file is 'E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\servers\AdminServer\logs\AdminServer.out'>
<Jan 6, 2012 12:08:12 PM PST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Jan 6, 2012 12:08:12 PM PST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Jan 6, 2012 12:08:14 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 19.1-b02 from Sun Microsystems Inc.>
<Jan 6, 2012 12:08:15 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<Jan 6, 2012 12:08:18 PM PST> <Error> <Management> <BEA-141244> <Schema validation errors while parsing E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\config\config.xml - Invalid xsi:type qname: 'ext:oam-servlet-authentication-filter-ia-providerType' in element realm@http://xmlns.oracle.com/weblogic/domain>
<Jan 6, 2012 12:08:18 PM PST> <Error> <Management> <BEA-141244> <Schema validation errors while parsing E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\config\config.xml - E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\<unknown>:14:9: error: failed to load java type corresponding to t=oam-servlet-authentication-filter-ia-providerType@http://xmlns.oracle.com/weblogic/security/extension>
<Jan 6, 2012 12:08:18 PM PST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141245]Schema Validation Error in E:\App\Oracle\Middleware\user_projects\domains\IDAM_Dev_domain\config\config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false>
<Jan 6, 2012 12:08:18 PM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jan 6, 2012 12:08:18 PM PST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jan 6, 2012 12:08:18 PM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jan 6, 2012 12:08:18 PM> <FINEST> <NodeManager> <Waiting for the process to die: 1648>
<Jan 6, 2012 12:08:18 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jan 6, 2012 12:08:18 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Please suggest.
Thanks,
PS

dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>jsf#[email protected]</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<module-type>war</module-type>
<source-path>E:\App\Oracle\Middleware\wlserver_10.3/common/deployable-libraries/jsf-1.2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>jstl#[email protected]</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<module-type>war</module-type>
<source-path>E:\App\Oracle\Middleware\wlserver_10.3/common/deployable-libraries/jstl-1.2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>UIX#[email protected]</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/oracle_common/modules/oracle.uix_11.1.1/uix11.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>ohw-rcf#[email protected]</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/oracle_common/modules/oracle.help_5.0/ohw-rcf.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>ohw-uix#[email protected]</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/oracle_common/modules/oracle.help_5.0/ohw-uix.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.pwdgen#[email protected]</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<source-path>E:/App/Oracle/Middleware/oracle_common/modules/oracle.pwdgen_11.1.1/pwdgen.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.rules#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.rules_11.1.1/rules.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.webcenter.composer#[email protected]</name>
<target>AdminServer,oam_server1,oaam_admin_server1,oim_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/oracle_common/webcenter/modules/oracle.webcenter.framework_11.1.1/oracle.webcenter.composer.war</source-path>
<deployment-order>300</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.webcenter.skin#[email protected]</name>
<target>AdminServer,oim_server1</target>
<module-type>ear</module-type>
<source-path>E:/App/Oracle/Middleware/oracle_common/webcenter/modules/oracle.portlet.server_11.1.1/oracle.webcenter.skin.ear</source-path>
<deployment-order>300</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.workflow.wc#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.workflow_11.1.1/oracle.soa.workflow.wc.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.idm.uishell#[email protected]</name>
<target>AdminServer,oam_server1,oaam_admin_server1,oaam_server_server1,oim_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/Oracle_IDM1/modules/oracle.idm.uishell_11.1.1/oracle.idm.uishell.war</source-path>
<deployment-order>300</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>oracle.soa.rules_editor_dc.webapp#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.rules_editor_dc.webapp_11.1.1/oracle.soa.rules_editor_dc.webapp.war</source-path>
<deployment-order>306</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.rules_dict_dc.webapp#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.rules_dict_dc.webapp_11.1.1/oracle.soa.rules_dict_dc.webapp.war</source-path>
<deployment-order>306</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bpm.mgmt#[email protected]</name>
<target>AdminServer</target>
<source-path>E:/App/Oracle/Middleware/oracle_common/bpm/modules/oracle.bpm.mgmt_11.1.1/oracle.bpm.bpmn-em-tools.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>emai</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/oracle_common/sysman/archives/applications/11_1_1_0_0_emai.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.oaam.libs#[email protected]</name>
<target>oam_server1</target>
<module-type>ear</module-type>
<source-path>E:/App/Oracle/Middleware/Oracle_IDM1/oaam/oaam_libs/ear/oaam_native_lib.ear</source-path>
<deployment-order>400</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>oracle.security.apm.core.model#[email protected]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>E:/App/Oracle/Middleware/Oracle_IDM1/apm/modules/oracle.security.apm_11.1.1/oracle.security.apm.core.model.ear</source-path>
<deployment-order>311</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>oracle.security.apm.core.view#[email protected]</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/Oracle_IDM1/apm/modules/oracle.security.apm_11.1.1/oracle.security.apm.core.view.war</source-path>
<deployment-order>311</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>oracle.sdp.messaging#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/communications/modules/oracle.sdp.messaging_11.1.1/sdpmessaging.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.sdp.client#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/communications/modules/oracle.sdp.client_11.1.1/sdpclient.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>emas</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/oracle_common/sysman/archives/applications/11_1_1_0_0_emas.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>emcore</name>
<target>AdminServer</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/oracle_common/sysman/archives/applications/11_1_1_0_0_emcore.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.bpel#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.bpel_11.1.1/oracle.soa.bpel.jar</source-path>
<deployment-order>301</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.worklist#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.worklist_11.1.1/oracle.soa.worklist.jar</source-path>
<deployment-order>302</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.workflow#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.workflow_11.1.1/oracle.soa.workflow.jar</source-path>
<deployment-order>303</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.mediator#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.mediator_11.1.1/oracle.soa.mediator.jar</source-path>
<deployment-order>304</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.composer.webapp#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.composer.webapp_11.1.1/oracle.soa.composer.webapp.war</source-path>
<deployment-order>306</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.ext#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.ext_11.1.1/oracle.soa.ext.jar</source-path>
<deployment-order>307</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.b2b#[email protected]</name>
<target>AdminServer,soa_server1</target>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar</source-path>
<deployment-order>308</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.soa.worklist.webapp#[email protected]</name>
<target>AdminServer,soa_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.worklist.webapp_11.1.1/oracle.soa.worklist.webapp.war</source-path>
<deployment-order>309</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.oaam.extensions#[email protected]</name>
<target>oaam_admin_server1,oaam_server_server1</target>
<module-type>war</module-type>
<source-path>E:/App/Oracle/Middleware/Oracle_IDM1/oaam/oaam_extensions/generic/oracle.oaam.extensions.war</source-path>
<deployment-order>400</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<machine>
<name>LocalMachine</name>
<node-manager>
<name>LocalMachine</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
<jms-server>
<name>UMSJMSServer</name>
<target>soa_server1</target>
<persistent-store>UMSJMSFileStore</persistent-store>
</jms-server>
<jms-server>
<name>SOAJMSServer</name>
<target>soa_server1</target>
<persistent-store>SOAJMSFileStore</persistent-store>
</jms-server>
<jms-server>
<name>OIMJMSServer</name>
<target>oim_server1</target>
<persistent-store>OIMJMSFileStore</persistent-store>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
</jms-server>
<self-tuning>
<max-threads-constraint>
<name>MaxThreadsConstraint-0</name>
<target>oim_server1</target>
<count>20</count>
</max-threads-constraint>
<max-threads-constraint>
<name>MaxThreadsConstraint-1</name>
<target>oim_server1</target>
<count>80</count>
</max-threads-constraint>
<work-manager>
<name>wm/SOAWorkManager</name>
<target>soa_server1</target>
</work-manager>
<work-manager>
<name>OIMUIWorkManager</name>
<target>oim_server1</target>
<max-threads-constraint>MaxThreadsConstraint-0</max-threads-constraint>
</work-manager>
<work-manager>
<name>OIMMDBWorkManager</name>
<target>oim_server1</target>
<max-threads-constraint>MaxThreadsConstraint-1</max-threads-constraint>
</work-manager>
</self-tuning>
<shutdown-class>
<name>JOC-Shutdown</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.ias.cache.Shutdown</class-name>
</shutdown-class>
<shutdown-class>
<name>DMSShutdown</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.dms.wls.DMSShutdown</class-name>
</shutdown-class>
<startup-class>
<name>JRF Startup Class</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>110</deployment-order>
<class-name>oracle.jrf.wls.JRFStartup</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>
<startup-class>
<name>JPS Startup Class</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>115</deployment-order>
<class-name>oracle.security.jps.wls.JpsWlsStartupClass</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>
<startup-class>
<name>ODL-Startup</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>145</deployment-order>
<class-name>oracle.core.ojdl.weblogic.ODLConfiguration</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>
<startup-class>
<name>Audit Loader Startup Class</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.security.audit.ajl.loader.JEEAuditLoader</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>false</load-before-app-deployments>
</startup-class>
<startup-class>
<name>AWT Application Context Startup Class</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.jrf.AppContextStartup</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>
<startup-class>
<name>JMX Framework Startup Class</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.as.jmx.framework.wls.spi.StartupListener</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>
<startup-class>
<name>JOC-Startup</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.ias.cache.Startup</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>
<startup-class>
<name>DMS-Startup</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.dms.wls.DMSStartup</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>
<startup-class>
<name>OWSM Startup class</name>
<notes>This class will seed the OWSM data in repository</notes>
<target>soa_server1,oaam_server_server1,oim_server1</target>
<deployment-order>150</deployment-order>
<class-name>oracle.wsm.policymanager.util.PolicyManagerStartup</class-name>
<failure-is-fatal>false</failure-is-fatal>
</startup-class>
<startup-class>
<name>SOAStartupClass</name>
<target>soa_server1</target>
<deployment-order>1000</deployment-order>
<class-name>oracle.bpel.services.common.util.GenerateBPMCryptoKey</class-name>
<failure-is-fatal>false</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>
<file-store>
<name>UMSJMSFileStore</name>
<directory>UMSJMSFileStore</directory>
<target>soa_server1</target>
</file-store>
<file-store>
<name>SOAJMSFileStore</name>
<directory>SOAJMSFileStore</directory>
<target>soa_server1</target>
</file-store>
<file-store>
<name>OIMJMSFileStore</name>
<directory>OIMJMSFileStore</directory>
<target>oim_server1</target>
</file-store>
<jms-system-resource>
<name>UMSJMSSystemResource</name>
<target>soa_server1</target>
<sub-deployment>
<name>UMSJMSSubDeployment</name>
<target>UMSJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/UMSJMSSystemResource-jms.xml</descriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>SOAJMSModule</name>
<target>soa_server1</target>
<sub-deployment>
<name>SOASubDeployment</name>
<target>SOAJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/soajmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>OIMJMSModule</name>
<target>oim_server1</target>
<sub-deployment>
<name>OIMSubDeployment</name>
<target>OIMJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/OIMJMSModule-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
<wldf-system-resource>
<name>Module-FMWDFW</name>
<target>AdminServer,oam_server1,oaam_admin_server1,soa_server1,oaam_server_server1,oim_server1</target>
<descriptor-file-name>diagnostics/Module-FMWDFW-2818.xml</descriptor-file-name>
<description>Creates FMWDFW incidents based on unchecked Exceptions and critical errors</description>
</wldf-system-resource>
<jdbc-system-resource>
<name>mds-owsm</name>
<target>AdminServer,soa_server1,oaam_server_server1,oim_server1</target>
<descriptor-file-name>jdbc/mds-owsm-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>oamDS</name>
<target>AdminServer,oam_server1</target>
<descriptor-file-name>jdbc/oam-db-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>OraSDPMDataSource</name>
<target>soa_server1</target>
<descriptor-file-name>jdbc/OraSDPMDataSource-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>mds-ApplicationMDSDB</name>
<target>AdminServer</target>
<descriptor-file-name>jdbc/apm-server-mds-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>apm-DBDS</name>
<target>AdminServer</target>
<descriptor-file-name>jdbc/apm-server-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>OAAM_ADMIN_DS</name>
<target>oaam_admin_server1</target>
<descriptor-file-name>jdbc/OAAM_ADMIN_DS-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>mds-oaam</name>
<target>AdminServer,oaam_admin_server1</target>
<descriptor-file-name>jdbc/OAAM_ADMIN_MDS_DS-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>SOADataSource</name>
<target>soa_server1</target>
<descriptor-file-name>jdbc/SOADataSource-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>EDNDataSource</name>
<target>soa_server1</target>
<descriptor-file-name>jdbc/EDNDataSource-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>EDNLocalTxDataSource</name>
<target>soa_server1</target>
<descriptor-file-name>jdbc/EDNLocalTxDataSource-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>SOALocalTxDataSource</name>
<target>soa_server1</target>
<descriptor-file-name>jdbc/SOALocalTxDataSource-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>mds-soa</name>
<target>AdminServer,soa_server1</target>
<descriptor-file-name>jdbc/mds-soa-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>OAAM_SERVER_DS</name>
<target>oaam_server_server1</target>
<descriptor-file-name>jdbc/OAAM_SERVER_DS-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>oimOperationsDB</name>
<target>soa_server1,oim_server1</target>
<descriptor-file-name>jdbc/oimOperationsDB-0237-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>mds-oim</name>
<target>oim_server1</target>
<descriptor-file-name>jdbc/oimMDS-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>oimJMSStoreDS</name>
<target>oim_server1</target>
<descriptor-file-name>jdbc/oimJMSStoreDS-0269-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>

Weblogic Admin server - Configuration/Server Start/Arguments ignored?

Hi,
I'm trying to specify a http proxy for a WebLogic Admin Server in order for an application to access external resources. I've placed the settings into the "Server Configuration / Server Start / Arguments", and verified that they have been saved into the config/config.xml file for that domain:
<server-start>
<arguments>-Dhttp.proxyHost=[XXXX] -Dhttp.proxyPort=8080</arguments>
<password-encrypted>[XXXX]</password-encrypted>
</server-start>
However, no matter how I start the server, these settings are ignored despite that the documentation states these should be added to the java command line.
starting weblogic with Java version:
java version "1.6.0_19"
Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
As a test I created a new managed server in the same domain, specifying the same startup properties, and they were picked up during startup.
If I manually place the settings into the bin/setDomainEnv.cmd batch file for the domain they are also picked up and work.
Is there an undocumented restriction on Admin Servers that they ignore the "Server Start / Arguments" setting, or is there something else I can check as to why this is not working?
Many thanks,
- Micha.

Umm... I already pasted the relevant snippet out of the config.xml, but following is the entire file. The startup arguments, as specified in the admin console, are:
-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080
which matches what is saved in the config.xml.
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>wls_starter</name>
<domain-version>10.3.2.0</domain-version>
<security-configuration>
<name>wls_starter</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>[XXXXXXXX]</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<max-http-message-size>-1</max-http-message-size>
<ssl>
<enabled>false</enabled>
</ssl>
<log>
<file-name>logs/AdminServer.log</file-name>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>true</number-of-files-limited>
<file-count>7</file-count>
<file-min-size>500</file-min-size>
<rotate-log-on-startup>true</rotate-log-on-startup>
<logger-severity>Trace</logger-severity>
<logger-severity-properties></logger-severity-properties>
<log-file-severity>Info</log-file-severity>
<stdout-severity>Info</stdout-severity>
<domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
<memory-buffer-severity>Debug</memory-buffer-severity>
<log4j-logging-enabled>false</log4j-logging-enabled>
<redirect-stdout-to-server-log-enabled>false</redirect-stdout-to-server-log-enabled>
<domain-log-broadcaster-buffer-size>1</domain-log-broadcaster-buffer-size>
</log>
<machine>[XXXXXXXXXX]</machine>
<listen-port>8080</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<web-server>
<frontend-http-port>0</frontend-http-port>
<frontend-https-port>0</frontend-https-port>
<keep-alive-enabled>true</keep-alive-enabled>
<keep-alive-secs>30</keep-alive-secs>
<https-keep-alive-secs>60</https-keep-alive-secs>
<post-timeout-secs>30</post-timeout-secs>
<max-post-size>-1</max-post-size>
<send-server-header-enabled>false</send-server-header-enabled>
<wap-enabled>false</wap-enabled>
<accept-context-path-in-get-real-path>false</accept-context-path-in-get-real-path>
</web-server>
<listen-address></listen-address>
<java-compiler>javac</java-compiler>
<tunneling-enabled>false</tunneling-enabled>
<tunneling-client-ping-secs>45</tunneling-client-ping-secs>
<tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
<server-start>
<arguments>-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080</arguments>
<password-encrypted>[XXXXXXX]</password-encrypted>
</server-start>
<server-life-cycle-timeout-val>30</server-life-cycle-timeout-val>
<startup-timeout>0</startup-timeout>
<graceful-shutdown-timeout>30</graceful-shutdown-timeout>
<ignore-sessions-during-shutdown>false</ignore-sessions-during-shutdown>
<client-cert-proxy-enabled>false</client-cert-proxy-enabled>
</server>
<embedded-ldap>
<name>wls_starter</name>
<credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.2.0</configuration-version>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<machine>
<name>[XXXXXXXXXX]</name>
</machine>
<jms-server>
<name>WseeJmsServer</name>
<target>AdminServer</target>
<persistent-store>WseeFileStore</persistent-store>
</jms-server>
<jms-server>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<persistent-store>WseeFileStore</persistent-store>
</jms-server>
<self-tuning>
<work-manager>
<name>weblogic.wsee.mdb.DispatchPolicy</name>
<target>AdminServer</target>
</work-manager>
</self-tuning>
<file-store>
<name>WseeFileStore</name>
<directory>WseeFileStore</directory>
<target>AdminServer</target>
</file-store>
<jms-system-resource>
<name>WseeJmsModule</name>
<target>AdminServer</target>
<sub-deployment>
<name>BEA_JMS_MODULE_SUBDEPLOYMENT_WSEEJMSServer</name>
<target>WseeJmsServer</target>
</sub-deployment>
<descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<sub-deployment>
<name>[XXXXXXXXXX]</name>
<target>[XXXXXXXXXX]</target>
</sub-deployment>
<descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
</jdbc-system-resource>
<saf-agent>
<name>ReliableWseeSAFAgent</name>
<target>AdminServer</target>
<store>WseeFileStore</store>
</saf-agent>
</domain>

Oracle weblogic Server 10g R3 -manual JMS migration and reverse migration

Folks
we are trying to use manual JMS migration with WLST scripts /console and noticed several issues in Oracle weblogic serevr 10g R3 .(Currently not interested in using automatic server migration stuff)
1)Our use case is to be able to manually migrate JMS with persistent file store in case of long lasting hardware failure (so we need this working with the source server down)
Here are my observations
1) The console based manual migration works only when both the source and destination are up (ie for doing migration during scheduled maintainance and not for our use case)
2) i tried wlst scripts which works partially for our use case
wls:/jmsmigrationclustertestdomain/edit !> migrate('sb_ms1', 'sb_ms2','true','fa
lse','all')
Migrating JMS and JTA services from 'sb_ms1' to destination 'sb_ms2' ...
Migration completed successfully.
question is how do you migrate this back (reverse migration)
I tried a couple of wlst scripts which all were unsuccessful in migrating the services back. Syntax is also extremly confusing as the weblogic.Admin commands seem to be aware of "migratable targets" (such as "sb_ms1 migratable") but WLST doesnt seem to understand "sb_ms1 migratable"
If I just restart sb_ms1 without running any scripts, it complains about JMS artifacts(not being present) as they are migrated onto the other instance
I have this whole setup working on 9.2mp3 with weblogic.admin scripts
Thanks for any guidance on this

Hi,
I guess you are using the default (system generated) migratable target names for the clustered servers, that have names ends with "(migratable)".
Are you performing the migration from "wls:/YOUR_ADMIN_SERVER_NAME/domainRuntime/MigratableServiceCoordinatorRuntime/the-MigratableServiceCoordinator" ?
Can you please post the exact WLST commands that you tried, syntax of the arguments and any erorr messages taht you have got while performing this operation?
Thanks
Kats

Browse jms destinations on managed servers (from admin server)

I need to browse JMS destinations from the admin server (in a WebLogic
9.2 console extension) that are only deployed on the managed servers.
I can get destination attributes via the domain runtime server, but
no JNDI or actually browse the destinations. All destinations in
which I am interested are queues.
I know I can change my initial context, but if that is the way to go, is there a way to determine the managed
servers' URLs at runtime?
Thank you for any help,
Seth

hi
this worked for me (on 8.1). I suppose there are
better ways in 9.2
Context adminCtx = null;
adminCtx = getInitialContextForAdminServer();
MBeanHome adminhome = (MBeanHome)
adminCtx.lookup(MBeanHome.ADMIN_JNDI_NAME);
// Get the list of running managed
ning managed servers and iterate over itSet
Set srSet =
Set srSet =
adminhome.getMBeansByType("ServerRuntime");
Iterator sr_iter = srSet.iterator();
while (sr_iter.hasNext())
ServerRuntimeMBean bean =
timeMBean bean = (ServerRuntimeMBean) sr_iter.next();
// Get the home for the managed
for the managed server
MBeanHome remoteHome = (MBeanHome)
me = (MBeanHome) adminCtx.lookup(MBeanHome.JNDI_NAME
+ "." + bean.getName());
// Get the MBeanServer for the
anServer for the managed server
MBeanServer rmbs =
eanServer rmbs = remoteHome.getMBeanServer();
//invoke it
ObjectName objectName= new
objectName= new ObjectName("$mbean");
rmbs.invoke(objectName,operation,params,types);
Edited by deepshet at 05/05/2007 10:00 AMThank you for the help.
MBeanHome is deprecated as of 9.0, so I was unable to directly use your example. You have helped though, thank you.
As of now I am querying the domain runtime server for:
ObjectName("com.bea:*,Type=ServerRuntime")
I am then iterating through the returned Set to get the server URLs and then setting my InitialContext with a PROVIDER_URL of the managed servers. This allows me to Look Up a Destination without JNDI based on step 4 from [url http://edocs.bea.com/wls/docs92/jms/implement.html#wp1313933]here. I can then browse as needed.
The ugly part is that if I include the Admin URL in my PROVIDER_URL then it does not work, so I am checking for it as I loop through the set of ServerRuntimes and not including it.
Further though slightly less annoying is that the managed server URLs include "t3://" but if I leave it in there, a malformed URL exception is thrown when setting the PROVIDER_URL. So I also remove all of those and then preppend one on the front for PROVIDER_URL as I actually need.
It is not pretty, but it is working on the only cluster I have been able to try thus far.
If anyone was a cleaner suggestion, please share.

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

Server Admin | Server Updates | updated to 10.5.5 WITHOUT restart?

A curious thing. I wonder whether anyone else experienced the same, or similar…
When the update to Mac OS X Server 10.5.5 was released, very soon after its announcement, I used Server Admin | Server Updates to apply the update to my Mac OS X Server 10.5.4 (PowerPC Xserve).
I expected a restart to be required.
The update completed, but no restart was required!
Amazed, I made an Apple Remote Desktop connection to the server and found that it was reporting itself as 10.5.5. Definitely, without a restart.
I lacked confidence at that point, so I did restart the server, without being asked to.
I might also try to run the combo updater. Just to be doubly sure that the whole caboodle installed as it should have.
I wonder how it apparently got from 10.5.4 to 10.5.5 without a restart; and whether anyone else has experienced such oddities.

I don't know what you've experienced
1. Mac OS X Server 10.5.4 on G4 PowerPC XServe
2. Server Admin on my Macbook Pro identified that the remote Xserve should gain an update to 10.5.5
3. I followed Server Admin's invitation.
3. An ARD view of the remote server's display (Apple menu | About This Mac) showed:
* 10.5.5
— with no invitation to restart, no log in.
I simply connected via ARD, observed, thought, "What? 10.5.5? That's impossible. I haven't restarted".
it's factually impossible for a server to go from 10.x.y to 10.x.(y+1) without a restart.
Hence my bug report to Apple

Weblogic Admin server 10.1mp3 migration to 12c over windows

Hi ,
The admin server is currently with 10.0mp3 over windows 2008 server .This needs migration to 12c over another windows server
The admin server is associated with MachineA & there are 3 managed weblogic servers over machineB .Can anyone suggest what are the ways i can migrate
what are the changes needed to be done over the below files
commEnv.cmd
startManagedWebLogic.cmd
wlsvc.exe -Seeing this file newly over weblogic 12c ?what is the purpose?
Under D:\bea\wls12\server\bin this directory what are the changed needed
installSvc.cmd
installNodeMgrSvc.cmd
Need to syntax to install weblogic admin & weblogic admin as windows services over windows with customized service name?

Thanks for the reply, this looks fine (I think)..the below is the output
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Administrator.SEALEDINFO-PROD>cd C:\Oracle\MiddlewareNew\user_projects\
domains\irm_domain\bin
C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain\bin>setdomainenv.cmd
C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>java -version
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>java weblogic.version
WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401
Use 'weblogic.version -verbose' to get subsystem information
Use 'weblogic.utils.Versions' to get version information for all modules
C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>

Shutdown Manged server without Admin

Hi All,
I have a requirement to Restart Managed servers via NodeManager but without AdminServer.
Using WLST I could start Managedserver using NM. (nmConnect, nmStart).
But for Stopping a Managedserver without Admin. I see the option nmKill. But I dont want to kill the process rather want to do a proper shutdown.
Was looking at few docs in oracle site, which says can shutdown a managedsevr using Node Manager to which it is connected. Means first connect(...) then Shutdown().
BUt is it possible to connect to managed server using WLST when Admin is not Available?
If not above is a possible way to shutdown, resume a managed server without Adminserver.
Weblogic11g is the version I have installed.
ThankYou,
Swapna

'I could see a command connect but its only for connecting to a AdminServer'
It is actually the same. (some example are given here: http://download.oracle.com/docs/cd/E13222_01/wls/docs90/config_scripting/reference.html#1005383)
Note that when your managed server is running on somehost and 8001, you can use the following:
wls:/offline> connect('adminusername','adminpassword','t3://somehost:8001');
Connecting to t3://somehost:8001 with userid adminusername ...
Successfully connected to managed Server 'soa_server1' that belongs to domain 'base_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/base_domain/serverConfig> shutdown();
Shutting down the server soa_server1 with force=false while connected to soa_server1 ...
Disconnected from weblogic server: soa_server1
Disconnected from weblogic server:
wls:/offline>

JMS Migration without admin server

Similar Messages

Maybe you are looking for