Wlsadmin Lab Guide

7/27/2019 Wlsadmin Lab Guide

1/59

Lab 1A: Installing Oracle WebLogic Server 10.3.2After completing this exercise, you should be able to install the Oracle WebLogic Server10.3.2 software

In this practice, you install Oracle WebLogic Server 10.3.2 by performing thefollowing steps:

1.1 Run the installation program: wl s1032_wi n32. exe

1.2 Use the following configuration information:

Screen Value

Choose BEA Home Directory C: \ Or acl e\ Mi ddl ewar e

Note: Select Yes when a warningmessage appears stating that Thedirectory is not empty, do you want toproceed?

Choose Install Type Typical

JDK Selection Bundled JDK - BEA JRockit 1.6.0_05SDK

Choose Product Installation Directories C: \ Or acl e\ Mi ddl ewar e\ wl ser ver _10. 3

1.3 Review Installation Summary. Finally, deselect the RunQuickstart check box and clickDone to complete the installation.

1


2/59

Lab 1B: Configuring a Domain

After completing this practice, you should be able to create: a new domain using the configuration wizard

Basic Instructions

1. Configure a new domain using the Configuration Wizard.

Configure the Administration Server with the following specifications:

Name: Admi nServerListen address: Al l Local Addr essesListen Port: 7001Note: Do not enable SSL.

Configure the Administrator username and password with the following specifications:

Username: webl ogi cPassword:webl ogi c1Confirm user password:webl ogi c1

Currently, there is no need to configure additional users, groups, and global resourcesroles.

2. Test the domain that was created by changing the directory to/ domai ns/ base_domai n and executing the following:

./st artWebLogi c. sh

Specify the following username and password:

Username: webl ogi c

Password:webl ogi c1

2


3/59

Lab 1C: Using the Administration Console

After completing this exercise, you should:

Be familiar with the Administration Console

Practice modifying the properties of Oracle WebLogic Server using the Administration

Console Configure and view log file entries for an Oracle WebLogic Server using the

Administration Console

Oracle WebLogic Server is administered by using a Web-based Administration Console

that enables you to configure and monitor the Oracle WebLogic servers. Using Log

messages, you can detect problems, track down the source of an error, and track systemperformance.

Basic Instructions1. Start Oracle WebLogic Server for the examples domain base_domai n.

2. Use the Administration Console to modify the standard output severity threshold for the

Admi nSer ver ( admi n) to I nf o.

3. Shut down the Admi nSer ver ( admi n) server by using the Administration Console.

4. Restart the Administration Server, and then view the server logging for Admi nServerusing the Administration Console.

3


4/59

Solution: Using the Administration Console

In this practice, you start and stop Oracle WebLogic Server by using the Administration

Console and view the server logs.

Start Oracle WebLogic Server for the Examples Domainbase_domain.1.1 Start > All Programs > Oracle Weblogic > User projects > base_domain > Start Admin

Server for Weblogic Server domain.

Use the Administ ration Console to modify the standard output severity threshold forbase_domainto Info.

2.1 Open a Web browser and navigate tohttp://localhost:7001/console.Log in as:



2.2 Navigate to base_domain> Environment > Servers >AdminServer(admin) >

Logging> General.

2.3 Scroll to the bottom of the page and clickAdvanced.

2.4 Set the following properties:

Redirect stdout logging enabled: Selected

2.5 In the Message Destination(s) section, set the following Standard out properties:

Severity level: Info 2.6 Save your changes.

Shut down the AdminServer(admin)server using the Administration Console.

3.1 Navigate to base_domain> Environment > Servers > AdminServer(admin) >

Control > Start/Stop. Verify that the Admi nServer ( admi n) check box is selected inthe ServerStatustable and click Shutdown.

4
http://localhost:7001/consolehttp://localhost:7001/consolehttp://localhost:7001/consolehttp://localhost:7001/console


5/59

Solution: Using the Administration Console (continued)

3.2 Start the server again using the instructions in the preceding step 1.1.

3.3 Note how much more information is output to the stdout I/O stream when the server is

started again (once again, you should see a number of notices of severity ).

View server logging for the AdminServerusing the Administration Console as the log

viewer.

4.1 Open a Web browser and navigate tohttp://localhost:7001/console.

Log in as:



4.2 Navigate to base_domain > Diagnostics > Log Files.

4.3 In the Log Files table, select ServerLog and click View. This allows you to view log fileentries via the console.

5
http://localhost:7001/consolehttp://localhost:7001/console


6/59

6


7/59

Node Manager Listen Node Manager ListenName Address Port (Type = Plain) Server

Lab 2

Configuring Servers and Machines

After completing this practice, you should be able to:

Create WebLogic machines

Create Managed Servers

Assign Managed Servers to machines

Start Managed Servers

In this lab, you create and configure the Managed Servers server1, server2, and

server3 and machines machine1and machine2for the base_domain that you createdto simulate the production environment.

Specifications

Table 2 Managed Server Specifications

Server Name Listen Address Listen Port SSL Listen Port

server1 127.0.0.1 7003 7004

server2 127.0.0.1 7005 7006

server3 127.0.0.1 7007 7008

Table 3 Machine Specifications

machine1 127.0.0.1 5555 server1

machine2 127.0.0.1 5556 server2

server3

7


8/59

Basic Instructions

1. Using the administration console, go to base_domain > Environment > ServersIf you havent acquire the lock, click Lock & Edit in ChangeCenter

2. Create and configure the Managed Servers server1, server2and

server3by referring to the server specifications in Table 2.

3. Create and configure the machines machine1and machine2by referring to the

machines specifications inTable 3.

4. Test the configuration by starting the created Managed Servers using the command line,by executing the following command that replaces with the name of theManaged Server (folder:C:\Oracle\Middleware\user_projects\domains\base_domain\bin):

startManagedWebLogic http://127.0.0.1:7001

Tip: If you are using the local address for the Administration Server, you can simply

supply the as the argument.

8
http://127.0.0.1:7001/http://127.0.0.1:7001/


9/59

Solut ion: Conf igur ing Servers and Machines

In this practice, you configure the Managed Servers and machines.

Create the servers.

1.1 If not already open, open a Web browser and navigate tohttp://localhost:7001/console.Log in as:

Username: weblogic

Password: weblogic1

1.2 Navigate to base_domain > Environment > Servers > server1>Configuration > General. Lock the console. Create the Managed Serverserver1to match the specifications in Table 2.

1.3 Create andconfigure the server2 and server3servers in the same way as step 2.2

.

9


10/59

Practice 2-1: Con f igur in g Servers and Machines (cont inu ed)

2.6 Navigate to base_domain > Environment > Servers > server2> Configuration >General. Specify the following properties:

SSL Listen Port Enabled: Selected

SSL Listen Port: 7006

Note: Leave the machine setting at None in this step. You will assign the machines to the

Managed Servers after you create them.Save and Activate your changes.

2.7 Similar to how you created and configured the Managed Server server2, create the

Managed Server server3using the Managed Server specifications from Table 2.

Create and configure the machines.

3.1 Navigate to base_domain > Environment > Machines. Lock the console. Underthe Machines table, click New. Specify the following properties on the Create aNew Machine page:

Name:machine1

Machine OS: Other

Click OK.

Activate your changes.

3.2 Assign the machine machine1to the server1server by clicking the machine

name. Lock the console and click the Servers tab.

3.3 Click Add under the Servers table. Select server1from the existing server drop-downlist and click Finish.

3.4 Click the Node Manager tab to enter the properties of Node Manager for this machineaccording to the machine specifications (Table 3).

Note: In this training environment, you use a PLAIN text connection between NodeManager and the servers. In production, using SSL secures the communication whenusing the Java-based Node Manager.

3.5 Save and activate your changes.

3.6 Repeat this process to create the machine, machine2, by referring to the machine

specifications in

Table 3, and assign the Managed Servers server2and server3to machine2.

Also configure the Node Manager properties for the machine.

Test the configuration by starting the created Managed Servers.

4.1 Open a window command prompt by running the cmd command.

4.2 Change to the \domains\base_domain\bin directory.

10


11/59

Practice 2-1: Conf ig ur ing Servers and Machines (con t inued)

4.3 Start the Managed Servers using the command line by executing the following

command that replaces with the name of the Managed Server

(folder:C:\Oracle\Middleware\user_projects\domains\base_domain\bin):

startManagedWebLogic http://127.0.0.1:7001

Tip: If you use the local address for the Administration Server, you can simply supplythe

argument.

4.4 If prompted, enter the Administrator credentials at server prompt.

Note: Check to make sure that all Managed Servers are up and running.Before you start the next lab, make sure that all Managed Servers are

stopped (CTRL+ C to stop server1, 2, and 3on terminal windows).

11
http://127.0.0.1:7001/http://127.0.0.1:7001/


12/59

Lab 3

Lab 3: Starting the Servers Using Node Manager

After completing this exercise, you should be able to:

Configure a machine for remote startup and shutdown

Configure and run Node Manager

Start and stop servers remotely

Node Manager is a Java program running in a remote machine that allows the Administration Server toremotely start any Managed Server instances on that machine. It can also be used to monitor the health

status of the Managed Servers on that machine. In this lab, you configure Node Manager properties formachine2and remotely start the Managed Server instances running on machine2using the

Administration Console.

The Node Manager service runs on Port 5556. You must declare the AdminServers IP address

as a trusted host so that it can access the Node Manager process on machine2.

Design Specifications

Element Value

Node Manager service port for machine2 5556

IP Address of AdminServer 127.0.0.1

Node Manager service port for machine1 5555

12


13/59

Basic Instructions

1. Connect to the domain using WLST. Apply the nmEnrollWLST command to enroll the

machine. Navigate to Domain and set the classpath of servers.

2. Open a prompt and change to the /server/bindirectory.

Start Node Manager to listen on port 5555 on machine1by executing the following

command:startNodeManager.cmd 127.0.0.1 5555

Start Node Manager to listen on port 5556 on machine2by executing the followingcommand:

startNodeManager.cmd 127.0.0.1 5556

3. Start the servers using the Node Manager service.

13


14/59

Solut ion: Start ing Servers Using Node Manager

1.1 Start WLST by entering the following command at the prompt:

java weblogic.WLST

Note: WLST is case-sensitive.

1.2 At the wls:/offline>prompt, enter:

connect (weblogic,weblogic1,t3://localhost:7001)

1.3 After you are connected at thewls:/base_domain/serverConfig> prompt, enter

the following command:

nmEnroll ([domainDir], [nmHome])

wls:/base_domain/serverConfig>nmEnroll(C:/Oracle/Middleware/user_projects/domains/base_domain,C:/Oracle/Middleware/wlserver_10.3/common/nodemanager)

Start Node Manager.

2.1 Open a command prompt and change to the \server\bindirectory.

2.2 Start Node Manager to listen on port 5555 on machine1by executing thefollowingcommand:

startNodeManager 127.0.0.1 5555

14


15/59

Practice 3-2: Start ing Servers Using Node Manager (con t inued)

2.3 Start Node Manager to listen on port 5556 on machine2by executing the

followingcommand:startNodeManager 127.0.0.1 5556

Start the servers using the Node Manager service.

3.1 Return to the Administration Console and navigate to base_domain> Environment >

Servers > server1> Control > Start/Stop. Select the check box against server1inthe Server Status table and click Start. When prompted to verify whether you want tostart the server1Managed Server, clickYes.

Note: If you get an error, shut down the Node Manager associated with 5555, edit the

nodemanager.propertiesfile underC:/Oracle/Middleware/wlserver_10.3/common/nodemanag er, and make surethat the SecureListener property is set to true. Start Node Manager and try step 4.1 again.

3.2 Repeat the preceding step to start the Managed Servers server2and server3.

3.3 Navigate tobase_domain> Environment > Servers. Verify the running state for both the

Managed Servers server2and server3.

3.4 Stop server1, server2, and server3and both Node Managers.

Note: From here on, you should try to start or stop the Administration Server and theManaged Servers using the command line rather than the Administration Console just tobe consistent. This will also allow you to see the error/debug/info messages easily on theterminal window (especially in the case of Clustering labs).

15


16/59

16


17/59

Lab 4

Deploying and Undeploying Web Applications

At the end of this exercise, you should be able to deploy a prepackaged .warfile.

Interactive, Web applications are groupings of static pages and dynamic pages for the overall

application. They can be packaged in a Web Archive file with a .war extension. They arepackaged using the JAR utility. In this lab, you deploy the Web application

helloworld.war, and also deploy and undeploy the helloworld_as_default.war

Web application.

: C:\studentWLSS103\work

Basic Instructions

1. Deploy the helloworld.warWeb application.

2. Deploy the helloworld_as_default.warWeb application.

3. Undeploy the helloworld_as_default.warWeb application using the Administration

Console.

17


18/59

Solut ion: Deploying/Undeploying Web App l icat ions

In this practice, you deploy, and then undeploy a Web application.

Deploy the Web application.2.1 Start AdminServerand the server1Managed Server if they are not already running.

2.2 Navigate to the /lab4directory, locate the helloworld.warfile.


Username: weblogicPassword: weblogic1

2.4 Navigate tobase_domain> Deployments. Lock the console.

2.5 If helloworld.warexists, select the helloworldapplication, and then click Stop >Force Stop Now. (The state changes to Prepared. If you click Prepared, you can see

that the application is successfully stopped.) Select the helloworldapplication, andthen click Delete. Activate your changes, and then re-lock the console.

2.6 Lock the console. In the Deployments table, click Install. Navigate to the location

/lab4, select helloworld.warand click Next.

2.7 On the Choose Targeting Style page, select Install this deployment as anapplication, which is the default option, and click Next.

2.8 On the Select Deployment Targets page, select the server1Managed Server in theServers table and click Next.

2.9 On the Optional Settings page, under the Source Accessibility header, select Copythis application onto every target for me and click Next.

2.10 On the Review page, select No, I will review the configuration later under theAdditional Configuration header and click Finish.

2.11 Activate your changes.

2.12 Navigate tobase_domain> Deployments. In the Deployments table, select the

helloworld application check box and click Start > Servicing All Requests. (Optional)

18


19/59

Solut ion: Deploying/Undeploying Web App l icat ions(cont inued)

2.14 The Summary of Deployments page should indicate the module state as Active orDistribute Running when the deployment has been completed.

2.15 Verify that the deployment has been completed by opening a browser and navigating tohttp://localhost:7003/helloworld.

This should open up the helloworld application.

Deploy the Web application helloworld_as_default.war.

3.1 Sometimes, it is convenient to set a Web application as a default Web application for aserver, so that in the request URL, you can omit the context name. You can select one

default Web application per server. In this lab, the helloworld_as_default.warapplication has been configured to be the default Web application.

Note: The only difference between helloworld.warand

helloworld_as_default.war is that the latter has a deployment descriptor file

called/WEB-INF/weblogic.xml, which contains the stanza:

/

Note:A similar result could also have been achieved by navigating to Servers > server1> Protocols > HTTP tab of the admin console and specifying value for the attribute"Default WebApp Context Root". This way developers don't have to built-in thisinformation during development.

3.2 Navigate to the /lab4directory, locate the

helloworld_as_default.war file.

3.3 Deploy the helloworld_as_default.warWeb application that is located in the

/lab4directory to server1.

Note: Do not forget to activate the changes and start the application.

3.4 Verify the default Web application configuration by browsing tohttp://localhost:7003.

Note: You do not need to specify the application root /helloworldin the requested URLany more.

Undeploy the helloworld_as_default.warWeb application using the Administration

Console.


4.2 In the Deployments table, click helloworld_as_default. The settings for

helloworld_as_default appears. Click the Targets tab, deselect the check box for

the server1 target, and then click Save. Under Message, you should get aconfirmation that your settingsweresaved successfully.


19
http://localhost:7003/benefitshttp://localhost:7003/http://localhost:7003/http://localhost:7003/benefits


20/59

Solut ion: Deploying/Undeploying Web App l icat ions(cont inued)

4.4 Verify that the Web application was indeed undeployed by browsing tohttp://localhost:7003.

You should get an error, Error 404 Not Found, when you do this.

Note: If you use the same browser window to request the Web application, browsercaching may result in pages being served even after the application itself is undeployed.You can clear the browser cache for Firefox by selecting Edit > Preferences > Privacy >Cache Options from the Menu bar and clicking Clear Cache Now. Reload the page.

20
http://localhost:7003/http://localhost:7003/http://localhost:7003/


21/59

21


22/59

Lab 5

Using a Deployment Plan


Create deployment plans

Deploy enterprise applications along with the deployment plan

Describe the directory structure of an exploded enterprise application for its successfuldeployment

Sometimes, it is necessary to deploy applications multiple times and in different types of

environments. Instead of having to configure the deployment information each time, it would beeasier to package that information with the application. Therefore, the user creates the

deployment plans for an enterprise application and creates a proper directory structure for thesuccessful deployment of enterprise applications.

The user manually creates an initial deployment plan for an enterprise application that resides

outside the application archive and configures an application for deployment to a specific OracleWebLogic Server environment. The deployment plan helps the administrator to easily modify anapplications WebLogic Server configuration for deployment into multiple, differing WebLogicServer environments without modifying the deployment descriptor files that are included in the

application archive. The user creates a proper directory structure for the successful deployment ofenterprise applications that are packaged withthedeployment plan. See Figure 8.

22


23/59

Basic Instructions

1. Create the folder C:\studentWLS103\work\lab5\plan

2. Use weblogic.PlanGeneratorto create a plan entitled plan.xmlfor the

helloworld application. Open a command prompt and change to the C:\work

directory. Execute the following command:

java weblogic.PlanGenerator all root lab5

Navigate to the C:/work/lab5/plandirectory and open

plan.xmlusing a text editor.

Set /as a value forWeblogicWebApp_ContextRoots_xxxxxxxxxxxxxx.

Remove the attribute xsi:nil="true"from the tag, so that itlooks like the following:

WeblogicWebApp_ContextRoots_

xxxxxxxxxxxxxx /

In the area WeblogicWebApp_ContextRoots_xxxxxxxxxxxxxx

add the following line: replace ,

so that it looks like the following:

WeblogicWebApp_ContextRoots_ xxxxxxxxxxxxxx

/weblogic-web-app/context-rootreplace

3. Redeploy the application with the plan in the Administration Console.

5. View the deployed application.

23


24/59

Solut ion: Using a Deploym ent Plan

In this practice, you create a deployment plan, and then deploy an application using thisplan.

Set up the exercise.

1.1 Create the folder C:\studentWLSS103\work\lab5\plan

Deploy the helloworldapplication

2.1 In the Administration Console, navigate tobase_domain> Deployments. Lock

the console, if necessary.

2.2 Click Install in the right pane and browse to theC:\studentWLSS103\work\lab5\appdirectory.

Select helloworld.warand click Next.

2.3 On the Install Application Assistant page, select Install this deployment as an

application and click Next.

2.4 Target the application to server1. Click Next.

2.5 On the Optional Settings page, enter HRAppas the name and select Copy this

application onto every target for me under the Source Accessibility section. ClickFinish and Activate the changes.

2.6 Navigate tobase_domain> Deployments and select the check box for the

helloworld application. Click Start > Servicing all Requests.

2.7 Point your browser tohttp://localhost:7003/helloworld.

24
http://localhost:7003/http://localhost:7003/http://localhost:7003/http://localhost:7003/


25/59

Solut ion: Using a Deploym ent Plan (cont inued)

Useweblogic.PlanGeneratorto create a plan plan.xml.

3.1 Change to the C:\studentWLSS103\work\lab5\plandirectory.

3.2 Enter the following command:

java weblogic.PlanGenerator all root lab5

PlanGeneratoris a utility for creating a deployment plan template based on the

standard descriptors included in an application. The resulting plan (-planoption) willdescribe the application structure, identify all deployment descriptors, and will export asubset of the applications configurable properties.

By default, the plan exports only application dependencies. This can be overridden withany one of the following:

-declarations: Export resources defined by the application

-configurables: Export non-resource-oriented configurable properties

-dynamics: Export properties that may be changed in a running application

-all: Export all changeable properties

-none: Export no properties

3.3 Navigate to the C:\studentWLSS103\work\lab5\plandirectory and open

plan.xmlusing a text editor.

3.4 Set /as a value forWeblogicWebApp_ContextRoots_xxxxxxxxx.

3.5 Remove the attribute xsi:nil="true"from the tag, so that it appears thus:

WeblogicWebApp_ContextRoots_xxxxxxxxxx/

3.6 In the following area:

WeblogicWebApp_ContextRoots_xxxxxxxxxxxx

Add the following line:

replace

So that it appears thus:

WeblogicWebApp_ContextRoots_xxxxxxxxxxxx

/weblogic-web-app/context-rootreplace

25


26/59

Solut ion: Using a Deploym ent Plan (cont inued)

Redeploy the application with the plan in the Administration Console.

4.1 In the Administration Console, navigate tobase_domain> Deployments. Lock

the console.

4.2 Select helloworldand click Update.

4.3 Click Change Path next to Deployment Plan Path.4.4 Select C:\studentWLSS103\work\lab5\plan.

Select plan.xmland click Next.

4.5 Select Redeploy this application using the following deployment files (if notselected). Click Next, and then click Finish. Click Activate changes.

View the deployed application.

5.1 Point your browser tohttp://localhost:7003/.

26
http://localhost:7003/EEOAPPhttp://localhost:7003/EEOAPPhttp://localhost:7003/EEOAPP


27/59

27


28/59

Lab 6: Production Redeployment

After completing this exercise, you should be able to describe:

Production Redeployment

The importance of versioning the enterprise applications that are deployed to OracleWebLogic Server

The importance and advantages in using Production Redeployment

The user gets to deploy the first version of an application and view the application. Thereafter, the

user redeploys the second version of the same application, which is modified a bit, and views thisversion of the application. The old client, if not yet finished with using the application, still hasaccess to the first version ofthe application, whereas the new clients get connected to the second

version of the application. When thefirstversion of the application is no longer in use by a client,the state of the first version of the application is retired and that version of the application

becomes unavailable.

Using the Production Redeployment strategy, users can experience how to use WebLogic Serverto redeploy a new version of a production application without interrupting the availability of theapplication tonew client requests. Thus, the new clients get connected to the new version of theapplication, and the previous version of the application, which is still in use by the older clients,gets retired after the client disconnects.

28


29/59

Basic Instructions

1. Verify that both v1and v2are in the C:\studentWLSS103\work\lab6directory.

2. Deploy the helloversionapplication that is stored in the

C:\studentWLSS103\work\lab6\v1directory such that the version number for that

application is v1.0.

3. View the deployed application, v1.0.

4. The State of the deployed application v1should be Active.

5. Deploy the helloversionapplication from the C:\studentWLSS103\work\lab6\v2

directory such that the version number for that application is v2.0.

6. After you redeploy the application as v2.0, the State of the application v1.0becomes

stop running (and later become retired)and the State of the newly deployed application

v2is Active.

7. View the deployed application v2.0for changes (the text displayed is v2.0). All the new

clients get connected to v2.0 of the application. When v1.0of the application is no

longer in use by a client, the State of the application becomes Retired.

29


30/59

Solut ion: Product ion Redeploym ent

In this practice, you configure production redeployment for two versions of anapplication.

Copy the helloversionapplication.1.1 Verify that both v1and v2are in the C:\studentWLSS103\work\lab6directory.

Deploy the helloversionapplication stored in the C:\studentWLSS103\work\lab6\v1


30


31/59

Practice 6-2: Produc t ion Redeploym ent (con t inued)

2.1 Open the command prompt and navigate to theC:\studentWLSS103\work\lab6\v1directory. Enter the following to deploy the

application:

java weblogic.Deployer -adminurl t3://localhost:7001

-user weblogic -password weblogic1 -deploy -name helloversion

sourcehelloversion.war -targets server1 -stage -appversion v1.0

View the deployed application v1.

3.1 Point your browser tohttp://localhost:7001/helloversion.

The text shown should be v1.0

Note: Do not close this browser because it is required to show further results.

State of the deployed application v1.0should beActive.

4.1 Click Deployments under the base_domaindomain structure in the left pane of theAdministration Console. In the right pane on the Summary of Deployments page, check

to see whether the State of the helloversion(v1.0)application is Active. (Note:Youmayseea warning message under the Health column.)

Deploy the helloversionapplication stored in the C:\studentWLSS103\work\lab6\v2


5.1 In the command prompt, navigate to the C:\studentWLSS103\work\lab6\v2

directory. Enter the following to deploy the helloversion.warapplication:

java weblogic.Deployer -adminurl t3://localhost:7001

-user weblogic -password weblogic1 -deploy -name helloversion

sourcehelloversion.war -targets server1 -stage -appversion v2.0

After redeploying the application as v2, the Stateof application v1.0becomes stoprunning and the Stateof the newly deployed application v2.0 isActive.

6.1 Click Deployments under the base_domaindomain structure in the left pane of theAdministration Console. In the right pane on the Summary of Deployments page, checkto see whether the State of the: helloversion(v1.0)application is stop running

and the helloversion(v2.0)application is Active.(Note: You may see a warningmessage under the Health column.)

6.2 Display the browser window that you opened in step 3.1.

Note: v1.0.

View the deployed application v2.0for changes.

31
http://localhost:7001/http://localhost:7001/http://localhost:7001/


32/59

Solut ion: Product ion Redeployment (cont inued)

9.1 Open up a new browser from your neighbours PC and point to your weblogicserverE.g. http://:7003/helloversion/

Note: The version should be v2.0.

All the new clients get connected to v2.0of the application. When v1.0of theapplication is no longer in use by a client, the State of the application becomes Retired.(It may take a while for the state to change.)

32


33/59

33


34/59

Lab 7

Configuring the JMS Servers and Destinations

After completing this practice, you should be able to get hands-on experience with configuringand monitoring Java Message Service (JMS) queues and topics.

A JMS server implements the JMS infrastructure on a WebLogic Server. Destinations

(queues or topics) are targeted to a WebLogic server when the JMS server is targeted tothe WebLogic server.

In this exercise, you configure a JMS server myJMSServer, a queue myQueue, and a

topic myTopic. You then post messages to the queue and topic, and monitor them in the

Administration Console. For reference, see the following figure.

Currently, you do not have any consumers; you simply post the messages and get familiarwith monitoring the message statistics in the Administration Console.

34


35/59

Basic Instructions

1. Configure a JMS server with the following specifications:

Name: myJMSServer

Persistent Store: (none)

2. Configure a JMS module, and add a queue and topic to the JMS module, according to thefollowing specifications:

JMS Module

Name: myModule

Descriptor File Name: myModule

Target: server1

Subdeployment

Subdeployment Name: server1SubDeployment

Targets: myJMSServer

Queue

Name: myQueue

JNDI Name: myQueue

Template: None

Target: myJMSServer

Topic

Name: myTopic

JNDI Name: myTopic

Template: None

Target: myJMSServer

3. Deploy the messaging.warWeb application, which allows you to post messages to the

queue or the topic.

4. Verify that the Web application is deployed correctly by navigating tohttp://localhost:7003/messaging and posting messages to either the queue or the topicusing thedeployed Web application.

35
http://localhost:7003/messaginghttp://localhost:7003/messaginghttp://localhost:7003/messaginghttp://localhost:7003/messaging


36/59

Practice 7-1: Conf igu r ing the JMS Servers and Dest inat ion s

In this practice, you configure the JMS server and JMS module, and add a queue andtopic to the module.

Configure a JMS server.

2.1 Ensure that AdminServer, and server1are running.

2.2 Navigate tobase_domain> Services > Messaging > JMS Servers. Lock the console.2.3 Click New under the JMS Servers table and specify the following properties:

Name: myJMSServer

Persistent Store: (none)

2.4 Click Next and target the JMS server to the server1Managed Server. Click Finish.


Configure a JMS module, and add a queue and topic to the JMS module. 3.1 Navigate tobase_domain> Services > Messaging > JMS Modules. Lock the console,

if necessary.

3.2 Click New under the JMS Modules table and specify the following properties:

Name: myModule

Descriptor File Name: myModule

3.3 Click Next and target the module to the server1Managed Server. Click Next and

select the following:

Would you like to add resources to this JMS system module?3.4 Click Finish.

3.5 On the Settings for myModule page, click the Subdeployments tab. Under theSubdeployments table, click New to create a subdeployment with the followingspecifications:

Subdeployment Name: server1SubDeployment

Click Next.

3.6 On the Targets page, select myJMSServeras the target under the JMS Servers

table. Click Finish.

36


37/59

Practice 7-1: Conf igu r ing the JMS Servers and Dest inat ion s(cont inued)

3.7 Click the Configuration tab.

3.8 On the Settings for myModule page, under the Summary of Resources table, click

New to configure a new JMS queue for the JMS module.

3.9 On the Create a New JMS System Module Resource page, under Choose the type ofresource you want to create, select Queue.

3.10 Click Next.

3.11 In JMS Destination Properties, specify the following parameters:

Name: myQueue

JNDI Name: myQueue

Template: None

3.12 Click Next.

3.13 Select server1SubDeploymentfrom the subdeployments list. Click Finish.

3.14 On the Settings for myModule page, under the Summary of Resources table, click

New to configure a new JMS topic for the JMS module.

3.15 On the Create a New JMS System Module Resource page, under Choose the type ofresource you want to create, select Topic.

3.16 Click Next.

3.17 In JMS Destination Properties, specify the following parameters:

Name: myTopic

JNDI Name: myTopic

Template: None3.18 Click Next.

3.19 Select server1SubDeploymentfrom the subdeployments list. Click Finish.

3.20 Activate the changes.

You should be able to see the JNDI entries, called myQueueand

myTopic, on the server1Managed Server.

Deploy the Web applicationmessaging.war, which allows you to post messages to the

queue ortopic.

4.1 Navigate to the C:\studentWLSS103\work\lab7directory, locate themessaging.warfile.

4.2 Navigate tobase_domain> Deployments. Lock the console.4.3 Select Install, navigate to C:\studentWLSS103\work\lab7 , and select

messaging.war. Click Next, accept all the defaults, and click Next again. Target the

application to server1. ClickNextand accept all the defaults. Click Finish (whenpossible).

37


38/59

Practice 7-1: Conf igu r ing the JMS Servers and Dest inat ion s(cont inued)


4.5 Start the application by selecting the check box against the application name under theDeployments table. Click Start and select Servicing all requests.

Verify that the Web application is deployed correctly.

5.1 If not already open, open a Web browser and navigate tohttp://localhost:7003/messaging.

5.2 Using the application, post several messages to the standard queue and to the topic, notto the distributed queue.

5.3 Use the Administration Console to view the number of messages that have been postedinto each of the destinations. Navigate tobase_domain> Services > Messaging >JMS Modules. In the JMS Modules table, click myModule. On the Summary of

Resources page, click myQueue, and then click the Monitoring tab.

Customize this table to show the Messages Total column. The Messages Total column

shows you the number of messages that have been sent to myQueue. Repeat thesesteps to view the number to messages sent to myTopic. (Observe the Messages total

count.)

38
http://localhost:7003/messaginghttp://localhost:7003/messaginghttp://localhost:7003/messaging


39/59

39


40/59

Lab 7b

Configuring Data Sources


Create a JDBC data source

Locate a JDBC data source in a servers JNDI tree

A DataSourceobject enables a JDBC client to obtain a DBMS connection from a JDBC pool.The connection pool within a JDBC data source contains a group of JDBC connections that

applications reserve,use, and then return to the pool. The connection pool and the connectionswithin it are createdwhenthe connection pool is registered, usually when starting up OracleWebLogic Server or when deploying the data source to a new target. In this lab, you create a

myDSdata source to connect to HRDatabase.

40


41/59

Basic Instructions

2. Create a DataSource with the following specifications:

Name: myDS

JNDI Name: myDS

Database Type: Oracle

Database Driver: *Oracles Driver(Thin) for instance connections;Versions:9.0.1,9.2.0,10,11

Database Name: xe

Host Name: 10.11.0.92

Port: 1052

Database User Name: testuser

Password: testing1

Initial Capacity: 1

Maximum Capacity: 2

Capacity Increment: 1

Login Delay: 1

Target: server1

3. Verify the DataSource by deploying a prepackaged testds.warWeb application andnavigating tohttp://localhost:7001/testds/testdatasource.jsp to test the datasource.

41
http://localhost:7001/testds/testdatasource.jsphttp://localhost:7001/testds/testdatasource.jsp


42/59

Practice 7b-1: Conf ig ur in g Data Sources

In this practice, you create and validate a new DataSource.

Create a DataSourceobject.

2.1 Start AdminServerand the server1Managed Server if they are not already running.2.2 If not already open, open a Web browser and navigate tohttp://localhost:7001/console.

Log in as:

Username: weblogic

Password: weblogic1

2.3 Navigate tobase_domain> Services > JDBC > Data Sources. Lock the console.

2.4 On the Summary of JDBC Data Sources page, lock the console and click New under theData Sources table. Specify the following properties for configuring a JDBC data source:

Name: myDSJNDI Name: myDS

Database Type: Oracle

Database Driver: *Oracles Driver(Thin) for instance connections;Versions:9.0.1,9.2.0,10,11

Note: Do not select the Thin XA driver.

2.5 Click Next.

2.6 On the Transaction Options page, retain the default options and click Next.

42


43/59

Practice 7b-1: Conf igu r ing Data Sources (cont in ued)

2.7 Define the following connection properties:

Database Name: xe

Host Name: 10.11.0.92

Port: 1521

Database User Name: testuser

Password: testing1

2.8 Click Next.

2.9 Click Test Configuration to check if the connection to the database is working, and thenclick Next.

2.10 Target the server1Managed Server and click Finish.

2.11 Click myDSunder the Data Sources table on the Summary of JDBC DataSources page.

2.12 Click the Configuration > Connection Pool tab. Specify the following parameters:

Initial Capacity: 1

Maximum Capacity: 2

Capacity Increment: 1

2.13 Save and activate your changes.

2.14 Check the JNDI tree of the server1Managed Server to make sure that the data source

is deployed.Look for a JNDI entry called myDS.

Verify the DataSourceby deploying a prepackaged testds.warWeb application.

3.1 Navigate to the /exercisedirectory, locate the testds.warfile, and

copy it tothe /applicationsdirectory.


3.3 Select Install, navigate to /applications , and select testds.war.

3.4 Make sure that you opt to Install this deployment as an application, target theapplication to server1, and select Copy this application onto every target for mefor Source accessibility on the Optional Settings page. Click Finish.

3.5 Activate your changes, and then start the application.

3.6 Open a Web browser and navigate tohttp://localhost:7003/testds/testdatasource.jsp totest the data source. Use the Test Data Source button to retrieve data from the xedatabase.

43
http://localhost:7003/testds/testdatasource.jsphttp://localhost:7003/testds/testdatasource.jsp


44/59

44


45/59

Lab 8: Configuring SSL

= C:\studentWLSS103\work = C:\Oracle\Middleware\user_projects


Use keytool to generate an identity keystore that contains a private key and a self-signedpublic certificate

Configure keystores

Configure secure sockets layer (SSL)

Many applications need the security of communicating over the secure sockets layer

(SSL). This provides secure communications between the server and the client, or

between two servers. In this lab, you configure SSL and the keystores for the server1

Managed Server in the base_domain domain.

Table 5: Identity Key and Certificate Design Specifications

Identity Key and Certificate

X.500 Distinguished Name: "CN=localhost, OU=Weblogic Workshop, O=Weblogic,C=US"

Private key alias: mykey

Private key password: mykeypass

Validity duration: 365 days

Encryption strength: Algorithm (-keyalg): RSA

Size (-keysize): 512-bit

CSR filename: my_cert_request.pem

Table 6: Identity Keystore Design Specifications

Identity Keystore

Keystore filename my_identity.jks

Keystore directory $WEBLOGIC_DOMAIN

Keystore password mystorepass

Keystoretype JKS

Table 7: Trust Keystore Design Specifications

Trust Keystore

Keystore filename cacerts

Keystore directory $JAVA_HOME/jre/lib

Keystore password changeit

45


46/59

Basic Instructions

1. Generate a key, a self-signed certificate, and an identity keystore:

Run the Java keytool-genkeycommand. For example:

keytool genkey v alias mykey keyalg RSA keysize 512-dname "CN=localhost, OU=Weblogic

Workshop, O=Weblogic, C=US"-keypass mykeypass-validity 365-keystore my_identity.jks-storepass mystorepass

Copy the my_identity.jksfile from /securityto the

/domains/base_domain directory.

2. Generate a CSR:

Run the Java keytool-certrequtility. For example:

keytool certreq v alias mykey file my_cert_request.pem-keypass mykeypass storepass mystorepass-keystore my_identity.jks

Copy the my_cert_request.pemfile from /securityto the


3. Configure the keystores by specifying the following properties from the WebLogicAdministrative Console:

Keystores: CustomIdentityandJavaStandardTrust

Custom Identity Keystore: my_identity.jks

Custom Identity Keystore Type: JKSCustom Identity Keystore Passphrase: mystorepass

Java Standard Trust Keystore Passphrase: changeit

4. Configure SSL by specifying the following properties:

Identity and Trust Locations: Keystores

Private Key Alias: mykey

Private Key Passphrase: mykeypass

5. Test the SSL setup.

46


47/59

Solut ion: Conf igur ing SSL

In this practice, you perform all the steps to configure SSL in an Oracle WebLogic Serverenvironment.

Generate a key, a self-signed certificate, and an identity keystore.

2.1 Navigate to the directory and create a new directory by name security.

2.2 Open a command prompt (if not already open).

2.3 Change to the /securitydirectory.

2.4 Run the Java keytool-genkeycommand.

Use the information in Table 5 and Table 6 to supply the keytoolcommand arguments,

for example:

C:\Oracle\Middleware\jdk160_14_R27.6.5-32\bin\keytool.exegenkey v alias mykey keyalg RSA keysize 512

-dname "CN=localhost, OU=WeblogicWorkshop, O=Weblogic, C=US"

-keypass mykeypass

-validity 365-keystore my_identity.jks-storepass mystorepass

The key and certificate are generated and stored in a keystore.

Copy the my_identity.jksfile from /securityto the


Generate a Certificate Signing Request (CSR).

3.1 Open a command (if not already open).

3.2 Change to the /securitydirectory.

47


48/59

Solut ion: Conf igur ing SSL (cont inued)

3.3 Run the Java keytool-certrequtility. Use the information in Table 5 and Table 6 to

supply the keytoolcommand arguments, for example:

C:\Oracle\Middleware\jdk160_14_R27.6.5-32\bin\keytool.execertreq v alias mykey file my_cert_request.pem

-keypass mykeypass storepass mystorepass-keystore my_identity.jks

A CSR is generated.

Copy the my_cert_request.pemfile from /securityto the


Configure the keystores.

4.1 Make sure that AdminServerand server1are running.


Username: weblogic

Password: weblogic1

4.3 Navigate tobase_domain> Environment > Servers > server1> Configuration >Keystores. Lock the console.

4.4 On the Keystores page, specify the following properties:

Keystores: CustomIdentityandJavaStandardTrust

Custom Identity Keystore: my_identity.jks

Custom Identity Keystore Type: JKS

Custom Identity Keystore Passphrase: mystorepass

Java Standard Trust Keystore Passphrase: changeit4.5 Save the changes.

Configure SSL.

5.1 Go tobase_domain> Environment > Servers > server1> Configuration > SSL.5.2 On the SSL page, specify the following properties:

Identity and Trust Locations: Keystores

Private Key Alias: mykey

Private Key Passphrase: mykeypass

5.3 Save the changes.5.4 Navigate tobase_domain> Environment > Servers > server1> Configuration >

General. Verify that the check box next to SSL Listen Port Enabled is selected andthat the SSLListenPort is 7004.

48


49/59

Solut ion: Conf igur ing SSL (cont inued)

5.5 Activate the changes and restart the server1Managed Server.

Test the SSL setup.

6.1 Open a browser window and navigate to https://localhost:7004/helloworld.

You should see a warning, The certificate issued by your server is not signed by a

trusted authority, because in this lab, you use a self-signed digital certificate. Acceptthe certificate (the description may vary from one browser to another). Thehelloworld application should then open up in your browser.

49


50/59

Lab 9

Creating a Basic Cluster

= C:\studentWLSS103\work = C:\Oracle\Middleware\user_projects


Create a cluster of Managed Servers

Start clustered servers

In this lab, you create a cluster of three servers, server1, server2, and server3.

base_domain

myClustermachine1 machine2

server1 server2 server3

Figure 10: Cluster Architecture

50


51/59

Basic Instructions

1. If they are running, shut down the server1, server2, and server3Managed Servers.If it is not open, start a Web browser and navigate tohttp://localhost:7001/console. Log in

as:

Username: weblogic

Password: weblogic1

Create a new cluster with the following properties:

Name: myCluster

Multicast Address: 239.192.0.0(default)Multicast Port: For example, a unique number (Check with your instructor.)

Servers: server1, server2, server3

2. Start server1, server2, and server3. Watch each server as it tries to synchronizewith other servers in the cluster and as it finally joins the cluster. During startup of the

servers, if prompted, enter the following:

Username: weblogic

Password: weblogic1

51


52/59

Configuring Proxy Servers


Set up HTTPClusterServletin a WebLogic Server to proxy requests to a cluster

You have created your myClusterbut you still have not finished setting up the environment, sothe application requests are sent to different servers in the cluster. In this lab, you create a proxy

servers: HTTPClusterServletin a new WebLogic Server called proxyServer

52


53/59

Specifications

Figure 11 presents the cluster with the HTTPClusterServletproxy architecture.

base_domain

proxyServer (with

HTTPClusterServlet)

myCluster

machine1 machine2

server1 server2 server3

Figure 11: HTTPClusterServletProxy Architecture

53


54/59

Basic Instructions

1. Create the WebLogic proxy server with the following properties:

Server Name: proxyServer

Server Listen Address: localhost

Server Listen Port: 7009

Standalone Server: True

Start the proxy server.

2. Configure the HTTPClusterServletin /WEB-INF/web.xml. Add the

element that tells the servlet what servers are in the cluster. Add the elements that map HTTPClusterServletto any request for JSPs, HTML, and HTM pages plus anything that is not recognized.

3. Using /WEB-INF/weblogic.xml, set the proxy application as the default Webapplication for the proxy server.

4. Package the proxy application into proxyApp.warand copy it to

/applications. Deploy proxyApp.warto proxyServer.

5. Deploy the application browsestore. Open a Web browser and navigate to the

browsestoreapplication on the proxy server athttp://localhost:7009/browsestore.

Test the proxy server by browsing the application and checking the server consolewindows to see which server is handling the request. You should see different servershandling each request.

54
http://localhost:7009/browsestorehttp://localhost:7009/browsestore


55/59

Solut ion: Creat ing a B asic Cluster

In this practice, you create and start a cluster.

Create a cluster.

1.1 If already running, shut downserver1

,server2

andserver3

Managed Servers.

1.2 If it is not already open, start a Web browser and navigate tohttp://localhost:7001/console. Log in as:

Username: weblogic

Password: weblogic1

1.3 Navigate tobase_domain> Environment > Clusters. Lock the console, if necessary.1.4 Create a new cluster with the following properties:

Name: myCluster

Messaging Mode: MulticastMulticast Address: 239.192.0.0(default)

Multicast Port: For example, 7011 (Check with your instructor.)

Each student must use a unique port number.

Click OK.

1.5 Return to myClusterand click the Configuration > Servers tab.

1.6 Add the existing servers server1, server2and server3to the cluster.


1.8 Navigate tobase_domain

> Environment > Servers and view the list of servers.Note that server1, server2, and server3are now part of myCluster.

Start the clustered servers.

2.1 Using a command prompt, navigate to

/domains/base_domain/bin .

2.2 Start the server1server by entering the following in the prompt:

startManagedWebLogic.cmd server1

55
http://localhost:7001/consolehttp://localhost:7001/consolehttp://localhost:7001/console


56/59

Practice 9-1: Creat ing a Basic Cluster (con t inued)

2.3 If you are prompted, enter the following:

Username: weblogic

Password: weblogic1

2.4 Watch the server start up in the prompt window. At some point, you should see it start

listening for cluster announcement and waiting to synchronize with other servers in thecluster. Because the other servers have not started yet, there is nothing for it tosynchronize with yet.

2.5 Finally, you should see that it has successfully joined the cluster. You see something like:

2.6 Start the server2server by entering the following in the prompt window:

startManagedWebLogic.cmd server2

2.7 If you are prompted, enter the following:

Username: weblogic

Password: weblogic1

2.8 Watch the server start up in the prompt window. Because one of the servers in the cluster

has started up, server2synchronizes with server1and downloads the cluster JNDItree.

2.9 Finally, start the server3server, watch it synchronize with the other servers in the

cluster, and finallyjoin the cluster.

56


57/59

Solut ion: Conf igur ing Proxy Servers

In this practice, you create and configure a proxy server.

Set up the exercise.

1.1 Download the application browsestore.war

1.2 Deploy the application browsestore to myCluster.

Create the WebLogic proxy server.

2.1 If it is not already open, start a Web browser and navigate tohttp://localhost:7001/console.Log in as:

Username: weblogic

Password: weblogic1

2.2 Navigate tobase_domain> Environment > Servers. Lock the console, if necessary.2.3 Create a new server with the following properties:

Server Name: proxyServer

Server Listen Address: localhost

Server Listen Port: 7009

Standalone Server: True

Click Next.

2.4 Click Finish. Activate your changes.

2.5 Open a command prompt. Navigate to the/domains/base_domain/bin directory.

2.6 Start the proxyServerserver by entering the following in the prompt. (Use

weblogic/weblogic1as username/password.):

startManagedWebLogic.cmd proxyServer

Configure the HTTPClusterServlet.

3.1 Open /applications/proxyApp/WEB-INF/web.xml in a text editor.

57


58/59

Solut ion: Conf igur ing Proxy Servers (cont inued)

3.2 In the element, add the HTTPClusterServlet.

HttpClusterServlet

weblogic.servlet.proxy.HttpClusterServlet

3.3 After the element, add the element that tells theservlet what servers are in the cluster.

WebLogicCluster

localhost:7003|localhost:7005|localhost:7007

3.4 After , add the elements that map

HTTPClusterServlet to any request for JSPs, HTML, and HTM pages plus anythingthat is not recognized.

HttpClusterServlet

/

HttpClusterServlet

*.jsp

HttpClusterServlet

*.htm

HttpClusterServlet

*.html

Alternatively, you could copy and paste the elements from

Z:/exercise/web.txt.

3.5 Save and close the file.

Set HTTPClusterServletas the default Web application on the proxy server.4.1 Open /lab10/proxyApp/WEB-INF/weblogic.xml in a text editor.

4.2 Within the element, add the element, which

makes this the default Web application for proxyServer.

/

4.3 Save and close the file.

58


59/59

Solut ion: Conf igur ing Proxy Servers (cont inued)

Package the proxy application and deploy to the proxy server.

5.1 In the prompt window, navigate to /applications/proxyApp

and package the application using the following command:

C:\Oracle\Middleware\jdk160_14_R27.6.5-32\bin\jar cf

../proxyApp.war *

5.2 Deploy /applications/proxyApp.war to the proxyServer.

Activate your changes and start the application.

Test the WebLogic proxy server.

6.1 Restore the server1, server2, and server3server windows and arrange them

so that you can see all three simultaneously.

6.2 Open a Web browser and navigate to the browsestoreapplication that is

accessed through the proxy server athttp://localhost:7009/browsestore.

6.3 Check the server windows to see which server received the request.

6.4 Click the Browse Store link. Check the server windows to see which serverreceived the request.

6.5 Select a category and retrieve the items. Return to the home page, select anothercategory, and retrieve the items again. Check the server windows to see whichserver received the request. (Try open a different browser to access theapplication through the proxy server athttp://localhost:7009/browsestore.)
http://localhost:7009/browsestorehttp://localhost:7009/browsestorehttp://localhost:7009/browsestorehttp://localhost:7009/browsestorehttp://localhost:7009/browsestorehttp://localhost:7009/browsestorehttp://localhost:7009/browsestorehttp://localhost:7009/browsestorehttp://localhost:7009/browsestore

Wlsadmin Lab Guide

Documents

Transcript of Wlsadmin Lab Guide