2017-07-22 21:47:43,769 INFO [WizardController] com.oracle.cie.domain.template.catalog.impl.ComponentsXMLConverter - C:\Oracle\Middleware\wlserver_10.3\common\lib\components.xml does not contain component elements and will be skipped
2017-07-22 21:47:43,770 INFO [WizardController] com.oracle.cie.wizard.domain.gui.tasks.MultipleTemplateSelectionGUITask - Selected required template: Basic WebLogic Server Domain:10.3.6.0 [C:\Oracle\Middleware\wlserver_10.3\common\templates\domains\wls.jar]
2017-07-22 21:55:50,948 INFO [WizardController] com.oracle.cie.domain.WLSTemplateBuilder - No config-groups.xml found in template
2017-07-22 21:55:50,948 INFO [WizardController] com.oracle.cie.domain.WLSTemplateBuilder - No template-database.xml found in template
2017-07-22 21:55:51,624 INFO [WizardController] com.oracle.cie.domain.AbstractTemplate - Adding top-level component reference: WebLogic Server version 10.3.6.0
2017-07-22 21:55:51,626 INFO [WizardController] com.oracle.cie.domain.AbstractTemplate - Setting symbol for component WebLogic Server version 10.3.6.0 to WebLogic_Server_10.3.6.0_wlserver_10.3_ORACLE_HOME
2017-07-22 21:58:40,502 WARN [WizardController] com.oracle.cie.common.util.JdkVersion - JDK version is null.
2017-07-22 22:01:36,221 INFO [WizardController] com.oracle.cie.domain.DomainChecker - ListenPort internal Validation result= [null]
2017-07-22 22:01:36,222 INFO [WizardController] com.oracle.cie.domain.DomainChecker - ListenPort external Validation result= [null]
2017-07-22 22:01:40,416 INFO [Thread-4] com.oracle.cie.domain.StartMenu - Creating start menu program=C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd link=Start Admin Server for Weblogic Server Domain
2017-07-22 22:01:40,586 INFO [Thread-4] com.oracle.cie.domain.StartMenu - Creating start menu program=C:\Oracle\Middleware\user_projects\domains\base_domain\bin\stopWebLogic.cmd link=Stop Admin Server
2017-07-22 22:01:40,589 INFO [Thread-4] com.oracle.cie.domain.StartMenu - Creating start menu program=C:\Windows\system32\rundll32.exe link=Admin Server Console
2017-07-22 22:01:40,621 INFO [Thread-4] com.oracle.cie.domain.DomainRegistryWrapper - need to initialize domainRegistrydocument object
2017-07-22 22:01:40,647 INFO [Thread-4] com.oracle.cie.domain.DomainGenerator - Domain Generation Successful!
<?xml version="1.0" encoding="UTF-8"?>
<domain-registry xmlns="http://xmlns.oracle.com/weblogic/domain-registry">
<domain location="C:\Oracle\Middleware\user_projects\domains\base_domain"/>
</domain-registry>
This autodeploy directory provides a quick way to deploy applications
to a development server. When the WebLogic Server instance is running
in development mode, applications and modules in this directory are
automatically deployed.
You can place J2EE applications such as the following in this directory:
* EAR files
* WAR, EJB JAR, or RAR archive files
* Exploded archive directories for applications or modules
The autodeploy directory is automatically created when you install
the WebLogic Server sample domains or when you use the Configuration
Wizard to create domains.
To automatically deploy an application:
1. Start the WebLogic Server domain in development mode.
2. Place the application's exploded directory structure
or archive file in this autodeploy directory.
STARTING WEBLOGIC SERVER IN DEVELOPMENT MODE
WebLogic Server domains start up in development mode by
default. To change startup mode for a domain, follow
the below instructions.
The startup mode applies to all WebLogic Server instances in a domain.
You can set the domain startup mode in any of the following ways:
* With the startWebLogic start scripts in the bin directory.
startWebLogic.cmd (for Windows) and startWebLogic.sh (for Unix)
can be modified with any text editor.
By default, the start scripts start WebLogic Server in development
mode so you do not need to modify the default scripts in order to
auto-deploy applications. If you want to start WebLogic Server in
production mode, use the 'production' argument with the start command
or modify the startup scripts.
* Start the server in development mode from the command line with the
-Dweblogic.ProductionModeEnabled=false setting. If you want to
start the server in production mode from the command line, use
the -Dweblogic.ProductionModeEnabled=true setting.
* Set the domain startup mode in the Administration Console by
selecting or deselecting the Production Mode box in the domain's
Configuration->General page. See the Administration
Console online help for more information about setting this
attribute.
This is the domain library directory and is usually located at $DOMAIN_DIR/lib.
The jars located in this directory will be picked up and added dynamically to the end of the server classpath at server startup. The jars will be ordered lexically in the classpath. The domain library directory is one mechanism that can be used for adding application libraries to the server classpath.
It is possible to override the $DOMAIN_DIR/lib directory using the -Dweblogic.ext.dirs system property during startup. This property specifies a list of directories to pick up jars from and dynamically append to the end of the server classpath using java.io.File.pathSeparator as the delimiter between path entries.
They are config.lok, EmbeddedLDAP.lok and XXXserver.lok files which are used by the admin server and managed server. Another lock file named edit.lok is used for the admin server only.
config.lok: The config.lok file is just used for getting a file lock on the config.xml file, in order to ensure that config file updates run serially. It will not cause any problems if it exists in the directory.
edit.lok: The edit lock is used to ensure that only one user at a time is editing the configuration. The edit lock is only used on the Admin server.
EmbeddedLDAP.lok: This file locks access to the embedded LDAP server, in order to ensure that only a single process has access to this directory server. if two processes write to the same directory server, the directory server will have a problem.
XXXServer.lok: The [server name].lok indicates that the server with name [server name] is running. This is used to prevent a server from being booted twice. If you are sure that this server process is shut down, you can delete it.
欢迎光临 JEE Study|JAVA EE|企业级开发学习网 (http://jeestudy.com/) | Powered by Discuz! X3.2 |