Have you had problems starting your JDE containers / JVM’s from SM and need to know what you need to start to get this working? Don’t know which services to register to get things running? This post might help you!
There is a nodemanager in wls_home\server\bin, this in not the right one.
There are a series of cms files here which allow you to think that you can register your node manager, but you cannot. I guess it helps to think about these things at a higher level to understand what you are looking at.
You need an admin server to log into and also to run commands to your node managers.
You need node managers to look after domains and start and stop the applications within domains, this is sometimes referred to as a machine.
It seems to me that server manager needs both the admin server and the nodegent to start a JDE HTML server, but it does not need the nodeagent to start the admin server. This is interesting. As SM must talk with the admin server, which then sends the commands to the nodeManager.
installNodeMgrSvc.cmd
installSvc.cmd
setWLSEnv.cmd
startNodeManager.cmd
uninstallNodeMgrSvc.cmd
uninstallSvc.cmd
They are not the ones that you want to run.
you actually want to be in your domain home, something like:
F:\oracle\wls\user_projects\domains\E1_Apps\bin
You see the following files in this dir:
installNodeMgrSvc.cmd
setDomainEnv.cmd
setStartupEnv.cmd
startComponent.cmd
startManagedWebLogic.cmd
startNodeManager.cmd
startWebLogic.cmd
stopComponent.cmd
stopManagedWebLogic.cmd
stopWebLogic.cmd
uninstallNodeMgrSvc.cmd
You can then setDomainEnv.cmd and then install your service.
See that the service is created with the name or your domain!
So now you can user SM to start and stop servers that have been installed in this domain.
No comments:
Post a Comment