BEA WebLogic series-default domain startup Behavior

 

If you have set the required environment in the environment, the WebLogic Server performs the following operations when you enter the command Java weblogic. server without any options:

1. Find the file named config. xml in the domain_name/config directory.
   
2. If the domain_name/config directory contains config. XML, WebLogic Server performs the following operations:
   1. If only one server instance is defined in config/config. XML, Weblogic server starts the server instance.

      For example, if Java weblogic. server is issued from wl_home/samples/domains/medrec, the Weblogic server starts the medrec server.
      

   2. If multiple server instances are defined in config/config. xml:
      
   • If you have defined a Management Server, use its name to search for the server.
   • If no management server is defined, find the server configuration named myserver. If this server configuration is found, the myserver instance is started.
     
   • If the server named myserver is not found, WebLogic Server exits the weblogic. server process and generates an error message.
     
3. If the config. xml file does not exist in the current directory, WebLogic Server prompts you to create one. In response to Y, WebLogic Server performs the following operations:
   1. Create a server configuration named myserver and save the configuration in the file named config/config. xml.

      All specified options are saved to the config. xml file. For example, if-dweblogic. listenport = 8001 is specified, WebLogic Server saves 8001 In the config. xml file. For any unspecified options, use the default value for the server instance.
      

      You can configure WebLogic Server to create a backup copy of the configuration file. This helps you recover when you need to restore configuration changes or when the configuration file is corrupted, but the latter rarely happens. For more information, see configure file archiving in "learn about Domain Configuration.
      

   2. Use the provided username and password to create users with administrative permissions. It stores user definitions and other security-related basic data in the domain_name/security file named defaauthauthenticatorinit. ldift, defaultrolemapperinit. ldift, and serializedsystemini. dat.

      WebLogic Server encrypts the user name and password and stores them in the SERVER_NAME/security/boot. properties file. Therefore, you can bypass the logon prompt during subsequent server instantiation. For more information, see the boot ID file in manage server startup and shutdown.
      

   3. Create two scripts that can be used to start subsequent server instances, bin/startweblogic. CMD and bin/startweblogic. Sh. You can use a text editor to modify the startup options (for example, if the server is started in production or development mode ). The startweblogic script contains comments describing each option.

      Note that the server in the new domain is started as the management server. There are no other servers in this domain, and no deployment or third-party solutions are included. You can add them, just as you can add them to any WebLogic domain.