How to change the nodemanager password on a machine with no AdminServer installed in a Fusion Applications environment

Introduction

 

In a Fusion Applications environment where a machine has been provisioned with no AdminServer it is not possible to change the node manager password using the console.
For security and during cloning you may need to change this password and this article describes how to do that.

 

 

Description of environment

 

Here is a short overview about the installation based on the CommonDomain. All information given for that domain would also fit for any other domain used in Fusion Applications.

Let us assume we have three machines available and CommonDomain is a multi-server domain spread across these three machines. The machines are named machineA, machineB and machineC. A graphical overview of this installation is given in Diagram1:

Diagram1:

diagram1

 

Prerequisites

 

In this article we will focus on the method to change the nodemanager passwords for machineB and machineC. For machineA where an AdminServer is running, you can use the standard solutions like changing the password through the wls console or with a wlst script. There is lots of information about that in the web that you can easily find.

Here is now a description how to change nodemanager password on machineB and machineC.

In any Fusion Applications installation you will see a file structure like this:

$APPLTOP/fa/config/domains/<hostname>

or sometimes it can be :

$APPLTOP/fa/instance/domains/<hostname>

where $APPLTOP can differ from installation to installation.

In our example we will use /u01/app as value for $APPLTOP.

So we have this structure:

/u01/app/fa/instance/domains/machineA/CommonDomain

/u01/app/fa/instance/domains/machineB/CommonDomain

/u01/app/fa/instance/domains/machineC/CommonDomain

 

Underneath these directories you will see the subdirectory config/nodemanager which should include a file named : nm_password.properties.

So for machineB you will see : /u01/app/fa/instance/domains/machineB/CommonDomain/ config/nodemanager/nm_password.properties.

All of these files should look like this :

#Node manager user information

#Sat Aug 10 07:20:43 UTC 2013

hashed={Algorithm\=SHA-256}szEOYms/EyFzmxyNahvttq7zB2v5gFyUcCMew/qbHys\=

 

Procedure to change passwords

 

Now check that no nodemanager process is running on machineB and machineC. If there are running processes please stop them first before proceed.

Now we need to change the files:

/u01/app/fa/instance/domains/machineB/CommonDomain/ config/nodemanager/nm_password.properties

and

/u01/app/fa/instance/domains/machineC/CommonDomain/ config/nodemanager/nm_password.properties

in an editor of your choice.

Remove the line starting with hashed in these files.

Then add these two new lines in both files:

username=admin

password=<newpasswordincleartext>

In this example we use admin as username as this is the standard for Fusion Applications.If you are not sure check the username in config.xml file of the CommonDomain.

The new password for the nodemanger must in clear text, after saving and closing the files start the nodemanager on machineB and machineC.

 

Verify the changes

 

Check that the change has worked by viewing the nm_password.properties you previously updated. They should now both have again the line starting with hashed instead of the manually created new lines and this will confirm that the password change is successful.


Add Your Comment