start the admin server using WLST
参考:http://weblogic-wonders.com/weblogic/2011/01/04/remote-administration-of-domain-through-wlst/
To start the admin server using WLST, ensure that the admin server is associated to a machine. Once done, start the WLST tool.
Start the nodemanager using the command startNodeManager() as seen in the image.
直接双击D:\bea\wlserver_10.3\common\bin\wlst.cmd
CLASSPATH=D:\bea\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_
patch.jar;D:\bea\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_p
atch.jar;D:\bea\JROCKI~1\lib\tools.jar;D:\bea\WLSERV~1.3\server\lib\weblogic_sp.
jar;D:\bea\WLSERV~1.3\server\lib\weblogic.jar;D:\bea\modules\features\weblogic.s
erver.modules_10.3.0.0.jar;D:\bea\WLSERV~1.3\server\lib\webservices.jar;D:\bea\m
odules\ORGAPA~1.5/lib/ant-all.jar;D:\bea\modules\NETSFA~1.0_1/lib/ant-contrib.ja
r;PATH=D:\bea\patch_wls1030\profiles\default\native;D:\bea\patch_cie660\profiles\d
efault\native;D:\bea\WLSERV~1.3\server\native\win\32;D:\bea\WLSERV~1.3\server\bi
n;D:\bea\modules\ORGAPA~1.5\bin;D:\bea\JROCKI~1\jre\bin;D:\bea\JROCKI~1\bin;C:\W
INDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Common File
s\Thunder Network\KanKan\Codecs;C:\Program Files\Intel\WiFi\bin\;C:\Program File
s\ThinkPad Wireless LAN Adapter Software;D:\bea\WLSERV~1.3\server\native\win\32\
oci920_8Your environment has been set.
CLASSPATH=D:\bea\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_
patch.jar;D:\bea\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_p
atch.jar;D:\bea\JROCKI~1\lib\tools.jar;D:\bea\WLSERV~1.3\server\lib\weblogic_sp.
jar;D:\bea\WLSERV~1.3\server\lib\weblogic.jar;D:\bea\modules\features\weblogic.s
erver.modules_10.3.0.0.jar;D:\bea\WLSERV~1.3\server\lib\webservices.jar;D:\bea\m
odules\ORGAPA~1.5/lib/ant-all.jar;D:\bea\modules\NETSFA~1.0_1/lib/ant-contrib.ja
r;;D:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbembedded57.jar;D:\bea\WLSERV~1.
3\common\eval\pointbase\lib\pbtools57.jar;D:\bea\WLSERV~1.3\common\eval\pointbas
e\lib\pbclient57.jarInitializing WebLogic Scripting Tool (WLST) …
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> startNodeManager()
Launching NodeManager …
Properties: {}
Command: D:\bea\JROCKI~1\jre\bin\javaw.exe -classpath “D:\bea\JROCKI~1\jre\lib\
rt.jar;D:\bea\JROCKI~1\jre\lib\i18n.jar;D:\bea\patch_wls1030\profiles\default\sy
s_manifest_classpath\weblogic_patch.jar;D:\bea\patch_cie660\profiles\default\sys
_manifest_classpath\weblogic_patch.jar;D:\bea\JROCKI~1\lib\tools.jar;D:\bea\WLSE
RV~1.3\server\lib\weblogic_sp.jar;D:\bea\WLSERV~1.3\server\lib\weblogic.jar;D:\b
ea\modules\features\weblogic.server.modules_10.3.0.0.jar;D:\bea\WLSERV~1.3\serve
r\lib\webservices.jar;D:\bea\modules\ORGAPA~1.5\lib\ant-all.jar;D:\bea\modules\N
ETSFA~1.0_1\lib\ant-contrib.jar;D:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbem
bedded57.jar;D:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbtools57.jar;D:\bea\WL
SERV~1.3\common\eval\pointbase\lib\pbclient57.jar” weblogic.NodeManager “-v”
NMProcess: <2011-1-10 16:12:35> <INFO> <Loading domains file: D:\bea\wlserver_10
.3\common\bin\nodemanager.domains>
NMProcess: <2011-1-10 16:12:36> <WARNING> <Domains file not found: D:\bea\wlserv
er_10.3\common\bin\nodemanager.domains>
NMProcess: <2011-1-10 16:12:38> <INFO> <Loading identity key store: FileName=D:/
bea/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
NMProcess: <2011-1-10 16:12:39> <WARNING> <Node manager configuration properties
file ‘D:\bea\wlserver_10.3\common\bin\nodemanager.properties’ not found. Using
default settings.>
NMProcess: <2011-1-10 16:12:39> <Info> <Saving node manager configuration proper
ties to ‘D:\bea\wlserver_10.3\common\bin\nodemanager.properties“>
NMProcess: Node manager v10.3
NMProcess:
NMProcess: Configuration settings:
NMProcess:
NMProcess: NodeManagerHome=D:\bea\wlserver_10.3\common\bin
NMProcess: ListenAddress=
NMProcess: ListenPort=5556
NMProcess: ListenBacklog=50
NMProcess: SecureListener=true
NMProcess: AuthenticationEnabled=true
NMProcess: NativeVersionEnabled=true
NMProcess: CrashRecoveryEnabled=false
NMProcess: JavaHome=D:\bea\JROCKI~1\jre
NMProcess: StartScriptEnabled=false
NMProcess: StopScriptEnabled=false
NMProcess: StartScriptName=startWebLogic.cmd
NMProcess: StopScriptName=
NMProcess: LogFile=D:\bea\wlserver_10.3\common\bin\nodemanager.log
NMProcess: LogLevel=INFO
NMProcess: LogLimit=0
NMProcess: LogCount=1
NMProcess: LogAppend=true
NMProcess: LogToStderr=true
NMProcess: LogFormatter=weblogic.nodemanager.server.LogFormatter
NMProcess: DomainsFile=D:\bea\wlserver_10.3\common\bin\nodemanager.domains
NMProcess: DomainsFileEnabled=true
NMProcess: StateCheckInterval=500
NMProcess: QuitEnabled=true
NMProcess:
NMProcess: Domain name mappings:
NMProcess:
NMProcess:
NMProcess: <2011-1-10 16:12:41> <INFO> <Secure socket listener started on port 5
556>
Successfully launched the Node Manager.
The Node Manager process is running independent of the WLST process.
Exiting WLST will not stop the Node Manager process. Please refer
to the Node Manager logs for more information.
The Node Manager logs will be under D:\bea\wlserver_10.3\common\bin\.
现在nodemanager成功启动起来了!
Note: Nodemanager starts and runs irrespective of the WLST tool. Even if you exit from WLST, the nodemanager will still be running.
Now you need to connect to the nodemanager using the nmConnect() command. This needs to be done because you need to start the the servers through node manager.
在配置的过程中遇到了不少麻烦,对节点管理器的一些机制有了新的理解,繁琐的排错过程就不一一列举了,官方文档还是最给力的,看明白了自然就迎刃而解了!
http://www.oraclefmw.com/wls92/server_start/nodemgr.html#wp1097447
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/config_scripting/reference.html#1111568
留声机