WebLogic stopManagedWeblogic.sh script prompts for username and password for shutting down managed server

6
votes

The managed server created in the WebLogic 12c environment is prompting for the username and password when stopping the managed server with stopManagedWeblogic.sh script even when boot.properties file is present with correct credentials.

The boot.properties file configured in some other accessible location whose path is specified using -Dweblogic.system.BootIdentityFile java option

I've observed below strange behavior

  • It's not prompting for username and password when starting the managed server with startManagedWeblogic.sh script(I suppose it's looking into boot.properties file).
  • It's not prompting for username and password when starting and stopping admin server

It's prompting for username and password only in case of managed server shutdown using stopManagedWeblogic.sh script.

Is passwordless managed server shutdown not supported in WebLogic ?, as I don't want username and password specified as a parameter to stop script.

2
weblogicweblogic12c
I experience the same behaviour. Try stopping the whole stack at once using the ${domain_home}/bitools/bin/stop.cmd instead. – access_granted

2 Answers

2
votes

I faced a similar issue and could resolve it by trying the following:

  1. create the directory <domain_home>/servers/<managed_server>/security
  2. create boot.properties in the above directory with the below values:
    username=<username>
    password=<password>

Now, start/stopManagedWeblogic.sh would work without prompting for credentials.

0
votes

It is identified as a bug in WebLogic 12c

The stopManagedWeblogic.sh implementation logic ignores -Dweblogic.system.BootIdentityFile option and checks the boot.properties file inside <domain_home>/servers/<managed_server_name>/security/boot.properties location, if boot.properties file is not present in this location, it prompts for admin server credentails.