oracle fusion middleware 11 g administration...

Oracle Fusion Middleware 11g: Administration Overview

Activity Guide

D76380GC10

Edition 1.0

September 2012

D79085O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Disclaimer

This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle.

The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free.

Restricted Rights Notice

If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTSThe U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

AuthorsBill BellShankar Raman

Technical Contributors and ReviewersMatthew SlingsbyJoe GreenwaldKevin TateDon BatesLisa ZhangPello SoleimanMarsha HancockHeike HundtSushil ShuklaKent RupiperNoah ArlissAl SaganichTJ PalazzoloDavid Mills

EditorsDaniel MilneAju Kumar Rashmi Rajagopal

Graphic DesignerMaheshwari Krishnamurthy

Publishers

Giri Venugopal Srividya Rameshkumar

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Oracle Fusion Middleware 11g: Administration Overview Table of Contents

i

Table of Contents

Practices for Lesson 1: Course Overview ................................................................................................ 1-1 Practices for Lesson 1 ............................................................................................................................. 1-2

Practices for Lesson 2: Fusion Middleware Products and Architecture ................................................. 2-1 Practices for Lesson 2 ............................................................................................................................. 2-2

Practices for Lesson 3: Fusion Middleware Repository .......................................................................... 3-1 Practices for Lesson 3 ............................................................................................................................. 3-2 Practice 3-1: Creating a Repository ......................................................................................................... 3-3 Practice 3-2: Backing Up the Database Installation and Instances ............................................................ 3-7

Practices for Lesson 4: Fusion Middleware Installation Overview .......................................................... 4-1 Practice Session 4 .................................................................................................................................. 4-2 Practice 4-1: Installing and Upgrading Oracle HTTP Server ...................................................................... 4-3 Practice 4-2: Installing the JRockit JDK and WebLogic Server .................................................................. 4-6 Practice 4-3: Installing and Upgrading Directory Services Components ..................................................... 4-9 Practice 4-4: Installing Oracle SOA Suite ................................................................................................. 4-12 Practice 4-5: Installing OAM and OIM ...................................................................................................... 4-14 Practice 4-6: Applying Patches for Oracle Identity and Access Management Products .............................. 4-16 Practice 4-7: Backing Up the Database and Fusion Middleware Installations ............................................. 4-20

Practices for Lesson 5: WebLogic Server Concepts ............................................................................... 5-1 Practice Session 5 .................................................................................................................................. 5-2 Practice 5-1: Creating a Domain .............................................................................................................. 5-3 Practice 5-2: Extending a Domain ............................................................................................................ 5-7

Practices for Lesson 6: Core WebLogic Server Administration and Monitoring ..................................... 6-1 Practices for Lesson 6 ............................................................................................................................. 6-2 Practice 6-1: Starting Servers and Creating Boot Identity.......................................................................... 6-3 Practice 6-2: Accessing the Administration Console ................................................................................. 6-6 Practice 6-3: Accessing Fusion Middleware Control ................................................................................. 6-11 Practice 6-4: Using WLST ....................................................................................................................... 6-24

Practices for Lesson 7: Node Manager .................................................................................................... 7-1 Practices for Lesson 7 ............................................................................................................................. 7-2 Practice 7-1: Configuring Node Manager ................................................................................................. 7-3 Practice 7-2: Starting Servers by Using FMW Control ............................................................................... 7-8

Practices for Lesson 8: Configuring Fusion Middleware Components ................................................... 8-1 Practice Session 8 .................................................................................................................................. 8-2 Practice 8-1: Configuring Oracle HTTP Server ......................................................................................... 8-3 Practice 8-2: Configuring Oracle Internet Directory and Oracle Directory Services Manager ...................... 8-13 Practice 8-3: Taking a Backup ................................................................................................................. 8-23

Practices for Lesson 9: Fusion Middleware Security ............................................................................... 9-1 Practices for Lesson 9 ............................................................................................................................. 9-2 Practice 9-1: Preparing the Identity Store for WLS Administrators ............................................................. 9-3 Practice 9-2: Preparing the Policy Store for WebLogic and FMW Components (Optional) .......................... 9-17 Practice 9-3: Taking a Backup ................................................................................................................. 9-21

Practices for Lesson 10: Fusion Middleware Backup and Recovery ....................................................... 10-1 Practices for Lesson 10 ........................................................................................................................... 10-2 Practice 10-1: Recovering from a Media Failure ....................................................................................... 10-3

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Oracle Fusion Middleware 11g: Administration Overview Table of Contents

ii

Practices for Lesson 11: High Availability ............................................................................................... 11-1 Practices for Lesson 11 ........................................................................................................................... 11-2

Practices for Lesson 12: Development to Production ............................................................................. 12-1 Practices for Lesson 12 ........................................................................................................................... 12-2 Practice 12-1: Cloning Oracle Fusion Middleware .................................................................................... 12-3

Practices for Lesson 13: Fusion Middleware Performance ..................................................................... 13-1 Practices for Lesson 13 ........................................................................................................................... 13-2 Practice 13-1: Creating a Work Manager ................................................................................................. 13-3 Practice 13-2: Tuning a Connection Pool ................................................................................................. 13-7 Practice 13-3: Tuning SOA Suite ............................................................................................................. 13-11

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 1: Course Overview

Chapter 1 - Page 1


Chapter 1

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 1 - Page 2

Practices for Lesson 1

Practices Overview There are no practices in lesson 1.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 2: Fusion Middleware Products and Architecture

Chapter 2 - Page 1


Chapter 2

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 2 - Page 2



Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 3: Fusion Middleware Repository

Chapter 3 - Page 1


Chapter 3

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 3 - Page 2


Practices Overview In these practices, you create the schemas necessary to configure Oracle SOA Suite, Oracle Internet Directory, and Oracle Identity Manager.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 3 - Page 3

Practice 3-1: Creating a Repository

Overview In this practice, you create the repository and schemas for Oracle Internet Directory, Oracle SOA Suite, and Oracle Identity Manager.

Assumptions Oracle Database 11g is already installed and a database with the name fmwdb is already created.

Tasks 1. Set up the database initialization parameters in fmwdb for loading the Fusion Middleware

schema.

a. Open a Terminal window and start the database listener and the database by running the 01_start_fmwdb.sh script in the /home/oracle/admin_scripts directory: $> cd /home/oracle/admin_scripts

$> ./01_start_fmwdb.sh

...

b. Use that Terminal window and run the oraenv utility. Enter fmwdb when prompted for ORACLE_SID. This sets up the environment variables for the fmwdb database: $> source oraenv

ORACLE_SID = [oracle]? fmwdb

The Oracle base for... is /u01/app/oracle

c. In the same Terminal window, invoke SQL*Plus and run the following SQL commands as a SYSDBA user to start the database and set up the fmwdb initialization parameters.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 3 - Page 4

Note: If you would prefer, after you have invoked SQL*Plus, you can run the init_fmwdb.sql script found in the /home/oracle/admin_scripts directory, rather than typing in and running each SQL command separately. To run the script, navigate to the /home/oracle/admin_scripts directory, access SQL*Plus, and enter: @init_fmwdb.sql

$> sqlplus / as sysdba

...

SQL> alter system set aq_tm_processes=1 scope=spfile;

System altered.

SQL> alter system set dml_locks=200 scope=spfile;

System altered.

SQL> alter system set job_queue_processes=10 scope=spfile;

System altered.

SQL> alter system set open_cursors=800 scope=spfile;

System altered.

SQL> alter system set session_max_open_files=50 scope=spfile;

System altered.

SQL> alter system set sessions=500 scope=spfile;

System altered.

SQL> alter system set processes=2500 scope=spfile;

System altered.

SQL> alter system set session_cached_cursors=500 scope=spfile;

System altered.

SQL> alter system set "_b_tree_bitmap_plans"=FALSE scope=spfile;

System altered.

SQL> alter system set sga_target=2G scope=spfile;

System altered.

SQL> alter system set pga_aggregate_target=1G scope=spfile;

System altered.

SQL> alter system set sga_max_size=2G scope=spfile;

System altered.

d. Exit SQL*Plus, then stop and start the fmwdb database with the stop_fmwdb.sh and 01_start_fmwdb.sh scripts in the /home/oracle/admin_scripts directory: SQL> exit

...

$> cd /home/oracle/admin_scripts

$> ./stop_fmwdb.sh

...


Note: Do not close the terminal window because you will be using it in the next step.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 3 - Page 5

2. Using RCU, configure the schemas in fmwdb.

a. In the same Terminal window, navigate to the /stage/rcu/rcuHome/bin folder and run RCU. $> cd /stage/rcu/rcuHome/bin

$> ./rcu

Use the guidelines in the following table to configure the Oracle Internet Directory schema:

Step Window/Page Description Task

a. Welcome Click Next.

b. Create Repository Select Create and click Next.

c. Database Connection Details Enter or select these values for the following fields:

• Database Type: Oracle Database

• Hostname: fmwhost1.example.com

• Port: 1521

• Service Name: fmwdb.example.com

• Username: sys

• Password: Welcome1

• Role: SYSDBA

Note: That is the numeral “one” at the end of the password and not the lowercase letter “L.” Then click Next.

d. Checking Global Prerequisites After the prerequisite check finishes, click OK.

e. Select Components Select Create a new Prefix.

Enter FMW in the prefix field.

In the Component table, click + to expand the Identity Management node. (Do not select the check box next to the node.)

Select:

• Oracle Internet Directory

• Oracle Identity Manager

• Oracle Access Manager

Note: When you select these components, RCU selects other required schema components:

• Metadata Services

• Audit Services

• SOA Infrastructure

• User Messaging Service

Click Next.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 3 - Page 6

Step Window/Page Description Task

f. Checking Component Prerequisites After the prerequisite check finishes, click OK.

g. Schema Passwords Select Use the same passwords for all schemas.

Enter and confirm the password of Welcome1.

Click Next.

h. Map Tablespaces Click Next.

i. Repository Creation Utility Click OK to confirm creating tablespaces.

j. Creating Tablespaces After the tablespaces have been created, click OK.

k. Summary Click Create.

l. Completion Summary Click Close.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 3 - Page 7

Practice 3-2: Backing Up the Database Installation and Instances

Overview In this practice, you perform a complete backup of the database installation and the database instances you have configured. This will enable you to restore the database to its starting point.

Tasks 1. Create a directory for storing backups.

a. In a Terminal window, create the backup directory under the stage directory: $> cd /stage

$> mkdir backup

2. Stop the fmwdb database instance along with the database listener and Database Control by using the supplied script.

a. In a Terminal window, change to the /home/oracle/admin_scripts directory and run the stop_fmdb.sh script: $> cd /home/oracle/admin_scripts

$> ./stop_fmwdb.sh

3. Take a complete backup of the installation and database instances by running the supplied script, and store the backup in the new /stage/backup directory.

a. Log in as the superuser (root). Then execute the backup.sh script from the /home/oracle/admin_scripts directory. Enter the practice session number (03 in this case) as a command option. This script creates a TAR file containing a backup of all files and directories under /u01/app, and places that TAR file in the /stage/backup directory. This script may take 10 to 15 minutes to complete. $> su

Password: oracle

#> ./backup.sh 03

Note: Because this script takes a long time to complete, you can start it and do something else while it runs, like going on a break, or listening to the next lecture. Check the script after a while, and when it completes, you can finish the rest of this practice.

b. List the files in the /stage/backup directory and notice the file that has the tarz extension. That file has the session number in its name. An example is shown here: #> ls /stage/backup

u01-bak-session-03.tarz

#>

4. After the backup is complete, start the database instances as the oracle user.

a. Log out of the superuser session. Then as the oracle user, change to the /home/oracle/admin_scripts directory. Use the 01_start_fmwdb.sh script to start the database instances.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 3 - Page 8

Note: Do NOT start the database as root! #> exit



Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 4: Fusion Middleware Installation Overview

Chapter 4 - Page 1


Chapter 4

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 2

Practice Session 4

Practices Overview In these practices, you install the Oracle Fusion Middleware products required for the rest of the practices. Some of the products need to be updated to version 11.1.1.5. In those cases, you initially install version 11.1.1.2 of the products, and then upgrade them to version 11.1.1.5. You will also apply any required patches to the installed components.

Important Note: All the products have already been installed, so practices 4-1 through 4-5 are not actually required before attempting the remainder of the practices. The course was set up this way so that if something goes wrong while doing the installation practices, you can revert to the preinstalled products and continue with the course.

Before starting the first installation practice (4-1), stop the database (if it is running) and rename the fmw directory under /u01/app/oracle/product:


$> ./stop_fmwdb.sh

...

$> cd /u01/app/oracle/product

$> mv fmw orig-fmw

After all the installation practices have been completed (4-1 through 4-5), you can use the products you installed. If something goes wrong during the installation process, or if you run out of time, delete the fmw directory you created, and rename the orig-fmw directory back to fmw.

Note: Practice 4-6 must be completed whether you do the first five practices yourself, or use the installation provided.

Environment Variable Directory Structure

ORACLE_BASE /u01/app/oracle

MW_HOME ORACLE_BASE/product/fmw

WEB_ORACLE_HOME MW_HOME/web

JAVA_HOME MW_HOME/jrockit-jdk

WL_HOME MW_HOME/wlserver_10.3

ORACLE_COMMON_HOME MW_HOME/oracle_common

IDM_ORACLE_HOME MW_HOME/idm SOA_ORACLE_HOME MW_HOME/soa

IAM_ORACLE_HOME MW_HOME/iam

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 3

Practice 4-1: Installing and Upgrading Oracle HTTP Server

Overview In this practice, you install Oracle HTTP Server 11.1.1.2 and upgrade it to Oracle HTTP Server 11.1.1.5.

Tasks 1. If you have not already done so, stop the database, and then rename the fmw directory

under /u01/app/oracle/product: $> cd /home/oracle/admin_scripts

$> ./stop_fmwdb.sh

...

$> cd /u01/app/oracle/product

$> mv fmw orig-fmw

2. Install Oracle HTTP Server 11.1.1.2. Oracle HTTP Server 11g is available in the Oracle Fusion Middleware Web Tier Utilities pack. The Web Tier Utilities installable is in /stage/web_11-1-1-2. The Web Tier installer installs both Oracle HTTP Server and Oracle Web Cache.

a. Open a Terminal window, and unset the ORACLE_HOME and ORACLE_SID environment variables. Then navigate to /stage/web_11-1-1-2/Disk1 and run the installer. $> unset ORACLE_HOME ORACLE_SID

$> cd /stage/web_11-1-1-2/Disk1

$> ./runInstaller

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 4

b. Use the guidelines in the following table to install the software:

Step Window/Page Description Choices or Values

a. Specify Oracle Inventory Directory

This screen appears when you install the first Oracle product. Because the Oracle database has already been installed, the screen may not appear. If it does appear, enter /u01/app/oraInventory and click Next. If it does not, just move to the next step.

b. Welcome Click Next.

c. Select Installation Type Select Install Software - Do Not Configure. Click Next.

d. Prerequisite Checks When all prerequisite checks are 100% successful, click Next.

e. Specify Installation Location Enter these values for the following fields:

• Oracle Middleware Home: /u01/app/oracle/product/fmw

• Oracle Home Directory: web

Then click Next.

f. Specify Security Updates Deselect “I wish to receive security updates via My Oracle Support.” (In your training environment, you do not want to associate the installations with a specific user.) Click Next.

In the dialog box that opens, click Yes.

g. Installation Summary Click Install.

h. Installation Progress Note the progress and successful completion of the installation. Click Next.

i. Installation Complete Click Finish.

3. Upgrade the installed Oracle Web Tier from 11.1.1.2 to 11.1.1.5. The Web Tier Utilities installable is in /stage/web_11-1-1-5. This upgrade is an example of using a Patch Set to upgrade a Fusion Middleware Product.

a. Open a Terminal window, and navigate to /stage/web_11-1-1-5/Disk1. When you are there, run the installer: $> cd /stage/web_11-1-1-5/Disk1

$> ./runInstaller

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 5




b. Specify Install Location Set the location where you installed Oracle Web Tier 11.1.1.2.

Enter these values for the following fields:


• Oracle Home Directory: web Then click Next.

c. Specify Security Updates Deselect “I wish to receive security updates via My Oracle Support.” (In your training environment, you do not want to associate the installations with a specific user.) Click Next.


d. Installation Summary Click Install.

e. Installation Progress Note the progress and successful completion of the Patch Set installation.

Click Next.

f. Installation Complete Click Finish.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 6

Practice 4-2: Installing the JRockit JDK and WebLogic Server

Overview In this practice, you install the JRockit JDK and WebLogic Server, which must be installed before installing the identity and access management components.

Tasks 1. Install the Oracle JRockit 64-bit JDK. It is in /stage/jrockit.

a. Open a Terminal window and navigate to /stage/jrockit. Ensure that the jrockit-jdk1.6.0_24-R28.1.3-4.0.1-linux-x64.bin file has executable permissions, and then run the executable file to install JRockit: $> cd /stage/jrockit

$> chmod +x jrockit-jdk1.6.0_24-R28.1.3-4.0.1-linux-x64.bin

$> ./jrockit-jdk1.6.0_24-R28.1.3-4.0.1-linux-x64.bin


Step Window/Page Description

Choices or Values


b. Product Installation Directory

Enter: /u01/app/oracle/product/fmw/jrockit-jdk

Click Next.

c. Optional Components Do not select any of the optional components.

Click Next.

d. Installation Complete Click Done.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 7

c. In the Terminal window, set the JAVA_HOME environment variable to point to the location where JRockit is installed, add the bin subdirectory in the JRockit installation to the PATH environment variable, and verify that the Java version is 64 bit: $> export JAVA_HOME=/u01/app/oracle/product/fmw/jrockit-jdk

$> export PATH=$JAVA_HOME/bin:$PATH

$> which java

/u01/app/oracle/product/fmw/jrockit-jdk/bin/java

$> java –version

java version "1.6.0_24"

Java(TM) SE Runtime Environment (build 1.6.0_24-b07)

Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1432-linux-x86_64, compiled mode)

2. Install Oracle WebLogic Server 10.3.5 by using the JRockit JDK that you just installed. The WebLogic Server generic installable is in /stage/wls.

a. In the same Terminal window where you set up the JAVA_HOME and PATH environment variables, navigate to the /stage/wls directory and invoke the WLS generic installer: $> cd /stage/wls

$> java –d64 –jar wls1035_generic.jar

b. Use the guidelines in the following table to install WebLogic Server:


Choices or Values


b. Middleware Home Directory

Select “Create a new Middleware Home.”

Enter /u01/app/oracle/product/fmw in the Middleware Home Directory field. Click Next.

In the Warning dialog box, click Yes to proceed with the installation.

c. Security Updates Deselect “I wish to receive security updates via My Oracle Support.” In the dialog box that opens, click Yes.

Click Next.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 8


Choices or Values

d. Email Address Not Specified

Click Yes in the Email Address Not Specified dialog box

.

Then click Yes in the “Are you sure” dialog box.

e. Connection Failed Finally, select “I wish to remain uninformed…” and click Continue.

f. Installation Type Select Typical and click Next.

g. JDK Selection Ensure that Oracle 1.6.0_24 is selected, and click Next.

h. Product Installation Directories

Leave the Product Installation Directories as they are and click Next.

• WebLogic Server: /u01/app/oracle/product/fmw/wlserver_10.3

• Oracle Coherence: /u01/app/oracle/product/fmw/coherence_3.6

i. Installation Summary

View the components that are to be installed, and click Next.

j. Installation Complete

After the installation is complete, deselect Run Quick Start and click Done.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 9

Practice 4-3: Installing and Upgrading Directory Services Components

Overview In this practice, you install the Directory Services components (OID/OVD) from the Oracle Identity Management 11.1.1.2 installable, and then upgrade the components to 11.1.1.5. Oracle recommends that you upgrade the components before configuring any runtime environments to minimize time and effort in the upgrade.

Tasks 1. Install the Oracle Identity Management components. The installable is in

/stage/idm_11-1-1-2.

a. Use the same Terminal window where you set up the JAVA_HOME and PATH environment variables. (If you have closed the window, follow the steps in the earlier practice to set those variables.) Navigate to the directory /stage/idm_11-1-1-2/Disk1, and invoke the installer: $> cd /stage/idm_11-1-1-2/Disk1

$> ./runInstaller

b. Use the guidelines in the following table to install the Directory Services components from the Oracle Identity Management installer:



b. Select Installation Type Select Install Software – Do Not Configure.

Click Next.

c. Prerequisite Checks When all prerequisite checks are 100% successful, click Next.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 10


d. Specify Installation Location Enter these values for the following fields:


• Oracle Home Directory: idm

Click Next.

e. Specify Security Updates Deselect “I wish to receive security updates via My Oracle Support.” Click Next.


f. Installation Summary View the applications selected for installation, and click Install.

g. Installation Progress When the progress bar reaches 100%, click Next.

h. OracleRoot.sh confirmation Open a new Terminal window, log in as root (superuser), and run the shell script indicated. $> cd /u01/app/oracle/product/fmw/idm

$> su

Password: oracle

#> ./oracleRoot.sh

#> exit

$>

Return to the dialog box, and click OK.

i. Installation Complete Click Finish.

2. Upgrade the Directory Services products from 11.1.1.2 to 11.1.1.5. The necessary installable is in /stage/idm_11-1-1-5.

a. In the same Terminal window where you set up the JAVA_HOME and PATH environment variables, navigate to /stage/idm_11-1-1-5/Disk1, and invoke the installer: $> cd /stage/idm_11-1-1-5/Disk1

$> ./runInstaller

O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 11

b. Use the guidelines in the following table to install the Directory Services components from the Oracle Identity Management installer:



b. Specify Installation Location Enter these values for the following fields:


• Oracle Home Directory: idm

Click Next.

c. Specify Security Updates Deselect “I wish to receive security updates via My Oracle Support.”

Click Next.


d. Installation Summary View the applications selected for installation, and click Install.

e. Installation Progress When the progress bar reaches 100%, click Next.

f. OracleRoot.sh confirmation Open a new Terminal window, log in as root (super user), and run the shell script indicated. Enter yes when asked about ports. $> cd /u01/app/oracle/product/fmw/idm

$> su

Password: oracle

#> ./oracleRoot.sh

Do you want to run oidRoot.sh to configure OID for privileged ports? (yes/no) yes

User selected for running OIDRoot.sh

/u01/app/oracle/product/fmw/idm

Finished root actions for OID

#> exit

$>

Return to the dialog box, and click OK.

g. Installation Complete Click Finish.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 12

Practice 4-4: Installing Oracle SOA Suite

Overview In this practice, you install Oracle SOA Suite 11.1.1.5.

Tasks 1. Install Oracle SOA Suite 11.1.1.5. Ensure that the SOA component is also installed under

the same Middleware Home directory where you installed other Fusion Middleware components, such as OHS, WLS, OID, and OVD. The installable is in /stage/soa.

a. In the same Terminal window where you set up the JAVA_HOME and PATH environment variables, change the path to /stage/soa/Disk1, and invoke the installer: $> cd /stage/soa/Disk1

$> ./runInstaller

...

Please specify JRE/JDK location ( Ex. /home/jre ), <location>/bin/java should exist:

/u01/app/oracle/product/fmw/jrockit-jdk

...

Note: Ignore the “WARN” message that appears.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 13

b. Use the guidelines in the following table to install the Oracle SOA components:



b. Install Software Updates Select Skip Software Updates.

Click Next.


d. Installation Location Enter these values for the following fields:


• Oracle Home Directory: soa

Click Next.

e. Application Server Select WebLogic Server and click Next.

f. Installation Summary Click Install.

g. Installation Progress When the progress bar reaches 100%, click Next.

h. Installation Complete Click Finish.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 14

Practice 4-5: Installing OAM and OIM

Overview In this practice, you install Oracle Access Manager and Oracle Identity Manager from the Oracle Identity and Access Management installable.

Tasks 1. Install Oracle Access Manager and Oracle Identity Manager 11.1.1.5 under the same

Middleware Home directory where you installed other Fusion Middleware components, such as OHS, WLS, OID, OVD and SOA. The necessary installable is in /stage/iam.

a. In the same Terminal window where you set up the JAVA_HOME and PATH environment variables, navigate to /stage/iam/Disk1, and invoke the installer. If you closed the Terminal window, first set up the variables: $> export MW_HOME=/u01/app/oracle/product/fmw

$> export JAVA_HOME=$MW_HOME/jrockit-jdk


Then navigate to the installer and run it: $> cd /stage/iam/Disk1

$> ./runInstaller –jreLoc $JAVA_HOME/jre

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 15

b. Use the guidelines in the following table to install Oracle Access Manager and Oracle Identity Manager:



b. Install Software Updates Select Skip Software Updates and click Next.


d. Installation Location Enter these values for the following fields:


• Oracle Home Directory: iam

Click Next.

e. Installation Summary Click Install.

f. Installation Progress When the progress bar reaches 100%, click Next.

g. Installation Complete Click Finish.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 16

Practice 4-6: Applying Patches for Oracle Identity and Access Management Products

Overview In this practice, you apply some interim patches (formerly known as Patch Set Exceptions or PSEs). These patches are required for the Identity and Access Management components to be properly configured.

For the purpose of this practice, the patches are found in /stage/fmw_patches/fa_idm_patches.

Identity and Access Management Product Oracle Home Patch Number

IDM Tools IAM_ORACLE_HOME 12995033

OAM 11g IAM_ORACLE_HOME 12989739

OIM IAM_ORACLE_HOME 12961473, 12418680

OID IDM_ORACLE_HOME 12937765

OVD-ODSM IDM_ORACLE_HOME 13031079

OVD IDM_ORACLE_HOME 13031196

OIF IDM_ORACLE_HOME 12968010

Tasks 1. Apply the IDM Tools patch found in

/stage/fmw_patches/fa_idm_patches/12995033.

a. Open a Terminal window, and set the ORACLE_HOME environment variable to $MW_HOME/iam. $> export MW_HOME=/u01/app/oracle/product/fmw

$> export ORACLE_HOME=$MW_HOME/iam

b. Navigate to /stage/fmw_patches/fa_idm_patches/12995033 and apply the patch. $> cd /stage/fmw_patches/fa_idm_patches/12995033

$> $ORACLE_HOME/OPatch/opatch apply

...

OPatch succeeded.

2. Apply the OAM11g patch in /stage/fmw_patches/fa_idm_patches/12989739.

a. In the same Terminal window (where ORACLE_HOME is set to $MW_HOME/iam), navigate to /stage/fmw_patches/fa_idm_patches/12989739 and apply the patch: $> cd /stage/fmw_patches/fa_idm_patches/12989739


...

OPatch succeeded.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 17

3. Apply the OIM patches in /stage/fmw_patches/fa_idm_patches/12961473 and /stage/fmw_patches/fa_idm_patches/12418680.

a. In the same Terminal window, navigate to /stage/fmw_patches/fa_idm_patches/12961473 and apply the patch: $> cd /stage/fmw_patches/fa_idm_patches/12961473


...

OPatch succeeded.

b. Navigate to /stage/fmw_patches/fa_idm_patches/12418680 and apply the patch: $> cd /stage/fmw_patches/fa_idm_patches/12418680


...

OPatch succeeded.

4. Apply the OID, OVD, and OIF patches from the corresponding subdirectories in /stage/fmw_patches/fa_idm_patches.

Note: When you are prompted with, “Is the local system ready for patching [y|n],” enter y.

a. In a Terminal window, change the ORACLE_HOME environment variable by setting it to $MW_HOME/idm: $> export MW_HOME=/u01/app/oracle/product/fmw

$> export ORACLE_HOME=$MW_HOME/idm

b. Navigate to /stage/fmw_patches/fa_idm_patches/12937765 and apply the patch: $> cd /stage/fmw_patches/fa_idm_patches/12937765


...

Is the local system ready for patching [y|n]

y

...

OPatch succeeded.

c. Navigate to /stage/fmw_patches/fa_idm_patches/13031079 and apply the patch: $> cd /stage/fmw_patches/fa_idm_patches/13031079


...

OPatch succeeded.

d. Navigate to /stage/fmw_patches/fa_idm_patches/13031196, and apply the patch: $> cd /stage/fmw_patches/fa_idm_patches/13031196


...

OPatch succeeded.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 18

e. Navigate to /stage/fmw_patches/fa_idm_patches/12968010 and apply the patch: $> cd /stage/fmw_patches/fa_idm_patches/12968010


...

OPatch succeeded.

5. Provision the OIM login modules under the WebLogic Server library directory. Some additional environment variables are necessary and must be added to the setDomainEnv.sh script of any WebLogic Server domain that contains OIM servers.

a. Using the Terminal window where the environment variable MW_HOME is still set, copy the OIMAuthenticator.jar, oimmbean.jar, oimsigmbean.jar and oimsignaturembean.jar files located in $MW_HOME/iam/server/loginmodule/wls to $MW_HOME/wlserver_10.3/server/lib/mbeantypes: $> cp $MW_HOME/iam/server/loginmodule/wls/*.jar $MW_HOME/wlserver_10.3/server/lib/mbeantypes/

b. Navigate to $MW_HOME/wlserver_10.3/server/lib/mbeantypes, and then use the chmod command to change the permissions for the files to 750 (rwx for the owner, r-x for the group, and --- for others): $> cd $MW_HOME/wlserver_10.3/server/lib/mbeantypes

$> chmod 750 *.jar

6. Create the wlfullclient.jar file. Oracle Identity Manager uses the wlfullclient.jar library for some of its operations. You must create this library file after installation and patching. Oracle recommends that you create it under $MW_HOME/wlserver_10.3/server/lib for all machines in the application tier of your environment.

a. In a Terminal window, set your JAVA_HOME environment variable, and ensure that JAVA_HOME/bin is in your PATH, and then navigate to $MW_HOME/wlserver_10.3/server/lib: $> export MW_HOME=/u01/app/oracle/product/fmw



$> cd $MW_HOME/wlserver_10.3/server/lib

b. Run the following command to create the wlfullclient.jar file: $> java -jar wljarbuilder.jar

...

Integrating jar <--(1)/(40377)/(96)//u01/app/oracle/product/fmw/modules/ com.bea.core.diagnostics.accessor_1.5.0.0.jar

Created new jar file: /u01/app/oracle/product/fmw/wlserver_10.3/server/lib/ wlfullclient.jar

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 19

7. There is a JAR file in the ORACLE_COMMON_HOME/modules directory that needs to be in the MW_HOME/modules directory. Create a symbolic link to that file so it can be accessed as if it were under MW_HOME.

a. In a Terminal window, navigate to the MW_HOME/modules directory. See if the JAR file is already there. If it is, skip to the next task. If not, continue with this task. $> cd /u01/app/oracle/product/fmw/modules

$> ls com.oracle.weblogic.sca.engine_1.2.0.0.jar

b. If the JAR file is not in the MW_HOME/modules directory, use the ln command with the -s option to create the symbolic link: $> cd /u01/app/oracle/product/fmw/modules

$> ln -s ../oracle_common/modules/

com.oracle.weblogic.sca.engine_1.2.0.0.jar .

Notes

• There is no space between the path and the file name. (The line breaks due to space limitations.) Do not forget the “.” at the end of the command.

• You could also copy the file into the MW_HOME/modules directory, but using a link is more efficient because with the link there is only one copy of the file, but it can be accessed in two ways.

8. There is another JAR file that might be missing. If it is missing, copy it to the correct location from /home/oracle/applications.

a. Open a Terminal window and navigate to /u01/app/oracle/product/fmw/oracle_common/soa/modules. List the files that start with “comm”. $> cd /u01/app/oracle/product/fmw/oracle_common/soa/modules

$> ls comm*

b. If the file commons-cli-1.1.jar is there, skip to the next task. If not, copy it from /home/oracle/applications: $> cp /home/oracle/applications/commons-cli-1.1.jar

commons-cli-1.1.jar

Note: Enter the command on one line. (It is on two lines here due to space limitations.)

9. Make sure that the /tmp directory is usable by all. In a Terminal window, change to the superuser, root, and run the chmod command.

Note: Do not stay logged in as root. Exit immediately, or close the Terminal window. $> su

Password: oracle

#> chmod -R 777 /tmp

#> exit

$>

Note: The -R option means recursive.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 4 - Page 20

Practice 4-7: Backing Up the Database and Fusion Middleware Installations

Overview In this practice, you perform a complete backup of the database and Fusion Middleware installations and the database instance that you have configured. This helps you in case you want to restore the machine to the starting point.

Tasks 1. Stop the fmwdb database instance along with the database listener, and the Database

Control.

a. In a Terminal window, navigate to $HOME/admin_scripts and run the stop_fmdb.sh script: $> cd $HOME/admin_scripts

$> ./stop_fmwdb.sh

2. Take a complete backup of the installation and database instances and store the backup in the /stage/backup directory.

a. In a Terminal window, log in as the superuser (root), and execute the backup.sh script from the /home/oracle/admin_scripts directory. Enter the practice session number (04 in this case) as the command option. This creates a backup of all files and directories under the /u01/app directory to the /stage/backup directory. This may take about 30 minutes to complete. $> su

Password: oracle

#> cd /home/oracle/admin_scripts

#> ./backup.sh 04

Note: Because this script takes a long time to complete, you can start it and do something else while it runs, like going on a break, or listening to the next lecture. Check the script after a while, and when it completes, you can finish the rest of this practice.

b. List the files in the /stage/backup directory and notice that a file is created with the tarz extension. The file has the session number in the name: #> ls /stage/backup

u01-bak-session-03.tarz u01-bak-session-04.tarz

c. Log out of the superuser session. #> exit

$>

Note: Or just close the Terminal window where you logged in as root.

3. After the backup is complete, start the database instance as the oracle user.

Note: Make sure that you are the oracle user (and not root) BEFORE you start the database!

a. As the oracle user, navigate to the /home/oracle/admin_scripts directory. Start the database by using the 01_start_fmwdb.sh script: $> cd /home/oracle/admin_scripts


Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 5: WebLogic Server Concepts

Chapter 5 - Page 1


Chapter 5

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 2

Practice Session 5

Practices Overview In these practices, you create a WebLogic Server domain by using the Configuration Wizard. You also extend that domain to support Oracle SOA Suite by using the Configuration Wizard.










Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 3

Practice 5-1: Creating a Domain

Overview In this practice, you create a WebLogic Server domain. After creating the domain, you start the administration server to see if the domain creation was successful.

Tasks 1. Create a domain by using the Configuration Wizard.

a. Start the database, if it is not already started. Open a Terminal window, navigate to /home/oracle/admin_scripts, and run the 01_start_fmwdb.sh script: $> cd /home/oracle/admin_scripts


b. In the Terminal window, navigate to <ORACLE_COMMON_HOME>/common/bin, set the PATH, and run the Configuration Wizard: $> cd /u01/app/oracle/product/fmw/oracle_common/common/bin

$> export JAVA_HOME=/u01/app/oracle/product/fmw/jrockit-jdk


$> echo $PATH

/u01/app/oracle/product/fmw/jrockit-jdk/bin:...

$> ./config.sh

Notes

• Make sure that the PATH is correct (starts with the bin directory of the JDK) before running the Configuration Wizard script.

• You must run the config.sh script under <ORACLE_COMMON_HOME>/common/bin and not the one under <WL_HOME>/common/bin.

c. Use the guidelines in the following table to create the domain:


a. Welcome Select “Create a new WebLogic domain” and click Next.

b. Select Domain Source Select “Generate a domain configured automatically to support the following products,” and then select the following products:

• Oracle Enterprise Manager

• Oracle JRF

Then click Next.

Notes

• Oracle JRF should be selected automatically.

• You may have to scroll to see all the sources.

• The source called Basic WebLogic Server Domain must be selected, so deselecting it is disabled.

c. Specify Domain Name and Enter these values for the following fields:

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 4


Location • Domain name: fmwdomain

• Domain location: /u01/app/oracle/admin/domains

• Application location: /u01/app/oracle/admin/domains/ applications

Note: There should be no spaces or line feeds in the paths. Click Next.

d. Configure Administrator User Name and Password

Enter these values for the following fields:

• Name: weblogic

• User password: Welcome1

• Confirm user password: Welcome1

• Description: This user is the default administrator.

Click Next.

e. Configure Server Start Mode and JDK

Under WebLogic Domain Startup Mode, select Production Mode.

Under JDK Selection, select Available JDKs and ensure that JRockit is selected. Click Next.

f. Select Optional Configuration Select Administration Server and “Managed Servers, Clusters, and Machines.” Then click Next.

g. Configure the Administration Server

Enter or select these values for the following fields:

• Name: AdminServer

• Listen address: All Local Addresses

• Listen port: 7001

• SSL listen port: (Disabled)

• SSL enabled: Deselected

Note: These should be the defaults.

Click Next.

h. Configure Managed Servers Click Next.

i. Configure Clusters Click Next.

j. Configure Machines Click the Unix Machine tab.

Click the Add button. Then, in the row, enter or select the following values:

• Name: ADMINHOST

• Post bind GID enabled: Deselected

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 5


• Post bind GID: nobody

• Post bind UID enabled: Deselected

• Post bind UID: nobody

• Node manager listen address: All Local Addresses

• Node manager listen port: 5556

Click Next.

k. Assign Servers to Machines Under Machine, select ADMINHOST. Then under Server, select AdminServer and click the right arrow button.

The Machine column should look like this:

Click Next.

l. Configuration Summary Click Create.

m. Creating Domain When the progress bar reaches 100%, click Done.

d. To ensure that the domain and administration server were successfully created, start the administration server. Navigate to the bin directory under the domain directory and run the start script startWebLogic.sh. When prompted for the username, enter weblogic. When prompted for the password, enter Welcome1:

$> cd /u01/app/oracle/admin/domains/fmwdomain/bin

$> ./startWebLogic.sh

...

Enter username to boot WebLogic server: weblogic

Enter password to boot WebLogic server: Welcome1

...

Note: The password does not display.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 6

e. Messages will appear in the window. When the server successfully completes its startup process, it writes the following message to the window: <Server started in RUNNING mode>

Note: Ignore any warnings or errors.

f. After the server has successfully started, shut it down. In a new Terminal window, navigate to the domain’s bin directory and run the stopWebLogic.sh script. When prompted for a username, enter weblogic. When prompted for the password, enter Welcome1: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin

$> ./stopWebLogic.sh

...

Please enter your username: weblogic

Please enter your password: Welcome1

...

Note: You will see that the server shuts down in the window in which it was running.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 7

Practice 5-2: Extending a Domain

Overview In this practice, you extend the domain created in the previous practice to include Oracle SOA Suite. After extending the domain, you start the administration server and a managed server to see if the domain extension was successful.

Tasks 1. Extend the domain to include Oracle SOA Suite.

a. If you did not stop the administration server in the previous practice, do so now.

b. In a new Terminal window, navigate to <ORACLE_COMMON_HOME>/common/bin, set the PATH, and run the Configuration Wizard: $> cd /u01/app/oracle/product/fmw/oracle_common/common/bin

$> export JAVA_HOME=/u01/app/oracle/product/fmw/jrockit-jdk


$> echo $PATH

/u01/app/oracle/product/fmw/jrockit-jdk/bin:...

$> ./config.sh

c. Use the guidelines in the following table to install the software:


Choices or Values

a. Welcome Select “Extend an existing WebLogic domain.” Click Next.

b. Select a WebLogic Domain Directory

Expand the nodes in the hierarchy to select /u01/app/oracle/admin/domains/ fmwdomain. Note: Notice that the icon for this directory looks different from the others. The wizard recognizes it as a domain directory. Click Next.

c. Select Extension Source Select “Extend my domain automatically to support the following products,” and then select Oracle SOA Suite. Notes

• When you select Oracle SOA Suite, Oracle WSM Policy Manager is automatically selected.

• Make sure that you select the correct source. Do not select “Oracle SOA Suite for developers.”

• Sources already in the domain will be preselected, and deselecting them is disabled.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 8


Choices or Values

Click Next.

d. Configure JDBC Component Schema

Select all check boxes to the left of the table.

Then enter these values for the following fields:

• DBMS/Service: fmwdb.example.com

• Host Name: fmwhost1.example.com

• Schema Password: Welcome1

Note: Any field not listed above should retain its default value (Vendor: Oracle; Driver: *Oracle’s Driver (Thin) for Service Connections…; Port: 1521).

Next, deselect all check boxes.

Select one check box at a time and change the Schema Owner from DEV_whatever to FMW_whatever for each source. For example, change DEV_SOAINFRA to FMW_SOAINFRA. After changing a field, deselect the schema before moving on to the next one.

When you have finished, the screen looks like the image shown in the next row. Click Next.

e. Test JDBC Component Schema

Make sure that all tests complete successfully. (There is a green check mark in each Status column.) Click Next.

f. Select Optional Configuration

Select:

• JMS Distributed Destination

• “Managed Servers, Clusters and Machines”

• JMS File Store.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 9


Choices or Values

Click Next.

g. Select JMS Distributed Destination Type

Ensure that all the JMS System Resources listed are Uniform Distributed Destinations (UDD). If any are not, select UDD from their drop-down list.

Click Next.

h. Override Warning Click OK in the dialog box.

i. Configure Managed Servers

Rename soa_server1 to wls_soa1. Leave its “Listen address” as All Local Addresses. Leave its “Listen port” at 8001.

Click Next.

j. Configure Clusters Click the Add button. In the new row, enter or select the following values in the fields:

• Name: cluster_soa

• Cluster messaging mode: unicast

• Cluster address: fmwhost1.example.com:8001

Click Next.

k. Assign Servers to Clusters Under Cluster, select cluster_soa. Then under Server, select wls_soa1 and click the right-arrow button.

When you are finished, the Cluster column should look like this:

Click Next.

l. Configure Machines First, under the Machine tab, if there is a machine listed, select it and click the Delete button.

Click the Unix Machine tab and ensure that the ADMINHOST machine is displayed. Ensure that the “Node manager listen address” is All Local Addresses and the “Node manager listen port” is 5556.

Do not add any other machines. Click Next.

m. Assign Servers to Machines

In the Machine column, select ADMINHOST.

Then in the Server column, select wls_soa1 and click the right-arrow button.

When you have finished, the Machine column should look like this:

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 10


Choices or Values

Click Next.

n. Configure JMS File Stores Notes

• Do not change the name of any of the JMS file stores.

• The subdirectory name itself is correct, so do not accidentally delete it. In the Directory field, move the cursor to the left, and insert the path to the directory. This will help prevent typos.

• All of the file stores have the same path to their subdirectories; take advantage of copy and paste.

• Leave the “Synchronous write policy” field blank. Update the Directory for each of the file stores as shown in the table.

Then click Next.

Name Directory

UMSJMSFileStore_auto_1 /u01/app/oracle/admin/domains/

cluster_soa/jms/UMSJMSFileStore_auto_1

BPMJMSFileStore_auto_1 /u01/app/oracle/admin/domains/

cluster_soa/jms/BPMJMSFileStore_auto_1

SOAJMSFileStore_auto_1 /u01/app/oracle/admin/domains/

cluster_soa/jms/SOAJMSFileStore_auto_1

o. Configuration Summary Click Extend.

p. Extending Domain When the progress bar reaches 100%, click Done.

d. To ensure that the domain was extended successfully, start the administration server and the new managed server. In a Terminal window, navigate to the bin directory under the domain directory, and run the start script startWebLogic.sh. When prompted for the username, enter weblogic. When prompted for the password, enter Welcome1:



...


Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 11


...

<Server started in RUNNING mode>

Notes

• The password does not display.

• Ignore any warnings or errors.

• Wait for the “RUNNING mode” message before continuing.

e. In a different Terminal window, navigate to the bin directory under the domain directory and run the managed server start script startManagedWebLogic.sh. This script takes two parameters: the managed server name and the URL of the administration server. The second parameter, if not entered, defaults to the local host and port 7001, so it can be omitted with our domain. When prompted for the username, enter weblogic. When prompted for the password, enter Welcome1: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin

$> ./startManagedWebLogic.sh wls_soa1

...



...


Notes


• Ignore any warnings or errors.

• Wait for the “RUNNING mode” message before continuing. It can take the SOA server a while to completely come up.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 5 - Page 12

f. After both servers have successfully started, shut them down by using the stopManagedWebLogic.sh and stopWebLogic.sh scripts in the domain’s bin directory. First, shut down the managed server. After the managed server has shut down, shut down the administration server. Wait for the first script to complete before running the second script: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin

$> ./stopManagedWebLogic.sh wls_soa1

...



...



...



...

Notes

• The passwords do not display.

• You will see that each server has been shut down in the window in which it was running.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 6: Core WebLogic Server Administration and Monitoring

Chapter 6 - Page 1


Chapter 6

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 2


Practices Overview In these practices, you start WebLogic Server instances by using start scripts. You also access the WebLogic Server Administration Console and Fusion Middleware Control. Finally, you get into the WebLogic Scripting Tool environment.










Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 3

Practice 6-1: Starting Servers and Creating Boot Identity

Overview In this practice, you start the administration server, create a boot identity file, stop the administration server, and restart it.

Tasks 1. Start the administration server, if it is not already running.

a. In a Terminal window, navigate to the bin directory under the domain directory, /u01/app/oracle/admin/domains/fmwdomain/bin, and run the script to start the administration server: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin


b. When prompted for the username, enter weblogic. When prompted for the password, enter Welcome1:

...




c. Messages will appear in the window. When the server successfully completes its startup process, it writes the following message to the window: <Server started in RUNNING mode>

Notes

• Ignore any warnings or errors displayed.

• If you close the window in which the server is running, you kill the server. Minimize the window, if you want.

2. Create a boot identity file.

a. Open a new Terminal window and navigate to the AdminServer directory in the domain: $> cd /u01/app/oracle/admin/domains/fmwdomain

$> cd servers/AdminServer

b. Create the security subdirectory under the AdminServer directory: $> mkdir security

c. Create a text file in this security directory called boot.properties and edit it. In this example, the gedit text editor is used. Use the editor of your choice; ensure that the file is saved as a text file: $> cd security

$> gedit --new-document boot.properties

Note: If there are any gedit warnings about “wrong permissions,” ignore them.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 4

d. Add the following two lines to the file and save it. Close the text editor. username=weblogic

password=Welcome1

3. Stop the administration server and restart it. Observe the server’s use of the boot identity

file.

a. In a new Terminal window, navigate to the bin directory under the domain directory, /u01/app/oracle/admin/fmwdomain/aserver/fmwdomain/bin, and run the script to stop the administration server: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin


Notes

• Notice that the script uses the WebLogic Scripting Tool (WLST). When the script finishes, if you look at the Terminal window in which the administration server was running, you will also notice that it has been shut down.

• You can also stop the server by pressing Ctrl + C in the window in which it is running. Using the stop script, although it does a “forced shutdown,” is a more controlled way to shut down the server.

b. In a Terminal window, navigate to the bin directory under the domain directory, and once again run the script to start the administration server: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin


Note: This time you are not prompted for the username and password.

c. Messages will appear in the window. When the server successfully completes its startup process, it writes the following message to the window: <Server started in RUNNING mode>

Notes

• If you look through the messages, you can see the message about storing the boot identity: <Storing boot identity in the file: ...>. It was at this point that the server found the boot.properties file, used the credentials in it, and because those credentials were valid, encrypted the credentials and copied over the plain text in the file.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 5

• You may have noticed that the stop script you used earlier did not prompt you for the username and password, as it did before. That script can also use the boot.properties file. It, however, does not encrypt the username and password, as the start script does.

d. Leave the administration server running for the next practice.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 6

Practice 6-2: Accessing the Administration Console

Overview In this practice, you access the WebLogic Server Administration Console and use some of its functionality.

Tasks 1. Before using the web browser, set it so it does not use the proxy for your local machine.

a. Open a web browser. (Use the Web Browser icon in the panel, which opens Mozilla Firefox.)

b. In the Firefox menu, select Edit > Preferences.

c. At the top, select Advanced.

d. Click the Network tab.

e. Click the Settings button.

f. Ensure that “Manual proxy configuration” is selected.

g. In the “No Proxy for” field, do not delete anything already there. Move the cursor to the end of the URLs and enter a “,” followed by: fmwhost1.example.com: ,fmwhost1.example.com

h. Click OK.

i. Click Close.

2. Access the WebLogic Server Administration Console.

a. In the web browser, enter the URL for the Administration Console: http://adminhost:adminport/console. In your domain, that is: http://fmwhost1.example.com:7001/console

b. When the Welcome (login) screen appears, enter weblogic for the Username and

Welcome1 for the Password, and click the Login button.

c. Look at the layout of the Administration Console. Top left is the Change Center. Below

that is the Domain Structure (the hierarchy of domain resources). The large area to the right displays information about the element selected in the Domain Structure.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 7

3. Use the Administration Console to make a change to the logging configuration of the administration server. a. In the Change Center, click the Lock & Edit button.

b. In the Domain Structure, expand Environment (click the “+” sign), then select Servers.

c. On the right, in the servers table, select AdminServer in the Name column.

d. When the “Settings for AdminServer” displays, select the Logging back tab and the

General front tab.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 8

e. Scroll down to find the “Rotation file size” field. Enter 7500. Then click the Save button.

Note: Notice the message: “Settings updated successfully.”

f. In the Change Center, click Activate Changes.

Notes

• Notice the message: “All changes have been activated. No restarts are necessary.” Also notice that the configuration is no longer locked.

• This change occurred without having to restart the affected server. Many configuration changes can be completed on a running server without a server restart.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 9

4. Use the Administration Console to make a change to the configuration, so that if a secure connection is used between Node Manager and the servers, the use of demonstration certificates will be allowed.

a. In the Change Center, click the Lock & Edit button.

b. In the Domain Structure, expand Environment (click the “+” sign), then select Servers.

c. On the right, in the servers table, select AdminServer in the Name column.

d. When the “Settings for AdminServer” appears, click the Configuration back tab and the SSL front tab.

e. Scroll down and click the Advanced link.

f. Use the drop-down list to set Hostname Verification to None.

g. Then click the Save button.

Note: Notice the message: “Settings updated successfully.”

h. Repeat these steps to change the Hostname Verification of the other server, wls_soa1. (Select the wls_soa1 in the Servers table, click the tabs Configuration > SSL, click Advanced, select None from the Hostname Verification drop-down list, click Save).

i. When both the servers have been altered, in the Change Center, click Activate Changes.

Note: Notice the message that the changes have been activated, but one item must be restarted for the changes to take effect. A change to Hostname Verification only takes effect after a server restart. The administration server is the only server currently running, so it is the only one that must be restarted. j. Log out of the Administration Console by clicking Log Out.

k. Stop and restart the administration server. To stop the server, you can use the stop

script, stopWebLogic.sh, or just press Ctrl + C in the window in which it is running. After the administration server is shut down, restart it by using the start script, startWebLogic.sh, as before.

Note: Wait for the <Server started in RUNNING mode> message in the Terminal window before continuing.

5. Use the monitoring capability of the Administration Console.

a. Access and log in to the WebLogic Server Administration Console, as before.

Note: The URL is: http://fmwhost1.example.com:7001/console. The username / password is: weblogic / Welcome1.

b. Select the only server currently running, the administration server, by using the Domain Structure area. Expand Environment, select Servers, and then select AdminServer in the Servers table.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 10

c. When the “Settings for AdminServer” appears, click the Monitoring back tab and the Performance front tab.

d. Scroll down to view performance data on the virtual machine in which this server is

running. See if you can answer the following questions:

• What is the current heap size?

• What percentage of the heap is free?

• What is the maximum heap size?

• How much time has the virtual machine spent on garbage collection (GC) since it started?

Note: The WebLogic Server Administration Console has many, many other monitoring capabilities. This is just a small example.

6. Log out of the Administration Console by clicking Log Out.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 11

Practice 6-3: Accessing Fusion Middleware Control

Overview In this practice, you access Enterprise Manager Fusion Middleware Control and use some of its functionality. You use it to create a new managed server, deploy a Java Enterprise Edition application, and deploy a SOA Composite application

Tasks 1. Access Fusion Middleware Control.

a. Open a web browser and enter the URL for Fusion Middleware Control: http://adminhost:adminport/em In your domain, that is: http://fmwhost1.example.com:7001/em

b. When the login screen appears, enter weblogic for the User Name and Welcome1

for the Password, and click the Login button.

c. If presented with the Accessibility Preference dialog box, select “Do not show me these

options again,” and click Continue.

d. Look at the layout of Fusion Middleware Control. On the left is the Target Navigation Pane. Here you expand and select elements of the farm. Above the Target Navigation Pane is the Farm menu. The Content Pane is the large area to the right which displays information about the element selected in the Target Navigation Pane.

2. Create a new managed server. a. Above the Target Navigation Pane, use the Farm menu to select Create/Delete

Components.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 12

b. Click the Create drop-down list and select WebLogic Server.

c. In the Name field, enter demoserver1. In the Listen Port field, enter 9009. Select the

radio button “Select existing WebLogic Machine,” and click next to ADMINHOST in the table. Then click the Create button.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 13

d. When the Confirmation dialog box indicates that the server “has been successfully created,” click the Close button.

e. The new managed server is displayed in the table.

f. Although a managed server can be created by using Fusion Middleware Control, the

Administration Console (or WLST) is used to configure it. Select the new server, demoserver1 in the Target Navigation Pane (under WebLogic Domain > fmwdomain). Use the WebLogic Server menu to select WebLogic Server Administration Console. Log in with weblogic / Welcome1.

Note: It would be possible to configure the server by using the System MBean Browser of Fusion Middleware Control, but most people find it easier to use the administration console.

O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 14

g. In the Administration Console, in the Domain Structure area, expand Environment, and then select Servers. In the servers table, select demoserver1. Under the Configuration back tab, the General front tab, notice the properties set when the server was created. The Name is demoserver1, the Machine is ADMINHOST, and the Listen Port is 9009.

h. Like you did for the other servers, you want to set the Hostname Verification to None

for demoserver1. First, in the Change Center, click Lock & Edit. Then select demoserver1 in the Servers table, click the tabs Configuration > SSL, click Advanced, select None from the Hostname Verification drop-down list, and click Save. Then, in the Change Center, click Activate Changes.

3. Start the new managed server.

a. Open a new Terminal window. Navigate to the bin directory under the domain directory, /u01/app/oracle/admin/domains/fmwdomain/bin, and run the script to start the managed server named demoserver1: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin

$> ./startManagedWebLogic.sh demoserver1

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 15

b. When prompted for the username, enter weblogic. When prompted for the password, enter Welcome1:

...



Notes


• The username and password must be entered at the prompts because you did not create a boot.properties file for this server.

c. Messages will appear in the window. When the managed server successfully completes its startup process, it writes the following message to the window: <Server started in RUNNING mode>

Note: Ignore any warnings or errors displayed.

d. Wait for the managed server to successfully complete its startup process before continuing.

4. Use Fusion Middleware Control to monitor a server.

a. If you closed the web browser, open a new one, enter the URL of http://fmwhost1.example.com:7001/em, and log in with weblogic and Welcome1.

b. Notice on the farm home page that the administration server and the managed server demoserver1 are up and running.

c. Select the demoserver1 server (either in the Fusion Middleware table, or by using the

Target Navigation Pane).

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 16

d. Notice the information about the server: the server’s State, Health, CPU Usage, Heap Usage, and so on. If the “Response and Load” graph does not show any data, wait a few minutes, and then click the refresh button at the top right (circling arrows).

5. Use Fusion Middleware Control to deploy a Java Platform, Enterprise Edition application to

WebLogic Server. a. In the Target Navigation Pane, select demoserver1 (under WebLogic Domain >

fmwdomain).

b. Below the server name in the Content Pane, use the WebLogic Server menu to select Application Deployment > Deploy.

c. On the Select Archive page, select “Archive is on the machine where this web browser

is running.” Then click the Browse button next to that field.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 17

d. Use the File Upload window to browse to /home/oracle/applications. Select the benefits.war file, and click the Open button. This fills in the path and the file name in the field. Then click Next.

e. A message window displays that the file is being uploaded. (This window may appear

and close quickly.) f. On the Select Target screen, ensure that demoserver1 is selected. Click Next.

g. On the Application Attributes screen, leave all the defaults. Ensure that the context root, under “Context Root of Web Modules,” is /benefits. If it is not, change it. Then click Next.

h. On the Deployment Settings screen, click Deploy.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 18

i. In the pop-up window, wait for the message that the deployment succeeded. Then click the Close button.

j. Back on the server home page, the new application, benefits, should display in the

Application Deployments table as up and running.

k. To verify that the application is running and servicing requests, in a web browser, enter

the URL to access the application on the server demoserver1: http://fmwhost1.example.com:9009/benefits

l. Use this very simple web application for a few minutes.

6. Use Fusion Middleware Control to monitor an application.

a. Open a new web browser (or a new tab), and log back in to Fusion Middleware Control. (Enter the URL http://fmwhost1.example.com:7001/em, and log in with weblogic and Welcome1.)

b. In the Target Navigation Pane, expand Application Deployments. Then select benefits (demoserver1).

c. Notice the general state of the application in the Summary area

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 19

d. Also look at the Response and Load graph.

e. Look around at the other information available on the application home page. Then,

use the Application Deployment menu to select Performance Summary.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 20

f. Notice the graphs displayed. Other metrics can be shown, if desired, by using the Show Metric Palette button. (Do not do that now.)

7. Use Fusion Middleware Control to deploy and test a SOA Composite application.

a. First, start the wls_soa1 SOA Server. Open a new Terminal window. Navigate to the bin directory under the domain directory, and run the script to start the managed server named wls_soa1. When prompted for the username, enter weblogic. When prompted for the password, enter Welcome1: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin

$> ./startManagedWebLogic.sh wls_soa1

...



...


Notes


• Ignore any warnings or errors displayed.

• You may notice some <Cluster> messages, because this server is in a cluster.

b. Wait for the managed server to successfully complete its startup process before continuing.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 21

c. In Fusion Middleware Control, in the Target Navigation Pane, expand SOA, and then select soa-infra.

d. On the “soa-infra” home page, from the SOA Infrastructure menu, select SOA

Deployment > Deploy.

e. On the Select Archive page, select “Archive is on the machine where this web browser

is running.” Then click the Browse button next to that field.

f. Use the File Upload window to browse to /home/oracle/applications. Select the sca_HelloWorldComposite_rev1.0.jar file, and click the Open button. This fills in the path and the file name in the field. Then click Next.

g. On the Select Target page, the server or cluster is selected (based on the context in

which the wizard was launched). In this domain, the cluster called cluster_soa is

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 22

selected. Use the drop-down list to select the SOA Partition. (In this domain, the only partition is called default.) Then click Next.

h. On the Confirmation page, click Deploy.

i. A window appears indicating that the application is being deployed. (It may open and

close quickly.) Then if the deployment is successful, a confirmation message appears. Click the “X” at the top right to close the message:

j. In the Target Navigation Pane, the new SOA Composite application now appears

under the default partition.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 23

k. Select the SOA Composite called HelloWorldComposite. Then, above the Content Pane, click the Test button.

l. On the Test Web Service screen, scroll down to the Input Arguments area. Expand it, if

needed. In the Value field, enter your name.

m. After your name is entered, scroll up and click the Test Web Service button.

n. Scroll down to view the response from the web service request on the Response tab.

8. Log out of Fusion Middleware Control by clicking the Log Out button. Close the web

browser.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 24

Practice 6-4: Using WLST

Overview In this practice, you access the WebLogic Scripting Tool (WLST), run some basic commands in interactive mode, and run some supplied WLST scripts.

Tasks 1. Access the WebLogic Scripting Tool and run some commands in interactive mode.

a. In a Terminal window, navigate to <ORACLE_COMMON_HOME>/common/bin and run the wlst.sh script: $> cd /u01/app/oracle/product/fmw/oracle_common/common/bin

$> ./wlst.sh

...

Your environment has been set.

...

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

wls:/offline>

Note: In the Terminal window, notice that the wlst.sh script set the PATH and the CLASSPATH. (That output is not shown above.)

2. Connect to the running administration server.

a. At the WLST prompt, enter the connect() command. The first parameter is the username, the second parameter is the password, and the third parameter is the URL to the administration server.

Notes

• Enter the command all on one line. It is on two lines here due to space limitations.

• Notice that all parameters must be delimited (by either single or double quotation marks), and that the parameters are separated by commas.

• Notice the protocol of t3 used in the URL of the administration server. This is a proprietary WebLogic Server protocol and is much faster than HTML.

wls:/offline> connect('weblogic', 'Welcome1',

't3://fmwhost1.example.com:7001')

Connecting to t3://fmwhost1.example.com:7001

with userid weblogic ...

Successfully connected to Admin Server 'AdminServer'

that belongs to domain 'fmwdomain'.

...

wls:/fmwdomain/serverConfig>

Note: Ignore the warning about an “insecure protocol.”

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 25

3. Run some WLST commands in interactive mode (one at a time). The commands shown reverse the change to the administration server’s log configuration you made in an earlier practice.

a. Navigate to Servers, and then AdminServer: wls:/fmwdomain/serverConfig> cd('Servers')

wls:/fmwdomain/serverConfig/Servers> cd('AdminServer')

Note: All commands and parameters are case-sensitive.

b. Next, navigate to the Log area of the AdminServer: wls:/fmwdomain/serverConfig/Servers/AdminServer> cd('Log')

wls:/fmwdomain/serverConfig/Servers/AdminServer/Log>

cd('AdminServer')

Note: Because of space limitations, the command is shown below the prompt.

c. View the “Rotation file size” that you changed earlier, which now has the value of 7500. This attribute is called FileMinSize here. wls:/...> ls()

...

-r-- FileMinSize 7500

...

Notes

• Because of the length of the WLST prompts and space limitations, when a prompt is long, it will be abbreviated.

• Notice that FileMinSize is read-only (the “r”).

d. You have been looking at domain configuration attributes through the read-only MBean hierarchy. To make changes, you must first access the editable MBean hierarchy by using the edit() command: wls:/...> edit()

wls:/fmwdomain/edit>

Note: Notice that WLST changes the prompt, and moves you to the root of the edit tree.

e. Navigate back to the log location of AdminServer (however, this time, you are there in the “edit tree”): wls:/fmwdomain/edit>

cd('/Servers/AdminServer/Log/AdminServer')

Note: Because of space limitations, the command is shown below the prompt.

f. Lock the configuration by starting an edit session. Notice the prompt changes again, this time to indicate that the configuration is locked: wls:/.../edit/...> startEdit()

wls:/.../edit/... !>

g. Change the rotation file size back to its original value of 5000. Then activate the change: wls:/.../edit/... !> set('FileMinSize', '5000')

wls:/.../edit/... !> activate()

Activating all your changes, this may take a while ...

The edit lock associated with this edit session is released

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 26

once the activation is completed.

Activation completed

wls:/.../edit/...>

Note: The prompt changes again (the “!” is removed) to show that the configuration lock is released.

h. Check to see whether the change occurred: wls:/.../edit/...> ls()

...

-rw- FileMinSize 5000

...

4. Run some more commands in WLST interactive mode. Here you enter commands to navigate to the configuration of one of the managed servers. You change the “Failure Action” of the demoserver1 server. This attribute can enable the automatic forced shutdown of a server when it goes into a failed state (the server self-health monitoring detects fatal failures and marks the server as failed). After the change is made, before you activate it, you undo the change.

a. You are still in the edit tree, but the configuration is no longer locked. Lock the configuration: wls:/.../edit/...> startEdit()

wls:/.../edit/... !>

b. Navigate to the managed server, demoserver1: wls:/.../edit/... !> cd('/Servers/demoserver1')

c. Get into the overload protection attributes of this server: wls:/.../edit/... !> cd('OverloadProtection/demoserver1')

d. See what the current value is for the FailureAction attribute. (The default is no-action, which means do nothing when the server goes into a failed state.) wls:/.../edit/... !> ls()

...

-rw- FailureAction no-action

...

e. Set the value of FailureAction to force-shutdown: wls:/.../edit/... !> set('FailureAction', 'force-shutdown')

f. Verify the change: wls:/.../edit/... !> ls()

...

-rw- FailureAction force-shutdown

...

Note: Do not activate.

g. Before you activate the change, the system architect tells you that it has been decided that this change should not be made. So, rather than enter the activate() command to activate the change and release the configuration lock, enter the stopEdit() command. The stopEdit() command stops the current edit session, releases the configuration lock, and discards any changes made. When asked if you are sure, enter “y”:

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 27

wls:/.../edit/... !> stopEdit()

Sure you would like to stop your edit session? (y/n) y

Edit session has been stopped successfully.

wls:/.../edit/...>

h. Verify that the change did not occur: wls:/.../edit/...> ls()

...

-rw- FailureAction no-action

...

i. Enter the command to exit WLST: wls:/.../edit/...> exit()

Exiting WebLogic Scripting Tool.

$>

5. Use some Fusion Middleware custom WLST commands.

a. To use custom WLST commands provided by SOA Suite, you must use the wlst.sh script found under the SOA home directory. Open a Terminal window and navigate to /u01/app/oracle/product/fmw/soa/common/bin: $> cd /u01/app/oracle/product/fmw/soa/common/bin

b. Then run the wlst.sh script: $> ./wlst.sh

...

wls:/offline>

c. Enter the help() command to receive help on the custom SOA Suite WLST command called sca_listDeployedComposites: wls:/offline> help('sca_listDeployedComposites')

...

List all composites deployed to the platform.

...

wls:/offline>

d. Enter this command with proper parameters to access the SOA server in your domain. Note: Enter the command on one line. It is on multiple lines here due to space limitations.

wls:/offline> sca_listDeployedComposites( 'fmwhost1.example.com', '8001', 'weblogic', 'Welcome1') host = fmwhost1.example.com port = 8001 user = weblogic Connecting to: service:jmx:t3://fmwhost1.example.com:8001/jndi/ weblogic.management.mbeanservers.runtime Following 1 composites are currently deployed to the platform: 1. HelloWorldComposite[1.0], partition=default, mode=active, state=on, isDefault=true, deployedTime=2012-07-16T12:36:08.393Z

wls:/offline>

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 28

Note: Notice that this command can be used “offline.” You do not have to first connect to the administration server. The command itself connects to the SOA server.

e. Use the custom SOA Suite WLST command to undeploy the SOA Composite application you deployed earlier. The command is sca_undeployComposite(). The first parameter is the URL of the SOA server, the second parameter is the composite application’s name, the third parameter is the revision of the application, and the next two parameters are a username and password.

Note: Enter the command on one line. It is on multiple lines here due to space limitations. wls:/offline> sca_undeployComposite(

'http://fmwhost1.example.com:8001',

'HelloWorldComposite', '1.0',

user='weblogic', password='Welcome1')

serverURL = http://fmwhost1.example.com:8001

user = weblogic

partition = default

compositeName = HelloWorldComposite

revision = 1.0

timeout= -1

set user and password...

compositeDN = default/HelloWorldComposite!1.0

INFO: Creating HTTP connection to host:fmwhost1.example.com,

port:8001

INFO: Received HTTP response from the server,

response code=200

---->Undeploying composite (default/HelloWorldComposite!1.0) success.

wls:/offline>

6. You do not really want the SOA Composite Application undeployed, so use the sca_deployComposite() command to deploy it again. The first parameter is the URL of the SOA server, the second parameter is the absolute path to the composite application archive file, and the next two parameters are a username and password.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 29

Notes

• Enter the command on one line. It is on multiple lines here due to space limitations.

• Do not forget the comma in between parameters. wls:/offline> sca_deployComposite(

'http://fmwhost1.example.com:8001',

'/home/oracle/applications/sca_HelloWorldComposite_rev1.0.jar',

user='weblogic', password='Welcome1')

serverURL = http://fmwhost1.example.com:8001

sarLocation = /home/oracle/applications/sca_HelloWorldComposite_rev1.0.jar

partition = default

overwrite = 0

user = weblogic

forceDefault = 1

configplan = None

keepInstancesOnRedeploy = 0

timeout = -1

set user and password...

Processing sar=

/home/oracle/applications/sca_HelloWorldComposite_rev1.0.jar

Adding sar file - /home/oracle/applications/sca_HelloWorldComposite_rev1.0.jar

INFO: Creating HTTP connection to host:fmwhost1.example.com, port:8001

INFO: Received HTTP response from the server, response code=200

---->Deploying composite success.

wls:/offline>

7. Exit WLST interactive mode.

a. Enter the command to exit WLST. wls:/offline> exit()


$>

8. Use WLST to run a supplied script. The script is called create_server.py and is found in the /home/oracle/admin_scripts directory. It creates a new managed server called demoserver2.

a. If you want to look at the script before running it, navigate to /home/oracle/admin_scripts and display create_server.py or look at it in a text editor.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 30

Note: If you use an editor, do not modify the file. $> more create_server.py

##########################################

# Modify these variable values if needed

url = 'fmwhost1.example.com:7001'

...

$>

Note: If you use the more command, press the spacebar when “--More--” is displayed.

b. In a Terminal window, navigate to /u01/app/oracle/product/fmw/oracle_common/common/bin. Execute the wlst.sh script with one parameter, which names the WLST script you wish to run: create_server.py. $> cd /u01/app/oracle/product/fmw/oracle_common/common/bin

$> ./wlst.sh /home/oracle/admin_scripts/create_server.py

...

*****Server created successfully


$>

c. Log in to Fusion Middleware Control to verify the creation of the new server. (The URL is http://fmwhost1.example.com:7001/em, the username is weblogic, and the password is Welcome1.)

Note: The new server, demoserver2, should be displayed on the farm home page.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 31

9. You do not really want this new server, so run another WLST script, delete_server.py, which deletes the server.

a. In the same Terminal window, execute the wlst.sh script with a parameter that names the deletion script: delete_server.py: $> ./wlst.sh /home/oracle/admin_scripts/delete_server.py

...

*****Server deleted successfully


$>

b. If you want, verify the deletion of the new server by using Fusion Middleware Control.

Note: If the server shows on the farm home page, refresh the browser.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 6 - Page 32

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 7: Node Manager

Chapter 7 - Page 1


Chapter 7

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 7 - Page 2


Practices Overview In these practices, you configure Node Manager and start it. You then start a managed server through Node Manager by using Fusion Middleware Control.










Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 7 - Page 3

Practice 7-1: Configuring Node Manager

Overview In this practice, you configure Node Manager. You then start that Node Manager.

Tasks 1. If the administration server is not running, start it. If it is already running, move to the next

task.

a. In a Terminal window, navigate to the bin directory under the domain directory, /u01/app/oracle/admin/domains/fmwdomain/bin, and run the script to start the administration server: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin


b. Messages will appear in the window. When the server successfully completes its startup process, it displays the following message in the window: <Server started in RUNNING mode>

2. If the managed servers are running, stop them. You can press Ctrl + C in the windows in which the servers are running. To use the stop script instead, perform the following steps:

a. In a Terminal window, navigate to the bin directory under the domain directory, /u01/app/oracle/admin/domains/fmwdomain/bin, and run the script to stop a managed server. The script takes a parameter, which is the server’s name and a parameter which is the URL of the administration server. The admin server URL parameter defaults to the local host and port 7001, so it can be omitted with this domain. When prompted for the username, enter weblogic, and for the password, enter Welcome1: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin

$> ./stopManagedWebLogic.sh wls_soa1

...



...

$> ./stopManagedWebLogic.sh demoserver1

...



...


3. Access the WebLogic Server Administration Console to examine the Node Manager configuration and the server assignments of the machine already created.

a. Open a web browser and enter the URL for the Administration Console: http://fmwhost1.example.com/console.

b. Log in with weblogic / Welcome1.

c. In the Domain Structure, select Environment > Machines.

d. In the Machines table, select ADMINHOST.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 7 - Page 4

e. Click the Configuration back tab and the Node Manager front tab.

f. Examine the Node Manager configuration.

g. In the Change Center, click the Lock & Edit button.

h. In the Listen Address field, enter fmwhost1.example.com. Click the Save button.

i. In the Change Center, click Activate Changes.

j. Next, click the Configuration back tab and the Servers front tab.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 7 - Page 5

k. See which servers are assigned to this machine.

4. Set the Node Manager username and password. This username and password are distinct

from the WebLogic Server administrator username and password. These are used by the administration server to communicate with Node Manager.

a. In the Administration Console, under Domain Structure, select the domain, fmwdomain.

b. Click the Security back tab and the General front tab.

c. Scroll down and click the Advanced link.

d. In the Change Center, click the Lock & Edit button.

e. In the NodeManager Username field, enter nmadmin. For the NodeManager Password and Confirm NodeManager Password fields, enter Welcome1. Leave all other fields unchanged. Click the Save button.

Note: The password does not have to match the WebLogic Server administrator’s password. That was done here so there is only one password to remember. f. In the Change Center, click Activate Changes. Note the message that no restarts are

necessary.

5. Create a new directory for the Node Manager. Copy or create the files needed there.

a. Use a Terminal window to create a directory called nodemgr for the Node Manager that deals with the machine ADMINHOST. Place the directory under: /u01/app/oracle/admin/domains. $> cd /u01/app/oracle/admin/domains

$> mkdir nodemgr

$> cd nodemgr

b. Copy the Node Manager start script, startNodeManager.sh, from <WL_HOME>/server/bin to the new nodemgr directory: $> cp /u01/app/oracle/product/fmw/wlserver_10.3/server/bin/

startNodeManager.sh startNodeManager.sh

$> ls

startNodeManager.sh

Note: Enter the command on one line. Do not add a space or line feed in between /u01/…/bin/ and the name of the file you are copying.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 7 - Page 6

c. Also copy the Node Manager domains file, nodemanager.domains, from <WL_HOME>/common/nodemanager to the new nodemgr directory: $> cp /u01/app/oracle/product/fmw/wlserver_10.3/common

/nodemanager/nodemanager.domains nodemanager.domains

$> ls

nodemanager.domains startNodeManager.sh

Note: Enter the command on one line. Do not add a space or line feed in between /u01/…/common and /nodemanager/nodemanager.domains.

d. Edit the startNodeManager.sh script in the nodemgr directory. In this example, the gedit text editor is used. Use the editor of your choice; ensure that the file is saved as a text file: $> gedit startNodeManager.sh

Note: If any gedit warnings about “wrong permissions” appear, ignore them.

e. In the file, locate where the NODEMGR_HOME variable is assigned. Change the value of this variable to the location of the new nodemgr directory, /u01/app/oracle/admin/domains/nodemgr. So, you will be changing the line from this: NODEMGR_HOME="${WL_HOME}/common/nodemanager"

To this: NODEMGR_HOME="/u01/app/oracle/admin/domains/nodemgr"

Save the file and close the editor when finished.

f. Create a text file in the nodemgr directory called nodemanager.properties and

edit it. In this example, the gedit text editor is used again: $> gedit –-new-document nodemanager.properties

Note: If any gedit warnings about “wrong permissions” appear, ignore them.

g. Add the following lines to the file and save it. Close the editor. ListenAddress=fmwhost1.example.com

ListenPort=5556

StartScriptEnabled=true

SecureListener=true

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 7 - Page 7

6. Start Node Manager.

a. In a Terminal window, navigate to the Node Manager home directory you created, and run the Node Manager start script. Near the end of the messages that print out in the window, you should see the message that a “Secure socket listener started on port 5556.” $> cd /u01/app/oracle/admin/domains/nodemgr

$> ./startNodeManager.sh

...

...<Secure socket listener started on port 5556, host fmwhost1.example.com/00.00.00.00>

...

Notes

• Do not close this window.

• The IP address is shown as all zeros for privacy.

7. Leave the administration server and Node Manager running.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 7 - Page 8

Practice 7-2: Starting Servers by Using FMW Control

Overview In this practice, you start managed servers through Node Manager by using Fusion Middleware Control.

Tasks 1. Access Fusion Middleware Control.

a. Open a web browser and enter the URL for Fusion Middleware Control: http://fmwhost1.example.com:7001/em

b. When the login screen appears, enter weblogic for the User Name and Welcome1 for the Password, and click the Login button.

2. Start managed servers by using Fusion Middleware Control. a. In the Target Navigation Pane, expand Farm_fmwdomain (if needed), then expand

WebLogic Domain, and fmwdomain. Finally, expand cluster_soa.

b. Select the wls_soa1 server in the Target Navigation Pane. Below the server name in the Content Pane, use the WebLogic Server menu to select Control > Start Up.

c. A Confirmation dialog box is displayed. Here messages appear while the server comes

up. Note: In the dialog box that appears, it indicates that the start operation cannot be canceled and will continue even if the browser window is closed.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 7 - Page 9

d. Eventually, if the server starts successfully, you see “Start operation on target /…/wls_soa1 successful.” When that appears, click the Close button.

Note: The SOA server can take a while to come up. Be patient.

e. Fusion Middleware Control should now show that the wls_soa1 server is up and

running.

f. Start the server demoserver1 in the same way. Select demoserver1 in the Target

Navigation Pane. Use the WebLogic Server menu to select Control > Start Up. Watch the Confirmation dialog box for the success message, and when it appears, click the Close button.

g. Exit Fusion Middleware Control.

3. Leave the administration server, Node Manager, and the two managed servers (wls_soa1 and demoserver1) running.

O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 7 - Page 10

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 8: Configuring Fusion Middleware Components

Chapter 8 - Page 1


Chapter 8

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 2

Practice Session 8

Practices Overview In these practices, you perform the following main tasks:

• Configure an Oracle HTTP Server (OHS) instance. You configure OHS to be the proxy to a WebLogic Server cluster. You configure OHS to enable you to access the tools on the administration server through OHS. You also register OHS with the WebLogic Server domain so you can manage OHS by using Fusion Middleware Control.

• Configure Oracle Internet Directory (OID) and Oracle Directory Services Manager (ODSM) components. You also register the OID instance with the WLS Domain to enable you to monitor the components by using Fusion Middleware Control.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 3

Practice 8-1: Configuring Oracle HTTP Server

Overview In this practice, you configure an Oracle HTTP Server (OHS) instance. You register OHS with the domain so that it can be controlled by Fusion Middleware Control. You configure the OHS instance to be the proxy to the WebLogic Server cluster. You also configure the OHS instance so that the tools on the administration server, the Administration Console, and Fusion Middleware Control are accessible through OHS.

Tasks 1. If Node Manager is not running, start it. If it is already running, move to the next task.

a. In a Terminal window, navigate to the Node Manager home directory, nodemgr, and run the Node Manager start script. Near the end of the messages that print out in the window, you should see the message that a “Secure socket listener started on port 5556”: $> cd /u01/app/oracle/admin/domains/nodemgr

$> ./startNodeManager.sh

...

...<Secure socket listener started on port 5556, host fmwhost1.example.com/000.000.00.000>

...

Notes

• Do not close this window.

• The IP address above was changed to all zeros for privacy.

2. If the administration server is not running, start it. If it is already running, move to the next task.

a. In a Terminal window, navigate to /home/oracle/admin_scripts and run the 07_wlst_start_adm.sh script: $> cd /home/oracle/admin_scripts

$> ./07_wlst_start_adm.sh

Notes

• Now that Node Manager has been set up and the administration server is assigned to its machine, the administration server can be started through Node Manager by using this supplied script. This script calls a WLST script, also supplied to you, called start_adm.py. The advantage of starting the administration server through Node Manager is that if it fails, Node Manager can automatically restart it.

• You can, if you prefer, continue to use the startWebLogic.sh script in the domain’s bin directory to start the administration server.

3. Start the managed server in the cluster by using Fusion Middleware Control. If the server in the cluster is already running, move to the next task.

a. Open a web browser and enter the URL for Fusion Middleware Control: http://fmwhost1.example.com:7001/em

b. When the login screen appears, enter weblogic for the User Name and Welcome1 for the Password, and click the Login button.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 4

c. In the Target Navigation Pane, expand Farm_fmwdomain (if needed), and then expand WebLogic Domain and fmwdomain.

d. Select the cluster_soa cluster in the Target Navigation Pane. Below the cluster name in the Content Pane, use the WebLogic Cluster menu to select Control > Start Up.

e. A Confirmation dialog box is displayed. Here messages appear while the server in the cluster comes up. When the cluster starts successfully, close the dialog box.

4. Run the Web Tier Configuration Wizard to configure an instance of OHS.

a. Navigate to the directory where the Web Tier Configuration Wizard script resides and run that script: $> cd /u01/app/oracle/product/fmw/web/bin

$> ./config.sh

b. Use the guidelines in the following table to configure the OHS instance:


Choices or Values

a. Welcome Click Next

b. Configure Components Select Oracle HTTP Server.

Deselect Oracle Web Cache.

Deselect Associate Selected Components with WebLogic Domain.

Click Next.

c. Specify Component Details

Enter the following values:

• Instance Home Location: /u01/app/oracle/admin/instances/ ohs_inst1

• Instance Name: ohs_inst1

• OHS Component Name: ohs1

Note: Do not add any spaces or line feeds in the fields.

Click Next.

d. Configure Ports Select “Specify Ports using Configuration file.”

Click Browse, and navigate to /home/oracle/prop_files.

Select ohs_static_ports.ini and click Open.

Click the View/Edit File button and ensure that the following port assignment is used:

• OPMN Local Port = 6700

• OHS Port = 7777

Click Save after verifying.

Then click Next.

e. Specify Security Updates Deselect “I wish to receive security updates via My Oracle Support.” Click Next.

Click Yes in the next dialog box.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 5


Choices or Values

f. Installation Summary Click Configure.

g. Configuration Progress The wizard launches multiple configuration assistants. When all are successful, and Web Tier Configuration reaches 100%, click Next.

h. Installation Complete Click Finish.

c. In a web browser, verify that the OHS instance is configured and is operational by accessing the URL: http://fmwhost1.example.com:7777.

d. Verify that the OHS instance is configured to run as the operating system user that

installed the software (oracle in this environment). In a Terminal window, navigate to /u01/app/oracle/admin/instances/ohs_inst1/config/OHS/ohs1. Verify that the User directive is set to oracle.

$> cd /u01/app/oracle/admin/instances/ohs_inst1/config/OHS/ohs1

$> grep -i "USER " httpd.conf

... User oracle

...

O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 6

e. If the User is oracle, move to the next task. If not, stop OHS. Then edit the OHS configuration file, httpd.conf, and set the User directive to oracle. Finally, restart OHS. To stop OHS, navigate to /u01/app/oracle/admin/instances/ohs_inst1/bin and run the opmnctl stopall command. To start OHS, run the opmnctl startall command. Both are shown here: $> cd /u01/app/oracle/admin/instances/ohs_inst1/bin

$> ./opmnctl stopall

opmnctl stopall: stopping opmn and all managed processes... $> $> ./opmnctl startall

opmnctl startall: starting opmn and all managed processes...

5. Register OHS with the WebLogic domain and verify the registration.

a. In a Terminal window, navigate to the bin subdirectory of the OHS instance, and run the command: opmnctl registerinstance. With this command, you enter the parameters for the administration server host, port, and username. At the prompt for the password, enter Welcome1. After registering the instance, run the opmnctrl restartproc command to restart OHS.

Notes

• Enter all commands on one line. (They are sometimes shown on multiple lines due to space limitations.)

• The password does not display when entered. $> cd /u01/app/oracle/admin/instances/ohs_inst1/bin

$> ./opmnctl registerinstance –adminHost fmwhost1.example.com

-adminPort 7001 –adminUsername weblogic

...

Command requires login to weblogic admin server

(fmwhost1.example.com):

Username: weblogic

Password: Welcome1

...

Done

Registering instance

Command succeeded.

$>

$> ./opmnctl restartproc ias-component=ohs1

opmnctl restartproc: restarting opmn managed processes...

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 7

b. Verify that the OHS instance is visible in Fusion Middleware Control. Access FMW Control in a web browser (http://fmwhost1.example.com:7001/em) and log in with weblogic / Welcome1. In the Target Navigation Pane, there should now be a Web Tier category. Expand it and see the OHS instance called ohs1.

6. Configure OHS as the proxy to the WebLogic Server cluster by using Fusion Middleware

Control. Also configure OHS, so that the tools running on the administration server (the Administration Console and Fusion Middleware Control) can be accessed through OHS. a. Access Fusion Middleware Control. In the Target Navigation Pane, expand Web Tier

and select ohs1.

O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 8

b. From the Oracle HTTP Server menu, select Administration > mod_wl_ohs Configuration.

Note: The mod_wl_ohs.conf file contains the configuration for the WebLogic Server module. When you use this functionality of Fusion Middleware Control, it edits the file for you. The file is found here: /u01/app/oracle/admin/instances/ohs_inst1/config/OHS/ohs1.

c. In the General area, select Dynamic Server List ON.

Note: Do not change anything else in this area.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 9

d. Scroll down to the Locations area and click the Add Row button. In the new row, enter these values for the following fields:

• Location: /soa-infra

• WebLogic Cluster: fmwhost1.example.com:8001

Note: Any field not listed should be left blank.

Note: If there were multiple servers in the cluster, you could list them with commas in between, as in the following:

fmwhost1.example.com:8001,fmwhost1.example.com:8003

e. Click the Add Row button again. In the new row, enter these values for the following fields:

• Location: /console

• WebLogic Host: fmwhost1.example.com

• WebLogic Port: 7001


f. Click the Add Row button again. In the new row, enter these values for the following fields:

• Location: /consolehelp



Notes

• Any field not listed should be left blank.

• This is the context root of the administration console help. g. Click the Add Row button one more time. In the new row, enter these values for the

following fields:

• Location: /em




Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 10

h. When you have entered all the locations, the table looks like this:

i. Click the Apply button to save the changes. A confirmation message appears. Close it

by clicking the “X.”

j. Changes to the configuration file require that the OHS instance restart to take effect.

Stop OHS by using Fusion Middleware Control. In the Target Navigation Pane, expand Web Tier and select ohs1. From the Oracle HTTP Server menu, select Control > Shut Down. When asked if you are sure, click the Shutdown button. After the confirmation message appears, click the Close button.

k. Start the OHS instance by using the menu again. From the Oracle HTTP Server menu, select Control > Start Up. Wait for the start confirmation message. After you see that the OHS instance has been started successfully, click the Close button.

Note: It sometimes takes OHS some time to pick up a configuration change. Wait a few minutes before moving to the next step.

l. Verify that OHS is now acting as the proxy to the cluster by accessing the /soa-infra web application through the OHS port of 7777. In a web browser, enter this URL: http://fmwhost1.example.com:7777/soa-infra

Note: If the authentication dialog box appears, enter weblogic for the User Name and Welcome1 for the Password. Then click OK.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 11

m. Verify that you can now access the WebLogic Server tools on the administration server

through the OHS port of 7777. In a web browser, enter these URLs: http://fmwhost1.example.com:7777/console

http://fmwhost1.example.com:7777/em

Note: Log in to both the Administration Console and Fusion Middleware Control with weblogic / Welcome1.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 12

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 13

Practice 8-2: Configuring Oracle Internet Directory and Oracle Directory Services Manager

Overview In this practice, you perform the following main tasks:

• Configure an Oracle Internet Directory (OID) instance and Oracle Directory Services Manager (ODSM) server using the Oracle Identity Management (OIM) Configuration Wizard.

• Register the OID instance with the WebLogic domain to enable you to monitor and manage the OID instance.

• Create a connection entry for OID in ODSM.

Tasks 1. Configure an Oracle Internet Directory instance by using the Oracle Identity Management

Configuration Wizard.

Note: You must use the OIM Configuration Wizard and not the Fusion Middleware Configuration Wizard for this purpose.

a. Ensure that the fmwdb database is up and running. (You can start it by using the 01_start_fmwdb.sh script in /home/oracle/admin_scripts.) $> /home/oracle/admin_scripts/01_start_fmwdb.sh

b. Open a Terminal window, and ensure that the ORACLE_HOME and ORACLE_SID variables are not set: $> unset ORACLE_HOME ORACLE_SID

c. Set the JAVA_HOME environment variable to /u01/app/oracle/product/fmw/jrockit-jdk, and set the PATH to include $JAVA_HOME/bin: $> export MW_HOME=/u01/app/oracle/product/fmw



d. Start the Oracle Identity Management 11g Configuration Assistant by running /u01/app/oracle/product/fmw/idm/bin/config.sh. $> cd /u01/app/oracle/product/fmw/idm/bin

$> ./config.sh

e. Use the following table for your selections and responses:


Choices or Values


b. Select Domain Select Extend Existing Domain and enter the following values:

• Host Name: fmwhost1.example.com

• Port: 7001

• User Name: weblogic

• User Password: Welcome1

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 14


Choices or Values

Click Next.

c. Warning dialog box

If the warning dialog box appears, Click Yes to confirm that this domain is suitable for configuring Oracle Internet Directory.

d. Specify Installation Location

Keep the WebLogic Server Directory as it is: /u01/app/oracle/product/fmw/wlserver_10.3


• Oracle Instance Location: /u01/app/oracle/admin/instances/oid_inst1

• Oracle Instance Name: oid_inst1 Click Next.

e. Security Updates

Deselect “I wish to receive security updates via My Oracle Support.” Click Next.

Click Yes to confirm.

f. Configure Components

Deselect Oracle Identity Manager Components at the top to deselect all the components.

Then select only:

• Oracle Internet Directory

• Oracle Directory Service Manager

Note: Selecting Oracle Directory Service Manager also selects its category of Management Components. Click Next.

g. Configure Ports Select Auto Port Configuration.

Click Next.

h. Specify Schema Database

Select Use Existing Schema. Then enter the following values:

• Connect String: fmwhost1.example.com:1521: fmwdb.example.com

• Schema Name: ODS (not changeable) • Password: Welcome1

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 15


Choices or Values

Note: Do not add any space or line feeds in the “Connect String.” It is on two lines due to space limitations.

Click Next. i. Create Oracle

Internet Directory


• Realm: dc=example,dc=com

• Administrator User Name: cn=orcladmin (not changeable)

• Administrator Password: Welcome1

• Confirm Password: Welcome1

Click Next.

j. Installation Summary

Review the selections to ensure that they are correct, and click Configure.

k. Configuration Progress

Configuration assistants are launched in the interface. This process may take about 15 minutes. Wait for the configuration process to finish. Note: You may have to scroll to see if all the configuration assistants have completed. Click Next.

l. Installation Complete

Click Finish.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 16

f. Validate the configuration of the Oracle Internet Directory instance by running the ldapbind commands:

1) Set the following environment variables: $> export MW_HOME=/u01/app/oracle/product/fmw

$> export ORACLE_HOME=$MW_HOME/idm

$> export ORACLE_INSTANCE=/u01/app/oracle/admin/instances/oid_inst1

$> export PATH=$ORACLE_HOME/bin:$PATH

2) Run the following ldapbind commands to verify successful configuration of OID instance. When asked for the bind password, enter Welcome1.

$> ldapbind -h fmwhost1.example.com

-p 3060 -D "cn=orcladmin" -q

Please enter bind password: Welcome1

bind successful

$> ldapbind -h fmwhost1.example.com

-p 3131 -D "cn=orcladmin" -q -U 1

Please enter bind password: Welcome1

bind successful

Note: Enter the commands on one line. They are shown on multiple lines due to space limitations.

2. Log in to Fusion Middleware Control (http://fmwhost1.example.com:7777/em with weblogic / Welcome1) to verify OID is accessible.

a. Verify that the oid1 instance is visible under Identity and Access in the Target Navigation Pane.

3. Setup ADMINHOST as the machine for the newly created wls_ods1 managed server.

a. In a web browser, access the WebLogic Server Administration Console at http://fmwhost1.example.com:7777/console, and log in as weblogic with the password Welcome1.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 17

b. Expand Environment under Domain Structure and click Servers.

c. Click the Control tab. Then select wls_ods1, and click Shutdown > Force Shutdown Now. When asked if you are sure, click Yes.

d. Wait a few minutes for wls_ods1 to shut down. Then click the wls_ods1 link.

e. In the Change Center, click Lock & Edit.

f. In the server’s settings, click the Configuration back tab and the General front tab. Use the Machine drop-down list and select ADMINHOST. Make sure that the Listen Address field is blank. Then click Save.

g. Also set the Hostname Verification of this server. Select wls_ods1 in the Servers table,

select the tabs Configuration > SSL, click Advanced, select None from the Hostname Verification drop-down list, and click Save.

h. In the Change Center, click Activate Changes.

i. Using the breadcrumbs of the Administration Console, click Summary of Servers. Then click the Control tab. Select wls_ods1, and click Start. When asked if you are sure, click Yes.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 18

j. Wait for the server’s State to change to “RUNNING” before continuing.

4. Configure OID parameters for better performance.

a. In Fusion Middleware Control, in the Target Navigation Pane, expand Identity and Access, and click oid1.

b. From the Oracle Internet Directory menu, select Administration > Shared Properties. On the General tab, in the Tuning section, select Skip Referral for Search, and deselect Match DN. Then click the Apply button.

Note: You may need to maximize the browser to see some of the parameters. If you still cannot see Match DN at the bottom, place the cursor in Hashed Attributes and click Tab.

c. Close the confirmation window by clicking “X.”

d. From the Oracle Internet Directory menu, select Administration > Server Properties. Then click the Performance tab. Enter the following values, and then click the Apply button:

• Number of OID LDAP Server Processes: 4

• Number of DB Connections per Server Process: 4

• Maximum number of LDAP connections per Server Process: 4096

Note: Any field not listed should retain its default value. O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 19

e. Notice that the confirmation indicates that a restart is needed. Close the confirmation

window by clicking “X.”

f. From the Oracle Internet Directory menu, select Control > Restart. Click OK when asked if you are sure. After you receive the confirmation that the “Restart Operation… Completed Successfully,” click Close.

g. Log out of Fusion Middleware Control and close the browser window.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 20

5. In a web browser, access ODSM at http://fmwhost1.example.com:7005/odsm, and create connections to OID to validate access to ODSM.

a. In a web browser, enter the following URL: http://fmwhost1.example.com:7005/odsm

b. Click Connect to a directory, and then click Create A New Connection.

c. Enter or select the following values in the New Connection dialog box, then click the

Connect button:

• Directory Type: OID

• Name: OID

• Server: fmwhost1.example.com

• Port: 3060

• SSL Enabled: Deselected

• User Name: cn=orcladmin

• Password: Welcome1

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 21

• Start Page: Home

d. The Oracle Directory Services Manager is now connected to OID.

6. In this practice environment, you want to disable the password expiry policy to avoid being

locked out of your account. a. In the ODSM window, which is now connected to OID, click the Data Browser tab.

b. Expand the nodes and access dc=com > dc=example > cn=OracleContext > cn=Products > cn=Common > cn=pwdPolicies.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 22

c. Click cn=default. On the default page on the right, scroll down and set the pwdLockout attribute to 0 (the number zero). Then click the Apply button.

Note: Do not change any other attributes.

d. A confirmation message saying “Changes have been applied successfully” appears. e. Click “X” at the top (next to Help) to close the connection. Then close the browser

window.

.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 23

Practice 8-3: Taking a Backup

Overview In this practice, you back up your environment.

Assumptions You have sufficient free space (about 15 GB) in /stage/backup.

Tasks 1. Stop all the processes in your environment.

a. Stop all system component processes (OHS and OID) by using the stop_fmw_inst.sh script provided in the /home/oracle/admin_scripts directory: $> cd /home/oracle/admin_scripts

$> ./stop_fmw_inst.sh

...

opmnctl stopall: stopping opmn and all managed processes...


b. Shut down the domain by using Fusion Middleware Control. This will stop all the managed servers in the domain. Because the OHS instance is no longer running, access Fusion Middleware Control with the URL http://fmwhost1.example.com:7001/em. Log in with weblogic / Welcome1. In the Target Navigation Pane, expand WebLogic Domain. Click fmwdomain. From the WebLogic Domain menu, select Control > Shut Down.

c. When asked if you are sure, click the Shutdown button.

d. Wait for the shutdown operation to complete. Then click the Close button.

e. Log out of Fusion Middleware Control, and close the browser window.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 24

f. Open a Terminal window, and in the bin directory of the domain, shut down the administration server by using the stopWebLogic.sh script. $> cd /u01/app/oracle/admin/domains/fmwdomain/bin


g. Stop Node Manager. If you can find the window in which Node Manager is running, press Ctrl + C in the window to kill it. If Node Manager is running in the background, use the ps command to get the process ID of the Node Manager process, and then issue the kill command.

Note: The process ID will be the first number (shown as “xxxxx” below) in the output for the weblogic.NodeManager process.

$> ps –ef | grep weblogic.nodemanager

...

oracle xxxxx yyyyy ... weblogic.NodeManager ...

$> kill -9 xxxxx

h. Run the stop_fmwdb.sh script in /home/oracle/admin_scripts to stop the database instances and listener processes: $> cd /home/oracle/admin_scripts

$> ./stop_fmwdb.sh

...

The command completed successfully

$>

2. Perform a complete backup of the database and FMW components.

a. In a Terminal window, run the ps command to ensure that no Fusion Middleware or database processes are running. $> ps –ef | grep oracle | grep /u01

b. Use the tar utility to back up everything in the /u01/app/ directories to the /stage/backup directory. The backup.sh script is available in /home/oracle/admin_scripts. Run this script as the root user to perform a complete backup. $> cd /home/oracle/admin_scripts

$> su

Password: oracle

#> ./backup.sh 08

...

Notes


• This backup will take 30 minutes or more. Because the script takes a long time to complete, you can start it and do something else while it runs, like going on a break, or listening to the next lecture. Check the script after a while, and when it completes, you can finish the rest of this practice.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 25

3. After the backup has completed successfully, log out as root, and start the environment in the proper order.

a. Exit, so you are no longer root. #> exit

b. In the Terminal window, navigate to the /home/oracle/admin_scripts directory: $> cd /home/oracle/admin_scripts

c. Start the database listener and OID database by using the 01_start_fmwdb.sh script: $> ./01_start_fmwdb.sh

...

d. Start the OID and ODSM instances by using the 03_start_oid.sh script: $> ./03_start_oid.sh


...

Note: Look for the status of all processes to be “Alive.”

e. Start the OHS instance by using the 05_start_ohs.sh script: $> ./05_start_ohs.sh


...

Note: Look for the status of the ohs1 process to be “Alive.”

f. Start Node Manager by using the 06_start_nm.sh script: $> ./06_start_nm.sh

Notes

• A new Terminal window labeled “Node Manager” should open. Node Manager will run in that window.

• Ignore any warning about “wrong permissions.”

g. Start the administration server by using the 07_wls_start_adm.sh script: $> ./07_wlst_start_adm.sh

...

Starting server AdminServer ...

Successfully started server AdminServer ...

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 8 - Page 26

h. Use Fusion Middleware Control (http://fmwhost1.example.com:7777/em with weblogic/Welcome1) to start all the managed servers in the domain. Select fmwdomain in the Target Navigation Pane. From the WebLogic Domain menu, select Control > Start Up.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 9: Fusion Middleware Security

Chapter 9 - Page 1


Chapter 9

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 2


Practices Overview In these practices, you configure the Identity and Policy stores for Fusion Middleware components.

Usually, WebLogic Server and Java EE applications deployed to WebLogic Server are associated with the DefaultAuthenticator. This authentication provider stores the users and identity information in the internal LDAP that comes with WebLogic Server. However, for most production environments, users and groups are stored in a production-ready LDAP store, such as Oracle Internet Directory.

In the first practice, you configure Oracle Internet Directory (OID) to be the Identity Store.

In the second, optional practice, you use WLST to reassociate Java Platform Security (JPS) with Oracle Internet Directory by using the Oracle Platform Security Services (OPSS). OPSS enables you to separate security management from application development.

In the final practice, you use the backup script to back up the environment.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 3

Practice 9-1: Preparing the Identity Store for WLS Administrators

Overview In this practice, you create the Identity Store (users and groups) in Oracle Internet Directory (OID) and associate it with the WebLogic Server domain you have created. Before you set Oracle Internet Directory as the authentication provider, you should first create the user and group data in it.

Tasks 1. Using Oracle Directory Services Manager (ODSM), create the fmwadm user in Oracle

Internet Directory.

a. In web browser, access ODSM at http://fmwhost1.example.com:7005/odsm. Click Connect to a directory > OID - OID.

b. Log in with the User Name of cn=orcladmin and the Password of Welcome1. Then

click Connect.

c. Click the Data Browser tab. Then expand the Data Tree progressively to access

dc=com > dc=example > cn=Users.

O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 4

d. Right-click cn=Users, and select Create in the menu.

e. On the Entry Properties screen of the Create New Entry Wizard, click the “+” in Object

Class and select the following classes: (Use Ctrl + click to select multiple values and then click OK.)

• inetOrgPerson

• orclUser

• orclUserV2

• organizationalPerson

• person

• top

Set the “Parent of the entry” field to: cn=Users,dc=example,dc=com, and click Next.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 5

f. Enter or select the following, and then click Next:

• cn: fmwadm

• sn: fmwadm

• Relative Distinguished Name: cn

Note: It will automatically set the Distinguished Name to cn=fmwadm,cn=Users,dc=example,dc=com.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 6

g. On the Status screen, verify that the new entry has been created successfully and click Finish.

2. Set the password for the newly created fmwadm user.

a. In the Data Tree, expand the cn=Users node and select cn=fmwadm.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 7

b. Click the Attributes tab. Then in the Views drop-down list, select Show All.

c. Scroll down and set the “userPassword” field to Welcome1. Then click the Apply

button. A message appears confirming that the changes have been applied successfully.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 8

3. Create a group named FMW_Admins in the cn=Groups,dc=example,dc=com node and assign fmwadm to be a member of this group.

a. In the Data Tree of ODSM, expand cn=Groups, and select cn=OCS_PORTAL_USERS. Then right-click “cn=OCS_PORTAL_USERS,” and select Create Like.

b. On the Entry Properties screen of the wizard, retain the object classes already set up.

Also ensure that the “Parent of the entry” field is set to cn=groups,dc=example,dc=com. Then click Next.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 9

c. On the Mandatory Properties screen, set or select the following values, then click Next:

• cn: FMW_Admins

• Relative Distinguished Name: cn

Note: This will automatically set the Distinguished Name as cn=FMW_Admins,cn=goups,dc=example,dc=com.

d. On the Optional Properties screen, enter the following, and then click Next:

• description: Group of users who can administer FMWDomain

• displayName: FMW Domain Administrators

• uniqueMember: cn=fmwadm,cn=Users,dc=example,dc=com

O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 10

e. On the status screen, verify that the group is successfully created, and click Finish.

f. Click “X” next to Help in the top menu of ODSM to close the connection to OID.

4. Add OID as an authentication provider to the WebLogic Server security realm using the

Administration Console.

a. Launch the web browser and access the Administration Console (http://fmwhost1.example.com:7777/console). Log in with weblogic / Welcome1.

b. In the Domain Structure panel, select Security Realms, and in the table, click myrealm.

c. In the Change Center, click Lock & Edit. Then click the Providers > Authentication tabs. Click the New button, enter or select the following values, and then click OK:

• Name: OID Auth

• Type: OracleInternetDirectoryAuthenticator

d. In the Authentication Providers table, click OID Auth.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 11

e. Click the Configuration > Provider Specific tabs, enter the following values, and then click Save.

Note: Any field not listed should retain its default value.

Field Value

Host fmwhost1.example.com

Port 3060

Principal cn=orcladmin

Credential and Confirm Credential Welcome1

User Base DN cn=Users,dc=example,dc=com

User Name Attribute cn

Group Base DN cn=Groups,dc=example,dc=com

Static Group Name Attribute cn

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 12

5. Adjust the authentication processing order.

a. Use the breadcrumb trail to return to the list of Authentication providers:

b. Click the Reorder button.

c. Use the arrow buttons and the check boxes to put the providers in the following order, and then click OK: OID Auth DefaultAuthenticator DefaultIdentityAsserter

d. In the table, click the OID Auth provider. Confirm that the Configuration > Common tabs are selected.

e. Set the Control Flag to Sufficient. Click Save.

f. Similarly, edit DefaultAuthenticator, and set its Control Flag to Sufficient as well.

g. In the Change Center, click Activate Changes.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 13

h. Shut down all the servers of the domain. Under Domain Structure, select Servers. Click the Control tab. Select the check box of all the servers and click Shutdown > Force Shutdown Now. When asked if you are sure, click Yes. Close the browser window. Wait a few minutes before continuing, to ensure that the servers have all shut down.

6. To manage WebLogic by using the fmwadm LDAP account, add the FMW_Admins group to the list of Weblogic Administration groups.

a. Using the 07_wlst_start_adm.sh script in the home/oracle/admin_scripts directory, start the administration server: $> /home/oracle/admin_scripts/07_wlst_start_adm.sh

Note: Wait for the script to successfully complete before continuing.

b. Log in to the WebLogic Server Administration Console and in Domain Structure, click Security Realms.

c. Click myrealm in the Realms table. On the Settings page for myrealm, click the Roles & Policies tab.

d. In the Roles table, expand Global Roles and then Roles, and click the View Role Conditions link for the Admin role.

e. Under Edit Global Role, click Add Conditions.

f. Select Group from the Predicate List drop-down list, and click Next.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 14

g. Enter FMW_Admins in the Group Argument Name field, and click the Add button.

h. Click Finish to return to the Edit Global Rule screen. The Role Conditions table

displays Group:FMW_Admins Or Group:Administrators. Click Save.

i. Log out of the Administration Console.

O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 15

j. Validate that the changes were successful by logging in to the Administration Console with the credentials for the fmwadm user (password Welcome1).

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 16

Practice 9-2: Preparing the Policy Store for WebLogic and FMW Components (Optional)

Overview In this practice, you associate the Policy Store for the fmwdomain with the Oracle Internet Directory you have configured. This will help you to consistently use the Identity and Access Management infrastructure that you have set up across all the applications including Java EE and ADF applications.

For ease of use, the necessary property files used in this practice are provided for you. You can use these files as examples for setting up property files suitable to your environment.

1. View the policy store property file, policystore.props. Then configure the Policy Store in Oracle Internet Directory by using the idmconfigTool utility.

a. In a Terminal window, set the MW_HOME, JAVA_HOME, IDM_HOME, and ORACLE_HOME environment variables: $> export MW_HOME=/u01/app/oracle/product/fmw

$> export IDM_HOME=$MW_HOME/idm

$> export IAM_HOME=$MW_HOME/iam


$> export ORACLE_HOME=$IAM_HOME

b. View the policystore.props file in /home/oracle/prop_files and note the following lines:

• POLICYSTORE_HOST: fmwhost1.example.com

• POLICYSTORE_PORT: 3060

• POLICYSTORE_BINDDN: cn=orcladmin

• POLICYSTORE_READONLYUSER: PolicyROUser

• POLICYSTORE_READWRITEUSER: PolicyRWUser

• POLICYSTORE_SEARCHBASE: dc=example,dc=com

• POLICYSTORE_CONTAINER: cn=jpsroot

c. Configure the Policy Store by using the idmConfigTool script in <ORACLE_HOME>/idmtools/bin. Use the following command syntax: $> cd /home/oracle/prop_files

$> $ORACLE_HOME/idmtools/bin/idmConfigTool.sh

–configPolicyStore

input_file=policystore.props

Notes


• For the passwords, use the following values:

• Policy Store Bind DN password: Welcome1

• User Password for PolicyROUser and confirm password: fmwro1

• User Password for PolicyRWUser and confirm password: fmwrw1

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 17

d. Check the automation.log file in the current directory for any errors.

2. Associate the WebLogic domain policy and credential store with OID by using the reassociateSecurityStore command of WLST.

a. Start the WLST shell from the <ORACLE_COMMON_HOME>/common/bin directory. Connect to the administration server, and run the reassociateSecurityStore command as follows:

Note: Do not copy and paste these commands into WLST, type them in. O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 18

1) Set the PATH variable to include $JAVA_HOME/bin and then invoke WLST: $> export PATH=$JAVA_HOME/bin:$PATH

$> $MW_HOME/oracle_common/common/bin/wlst.sh

2) Connect to the administration server:

connect('weblogic', 'Welcome1', 't3://fmwhost1.example.com:7001')

3) Reassociate the Security Store: reassociateSecurityStore(

domain= 'fmwdomain', admin= 'cn=orcladmin',

password='Welcome1',

ldapurl='ldap://fmwhost1.example.com:3060',

servertype='OID', jpsroot='cn=jpsroot')

Notes


• This WLST command will take a few minutes to complete.

4) Exit from WLST:

exit()

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 19

b. Shut down all the servers of the domain. In the Administration Console, under Domain Structure, select Servers. Click the Control tab. Select the check box of all the servers and click Shutdown > Force Shutdown Now. When asked if you are sure, click Yes. Close the browser window. Wait a few minutes before continuing, to ensure that the servers have all shut down.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 20

Practice 9-3: Taking a Backup

Overview In this practice, you back up your environment.

Assumptions You have sufficient free space (about 15 GB) in /stage/backup.

Tasks 1. Stop all the system processes in your environment.

a. Stop all system component processes (OHS and OID) by using the stop_fmw_inst.sh script provided in the /home/oracle/admin_scripts directory: $> cd /home/oracle/admin_scripts

$> ./stop_fmw_inst.sh

...



2. Shut down the domain.

Note: If you did the previous, optional practice, then all the servers in the domain have already been shut down and you can skip to the next task.

a. Shut down the domain by using Fusion Middleware Control. This will stop all the managed servers in the domain. Because the OHS instance is no longer running, access Fusion Middleware Control with the URL http://fmwhost1.example.com:7001/em. Log in with weblogic/Welcome1. In the Target Navigation Pane, expand WebLogic Domain. Click fmwdomain. From the WebLogic Domain menu, select Control > Shut Down.

b. When asked if you are sure, click the Shutdown button.

c. Wait for the shutdown operation to complete. Then click the Close button.

d. Log out of Fusion Middleware Control, and close the browser window.

e. Open a Terminal window, and in the bin directory of the domain, shut down the administration server by using the stopWebLogic.sh script:

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 21



3. Stop Node Manager.

a. If you can find the window in which Node Manager is running, press Ctrl + C in the window to kill it. If Node Manager is running in the background, use the ps command to get the process ID of the Node Manager process, and then issue the kill command.

Note: The process ID will be the first number (shown as “xxxxx” below) in the output for the weblogic.NodeManager process.

$> ps –ef | grep weblogic.nodemanager

...

oracle xxxxx yyyyy ... weblogic.NodeManager ...

$> kill -9 xxxxx

4. Stop the database and listeners.

a. Run the stop_fmwdb.sh script in /home/oracle/admin_scripts to stop the database instances and listener processes: $> cd /home/oracle/admin_scripts

$> ./stop_fmwdb.sh

...

The command completed successfully

$>

5. Perform a complete backup of the database and FMW components.

a. In a Terminal window, run the ps command to ensure that no Fusion Middleware or database processes are running: $> ps –ef | grep oracle | grep /u01

b. Use the tar utility to back up everything in the /u01/app/ directories to the /stage/backup directory. The backup.sh script is available in /home/oracle/admin_scripts. Run this script as the root user to perform a complete backup: $> cd /home/oracle/admin_scripts

$> su

Password: oracle

#> ./backup.sh 09

...

#> exit

$>

Notes


• This backup will take 30 minutes or more. Because the script takes a long time to complete, you can start it and do something else while it runs, like going on a break, or listening to the next lecture. Check the script after a while, and when it completes, you can finish the rest of this practice.

6. After the backup has completed successfully, start the environment in the proper order.

a. In the Terminal window, navigate to the /home/oracle/admin_scripts directory: $> cd /home/oracle/admin_scripts

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 9 - Page 22

b. Start the database listener and OID database using the 01_start_fmwdb.sh script: $> ./01_start_fmwdb.sh

...

c. Start the OID instance by using the 03_start_oid.sh script: $> ./03_start_oid.sh


...

Note: Look for the status of all processes to be “Alive.”

d. Start the OHS instance by using the 05_start_ohs.sh script: $> ./05_start_ohs.sh


...

Note: Look for the status of the ohs1 process to be “Alive.”

e. Start Node Manager by using the 06_start_nm.sh script: $> ./06_start_nm.sh

Notes

• A new Terminal window labeled “Node Manager” should open. Node Manager will run in that window.

• Ignore any warning about “wrong permissions.”

f. Start the administration server by using the 07_wls_start_adm.sh script: $> ./07_wlst_start_adm.sh

...

Starting server AdminServer ...

Successfully started server AdminServer ...

g. Use Fusion Middleware Control (http://fmwhost1.example.com:7777/em with weblogic/Welcome1) to start all the managed servers in the domain. Select fmwdomain in the Target Navigation Pane. From the WebLogic Domain menu, select Control > Start Up.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 10: Fusion Middleware Backup and Recovery

Chapter 10 - Page 1


Chapter 10

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 10 - Page 2


Practices Overview In this practice, you will perform a restore / recovery after a simulated media failure.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 10 - Page 3

Practice 10-1: Recovering from a Media Failure

Assumptions You have completed Practice 9 (and taken a backup).

Tasks 1. Start up the database, OID instance, OHS instance, Node Manager, and the administration

server, if these are not already running.

a. In the Terminal window, change directory to the /home/oracle/admin_scripts directory.

b. Start the database listener and the OID database using the 01_start_fmwdb.sh script.

c. Start the OID instance by using the 03_start_oid.sh script.

d. Start the OHS instance by using the 05_start_ohs.sh script.

e. Start Node Manager by using the 06_start_nm.sh script.

f. Start the administration server by using the 07_wls_start_adm.sh script.

2. Configure ODSM to work through OHS, and verify access through OHS.

a. Using FMW Control, start the wls_ods1 managed server, if it is not already running.

b. In FMW Control, navigate to Web Tier > ohs1. Then using the Oracle HTTP Server menu select Administration > mod_wl_ohs configuration. This gives you access to the mod_wl_ohs configuration page.

c. Add a row to the Locations table as follows, and then click Apply:

• Location: /odsm



d. Restart the OHS instance by using FMW Control. (From the Oracle HTTP Server

menu, select Control > Restart. When asked if you are sure, click the Restart button.)

e. Log out of FMW Control.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 10 - Page 4

f. Access ODSM through OHS by using http://fmwhost1.example.com:7777/odsm.

3. Simulate a media failure.

a. In a Terminal window, change directory to /u01/app/oracle/admin/instances/ohs_inst1/config/OHS/ohs1. $> cd /u01/app/oracle/admin/instances/ohs_inst1

$> cd config/OHS/ohs1

b. Copy mod_wl_ohs.conf to the /stage/backup directory: $> cp mod_wl_ohs.conf /stage/backup/mod_wl_ohs.conf

c. Rename the original mod_wl_ohs.conf file to mod_wl_ohs.bak. This will simulate a media failure (the file is gone or corrupt). $> mv mod_wl_ohs.conf mod_wl_ohs.bak

d. Try to access ODSM through OHS with this URL in a web browser: http://fmwhost1.example.com:7777/odsm

Note: Notice that you can still access ODSM. This is because mod_wl_ohs.conf has already been read into memory.

e. Log in to FMW Control by using http://fmwhost1.example.com:7001/em and try to make changes to the mod_wl_ohs configuration. Select ohs1 under Web Tier and use the Oracle HTTP Server menu selection of Administration > mod_wl_ohs configuration. An error message appears:

f. Click Close.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 10 - Page 5

g. If you wait for a long time, OHS may be stopped automatically and you will not be able to change the mod_wl_ohs configuration.

h. Log out of FMW Control.

4. Perform recovery from the previous backup that you have created.

a. Stop all the servers in the domain by using the WebLogic Server Administration Console. (URL: http://fmwhost1.example.com:7001/console, under Domain Structure expand Environment and select Servers, click the Control tab, select all the servers and then click Shutdown > Force Shutdown Now, click Yes, close the web browser)

b. Stop Node Manager. (Press Ctrl + C in its window.)

c. Stop all the system component processes. (Use the /home/oracle/admin_scripts/stop_fmw_inst.sh script.)

d. Stop the database processes. (Use the /home/oracle/admin_scripts/stop_fmwdb.sh script.)

e. Ensure that there are no domain, system, or database processes running: $> ps –ef | grep u01

oracle 10911 2448 0 10:51 pts/2 00:00:00 grep u01

Note: If you followed the previous steps correctly, there should be no processes running with “u01,” except the grep process itself. If there are any other processes with “u01,” make note of each process ID and use the kill -9 command (with each process ID, shown as nnnn below):

$> kill -9 nnnn

f. Change to the root folder (/), and clean up everything under /u01/app. (Use mv to rename things, rather than using rm –rf). $> mv /u01/app /u01/old_app

g. Extract and restore from the backup you took after the previous practice. This command may take 15 to 20 minutes to complete: $> tar –zxpvf /stage/backup/u01-bak-session-09.tarz

Notes

• You could have copied the latest mod_wl_ohs.conf file from the /stage/backup directory. But the intention is to show you how to recover using the full backup.

• Because this command takes a while to complete, you can start it and do something else while it runs, like going on a break, or listening to the next lecture. Check the command after a while, and when it completes, you can finish the rest of this practice.

h. Change directory to /home/oracle/admin_scripts and start up all the processes. Wait for each script to complete before running the next one.

1) Start the database using 01_start_fmwdb.sh.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 10 - Page 6

2) Start the OID instance using 03_start_oid.sh.

3) Start the OHS instance using 05_start_ohs.sh.

4) Start Node Manager by using 06_start_nm.sh.

5) Start the administration server by using 07_wlst_start_adm.sh.

i. Access FMW Control and navigate to Web Tier > ohs1. Then using the Oracle HTTP Server menu, select Administration > mod_wl_ohs configuration, and see if the mod_wl_ohs configuration contains your latest change (you added a row for /odsm). It should not. This demonstrates that when recovering by using a backup, some of the latest changes can be lost.

Note: Access FMW Control by using the administration server port: http://fmwhost1.example.com:7001/em

j. Stop OHS using FMW Control. (In FMW Control, select ohs1 under Web Tier and use the Oracle HTTP Server menu selection of Control > Shut Down. When asked if you are sure, click Shutdown.)


k. Copy the latest version of mod_wl_ohs.conf from /stage/backup to /u01/app/oracle/admin/instances/ohs_inst1/config/OHS/ohs1. $> cd /u01/app/oracle/admin/instances/ohs_inst1

$> cd config/OHS/ohs1

$> cp /stage/backup/mod_wl_ohs.conf mod_wl_ohs.conf

l. Start OHS by using FMW Control. (In FMW Control, select ohs1 under Web Tier and use the Oracle HTTP Server menu selection of Control > Start Up.)


m. After OHS has started, in FMW Control, navigate to Web Tier > ohs1. Then using the Oracle HTTP Server menu, select Administration > mod_wl_ohs configuration, and see if the mod_wl_ohs configuration once again contains your latest change (the row for /odsm).

Note: Notice that the latest OHS configuration is available again.

n. Log out of FMW Control and close the web browser.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 11: High Availability

Chapter 11 - Page 1


Chapter 11

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 11 - Page 2



Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 12: Development to Production

Chapter 12 - Page 1


Chapter 12

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 12 - Page 2


Practices Overview In this practice, you run some scripts as if you were moving your environment from development to test or from test to production.










Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 12 - Page 3

Practice 12-1: Cloning Oracle Fusion Middleware

Overview In this practice, you follow a part of the procedure and run some scripts as if you were copying the current environment, (the source system) to a new environment (the target system). This is good practice for moving a development environment to test or a test environment to production. Because there is no target system to which you can copy or clone elements, you will not perform some of the tasks of the procedure, although they are discussed in this practice.

Tasks 1. The first step in copying a system to a new environment is to create a new database in the

target system, or copy the database from the source to the target. There is no target system, and this is beyond the scope of this course, so you will not perform this task.

2. Clone the current environment’s Middleware Home by using the copyBinary.sh script.

a. Open a new Terminal window and navigate to /u01/app/oracle/product/fmw/oracle_common/bin. $> cd /u01/app/oracle/product/fmw/oracle_common/bin

b. Run the copyBinary.sh script. The servers do not need to be stopped first, because the environment is Linux. With the copyBinary.sh script, the first parameter points to the JDK. The second parameter is the location and name of the JAR file to create. The third parameter is the location of the domain to copy. When asked if you wish to proceed, enter yes.

Note: Enter the command on one line. It is shown on multiple lines here due to space limitations:

$> ./copyBinary.sh

-javaHome /u01/app/oracle/product/fmw/jrockit-jdk

-archiveLoc /home/oracle/mw_clone.jar

-sourceMWHomeLoc /u01/app/oracle/product/fmw

Log File: "/tmp/CLONE2012-07-17_12-04-48PM-LOG/CLONE2012-07-17_12-04-48PM.log".

Error File: "/tmp/CLONE2012-07-17_12-04-48PM-LOG/CLONE2012-07-17_12-04-48PM.error".

INFO : Jul 17, 2012 12:04:51 PM - CLONE-21009 The Middleware home that will be included in the archive is /u01/app/oracle/product/fmw.

...

To proceed enter "yes", or any other text to abort: yes

...

Note: Some of the output from the script is shown. This script takes a very long time to run, so watch the script’s output for a while, and then move to the next step.

c. Let the script run for a little while. Because it will take a very long time to complete and the file it creates is very large, after watching it run for a little while, press Ctrl + C in the terminal window to stop it.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 12 - Page 4

d. The file the script created is incomplete because you killed the script (and there is no target system to which to copy it). So delete the file: $> cd /home/oracle

$> rm mw_clone.jar

3. The next step in the process is to move the Middleware Home archive file to the target system, along with <ORACLE_COMMON_HOME>/jlib/cloningclient.jar and <ORACLE_COMMON_HOME>/bin/pasteBinary.sh. In addition, you must have installed the JDK on the target system. Then, at the target system, you use the pasteBinary.sh script to extract the archive. Because in this practice there is no target system, you stopped the copyBinary.sh script before it completed, and you deleted the incomplete archive file, you will not perform this task.

4. Clone the Java components by using the copyConfig.sh script.

a. Stop the administration server because in a later step, you must edit the config.xml configuration file. Use the stopWebLogic.sh script in the domain’s bin directory: $> cd /u01/app/oracle/admin/domains/fmwdomain/bin


b. The copyConfig.sh script requires a file that contains the WebLogic administrator’s password. Create a file in /home/oracle called p.txt. Edit the file to contain the WebLogic Server administrator’s password, Welcome1. Save the file and close the editor when finished: $> cd /home/oracle

$> gedit --new-document p.txt

Note: If any gedit “wrong permissions” warnings appear, ignore them.

c. Another quirk of the copyConfig.sh script is that it cannot handle the “UNIX” machine type in the configuration. Very carefully edit config.xml to remove that type from the machine definition. When in the editor, click the Find button and search for: unix-machineType. $> cd /u01/app/oracle/admin/domains/fmwdomain/config

$> gedit config.xml O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 12 - Page 5

d. Find all instances of the tag <machine xsi:type="unix-machineType"> and

change them to the simple tag <machine>. After the changes are made, save the file and close the editor.

Note: It is absolutely critical that you make no other changes to the file. If there are any errors in the configuration file, the administration server cannot start and no changes to the domain can be made.

e. Start the administration server. The administration server must be running for the copyConfig.sh script to work. Use the 07_wlst_start_adm.sh script found in /home/oracle/admin_scripts or the startWebLogic.sh script found in the bin directory of the domain: $> cd /home/oracle/admin_scripts

$> ./07_wlst_start_adm.sh

f. Next ensure that all the managed servers in the domain are running by using Fusion Middleware Control. All managed servers in the domain must be running for the copyConfig.sh script to work. Open a web browser and enter the URL for Fusion Middleware Control, http://fmwhost1.example.com:7777/em. Log in with the usual username (weblogic) and password (Welcome1).

g. Look at the farm home page, the Fusion Middleware chart. If there are any servers that are not running, in the Target Navigation Pane, expand WebLogic Domain and select fmwdomain. Then use the WebLogic Domain menu to select Control > Start Up. Wait for all the servers to successfully come up before continuing.

h. All SOA Composite applications must be active for the cloning process to work. In case instances of the deployed composite are “stale” or in some other state, you will delete all instances of the SOA Composite. 1) In the Target Navigation Pane, expand SOA > soa-infra > default.

2) Select HelloWorldComposite.

3) Click the Instances tab.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 12 - Page 6

4) Above the table, click the Delete With Options button.

5) In the Delete With Options window, select Delete All Instances Of This Composite and click the Delete button.

6) When asked if you are sure, click the Delete button.

7) Close the Confirmation message by clicking the “X.”

i. Log out of Fusion Middleware Control and close the web browser.

j. In a Terminal window, navigate to /u01/app/oracle/product/fmw/oracle_common/bin. $> cd /u01/app/oracle/product/fmw/oracle_common/bin

k. Run the copyConfig.sh script to create an archive of the Java components. The first parameter of the script points to the JDK. The second parameter is the location and name of the JAR file to create. The third parameter is the location of the domain to copy. The fourth parameter is the location of MW_HOME. The next parameters are the domain host name, the domain administration server port, and an administrator’s user name. The next parameter is the location of a file that contains the administrator’s password. The final parameter says not to import MDS data into the archive. When you run the script, you will be asked if you wish to proceed. Enter yes.


$> ./copyConfig.sh


-archiveLoc /home/oracle/configcopy.jar

-sourceDomainLoc /u01/app/oracle/admin/domains/fmwdomain

-sourceMWHomeLoc /u01/app/oracle/product/fmw

-domainHostName fmwhost1.example.com

-domainPortNum 7001

-domainAdminUserName weblogic

-domainAdminPassword /home/oracle/p.txt

-mdsDataImport false



To proceed enter "yes", or any other text to abort:yes

...

INFO : Jul 17, 2012 2:27:09 PM - CLONE-21032 Archive created successfully at /home/oracle/configcopy.jar.

INFO : Jul 17, 2012 2:27:09 PM - CLONE-21006 Total time taken by cloningclient was "88" seconds.

INFO : Jul 17, 2012 2:27:09 PM - CLONE-21007 Cloning operation completed successfully.

Note: Some of the output from the script is shown. This script will take a few minutes to complete.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 12 - Page 7

l. See how big the created file is: $> cd /home/oracle

$> ls configcopy.jar –lh

-rw-r--r-- 1 oracle oinstall 22M Jul 17 12:05 configcopy.jar

Note: In this example, the file is 22 MB.

5. Next, extract the move plan from the cloned Java components archive by using the extractMovePlan.sh script.

a. In a Terminal window, navigate to the script’s location. $> cd /u01/app/oracle/product/fmw/oracle_common/bin

b. Run the extractMovePlan.sh script. The first parameter points to the JDK. The second parameter is the location of the cloned Java components archive. The third parameter is the directory where to put the move plan and other files that are extracted. (The directory must not already exist.)


$> ./extractMovePlan.sh



-planDirLoc /home/oracle/moveplans



INFO : Jul 17, 2012 3:07:07 PM - CLONE-23300 Configplans have been extracted at "/home/oracle/moveplans".

INFO : Jul 17, 2012 3:07:07 PM - CLONE-23301 ExtractMovePlan operation completed successfully.

c. Observe the files and directories created. $> cd /home/oracle/moveplans

$> ls

composites deployment_plans moveplan.xml

Notes

• Notice the move plan file, moveplan.xml, which contains values that can be edited for the target environment. Also notice the directories composites and deployment_plans, containing configuration plan files for SOA composite applications and deployment plans for Java EE applications, respectively. These composite configuration plans and deployment plans can also be edited to change values within them and used in the target environment.

• If either or both of the directories are not created, it could be that you do not have SOA Composite applications or Java EE applications in the configuration.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 12 - Page 8

d. Open moveplan.xml in an editor. Notice, for example, where you could change the Listen Address and the Listen Port of the server called wls_soa1. Observe the file some more if you wish, but do not make any changes yet. Do not close the editor. $> cd /home/oracle/moveplans

$> gedit moveplan.xml

Notes

• If you want to change the Listen Port for this server, there are other places in the configuration file that might also have to change. For example, in this domain, the Cluster Address also contains that port number.

• If any gedit “wrong permissions” warnings appear, ignore them.

6. The next step in the process is to move the archive to the target system and run the script pasteConfig.sh. There is no target system, but you will perform part of this task on the current system as if it were the target system.

a. For the pasteConfig.sh script to work, each data source and some security entries in the moveplan.xml file must point to a file that contains its password. The data source passwords and the OPSS security passwords are all the same as the WebLogic Server administrator’s password (Welcome1). Therefore, each element can point to the file already created, /home/oracle/p.txt. In the editor, click the Find button and search for: DATASOURCE.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 12 - Page 9

b. Scroll down within this <configGroup> element of <type>DATASOURCE</type> to

find all the <configProperty id="DataSourceN"> (where N is some number) tags. Within each of those, find the <configProperty> with the <name>Password File</name>.

c. Change each one so that the <value/> tag becomes:

<value>/home/oracle/p.txt</value>

d. Use the Find button and search for Password File to help you find them all. When

you find each one, edit its <value/> tag in the same way. When finished, save the file and close the editor.

e. You will now run the pasteConfig.sh script on the current system as if it were the target system. The script should fail if any of your domain’s servers are running. The new domain the script is trying to create uses the same ports as the servers in the current domain, so the script fails when it checks if those ports are free. This is a good thing, because you do not want a copy of your domain on this system. When you run the script, you will be asked if you wish to proceed. Enter yes.

Note: Enter the command on one line. It is shown on multiple lines here due to space limitations. O

racl

e U

nive

rsity

and

(Ora

cle

Cor

pora

tion)

use

onl

y.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 12 - Page 10

IMPORTANT NOTE: If the script does not fail on its own (perhaps the servers in the current domain are not running), do NOT let the script keep going. Watch the output for a short while and then press Ctrl + C.

$> cd /u01/app/oracle/product/fmw/oracle_common/bin

$> ./pasteConfig.sh



-targetDomainLoc /u01/app/oracle/admin/scratch/domain

-targetMWHomeLoc /u01/app/oracle/product/fmw

-movePlanLoc /home/oracle/moveplans/moveplan.xml

-domainAdminPassword /home/oracle/p.txt

Log File: "/tmp/CLONE2012-07-18_08-10-08AM-LOG/CLONE2012-07-18_08-10-08AM.log".

Error File: "/tmp/CLONE2012-07-18_08-10-08AM-LOG/CLONE2012-07-18_08-10-08AM.error".

To proceed enter "yes", or any other text to abort:yes

...

INFO : Jul 28, 2012 1:02:14 PM - CLONE-23282 Reading the extracted domain template and pasting server, machine, cluster, datasource configuration changes...

INFO : Jul 28, 2012 1:02:14 PM - CLONE-23287 Paste Server Configuration.

SEVERE : Jul 28, 2012 1:02:14 PM - ERROR - CLONE-20372 Server port validation failed....

...

$>

7. The next step in the process is to clone the System components, such as OHS, by using the copyConfig.sh script again. As with the Java components, you use the extractMovePlan.sh script to extract the move plan from the cloned System components archive and edit values for the target system. You move the System components archive and the move plan directory to the target system, and once again use the pasteConfig.sh script to extract the archive and use the information in the move plan file to update configuration values. Because you have practiced using these scripts with the Java components, you will not perform these tasks.

8. Clean up files and directories not needed. Be very careful with the rm -rf command because it will remove a directory and all the files and subdirectories under it. Do not accidentally delete a directory and files that are needed.

a. Delete the moveplans directory under /home/oracle: $> cd /home/oracle

$> rm –rf moveplans

b. Delete the p.txt file under /home/oracle: $> rm p.txt

c. Delete the configcopy.jar file under /home/oracle: $> rm configcopy.jar

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.




d. If the pasteConfig.sh script did not fail on its own (you had to kill it by pressing Ctrl + C), then it may have created a part of the new domain. The new domain was to be placed in the scratch directory under /u01/app/oracle/admin, so, if the scratch directory exists, remove it.

Note: Do not remove anything else under the admin directory! $> cd /u01/app/oracle/admin

$> rm –rf scratch

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.




Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.


Practices for Lesson 13: Fusion Middleware Performance

Chapter 13 - Page 1


Chapter 13

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 13 - Page 2


Practices Overview In these practices, you create work managers, tune a JDBC connection pool, and tune some Oracle SOA Suite parameters.










Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 13 - Page 3

Practice 13-1: Creating a Work Manager

Overview In this practice, you create two work managers, two fair share request classes, and two “max threads” constraints. You use the request classes and the constraints in the new work managers. The strategy is for developers to assign the “higher priority” work manager to higher priority applications deployed to demoserver1 and the “lower priority” work manager is assigned to the rest of the applications deployed to that server.

Tasks 1. Access the WebLogic Server Administration Console and create two fair share request

classes.

a. Open a web browser and enter the URL for the Administration Console, http://fmwhost1.example.com:7777/console. Log in with weblogic and Welcome1.

b. In the Change Center, click Lock & Edit.

c. In the Domain Structure expand Environment, and select Work Managers.

d. On the right, click the New button.

e. Select Fair Share Request Class and click Next.

f. In the Name field, enter LowerShare. In the Fair Share field, enter 300. Click Next.

g. For the target, select demoserver1. Click Finish.

h. Follow the same procedure to create another fair share request class called HigherShare with a Fair Share value of 500. Target this fair share request class to demoserver1 as well.

i. In the Change Center, click Activate Changes.

2. Create two “max threads” constraints. a. In the Change Center, click Lock & Edit.

b. In the Domain Structure, expand Environment, and click Work Managers.

c. On the right, click the New button.

d. Select Maximum Threads Constraint and click Next.

e. Enter LowerMaxThreads in the Name field. Enter 15 in the Count field. (Leave the Data Source field blank.) Click Next.

f. For the target, select demoserver1. Click Finish.

g. Follow the same procedure to create another maximum threads constraint called HigherMaxThreads with a Count value of 20. Target this maximum threads constraint to demoserver1 as well.

h. In the Change Center, click Activate Changes.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 13 - Page 4

3. Create two new work managers and set their configurations. a. In the Change Center, click Lock & Edit.

b. In the Domain Structure, expand Environment, and click Work Managers.

c. On the right, click the New button.

d. Select Work Manager and click Next.

e. In the Name field, enter LowerPriorityWorkManager. Click Next.

f. For the target, select demoserver1. Click Finish.

g. In the table, select the new work manager, LowerPriorityWorkManager.

h. Under the Configuration tab, for the Request Class, select LowerShare. For Maximum Threads Constraint select LowerMaxThreads. Leave all other fields as they are. Click Save.

i. Click the Targets tab. Ensure that demoserver1 is selected. If not, select it and click

Save.

j. In the Domain Structure, expand Environment, and click Work Managers.

k. On the right, click the New button.

l. Select Work Manager and click Next.

m. In the Name field, enter HigherPriorityWorkManager. Click Next.

n. For the target, select demoserver1. Click Finish.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 13 - Page 5

o. In the table, select the new work manager, HigherPriorityWorkManager.

p. Under the Configuration tab, for the Request Class select HigherShare. For Maximum Threads Constraint, select HigherMaxThreads. Leave all other fields as they are. Click Save.

q. Click the Targets tab. Ensure that demoserver1 is selected. If not, select it and click

Save.

r. In the Change Center, click Activate Changes.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 13 - Page 6

4. LowerPriorityWorkManager should be used by most applications deployed to demoserver1. Some applications, that are deemed more important, should use the other work manager, HigherPriorityWorkManager. Developers should add an element called <wl-dispatch-policy> to the WebLogic deployment descriptor of the Java EE applications they develop. That element names the work manager to use for the application. An example of the element is shown here with the value for the higher priority work manager:

<wl-dispatch-policy>

HigherPriorityWorkManager

</wl-dispatch-policy>

Note: After the deployment descriptor is modified to reference the correct work manager, that application would be redeployed. The value of this element could also be modified by using a deployment plan.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 13 - Page 7

Practice 13-2: Tuning a Connection Pool

Overview In this practice, the scenario is that the DBAs have read the documentation and done some experimentation, and have given you recommendations for tuning two SOA Suite databases. You make some modifications to the appropriate connection pools to (hopefully) improve their performance.

Note: The values for various attributes in this practice are for demonstration purposes only and should not be taken as recommendations.

Tasks 1. Log in to Fusion Middleware control and access the data sources.

a. Access Fusion Middleware Control. Open a web browser and enter its URL, http://fmwhost1.example.com:7777/em. Log in with weblogic and Welcome1.

b. In the Target Navigation Pane, expand elements until you can select the fmwdomain domain. Then use the WebLogic Domain menu to select JDBC Data Sources.

2. Use Fusion Middleware Control to modify the values of the appropriate data sources. a. In the JDBC Data Sources table, select EDNDataSource. (This data source is used by

SOA Suite’s Event Delivery Network.)

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 13 - Page 8

b. Click the Transaction Properties tab. The Administrator’s Guide for Oracle SOA Suite and Oracle Business Process Management Suite recommends setting an XA transaction timeout for this data source and the SOADataSource. (The default is no transaction timeout.) Select the check box for Set XA Transaction Timeout. The DBAs have decided on the timeout value of 20 seconds. Enter 20 in the XA Transaction Timeout field. Leave all other fields at their default values. When finished, click the Apply button.

c. Notice the confirmation message. The data source needs to be redeployed or the

server(s) need to be restarted. You will restart the server later. Click the “X” in the top right of the Confirmation box to close it.

Note: A change to any field with the red and green arrow icon requires a data source redeployment or server restart.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.



Chapter 13 - Page 9

Select EDNDataSource again. This time click the Connection Properties tab. The DBAs have determined the values desired for connection pool properties. Enter or select these values for the following fields, and then click the Apply button:

• Initial Capacity: 15

• Maximum Capacity: 15

• Capacity Increment: 1

• Statement Cache Type: LRU

• Statement Cache Size: 12


d. There should be a confirmation message that the data source has been updated.

e. Follow a similar procedure to change the settings of the data source called SOADataSource. You can wait to click the Apply button after all the changes have been made. Here are the attributes and their desired values:

• Transaction Properties

− Set XA Transaction Timeout: selected

− XA Transaction Timeout: 10

• Connection Properties

− Initial Capacity: 10

− Maximum Capacity: 20

− Capacity Increment: 5

− Statement Cache Type: LRU

− Statement Cache Size: 10


Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.




3. Stop and start the server in the cluster. (The cluster is the target of the modified data sources.) a. In the Target Navigation Pane, expand elements until you can select the cluster_soa

cluster. Then use the WebLogic Cluster menu to select Control > Shut Down. When asked if you are sure, click the Shutdown button. When the server in the cluster has finished shutting down, click the Close button.

b. Now use the WebLogic Cluster menu to select Control > Start Up. Wait for the server to successfully start, and close the message window before continuing.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.




Practice 13-3: Tuning SOA Suite

Overview In this practice, you will tune some Oracle SOA Suite properties.

Tasks 1. Log in to Fusion Middleware control.

a. Access Fusion Middleware Control. Open a web browser and enter its URL http://fmwhost1.example.com/em. Log in with weblogic and Welcome1.

2. Set some SOA Infrastructure common properties. Set the Audit Level to Production, deselect Capture Composite Instance State, change fetching metrics to be on demand, and set a default search criteria time period for fetching recent instances and faults. a. In the Target Navigation Pane, expand SOA, then select soa-infra.

b. From the SOA Infrastructure menu, select SOA Administration > Common

Properties.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.




c. Use the Audit Level drop-down list to select Production. Also ensure that Capture Composite Instance State is deselected.

d. Scroll down on the screen to view the Data Display Options. Select Disable fetching

of instance and fault count metrics.

Note: Rather than periodically fetching metrics and displaying them, the metrics are replaced with links to retrieve metrics on demand. This setting can improve the time it takes to load pages in Fusion Middleware Control.

e. Also select Set default search criteria to fetch recent instances and faults only within a recent duration. This enables the Duration Details and time unit fields. Set the Duration Details field to 12 and the time unit to hours. This means that when recent instances, faults, and count metrics are retrieved, only those that occurred within the last 12 hours will be gathered.

Note: It is highly recommended that you set a time period duration because it has a significant impact on the performance of multiple Oracle Enterprise Manager Fusion Middleware Control pages and queries. f. When finished setting these properties, click the Apply button.

g. When asked if you wish to continue, click Yes.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.




h. A confirmation message appears. Close it by clicking “X.”

3. Set the logging level for SOA Suite logs to ERROR.

a. From the SOA Infrastructure menu, select Logs > Log Configuration.

b. Use the drop-down list to set the level of the oracle-soa category to ERROR. (Other

loggers or categories can be set to ERROR as well, if desired.)

Note: According to the Oracle Fusion Middleware Administrator’s Guide, none of the settings at level 1 (INCIDENT_ERROR, ERROR, WARNING, and NOTIFICATION) have a performance impact. However, it has been decided that in production, you need to see only errors. c. Click the Apply button.

d. A confirmation window appears. After the message that “The log levels have been updated successfully,” close the window by clicking the Close button.

e. Log out of Fusion Middleware Control and close the web browser.

Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.




Ora

cle

Uni

vers

ity a

nd (O

racl

e C

orpo

ratio

n) u

se o

nly.

Thes

e eK

it m

ater

ials

are

to b

e us

ed O

NLY

by

you

for t

he e

xpre

ss p

urpo

se S

ELF

STU

DY.

SH

ARIN

G T

HE

FILE

IS S

TRIC

TLY

PRO

HIB

ITED

.

oracle fusion middleware 11 g administration...

Documents