Managed Servers Without NodeManager

Hi,
With WL7, I have an admin server and several managed servers on the same
machine, but no node manager. None of the managed servers have an
msi-config.xml; instead they get their configurations from the admin server
(on the same machine) as long as their ADMIN_URL is set to that of the
admin server.
With WebLogic 8.1, I can't start the managed servers at all unless the node
manager is started. Have things changed from WL7 to WL8.1 so that Node
Manager is always required, or you have to have an msi-config.xml file for
the managed server?

HI Ron,
This is not the case. Node manager is not required. The managed servers
should be able to start using the scripts provided. If this is not the case
please let support know the details of the problem.
The following link has some information about configuring the managed
servers in MSI mode.
http://edocs.bea.com/wls/docs81/adminguide/overview.html#1055732
cheers,
Gaurav.
"Ron Cordell" <[email protected]> wrote in message
news:[email protected]..
Hi,
With WL7, I have an admin server and several managed servers on the same
machine, but no node manager. None of the managed servers have an
msi-config.xml; instead they get their configurations from the adminserver
(on the same machine) as long as their ADMIN_URL is set to that of the
admin server.
With WebLogic 8.1, I can't start the managed servers at all unless thenode
manager is started. Have things changed from WL7 to WL8.1 so that Node
Manager is always required, or you have to have an msi-config.xml file for
the managed server?

Similar Messages

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

Starting Managed Servers without admin Server

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

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

Starting managed servers using Nodemanager

When I try to start a manage server using the nodemanager sitting on the same machine
as the Admin Server and the nodemanager itself, I get the following message:
<Error> <NodeManager> <Could not start server 'serverA' via Node Manager - reason:
'[SecureSocketListener: Could not load certificate '.\\c:\weblogic6.1\wlserver6.1/config/mydomain/demo.crt'
of type 'RSA' - reason: '.\\c:\weblogic6.1\wlserver6.1/config/mydomain/demo.crt
(The filename, directory name, or volume label syntax is incorrect)']'>
What's causing this?

Hi,
Try deactivating Hostname Verification to None in the admin server throught the WLS console. If you have configured the nodemanager.hosts with the ip of the admin server with this step should work. I fthe admin server is with dns name then you need to enable reverse DNS lookup in the nodemanager.properties file, or with the command-line argument:
ReverseDnsEnabled=true

Stop managed server without node manager and admin server

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

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

Create managed servers

is there any way to create managed server in putty? i only took the option of starting admin server while running ./config.sh and after finishing all the steps i now want to create manage servers without using the browser. i have started weblogic using honup ./startWeblogic.sh & . As it is in development mode the username and pass has been taken automatically. i tried to search google on how to do it in putty but couldnot find one, every where they are doing it by http browser.
or i have to do ./config.sh every time if i have to modify or create managed servers?
and 1 more doubt in real time do we use 1 nodemanager to all domains or individual for each domain? i got a unix box with 2 sample domains, so i have created 2 nodemanagers for both the domains(i dont want both the domains to have dependency). please suggest best practises on nodemanager 1 per box or 1 for each domain?
thank you.

By "putty" I'm assuming you mean using the command line in an operating system shell.
The WLST functionality in WLS gives you a lot of power to execute administration/configuration tasks on a WebLogic Server domain.
As a really well illustrated example, I'd suggest looking at this blog post from Rene van Wilk which shows how he uses WLST to create an environment consisting of multiple managed servers. The script he provides can be run non-interactively in the WLST shell, or you can type the respective commands you want to use into the shell in an interactive manner.
http://middlewaremagic.com/weblogic/?p=6637
Below is an example from his blog that shows the commands used to create and configure a managed server instance. This has been taken from the URL above (without permission, hope it's OK) and I suggest reading his full blog to see the entire script and description thereof.
-steve-
082 print 'CREATE MANAGED SERVER: server1';
083     server1 = cmo.createServer('Server1');
084     server1.setListenPort(7002);
085     server1.setAutoRestart(true);
086     server1.setAutoKillIfFailed(true);
087     server1.setRestartMax(2);
088     server1.setRestartDelaySeconds(10);
089     server1.getServerStart().setJavaHome(jvmlocation);
090     server1.getServerStart().setJavaVendor('Oracle');
091     server1.getServerStart().setArguments('-Xms512m -Xmx512m -Xns256m -Xgcprio:pausetime');Using his script as a template, I think you should be able to tweak it very easily to support your specific requirements.
-steve-

Starting managed servers

Hi,
Environment: WebLogic 6.1 SP2, JDK1.3.1, Solaris 8
1. How to start the managed servers using NodeManager from the command line? Already
NodeManager configured and able to start managed servers from the Admin Console.
So from the console start/stop/kill managed servers is fine. From the command
line, if I use `weblogic.Server` to start managed server it's not using the node
manager.
2. In the `java weblogic.nodemanager.NodeManager help`, option `starttemplate`
defaults to `nodemanager.sh`. Any details on this please ?
3. Each time we start managed server with Node Manager, it writes the output to
the new file `OutputFile=./config/NodeManagerlogs/<server>/startserver-<XXXX.log`.
From the documentation it looks like we can set logs directory
`-Dweblogic.nodemanager.savedLogsDirectory=path`, however is it possible to specify
the log file name also?
4. Where is the location of the java applications `System.out`, if the managed
server is started with NodeManager. If the managed server is started with `weblogic.Server`
the `System.out` are printed to the console. So this enables us to redirect to
a file.
thanks
Sarva Meduri

I think you can configure the NodeMgr to start ManagedServers instead of having the
Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
and then let NM take care of starting other servers. I believe you have to set
ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
By default it is true.
prasen
Gerardo Rojas wrote:
Hi:
I have been trying to configure my WebLogic environment to start the managed servers
in a domain automatically when the machine is rebooted. I have done some testing
with Node Manager but, as I understood, Node Manager only restarts a server if
it was started using Node Manager and the server crashes or fails. On the other
hand, if the server is installed as a Windows service, it will be started at reboot
time, but not when the server (not the machine) crashes or fails. So, both solutions
seems to be uncompatible. Is it right?? Is it possible to have both benefits,
that is, to get the managed servers started at boot time (as done by Windows services)
and restarted each time they fail (as done by Node Manager)?
Thanks,
Gerardo

Automatically starting of Managed Servers

Hi, is it possible to start the managed servers without the use of WLST and the admin console automatically?
I want to make it such that when the Admin Server starts up, a service will run and automatically start the managed servers at a different host via the node manager?
Is it even possible? Please advise! Thanks!

Node Manager uses WLST so I'm not sure how else you would plan on using it?
Node Manager can start your machines in the last known state they were in on reboot using CrashRecoveryEnabled=true:
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
Another option is to use the startup/services feature of your OS as Jay described. On *nix you could remotely login to another host and invoke the domain's bin/startManagedWebLogic script directly.

Managed servers are started/stopped from admin console using NodeManager

Hi,
I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
I have node manager setup on the two machines. I use admin console to start/stop managed servers.
Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
Your inputs are highly appreciated.
Thanks in advance.
BR,
Ajmal

Hi Ajmal,
For your issue there are two solution's as shown below:
Solution-1
You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
Console Path:
Servers > Configuration > Server Start
However this has to be done with all the managed serves.
Solution-2
If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
This way whenever you start any of you managed servers from console it would pick up that lib files.
In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
Hope this would help you.
Regards,
Ravish Mody

Have NodeManager start managed servers on machine reboot

Is there any way to have the Node Manager start all the managed servers belonging to a domain when a server reboots?
I know I could create a separate Windows service for each of the managed servers I want running when the server comes on-line, or I could do some fancy scripting at start-up to connect to the Node Manager and have it start the managed servers.
But I was hoping there would be a more elegant way of having the NM start them when it comes on-line.
Ideas appreciated,
dmac.

Hi Dmac,
To achieve this in Windows, you must consider the following WLS Components:
1. Node Manager
2. Admin Server
3. Managed Server
Node Manager
For Node Manager, if you want the component to start automatically on boot up, your best option is to create a Windows Service. You may have selected the option to create a service for Node Manager during the WebLogic Server installation. Use Start -> Run -> services.msc from the Start menu to load the Windows Services Manager. If there is no service for Node Manager, use the following steps to create one.
Create a Windows service for Node Manager:
1. WL_HOME\server\bin\installNodeMgrSvc.cmd
2. Verify in Windows Services that a service was created.
Admin Server
For the Admin Server, you can also create a Windows Service. Here are the steps for doing so:
Create a Windows service for the Admin Server
1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\AdminServer\security\boot.properties. Add the following lines:
username=weblogic
password=<the weblogic username password>
2. Create a command script called installAdmServer_Service.cmd which you will want to make sure has lines like:
SETLOCAL
set DOMAIN_NAME=<your wls domain>
set USERDOMAIN_HOME=<path to domain> # e.g., C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=AdminServer
set PRODUCTION_MODE=true
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
3. For troubleshooting/debugging purposes it is helpful to redirect standard out and error to a text file. Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer from the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd and change the line at the bottom of the file so it includes the -log parameter, e.g.
"%WL_HOME%\server\bin\beasvc" -install -svcname:"%DOMAIN_NAME%_%SERVER_NAME%" -javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%" -extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%" -cmdline:%CMDLINE% -log:"<your middleware home>\user_projects\domains\<your wls domain name>\servers\AdminServer\logs\AdminServer-stdout.txt"
4. Now run "installAdmServer_Service.cmd." The Service should be installed. It will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_AdminServer). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the admin server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Managed Server
For the Managed Server, you can also create a Windows Service. Here are the steps for doing so:
Create a Windows service for the Managed Server (using wls_forms as an example)
1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\WLS_FORMS\security\boot.properties. Add the following lines:
username=weblogic
password=<the weblogic username password e.g manager11g>
2. Create a command script called installWLSFORMS_Service.cmd which has lines like
SETLOCAL
set DOMAIN_NAME=<your wls domain>
set USERDOMAIN_HOME=<path to domain> # e.g. C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=WLS_FORMS
set PRODUCTION_MODE=true
set ADMIN_URL=http://mymachine.mycompany.com:7001
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
NOTES:
a. The ADMIN_URL value should reference the AdminServer hostname and listen port.
b. The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.
c. Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error
<19-Jan-2010 11:37:58 o'clock GMT> <Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server
3. Now run "installWLSFORMS_Service.cmd." The Service should be installed, it will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_WLS_FORMS). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Configuring the Windows service to restart upon failure
As with any Windows Service, it is possible to configure the service to restart itself upon failure. These are standard options available when configuring a Windows Service in the context of Windows Services Manager. However, it is important to understand that 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, whereas if the Admin Server and Managed Server had been started using Node Manager, Node Manager would recognize such a state and restart the process accordingly. So it may be desirable to start Node Manager with a Windows Service and then start the Admin Server and Managed Servers with Node Manager to take advantage of this monitoring feature. Below you will find one such example of how to do this.
Example of starting the Admin Server and a Managed Server using Node Manager
1. Create a batch script similar to this:
Myscript.cmd
call D:\Product\Oracle\Middleware\user_projects\domains\base_domain\bin\setDomainEnv.cmd
java weblogic.WLST D:\Product\Oracle\Middleware\user_projects\domains\base_domain\ServerStart.py
2. Create a Python script similar to this:
ServerStart.py
nmConnect('weblogic', 'welcome1', '192.168.0.101', '5556', 'base_domain','D:\Product\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1','ssl')
nmStart('AdminServer')
connect ('weblogic','welcome1','t3://192.168.0.101:7001')
nmstart('myserver','Server','t3://192.168.0.101:7002')
If you want this to happen automatically on boot up, you can run the script (myscript.cmd) from the Windows Scheduler. You must configure the scheduler to run the script on system startup. This will execute the script without requiring an interactive login to Windows (unattended).
Some Additional Information to Remember
The startup.properties file for the Admin and Managed servers must have "AutoRestart=true." This can be set in the "Health Monitoring" tab for each respective server in the WLS console.
The boot.properties file must be configured and present for each server that you plan to start automatically so that you are not prompted for the user name and password each time. If you are not currently prompted when you start the servers then it is already done.
The nodemanager.properties file must have "StartScriptEnabled=true" and "StartScriptName=StartWeblogic.cmd" in place.

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();

How nodemanager starts managed servers?

Hello All,
I'm facing strange issue with weblogic server. Currently i'm using WLS 8.1 SP 4 on solaris 9 server.
To start weblogic i have customize the script such that when server goes on reboot it will pick the startweblogic.sh script from /opt/bin and start the weblogic. Where as in startweblogic.sh i have mentioned -
NMLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/nodemanager.log; export WL8NMLOG
ADMINLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/adminserver.log; export WL8ADMINLOG
CLUSTERLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/cluster.log; export WL8CLUSTERLOG
cd /u001/wls8/bea/weblogic81/server/bin/
su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
sleep 60
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
sleep 1200
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startcluster.sh >> $CLUSTERLOG 2>&1" &
Though the script works as expected till adminserver is UP/Running, but script doesn't wait for 1200 secs. to start cluster. Somehow nodemanager starts the managed servers immediately after the adminserver is UP.
I have checked the nodemanager.properties file, there is nothing such mentioned. Also, from console i have unchecked the option of AutoStart for both managed servers.
Can anyone tell me how nodemanager starts the managed servers automatically??
Thanks,
HK

can you please tell me what is this .startCluster.sh script.
is it your custom script?
And the idea i have in my mind is that after
cd /u001/wls8/bea/weblogic81/server/bin/
su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
sleep 60
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
sleep 1200
you can give the command to start the individual managed servers like:
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startManagedWebLogic.sh <arguments> >> $CLUSTERLOG 2>&1" &
I think this way it will work....

1 NodeManager, 1 Admin Server and 2 Managed Servers

Hi All, I'm new in Weblogic and this is my 1st time to post a question on this forum. Would like ask for help from you all above my setup, I'm not sure whether it will work or not. Please find out the scenario below:
Setup:
1 Machine (RedHat Enterprise Linux 5.5)
1 NodeManager
1 AdminServer (Name: APP)
2 Managed Servers (Name: APPLIVE, APPUAT)
Currently I would like to using one NodeManager to control both Managed Servers under 1 machine. When I configure my APP Admin Server and two Managed Servers, i would like to nmEnroll both Managed Servers under one NodeManager but it will overwrite my enroll entries if i enroll 2nd Managed Server.
Is it possible to configure NodeManager to accept both Managed Servers entries? Thanks. :)
Edited by: user13602952 on Jan 2, 2011 9:54 PM

Hi Hong,
Following are the few things which you help you understand about NodeManager and nmEnroll
- First of all a Node Manager process is not associated with a specific WebLogic domain but with a machine
- When you run a nmEnroll then you just give "domainDir" and "nmHome" which would then gets the file called "*nm_password.properties*" which contains the encrypted username and password that is used for server authentication and "*SerializedSystemIni.dat*" file.
Example:
nmEnroll([domainDir], [nmHome])
- With above files it also updates the nodemanager.domains file with the domain information which was mentioned in the above command.
Thus when you run the nmEnroll command it would get all the details which it needs to start any managed servers in the same Machine, hence you do not need to run the same commend for each managed servers in the same Machine.
For more information have a look at the below links:
Topic: Search for "nmEnroll"
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/config_scripting/reference.html
Topic: Overview of Node Manager
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html#1091317
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…

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

Creating new Managed Servers on remote machines

Hi,
We have a multi-machine domain already in place. Nodemanager is configured and we're using the architecture suggested in Oracle SOA Enterprise Deployment Guide, where we have one domain home for the AdminServer and one domain home for the Managed servers. Right now what we need to know is how to add new managed servers in the easiest and fastest way possible on the mserver home on both the adminserver local machine and on the remote machine, this is a development environment and we need to be able to quickly create and delete these servers for developers to work.
We know that the standard way of doing it is doing a pack (for the managed servers only), and then an unpack on the mserver home both on local and remote machine after changing the root directory of these servers to match those homes. Here is were we have our first doubts. Do the unpack command command has to be run with the already running servers down? Does this pack and unpack process affects what we already have deployed on the running managed servers? And last but not least, is there any way to automate this process? Because we need to give the developers the ability to create clusters on the environment through the admin server console, but without giving them access to the underlying operating system.
If this seems like a newbie question is because we are, we're just in the process of migrating oas 10g to weblogic 11g and there are tons of basic administration stuff that seem pretty strange for us, we've looked through the Oracle manuals and metalink but even though some show you how to create the domain with remote managed servers for the first time, we couldn't find any mention on how to add the mserver efficiently after that.
Thanks!

Cris,
Thanks again for your help, we're trying to figure out how to present this procedure to our customer, just one thought though, we were thinking about moving away from the architecture presented by de SOA Enterprise Deployment guide, and using a single domain home located on the shared storage, that way we could create the managed servers from the admin console without having to use pack/unpack and deciding where to run the servers just by configuring machines and nodemanager. However, we haven't seen this kind of configuration anywhere on Oracle manuals, is there any other problem you are aware of in this idea? We're using a storage with multipath for the shared disk so we're not very concerned about availability (and if the storage went down the weblogic domain would be the least of our problems).
Regards, Franco.

Managed Servers Without NodeManager

Similar Messages

Maybe you are looking for