2 Replies Latest reply on Oct 1, 2012 4:13 PM by ManojBandarupally

    startManagedWeblogic.cmd is not referring startup.properties


      I am starting multiple managed servers by using startManagedWeblogic.cmd. But the startManagedWeblogic.cmd is not using domain_home/servers/server_name/data/boot.properties and domain_home/servers/server_name/data/nodemanager/startup.properties files while starting. Is there any way to pass startup properties to startManagedWeblogic.cmd?
        • 1. Re: startManagedWeblogic.cmd is not referring startup.properties
          Brett Curtis
          If you're using startManagedWeblogic.cmd it wont use anything related to nodemanager, unless your using nodemanager to call it with startscriptenabled. We use boot.properties for username/pass startup options. We do not store it in the data directory but in the servers/server_name/security directory. Might need to create the dir. Does this help ?
          1 person found this helpful
          • 2. Re: startManagedWeblogic.cmd is not referring startup.properties
            The files under
            will be used by nodemanager while starting the servers. You should configure nodemanager and use it to start the managed servers. See : http://docs.oracle.com/cd/E24329_01/web.1211/e21050/starting_nodemgr.htm#NODEM209 for more information. Also take a look at this : http://docs.oracle.com/cd/E24329_01/web.1211/e21050/java_nodemgr.htm#i1068413 for configuring nodemanager.properties to enable the StartScriptEnabled and StartScriptName