This article provides a quick overview of managing domains in WebLogic Server 12c. The examples all relate to WebLogic 12.1.2 and 12.1.3. If you are using WebLogic 12.1.1, you should probably refer to this article . - Create a Domain - Update a Domain - Delete a Domain - Creating a Boot Identity File - Altering Server Port Settings - Switching Development/Production Startup Mode Related articles. Start the Configuration Wizard. Accept the "Create a new WebLogic domain" option and enter the domain location, including the domain name at the end of the location. In this case I used "/u01/app/oracle/config/domains/testDomain". Click the the "Next" button. Select the templates the domain requires and click the "Next" button. Depending on the options you pick, a number of additional steps may be included.

Enter the application location, including the domain name in the path, and click the "Next" button.

Enter the administor account credentials and click the "Next" button.

Enter the domain mode and JDK, then click the "Next" button.

Select the "RCU Data" option and enter the database details. Click the "Get RCU Configuration" button.

Once the details are retrieved, click the "Next" button.

Accept the component datasources by clicking the "Next" button.

Once the JDBC tests have completed successfully, click the "Next" button.

Select the advanced configuraton options you require and click the "Next" button. For this example I just configured the Node Manager. Depending on the options you pick, extra steps may be added.

Select the type of node manager you require and enter the credentials. Click the "Next" button.

If you are happy with the summary information, click the "Create" button.

Once the configuration is complete click the "Next" button.

Make a note of the Admin Server URL and click the "Finish" button.

The following scripts are created for the "testDomain" domain. You will need to create a Boot Identity File if you want to use the "&" to start the domain or and managed servers as background processes. Once the domain is started, the administration console is available in a browser using a URL such as "http://machine:7001/console". Updating a domain involves similar screens to those seen during the installation. - Start the Configuration Wizard. - Select the "Update an existing domain" option, select the required domain location and click the "Next" button. - Select the additional product templates and click the "Next" button. - Work through the additional configuration steps, as you did during the previous creation. - If you are happy with the information in the configuration summary, click the "Update" button. - Wait while the domain is update, then click the "Next" button. - Click the "Finish" button to exit the Configuration Wizard. To remove the "testDomain" domain we just created, do the following steps: - Stop the processes associated with the domain. Stop the processes associated with the domain. - Remove the relevant domain entry from the "$MW_HOME/domain-registry.xml" file. Remove the relevant domain entry from the "$MW_HOME/domain-registry.xml" file. - If you are not using a per-domain node manager, remove the relevant domain entry from the "nodemanager.domains" file. When using a per-domain node manager, the relevant file will be cleaned up by the following step. If you are not using a per-domain node manager, remove the relevant domain entry from the "nodemanager.domains" file. When using a per-domain node manager, the relevant file will be cleaned up by the following step. - Delete the "testDomain" application and domain directories. Delete the "testDomain" application and domain directories. Stop the processes associated with the domain. Remove the relevant domain entry from the "$MW_HOME/domain-registry.xml" file. If you are not using a per-domain node manager, remove the relevant domain entry from the "nodemanager.domains" file. When using a per-domain node manager, the relevant file will be cleaned up by the following step. Delete the "testDomain" application and domain directories. When running in production mode, starting a server requires the credentials you provided while creating the domain. Using a boot identity file prevents you from having to type in the username/password each time the server is started. Create a file called "boot.properties" with the following contents. Save the file under the "$DOMAIN_HOME/servers/<server-name>/security" directory. The managed server will now start and stop without needing credentials. This should be done for the AdminServer, as well as all managed servers. Alternatively, modify the in the "setDomainEnv.sh" file to point to the location of the file. For example, if the "boot.properties" file is in the domain's home directory, you could place the following lines after the definition. This method works fine for startup, but shutdown will still require credentials, so it is not as convenient. The first time the server starts using a boot identity file, it will encrypt the credentials in the file and use them when starting in future. When you create a domain you will automatically create an AdminServer that listens on port 7001 by default. To change this, edit the "$DOMAIN_HOME/config/config.xml" file, adding or amending the "listen-port" entry, shown in bold. There are two locations where the startup mode can be set. If you are using the Java based controls the mode is picked up from the "$DOMAIN_HOME/config/config.xml" file. Set the "production-mode-enabled" tag to the appropriate value. If you are starting the domain using the generated startup scripts, you should edit the "$DOMAIN_HOME/bin/setDomainEnv.sh" file. Set the "PRODUCTION_MODE" parameter to the appropriate value. To prevent confusion, it makes sense to keep both files set to the same value. For more information see: Hope this helps. Regards Tim...