WebLogic Server 8.1.1 Setup Instructions

WebLogic Server 8.1.1 Setup Instructions

1.Installing WebLogic Server 8.1.1

__ 1.Log on to Windows with user name wasadmin and password wasadmin.

__ 2.From the CD, copy the server811_win32.exe file to c:\download\.

__ 3.Run the file c:\download\server811_win32.exe.

__ 4.Wait a moment.

__ 5.On the Welcome page, click Next.

__ 6.In the License Agreement page select Yes and click Next.

__ 7.In the home directory page accept the default as follows and click Next.

__ 8.On the Choose Install Type page, select Complete Installation and click Next.

__ 9.In the Choose Product Directory keep C:\bea\weblogic81 as the default Installation Directory and click Next.

Note: From this point on, the product installation directory (c:\bea\weblogic81) will be referred as <WebLogic Install> and <WL_HOME>.

__ 10.System will begin installing the product.

__ 11.On the Installation Complete page, uncheck both Install XML Spy and Run Quickstart.

__ 12.Click Done.

2.Configuring the system path.

__ 1.If you haven’t already done so, log on to Windows as wasadmin (password: wasadmin).

__ 2.From the Windows Start menu, select Settings -> Control Panel -> System. The System Properties window will be displayed.

__ 3.Select the Advanced tab -> Environment Variables.

__ 4.Highlight Path under System variables and click Edit.Add the following after the previous paths, and click OK.


__ 5.Click New under system variables.

__ 6.Enter CLASSPATHas Variable Name

__ 7.Enter the following path to Variable Value


__ 8.Click OK.

__ 9.Select the OK button to return to the System Properties window.

__ 10.In the System Properties window, click the OK button to apply the changes.

__ 11.Close the Control Panel window.

3.Examine environment variables

__ 1.Edit the C:\labs\PointBase\setenv.cmd file with a text editor and examine these 2 entries:
set WL_HOME=C:\BEA\WebLogic81

__ 2.Make sure these values are consistent with your installation of BEA WebLogic Server (these should match if the installation instructions were followed correctly.)

__ 3.Similarly, open theC:\labs\Lab1\setenv.cmd file with a text editor and examine these 2 entries:


set WL_HOME=C:\BEA\WebLogic81

__ 4.Again, verify sure these values are consistent with your installation of BEA WebLogic Server.

4.Start the PointBase database server

__ 1.Open a command prompt and change directory to C:\labs\PointBase.

__ 2.Type dbStart at the command prompt.

__ 3.Verify the message above is displayed. Do not close the command prompt because the server is running.

5.Create the CIGNA database

__ 1.Open another command prompt and change directory toC:\labs\PointBase.

__ 2.TypedbCreateat the command prompt.

Note: The dbCreate command creates a database user with a username/password of cignauser/cignapwsd and creates 5 tables in this user's database schema. You will see DROP TABLE error messages when running dbCreate for the first time. This is expected behavior, because the tables don't exist yet. This script can be used later to recreate the database and put it back into a "fresh" state for testing.

6.Verify the creation of the CIGNA database

__ 1.Type dbSQLat the command prompt.

__ 2.Type the following (don’t forget the ; at the end of the line.)

select * from category;

__ 3.You will see the records in the category table as shown below.

__ 4.Verify that 5 rows are returned.

__ 5.Type the following to exit.


__ 6.Close this command prompt but do not close the command prompt where the server is running.

7.Create the WebLogic CIGNA domain and CIGNA server

__ 1.To run the BEA WebLogic Configuration Wizardfrom the Start menu, select Programs > BEA WebLogic Platform 8.1 > Configuration Wizard.

__ 2.On the first screen, selectCreate a new WebLogic configuration and click Next.

__ 3.Choose Basic WebLogic Server Domain and clickNext.

__ 4.On the "Choose Express or Custom Configuration" screen, select the option to create a Custom configuration and click Next.

__ 5.On the "Configure the Administration Server" screen, change the "Name" field to CIGNA_Server. Leave the other values as defaults.

__ 6.Click Next.

__ 7.On the "Managed Servers, Clusters, and Machines Options" screen, selectNo and click Next.

__ 8.On the "Database (JDBC) Options" screen, selectYes and click Next.

__ 9.On the "Configure JDBC Connection Pools" screen, click Add.

__ 10.Fill out the fields as shown below (the user password is cignapswd).

__ 11.Click Next.

__ 12.On the "Configure JDBC MultiPools" screen, click Next.

__ 13.On the "Configure JDBC Data Sources" screen, click Add.

__ 14.Fill out the fields as below. The "Honor global transaction" checkbox should be cleared.

__ 15.Click Next.

__ 16.On the "Test JDBC Connection Pools…" screen, click Test Connection.

Verify that the Test Successful message appears under Results. Note: If the connection test fails, verify the following things:

1. The database server is running

2. The fields in the "Configure JDBC Connection Pools" screen are correct.

__ 17.Click Next.

__ 18.On the "Messaging (JMS) Options" screen, choose No and click Next.

__ 19.On the "Applications and Services Targeting Options" screen, choose Yes and click Next.

__ 20.On the "Target Services to Servers or Clusters" screen, click Select All or the checkbox next to the "JDBC" folder to select all the items. CIGNA_Server should be shown as the target server.

__ 21.Click Next.

__ 22.On the "Configure Administrative Username and Password" screen, fill out the fields as follows, the user and password arewlsadmin:

__ 23.Underneath these fields, choose No for "Configure additional users, groups, and global roles." Click Next.

__ 24.On the "Configure Windows Options" screen, choose Yes for "Create Start Menu" and No for "Install Administrative Server as a Windows Service." Click Next.

__ 25.On the "Build Start Menu Entries" screen, you may change the "Shortcut link name" to Start CIGNA_Server or just accept the default value. Click Next.

__ 26.On the "Configure Server Start Mode and Java SDK" screen, choose Development Mode and Sun SDK 1.4.1_03-ea @ C:\BEA\jdk141_03 in the "BEA Supplied SDKs" list. (The server will start much faster.).

__ 27.Click Next.

__ 28.On the "Create WebLogic Configuration" screen, change the "Configuration Name" field in the lower right corner to CIGNA_Domain.

__ 29.Click Create.The configuration wizard will now create the domain and server configuration, which may take a few moments.

__ 30.After it completes, check the "Start Admin Server" checkbox and click Done.A startWeblogic command will open and it will show the message “<Server started in RUNNING mode>”. Leave the command prompt open.

8.Start the WebLogic Server Console

__ 1.Launch a browser and point to . (You may want to bookmark this URL.)

__ 2.Log in using wlsadmin/wlsadmin as the username/password.

__ 3.In the navigation pane on the left, expand the Servers,Deployments, and Services nodes, by clicking the [+] next to each one of these nodes.

__ 4.Under Services, expand the JDBC nodethen expand its Connection Pools andData Sourcesnodes.

__ 5.Verify that CIGNA_Server, CIGNA_ConnectionPool, and CIGNA_DataSource are shown.

__ 6.Leave the WebLogic Server Console open.

9.Deploy the CignaWeb application

__ 1.Open a command prompt and change the directory to C:\labs\Lab1.

__ 2.Type deploy at the command prompt. Leave the command prompt open.

__ 3.Go back to the WebLogic Server Console and refresh the page.

__ 4.Verify the CignaWeb application is now listed under the DeploymentsWeb ApplicationModules node.

10.Test the application

__ 1.Open another browser window and point to .
Note that there will be delays in loading the pages the first time, because the JSPs are being translated and compiled.

__ 2.Verify the CignaWeb application looks like this:

__ 3.To stop the server, right click on CIGNA_Server in the WebLogic Server Console, and click start/stop this server.

__ 4.In the right pane, click the Force shutdown of this server … link.

__ 5.At the confirmation page, click Yes.

__ 6.After few seconds the browser will show an Action canceled page.

__ 7.Close all the web browser and command prompt open.

Page 1 of 22