Administration and Deployment Lab 3 – Setting up BEA WebLogic Remote Start Properties

Lab 3-1

Lab 3 — Setting up BEA WebLogic to start and stop remote managed servers from the Administrative Console App

Estimated Time: 25 minutes

Goals Configure the Remote Start properties in the Administrative Console to enable starting and stopping remote and local managed server instances from within the Administrative Console, instead of using scripts or menu shortcuts.

Tasks 1. Edit the startManagedWebLogic.cmd script to output environment settings to temporary files and not actually start the server instance.

2. Execute the startManagedWebLogic.cmd to generate the temporary files.

3. Copy the contents of the temporary files and paste them into the Remote Start properties page in the Administrative Console for each managed server instance.

4. Start the server instances from the Administrative Console and test connectivity to Webtop through the proxyServer.

5. Restore the startManagedWebLogic.cmd file to it’s previous state.

Background To complete this lab, you must have successfully completed Labs 1 and 2.

Once Webtop has been installed, and the startup scripts have been created and configured to start and stop managed server instances, this lab will show you how to configure the Remote Start properties in the Administrative Console so that you can start and stop managed server instances from the console, instead of using scripts or menu shortcuts.

Steps 1. Edit the startManagedWebLogic.cmd script to output environment settings to

temporary files and not actually start the server instance.

Administration and Deployment Lab 3 – Setting up BEA WebLogic Remote Start Properties

Lab 3-2

NOTE: You must have already installed Webtop or another Documentum product and configured each remote server machine using the Documentum installer before performing the steps in this lab. Documentum installers modify the contents of the startManagedWebLogic.cmd script with each installation. These settings are what you will paste into the Remote Start properties in the Administrative Console so that it will support Documentum software. If you plan to install more than one Documentum Mid-Tier application, you should complete all installs and get everything working with startup scripts, and only then, follow the steps in this lab. Also, keep in mind that if you cannot run the application by starting the server instances with startManagedWebLogic.cmd file, then moving those settings to the Remote Start properties in the Administrative Console will also fail. Remote Start settings will make administration much easier, but they must be exactly the same as what is in the startManagedWebLogic.cmd file following the installation of the Documentum web application.

1.1. Before getting started, make sure the Node Manager, adminServer, proxyServer, managedServer1 and managedServer2 are stopped. There will be an open DOS window for each one since they were launched through batch scripts. Just close each DOS window in any order.

1.2. Make a backup copy of the startManagedWebLogic.cmd file: C:\bea\user_projects\domains\labDomain\startManagedWebLogic.cmd

1.3. Open startManagedWebLogic.cmd in notepad by clicking Start > Run and entering the following command: notepad C:\bea\user_projects\domains\labDomain\startManagedWebLogic.cmd

1.4. Scroll to the bottom of the script file and place a REM at the beginning of the java command that starts the server instance: REM "%JAVA_HOME%\bin\java" %JAVA_VM% …

NOTE: You will be executing this script in order to capture the environment settings to file, and we don’t actually want to run the command itself.

1.5. Add the following two lines just underneath the command you commented out in the previous step: ECHO %MEM_ARGS% %JAVA_OPTIONS% > c:\temp\arguments.txt ECHO %CLASSPATH% > c:\temp\classpath.txt

Administration and Deployment Lab 3 – Setting up BEA WebLogic Remote Start Properties

Lab 3-3

1.6. When you are finished editing the file, the last lines in startManagedWebLogic.cmd should look like this (some of the java command is omitted for brevity): … REM "%JAVA_HOME%\bin\java" %JAVA_VM% %MEM_ARGS% … ECHO %MEM_ARGS% %JAVA_OPTIONS% > c:\temp\arguments.txt ECHO %CLASSPATH% > c:\temp\classpath.txt :finish ENDLOCAL

1.7. Save the file but leave it opened in notepad in case you need to edit it for syntax errors after the next step.

2. Execute the startManagedWebLogic.cmd to generate the temporary files.

2.1. Execute the following Start menu shortcut: click Start > Programs > BEA WebLogic Platform 8.1 > User Projects > labDomain > Start Managed Server 1. This will open a DOS window.

2.2. Verify there were no errors running the script. If you see errors, edit the startManagedWebLogic.cmd file and fix any syntax errors you may have introduced.

2.3. Close the DOS window.

3. Copy the contents of the temporary files and paste them into the Remote Start properties page in the Administrative Console for each managed server instance.

3.1. Open the temporary files you created when running the script file. Click Start > Run, and execute the following command: notepad c:\temp\arguments.txt

3.2. Click Start > Run again, and execute the following command: notepad c:\temp\classpath.txt

3.3. Start the WebLogic Node Manager from the Start menu on Windows: click Start > Programs > BEA WebLogic Platform 8.1 > Other Development Tools > Node Manager.

3.4. Start the adminServer from the Start menu on Windows: click Start > Programs > BEA WebLogic Platform 8.1 > User Projects > labDomain > Start Admin Server:

3.5. When asked to enter a username and password in the command window, enter the administrative username and password you chose in Lab 2 which should be ‘weblogic’

Administration and Deployment Lab 3 – Setting up BEA WebLogic Remote Start Properties

Lab 3-4

3.6. Open a browser window and navigate to http//localhost:7001/console and enter the administrative username and password.

3.7. In the Administrative Console window’s left pane (tree control), select the Servers > managedServer1 node, and in the right hand pane, click the Configuration tab (top level), and then click the Remote Start sub tab:

3.8. You are only going to edit the contents of the Class Path and Arguments properties:

3.9. Paste the contents of c:\temp\classpath.txt into the Class Path property:

3.10. Paste the contents of c:\temp\arguments.txt into the Arguments property:

3.11. Click the Apply button in the lower right corner of the page.

3.12. Select Servers > managedServer2 in the left pane of the Administrative Console and repeat the process from step 3.7.

4. Start the managed server instances from the Administrative Console and test connectivity to Webtop through the proxyServer.

4.1. In the Administrative Console window’s left pane (tree control), select the Servers > managedServer1 node, and in the right hand pane, select the Control tab (top level), and then click the Start/Stop sub tab for managedServer1.

4.2. Click the Start this server… link:

Administration and Deployment Lab 3 – Setting up BEA WebLogic Remote Start Properties

Lab 3-5

NOTE: From now on, you can start and stop this managed server instance from the Control > Start/Stop tab in the Administrative Console. If this managed server instance was located on a remote computer, just follow the steps in this lab to capture the classpath and arguments data from the remote computer so the settings reflect the local file system paths on the system in which the managed server instance will actually be run.

4.3. Select Servers > managedServer2 in the left pane of the Administrative Console and start it.

4.4. Select Servers > proxyServer in the left pane of the Administrative Console and start it.

5. Test configuration by logging into Webtop.

5.1. In the admin console, select the Deployments > Web Application Modules > webtop node in the left pane.

5.2. Open a browser window and connect to managedServer1 by entering the following URL:

http://localhost:8001/webtop/

5.3. After a few moments a Webtop Login page will display. You have just verified that the managedServer1 has been correctly configured with Remote Start settings.

5.4. Repeat the test for managedServer2 at:

http://localhost:8002/webtop/

5.5. Test the load balancing mechanism through the HttpClusterServlet by connecting to the proxyServer:

http://localhost:7003/webtop

Administration and Deployment Lab 3 – Setting up BEA WebLogic Remote Start Properties

Lab 3-6

5.6. A Webtop Login page should display:

6. Restore the startManagedWebLogic.cmd file to it’s previous state.

6.1. Edit the startManagedWebLogic.cmd file you modified in step 1 and reverse your temporary changes. Save the file.

6.2. Or, you can simply copy your backup version of the file over the one you edited in this lab.

NOTE: This file is no longer needed. From this point you will normally start and stop your managed server instances from within the Administrative Console.

End of Lab 3