Где находится файл config xml
pfSense® software stores its settings in an XML format configuration file. All configuration settings including settings for packages are held in this one file. Run-time configuration files for services and firewall behavior are generated dynamically based on the settings held within this XML configuration file.
Those familiar with FreeBSD and related operating systems have found this out the hard way, when their changes to system configuration files were repeatedly overwritten by the firewall before they came to understand that pfSense software handles everything automatically.
The configuration file is stored at /conf/config.xml on the firewall.
Server Root Directory for a Managed Server Started with Node Manager
If you use the Node Manager to start a Managed Server, the root directory is located on the computer that hosts the Node Manager process. To determine the location of the server's root directory, WebLogic Server does the following:
The server root directory for a Managed Server started with Node Manager directory contains a subdirectory for each Managed Server instance. The name of the subdirectory is the name of the server as defined in the domain configuration.
config/ startup
This directory contains system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
config/ diagnostics
This directory contains system modules for instrumentation in the WebLogic Diagnostic Framework. For more information, see Understanding the WebLogic Diagnostic Framework.
config/ security
This directory contains system modules for the security framework. It contains one security provider configuration extension for each kind of security provider in the domain's current realm. For more information, see Understanding WebLogic Security.
Editin g Configuration Files
In most circumstances, you should not directly modify the config.xml file or the other configuration files. Instead, use the Administration Console or one of the other tools described in Summary of System Administration Tools and APIs in Overview of WebLogic Server System Administration to modify the domain's configuration. The configuration changes will then be reflected in the configuration files.
Directly modifying configuration files may be appropriate if you choose to place configuration files and other components of your installation under source control, managing them using WLST.
Warning: You cannot edit configuration files while WebLogic Server is executing, since WebLogic Server rewrites the files periodically. Your changes will be lost and, depending on your platform, you could cause WebLogic Server failures.
Since the WebLogic Server configuration files are well-formed XML files, it is possible to modify them using XSLT or to script certain repetitive changes using an XML parser application such as Apache Xerces, or JDOM. Be sure to test any scripts you create thoroughly and always make a backup copy of each configuration file before you make any changes to it.
config/ deployments
This directory holds the domain's deployed applications, in either archive file or exploded archive directory format.
config/ jms
This directory contains system modules for JMS: global JMS modules that can be configured directly from JMX (as opposed to JSR-88). For more information, see Messaging and WebLogic Server (JMS).
servers/server-name/logs/connector
This directory is the default base directory for connector module (JCA ResourceAdapter) logs.
servers/server-name/logs/diagnostic_images
This directory holds information created by the Server Image Capture component of the WebLogic Diagnostic Framework. For more information, see Understanding the WebLogic Diagnostic Framework.
Элементы Config.xml
Элемент верхнего уровня (обязательно). Имеет атрибут Product, например: Product = Lync
Определяет, как при установке будут обрабатываться компоненты конкретного продукта. Следующие атрибуты используются для предотвращения установки служб Business Connectivity Services, включая общие компоненты, которые мешают работе Outlook 2010:
Дочерние элементы = " Force"
Уровень пользовательского интерфейса, отображаемого пользователю программой установки. Обычно используются следующие атрибуты:
CompletionNotice = " Да " | " нет " (по умолчанию)
Атрибута AcceptEULA = " Да " | " нет " (по умолчанию)
Параметры ведения журнала программой установки. Обычно используются следующие атрибуты:
Type = " Off " | " Standard " (по умолчанию) | " Подробный"
Template="filename.txt" (имя файла журнала)
Определяет значения для свойств программы установщика Windows. Обычно используются следующие атрибуты:
Параметр Name " (имя свойства установщика Windows)
Value = " value " (значение, которое нужно присвоить свойству)
Полный доменный путь точки сетевой установки, из которой запускается установка. Содержит атрибут Location:
В следующем примере показан файл Config.xml для типичной автоматической установки Lync 2013.
config/ nodemanager
This directory holds configuration information for connection to the Node Manager. For more information, see Using Node Manager to Control Servers in Managing Server Startup and Shutdown.
Subsi diary Configuration Files
In previous releases, the config.xml file was a repository for all configuration information. In this release, several WebLogic Server subsystems are configured in subsidiary configuration files that are referred to by the central config.xml file. These subsidiary configuration files reside in subdirectories of the /domains/ DOMAIN_NAME /config directory. For more information about these subsidiary configuration files, see Domain Directory Overview and Domain Directory Contents.
servers/server-name/cache
This directory holds directories and files that contain cached data. By "cached" here we mean that the data is a copy, possibly in a processed form (compiled, translated, or reformatted), of other data.
config
This directory contains the current configuration and deployment state of the domain. The central domain configuration file, config.xml , resides in this directory
servers/server-name/bin
This directory holds executable or shell files that can be or must be different for each server. The server environment script ( setServerEnv.sh or setServerEnv.cmd ) is an example of a file that resides here because it can differ from one WebLogic Server instance to the next, for example, depending on whether the server instance has its own startup plan.
Config uration File Archiving
You can configure WebLogic Server to make backup copies of the configuration files. This facilitates recovery in cases where configuration changes need to be reversed or the unlikely case that configuration files become corrupted. When the Administration Server starts up, it saves a JAR file named config-booted.jar that contains the configuration files. When you make changes to the configuration files, the old files are saved in the configArchive directory under the domain directory, in a JAR file with a sequentially-numbered name like config-1.jar.
Whether to back up configuration files is specified by the DomainMBean.ConfigBackupEnabled attribute, whose default value is false. The number of configuration archive files retained is specified by the DomainMBean.ArchiveConfigurationCount attribute, whose default value is 0.
WebLogic Server installs the domain directory by default within the BEA_HOME /user_projects/domains directory. Figure 3-1 is an overview of the domain directory tree hierarchy within the domains directory. The domain-name , deployment-name , and server-name directory names are not literal, but are replaced in any actual case with whatever specific names are appropriate; the other directory names are literal. This overview shows only directories, not files within the directories. In any actual particular domain directory tree, this whole hierarchy might not be present.
Figure 3-1 Domain Directory Structure
This section describes the contents of the domain directory and its subfolders. Note that the domain-name, server-name, and deployment-name directory names are not literal, but are replaced with whatever specific names is appropriate; other directory names are literal.
servers/server-name
This directory is the server directory for the WebLogic Server instance with the same name as the directory.
domain-name
The name of this directory is the name of the domain.
servers/server-name/data
This directory holds files that maintain persistent per-server state used to run the WebLogic Server instance, other than security state, as opposed to temporary, cached or historical information. Files in this directory are important data that must be retained as the WebLogic Server instance is brought up, is brought down, crashes, restarts, or is upgraded to a new version.
config/deployments/deployment-name-1
This directory contains one application, or deployable module. It contains a subhierarchy that can contain an archive file (EAR or WAR), a deployment plan file, external descriptors, and so on. The directory takes its name from the module's name.
Domain Directory Contents
By default, Oracle WebLogic Server creates domain directories under Oracle Middleware ORACLE_HOME /user_projects/domains directory.
Individual applications in a domain might create additional files and directories in the domain directory.
If you have not yet created a domain, you can see an example of an existing domain directory by looking in ORACLE_HOME /user_projects/domains/wl_server where ORACLE_HOME is the directory you specified as the Oracle Home when you installed Oracle WebLogic Server.
The following section describes the contents of the domain directory and its subfolders. Here domain-name , deployment-name , and server-name represent names that you define when you create a domain.
domain-name
The name of this directory is the name of the domain. The name must conform to the guidance in Domain and Server Name Restrictions.
autodeploy
This directory provides a quick way to deploy applications in a development server. When the Oracle 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:
A WAR, EJB JAR, RAR, or CAR archived module
An exploded archive directory for either an application or a 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 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, and such. See Administering Server Startup and Shutdown for Oracle WebLogic Server.
config
This directory contains the current configuration and deployment state of the domain. The central domain configuration file, config.xml , resides in this directory.
config/configCache
Contains data that is used to optimize performance when validating changes in the domain's configuration documents. This data is internal to Oracle WebLogic Server and does not need to be backed up.
config/diagnostics
This directory contains system modules for instrumentation in the WebLogic Diagnostic Framework. See Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
config/jdbc
This directory contains system modules for JDBC: global JDBC modules that can be configured directly from JMX (as opposed to JSR-88). See Database Connectivity for Oracle WebLogic Server.
config/jms
This directory contains system modules for JMS: global JMS modules that can be configured directly from JMX (as opposed to JSR-88). See Messaging for Oracle WebLogic Server.
config/lib
This directory is not used in the current release of Oracle WebLogic Server.
config/nodemanager
This directory holds information for connection to the Node Manager. See Node Manager Configuration and Log Files in Administering Node Manager for Oracle WebLogic Server .
config/security
This directory contains system modules for the security framework. It contains one security provider configuration extension for each kind of security provider in the current realm of the domain. See Understanding Security for Oracle WebLogic Server .
configArchive
The maximum number of versioned JAR files to be kept is specified by the archiveConfigurationCount attribute of DomainMBean . Once this maximum number is reached, the oldest conversion archive is deleted before a new one is created.
console-ext
This directory contains extensions to the WebLogic Server 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 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 used for WebLogic domain provisioning. You should not modify any files in this directory.
JAR files you put in this directory are made available (within a separate system level classloader) to all Java EE applications running on WebLogic Server instances in the domain. See Adding JARs to the Domain /lib Directory in Developing Applications for Oracle WebLogic Server .
pending
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. See Managing Configuration Changes.
security
This directory holds those security-related files that are the same for every Oracle WebLogic Server instance in the domain:
This directory also holds security-related files that are only needed by the domain's Administration Server:
config/ jdbc
This directory contains system modules for JDBC: global JDBC modules that can be configured directly from JMX (as opposed to JSR-88). For more information, see Database Connectivity (JDBC).
Изменение файла Config.xml
Откройте файл Config.xml с помощью текстового редактора, такого как "Блокнот".
Найдите строки, содержащие элементы, которые нужно изменить.
Измените запись для элемента, используя нужные значения параметров автоматической установки. Убедитесь, что вы удалите разделители комментариев, " ". Например, используйте следующий синтаксис:
The Config.xml file is an optional User State Migration Tool (USMT) 10.0 file that you can create using the /genconfig option with the ScanState.exe tool. If you want to include all of the default components, and do not want to change the default store-creation or profile-migration behavior, you do not need to create a Config.xml file.
However, if you are satisfied with the default migration behavior defined in the MigApp.xml, MigUser.xml and MigDocs.xml files, but you want to exclude certain components, you can create and modify a Config.xml file and leave the other .xml files unchanged. For example, you must create and modify the Config.xml file if you want to exclude any of the operating-system settings that are migrated. It is necessary to create and modify this file if you want to change any of the default store-creation or profile-migration behavior.
The Config.xml file has a different format than the other migration .xml files, because it does not contain any migration rules. It contains only a list of the operating-system components, applications, user documents that can be migrated, as well as user-profile policy and error-control policy. For this reason, excluding components using the Config.xml file is easier than modifying the migration .xml files, because you do not need to be familiar with the migration rules and syntax. However, you cannot use wildcard characters in this file.
For more information about using the Config.xml file with other migration files, such as the MigDocs.xml and MigApps.xml files, see Understanding Migration XML Files.
Note To exclude a component from the Config.xml file, set the migrate value to "no". Deleting the XML tag for the component from the Config.xml file will not exclude the component from your migration.
Edit In Place¶
Editing the configuration in-place is also possible in a variety of ways. The general procedure is:
Run rm /tmp/config.cache to clear the configuration cache
Reboot, or use the GUI to save/reload whichever part of the firewall utilizes the edited settings
From the console or ssh, administrators familiar with the vi editor can use the viconfig command to edit the running configuration, and this command automatically clears the cache file after saving and exiting.
Other editors are available on the firewall, such as ee or in the GUI under Diagnostics > Edit File ( Editing Files on the Firewall ). Clear the cache file manually after using one of these other methods, either using the shell or Diagnostics > Command Prompt ( Command Prompt ).
Хотя Центр развертывания Office является основным средством настраиваемой установки, администраторы могут использовать файл Config.xml, чтобы задать для установки дополнительные инструкции, недоступные в Центре развертывания Office. Следующие настройки выполнимы только с помощью файла Config.xml:
задание пути для точки сетевой установки;
выбор устанавливаемых продуктов;
настройка ведения журнала и местоположения файла настроек установки и обновлений ПО;
задание параметров установки, таких как имя пользователя;
копирование локального источника установки на компьютер пользователя без установки Office;
добавление и удаления языков из установки.
Для настройки автоматической установки Lync 2013 рекомендуется использовать файл Config.xml.
По умолчанию файл Config.xml, хранящийся в основной папке продукта (например, \ Product. WW) направляет настройку для установки этого продукта. Например, файл Config.xml в следующей папке устанавливает Lync 2013:
- \\\общий доступ к серверу \ Lync15 \ Lync. WW \Config.xml
Элементы Config.xml, наиболее часто используемые при установке Lync 2013, перечислены в приведенной ниже таблице.
user_staged_config
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.
All instances of WebLogic Server use a server root directory to store runtime data and to provide the context for any relative pathnames in the server's configuration. You can specify the path and name of the server root directory for each server instance. You can specify a common server root directory for multiple server instances hosted on a single computer or you can specify a different server root directory for each server. A domain may have one or more server root directories.
servers/server-name/security
This directory holds security-related files that can be or must be different for each WebLogic Server instance. The file boot.properties is an example of a file that resides here because it can differ from one server to the next. This directory also maintains files related to SSL keys.
Server Root Directory for a Managed Server Not Started with Node Manager
If you do not use the Node Manager to start a Managed Server (and therefore use the java weblogic.Server command or a script that calls that command), WebLogic Server does the following to determine the root directory:
-
If the server's startup command includes the -Dweblogic.RootDirectory= path option, then the value of path is the server's root directory. If -Dweblogic.RootDirectory= path is not specified, then the working (current) directory is the root directory. For example, if you run the weblogic.Server command from c:\config\MyManagedServer , then c:\config\MyManagedServer is the root directory.
To make it easier to maintain your domain configurations and applications across upgrades of WebLogic Server software, it is recommended that the server root directory not be the same as the installation directory for the WebLogic Server software.
The domain configuration files are XML documents that Oracle WebLogic Server uses to persist the configuration of a domain.
This chapter includes the following sections:
configArchive
The maximum number of versioned JAR files to be kept is specified by the archiveConfigurationCount attribute of DomainMBean . Once this maximum number is reached, the oldest conversion archive is deleted before a new one is created.
Overview of Domain Configuration Files
Each domain describes its configuration in an XML document that is located in the configuration directory of the domain. At run time, each Oracle WebLogic Server instance in a given domain creates an in-memory representation of the configuration described in this document.
The domain directory must have both Write and Read privileges, for the domain to function properly, even if no changes are made to the configuration after it is created. These privileges are required because WebLogic Server performs its own internal deployments, and configuration files may be rewritten when the server is restarted.
Do not add non-configuration files in the config directory or subdirectories. Non-configuration files include log (.log) and lock (.lck) files. Administration Server replicates the config directory in all Managed Server instances. Storing non-configuration files in the config directory can cause performance issues in the domain.
The central configuration file for a domain is DOMAIN_NAME /config/config.xml . This file specifies the name of the domain and the configuration of each server instance, cluster, resource, and service in the domain. The file includes references to additional XML files that are stored in subdirectories of the DOMAIN_NAME /config directory. These included files are used to describe major subsystems of Oracle WebLogic Server.
As a performance optimization, Oracle WebLogic Server does not store most of its default values in the domain's configuration files. Sometimes, this optimization prevents XML elements from being written to the configuration files. For example, if you never modify the default logging severity level for a domain while the domain is active, the config.xml file does not contain an XML element for the domain's logging configuration.
As an additional performance optimization, each Managed Server maintains a copy of the domain's configuration files. This copy is read-only and can be updated only as part of a change management process (see Managing Configuration Changes).
Editing Configuration Documents
In most circumstances, you should not use a text editor or other non-Oracle tools to modify a domain's configuration document. Instead, use the WebLogic Server Administration Console, Fusion Middleware Control (FMWC), WebLogic Scripting Tool (WLST), or one of the other tools described in System Administration in Understanding Oracle WebLogic Server .
However, because the Oracle WebLogic Server configuration document is an XML file that conforms to a schema, it is possible to modify them using XSLT or an XML parser application such as Apache Xerces or JDOM. Be sure to test any scripts that you create thoroughly and always make a backup copy of each configuration file before you make any changes to it.
The schemas that define a domain's configuration document are in the following locations:
In JAR files under WL_HOME /server/lib/schema , where WL_HOME is the directory in which you install Oracle WebLogic Server. Within this directory:
The domain.xsd document is represented in the weblogic-domain-binding.jar under the pathname META-INF/schemas/schema-0.xsd .
The security.xsd document is represented in the weblogic-domain-binding.jar under the pathname META-INF/schemas/schema-1.xsd .
The weblogic-diagnostics.xsd document is represented in the diagnostics-binding.jar under the pathname META-INF/schemas/schema-0.xsd .
Do not edit configuration files for a domain that is currently running. Because Oracle WebLogic Server rewrites the files periodically, your changes will be lost. Depending on your platform, you also could cause Oracle WebLogic Server failures.
Security Credentials in Configuration Files
Security credentials for domain security and the embedded LDAP server are stored in the config.xml file in encrypted form. If you create your config.xml file with a text editor or other non-Oracle tool, you need to locate these credentials, encrypt them, and copy the encrypted credential into your config.xml file.
For information about Oracle WebLogic Server's encryption utility, see encrypt in the Command Reference for Oracle WebLogic Server . After you encrypt the credentials, include the encrypted values in your config.xml file in elements as shown in Example 3-1:
Example 3-1 Configuring Encrypted Credentials
Configuration File Archiving
You can configure Oracle WebLogic Server to make backup copies of the configuration files. This facilitates recovery in cases where configuration changes need to be reversed or the unlikely case that configuration files become corrupted. When the Administration Server starts up, it saves a JAR file named config-booted.jar that contains the configuration files. When you make changes to the configuration files, the old files are saved in the configArchive directory under the domain directory, in a JAR file with a sequentially-numbered name like config-1.jar .
For information about archiving configuration files, see Archive configuration files in Oracle WebLogic Server Administration Console Online Help . If you want to use WLST to configure Oracle WebLogic Server to make backup copies, set the ConfigBackupEnabled attribute in DomainMBean to true and the ArchiveConfigurationCount attribute to the number of configuration archive files that you want to retain, shown in Example 3-2.
Example 3-2 Configuring Archive Files
servers/server-name/tmp
This directory holds temporary directories and files that are created while a server instance is running. For example, a JMS paging directory is automatically created here unless another location is specified. Files in this directory must be left alone while the server is running, but may be freely deleted when the server instance is shut down.
This directory stores temporary files used in the change management process. You should not modify any files in this directory.
In this topic
In USMT there are new migration policies that can be configured in the Config.xml file. For example, you can configure additional , , and options. The following elements and parameters are for use in the Config.xml file only.
This section describes how a domain is represented in the file system. It includes the following sections:
WebLogic Server management and configuration services are accessed with the Java Management Extensions (JMX) API. The configuration of a domain is stored in XML files in the configuration directories under the domain directory. The files in these configuration directories act as a persistent store for the managed objects that WebLogic Server creates and modifies during its executing using the JMX API. The purpose of the configuration files is to store changes to managed configuration objects so that they are available when WebLogic Server is restarted.
The central configuration file for the domain is DOMAIN_NAME / config/config.xml file. It specifies the name of the domain and the configuration parameter settings for each server instance, cluster, resource, and service in the domain. The configuration for some major subsystems of the domain is stored in subdirectories of the DOMAIN_NAME /config directory in separate configuration files that are incorporated by reference into the central config.xml file.
The domain directory also contains default script files, such as startWebLogic.cmd and startWebLogic.sh , that you can use to start the domain's Administration Server and Managed Servers. For details about these configuration files and script files, see Domain Directory Contents.
The central configuration file for the domain is the /domains/ DOMAIN_NAME /config/config.xml file. It specifies the name of the domain and the configuration parameter settings for each server instance, cluster, resource, and service in the domain.
For a reference guide to the domain configuration XML Schema, see the WebLogic Server Domain Configuration Schema Reference.
autodeploy
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 J2EE applications, such as:
-
An EAR file A WAR, EJB JAR, RAR, or CAR archived module An exploded archive directory for either an application or a 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. For more information, see Manag ing Server Startup and Shutdown.
Server Root Directory for an Administration Server
An Administration Server uses its server root directory as a repository for the domain's configuration data (such as config.xml ) and security resources (such as the default, embedded LDAP server).
To determine the root directory for an Administration Server, WebLogic Server does the following:
-
If the server's startup command includes the -Dweblogic.RootDirectory= path option, then the value of path is the server root directory. If -Dweblogic.RootDirectory= path is not specified, then the working directory is the server root directory. However, if you are upgrading a domain created under WebLogic Server 6.x, then the server root directory is the parent of the working directory.
If WebLogic Server cannot find a config.xml file, then it offers to create one. You can use this method to create a new domain. For more information, see Using the weblogic.Server Command Line to Create a Domain in the WebLogic Server Command Reference.
servers/server-name/logs
This directory holds logs and diagnostic information. This information is historical in nature. It is not crucial to the operation of the server, and can be deleted (while the WebLogic Server instance is down, at least) without affecting proper operation. However, the information can be quite useful for debugging or auditing purposes and should not be deleted without good reason.
config/deployments/ library_modules
This directory holds library modules; that is, anything found in this directory will automatically be registered as a library module.
pending
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. For more information, see Managing Configuration Changes.
Specifying a Server Root Directory
You can specify the path for the server root directory by one of the following means:
-
Use the -Dweblogic.RootDirectory= path option when starting a WebLogic Server instance from command line. For example the following command:
starts a WebLogic Server instance and uses c:\MyServerRootDirectory as the server root directory.
If you do not use one of the above means to specify a server root directory, the path and name of the server root directory depend on whether a server instance is a Managed Server or the Administration Server and whether or not you use Node Manager to start the server instance. These variations are discussed in the next sections.
servers/server-name/cache/EJBCompilerCache
This directory is a cache for compiled EJBs.
servers
This directory contains one subdirectory for each WebLogic Server instance in the domain. For more information, see A Server's Root Directory.
Secur ity Credentials in Configuration Files
Security credentials for domain security and the embedded LDAP server are stored in the config.xml file in encrypted form. If you create your config.xml file by hand, you need to locate these credentials, encrypt them, and copy the encrypted credential into your config.xml file.
For information about WebLogic Server's encryption utility, see encrypt in the WebLogic Server Command Reference. Once you have encrypted the credentials, include the encrypted values in your config.xml file in elements as in Listing 3-1:
Listing 3-1 Configuring Encrypted Credentials
servers/server-name/data/ldap
This directory holds the embedded LDAP database. The runtime security state for the WebLogic Server instance is persisted in this directory.
servers/server-name/data/store
This directory holds WebLogic persistent stores. For each persistent store, there is a subdirectory that holds the files that represent the persistent store. The name of the subdirectory is the name of the persistent store. By convention there is one store named default .
Manually editing the configuration¶
A handful of configuration options are only available by manually editing the configuration file, though this isn’t required in the vast majority of deployments. Some of these options are covered in other parts of this documentation where they are relevant. Additionally, for advanced administrators in rare cases large-scale or tricky changes may be easier to make by directly editing the configuration file.
Even for seasoned administrators it is easy to incorrectly edit the configuration file. Always keep backups and be aware that breaking the configuration will result in unintended consequences.
security
This directory holds those security-related files that are the same for every WebLogic Server instance in the domain:
This directory also holds security-related file that are only needed by the domain's Administration Server:
-
DefaultAuthorizerInit.ldift DefaultAuthenticatorInit.ldift DefaultRoleMapperInit.ldift
init-info
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.
servers/server-name/logs/jmsServers
This directory contains one subdirectory for each JMS server in the WebLogic Server instance. Each such subdirectory contains the logs for that JMS server. The name of the subdirectory is the name of the JMS server.
Edit a Backup¶
Navigate to Diagnostics > Backup/Restore in the GUI
Download and save backup file
Open the file in a text editor that properly understands UNIX line endings, and preferably an editor that has special handling for XML such as syntax highlighting. Do not use notepad.exe on Windows.
Make changes to the configuration and save
Navigate to Diagnostics > Backup/Restore in the GUI
Restore the edited configuration
The firewall will automatically reboot as a part of the restoration process, and the new settings will be active afterward.
Читайте также: