Configure the managed Server

Managed server is usually the server where applications are deployed. Therefore, it is best to configure the managed server on weblgoic instead of directly deploying the application to the admin server.

1. The managed server is created when the domain is created, and the machine and nodemanager

2. To run the managed server, you must set its startup environment and startup items. Because the application on WebLogic is loaded to the JVM for running. The managed Server Java environment must be set.

Java main directory: D: \ Bea \ jdk1.6

Java vendor: Sun

Bea main directory: D: \ Bea

Root directory: D: \ Bea \ use_projects \ Domains \ my_domain

Class path: D: \ Bea \ wlserver_1.0 \ Server \ Lib \ weblogic. jar; D: \ Bea \ wlserver_1.0 \ Server \ Lib \ weblogic_sp.jar

Security Policy: D: \ Bea \ wlserver_1.0 \ Server \ Lib \ weblogic. Policy

Username: Weblogic

Password :........

　　　　

The configuration in config. XML is as follows:

<Server>

<Name> server0 </Name>

<SSL>

<Enabled> false </enabled>

</SSL>

<Machine> machine0 </machine>

<Listen-port> 8001 </listen-port>

<Cluster xsi: Nil = "true"> </cluster>

<Listen-address> </listen-address>

<Server-Start>

<Java-vendor> Bea </Java-vendor>

<Java-Home> D: \ Bea \ jdk150_06 </Java-Home>

<Class-path> D: \ Bea \ wlserver_10.0 \ Server \ Lib \ weblogic. jar; D: \ Bea \ wlserver_10.0 \ Server \ Lib \ weblogic_sp.jar </class-path>

<Bea-Home> D: \ Bea </Bea-Home>

<Root-directory> D: \ Bea \ user_projects \ Domains \ ngi_domain </root-directory>

<Security-policy-File> D: \ Bea \ wlserver_10.0 \ Server \ Lib \ weblogic. Policy </security-policy-File>

<Username> iboss </username>

<Password-encrypted> {3DES} jqzlsjckdqwvaidoqa3sbw ==</password-encrypted>

</Server-Start>

</Server>

3. Save the preceding settings to activate WebLogic updates.

4. Follow these steps to start the managed Server:

(1) start it on the console

1. Open the Node Manager

2. Open the contral page of the managed server and click Start to start.

3. During the startup process, if the error "cannot find the corresponding nodemanager and Machine" is reported, it may be because nodemanager is not started or port 5556 is occupied.

Method:

1. Use netstat-ano 5556 to locate the process PID and kill the process.

2. Start the process whose username is user by running java.exe. * 32 on the task manager.

(2) start through the command line

1. Go to the bin directory under the my_domain directory and run the startmanagedweblogic. CMD command to start the managed server.

Note: method 2 is preferred for the above two methods. If you start from the console, it is likely that the first pegment out of memory overflow will occur, and it is very difficult to modify the JVM configuration in WebLogic !!

　　

========================================================== ========================================================

The following is an example of starting the managed server: See the document of configuring the managed server .doc in ebook/WebLogic/weblogic.

 

　　　　

　　

　　

Configure the managed Server