Today morning one of my buddy pinged me from my team, seeking help on an issue he is faceing in his newly configured WL domain for his learnings.
Understanding the Issue
My buddy novice WLA is trying to start the WebLogic instance on a remote machine. He is working on Solaris 10 operating environment, WebLogic 9.2. I asked for Java version, He executed the following command:
$ java -version
I asked for jps command execution the system is refused and said that ' jps is bad cammand'. I understand that JAVA_HOME is not set for his environment. asked for echo $PATH. It is showing Java Path. Ohh!! what is missing then??
$which java
this resulted that JAVA_HOME is NOT set to weblogic installation JDK, it was pointed to JAVA_HOME come with the Solaris installation. I understand that could be one of the reason of not starting the server instance. Update the .profile file with JAVA_HOME as required to set JDK residing in WebLogic installation path.
What is your NodeManager saying?
My buddy located the logs and found the following line
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE
To avoiding this Exception you must have certificate generated and installed as requested bye nodemanager. Why we need this SSL certificate? Open the WebLogic Admin console, found that he is working with SSL type of Node Manager. If you don't have secure certificates to configure you should not use SSL type nodemanager. I suggested better to use "Plain" type for the NodeManager configuration on the machine for learning purpose. Change it in the admin console and save the changes.
Redefining NM properties
You need to update few NodeManager properies on every machine your domain is configured.
Machine wise changes
ListenAddress=yourmachineip
ListenPort=5557
Common "Plain" setting for all the machines involved in domain
SecureListener=false
Stop the Admin server and managed servers (if any running) stop the NodeManger in all machines the domain configured.
Now, First start the NodeManager in the which Admin server residing then start the Admin Server. After Admin Server starting all the domain configuration details will be captured by NodeManager on that machine and ready for communicate with remote NodeManagers. Next, Start the NodeManager on the remote Machine(s) .
Finally, start the remote server using admin console. to start your remote managed server make sure that your admin server, Node Managers on admin machine and remote machines must be running without any ERROR or WARN messages. Conclude your configuration is successful by checking the Node Manager logs, and on the admin console check the server state
Note that jps command will list all java processes which includes NodeManager process too.
$jps
12121 NodeManager
4544 Server
Further References for Secure NodeManager:
1. SSL Node Manager configuration
2. Fisal SSL
After changing myself to a WLA middleware server-bender, this new AVATAR have many responsibilities on my shoulders. Everything is need to be controlled with my middleware skills those I am sharing with a Smart WLA (You). I have made my own ways of monitoring and leverage many automated tasks, each of them with powerful shell scripting skills on Sun-Solaris, Linux.
No comments:
Post a Comment