Howto Programatically discover clusters, admin server, managed servers

Hi,
          I'm want to programatically discover what clusters, admins servers, and managed servers exist in my domain.
          I've tried using get MBeanHome, but in order to get that I must know the location of the admin server.
          I'd like to be able to discover from within my program the host name and port of the admin server,and then from there to be able to discover the managed servers and clusters that are running and on what machines/ ports they are running on.
          Is this possible.
          Cheers,
          Keith

Keith Hyland <> writes:
 > I'm want to programatically discover what clusters, admins servers, and managed servers exist in my domain.
 >
 > I've tried using get MBeanHome, but in order to get that I must know the location of the admin server.
 >
 > I'd like to be able to discover from within my program the host name and port of the admin server,and then from there to be able to discover the managed servers and clusters that are running and on what machines/ ports they are running on.
 >
 > Is this possible.
 Its possible, but there are no public APIs for directly doing this. I
 guess you could try looking up the local server's MBean and navigating
 to the admin server's MBean from there.
 You could probably also deduce it from the system property
 weblogic.management.host that you would have set to boot the managed
 server.
 andy
 --

Similar Messages

Automatic startup of admin server + managed server on Windws

Hello,
I have installed/configured WLS 10.3.6 + Forms/Reports 11.1.2.1 on Windows 2008 R2. All this went ok with no errors.
The NodeManager is installed as a service and runs happily after every reboot of the server. OPMN does it as well.
I can connect to the NodeManager with WLST and start/stop/status the Admin Server and the managed servers (WLS_FORMS,WLS_REPORTS) created during the
the installation/configuration step. Each server has the username/password defined (and already encrypted).
However, when I restart the Windows Server, neither the Admin Server nor the WLS_x servers are started during the boot.
I thought that the configuration process was in charge of setting all this, that was my experience with the previous version Oracle Internet Application Server (iAS) 10.1.2.x (opmn running as a service started them all).
I have run through the installation/configuration docs, and found nothing that says that Oracle will configure (or not) the automatic startup.
1) Is the Oracle configuration process (the one that creates the ClassicDomain) supposed to configure the automatic startup of the admin server + managed servers in this setup ? Am I missing perhaps some extra steps ?
or
2) Do I have to create WLST scripts (that connect to the NodeManager and start the admin server + managed servers) and deploy them as Windows Services myself ?
regards.

Hi,
During weblogic installation in window server, node manager will be automatically registered as window services. But for admin and managed servers, you need to register it manually after succesful installation and configuration for automatic startup during machine reboot.
Please refer the metaliknk id for register as window services:1060058.1.
If this helps please mark.
Regards,
Kishore

Command for STOPPING admin and managed servers

I am writing a script for our application, which apart from building and
deploying application, also needs to stop and start both admin and managed
servers. Is there any command available for properly stopping the weblogic
servers? ( something that "initiates the shutdown")
Thanks

Scott, could you try specifying the protocol: t3 in the url of the
servers.
eg) java weblogic.Admin -url t3://172.17.13.46:7013 -username system
-password
xxx SHUTDOWN
-mihir
Scott Jones wrote:
I have a script that shutsdown all my servers java weblogic.Admin -url
neo.conway.acxiom.com:$S4_ONLINE_PORT SHUTDOWN -username system
-password $S4_WLS_ADMIN_PW
java weblogic.Admin -url neo.conway.acxiom.com:$S4_S4MT_PORT SHUTDOWN
-username system -password $S4_WLS_ADMIN_PW
java weblogic.Admin -url neo.conway.acxiom.com:$S4_WLS_ADMIN_PORT
SHUTDOWN -username system -password $S4_WLS_ADMIN_PWThe first two
lines shut down my managed server. The last shuts down my admin
server. Scott [email protected]
"Mihir Kulkarni" <[email protected]> wrote in
message news:[email protected] here -
Solaris 2.7 with WLS 60 sp1.
I am not facing any problems, though!
Fyi, my managed-server is not in a cluster.
JD wrote:
I am running on Solaris 2.7 using WL6.0sp1.
Mihir Kulkarni <[email protected]> wrote:
<!doctype html public "-//w3c//dtd html 4.0transitional//en">
<html>
Hi,
 Could you please specify on which platform are youfacing this problem.Also,
which sp of the WLS 60 are you using ?
I tried the weblogic.Admin SHUTDOWN command on NT andSolaris and
it
runs correctly on both. These are the results:
on NT:
 on the client:
 java weblogic.Admin -url t3://172.17.13.46:7013-username system
-password
xxx SHUTDOWN
 Shutdown initiated
 The shutdown sequence has been initiated.
on the Managed server:
 <Jun 13, 2001 11:45:49 AM PDT> <Alert><WebLogicServer>
<The
disabling of server
 logins has been requested by system>
 <Jun 13, 2001 11:45:49 AM PDT> <Alert><WebLogicServer>
<Server
logins have been
 disabled.>
 <Jun 13, 2001 11:45:49 AM PDT> <Alert><WebLogicServer>
<Server
shutdown has bee
 n requested by system>
 <Jun 13, 2001 11:45:49 AM PDT> <Alert><WebLogicServer>
<The
shutdown sequence h
 as been initiated.>
 <Jun 13, 2001 11:45:49 AM PDT> <Info><WebLogicServer> <Server
shutdown is comme
 ncing NOW and is irreversible.>
 <Jun 13, 2001 11:45:49 AM PDT> <Info> <HTTP> <[HTTPstandAloneServer]
Destroying
 servlets in default servlet context>
 <Jun 13, 2001 11:45:49 AM PDT> <Info> <JMS><Undeployed
4 default connection fac
 tories.>
 <Jun 13, 2001 11:45:49 AM PDT> <Info> <JMS> <JMSshutdown
is complete.>
 <Jun 13, 2001 11:45:49 AM PDT> <Info><WebLogicServer> <Removing
"ClientContext
 - id: '#|standAloneServer|1.992457846784', bound:'false', dead:
'false'"
becaus
 e of hard disconnect timeout.>
 <Jun 13, 2001 11:45:50 AM PDT> <Info><WebLogicServer> <Requesting
all threads t
 o perform their own shutdown.>
 <Jun 13, 2001 11:45:50 AM PDT> <Info><WebLogicServer> <Shutting
down Thread[SSL
 ListenThread,5,WebLogicServer]>
 <Jun 13, 2001 11:45:50 AM PDT> <Info><WebLogicServer> <Waiting
20 seconds for t
 hreads to complete shutdown.>
 <Jun 13, 2001 11:45:50 AM PDT> <Info><WebLogicServer> <Shutting
down Thread[Lis
 tenThread,5,WebLogicServer]>
 <Jun 13, 2001 11:46:10 AM PDT> <Info><WebLogicServer> <Stopping
execute threads
 .>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '0' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '1' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '2' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '3' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '4' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '5' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '6' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '7' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '8' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '9' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '10' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '11' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '12' for queue: 'default'' stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '0' for queue: '__weblogic_admin_html_queue''stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '1' for queue: '__weblogic_admin_html_queue''stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '0' for queue: '__weblogic_admin_rmi_queue''stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Critical> <Kernel><Execute
Thread: 'ExecuteThre
 ad: '1' for queue: '__weblogic_admin_rmi_queue''stopped.>
 <Jun 13, 2001 11:46:10 AM PDT> <Info><WebLogicServer> <Shutdown
has completed.>
on Solaris platform:
 on client:
 java weblogic.Admin -url t3://willard.beasys.com:7003-username system
-xxx mihirk00 SHUTDOWN
 Shutdown initiated
 The shutdown sequence has been initiated.
on the Managed server:
 <Jun 13, 2001 11:52:26 AM PDT> <Alert><WebLogicServer>
<Server
shutdown has been requested by system>
 <Jun 13, 2001 11:52:26 AM PDT> <Alert><WebLogicServer>
<The
shutdown sequence has been initiated.>
 <Jun 13, 2001 11:52:26 AM PDT> <Emergency><WebLogicServer>
<ListenThread.run() failed: java.lang.ThreadDeath>
 <Jun 13, 2001 11:52:27 AM PDT> <Emergency><WebLogicServer>
<The WebLogic Server is no longer listening forconnections. You should
probably restart it.>
 <Jun 13, 2001 11:52:27 AM PDT> <Alert><WebLogicServer>
<Server
shutdown has been requested by system>
 <Jun 13, 2001 11:52:27 AM PDT> <Alert><WebLogicServer>
<The
shutdown sequence has been initiated.>
So, it works fine for me.
 Please let me know if I am missing something.
cheers,
 Mihir
 
Scott Simpson wrote:
<blockquote TYPE=CITE>"JD" <[email protected]> wrote
in message
 <a
href="news:[email protected]">news:[email protected]</a>...
 > I ran this problem past BEA support and as usualthey can not duplicate
 the problem.
They can't duplicate the problem! Everybody on thisnewsgroup has
the
same
 problem. How can they not duplicate it?!</blockquote>
</html>
[att1.html]

Automating start / restart of WebLogic Admin and managed servers on MS Windows

Hi All,
Please help me to do the automation of start and stop scrip of Oracle Weblogic 10.3.6 and Forms and Reports 11.1.2.2.0(Managed Servers) On Windows server 2008.
Here are two options for automating start / stop of WebLogic Admin and managed servers on MS Windows. Please suggesst which one is standrad procedure.
Use NodeManager (installed as a MS Windows Service)
or
Create Windows Service(s) for the server(s) - no NodeManager
Following Document : 1060058.1
Please suggest me the best practice. Many thanks in advance.
Kind Regards,
Mohan

Hi Borys,
Thank you for quick reply...
If we use the first option "Create Windows Service(s) for the server(s) - no NodeManager" then we will be facing issue Like "Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running"
In the document : 1060058.1 : Mentioned as Important Note: The second option has a limitations.
Limitaion is below when we use first option : "Create Windows Service(s) for the server(s) - no NodeManager" -
Windows Services Manager only monitors the JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running. The Windows Service will not know to restart the process in these cases. If a server is started using NodeManager, NodeManager would recognize such a state and restart the process accordingly. Furthermore, if you start up managed servers via a MS Windows Service, you cannot monitor and/ or stop the managed server via the Weblogic Admin Console and/or Fusion Middleware ( Enterprise Manager ) Control.
I have implemented the second option "Use NodeManager starting admin and manged servers via WLST script" - Python script. Its working well without issue...No Limitation...
Script Contains Below :
print "================== Start scripts of Managed servers and Admin server ======================"
nmConnect(userConfigFile='D:/myFiles/myuserconfigfile.secure',userKeyFile='D:/myFiles/myuserkeyfile.secure',host='00.0.00.00',port='5556',domainName='ClassicDomain',domainDir='D:\Oracle\Middleware\user_projects\domains\ClassicDomain',nmType='ssl')
print "================== Adminserver Starting ================================================"
nmStart('AdminServer')
connect('weblogic','Password1','10.4.93.117:7001')
print "================== MANAGED SERVER (FROMS) Starting ====================================="
start('WLS_FORMS','Server')
print "================== MANAGED SERVER (REPORTS) Starting ==================================="
start('WLS_REPORTS','Server')
exit()
HOPE WE WILL MEET AGAIN AND AGAIN...
Many thanks for your comments!
Kind Regards,
Mohan

Alert setup for Admin and Manage servers in weblogic

Hi All,
We need to setup e-mail notification for health status of admin and managed servers on fusion middleware 11g. Kindly advise.
Thanks,
Vijay

Hi there Vijay,
you can easily do this using the WebLogic Diagnostic Framework. If your WebLogic installation hosts products from the Fusion Middleware portfolio, e.g. Oracle SOA Suite, Oracle WebCenter, etc., you will have a preconfigured WLDF module targeted to all servers named Module-FMWDFW.
In general you will have to:
1. Configure mail session and target it to all servers. Details on the mail server are provided as properties. Use the following as a starting point:
mail.host=<your_outgoing_mail_server_host>
mail.user=<your_outgoing_mail_server_user>
mail.transport.protocol=smtp
mail.from=<address_to_send_emails_from>
mail.debug=True
2. Configure WebLogic Diagnostic Framework Module or reconfigure the Module-FMWDFW if exists
3. Configure Watches and Notifications for that module and the data/events you are interested in. By default the Module-FMWDFW is configured to generate ADR incidents in certain occasions (you can examine the configuration of Module-FMWDFW).
You can get more details from these resources:
http://docs.oracle.com/cd/E29542_01/web.1111/e13714/architecture.htm#WLDFC115
https://blogs.oracle.com/jamesbayer/entry/weblogic_notifications_watch_t
Hope this helps,
A.

Commands for STOPPING admin and managed servers

I am writing a script for our application, which apart from building and
deploying application, also needs to stop and start both admin and managed
servers. Is there any command available for properly stopping the weblogic
servers? ( something that "initiates the shutdown")
Thanks

sorry i haven't moved up to 6.0 yet, so i don't know much about it :(
hope someone else can help you there
Manmari wrote:
thanks bhavin. I will try this on my 6.0 However what is the command for
stopping any of my "managed servers"? Is it the same or something like
java weblogic.Managed "t3://managedserver:7003" SHUTDOWN
Have you tried it. I founf a note on other newsgroup that this does not work
for maged servers. Do you know the solution? Does it work for you?
youe help is much appreciated
Thanks
"bhavin patel" <[email protected]> wrote in message
news:[email protected]..
i don't know if this is what you are looking for, but to stop wl 5.10
you just need to run the weblogic.Admin class
like this
java weblogic.Admin "t3://yourserver:7001" SHUTDOWN <username> <password>
hth
Manmari wrote:
I am writing a script for our application, which apart from building and
deploying application, also needs to stop and start both admin and
managed
servers. Is there any command available for properly stopping theweblogic
servers? ( something that "initiates the shutdown")
Thanks

Clustering Admin server

 Hi,
 Here is my question!
 I have a setup like this, 4 solaris unix machines, 1 Multi-Host Clustered Domain
 for all 4 boxes. 1 Admin server & 16 Managed servers (4 managed servers on each
 solaris box)so 4X4 = 16. i.e.
 Machine A
 Admin
 server 1, server 2, server 3, server 4
 Machine B
 server 5, server 6, server 7, server 8
 Machine C
 server 9, server 10, server 11, server 12
 Machine D
 server 13, server 14, server 15, server 16.
 Now All the 16 servers are in cluster. Everything is running and perfectly fine.
 All load balancing, replication etc. are fine. Now for some reason, My Machine
 A is down and not going to be up for a day. All the other running instances in
 the boxes B,C & D are running and fine. Now I have to deploy an application to
 that cluster and also to see the console for monitoring. Whatz the way??
 Is this possible for a domain to have a backup Admin server. Any clustering for
 Admin server and backup admin servers. ?????
 Please let me know
 thanks
 Sarva Meduri


 Hi,
 I actually have a question..rather than an answer. It might be quite trivial.
 What situation makes it necessary to have 4 managed servers on one machine. Does
 it not put a lot more overheads on the machine.
 Thanks in Advance.
 "Cameron Purdy" <[email protected]> wrote:
 >Admin server can't be clustered. It must be outside of the cluster. It
 >should be on a different port. Note that admin server doesn't have to
 >be
 >running for the cluster to keep running. AFAIK It can be brought up on
 >any
 >machine while the cluster is running so this should not be an issue at
 >all.
 >
 >Peace,
 >
 >--
 >Cameron Purdy
 >Tangosol, Inc.
 >Clustering Weblogic? You're either using Coherence, or you should be!
 >Download a Tangosol Coherence eval today at http://www.tangosol.com/
 >
 >
 >
 >"sarva meduri" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> Hi,
 >>
 >> Here is my question!
 >> I have a setup like this, 4 solaris unix machines, 1 Multi-Host Clustered
 >Domain
 >> for all 4 boxes. 1 Admin server & 16 Managed servers (4 managed servers
 >on
 >each
 >> solaris box)so 4X4 = 16. i.e.
 >>
 >> Machine A
 >> Admin
 >> server 1, server 2, server 3, server 4
 >>
 >> Machine B
 >> server 5, server 6, server 7, server 8
 >>
 >> Machine C
 >> server 9, server 10, server 11, server 12
 >>
 >> Machine D
 >> server 13, server 14, server 15, server 16.
 >>
 >> Now All the 16 servers are in cluster. Everything is running and perfectly
 >fine.
 >> All load balancing, replication etc. are fine. Now for some reason,
 >My
 >Machine
 >> A is down and not going to be up for a day. All the other running
 >instances in
 >> the boxes B,C & D are running and fine. Now I have to deploy an
 >application to
 >> that cluster and also to see the console for monitoring. Whatz the
 >way??
 >> Is this possible for a domain to have a backup Admin server. Any
 >clustering for
 >> Admin server and backup admin servers. ?????
 >>
 >> Please let me know
 >> thanks
 >> Sarva Meduri
 >>
 >
 >

Can I run the admin and managed servers as different users?

in unix, is it possible to run my admin and manged servers as different users with
7.1?

As long as users are in admin group, there could be different users starting different
servers.
"Frank" <[email protected]> wrote:
>
"Erik Johnson" <[email protected]> wrote:
Hi, Frank.
Could you be a little more specific about what it is you want to do?
Thanks.
erikUh, I'm on unix, I have Weblogic 7.0 service pack4. I have 1 managed
server and
I have one admin server...Can I run the admin server as user 'hithere'
and run
the managed server as user, 'byethere'......
"Frank" <[email protected]> wrote:
in unix, is it possible to run my admin and manged servers as different
users with
7.1?

Silent Install w/Admin and Managed Servers

I noticed on versions 11 and 12 of Weblogic, it seems the parameters available for a silent install have been greatly simplified to where it just does a base install. How would I go about getting it to do a silent install with an Admin server and 2 Managed servers? Do I need to do an install and update-install or is there a way I can do all this in 1 shot?
Thanks In Advance
Nic

An example is given here: Middleware Snippets: Automate WebLogic 12.1.2 Deployment.

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.

Self start admin server,manage server, weblogic server

after studying some tutorial,
i suceeded to install wls 11g 10.3.5 in production mode,
node manger is running as windows service,
admin server can be seen running when startweblogic.cmd is used, throughe console,
managed server do start in healthy state when click start from the console,
but
instalsvc.cmd is required to succeed, as to avoide running startweblogic.cmd script, and to avoide
starting managed server through the console,
Kindly,
Edited by: kashif, pakistan on Sep 23, 2011 12:12 AM

first create the AdminServer_service
then the managed Server
try and check it :
SETLOCAL
rem
rem
set DOMAIN_NAME=YourDomain
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\YourDomain
rem
set SERVER_NAME=AdminServer
rem for managed_server :
rem set SERVER_NAME=YOUR_MANAGED_SERVER_NAME
rem
set PRODUCTION_MODE=true
rem
set WLS_USER=weblogic_user
set WLS_PW=your_pwd
rem
set MEM_ARGS="-Xms512m -Xmx512m"
set JAVA_VENDOR=Sun
set JAVA_HOME=C:\Java\jdk1.6.0_26
rem
rem
rem
rem maybe, you need to set more env-parameter,
rem you can runt this before call installSvc.cmd
rem call "C:\Oracle\Middleware\user_projects\domains\YourDomain\bin\setDomainEnv.cmd"
rem
rem
call "C:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc.cmd"
echo .
pause
ENDLOCAL
if it fails , you can de-install the service
and make a new one
SETLOCAL
set DOMAIN_NAME=YourDomain
set SERVER_NAME=AdminServer
rem for managed_server :
rem set SERVER_NAME=YOUR_MANAGED_SERVER_NAME
rem
echo DOMAIN_NAME = %DOMAIN_NAME%
echo SERVER_NAME = %SERVER_NAME%
pause
call "C:\Oracle\Middleware\wlserver_10.3\server\bin\uninstallSvc.cmd"
echo .
pause
ENDLOCAL
if you want to start your Windows-Host
with first the AdminServer-Service
and after that the Managed_Server_Service
you need to edit the / your own installSvc.cmd
in the row %WL_HOME%\server\bin\beasvc" -install ......
with
-depend:beasvc YourDomain_AdminServer - wait for adminserver
-delay:180000 - delay 3 min to start the managed_server_service
Norbert

Clustering Admin Server(Weblogic) 10.1.3 with OBIEE

I was reading through this document - http://docs.oracle.com/cd/E14571_01/doc.1111/e15722.pdf, and it says weblogic cannot be available active - active and there is no automatic fail over available, did anyone tried weblogic clustering? can you recommend any other documents/links for more info :)
Appreciate your help
~Srix

The message "This Connection Pool can not be tested" means that the ManagedConnectionFactory class of adapter does not implement ValidatingManagedConnectionFactory therefore it is impossible to do test.
You may need to post to DBAdapter's forum to get the answer. This forum is about WebLogic Container itself.
Thanks

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

<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

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

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

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

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

Howto Programatically discover clusters, admin server, managed servers

Similar Messages

Maybe you are looking for