At the end of this chapter you will be able to:
A WebLogic Server administration domain is a logically related group of WebLogic Server resources. Domains include a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional WebLogic Server instances called Managed Servers. You deploy Web applications, EJBs, Web Services, and other resources onto the Managed Servers and use the Administration Server for configuration and management purposes only.
You can use a single WebLogic Server installation to create and run multiple domains, or you can use multiple installations to run a single domain. Depending on your particular business needs and system administration practices, you might decide to organize your domains based on criteria such as:
For development or test environments, you can create a simple domain that consists of a single server instance. This single instance acts as an Administration Server and hosts the applications that you are developing. The wl_server domain that you can install with WebLogic Server is an example of this type of domain.
The Administration Server operates as the central control entity for the configuration of the entire domain. It maintains the domain’s configuration documents and distributes changes in the configuration documents to Managed Servers. You can also use the Administration Server as a central location from which to monitor all resources in a domain. Admin Clients: To interact with the Administration Server, you can use the Administration Console, WLST, or create your own JMX client.
Managed Servers host business applications, application components, Web Services, and their associated resources. To optimize performance, Managed Servers maintain a read-only copy of the domain's configuration document. When a Managed Server starts up, it connects to the domain's Administration Server to synchronize its configuration document with the document that the Administration Server maintains. For production environments that require increased application performance, throughput, or high availability, you can configure two or more Managed Servers to operate as a cluster. A cluster is a collection of multiple WebLogic Server instances running simultaneously and working together to provide increased scalability and reliability.
In addition to the Administration Server and Managed Servers, a domain also contains the resources and services that Managed Servers and deployed applications require.
Security providers, which are modular components that handle specific aspects of security, such as authentication and authorization.
Note: All managed servers in a domain must run the same version of WebLogic Server. The administration server can run either the same version as the managed servers in the domain or a later service pack.
In designing your domain configuration, note the following restrictions:
You might find it useful to configure multiple domains based on specific criteria, such as system administrator responsibilities, the logical classification of applications, the geographical locations of servers, or size. The following table outlines the most common domain configurations. 1) Domain with managed servers: In typical production environments, several managed servers can host applications, and an administration server performs management operations. 2) Domain with managed servers and clusters: In production environments that require increased performance, throughput, or availability for an application, several managed servers might be grouped in a cluster. In such a case, the domain consists of one or more clusters with the applications they host, additional managed servers, if necessary, and an administration server to perform management operations. 3) Stand-alone Server Domain: In development or test environments, a single application and server might be deployed independently without managed servers. In such a case, you can have a domain consisting of a single administration server that also hosts the applications you want to test or develop. Note: In production environments, it is recommended that you deploy applications only on managed servers; the administration server should be reserved for management tasks.
Before you can develop and run a WebLogic application, you must first create a domain. The Configuration Wizard (illustrated in Figure 1-2), simplifies the process of creating and extending a domain. To create or extend a domain by using the Configuration Wizard, you simply select the product components to be included in the domain (or choose a template that best meets your requirements) and provide basic configuration information. The Configuration Wizard then creates or extends the domain by using the settings from templates.
After you create a domain by using the Configuration Wizard, you can start a WebLogic Server instance to run in the domain for developing, testing, and deploying applications.
You might want to customize your domain in the following circumstances:
You can start the Configuration Wizard in graphical mode from either the Windows Start menu or from the command line. Note: If you attempt to start the Configuration Wizard in graphical mode on a system that cannot support graphical display, the Configuration Wizard automatically starts in console mode.
On Windows: config.cmd
On UNIX: sh config.sh
1. Open an MS-DOS command prompt window (on Windows) or a command shell (on UNIX).
2. Go to the commonbin subdirectory of the product installation directory.
3. Execute the following command:
– Windows: config.cmd -mode=console
– UNIX: sh config.sh -mode=console
Note: The command and arguments must be entered in lower case.
The Welcome screen is displayed.
Note: silent mode is deprecated in WebLogic Server 9.X
The Configuration Wizard guides you through the process of creating a new domain quickly and easily, by selecting the product components that you want to include in your domain, or by using domain templates.
1. Start the Configuration Wizard as described in Starting the Configuration Wizard. The Welcome window is displayed
3. Select Generate a domain configured automatically to support the following products: WebLogic Server is selected, by default. Select the checkboxes corresponding to the other products that you want to include in the
4) Click Next. The Configure Administrator Username and Password window are displayed and configure the username and password for the administrator:
5) Select the WebLogic domain startup mode:
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.
Click next then The Customize Environment and Services Settings window is displayed.
6) Customizing the Environment and Service Settings… While creating the domain, you can specify the RDBMS security store settings, configure the distribution of your domain across servers, clusters, and machines, specify JDBC data sources, define JMS file store settings. Select Yes and click on Next.
7) Configure the Administration Server and Managed Servers
8) Configure Clusters
9) Assign Servers to Clusters
10) Configure Machines
11) Assign Servers to Machines
12) Enter the name of the domain and specify the domain location.
13) 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 name of this directory is the name of the domain.
This directory provides a quick way to deploy applications in a development server. When the WebLogic Server instance is running in development mode, it automatically deploys any applications or modules that you place in this directory. The files you place in this directory can be Java EE applications, such as: An EAR file, A WAR, EJB JAR, RAR archived module.
This directory contains scripts that are used in the process of starting and stopping the Administration Server and the Managed Servers in the domain. These scripts are generally provided as .sh files for UNIX and .cmd files for Windows. The bin directory can optionally contain other scripts of domain-wide interest, such as scripts to start and stop database management systems, full-text search engine processes, etc.
This directory contains the current configuration and deployment state of the domain. The central domain configuration file, config.xml, resides in this directory.
This directory contains extensions to the Administration Console, which enable you to add content to the WebLogic Server Administration Console, replace content, and change the logos, styles, and colors without modifying the files that are installed with WebLogic Server. For example, you can add content that provides custom monitoring and management facilities for your applications.
This directory contains files used for WebLogic domain provisioning. You should not modify any files in this directory.
Any JAR files you put in this directory are added to the system classpath of each server instance in the domain when the server’s Java virtual machine starts.
This directory contains domain configuration files representing configuration changes that have been requested, but not yet activated. Once the configuration changes have been activated, the configuration files are deleted from this directory.
This directory holds those security-related files that are the same for every WebLogic Server instance in the domain: SerializedSystemIni.dat This directory also holds security-related files that are only needed by the domain’s Administration Server: DefaultAuthorizerInit.ldift, DefaultAuthenticatorInit.ldift, DefaultRoleMapperInit.ldift
This directory contains one subdirectory for each WebLogic Server instance in the domain. The subdirectories contain data that is specific to each server instance.
This directory stores temporary files used in the change management process. You should not modify any files in this directory.
By default, configuration information is automatically copied from the Administration Server to each Managed Server. If instead, you prefer to stage configuration changes manually, you can use this directory as an alternative to the config directory.
You liked the article?
Like : 0
Vote for difficulty
Current difficulty (Avg): Medium
TekSlate is the best online training provider in delivering world-class IT skills to individuals and corporates from all parts of the globe. We are proven experts in accumulating every need of an IT skills upgrade aspirant and have delivered excellent services. We aim to bring you all the essentials to learn and master new technologies in the market with our articles, blogs, and videos. Build your career success with us, enhancing most in-demand skills in the market.
Get stories of change makers and innovators from the startup ecosystem in your inbox