Weblogic Directory Structure And Usage

It is very important to know what directory stores what and what are the use of it. By creating a domain, you define a collection of resources, such as:

• Managed Servers

• Clusters

• Database connections

• Security services

• Java EE applications

After the domain has been created, some files and directories are placed on your local server.

domain-name: The name of this directory is the name of the domain.

• autodeploy: In development mode, WLS automatically deploys any applications or modules that you place in this directory. This directory provides a quick way to deploy applications in a development server. When the Oracle WebLogic Server instance runs in development mode, it automatically deploys any applications or modules that are placed in this directory.

 

• bin: This directory contains the scripts that are used for 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 domainwide interest, such as scripts to start and stop database management systems, full-text search engine processes, and so on.

 

• config: The current configuration and deployment state of the domain is stored into the configuration repository, represented as the config.xml. All configurations in WebLogic are stored as xml files in this directory. When the Admin Server boots, it reads this file and knows how its domain is configured. Managed Servers also use this configuration for their part/role within the domain.

 

• console-ext: This directory contains extensions to the Administration Console, which enables you to add content to Oracle WebLogic Server Administration Console, replace content, and change the logos, styles, and colors without modifying the files that are installed with Oracle WebLogic Server. For example, you can add content that provides custom monitoring and management facilities for your applications.

 

• init-info: This directory contains files that are used for WebLogic domain provisioning. You should not modify any files in this directory.

 

• lib: Any JAR files that you put in this directory are added to the Java system CLASSPATH of each server instance in the domain when the server’s Java Virtual Machine starts.

 

• pending: This directory contains the domain configuration files that represent the configuration changes that have been requested, but not yet been activated. After the configuration changes are activated, the configuration files are deleted from this directory. Configurations can be changed at runtime in the console of the Administration Server. Before they are implemented within the domain, they are temporarily stored in this directory.

 

• security: This directory holds the security-related files that are same for every Oracle WebLogic Server instance in the domain: SerializedSystemIni.dat.It also holds the security-related files that are needed only by the domain’s Administration Server: °° DefaultAuthorizerInit.ldift °° DefaultAuthenticatorInit.ldift °° DefaultRoleMapperInit.ldift

 

• servers: The server’s directory that contains the subdirectories for the Administration and Managed Servers is created the first time the servers are started. This directory contains one subdirectory for each Oracle WebLogic Server instance in the domain. The subdirectories contain data that is specific to each server instance.

 

• tmp: This directory is used for temporarily storing files. You should not modify any files in this directory.

 

• user_staged_config: This directory is an alternative to the config directory, if the domain is set up such that the configuration information is “user-staged”.

In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.