If you are working on OFMW environments there is a utility script startNMProps.sh/.cmd file present in the ORACLE_COMMON_HOME/common/bin. This script would update the nodemanager.properties file, which is exists in the WL_HOME/common/nodemanger [NM_Home].
When I've used the example command given in the WLST help got the following error:
Here the problem could be solved or workaround with two options:
When you execute the startNodeManager command for the WLST offline you could pass two arguments: DomainRegistrationEnabled, NodeManagerHome.
You could experiment on NodeManager on Windows share your issues in the comments.
When I've used the example command given in the WLST help got the following error:
Caused by: java.lang.UnsatisfiedLinkError: no nodemanager in java.library.path
Here the problem could be solved or workaround with two options:
- Check your JAVA_HOME, JAVA_VENDOR values correctly pointed or not.
- Change the nodemanager.properties content with the following option
NativeVersionEnabled=false
When you execute the startNodeManager command for the WLST offline you could pass two arguments: DomainRegistrationEnabled, NodeManagerHome.
wls:/offline> startNodeManager(DomainRegistrationEnabled='true',NodeManagerHome='c:/Oracle/product/fmw/wlserver_10.3/common/nodemanager') Launching NodeManager ... Removed output here... Where it displays that generated nodemanager.properties and also shows the domain mapping. : : NMProcess: INFO: Secure socket listener started on port 5556 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 c:\Oracle\product\fmw\wlserver_10.3\common\nodemanager Node Manager starting in the background
You could experiment on NodeManager on Windows share your issues in the comments.
No comments:
Post a Comment
Please write your comment here