Node Manager in Weblogic Server, Weblogic Multiple domains Single Node Manager:
Node Manager is a utility in Weblogic Server.Node Manager is used to perform the following tasks in weblogic server :
1) Start the administration and managed server instances from remote location
2) Stop the administration and managed server instances from remote location
3) Restart the administration and managed server instances from remote location
Node manager is available in two forms/versions
1) Jave based
2) Script based
Node manager process is machine-specific and not associated with a weblogic domain.
Weblogic Provide User Credentials For Starting a Server:
When we create a domain, the Configuration Wizard prompts us to provide the username and password for an initial administrative user.If we create the domain in development mode,the wizard saves the username and encrypted password in a boot identity file.
A boot identity file is a text file that contains user credentials for starting and stopping an instance of WebLogic Server.
It is located at :
domain_name/servers/server_name/data/nodemanager
A WebLogic Server instance can refer to a boot identity file during its startup process. If a server instance does not find such a file, it prompts us to enter credentials.If we create a domain in production mode, or if we want to change user credentials in an existing boot identity file, we can create a new boot identity file.WebLogic Server does not support copying a boot identity file from one server root directory to another.
Creating a boot identity file for an Administration Server in Weblogic:
Weblogic Server - Notifications when adding server to a cluster happens as follows : The weblogic server cluster broadcasts the availability of new instance every time a new instance is added to the cluster. Cluster-aware stubs periodically update their list of available server instances.Weblogic Server - Notifications when adding server to a cluster
If you use the Configuration Wizard to create a domain in development mode, the Configuration Wizard creates an encrypted boot identity file in the security directory of the Administration Server's root directory.If a boot identity file for an Administration Server does not already exist, and if you want to bypass the prompt for username and password, create one as follows. This usually happens when we create a domain in production mode.
Follow the steps to create a boot identity file for an administrative server in weblogic:
1) Start the Administration Server at least once and provide the user credentials on the command line.During the Administration Server's initial startup process, it generates security files that must be in place before a server can use a boot identity file.
2) Place the following two lines in a text file:
username=username
password=password
The username and password values must match an existing user account in the Authentication provider for the default security realm and must belong to a role that has permission to start and stop a server.
3) Save the file.If you save the file as boot.properties and locate it in the security directory of the server's root directory, the server automatically uses this file during its subsequent startup cycles.
4) The first time you use this file to start a server, the server reads the file and then overwrites it with an encrypted version of the username and password.
Second method is the usage of java weblogic.server command in the command-line.
Usage :
java -Dweblogic.management.username=weblogic
-Dweblogic.management.password=weblogic
-Dweblogic.system.StoreBootIdentity=true
-Dweblogic.Name=myAdminServer weblogic.Server
Webcentre installation failure RCU-6083:
I tried installing fusion middleware components using repository creation utility. At the point of installing Webcenter, I got the following error. RCU-6083:Failed - Check prerequisites requirement for selected component:WEBCENTER Please refer to RCU log at D:rcuHomerculoglogdir.2010-09-06_22-38rcu.log for details. Error: Oracle Initialization Parameter 'PROCESSES' is too low. Cause: The Oracle Initialization Parameter 'PROCESSES' must be at least 300. Action: Change the Database Initialization Parameter 'PROCESSES' to 300 or more, then rerun RCU. RCU-6092:Component Selection validation failed. Please refer to log at D:rcuHomerculoglogdir.2010-09-06_22-38rcu.log for details.
Solution :
1) Set the value of processes initialization parameter in the database to value greater than 300 . Follow the steps
SQL> show parameter processes
NAME TYPE VALUE
------------------------------------ ----------- ---------------------
aq_tm_processes integer 0
db_writer_processes integer 1
gcs_server_processes integer 0
global_txn_processes integer 1
job_queue_processes integer 1000
log_archive_max_processes integer 4
processes integer 150
SQL> alter system set processes=500 scope=both;
alter system set processes=500 scope=both
*
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified
SQL> show parameter processes
NAME TYPE VALUE
processes integer 150
SQL> alter system set processes=500 scope=spfile;
System altered.
Now try running rcu and the problem gets fixed.
