Troubleshoot your Node Manager for AIA Foundation Pack 11gR1
By email@example.com on May 09, 2010
In the last couple of months, I have encountered several queries on node manager setup. This article should help you understand the most common pitfalls in setting up your node manager for AIA FP 11gR1 install. The following tips might help you go through the AIA 11gR1 install without any road blocks related to node manager.
- Monitor your Node Manager
First of all, verify if the node manager is reachable from weblogic admin console. To verify, open the console and browse to the machines link. Open the machine on which you have configured your node manager. In the resulting screen open the monitoring tab.This should show you the current status of your node manager. The following images explain the process.
- Starting the Node Manager
When you created a domain, you would have specified a value different from default settings for node manager address and port. In such a case, if you start node manager with default settings, the server can not reach the node manager. In order to avoid this you can verify the below.
Open the console and click on the machines link on the left hand panel under environments. Under machines click on the machine link for the configured node manager. Open the tab for the configurations of the node manager and verify the listen address and listen port against the default port and address for your node manager. You can follow the images below for the steps mentioned.
Once you have verified the above, browse to $WEBLOGIC_HOME/server/bin directory and execute 'startNodeManager.sh/cmd' script with the listen address and the listen port as parameters. This should make your node manager reachable to the admin server.
Note: In case your node manager is configured to listen to "localhost", remote deployment of AIA Foundation Packmay not be possible. It is recommended that you use a global address as the listen address for the node manager in the domain.
- Enabling the SOA Server Start from Node Manager
The AIA 11gR1 installer restarts SOA Server using node manager. To allow this you need to make sure that "StartScriptEnabled" property in the nodemanager.properties file under $WEBLOGIC_HOME/common/nodemanager directory is set to true.If the above step is not performed, the JRF classes will not be available to the SOA Server upon re-start and all subsequent deployments would fail. In order to ensure the above step is performed appropriately, try to shut down and restart the server from the Weblogic AdminConsole.
I hope the above common issues and solutions will help you get through most of your AIA 11gR1 deployments without any issues with the node manager.
Enjoy your Installs.