Setting up an admin server (win) + a managed server (linux)

I am trying to set up the following domain on weblogic 8.1 SP2:
1. An administration server (+workshop) on my local Windows box
2. A managed server running on a red hat enterprise box, that connects to the
administration server on my windows box.
I've not been able to find any documentation on this, and the installation process
is far from intuitive.
Can someone help me with a step-by-step guide? I'm not trying to do anything fancy
here ;-) Thanks!

Resolution found:
Went through the config.xml file. Found that in the server tag the listen address
for the server and managed server is not there. Entered the Corresponding listen
address for both Admin and Managed server
"Henrik Pettersen" <[email protected]> wrote:
>
>
>
Thank you for the information. Just what I needed. But I am now encountering
another
problem when I try to startManagedWebLogic:
<03-Jun-2004 16:48:03 o'clock BST> <Info> <Configuration Management>
<BEA-150015>
<Connecting to the administration server http://banana:7001 to retrieve
the initial
configuration.>
<03-Jun-2004 16:48:06 o'clock BST> <Notice> <Log Management> <BEA-170019>
<The
server log file /usr/local/bea/user_projects/domains/domain/managed/managed.log
is opened. All server side log events will be written to this file.>
<03-Jun-2004 16:48:06 o'clock BST> <Emergency> <Configuration Management>
<BEA-150011>
<There was an attempt to start a managed server ( null:7001 ) using the
same address
as the admin server ( banana:7001 ).>
<03-Jun-2004 16:48:06 o'clock BST> <Emergency> <WebLogicServer> <BEA-000342>
<Unable
to initialize the server: weblogic.management.configuration.ConfigurationException:
[Configuration Management:150011]There was an attempt to start a managed
server
( null:7001 ) using the same address as the admin server ( banana:7001
).>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException:
[Configuration
Management:150011]There was an attempt to start a managed server ( null:7001
using the same address as the admin server ( banana:7001 ).'
Reason: weblogic.management.configuration.ConfigurationException: [Configuration
Management:150011]There was an attempt to start a managed server ( null:7001
using the same address as the admin server ( banana:7001 ).
I am trying to run Weblogic 8.1 Portal Domain on Red Hat Enterprise 3.
The Linux config file is attached. Any clues would be most appreciated.
Thank you for your help.
Henrik
"Michael Zanchelli" <[email protected]> wrote:
Involving multiple machines obviously adds some complexity but for a
development
environment that you describe, you'll want to use the ConfigurationWizard
to
create domains (with the same name) on both machines. On the admin server
machine,
use the Custom path in Config Wiz to add the managed server, and onthe
managed
server machine, you can use Express mode. Start the admin server, then
use startManagedWeblogic
on the managed server machine, specifying the managed server name and
admin url
as command line args.
In a production environment, you'll likely use node manager to start
managed servers
and a domain does not need to be created on the managed server machine
in that
case.
edocs has lots of good overview information and details on using Config
Wiz.
"Henrik" <[email protected]> wrote:
I am trying to set up the following domain on weblogic 8.1 SP2:
1. An administration server (+workshop) on my local Windows box
2. A managed server running on a red hat enterprise box, that connects
to the
administration server on my windows box.
I've not been able to find any documentation on this, and the installation
process
is far from intuitive.
Can someone help me with a step-by-step guide? I'm not trying to doanything
fancy
here ;-) Thanks!

Similar Messages

  • Starting weblogic cluster and admin server on Win 2000 platform

    Hi! Here's my problem scenario:
    I'm running my WLS 8.1 application as WLS cluster on Win 2000 platform. I have
    3 replicated WLS servers in my cluster and of course one WLS server as admin server
    (4 WLS servers all together). I'm starting my WLS application using Win services
    which behind a scene call win 2000 comand interpreter batch-file to start the
    servers. Currently I have 4 different win 2000 services each calling different
    batch-files to start a WLS server (4 all together). Here's my question:
    Is there any way to start my cluster (3 managed WLS servers) and WLS admin server
    from single win 2000 command file (using single win 2000 service). Using win 2000
    AT-command interpreter command I can start executables and command(s) and command-files
    at background at specific date and time, but I want to start my WLS application
    on every win 2000 platform boot, is there any way to achieve this ???
    Best Regards!
    Jami

    hi,
    Thanks for stepping up!
    But I wasn't using any clustering or loadbalancing.
    Just a simple Admin server, Managed server set up.
    256 Meg, Pentium box running Win 2000 premium edition.
    I tried tweeking around the heap size too.... coz' the operations were slogging
    like anything...
    Bal
    "Raja Mukherjee" <[email protected]> wrote:
    It seems like network issue....do you have Windows Clustering/Load Balancing
    service turned on by any chance? I would also use netmon to see the traffic
    between the ips....
    ..raja
    "Bala" <[email protected]> wrote in message
    news:3b3a6c00$[email protected]..
    hi,
    I am looking at a strange behaviour with WLS6.0SP1 installed on WINDOWS2000 Premium.
    I brought up the Admin server and a Managed server. After a while theAdmin Server
    is compeletely
    losing the control of the managed server (for no reason).
    when I tried monitoring the managed server from the console, I couldnot
    access
    the manager server
    and the status down (red ball). I tried restarting the Admin Server
    in the discover mode - NO LUCK.
    But when I restart the Managed server and go to the Web Based Admin
    Console and refresh, it worked. But I dont think we should be doingthat
    in a
    production environment.
    Did anybody come across such a problem before ???
    Is this a problem with Win 2000 ???
    coz' it never happened with NT workstation
    thanks in advance

  • Problem starting managed server in cluster (The name of the managed server is same as admin server)

              We have the following setup.
              CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
              administrator. We start CLUSTER3 as a self-managed server and then try and start
              CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
              1 and 2 we get the following:
              D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
              03:7001
              D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
              D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              D:\bea\wlserver6.1>echo off
              * To start WebLogic Server, use the password *
              * assigned to the system user. The system *
              * username and password must also be used to *
              * access the WebLogic Server console from a web *
              * browser. *
              D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
              ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
              ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
              -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
              "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
              r
              <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
              Enter password to boot WebLogic server:
              Starting WebLogic Server ....
              Connecting to http://10.0.1.103:7001...
              The WebLogic Server did not start up properly.
              Exception raised: weblogic.management.configuration.ConfigurationException: The
              name of the managed server is same as admin server. The managed server will not
              be allowed to start up.
              weblogic.management.configuration.ConfigurationException: The name of the manage
              d server is same as admin server. The managed server will not be allowed to star
              t up.
              at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
              at weblogic.management.Admin.initialize(Admin.java:320)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              at weblogic.Server.main(Server.java:35)
              Reason: Fatal initialization exception
              D:\bea\wlserver6.1>goto finish
              D:\bea\wlserver6.1>cd config\CLUSTER1
              D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
              D:\bea\wlserver6.1\config\CLUSTER1>
              Many thanks in advance,
              Alex Burton
              http://www.e-plus.com.au/
              

    Don't start the admin server as managed. Removing
              -Dweblogic.management.server...
              from the command line should help.
              Alex Burton wrote:
              > We have the following setup.
              > CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
              > administrator. We start CLUSTER3 as a self-managed server and then try and start
              > CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
              > 1 and 2 we get the following:
              >
              > D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
              > 03:7001
              >
              > D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
              >
              > D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              >
              > D:\bea\wlserver6.1>echo off
              >
              > ***************************************************
              > * To start WebLogic Server, use the password *
              > * assigned to the system user. The system *
              > * username and password must also be used to *
              > * access the WebLogic Server console from a web *
              > * browser. *
              > ***************************************************
              >
              > D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
              > ".
              > ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
              > ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
              > -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
              > "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
              > r
              > <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
              > Enter password to boot WebLogic server:
              > Starting WebLogic Server ....
              > Connecting to http://10.0.1.103:7001...
              > ***************************************************************************
              > The WebLogic Server did not start up properly.
              > Exception raised: weblogic.management.configuration.ConfigurationException: The
              > name of the managed server is same as admin server. The managed server will not
              > be allowed to start up.
              > weblogic.management.configuration.ConfigurationException: The name of the manage
              > d server is same as admin server. The managed server will not be allowed to star
              > t up.
              > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
              > at weblogic.management.Admin.initialize(Admin.java:320)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              > at weblogic.Server.main(Server.java:35)
              > Reason: Fatal initialization exception
              > ***************************************************************************
              >
              > D:\bea\wlserver6.1>goto finish
              >
              > D:\bea\wlserver6.1>cd config\CLUSTER1
              >
              > D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
              >
              > D:\bea\wlserver6.1\config\CLUSTER1>
              >
              > Many thanks in advance,
              > Alex Burton
              > http://www.e-plus.com.au/
              

  • 10.3 Deploying same EAR on both admin server  &managed :server  jndi in use

    Hypotehetical question but is it possible to deploy the same EAR file (some minor differneces) on both Admin server and not have an issue with jndi naming.
    I get the follwoing error when deploying on the managed server and suspect it could be cached compiled ejb's as I have already had a failed deployment on this server so might need to clear the cache
    Error I am getting is:
    An error occurred during activation of changes, please see the log for details.
    Exception preparing module: EJBModule(xxx_base_ejb.jar) Unable to deploy EJB: SessionAdministrationLogicEjb from xxx_base_ejb.jar: [EJB:011055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: norkom_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    Substituted for missing class [EJB - 11055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: xxx_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    Any input very much appreciated.

    Hypotehetical question but is it possible to deploy the same EAR file (some minor differneces) on both Admin server and not have an issue with jndi naming.
    I get the follwoing error when deploying on the managed server and suspect it could be cached compiled ejb's as I have already had a failed deployment on this server so might need to clear the cache
    Error I am getting is:
    An error occurred during activation of changes, please see the log for details.
    Exception preparing module: EJBModule(xxx_base_ejb.jar) Unable to deploy EJB: SessionAdministrationLogicEjb from xxx_base_ejb.jar: [EJB:011055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: norkom_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    Substituted for missing class [EJB - 11055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: xxx_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    Any input very much appreciated.

  • 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

  • Use Admin Server to Manage multiple managed servers through Nodemanager

    hi guys,
    Iam trying to simulate the production environment for a Weblogic based application.
    I want to use one Admin Server(adminServer) to control 2 managed servers(weblogic,Bizarro).
    adminServer & weblogic sit on windows machine (prod1) and Bizarro sits on OakStage(unix
    machine).
    I have nodeManagers running on both machines. They were started using the default
    start scripts that were provided.
    I can sucessfully start&stop instance weblogic (the instance that resides on the
    same machine as adminServer). When I try to start Bizarro i get the following
    error in the console
    <Oct 18, 2002 7:59:22 AM PDT> <Error> <NodeManager> <Could not start server 'Bizarro'
    via Node Manager - reason: '[SecureCommandInvoker: Could not create a socket to
    the NodeManager running on host '192.168.0.97:5555' to execute command 'online
    Bizarro', reason: Operation timed out: connect. Ensure that the NodeManager on
    host '192.168.0.97' is configured to listen on port '5555' and that it is actively
    listening]'>
    but iam sure node manager is running on port 5555 on that box.
    Here is my config.xml file. Is there something Iam missing?
    I have also modified the hosts file to only have the ip address of the admin server.
    <?xml version="1.0" encoding="UTF-8"?>
    <!--If your domain is active, please do not edit the config.xml file. Any changes
    made to that file while the domain is active will not have any effect on the domain's
    configuration and are likely to be lost. If your domain is inactive, you may edit
    this file with an XML editor. If you do so, please refer to the BEA Weblogic Server
    Configuration Reference documentation available from http://edocs.bea.com/wls/docs61/reference.html.
    In general, we recommend that changes to your configuration file be made through
    the Administration Console.-->
    <Domain Name="adminDomain">
    <Security Name="adminDomain" PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
    <PasswordPolicy Name="wl_default_password_policy"/>
    <FileRealm Name="wl_default_file_realm"/>
    <StartupClass ClassName="com.ias.hub.weblogic.WeblogicStartup" Name="hubStartup"
    Targets="weblogic"/>
    <CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people,
    o=beasys.com;server.principal=uid=admin, ou=Administrators, ou=TopologyManagement,
    o=NetscapeRoot;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups,
    o=beasys.com" Name="defaultLDAPRealmForNetscapeDirectoryServer" Notes="This is
    provided as an example. Before enabling this Realm, you must edit the configuration
    parameters as appropriate for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ=="
    RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
    <Server ListenPort="9000" Machine="Prod1" Name="weblogic" StdoutDebugEnabled="true"
    StdoutSeverityLevel="64">
    <ServerStart ClassPath="my correct claspath" Name="weblogic" OutputFile="weblogic.log"/>
    <SSL ListenPort="9001" Name="weblogic"/>
    <ServerDebug Name="weblogic"/>
    <KernelDebug Name="weblogic"/>
    <Log FileName="weblogic.log" Name="weblogic"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <WebServer LogFileName="./config/adminDomain/logs/access.log" LoggingEnabled="true"
    Name="weblogic"/>
    </Server>
    <JDBCConnectionPool CapacityIncrement="2" DriverName="weblogic.jdbc.oci.Driver"
    InitialCapacity="15" LoginDelaySeconds="1" MaxCapacity="15" Name="IasPool" Properties="user=stage2;password=******;server=ORCL_STAGE.INTERASSET.COM"
    RefreshMinutes="25" Targets="weblogic" TestTableName="DUAL" URL="jdbc:weblogic
    racle"/>
    <SNMPAgent Name="adminDomain"/>
    <Application Deployed="true" Name="certificate" Path=".\config\adminDomain\applications">
    <WebAppComponent Name="certificate" Targets="adminServer" URI="certificate.war"/>
    </Application>
    <JDBCDataSource JNDIName="IAS_DATA_SOURCE" Name="IasDataSource" PoolName="IasPool"
    Targets="weblogic"/>
    <Application Deployed="true" Name="DefaultWebApp" Path=".\config\adminDomain\applications">
    <WebAppComponent Name="DefaultWebApp" Targets="adminServer" URI="DefaultWebApp"/>
    </Application>
    <CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people,
    dc=example, dc=com;server.principal=cn=Manager, dc=example, dc=com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups,
    dc=example, c=com" Name="defaultLDAPRealmForOpenLDAPDirectoryServices" Notes="This
    is provided as an example. Before enabling this Realm, you must edit the configuration
    parameters as appropriate for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ=="
    RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
    <Machine Name="Prod1">
    <NodeManager Name="Prod1"/>
    </Machine>
    <Application Deployed="true" Name="entity" Path=".\config\adminDomain\applications">
    <EJBComponent Name="entity" Targets="weblogic" URI="entity.jar"/>
    </Application>
    <Application Deployed="true" Name="hub" Path=".\config\adminDomain\applications">
    <WebAppComponent Name="hub" Targets="weblogic" URI="hub"/>
    </Application>
    <Server ListenAddress="192.168.0.97" ListenPort="7000" Machine="OakStage" Name="Bizarro">
    <ServerStart ClassPath="my correct classpath" Name="Bizarro" OutputFile="bizarro.log"/>
    <SSL Name="Bizarro"/>
    <ServerDebug Name="Bizarro"/>
    <KernelDebug Name="Bizarro"/>
    <Log Name="Bizarro"/>
    <WebServer Name="Bizarro"/>
    </Server>
    <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
    <ApplicationManager Name="adminDomain"/>
    <CustomRealm ConfigurationData="server.host=ldapserver.example.com;membership.scope.depth=1;microsoft.membership.scope=sub;membership.filter=(|(&(memberobject=%M)(objectclass=memberof))(&(groupobject=%M)(objectclass=groupmemberof)));group.dn=ou=Groups,
    o=ExampleMembershipDir;group.filter=(&(cn=%g)(objectclass=mgroup));server.principal=cn=Administrator,
    ou=Members, o=ExampleMembershipDir;user.dn=ou=Members, o=ExampleMembershipDir;user.filter=(&(cn=%u)(objectclass=member))"
    Name="defaultLDAPRealmForMicrosoftSiteServer" Notes="This is provided as an example.
    Before enabling this Realm, you must edit the configuration parameters as appropriate
    for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
    <JTA Name="adminDomain"/>
    <Server ListenPort="7000" Name="adminServer" NativeIOEnabled="true" TransactionLogFilePrefix="config/adminDomain/logs/">
    <ServerStart Name="adminServer"/>
    <Log FileName="config/adminDomain/logs/weblogic.log" Name="adminServer"/>
    <ServerDebug Name="adminServer"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <KernelDebug Name="adminServer"/>
    <WebServer DefaultWebApp="DefaultWebApp" LogFileName="./config/adminDomain/logs/access.log"
    LoggingEnabled="true" Name="adminServer"/>
    <SSL Enabled="true" ListenPort="7005" Name="adminServer" ServerCertificateChainFileName="config/adminDomain/ca.pem"
    ServerCertificateFileName="config/adminDomain/democert.pem" ServerKeyFileName="config/adminDomain/demokey.pem"/>
    </Server>
    <UnixMachine Name="OakStage">
    <NodeManager ListenAddress="192.168.0.97" Name="OakStage"/>
    </UnixMachine>
    <Log FileName="adminDomain.log" Name="adminDomain"/>
    </Domain>
    Thanks guys
    regards
    syd

    Can this be done when you set up your domain along with admin and managed servers the very first time ? Even if you set up a domain with bunch of managed servers why does the library still get installed on admin server??? Also, for the method you described dont we have to update targets for statup and shutdown classes and work managers?
    Also, what is the other method to do it from the console?
    METHOD 2 (Other than the one you described- Please tell me if this is correct method and if we need to go to till level)
    Step1:
    I went to deployments base_domain (in admin console) > deployments chose each library and changed targets manually and activate the changes
    Step2
    Go to Startup and shutdown classes and change targets there
    Step 3
    Go to work managers and change targets there.
    Please let me know
    Edited by: user9021545 on May 12, 2011 10:18 AM

  • Starting cluster fails, managed servers can't seem to connect to admin serv

    I have been trying to run the WebLogic JPA example from,
    http://wiki.eclipse.org/EclipseLink/Examples/JPA/CacheCoordination
    but not having much luck on three different Linux machines,
    The first issue I found was if you did not set the memory options just right, the JVM would just hang,
    I am now using,
                   <jvmarg value="-XX:PermSize=512m"/>
                   <jvmarg value="-XX:MaxPermSize=960m"/>
    with JDK 1.7_17, not sure if there are better options...
    The 3 servers are started using (each with different port, all server run on the same machine, as with the admin server),
    <java classname="weblogic.Server"
    fork="true"
    failonerror="true">
    <jvmarg value="-server"/>
    <!--jvmarg value="-Xms512m"/>
    <jvmarg value="-Xmx960m"/-->
                   <jvmarg value="-XX:PermSize=512m"/>
                   <jvmarg value="-XX:MaxPermSize=960m"/>
    <env key="PATH" value="${env.JAVA_HOME}/bin:${env.PATH}"/>
                   <sysproperty key="java.security.egd" value="file:///dev/./urandom"/>
    <sysproperty key="weblogic.Name" value="server1"/>
    <sysproperty key="bea.home" value="${JEE_HOME}"/>
    <sysproperty key="weblogic.management.server" value="${JEE_HOST}:7001"/>
    <sysproperty key="weblogic.management.username" value="${JEE_USER}"/>
    <sysproperty key="weblogic.management.password" value="${JEE_PASSWORD}"/>
    <sysproperty key="java.security.police" value='"${JEE_SERVER}/lib/weblogic.policy"'/>
    <sysproperty key="weblogic.RootDirectory" value="${JEE_DOMAIN}"/>
    <sysproperty key="weblogic.Stdout" value="server1.log"/>
    <sysproperty key="weblogic.Stderr" value="server1.err"/>
    <classpath>
    <fileset dir="${JEE_SERVER}/lib" includes="weblogic.jar,weblogic_sp.jar"/>
    <pathelement location="${env.JAVA_HOME}/lib/tools.jar"/>
    </classpath>
    </java>
    I found that the start-up would sometimes fail on some of the machines unless I used,
                   <sysproperty key="java.security.egd" value="file:///dev/./urandom"/>
    But on once machine this does not help either,
    I also tried using unicast, but still does not start,
    the admin server starts, then the managed servers start and seem to try to connect to the admin server and just never do, never get past STARTING (to STARTED in the log).
    Another have any other ideas?

    How are you starting the managed servers. try running the command
    from /MW_HOME/user_projects/domains/bifoundation_domain/bin
    nohup sh ./startManagedWebLogic.sh bi_server1 http://localhost:7001> start_bi_server1.log &
    and see how it goes. make sure you have set the boot.properties files under security folder so that it wont get failed looking for username and password.
    hope it helps

  • Admin Server and Managed server startup problem

    Hi,
    My weblogic server version is 11g and OS is Linux.
    When i am trying to start the admin server a frer i created the domain i am getting following exceptions in the server log and server is shutting down.
    FPR6 4008000000000000 (f: 0.000000, d: 3.000000e+00)
    FPR7 4010000000000000 (f: 0.000000, d: 4.000000e+00)
    FPR8 006f007300690078 (f: 6881400.000000, d: 1.379624e-306)
    FPR9 0053006f0063006b (f: 6488171.000000, d: 4.228017e-307)
    FPR10 00650074004d0075 (f: 5046389.000000, d: 9.346098e-307)
    FPR11 0078006500720024 (f: 7471140.000000, d: 2.136208e-306)
    FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
    FPR13 4068000000000000 (f: 0.000000, d: 1.920000e+02)
    FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    Module=/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so
    Module_base_address=0800000000003000
    Target=2_40_20090409_033254_BHdSMr (AIX 5.3)
    CPU=ppc64 (4 logical CPUs) (0x220000000 RAM)
    - Stack Backtrace -
    /usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so:0x000046F4 [0x00003000 +0x000016F4]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005F7088 [0x005AF000 +0x00048088]
    /usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB8228 [0x00FAB000 +0x0000D228]
    /usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB884C [0x00FAB000 +0x0000D84C]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EDE08 [0x005AF000 +0x0003EE08]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF600 [0x005AF000 +0x00040600]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF3A8 [0x005AF000 +0x000403A8]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EC1A0 [0x005AF000 +0x0003D1A0]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB5B4 [0x005AF000 +0x0000C5B4]
    /usr/java6_64/jre/lib/ppc64/default/libj9prt24.so:0x0064C21C [0x00649000 +0x0000321C]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB4D0 [0x005AF000 +0x0000C4D0]
    /usr/java6_64/jre/lib/ppc64/default/libj9thr24.so:0x006375F0 [0x00635000 +0x000025F0]
    /usr/lib/libpthreads.a:0x005084F0 [0x00505000 +0x000034F0]
    0x00000000
    JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
    JVMDUMP007I JVM Requesting System dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp'
    JVMDUMP010I System dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp
    JVMDUMP007I JVM Requesting Snap dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc'
    UTE105: Error writing header to tracefile: /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
    JVMDUMP010I Snap dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
    JVMDUMP007I JVM Requesting Java dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt'
    JVMDUMP012E Error in Java dump: /usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt
    JVMDUMP013I Processed dump event "gpf", detail "".
    After adding "<native-io-enabled>false</native-io-enabled>" in cofig.xml as shown below , i am able to start the admin server.
    <server>
    <name>AdminServer</name>
    <native-io-enabled>false</native-io-enabled>     
    <listen-port>9595</listen-port>
    <listen-address>10.10.15.16</listen-address>
    </server>
    i did the same thing for managed servers to start the server.
    My Question is:
    Are we missing any configurations/settings while creating domain?
    Is there any other option to start the server without adding <native-io-enabled>false</native-io-enabled>?
    Regards,
    Naga

    Hi,
    my managed server heap size properties are
    -XX:PermSize=256m -XX:MaxPermSize=256m -Xms256M -Xmx512M
    But the error with Admin server also and we are not providing any heap size properties to admin server. Becuase while creating the domain, i haven't got any
    option to set the heap size for Admin server. Am i required to set heap size properties in Admin server by following this path "Summary of Servers >AdminServer->Server start->"Arguements"?
    Sorry, i am not able to find activity.log. Can you please tell me the location where i can find acivity.log. If i am not wrong, are you taling about serverOut.log? If that is serverOut.log, please tell me which log you require? is it admin server or managed server?

  • Admin server cannot Re-discover the managed server

    Hi,
              mypc) win2k version 6.0 sp2, ip=192.168.1.108:7001 (being an admin
              server)
              abpqa1) solaris8 version 6.0sp2, ip=192.168.3.20:8888 adm port:1755
              abpqa2) solaris8 version 6.0sp2, ip=192.1683.2:8888 admport:1755
              **abpqa1 and abpqa2 is clustered.**
              After WL server has restarted in
              mypc(-Dweblogic.management.discover=true option has been used), it
              cannot find any managed WL. What else I need to do in order to make
              discover action work?
              Thanx in Advance.
              Regards,
              Tony
              Starting process:
              C:\bea\wlserver6.0sp1>"C:\bea\jdk130\bin\java" -hotspot -ms64m -mx64m
              -classpath
              .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar -Dweblogic.Domain=mydomain
              -Dweblogi
              c.Name=myserver "-Dbea.home=C:\bea"
              "-Djava.security.policy==C:\bea\wlserver6.0s
              p1/lib/weblogic.policy" -Dweblogic.management.discover=true
              -Dweblogic.managemen
              t.password=password weblogic.Server
              Starting WebLogic Server ....
              <2001/8/20 ??02?56?46?> <Notice> <Management> <Loading configuration
              file .
              \config\mydomain\config.xml ...>
              log file: C:\bea\wlserver6.0sp1\.\config\mydomain\logs\weblogic.log
              <2001/8/20 ??02?56?50?> <Info> <Logging> <Only log messages of severity
              "Er
              ror" or worse will be displayed in this window. This can be changed at
              Admin Con
              sole> mydomain> Servers> myserver> Logging> General> Stdout severity
              threshold>
              <2001/8/20 ??02?56?55?> <Notice> <Management> <Starting discovery of
              Manage
              d Server...>
              <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <WebLogic Server
              started>
              <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <ListenThread
              listening o
              n port 7001>
              <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <SSLListenThread
              listenin
              g on port 7002>
              [ytlu.vcf]
              

    Hi,
              After administration port changed back to 0, it has no error and admin
              server
              can discover the managed server.
              However, the admin server cannot control the active/inactive of the
              deployment
              of the war/ear file in the managed servers after admin has discovered those
              managed server. What I have done is...
              1. click in deployment tab
              2. select a war/ear file from available box to chosen box
              3. click apply
              4. try to view in my browser
              5. 404 page not found
              6. restart managed server
              7. try to view in my brower
              8. got the page displayed in my browser
              ** I have tried active the ear/war files and inactive those files. the
              result is the same **
              Anything configuration I have missed?
              Regards,
              Tony
              ytlu wrote:
              > Already set the value to true. Please read the log carefully.
              >
              > Regards,
              > Tony
              >
              > Kumar Allamraju wrote:
              >
              > > In 6.0 the default value of weblogic.management.discover = false.
              > > You have to explicitly turn it on for the admin server to discover
              > > managed servers.
              > >
              > > --
              > > Kumar
              > >
              > > ytlu wrote:
              > >
              > >> Hi,
              > >>
              > >> mypc) win2k version 6.0 sp2, ip=192.168.1.108:7001 (being an
              > >> admin
              > >> server)
              > >> abpqa1) solaris8 version 6.0sp2, ip=192.168.3.20:8888 adm
              > >> port:1755
              > >> abpqa2) solaris8 version 6.0sp2, ip=192.1683.2:8888 admport:1755
              > >>
              > >> **abpqa1 and abpqa2 is clustered.**
              > >>
              > >> After WL server has restarted in
              > >> mypc(-Dweblogic.management.discover=true option has been used), it
              > >> cannot find any managed WL. What else I need to do in order to make
              > >>
              > >> discover action work?
              > >>
              > >> Thanx in Advance.
              > >>
              > >> Regards,
              > >> Tony
              > >>
              > >> Starting process:
              > >>
              > >> C:\bea\wlserver6.0sp1>"C:\bea\jdk130\bin\java" -hotspot -ms64m
              > >> -mx64m
              > >> -classpath
              > >> .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              > >> -Dweblogic.Domain=mydomain
              > >> -Dweblogi
              > >> c.Name=myserver "-Dbea.home=C:\bea"
              > >> "-Djava.security.policy==C:\bea\wlserver6.0s
              > >> p1/lib/weblogic.policy" -Dweblogic.management.discover=true
              > >> -Dweblogic.managemen
              > >> t.password=password weblogic.Server
              > >> Starting WebLogic Server ....
              > >> <2001/8/20 ??02?56?46?> <Notice> <Management> <Loading configuration
              > >>
              > >> file .
              > >> \config\mydomain\config.xml ...>
              > >> log file: C:\bea\wlserver6.0sp1\.\config\mydomain\logs\weblogic.log
              > >> <2001/8/20 ??02?56?50?> <Info> <Logging> <Only log messages of
              > >> severity
              > >> "Er
              > >> ror" or worse will be displayed in this window. This can be changed
              > >> at
              > >> Admin Con
              > >> sole> mydomain> Servers> myserver> Logging> General> Stdout severity
              > >>
              > >> threshold>
              > >>
              > >> <2001/8/20 ??02?56?55?> <Notice> <Management> <Starting discovery of
              > >>
              > >> Manage
              > >> d Server...>
              > >> <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <WebLogic Server
              > >> started>
              > >>
              > >> <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <ListenThread
              > >> listening o
              > >> n port 7001>
              > >> <2001/8/20 ??02?57?02?> <Notice> <WebLogicServer> <SSLListenThread
              > >> listenin
              > >> g on port 7002>
              > >
              [ytlu.vcf]
              

  • Error Trying to get a managed server connected to the admin server

    I am getting the following error when I try starting up a managed server. I
    put -Dweblogic.management.server=http://host:port
    The managed server starts with out setting the management.server setting.
    It gives the error below when I put the management server setting in
    <Error deploying application DefaultWebApp_online: error retrieving
    component [Caching Stub]Proxy for
    rnd2Domain:Name=DefaultWebApp_online,Location=online,Type=WebAppComponentCon
    fig,ApplicationConfig=DefaultWebApp_online>
    Thanks,
    Scott Jones
    [email protected]

    Can you post the error message from both admin as well as managed servers?
    Viresh Garg
    Principal Developer Relations Engineer
    BEA Systems
    Scott Jones wrote:
    I am getting the following error when I try starting up a managed server. I
    put -Dweblogic.management.server=http://host:port
    The managed server starts with out setting the management.server setting.
    It gives the error below when I put the management server setting in
    <Error deploying application DefaultWebApp_online: error retrieving
    component [Caching Stub]Proxy for
    rnd2Domain:Name=DefaultWebApp_online,Location=online,Type=WebAppComponentCon
    fig,ApplicationConfig=DefaultWebApp_online>
    Thanks,
    Scott Jones
    [email protected]
    [att1.html]

  • Problem starting Admin Server using Node Manager

    I have configured the Node Manager to run as a windows service. I want it to start the Admin Server when it is started. This is not working. The Node Manager starts without problem but does not appear to even attempt to start the Admin Server. No error message is written to the nodemanager.log. I have configured the following properties as described in the documentation:
    StartScriptEnabled=true
    StartScriptName=startWebLogic.cmd
    Starting the Admin Server using wlst works. As does starting and stopping a Managed server using the Admin console. This leads me to conclude that the Node Manager configuration is ok.
    WLS version is 9.2.
    All suggestions as to what could be the issue here would be greatly appreciated.
    Cheers!

    Ok, I just wasted a whole day before I found the tricks.
    First, you don't need to do that StartScriptEnabled stuff, unless you have important things to add there.
    Ok, and now what I found:
    - You must make sure you have installed the NodeManager as a service
    - Next, make sure the admin server is assigned to the right machine. Since you can do the WLST trick, that should be fine. If not, tough luck, because the docs say you cannot re-assign an admin server.
    - In nodemanager.properties (...\weblogic92\common\nodemanager) make sure CrashRecoveryEnabled is set to true
    - In nodemanager.domains (same dir) make sure your domain is mentioned with its path
    - For each of the servers to be auto-started, make sure that a startup.properties (in <your-domain-dir> \servers\<server-name> \data\nodemanager) contains Arguments=-Xnohup (for JRockit, for Sun JDK its -Xrs)
    Make sure they are started through the nodemanager, et voila, they'll be restarted after a reboot.
    Why this works? At reboot, the OS ask all processes to die, nicely. Those that don't, get killed forcibly. Without the -Xnohup/rs, the WebLogic servers respond to the nice request, and the nodemanager immediately tries to restart them. Unfortunately, the OS refuses to do that, and the server process is marked as failed, and won't be restarted after reboot. With the option given, the servers ignore mr nice guy, and get killed after the nodemanager has disappeared.
    What can go wrong? A lot. I was playing with the nodemanager username and password, and that took some time to clean up. I probably have to redo the entire setup just to make sure I have a repeatable experience now...
    Cheers,
    Bert

  • How to start managed server automatically with admin server.

    Hello all, I have an admin server anda managed server configured in a machine. I want to start the managed server as soon as I run the script to start the admin server and node manager in the unix pc.
    The admin and managed server are added to the same machine and the machine is connected with the node manager.
    Please let me know what else need to be configured or make change in the script.

    hello user12003735..
    sorry for not mentioning the wlst tool path.
    You can start the wlst(WEBLOGIC SCRIPTING TOOL) in two ways and run your jython scripts.
    PROCEDURE 1) Directly invoking wlst :
    You will find the wlst.cmd(wlst.sh in case of UNIX enviroments) in $WL_HOME/common/bin. From command line do this
    wlst <JYTHON SCRIPT>
    ./wlst.sh <JYTHON SCRIPT> [UNIX]
    PROCEDURE 2) From Command Line :
    There is a jar file in $WL_HOME/server/lib named weblogic.jar. It conatins a class file named WLST.cmd in the package weblogic[Try jd-gui.exe java decompiler to look inside the jarfile. to get it google it]. This jar file actually makes the wlst tool running. If you try to look inside wlst.cmd or wlst.sh you will find that the scripts are internally adding this jar file in CLASSPATH and calling it:
    eval '"${JAVA_HOME}/bin/java"' ${JVM_ARGS} weblogic.WLST '"$@"' [wlst.sh]
    "%JAVA_HOME%\bin\java" %JVM_ARGS% weblogic.WLST %* [wslt.cmd]
    So you can do exactly what the scripts doing from command line. do this :
    {A} $WL_HOME/server/bin/setWLSEnv.sh [or setWLSEnv.cmd] <---------------------------------------- SETS THE CLASSPATH
    You will see a lot of jar files added to your classpath and this step is exactly same when you run the wlst from the scripts in PROCEDURE 1.
    java weblogic.WLST <JYTHON SCRIPT>
    One thing you can also use the weblogic jar file to monitor any weblogic server[You have to first set the env with setWLSEnv.cmd or .sh]:
    java weblogic.Admin -url t3://<IP>:<PORT> -username <USERNAME> -password <PASSWORD> GETSTATE <SERVERNAME> [GETTING THE STATE]
    java weblogic.Admin -url t3://<IP>:<PORT> -username <USERNAME> -password <PASSWORD> FORCESHUTDOWN <SERVERNAME> [FORCIBLY SHUTTING DOWN SERVERS]
    You can do many other things with weblogic.jar not just the previous two. Refer to oracle manuals.

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

  • Clustered enviroments -Starting/Stopping Managed servers, NodeManager & Admin server from single node

    Hi,
    We have 5 node Weblogic cluster. At the time of some mass activities like patching we have to stop all our managed, Admin Servers and node manager and it takes a lot of time to do this by logging in to all 5 managed servers and stopping all components. Though we have node manager configured so we can stop managed servers from console itself, but still have to login to each server to stop NodeManager and Oracle Http Servers.
    Things become worse when wee have to shutdown almost 15-20 instances.
    Is there a way (using wlst or shell script) that we can do all these tasks from by logging in to just one server?
    Thanks,
    Suraj

    The simple code below would shutdown all the running Servers. Some of the APIs for ex MBeanHome are deprecated..still work though..if your concerned about that..I am working on the same using JMX API..if you want I could share that too. And also as described in the below link..you can Cluster stop and start using WLST commands.  Managing the Server Life Cycle - 12c Release 1 (12.1.1)
    <This code is from Oracle Weblogic documentation>
    import java.util.Set;
    import java.util.Iterator;
    import java.rmi.RemoteException;
    import javax.naming.Context;
    import javax.management.ObjectName;
    import java.io.*;
    import java.net.*;
    import weblogic.jndi.Environment;
    import weblogic.management.MBeanHome;
    import weblogic.management.WebLogicMBean;
    import weblogic.management.configuration.ServerMBean;
    import weblogic.management.runtime.ServerRuntimeMBean;
    import weblogic.management.runtime.ServerStates;
    import weblogic.management.WebLogicObjectName;
    public class ServerStopper {
      public static void stop() throws Exception {
        MBeanHome home = null;
        //url of the Admin server
        String url = "t3://localhost:7001";
        String username = "weblogic";
        String password = "welcome1";
        ServerRuntimeMBean serverRuntime = null;
        Set mbeanSet = null;
        Iterator mbeanIterator = null;
        try {
          // Set ContextClassloader to prevent assertions
          URL[] urls = { new File("/").toURL() };
          Thread.currentThread().setContextClassLoader(new
             URLClassLoader(urls));
          Environment env = new Environment();
          env.setProviderUrl(url);
          env.setSecurityPrincipal(username);
          env.setSecurityCredentials(password);
          Context ctx = env.getInitialContext();
          home = (MBeanHome)
               ctx.lookup("weblogic.management.adminhome");
          mbeanSet = home.getMBeansByType("ServerRuntime");
          mbeanIterator = mbeanSet.iterator();
          while(mbeanIterator.hasNext()) {
            serverRuntime = (ServerRuntimeMBean)mbeanIterator.next();
            if(serverRuntime.getState().equals(ServerStates.RUNNING)){
                serverRuntime.shutdown();
        } catch (Exception e) {
          e.printStackTrace();

  • Managed Servers vs. Admin Server - heap sizes

    I have a question. I opened a support ticket with BEA yesterday, the technician got back to me and completely confused the hell out of me.
    We're looking to upgrade to WLS10 with an admin server/managed server design. I was under the impression that each server instance, when fired up, starts up in its own JVM with its own memory allocations. If I set the admin server startup script to have a min and max of 1024, the managed server starts up with the same memory settings. The technician I spoke with yesterday from BEA support to clarify this then explains to me that each server instance, admin and managed, do not exist in their own JVMs but that they share the same JVM. I found verbage in the documentation that says the complete opposite...that one server instance can only exist in one JVM...SO if I have the admin server with 1024 and the managed server with 1024 and the machine only has 2 gigs, that's pretty much all I can have running on this machine, right?
    The thing I don't understand at all is why would I want the admin server and my application on the managed server to use the same amount of ram? My managed server should have way more ram available to it than the admin server which is rarely used throughout the day. Is there a way to set the admin server to 512 and then fire up the managed server with a gig and a half?
    I would think it makes more sense that you specify a different heap size for the admin versus the managed...but maybe not. What is the recommended heap size for the admin server? Is it strictly recommended to let them all use the same heap size settings? Can someone explain why I'd want the admin server to have access to the same amount my heavyweight, client-hit-all-day-long application?
    Any help would be greatly appreciated.
    Cheers,
    rlb

    Thanks David. As God as my witness, the tech seriously told me that they all use the same JVM. Then I got seriously confused, like I was an idiot and didn't understand what a JVM was and I started second-guessing myself. The whole conversation was very strange and yes, there was definitely a language barrier and I'm guessing I just wasn't being clear enough...I don't know...all I know is I walked away from the phone call in worse shape then when I first opened the ticket.
    At any rate, do you have recommendations for admin server ram? I know there are performance tuning tools to help us figure out the optimum settings for our managed server, and I plan on implementing them...but going back to the ram for the Admin server, versus managed server...is there a recommended way of specifying different heap size for the managed servers? Is the recommended way to set the the -Xms and -Xmx settings via the 'Arguments' field on Environment > Servers > serverName > Configuration > Server Start tab via the admin console?
    Thanks again for your quick reply!
    Cheers,
    rlb

Maybe you are looking for