Start managed server with the node manager???

Hello,
I have one admin server and one managed server for my domain. Can i Start the amdin and managed server from the node manager and not just the admin server. Currently with the install of node manager only the admin server starts and not the managed server. I need to log in to the admin server to start my managed server which is very cumbersome.
Edited by: user9021545 on Mar 11, 2011 1:58 PM

hi,
In order to start Managed server from the console itself,then u have to enroll your node manager.
Step1). Start the AdminServer...using startScript "startWebLogic.sh/cmd"
step2)start ur node manager using stat node manager scripts,
step3)Login to adminConsole and then see the NodeManager is Reachable or not
If reachanble
then run "setWLSEnv.sh/cmd".
Then run wlst.sh file
Step3)connect('weblogic','weblogic','t3://localhost:7001')
Step4)nmEnroll('C:/bea103/user_projects/domains/7001_Domain','C:/bea103/wlserver_10.3/common/nodemanager')
After this u will be able to start and stop managed server from console itself
Note:even after dis your managed server doesnt starts then please check under <DOMAIN_ROOT>\servers\<SERVER_NAME> whether you have a folder name as security and inside it whether you have file called as boot.properties
if no then follow these below steps
Please create a directory "security" inside your
<DOMAIN_ROOT>\servers\<SERVER_NAME>
inside "<DOMAIN_ROOT>\servers\<SERVER_NAME>\security" ( Example Location:
WLS103/user_projects/domains/Test_Domain/servers/AdminServer/security )
directory create a file with exactly same name as "boot.properties" and with
following 2 lines inside it:
username=weblogic
password=weblogic
NOTE: Here "weblogic" is the Administrator username & password...
if you want dont want to run Admin server from foreground then try runnin it as a background process
This link wi; b helpful for that
http://middlewareforum.com/weblogic/?cat=23
any further help in this den do let me know
Regards
Fabian

Similar Messages

Impossible to start UCM managed server with the WLS console

Hi,
I cannot start the UCM managed server with the WLS console. The node manager is running by startNodeManager.cmd. The admin server by startWebLogic.cmd.
When I start the UCM server with the console WLS (Environment, Servers, Control tab and Start on the checked server), it seems to be running (the state is RUNNING) but when I open the url on the the web server UCM there is a 404 error
In the log, there are many java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup, oracle.security.jps.wls.JpsWlsStartupClass, oracle.core.ojdl.weblogic.ODLConfiguration, oracle.jrf.AppContextStartup, oracle.as.jmx.framework.wls.spi.StartupListener, oracle.ias.cache.Startup, oracle.dms.wls.DMSStartup ...
If I start UCM directly by startManagedWebLogic.cmd and not with the WLS console, everything is OK. No error in the log and UCM server is working well
Any idea ?
Thanks
Hugues

Great!
I had the same error: when starting UCM on WL Console, it starts and says Running. But when accessing it on the browser receive the error 404. In the other hand, when starting with Commands, it force shutdowns.
I have set the StartScriptEnabled property to true, now I can start UCM only on the command Line, to start it on WL Console, I have to manually start the node manager.
Is there a way/script to start the node manager automatically?
Regards,

How to start Integration server with the user XISUPER

Hi,
How to start Integration server with the user XISUPER?
Regards,

Mahesh,
In the post installation document, under Creating User XISUPER,
I see the following,
1.You must now log on to the Integration server host with the user XISUPER, to switch the initial password to a valid password.
2.You must restart the J2EE engine to transfer the user creation to the J2EE immediately.
I am unable to proceed here.Can you please help me to resume the post installation steps ?
Thanks,

Is there any way changing the priviledge after starting the managed server with the other user

Hi,
is there any way to change the user privilege after i have started the managed
server with one user.....say for example ....i have started one of my Managed
server as "root" ...but after that i wanted to make this instance work under as
"inet"
how do i do this OR is it possible ????
please advise ....
sangita

Thanks again Rob.
Rob Woollen <[email protected]> wrote:
>
>
sangita wrote:
Thanks Rob for been so quick in responding.
I have 3 questions for you:
Running a server under root is a huge security hole.My Question: 1) what are the probable security issues while runninga server under
root ?
are these security issues external(from outside world) or internal(internally
within a company) ?
Iam basically curious to know external threats.
The problem is the root user can do anything. So if someone finds a
security hole in your server, then they have complete control of your
system.
The usual reason people want to do this is so they can bind to a port
<
1024. ie they want their web server to listen to 80.My Question: 2) What is the harm in using port 80 for webserver andwhy do the
people wanted to bind to a port < 1024 ?
People normally use 80 for web servers because that's the well-known
port.
Personally I would not recommend that you go that route. I would
recommend that you start the server as a very unprivileged user andbind
it to some port (say 7001).
Most firewalls support redirecting ports. Your firewall can redirect
80
on the external net to 7001 on the internal net. That's the solution
I
would recommend.My Question: 3) Suppose iam having a cluster of 2 Managed servers runningon port
7070. And Iam having a Iplanet server working as a Webserver that basicallyproxies
requests to this cluster. Then what is the best approach that i shouldfollow
in this context.....to be honest with you ....i still couldnot understandwhat
does "binding" the webserver port to a managed server in weblogic mean.
I would have your firewall redirect 80 to whatever port Iplanet is
listening on and then have iplanet proxy to WLS.
Do not run your WLS servers as root.
-- Rob
Iam sorry for asking these "silly" questions(in your opinion) ...butiam a bit
confused.
thanks, sangita
Rob Woollen <[email protected]> wrote:
Running a server under root is a huge security hole.
The usual reason people want to do this is so they can bind to a port
<
1024. ie they want their web server to listen to 80.
There is a set uid option in WLS where you start the server as root
and
then after it binds to the low port, it will switch to another userthat
you specify.
Personally I would not recommend that you go that route. I would
recommend that you start the server as a very unprivileged user andbind
it to some port (say 7001).
Most firewalls support redirecting ports. Your firewall can redirect
80
on the external net to 7001 on the internal net. That's the solution
I
would recommend.
-- Rob
sangita wrote:
<Sure, it's possible to do this, >
how to do this?
<but why do you want to do it? >
Iam not sure why this group (the other group than me) does start theirserver
as "root"...but somebody from that group asked me about this today.
I would not recommend that you start WLS as root on your production
system ever under any cirucmstance.then what is the best approach and what are the pros and cons if westart the
server as "root" OR as different user ????
please advise ....
thanks again.
Rob Woollen <[email protected]> wrote:
Sure, it's possible to do this, but why do you want to do it?
I would not recommend that you start WLS as root on your production
system ever under any cirucmstance.
-- Rob
sangita wrote:
Hi,
is there any way to change the user privilege after i have startedthe managed
server with one user.....say for example ....i have started one
of
my Managed
server as "root" ...but after that i wanted to make this instance
work
under as
"inet"
how do i do this OR is it possible ????
please advise ....
sangita

Managed server CLASSPATH using Node Manager

Hi All,
I ve' created a clustered (WLS 10.3) environment with tow managed servers and Admin Server all in one machine and I use the Node Manager to start the managed Servers (by Admin Console or WLST), I want to set some jars to be loaded before WEBLOGIC_CLASSPATH actually (apache XMLbeans and SAXON jars) . I tried the setDomainEnv.cmd and placed my jars in the PRE_CLASSPATH variable but It is not working.Could u help me in this please?.
Thnx in advance

Here is the WLST online script to do what David Told, please make necessary changes to it.
connect(userName, passWord, URL)
clustHM = HashMap()
edit()
startEdit()
cd("/Servers/"+ManagedServer1+"/ServerStart/"+ManagedServer1)
print "setting attributes for mbean type ServerStart"
set("RootDirectory", domainDir)
set("Arguments","-jrockit -Xms256m -Xmx256m -Xss256k -da -Dplatform.home=/usr/local/bea10/weblogic10 -Dwls.home=/usr/local/bea10/weblogic10/server -Dweblogic.home=/usr/local/bea10/weblogic10/server -Dweblogic.management.discover=false -Dweblogic.management.server="+URL+" -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/usr/local/bea10/patch_wlw1001/profiles/default/sysext_manifest_classpath:/usr/local/bea10/patch_wls1001/profiles/default/sysext_manifest_classpath -Dweblogic.Stdout=/var/Domain_Logs/Public_Domain/serverlogs/stdout_ms1.log -Dweblogic.Stderr=/var/Domain_Logs/Public_Domain/serverlogs/stderr_ms1.log -Dlog4j.configuration=/usr/local/appstage/Publicdm/cluster_1/config/log4j/log4j.properties -Dconfig.location=classpath -Dconfig.filename=dev.config.xml -DweblogicName="+ManagedServer1+" -Djava.security.policy=/usr/local/bea10/weblogic10/server/lib/weblogic.policy")
set("SecurityPolicyFile", Security_Policy)
set("JavaHome", JAVA_HOME)
set("BeaHome", BEA_HOME)
set("ClassPath",CLASSPATH)
set("Username", userName)
set("Password", passWord)
Thanks
Togotutor
<b><a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free)</b>

Passing memory settings from the Node Manager to the Managed Server

All,
I am trying to start a Managed server from the Node Manager. The configuration is as follows:
I have a domain with two managed servers(M1, M2). I could start both of them using the shell scripts without any problems. Both of the servers has custom memory settings -Xms3072m -Xmx3072m -XX:PermSize=256m
to facilitate deployment and effective operation of managed servers (the applications being deployed are kind of large).
Now, I am trying to start the same two servers using Admin Console:
In the admin console: I created a Unix Machine(U1) assigned the managed servers (M1, M2) to U1. I started the Node Manager on U1.
When I try to start a Managed Server from console, the server is starting but the memory settings (-Xms3072m -Xmx3072m -XX:PermSize=256m ) are not passed to the managed server startup, so the application deployment is failing with out of Memory errors. I tried to assign same memory settings to Node manager assuming it will pass on that configuration to the node manager without any luck.
Any help is appreciated.
Thanks
Raj

Starting Managed Server from Node Manager

Redirecting stdout and stderr when starting a MS with the NM

We are looking at using the Node Manager for stopping and starting the managed servers in some of our projects, to give the testers/developers the ability with operator role in the WLS console to save them calling someone.
The only trouble is, with our existing shell start scripts we redirect shell level stdout and stderr to a file, i.e
nohup ./startManagedWebLogic.sh test1-ms11 >> $OUTFILE 2>&1 &
But how do you do the same when starting the same managed server using the node manager and the WLS Admin Console??
There is the argument "-Dweblogic.log.RedirectStdoutToServerLogEnabled=true", but this only redirects on the JVM level.
Is there a way around this problem to get the node manager outputing the same as our scripts do.
Any direction would be great.
Alistair.

Gene
Thanks for the replies and additional information.
I was almost sure that one of the previously suggested troubleshooting steps would solve the problem but unfortunately that was not the case.
So, let us look at the following factors....
1. Delete the Adobe Premiere Elements Prefs file and, if that does not work, then delete the whole 12.0 Folder in which the Adobe Premiere Elements Prefs file exists.
Local Disk C
Users
Owner
AppData
Roaming
Adobe
Premiere Elements
12.0
and in the 12.0 Folder is the Adobe Premiere Elements Prefs file that you delete. If that does not work, then you delete the whole 12.0 Folder in which the Adobe Premiere Elements Prefs file exists. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the complete path cited.
2. Try to open the Premiere Elements 12 Editor from its Adobe Premiere Elements.exe file rather than desktop icon which uses Adobe Premiere Elements 12.exe file.
Local Disk C
Program Files
Adobe Premiere Elements 12
and in the Adobe Premiere Elements 12 Folder is the Adobe Premiere Elements.exe file that you double click to open the Premiere Elements 12 Editor bypassing the Welcome Screen. If necessary, we could create a desktop shortcut for the Adobe Premiere Elements.exe file for future use to open the program.
Also, look at the necessity to right click the desktop icon for the program and the .exe files and apply Run As Administrator to each even if you are running the program from a User Account with Administrative Privileges.
3. Consider creating a new User Account with Administrative Privileges and install and running Premiere Elements 12 in it (I would save this consideration for the last.)
Please review. We will be watching for the results.
Thank you.
ATR

For server Eagle-PROD-Instance, the Node Manager associated with machine

I have a wlst script that creates a domain and a managed server. I associate the server with a machine that's attached to a node manager. It creates the managed server fine but when I try and start it I get this error
For server Eagle-PROD-Instance, the Node Manager associated with machine Eagle-Machine is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
The machine is associated with the Node Manager and the NM is running. I can start the managed server from the command line, but not from the admin console
This is the script, am I missing something?
Thanks
name: createManagedServer.py
description: This script create the weblogic domain, and executes each weblogic queue module
subfile. it reads a property file : weblogic_wlst.properties for server domain information
author     : mike reynolds - edifecs 2011
created     : April 8th 2011
import sys
from java.lang import System
from java.util import Properties
from java.io import FileInputStream
from java.io import File
from weblogic.management.security.authentication import UserEditorMBean
from weblogic.management.security.authentication import GroupEditorMBean
from weblogic.management.security.authentication import UserPasswordEditorMBean
# Loads the contents a properties file into a java.util.Properties
# configPropFile = "weblogic_wlst.properties"
def loadPropertiesFromFile(configPropFile):
     configProps = Properties()
     propInputStream = FileInputStream(configPropFile)
     configProps.load(propInputStream)
     propInputStream.close()
     return configProps
def getProperties():
     importConfigFile = sys.argv[1]
     print importConfigFile
     domainProps = loadPropertiesFromFile(importConfigFile)
     properties = Properties()
     input = FileInputStream(importConfigFile)
     properties.load(input)
     input.close()
     return properties
def create_users(username, password, description):
# create admin user
cmo.getFileRealms()
try:
userObject=cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
userObject.createUser(username,password,description)
print "Created user " + username + "successfully"
except:
print "check to see if user " + username + " exists "
def add_user_to_group(username):
print "Adding a user to group ..."
cmo.getFileRealms()
try:
userObject2 = cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
userObject2.addMemberToGroup('Administrators',username)
print "Done adding user " + username
except:
print "check to see if user " + username + " is already in group "
def connect_server(user,pw,url):
          connect(user,pw,url)
def create_machine():
try:
print 'Creating machine' + machine
# cd('/')
# create(machine, 'Machine')
mach = cmo.createUnixMachine(machine)
mach.setPostBindUIDEnabled(true)
mach.setPostBindUID('oracle')
mach.setPostBindGIDEnabled(true)
mach.setPostBindGID('oracle')
mach.getNodeManager().setNMType('ssl')
except:
     print "machine exists"
def build_domain():
### Read Basic Template
WL_HOME = "C:/Oracle/Middleware/wlserver_10.3"
readTemplate(WL_HOME+"/common/templates/domains/wls.jar")
template=WL_HOME+"/common/templates/domains/wls.jar"
cd('Servers/AdminServer')
set('ListenAddress', adminServerAddress)
set('ListenPort', int(adminServerPort))
cd('/')
cd('/Security/base_domain/User/weblogic')
cmo.setPassword('w3bl0g1c')
### Write Domain
setOption('OverwriteDomain', 'true')
print "writing domain " + domainDir + domainName
writeDomain(domainDir+'/'+domainName)
closeTemplate()
create_machine()
arg = "Arguments=\" -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -da\""
prps = makePropertiesObject (arg)
domain = domainDir + domainName
try:
     #startNodeManager()
#nmConnect('weblogic', 'w3bl0g1c', host, 5556, 'AdminServer', domain, 'ssl')
# nmStart('AdminServer')
startServer('AdminServer', domainName, url, adminUser, adminPassword, domainDir, 'true')
except:
print "could not connect to Node Manager"
def create_server():
# get server instance properties
name = properties.getProperty("serverName")
domain = properties.getProperty("domainName")
port = properties.getProperty("listenPort")
address = properties.getProperty("listenAddress")
servermb=getMBean("Servers/" + name)
machine = properties.getProperty("machineName")
nodePort = properties.getProperty("nodeManagerPort")
domainDir = properties.getProperty("domainDir")
if servermb is None:
          startEdit()
          cd('/')
          cmo.createServer(name)
          cd('/Servers/'+ name)
          cmo.setListenAddress(address)
          cmo.setListenPort(int(port))
          cd('/')
          cmo.createMachine(machine)
          cd('/Machines/' + machine + '/NodeManager/' + machine )
          cmo.setNMType('Plain')
          cmo.setListenAddress(address)
          cmo.setListenPort(int(nodePort))
          cmo.setDebugEnabled(false)
          cd('/Servers/' + name)
          cmo.setListenPortEnabled(true)
          cmo.setJavaCompiler('javac')
          cmo.setClientCertProxyEnabled(false)
          cmo.setMachine(getMBean('/Machines/' + machine ))
          cmo.setCluster(None)
          cd('/Servers/' + name + '/SSL/' + name)
          cd('/Servers/' + name + '/ServerDiagnosticConfig/' + name)
          cmo.setWLDFDiagnosticVolume('Low')
          cd('/Servers/' + name)
          cmo.setCluster(None)
          cd('/Servers/' + name + '/SSL/' + name)
          cmo.setEnabled(false)
### Executable Script
### CreateDomain.py
### Define constants
WL_HOME = "C:/Oracle/Middleware/wlserver_10.3"
print "Starting the script ..."
print "Getting properties ... "
properties = getProperties()
adminServerAddress = properties.getProperty("adminServerAddress")
adminServerPort = properties.getProperty("adminServerPort")
adminUser = properties.getProperty("adminUser")
adminPassword = properties.getProperty("adminPassword")
edifecsUser = properties.getProperty("edifecsUser")
edifecsPassword = properties.getProperty("edifecsPassword")
host = properties.getProperty("host")
domainDir = properties.getProperty("domainDir")
domainName = properties.getProperty("domainName")
user = properties.getProperty("username")
pw = properties.getProperty("passwd")
url = properties.getProperty("adminURL")
machine = properties.getProperty("machineName")
print "Building the domain..."
build_domain()
print "Connecting to server"
connect_server(adminUser, adminPassword, url)
edit()
startEdit()
# create managed server
# create_machine()
create_server()
print "Creating users"
# starting configuration tree
serverConfig()
create_users(adminUser, adminPassword, "Administrator")
add_user_to_group(adminUser)
create_users(edifecsUser, edifecsPassword,"Administrator")
add_user_to_group(edifecsUser)
# have to restart edit to save config
edit()
startEdit()
# nmKill('AdminServer')
print "saving configuration"
try:
     save()
     activate(block="true")
     print "script returns SUCCESS"
     print "admin server is running"
     print "starting server " + name
     startServer(domainName, name ,url,adminUser, adminPassword, domainDir,'true')
except:
     print "failed to save server"
     dumpStack()

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

Starting Admin Server with nohup from Node Manager

We are using WebLogic 9.1 on Windows 2003. I am able to start the Admin Server from the Node Manager using WLST but when the user logs off the server the Admin Server exits.
The documentation says to use the -Xrs or -Xnohup options for Sun Jvm or JRockit Jvm. Where should this option be invoked?
I have placed the option in the Arguments field of the 'Server Start' tab in the Admin Console. And I have also placed the option on the command line when invoking the WLST The Admin Server still exits when the user logs off the server.
Can this option be used with the WLST command that starts the Admin Server? If so, does anyone know the syntax?
Your help would be appreciated.
Thanks

Can you explain how are you doing this. Are starting the server using WLST nmStart()?
If you are using nmStart(), then is your nodemanager running as a windows service.
Also, the option you are referring to should be used for the JVM running as a Windows service. If you start nodemanager as a service (which you typically should do in your case), then you can place the -XnoHup option on the Java command line for the Nodemanager service..
Venkat

MicroSoft Content Management Server with WL Portal 10

Hello,
Has anyone got experience with integrating MS Content Management Server with the BEA WL Portal 10?
i need develop a custom SPI?
Comments, Issues, opinions?
Best Regards,
Zarco

------- Pallav Tandon wrote on 1/18/05 1:37 PM -------Cam you elaborate more on the type of integration you are looking for.WE have done integration at portlet level...crawler level etc for MCMS .. I can share my experiences if you can provide some direct queries
Hi Pallav, we are also contemplating integration of MSCMS 2002 with plumtree. Can you describe what types of integration you have done?
- Brandt

For server the Node Manager associated with machine is not reachable

Hello all,
I am getting this error, when i start my Managed Server which is in shutdown state
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The configuration details are
i am using weblogic 9.2 MP3 version in windows 2k3 server.
It has a machine vm-bea-dev, a cluster cluster-saa-dev, to which both the managed servers saa-dev-1 and saa-dev-2 are assigned. There are 3 applications deployed onto managed Server 1 and 1 for managed Server 2.
Managed Server 1 is in shutdown state, and when i start the server, it gives the error specified below
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The same for Managed Server 2 too, and this server is in Admin State, i dont know how it went into that state.
Can somebody please help me reslove it.
Thanks in advance

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

Starting a specific managed server with a different JVM.

Hello!
We have a Weblogic (11g 10.3.6.0) Domain created using the Configuration Wizard (WL_HOME/common/bin/config.sh). This domain was configured to use Oracle JRockit JVM. So, all managed servers in this domain uses JRockit. But for some test/P.O.C reasons we want to configure a specific managed server (in this same domain) to run on top of Sun HotSpot. We need do this without change the domain's default JVM (Oracle JRockit).
Is it possible?
I tried many ways but now I'm a bit confused. Reading the DOC [1] I tried to change the setDomainEnv.sh to set the JAVA_VENDOR ('Sun') and JAVA_HOME (/path/to/sun/jdk). But in this way you change the JVM for whole Domain.
If I change the Server's configuration using AdminConsole (ServerX>Configuration>Server Start page) and them start it using AdminConsole or NodeManager, it (partially) works. I mean, the server starts using Sun Hotspot JVM, but if you look at the command process used to statrt it, you can see something strange.
"/opt/Oracle/java/ *jdk1.7.0_07* /bin/java -Dweblogic.Name=server-2 -Dbea.home=/opt/Oracle/Middleware11g -Djava.security.policy=/opt/Oracle/Middleware11g/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.management.server=http://192.168.56.101:7001 -D *java.library.path* = */opt/Oracle/java/jrmc-4.0.1-1.6.0/jre/lib/amd64/jrockit:/opt/Oracle/java/jrmc-4.0.1-1.6.0/jre/lib/amd64:/opt/Oracle/java/jrmc-4.0.1-1.6.0/jre/../lib/amd64* :/opt/Oracle/Middleware11g/patch_wls1036/profiles/default/native:/opt/Oracle/Middleware11g/patch_ocp371/profiles/default/native:/opt/Oracle/Middleware11g/wlserver_10.3/server/native/linux/x86_64:/opt/Oracle/Middleware11g/wlserver_10.3/server/native/linux/x86_64/oci920_8 -D *java.class.path* =/opt/Oracle/Middleware11g/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/Oracle/Middleware11g/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:*/opt/Oracle/java/jrmc-4.0.1-1.6.0/lib/tools.jar*:/opt/Oracle/Middleware11g/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/Oracle/Middleware11g/wlserver_10.3/server/lib/weblogic.jar:/opt/Oracle/Middleware11g/modules/features/weblogic.server.modules_10.3.6.0.jar:/opt/Oracle/Middleware11g/wlserver_10.3/server/lib/webservices.jar:/opt/Oracle/Middleware11g/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/opt/Oracle/Middleware11g/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/opt/Oracle/Middleware11g -Dweblogic.system.BootIdentityFile=/opt/Oracle/Middleware11g/user_projects/domains/base_domain/servers/server-2/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -server -d64 -Xms512m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256m weblogic.Server"
As you can see above, the server process are still using java.class.path and java.library.path with references to Oracle JRockit JVM.
I've tested in x86_64 and Sun SPARC platform. On x86_64 the server starts with no problem. But on Solaris SPARC the server crashs during startup time.
So, my question is: how can we solve this? Are the Node Manager using setDomainEnv.sh or commEnv.sh vars to set the java.class.path and java.library.path opitons?
Thanks.
[1] http://docs.oracle.com/cd/E23943_01/web.1111/e13708/overview.htm

Hi,
You can use a different JVM for specific managed server by editing parameters in server start tab from console. But if you want to change java.class.path and java.library.path with references from Oracle JRockit JVM to JDK hotspot, then you have to create separate commonenv.sh,setdomainenv.sh and startWeblogic.sh file for your managed server.
java.class.path and java.library.path env variables generally generates from commonenv.sh file.
Regards,
Kishore

Starting managed server with nodemanager

Hi there,
Please help me with the weblogic server installation, i've studk with failed to start managed server with node manager. My scenario as below:
(1) set up the main server and able to run the server successfully.
(2) set up one managed server, set up one machine on same server as main server.
(3) assign machine to created managed server.
(4) after that i've tried to run that managed server and error giving as below:
Error from main server terminal
===================
<NodeManager> <BEA-300048> <Unable to start the server 'ManagedServer1': Exception while starting server 'ManagedServer1': java.io.IOException: Server failed to start up. See server output log for more details.>
Error from Node Manager Termal
====================
<Info> <MainServer> <'ManagedServer1'> <Server failed during startup so will not be restarted>
<Dec 7, 2009 7:04:45 PM> <Warning> <Exception while starting server ''ManagedServer1'': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Thanks in advance,
Tim

Sorry , i forgot to mention that the OS i am using is Solaris.
Thx

ClassNotFoundException When Starting Managed Server with NodeManager

Hi Experts,
ENV:
Weblogic Server 10.3.3
Webcenter 11.1.1.3
My managed server can be brought up correctly by stopManagedWebLogic.sh <ManagedServerName>. But when trying to start them up, app on that server can not run correctly, and node manager log complained that below classes are not found:
oracle.jrf.wls.JRFStartup
oracle.security.jps.wls.JpsWlsStartupClass
oracle.core.ojdl.weblogic.ODLConfiguration
oracle.jrf.AppContextStartup
oracle.ias.cache.Startup
oracle.dms.wls.DMSStartup
My Nodemanager is setup following instructions in OBE.Administering Managed Servers by Using the Node Manager(http://www.oracle.com/technology/obe/fusion_middleware/wls103/installconfig/admin_mngd_srvr/admin_ms_using_nm.htm#t4). Output javaclaspath of setWLSEnv.sh has been copy&pasted to admin console->server->..->Server start->classpath
Thanks,
Todd

Trying setting the property StartScriptEnabled=true instead of false.
You can change this in the nodemanager.properties file (usually located in the directory <middleware-home>/wlserver_10.3/common/nodemanager)
The classes are set in the startscripts, such as setDomainEnv, which is called by startWebLogic.
The latter script is set by default in the nodemanager.properties file, through the property StartScriptName=startWebLogic.cmd.

Start all managed server with nodemanager wls 8.1

Hi,
I've configured nodemanager in my environment, now I'd like to restart all managed servers at boot time. I've created a script that start the nodemanager process at boot time but I didn't found any properties to automatically restart all managed servers.
How can I do it ?
Thank you.
Fanelli Massimiliano
[email protected]

Great!
I had the same error: when starting UCM on WL Console, it starts and says Running. But when accessing it on the browser receive the error 404. In the other hand, when starting with Commands, it force shutdowns.
I have set the StartScriptEnabled property to true, now I can start UCM only on the command Line, to start it on WL Console, I have to manually start the node manager.
Is there a way/script to start the node manager automatically?
Regards,

Start managed server with the node manager???

Similar Messages

Maybe you are looking for