Assuming you’ve already made sure all the parameters in the nmConnect command are correct and the NM process is up and running, there is actually one more thing to check: has your domain been set up in Production Mode? If so, then the Node Manager credentials have been generated by the Configuration Wizard at domain creation time. While the AdminServer will be aware of these credentials by default (you are able to connect to the NM via de admin console, after all), you will not be able to connect via WLST since you have to provide this random username and password. The solution is to reset the credentials in the Administration Console.

To change the default Node Manager username and password, startup the Admin Server and access the administration console. Then, click your domain’s name from the “Domain Structure” area:

Then navigate to the “Security” tab and click on “Advanced”. You will find the Node Manager credentials:

Click “Lock and Edit” and change the credentials, then click “Save” and “Activate Changes”. No restarts are required. Now, your nmConnect command within WLST should be successful:

If you are worried about your password showing up in clear text in the startup scripts, you can use the storeUserConfig command to generate encrypted userconfigFile and a userKeyFile that you can then use in the nmConnect command.

For example, to create the user configuration file and key file:connect(‘weblogic’, ‘weblogic1’, ‘localhost:7001’)storeUserConfig('/shared/oracle/FMW_Home/user_projects/domains/FMW_XPS/userConfigFile','/shared/oracle/FMW_Home/user_projects/domains/FMW_XPS/userKeyFile')