altquark
Legendary Poster
Yes - the steps are good.
You're enrolling the Admin Server to the Nodemanager home using the "nmEnroll" command !
In your case, the statements should be as follows :
Step 5&6 With Weblogic Admin Server running :
Step 7 - kill the AdminServer
Step 8 - kill NodeManager
Step 9 - start NodeManager (the service now !)
Step 10,11 - connect to the NodeManager and start AdminServer:
Test to make sure everything comes up again (after the AdminServer has brought up all the JDE instances) by then rebooting your machine.
Using the instructions above, you can work out how to do exactly the same with Linux and any other platform. If you are STILL confused, I'd recommend getting a consultant in to help you !!!!
If you're not starting Weblogic up using the NodeManager like this, then you're probably not abiding by Oracles recommendations. I would probably highlight this as an issue if I had to perform a Technical Audit on your customers' installation if you didn't have this, because its the simplest method to auto-start weblogic instances, and you're using Oracles Nodemanager - which is what it is for. Any weblogic consultant that then later comes into your customer would then be able to easily understand how you're starting the weblogic instances without miscommunication.
Lastly, if you are EVER going to implement Oracle SOA Suite in a clustered environment - or something else in a clustered manner, then the nodemanager is the ONLY way to get everything working together....!!!
You're enrolling the Admin Server to the Nodemanager home using the "nmEnroll" command !
In your case, the statements should be as follows :
Step 5&6 With Weblogic Admin Server running :
Code:
[COLOR=#333333]c:\Oracle\Middleware\user_projects\domains\E1_Apps[/COLOR]\bin>setDomainEnv.cmd
[COLOR=#333333]c:\Oracle\Middleware\user_projects\domains\E1_Apps[/COLOR]>java weblogic.WLST
wls:/offline> connect('weblogic','Password','t3://{weblogicservername}:{weblogicadminport}')
wls:/E1_Apps/serverConfig>nmEnroll(domainDir='[COLOR=#333333]C:\Oracle\Middleware\user_projects\domains\E1_Apps[/COLOR]',nmHome='[COLOR=#333333]C:\Oracle\Middleware\user_projects\domains\E1_Apps[/COLOR]/nodemanager')
wls:/E1_Apps/serverConfig>exit()Step 7 - kill the AdminServer
Step 8 - kill NodeManager
Step 9 - start NodeManager (the service now !)
Step 10,11 - connect to the NodeManager and start AdminServer:
Code:
[COLOR=#333333]c:\Oracle\Middleware\user_projects\domains\E1_Apps[/COLOR]\bin>setDomainEnv.cmd
[COLOR=#333333]c:\Oracle\Middleware\user_projects\domains\E1_Apps[/COLOR]>java weblogic.WLST
wls:/offline> nmConnect(domainName='E1_Apps',username='weblogic',password='password')
wls:/nm/E1_Apps> nmStart('AdminServer')
wls:/nm/E1_Apps>exit()Using the instructions above, you can work out how to do exactly the same with Linux and any other platform. If you are STILL confused, I'd recommend getting a consultant in to help you !!!!
If you're not starting Weblogic up using the NodeManager like this, then you're probably not abiding by Oracles recommendations. I would probably highlight this as an issue if I had to perform a Technical Audit on your customers' installation if you didn't have this, because its the simplest method to auto-start weblogic instances, and you're using Oracles Nodemanager - which is what it is for. Any weblogic consultant that then later comes into your customer would then be able to easily understand how you're starting the weblogic instances without miscommunication.
Lastly, if you are EVER going to implement Oracle SOA Suite in a clustered environment - or something else in a clustered manner, then the nodemanager is the ONLY way to get everything working together....!!!
Last edited:
