1. Creating Distributed Setup WEBLOGIC SERVER

2. Create a Distributed Setup Using Node Manager Basic idea: When the servers are in production, and all of them are running on the same physical box, for some reason if the system crashes, the admin server along with all the managed servers will crash and the whole production environment is haulted. To avoid this situation, if there is a distributed setup and the managed servers reside on different machines, even if one system crashes, other managed servers are still functioning. So the application is still available.

3. Requirements : 1. Two Physical machine on LAN. (Local, Remote) 2. Weblogic (required version) should be installed on both the Machines Configuration on Local machine : - From the admin console create a domain on Local machine and start the admin server. - Create two managed servers MSLocal and MSRemote - Create a cluster Cluster and assign MSLocal and MSRemote to it. - Create a machine MachineLocal and keep MSLocal in that (MSLocal will run on Local). Give the IP for the MSLocal and Machine Local as that of the Local machine - Create a machine MachineRemote and keep MSRemote in that (MSRemote will run on Remote). Give the IP address for the MSRemote and MachineRemote as that of the Remote machine

4. Configurations on Remote machine : - On the remote machine and do the following changes to nodemanager.properties under D:\BEA923\weblogic92\common\nodemanager a. ListenAddress = (IP address of the remote machine) b. SecureListener = false c. AuthenticationEnabled = false d. CrashRecoveryEnabled = true

5. - Start node manger - Open the Admin console by giving http:// : /console on which the admin server is running (Local Machine). - Open command prompt and set the environment by running the script setDomainEnv.cmd from the path D:\BEA923\user_projects\domains\base_domain\bin - Then start WLST using java weblogic.WLST command - It will start in offline mode, to connect to the admin server, give the command connect(). - Give the username password and the admin server url.

6. - Now to enroll the machine and start the managed server on remote machine, type the below command: nmEnroll ('D:/BEA923/weblogic92/co mmon/nodemanager') (nmEnroll is the node manager enroll command and the path is the node manager home where the remote managed server will be created.

7. - Now go to the admin console from the remote machine itself. Check the status of the node manager of the MachineRemote. It should be reachable. - Start the MSRemote from the console, you will see that all the files of the managed server (bin, config, security, servers, tmp) will created in the nodemanager home. - Config folder mainly has the config.xml of the domain, which the local managed server will not have. This is because this managed server should start the next time even if the admin server is down. - Now if you shutdown this managed server, rename the config.xml file and restart the server while the admin server is up, a new config.xml will be created in the directory.