The steps for starting an Administration Server using WLST and Node Manager are :
i) Setting up your environment.
Add WebLogic Server classes to the
You can use a

ii) Start WLST Session using command : java weblogic.WLST

iii) Start Node Manager using command :
startNodeManager(verbose=’true’, NodeManagerHome=’C:\\Oracle\\Middleware\\wlserver_12.1\\common\\nodemanager’, ListenPort=’5556′, ListenAddress=’localhost’)


iv) Connect WLST to a Node Manager by entering the nmConnect command.
nmConnect(‘weblogic’, ‘weblogic123′, ‘localhost’, ’5556′, ‘base_domain’ , ‘C:\\Oracle\\Middleware\\user_projects\\domains\\base_domain’ , ‘ssl’)

note: Node Manager security relies on a one-way SSL connection between the client and server.If you are establishing a command line connection to the Java Node Manager using the WebLogic Server Scripting Tool (WLST) nmConnect command, you provide the Node Manager user name and password(here weblogic and weblogic123 respectively). Node Manager verifies the username and password against the domain’s nm_password.properties file.Node Manager credentials are located on the Security>General>Advanced Options of Console page.Administration Console users do not need to explicitly provide credentials to connect to Node Manager—the Node Manager user name and password are available in the domain configuration and are provided automatically.
v) Use the nmStart command to start a server.
nmStart(‘AdminServer’)

Monitor the status of the Administration Server by entering the nmServerStatus command.
nmServerStatus(‘AdminServer’)
vi) Connect WLST to a running WebLogic Administration Server instance using the connect command.
connect(‘weblogic’,'weblogic123′)

vii) Stop the AdminServer by entering the nmKill command.
nmKill(‘AdminServer‘)

viii) Disconnect the node manager : nmDisconnect() and Exit the WLST: exit()

i) Setting up your environment.
Add WebLogic Server classes to the
CLASSPATH
environment variable andWL_HOME
\server\bin
to the PATH
environment variable. ORYou can use a
C:\Oracle\Middleware\wlserver_12.1\server\bin\setWLSEnv
.cmd script to set both variables.ii) Start WLST Session using command : java weblogic.WLST
iii) Start Node Manager using command :
startNodeManager(verbose=’true’, NodeManagerHome=’C:\\Oracle\\Middleware\\wlserver_12.1\\common\\nodemanager’, ListenPort=’5556′, ListenAddress=’localhost’)
iv) Connect WLST to a Node Manager by entering the nmConnect command.
nmConnect(‘weblogic’, ‘weblogic123′, ‘localhost’, ’5556′, ‘base_domain’ , ‘C:\\Oracle\\Middleware\\user_projects\\domains\\base_domain’ , ‘ssl’)
note: Node Manager security relies on a one-way SSL connection between the client and server.If you are establishing a command line connection to the Java Node Manager using the WebLogic Server Scripting Tool (WLST) nmConnect command, you provide the Node Manager user name and password(here weblogic and weblogic123 respectively). Node Manager verifies the username and password against the domain’s nm_password.properties file.Node Manager credentials are located on the Security>General>Advanced Options of Console page.Administration Console users do not need to explicitly provide credentials to connect to Node Manager—the Node Manager user name and password are available in the domain configuration and are provided automatically.
v) Use the nmStart command to start a server.
nmStart(‘AdminServer’)
Monitor the status of the Administration Server by entering the nmServerStatus command.
nmServerStatus(‘AdminServer’)
vi) Connect WLST to a running WebLogic Administration Server instance using the connect command.
connect(‘weblogic’,'weblogic123′)
vii) Stop the AdminServer by entering the nmKill command.
nmKill(‘AdminServer‘)
viii) Disconnect the node manager : nmDisconnect() and Exit the WLST: exit()
No comments:
Post a Comment