WebLogic (02)

 

1.  
   1. configure machine
   2. The administration server uses the machine definition with the node manager application to start remote weblogic server instances
   3. is a computer that hosts weblogic server(s)
   4. 
      
2. configure managed server
   1. Creating a boot identity file
      1. Create a file called boot.properties located in the <DOMAIN_HOME>\servers\srvername\security directory contaning two lines:
         1. - username=username
         2. - password=password
      2. The username must be belongs to a role that has permission to start a server. Save the text file as boot.properties
      3. Boot.properties is created automatically for the Admin Server in dev mode, and in production mode, we have to create the file and place it in the admin sever's \sercurity subdirectory manully.
      4. The first time you start the server, the server reads the Boot identity file and overwrites it with an encrypted version of the username and password
      5. Thereafter, the sever will remember your identity for the subsequent startup cycles.
      6. 
         
   2. Managed server(s) can be configured using:
      1. Domain configuration wizard
      2. 
         
      3. Administration consosle
      4. Command Line (WLST)
   3. Managed server
      1. using startManager to start managed server
         1. setDomainEnv.cmd
         2. start startManagedWeblogicserver.cmd <server name>
         3. 
            
   4. Managed Machine
      1. target a server to a machine
      2. sever/bin/startnodemanager.cmd 127.0.0.0 5555
      3. but, we have a new file 'notemanager.host for the master machine in the remote managed server
      4. 
         
3. publish application
4. learn to view the log file
5. use sample domain: wl_server