Creating a WebLogic Domain

Before you can develop and run WebLogic-based applications, you must first create a domain. The Configuration Wizard guides you through the process of creating a new domain.

Start the Configuration Wizard as described in Starting the Configuration Wizard.

The Welcome window is displayed.

Select Create a new WebLogic domain and click Next.
Select one of the following options:

Generate a domain configured automatically to support the following products:

The WebLogic Server option is is selected, by default.

Select the check boxes corresponding to the other products that you want to include in the domain.

Base this domain on an existing template

Select this option if you want to create a domain by using an existing domain template. For information about domain templates, see Domain Template Reference.

Enter the full path to the template in the Template location field, or click Browse to navigate to the directory containing the required template.

Note:

While using the Configuration Wizard or the WebLogic Scripting Tool to create or extend a clustered domain with a template that has applications containing application-scoped JDBC and/or JMS resources, you may need to perform certain additional steps after the domain is created or extended. These additional steps are required to make sure that the application and its application-scoped resources are targeted and deployed properly in a clustered environment. For more information on targeting and deploying application-scoped modules, see Deploying Applications and Modules with weblogic.deployer.

Click Next.

The Configure Administrator Username and Password window is displayed.

Configure the username and password for the administrator.

The username is used to boot the administration server and connect to it. Do not use commas or any of the following characters: \t, < >, #, |, &, ?, ( ), { }.

The username is case sensitive.

The password value is encrypted. The password must contain at least eight characters, and is case sensitive.

Note: Do not use the weblogic as the password in a production environment.

Click Next.

The Configure Server Start Mode and JDK window is displayed.

Select the WebLogic domain startup mode.

In the development mode, the configuration of security is relatively relaxed, allowing you to auto-deploy applications.
In the production mode, the configuration of security is stringent, requiring a user name and password to deploy applications. Before putting a domain into production, familiarize yourself with the securing the production environment. For more information, see Securing a Production Environment.

For information about changing the run-time mode after you have created a domain, see “Change to production mode” in the WebLogic Server Administration Console Online Help.

Table 3-1 provides information to help you choose a startup mode that suits your requirements.

Table 3-1 Differences Between Development Mode and Production Mode
Function	In development mode...	In production mode...
SSL	You can use the demonstration digital certificates and the demonstration keystores provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL. For more information about managing security, see Configuring SSL.	You must not use the demonstration digital certificates and the demonstration keystores. If you do so, a warning message is displayed.
Deploying applications	WebLogic Server instances can deploy and update applications that reside in the `domain_name/autodeploy` directory automatically. It is recommended that this method be used only in a single-server development environment. For more information, see Deploying Applications to WebLogic Server.	The auto-deployment feature is disabled; so, you must use the WebLogic Server administration console, the `weblogic.Deployer` tool, or the WebLogic Scripting Tool.
Log file rotation	By default, when you start the WebLogic Server instance, the server automatically renames (rotates) its local server log file as `SERVER-NAME.log.n`. For the remainder of the server session, messages accumulate in the log file until the file grows to a size of 500 kilobytes. For more information, see Rotate Log Files.	The server rotates the local log file after the size of the file reaches 5000 kilobytes. When the server is configured for production mode, by default, all versions of the log files are kept. Administrators may want to customize the number of log files retained.
JDBC system resource	The default capacity is 15 connections.	The default capacity is 25 connections.

Select the JDK.

In the JDK Selection pane, select the JDK for the startup mode that you selected in the WebLogic Domain Startup Mode pane.

The Configuration Wizard presents a list of the JDKs included in the installer. You can choose one of these JDKs or another JDK that you have installed on your system.

Note:

If you select a JDK that is included in the installer, the Configuration Wizard creates server startup scripts to invoke the JDK. If you select a JDK that is not supplied by JDK, the Configuration Wizard does not configure the startup scripts; you must change the startup scripts manually. For more information about startup scripts, see WLS Performance and Tuning.

Select only those JDKs that are supported on the platform you are using. For a list of the JDKs that are supported for a specific platform, see Supported Configurations. The default selection reflects the JDK that best meets the requirements of your environment, based on the platform on which you are installing the domain.

Note:

If you plan to use the JRockit JDK in production mode, it is recommended that you develop and test your applications by using JRockit early in the project cycle. For more information, see the JRockit documentation.

Click Next.

The Customize Environment and Services Settings window is displayed.

While creating the domain, you can specify RDBMS security store settings; configure distribution of your domain across servers, clusters, and machines; specify JDBC data sources; and define JMS file store settings.

To configure the distribution of your domain across servers, clusters, and machines, or to modify existing JDBC and JMS file store settings, select Yes and click Next.

The Configure RDBMS Security Store Database window is displayed.

For information about configuring the RDBMS security store, managed servers, clusters, and machines see Customizing the Environment.

For information about specifying JDBC data sources and defining JMS file store settings, see Customizing JDBC and JMS Settings in WebLogic Domains.

To retain the current settings, select No, and click Next.

The Create WebLogic Domain window is displayed.

Enter the name of the domain and specify the domain location.

Domain names must not start with a number. This restriction prevents potential conflicts with internally-generated JDBC store table names, which must begin with a letter.
The domain directory can be located anywhere in the system. By default, it resides in BEA_HOME\user_projects\domains\domain, where BEA_HOME is the directory that contains the product installation, and domain is the name of the domain directory defined by the selected template.

The Configuration Wizard stores the config.xml file and all other generated components in the domain directory that you specify.

Click Create.

Note:

You cannot overwrite an existing domain. If a domain with the name you specified already exists in the selected location, you must either delete the existing domain, or specify a different name or location for the new domain.

The Creating Domain window displays status messages during the domain creation process.

Creating WebLogic Domains Using the Configuration Wizard

Creating a WebLogic Domain