Upgrading Oracle Middleware 11g; How to Check that the Core Components are Running Successfully? [ID 1086348.

1] Modified 04-AUG-2011 Type BULLETIN Status PUBLISHED

In this Document Purpose Scope and Application Upgrading Oracle Middleware 11g; How to Check that the Core Components are Running Successfully? Introduction and Terminology Check The State of the Core Oracle Middleware 11g Components Starting and Stopping Core Oracle Middleware 11g Components Additional Advice Useful Documentation References: References

Applies to:
Oracle Fusion Middleware - Version: 11.1.1.2.0 to 11.1.1.4.0 - Release: Oracle11g to Oracle11g Information in this document applies to any platform.

Purpose
When upgrading to Oracle Middleware 11g it is essential, at the various stages in the process, to test that the key components are fully operational. Depending on the chosen Oracle Middleware 11g Install type, these components can include: Oracle WebLogic Server Oracle Web Cache Oracle HTTP Server Fusion Middleware Control

Oracle Middleware 11g install types such as "Portal/Forms/Reports/Discoverer" will include all of the above. Other types like "SOA" and "WebCenter" will not feature "WebCache" and "HTTP Server" The purpose of this article is to describe how to test each component to ensure that they can be successfully started.

Scope and Application

The article is intended for Middleware administrators, consultants and support engineers.

Upgrading Oracle Middleware 11g; How to Check that the Core Components are Running Successfully? Introduction and Terminology

Before reading the advice below, become familiar with the new Fusion Middleware architecture and terminology. The following chapter is a good place to start: Oracle Fusion Middleware Installation Planning Guide 11g Release 1 (11.1.1) chapter 1 Installation Overview and Oracle Fusion Middleware Upgrade Planning Guide 11g Release 1 (11.1.1) Chapter 2 Introduction to Oracle Fusion Middleware for 10g Users The following terminology will be used in the document, you may want to make a note of how these map onto your environment. MW_HOME e.g /oracle/app/product/oracle/Middleware ORACLE_HOME e.g /oracle/app/product/oracle/Middleware/PFRD_Binaries ORACLE_INSTANCE e.g /oracle/app/product/oracle/Middleware/instances/asinst_1 WL_HOME e.g /oracle/app/product/oracle/Middleware/wlserver_10.3 DOMAIN_HOME e.g /oracle/app/product/oracle/Middleware/user_projects/domains/FRDomain

Check The State of the Core Oracle Middleware 11g Components

WebCache / HTTP Server To check the status of Web Cache and HTTP Server use the opmnctl command from the operarating system. Run the opmnctl status command from the INSTANCE_HOME/bin (on UNIX operating systems) or INSTANCE_HOME\bin (on Windows operating systems) directory in your instance home location. The example below shows the output on a UNIX system:
> ./opmnctl status Processes in Instance: asinst_1 ---------------------------------+--------------------+---------+--------ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------emagent_asinst_1 | EMAGENT | 11849 | Alive wc1 | WebCache-admin | 11333 | Alive wc1 | WebCache | 11332 | Alive ohs1 | OHS | 11207 | Alive

This information shows the components configured for this installation. The status "Alive" means the component is up and running. You can also run the opmnctl status -l command to obtain a list of ports used by the components. The example below shows output on a UNIX system from an Oracle Forms / Reports Services Instance
> ./opmnctl status -l Processes in Instance: asinst_1 ---------------------------------+--------------------+---------+----------+-----------+----------+-----------+-----ias-component | process-type | pid | status | uid | memused | uptime | ports ---------------------------------+--------------------+---------+----------+-----------+----------+-----------+-----emagent_asinst_1 | EMAGENT | 11849 | Alive | 1133259606 | 4204 | 0:09:38 | N/A

wc1 | WebCache-admin | 11333 | Alive | 1133259605 | 43736 | 0:15:35 | http_admin:8091 wc1 | WebCache | 11332 | Alive | 1133259604 | 63940 | 0:15:35 | http_stat:8092,http_invalidation:8093,https_listen:8094,http_listen:8090 ohs1 | OHS | 11207 | Alive | 1133259603 | 50744 | 0:15:43 | https:8889,https:8890,http:8

If WebCache and the HTTP server are running you should be able to access the Welcome Page below using the URL http://server_name.domain:<webcache listen port number> or http://server_name.domain:<HTTP Server listen port number>

Fusion Middleware Control To display Fusion Middleware Control, enter the Fusion Middleware Control URL, which includes the name of the host and the port number assigned during the installation. The following shows the format of the URL: http://hostname.domain:<weblogic admin server port>/em e.g http://mycompany.oracle.com:7001/em

http://10.72.5.19.reynoldspkg.rpg.local:7001/em

Enter the Oracle Fusion Middleware administrator user name and password and click Login. The default user name for the administrator user is weblogic. The password is the one you supplied during the installation of Oracle Fusion Middleware. For the Fusion Middleware Control to work the WebLogic Admin Server and EM Agent components must be started. The EM Agent component is started via OPMN. See instructions below. After logging into Fusion Middleware Control you will be able to view the status of all components in the Middleware Home. See example screenshots below. These show an Oracle Instance / WebLogic Domain containing Forms / Reports Services.

WebLogic Administration Server and Console

The easiest way to test whether the Oracle WebLogic Adminstration Server is up and running is to try and access the console. Assuming you are using the default port 7001 the url will be :http://host:domain:7001/console

If the page is not available then start the Administration Server. See start / stop instructions below. Once logged in you can view the status of all weblogic servers in the domain. See example screenshot below

Weblogic Managed Servers The status of the managed servers can viewed via the WebLogic Admin Console or the Fusion Middleware Control. See details above. You can also view the status via the command line. For this method to work the NodeManager process / service must be started. Steps as follows: Unix: 1. Check NodeManager is started Unix : ps -ef | grep NodeManager If NodeManager is not started, start the process using the shell script

WL_HOME/server/bin/startNodeManager.sh

MS Windows: NodeManager should be installed as a MS Windows Service. Ensure this service is started 2. Set up the environment variable to run WLST Unix:
cd MW_HOME/user_projects/domains/<domain name>/bin . ./setDomainEnv.sh

MS Windows Command Prompt

cd MW_HOME\user_projects\domains\<domain name>\bin setDomainEnv.cmd

3. Launch the WLST shell and connect to the Admin Server e.g
java weblogic.WLST Initializing WebLogic Scripting Tool (WLST) ... Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands wls:/offline> connect('weblogic','manager11g','demohost.us.oracle.com:7001') Connecting to t3://demohost.us.oracle.com:7001 with userid weblogic ... Successfully connected to Admin Server 'AdminServer' that belongs to domain 'FRDomain_SP'. Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead.

The warning can be ignored 5. Now run the state command for the Weblogic Servers configured in the domain. The example output below examines the state of the Forms and Reports Weblogic Managed Servers - WLS_FORMS and WLS_REPORTS
wls:/FRDomain_SP/serverConfig> state('WLS_FORMS','Server') Current state of 'WLS_FORMS' : RUNNING wls:/FRDomain_SP/serverConfig> state('WLS_REPORTS','Server') Current state of 'WLS_REPORTS' : RUNNING

Starting and Stopping Core Oracle Middleware 11g Components

OPMN Managed Components: WebCache / HTTP Server / EM Agent If the WebCache and HTTP Server components are showing as "Down" then they need to be started from the ORACLE_INSTANCE directory
$ORACLE_INSTANCE/bin/opmnctl startall

Alternatively you can start components individually

$ORACLE_INSTANCE/bin/opmnctl startall $ORACLE_INSTANCE/bin/opmnctl startproc ias-component=component_name

To start Oracle HTTP Server, ohs1

$ORACLE_INSTANCE/bin/opmnctl startproc ias-component=ohs1

For further information regarding opmnctl refer to the following manual:Oracle Fusion Middleware Oracle Process Manager and Notification Server Administrator's Guide Release 11g (11.1.1.2.0) Oracle WebLogic Server Administration Server If the Admin Console page is not available then start the Administration Server, use the following script, which is based on WebLogic Scripting Tool (WLST) commands:
Unix: MW_HOME/user_projects/domains/domain_name/bin/startWebLogic.sh MS Windows: MW_HOME\user_projects\domains\domain_name\bin\startWebLogic.cmd

The shell / command script will prompt for the username (i.e weblogic) and password (i.e the one specified at install / configuration time). Alternatively you can pass this values on the command line e.g
Unix: MW_HOME/user_projects/domains/domain_name/bin/startWebLogic.sh Dweblogic.management.username=weblogic -Dweblogic.management.password=password Dweblogic.system.StoreBootIdentity=true MS Windows: MW_HOME\user_projects\domains\domain_name\bin\startWebLogic.cmd Dweblogic.management.username=weblogic -Dweblogic.management.password=password Dweblogic.system.StoreBootIdentity=true

To stop an Administration Server, use the following script:MW_HOME/user_projects/domains/domain_name/bin/stopWeblogic.sh username password admin_url

Log files can be located in:MW_HOME/user_projects/domains/domain_name/servers/AdminServer/logs Managed Servers e.g WLS_FORMS, WLS_REPORTS If the Managed Servers are showing as down, they need to be started, there are numerous ways to start the Managed Servers:From the operating system:1) Navigate to your domain bin directory MW_HOME/user_projects/domains/domain_name/bin 2) Issue the following commands seperately, entering the weblogic username and password when

prompted - examples below are for stopping and starting the Forms and Reports Weblogic Managed Servers
./startManagedWeblogic.sh WLS_FORMS http://administration_server_host:7001 ./startManagedWeblogic.sh WLS_REPORTS http://administration_server_host:7001

3) Log files can be found in ORACLE_HOME/user_projects/domains/domain_name/servers/WLS_FORMS/logs/WLS_FORMS.log ORACLE_HOME/user_projects/domains/domain_name/servers/WLS_REPORTS/logs/WLS_REPORTS.l og You can also start the Managed Servers via the WebLogic Admin Console. To do this, however, the nodemanager needs to be up and running. On Unix the NodeManager can be started using the command
WL_HOME/server/bin/startNodeManager.sh

On MS Windows NodeManager should exist as a MS Windows Service - as such ensure this service is started. The advantages of using NodeManager, compared to stop/ start via the WebLogic shell script, are The managed servers will be automatically started in the background The NodeManager daemon will monitor the status of the servers and restart them if the processes are terminated

Reference: Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server 11g Release 1 (10.3.1) For further information about starting and stopping WebLogic Managed Servers read: Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server 11g Release 1 (10.3.1) Additional Useful Reference: How to Install MS Windows Services For FMW 11g WebLogic Admin and Managed Servers? (Note:1060058.1)

Additional Advice
If your chosen product / service is integrated with Single Sign-On - for example Oracle Portal - then remember to check that the Oracle Identity Management components are up and running. In this respect there are two scenarios: An Oracle Identity Management 10g (OID,DIP,SSO and OIDDAS) architecture is being used. If this is the case the check and start up of the Identity Management components is only required in the 10g Oracle Home or Home (depending on whether the Identity Management architecture is co-located or distributed)

Oracle Identity Management (OID and DIP) components may have been upgraded to 11g - with SSO and OIDDAS remaining at 10g If this is the case the check and start up of the Identity Management components is performed in the 11g and 10g homes.

Useful Documentation References:

Oracle Fusion Middleware Administrator's Guide 11g Release 1 (11.1.1) Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache 11g Release 1 (11.1.1) Oracle Fusion Middleware Administrator's Guide for Oracle HTTP Server 11g Release 1 (11.1.1) Oracle Fusion Middleware Oracle Process Manager and Notification Server Administrator's Guide Release 11g Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server 11g Release 1 (10.3.3) Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server 11g Release 1 (10.3.3)

References
NOTE:1060855.1 - Sample Script To Startup A Fusion Middleware Instance Without Node Manager NOTE:1077087.1 - Getting Started with Oracle WebLogic Server: Setting Up a Domain and Node Manager