Overview of Starting and Stopping Procedures

Starting and Stopping Oracle Fusion Middleware 4-3 UNIX MW_HOMEuser_projectsdomainsdomain_namebinstartManagedWebLogic.sh managed_server_name admin_url Windows MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd managed_server_name admin_url When prompted, enter your user name and password. To stop a WebLogic Server Managed Server, use the following script: UNIX MW_HOMEuser_projectsdomainsdomain_namebinstopManagedWebLogic.sh managed_server_name admin_url username password Windows MW_HOME\user_projects\domains\domain_name\bin\stopManagedWebLogic.cmd managed_server_name admin_url username password

4.2.3 Enabling Servers to Start Without Supplying Credentials

You can enable the Administration Server and Managed Servers to start without prompting you for the administrator user name and password. 1. For the Administration Server, create a boot.properties file: a. Create the following directory: MW_HOMEuser_ projectsdomainsdomain_nameserversAdminServersecurity b. Use a text editor to create a file called boot.properties in the security directory created in the previous step, and enter the following lines in the file: username=adminuser password=password 2. For each Managed Server: a. Create the following directory: MW_HOMEuser_ projectsdomainsdomain_nameserversserver_namesecurity b. Copy the boot.properties file you created for the Administration Server to the security directory you created in the previous step. 3. Restart the Administration Server and Managed Servers, as described in Section 4.2.1 and Section 4.2.2 .

4.2.4 Configuring Node Manager to Start Managed Servers

If a Managed Server contains other Oracle Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter, or Oracle JRF, the Managed Servers environment must be configured to set the correct classpath and parameters. This Note: When you start the Administration Server or Managed Server, the user name and password entries in the file are encrypted. For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible in order for the entries to be encrypted. See Also: Boot Identity Files in the Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server for more information