Skip Headers
Oracle® Fusion Applications Administrator's Guide
11g Release 1 (11.1.1.5)

Part Number E14496-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

3 Performing Routine Administrative Tasks

This chapter describes the common, essential tasks for administering your Oracle Fusion Applications environment.

This chapter contains the following topics:

3.1 Introduction to Performing Routine Administrative Tasks

An important aspect of system administration of the Oracle Fusion Applications environment is performing a range of maintenance life-cycle and management operations. Section 1.3 provides a roadmap of when to perform these essential administrative tasks. In addition to following this roadmap, if you run into performance or security issues, then use the tasks in the chapter to maintain the environment.

In addition to the tasks in this guide, refer to the following documentation for tasks that you may need to perform, depending on your business needs:

3.2 Running Administration Servers and Managed Servers from Shared and Local Disks

Configuration for domains is stored centrally on a shared disk. This location is accessible to all hosts, so the Administration Servers can run from this shared location. Managed Servers can run from either the shared location or from a local disk, that is, a non-network disk, visible only to the processes running on that host. During provisioning of Oracle Fusion Applications, in the Installation Location page of the Provisioning Wizard, you make this decision with the Enable Local Application Configuration option. When you select this option, provisioning copies the domain configuration from the shared server location to the specified local disk, and you run the Managed Servers from the local disk. If you chose not to select this option, then all the Managed Servers are configured to run from the shared disk. See the "Installation Location" section in the Oracle Fusion Applications Installation Guide for information about using the Installation Location page.

3.3 Starting and Stopping

You start and stop the Oracle Fusion Applications environment and its components to perform a range of maintenance operations that require process downtime. Understanding the state (that is, up, down, starting, and stopping) of each component in the Oracle Fusion Applications environment is an essential activity when diagnosing and resolving availability and performance issues, and when performing life-cycle and management operations.

A typical Oracle Fusion Applications environment contains the applications, the Oracle Database, and the Oracle Fusion Middleware components. Depending on whether you need to start and stop an individual component or the entire environment, there are many several supported scenarios for performing these operations correctly.

This sections contains the following topics:

3.3.1 Starting and Stopping Components in the Oracle Fusion Applications Environment

For many of the Oracle Fusion Middleware components, you can start and stop in different ways, depending on your requirements. In most situations, you can use Fusion Applications Control, Oracle WebLogic Server Administration Console, or the Oracle WebLogic Scripting Tool (WLST) or Oracle Process Manager and Notification Server (OPMN) commands to start or stop Oracle Fusion Middleware components.

Table 3-1 describes the Oracle Fusion Applications, Oracle Fusion Middleware, and Oracle Database components you can start and stop, and provides information on where to find related documentation for each component.

The procedures referenced in the Oracle Fusion Middleware guides describe using Fusion Middleware Control. These procedure also apply to Fusion Applications Control.

Table 3-1 Starting and Stopping

Component Description Documentation

Oracle Fusion Applications

Oracle Fusion applications

You can start and stop applications using the WLST command line, the WebLogic Server Administration Console, or Fusion Applications Control.

Section 3.3.6

Oracle Fusion Middleware

Administration Server

The Administration server operates as the central control entity for the configuration of the entire Oracle WebLogic Server domain. It maintains the domain's configuration documents and distributes changes in the configuration documents to Managed Servers. The Administration Server serves as a central location from which to manage and monitor all resources in a domain.

Oracle WebLogic Server provides several ways to start and stop server instances. The method that you choose depends on whether you prefer using a command-line interface, and on whether you are using Node Manager to manage the server's life cycle.

Section 3.2

"Starting an Administration Server with a Startup Script" section in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

"Starting an Administration Server from the Windows Start Menu" section in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

"Starting an Administration Server with the java weblogic.Server Command" section in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

"Starting an Administration Server Using WLST and Node Manager" section in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

"Starting an Administration Server Using WLST Without Node Manager" section in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

Node Manager

Node Manager is an Oracle WebLogic Server utility that enables you to start, shut down, and restart the Administration Server and the Managed Server instances.

On Windows, Node Manager is configured to automatically start by default.

"Node Manager Overview" section in the Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server

Task 3, "Start Node Manager"

Managed Server for an application

Managed Servers host business applications, application components, Web services, and their associated resources.

Oracle WebLogic Server provides several ways to start and stop server instances. The method that you choose depends on whether you prefer using the Fusion Applications Control, Oracle WebLogic Server Administration Console, or a command-line interface, and on whether you are using Node Manager to manage the server's life cycle.

Section 3.2

"Starting Managed Servers with a Startup Script" section in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

"Starting Managed Servers with the java weblogic.Server Command" section in the Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

"Starting and Stopping Managed Servers Using Fusion Middleware Control" section in Oracle Fusion Middleware Administrator's Guide

"Start Managed Servers in a cluster" and "Shutdown servers in a cluster" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help

Oracle Business Intelligence Suite

You can use Fusion Applications Control or the opmnctl command to start and stop Oracle Business Intelligence system components.

"Starting and Stopping Oracle Business Intelligence" chapter in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition

Oracle Enterprise Scheduler Service

You can use Fusion Applications Control to start and stop the Oracle Enterprise Scheduler Service.

Section 5.6

Oracle HTTP Server

You can use Fusion Applications Control or the opmnctl command to start and stop Oracle HTTP Server.

"Starting, Stopping, and Restarting Oracle HTTP Server" section in the Oracle Fusion Middleware Administrator's Guide for Oracle HTTP Server

Oracle WebLogic Server domain for a product family

When applying a patch that only applies to a product family, you can stop the Oracle WebLogic Server domain for the product family and restart it after you apply the patch without stopping the entire Oracle Fusion Applications environment. You can use Fusion Applications Control to start and stop an Oracle WebLogic Server domain.

Section 3.3.4

Oracle WebLogic Server cluster for a product family

If you modify the Oracle WebLogic Server configuration, you must stop and restart the cluster for the configuration changes to take effect.

You can start and stop Oracle WebLogic Server clusters with either Fusion Applications Control, Node Manager, or a startup script.

Section 3.3.5.3 for Fusion Applications Control

"Using Node Manager to Start Managed Servers in a WebLogic Domain or Cluster" section in Oracle Fusion Middleware Oracle WebLogic Scripting Tool

"Starting Managed Servers with a Startup Script" section in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

Oracle Database

Oracle Database

You can start and stop the Oracle database with the Oracle Enterprise Manager Database Control.

"Accessing the Database Home Page" section in the Oracle Database 2 Day DBA


3.3.2 Starting and Stopping the Entire Oracle Fusion Applications Environment

Some components in the Oracle Fusion Applications environment dependent on one another. Therefore, it is important to start and stop components in the proper order. In the course of normal IT operations, common operations include shutting down computers and starting them back up. Therefore, it is crucial to start and stop Oracle Fusion Applications in a sequential manner.

This section contains the following topics:

3.3.2.1 Starting an Oracle Fusion Applications Environment

To perform a complete start of the Oracle Fusion Applications environment, you must start the Oracle WebLogic Server domain for the Oracle Fusion Setup product family before the domains for the other product families.

Applications may not work correctly until all the Managed Servers in all domains have been started.

The section contains the following topics for performing a complete start of the Oracle Fusion Applications environment:

The fastartstop utility provides an alternative way to starting the Administration Servers and Managed Servers for all the product families in one step. See Section 3.3.3.

Task 1   Start the Oracle Database

To start the Oracle database instance using Oracle Database Control:

  1. Go to the Database Home page.

    For information about how to access the Database Home page in Oracle Enterprise Manager, see "Accessing the Database Home Page" section in the Oracle Database 2 Day DBA.

  2. In the Database Home page, click Startup.

    The Startup/Shutdown Credentials page appears.

  3. Enter credentials as follows:

    1. Enter the host computer credentials of the user who installed Oracle Database, or of any user who is authorized to use SQL*Plus.

    2. Enter the database credentials consisting of the user name SYS and the password that you assigned to SYS during the installation.

    3. From the Connect As list, select SYSOPER.

  4. Click OK.

    A confirmation page appears.

  5. Click Yes.

    The Startup page appears, indicating that the database is being started up. When startup is complete, the Login page appears.

  6. Log in to the database.

    The Database Home page appears indicating that the database instance status is Up.

For information about shutting down and starting up the Oracle database instance, see the "Shutting Down and Starting Up the Oracle Instance" section in the Oracle Database 2 Day DBA.

Task 2   Start the Oracle Identity Management Suite

To start the Oracle Identity Management system components:

  1. Set the ORACLE_HOME environment variable to the Oracle home for the Oracle Identity Management components.

  2. Start Oracle Process Manager and Notification Server (OPMN) and all system components:

    opmnctl startall
    
Task 3   Start the Administration Servers

You must start the Oracle WebLogic Server Administration Server for the CommonDomain domain in the Oracle Fusion Setup product family from a shared disk. The applications and other product families depend on topology information in the Administration Server in the Oracle Fusion Setup product family. For more information about running the Administration Server from a shared location, see Section 3.2.

Optionally, if you need to perform administration tasks for other product families, start the Administration Server for those product families.

When you start the Administration Server, you also start the applications that run on the Administration Server, including the WebLogic Server Administration Console and Fusion Applications Control.

To start an Administration Server, use the following script from the Oracle WebLogic Server domain home directory, which is based on WLST commands:

(UNIX) DOMAIN_HOME/bin/startWebLogic.sh
(Windows) DOMAIN_HOME\bin\startWebLogic.cmd

where DOMAIN_HOME is located in the following locations:

(UNIX) APPLICATIONS_CONFIG/instance/domains/host/domain_name
(Windows) APPLICATIONS_CONFIG\instance\domains\host\domain_name

When the server successfully completes its startup process, it writes the following message to standard out (which, by default, is the command window):

<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode> 

Another alternative to starting the Administration Servers and Managed Servers for all the product families is the fastartstop utility. See Section 3.3.3.

See the following documentation resources to learn more about other methods for starting and stopping the Administration Servers:

Task 4   Start the Managed Servers

Depending on the configuration established during provisioning, you can start Oracle WebLogic Server Managed Servers from either a shared or local disk. See Section 3.2.

To start Oracle WebLogic Server Managed Servers, use the following script from the Oracle WebLogic Server domain home directory, which is based on WLST commands:

(UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url            
(Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url

where managed_server_name specifies the name of the Managed Server and admin_url specifies the listen address (host name, IP address, or DNS name) and port number of the domain's Administration Server. See Section 2.4 for more information on locating the Administration Server port. When prompted, enter your user name and password.

When the server successfully completes its startup process, it writes the following message to standard out (which, by default, is the command window):

<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode> 

Another alternative to starting the Administration Servers and Managed Servers for all the product families is the fastartstop utility. See Section 3.3.3.

See the following documentation resources to learn more about other methods for starting and stopping the Managed Servers:

Task 5   Start Oracle Business Intelligence

See "Starting and Stopping Oracle Business Intelligence" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

Task 6   Start the Oracle HTTP Server

To start the Oracle HTTP Server using opmnctl:

(UNIX) WT_CONFIG_HOME/bin/opmnctl startproc process-type=OHS
(Windows) WT_CONFIG_HOME\bin\opmnctl startproc process-type=OHS

To start Oracle HTTP Server using Fusion Applications Control:

  1. From the navigation pane, expand the farm and then the Web Tier installation type.

  2. Select the Oracle HTTP Server.

  3. From the Oracle HTTP Server menu, choose Control, then Start Up.

3.3.2.2 Stopping an Oracle Fusion Applications Environment

You can follow these procedures when you need to completely shut down the Oracle Fusion Applications environment. For example, when preparing to perform a complete backup of your environment, or apply a patch.

The section contains the following topics for performing a complete stop of the Oracle Fusion Applications environment:

The fastartstop utility provides an alternative way to stopping the Administration Servers and Managed Servers for all the product families in one step. See Section 3.3.3.

Task 1   Stop the Oracle HTTP Server

To stop the Oracle HTTP Server using opmnctl:

(UNIX) WT_CONFIG_HOME/bin/opmnctl stopproc process-type=OHS
(Windows) WT_CONFIG_HOME\bin\opmnctl stopproc process-type=OHS

To stop the Oracle HTTP Server using Fusion Applications Control:

  1. From the navigation pane, expand the farm and then the Web Tier installation type.

  2. Select the Oracle HTTP Server.

  3. From the Oracle HTTP Server menu, choose Control, then Shut Down.

Task 2   Stop the Administration Servers

When stopping the Oracle Fusion Applications environment, stop the Administration Server for the product families other than the Oracle Fusion Setup product family first, and then stop the Administration Server for the Oracle Fusion Setup product family. The applications and other product families depend on topology information in the Administration Server in the Oracle Fusion Setup product family. Therefore, you need to stop the Administration Server in the Oracle Fusion Setup product family after the other product families. You stop the Administration Servers from a shared disk.

Use the following script from the Oracle WebLogic Server domain home directory directory, which is based on WLST commands:

(UNIX) DOMAIN_HOME/bin/stopWebLogic.sh
(Windows) DOMAIN_HOME\bin\stopWebLogic.cmd

where DOMAIN_HOME is located in the following locations:

(UNIX) APPLICATIONS_CONFIG/instance/domains/host/domain_name
(Windows) APPLICATIONS_CONFIG\instance\domains\host\domain_name

When the server successfully completes its shutdown process, it writes the following message to standard out (which, by default, is the command window):

<Notice> <WebLogicServer> <BEA-000365> <Server state changed to SHUTTING DOWN>
 

Another alternative to stopping the Administration Servers and Managed Servers for all the product families is the fastartstop utility. See Section 3.3.3.

See the following documentation resources to learn more about other methods for stopping the Administration Servers:

Task 3   Stop the Managed Servers

Depending on the configuration established during provisioning, you can stop Oracle WebLogic Server Managed Servers from either a shared or local disk. See Section 3.2.

To stop the Managed Servers, use the following script from the Oracle WebLogic Server domain home directory, which is based on WLST commands:

(UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url            
(Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

where managed_server_name specifies the name of the Managed Server and admin_url specifies the listen address (host name, IP address, or DNS name) and port number of the domain's Administration Server. See Section 2.4 for more information on locating the Administration Server port. When prompted, enter your user name and password.

When the server successfully completes its shutdown process, it writes the following message to standard out (which, by default, is the command window):

<Notice> <WebLogicServer> <BEA-000365> <Server state changed to SHUTTING DOWN>
 

Another alternative to stopping Administration Servers and Managed Servers for all the product families is the fastartstop utility. See Section 3.3.3.

See the following documentation resources to learn more about other methods for stopping the Managed Servers:

Task 4   Stop Oracle Business Intelligence

See "Starting and Stopping Oracle Business Intelligence" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

Task 5   Stop the Oracle Identity Management Suite

To stop the Oracle Identity Management system components:

  1. Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components.

  2. Start OPMN and all system components:

    opmnctl stopall
    
Task 6   Stop the Oracle Database

To stop the Oracle database instance using Oracle Database Control:

  1. Go to the Database Home page.

    For information about how to access the Database Home page in Oracle Enterprise Manager, see "Accessing the Database Home Page" section in the Oracle Database 2 Day DBA.

  2. In the Database Home page, click Shutdown.

    The Startup/Shutdown Credentials page appears.

  3. Enter credentials as follows:

    1. Enter the host computer credentials of the user who installed Oracle Database, or of any user who is authorized to use SQL*Plus.

    2. Enter the database credentials consisting of the user name SYS and the password that you assigned to SYS during the installation.

    3. From the Connect As list, select SYSOPER.

  4. (Optional) Select the Save as Preferred Credential option if you want these credentials to be automatically filled in for you the next time that this page appears.

  5. Click OK.

    A confirmation page appears.

  6. Click Yes to start the SHUTDOWN IMMEDIATE operation on the database.

    The Shutdown: Activity Information page appears, informing you that the database is being shut down.

  7. After a short period (approximately 2 minutes), click Refresh to be returned to the Database Home page.

    The Database Home page indicates that the database instance status is Down.

For information about shutting down and starting up the Oracle database instance, see the "Shutting Down and Starting Up the Oracle Instance" section in the Oracle Database 2 Day DBA.

3.3.3 Starting and Stopping the Oracle Fusion Applications Middle Tier Using the fastartstop Utility

Another alternative to starting and stopping the Oracle Fusion Applications Administration Servers and Managed Servers is the fastartstop utility. The fastartstop utility uses a registry file named SetupDetails.xml in the following fusionapps Middleware subdirectories to determine the entities to start and stop:

(UNIX) FA_MW_HOME/admin/
(Windows) FA_MW_HOME\admin

After installation, the registry file for each product family is populated with Oracle WebLogic Server domain entries for all product families, including the Oracle Fusion Applications Common Domain in the Oracle Fusion Setup product family. You can use this utility to start all the domains or select domain. When the fastartstop utility is used to start a domain, all the Managed Servers will be started and the Administration Server of the domain will be stopped after all the Managed Servers have been started. The fastartstop utility requires Node Manager to run.

While the utility starts and stops the domains, it does not start and stop Oracle Business Intelligence, Oracle HTTP Server, Oracle Identity Management, and the Oracle Database. Therefore, you must start these components separately.

This section contains the following topics:

3.3.3.1 fastartstop Syntax

The following shows the syntax of the fastartstop utility:

(UNIX) fastartstop.sh -start|stop -all|-domains domain_name, ...domain_nameN-username user_name -password password -appsbase APPLICATIONS_BASE
(Windows) fastartstop.cmd -start|stop -all|-domains domain_name, ...domain_nameN-username user_name -appsbase APPLICATIONS_BASE

Table 3-2 describes the options for the fastartstop script.

Table 3-2 Options for the fastartstop Script

Options Description

-appsbase

Specify the path for the Oracle Fusion Applications installation.

-all|-domains

Use -all for to start or stop all domains, and use -domains for specific domains. If using the -domains option, delineate the domains names with a comma and space (domain_name, domain_name).

-start|stop

Specify the path for the Oracle Fusion Applications installation.

-username

Specify the Oracle Fusion Middleware administration user.


The utility prompts you for the Oracle Fusion Middleware administration user. See Section 4.8.5.2 for more information about changing this password.

The fastartstop utility generates SSUtil.log in the following fusionapps Middleware subdirectories:

(UNIX) FA_MW_HOME/admin/lcm/ad/bin
(Windows) FA_MW_HOME\admin\lcm\ad\bin

3.3.3.2 Registry Entries

Example 3-1 shows the format of a typical entry in the SetupDetails.xml. It is populated with the CommonDomain domains details. The other domains are not represented, because they are automatically read from the API. The file contains Oracle WebLogic Server domain information, including the Administration Server, the Managed Servers, and Node Manager.

Example 3-1 Registry File Format

<?xml version = '1.0' encoding = 'UTF-8'?>
<DomainServers><ServerInfo ServerHostName="host_name" AdminServerName="AdminServer" NodeManagerPort="port" NodeManagerHost="host_name" DomainRootDir="root_directory" DomainName="CommonDomain" AdminPort="port"/></DomainServers>

3.3.3.3 Starting an Oracle Fusion Applications Environment with the fastartstop Utility for the Middle Tier

You can reduce the number of steps required to start the Oracle Fusion Applications environment with the fastartstop utility.

The section contains the following topics for starting the Oracle Fusion Applications environment with the fastartstop utility:

Task 1   Start the Oracle Database

To start the Oracle database instance using Oracle Database Control:

  1. Go to the Database Home page.

    For information about how to access the Database Home page in Oracle Enterprise Manager, see "Accessing the Database Home Page" section in the Oracle Database 2 Day DBA.

  2. In the Database Home page, click Startup.

    The Startup/Shutdown Credentials page appears.

  3. Enter credentials as follows:

    1. Enter the host computer credentials of the user who installed Oracle Database, or of any user who is authorized to use SQL*Plus.

    2. Enter the database credentials consisting of the user name SYS and the password that you assigned to SYS during the installation.

    3. From the Connect As list, select SYSOPER.

  4. Click OK.

    A confirmation page appears.

  5. Click Yes.

    The Startup page appears, indicating that the database is being started up. When startup is complete, the Login page appears.

  6. Log in to the database.

    The Database Home page appears indicating that the database instance status is Up.

For information about shutting down and starting up the Oracle database instance, see the "Shutting Down and Starting Up the Oracle Instance" section in the Oracle Database 2 Day DBA.

Task 2   Start the Oracle Identity Management Suite

To start the Oracle Identity Management system components:

  1. Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components.

  2. Start OPMN and all system components:

    opmnctl startall
    
Task 3   Start Node Manager

The fastartstop utility requires the Node Manager be running.

To start Node Manager, use the startNodeManagerWrapper utility from the Oracle WebLogic Server domain home directory under the fusionapps Middleware subdirectory:

(UNIX) WL_HOME/nodemanager/host_name/startNodeManagerWrapper.sh
(Windows) WL_HOME\nodemanager\host_name\startNodeManagerWrapper.cmd 
Task 4   Run the fastartstop Utility

From the CommonDomain domain in the environment, run fastartstop to start all the domains or specific domains:

(UNIX) fastartstop.sh -start -all|-domains domain_name, ...domain_nameN-username user_name -password password -appsbase APPLICATIONS_BASE
(Windows) fastartstop.cmd -start -all|-domains domain_name, ...domain_nameN-username user_name -appsbase APPLICATIONS_BASE

For more information about the syntax, see Table 3-2.

Task 5   Start Oracle Business Intelligence

See "Starting and Stopping Oracle Business Intelligence" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

Task 6   Start the Oracle HTTP Server

To start the Oracle HTTP Server using opmnctl:

(UNIX) WT_CONFIG_HOME/bin/opmnctl startproc process-type=OHS
(Windows) WT_CONFIG_HOME\bin\opmnctl startproc process-type=OHS

To start Oracle HTTP Server using Fusion Applications Control:

  1. From the navigation pane, expand the farm and then the Web Tier installation type.

  2. Select the Oracle HTTP Server.

  3. From the Oracle HTTP Server menu, choose Control, then Start Up.

3.3.3.4 Stopping an Oracle Fusion Applications Environment with the fastartstop Utility

You can reduce the number of steps required to stop the Oracle Fusion Applications environment with the fastartstop utility.

The section contains the following topics for stopping the Oracle Fusion Applications environment with the fastartstop utility:

Task 1   Stop the Oracle HTTP Server

To stop the Oracle HTTP Server using opmnctl:

(UNIX) WT_CONFIG_HOME/bin/opmnctl stopproc process-type=OHS
(Windows) WT_CONFIG_HOME\bin\opmnctl stopproc process-type=OHS

To stop the Oracle HTTP Server using Fusion Applications Control:

  1. From the navigation pane, expand the farm and then the Web Tier installation type.

  2. Select the Oracle HTTP Server.

  3. From the Oracle HTTP Server menu, choose Control, then Shut Down.

Task 2   Start Node Manager

The fastartstop utility requires the Node Manager be running.

To start Node Manager, use the startNodeManagerWrapper utility from the Oracle WebLogic Server domain home directory under the fusionapps Middleware subdirectory:

(UNIX) WL_HOME/nodemanager/host_name/startNodeManagerWrapper.sh
(Windows) WL_HOME\nodemanager\host_name\startNodeManagerWrapper.cmd 
Task 3   Run the fastartstop Utility

From the CommonDomain domain in the environment, run fastartstop to stop all the domains or specific domains:

(UNIX) fastartstop.sh -stop -all|-domains domain_name, ...domain_nameN-username user_name -password password -appsbase APPLICATIONS_BASE
(Windows) fastartstop.cmd -stop -all|-domains domain_name, ...domain_nameN-username user_name -appsbase APPLICATIONS_BASE

For more information about the syntax, see Table 3-2.

Task 4   Stop Oracle Business Intelligence

See "Starting and Stopping Oracle Business Intelligence" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

Task 5   Stop the Oracle Identity Management Suite

To stop the Oracle Identity Management system components:

  1. Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components.

  2. Start OPMN and all system components:

    opmnctl stopall
    
Task 6   Stop the Oracle Database

To stop the Oracle database instance using Oracle Database Control:

  1. Go to the Database Home page.

    For information about how to access the Database Home page in Oracle Enterprise Manager, see "Accessing the Database Home Page" section in the Oracle Database 2 Day DBA.

  2. In the Database Home page, click Shutdown.

    The Startup/Shutdown Credentials page appears.

  3. Enter credentials as follows:

    1. Enter the host computer credentials of the user who installed Oracle Database, or of any user who is authorized to use SQL*Plus.

    2. Enter the database credentials consisting of the user name SYS and the password that you assigned to SYS during the installation.

    3. From the Connect As list, select SYSOPER.

  4. (Optional) Select the Save as Preferred Credential option if you want these credentials to be automatically filled in for you the next time that this page appears.

  5. Click OK.

    A confirmation page appears.

  6. Click Yes to start the SHUTDOWN IMMEDIATE operation on the database.

    The Shutdown: Activity Information page appears, informing you that the database is being shut down.

  7. After a short period (approximately 2 minutes), click Refresh to be returned to the Database Home page.

    The Database Home page indicates that the database instance status is Down.

For information about shutting down and starting up the Oracle database instance, see the "Shutting Down and Starting Up the Oracle Instance" section in the Oracle Database 2 Day DBA.

3.3.4 Starting and Stopping a Product Family Oracle WebLogic Server Domain

When applying a patch that only applies to a product family, you can stop the Oracle WebLogic Server domain for the product family and restart it after you apply the patch. Your environment may require a restart of a domain for reasons other than a patch.

This section contains the following topics:

3.3.4.1 Stopping an Oracle WebLogic Server Domain for a Product Family

You stop an Oracle WebLogic Server domain for a product family before applying a patch.

This section contains the following topics for stopping an Oracle WebLogic Server domain for a product family:

Task 1   Stop the Oracle HTTP Server

Oracle HTTP Server is typically installed on a computer separate from the product family. By stopping Oracle HTTP Server, you stop requests to the entire Oracle Fusion Applications environment. Stopping Oracle HTTP Server before the product family ensures a cleaner shutdown.

To stop the Oracle HTTP Server using opmnctl:

(UNIX) WT_CONFIG_HOME/bin/opmnctl stopproc process-type=OHS
(Windows) WT_CONFIG_HOME\bin\opmnctl stopproc process-type=OHS

To stop Oracle HTTP Server using Fusion Applications Control:

  1. From the navigation pane, expand the farm and then the Web Tier installation type.

  2. Select an Oracle HTTP Server.

  3. From the Oracle HTTP Server menu, choose Control, then Shut Down.

Task 2   Stop the Product Family Domain

When you stop an Oracle WebLogic Server domain for a product family, you stop all the applications on the cluster of Managed Servers in the domain. For example, the Oracle Enterprise Scheduler ESSAPP application and the SOA Infrastructure soa-infra application stop running.

To stop a product family domain using Fusion Applications Control:

  1. From the navigation pane, expand the farm, then WebLogic Domain.

  2. Select the Oracle WebLogic Server domain.

  3. From the WebLogic Domain menu, choose Control, then Shut Down.

3.3.4.2 Starting an Oracle WebLogic Server Domain for a Product Family

You start an Oracle WebLogic Server domain for a product family after applying a patch.

This section contains the following topics for starting an Oracle WebLogic Server domain for a product family:

Task 1   Start the Oracle HTTP Server

To start the Oracle HTTP Server using opmnctl:

(UNIX) WT_CONFIG_HOME/bin/opmnctl startproc process-type=OHS
(Windows) WT_CONFIG_HOME\bin\opmnctl startproc process-type=OHS

To stop Oracle HTTP Server using Fusion Applications Control:

  1. From the navigation pane, expand the farm and then the Web Tier installation type.

  2. Select the Oracle HTTP Server.

  3. From the Oracle HTTP Server menu, choose Control, then Start Up.

Task 2   Start the Product Family Domain

When you start an Oracle WebLogic Server domain for a product family, you start the cluster of Managed Servers in the domain and all the applications.

To start a product family domain using Fusion Applications Control:

  1. From the navigation pane, expand the farm, then WebLogic Domain.

  2. Select the Oracle WebLogic Server domain.

  3. From the WebLogic Domain menu, choose Control, then Start Up.

3.3.5 Starting and Stopping an Oracle WebLogic Server Cluster for a Configuration Change

If you modify the Oracle WebLogic Server configuration, you must stop and restart the cluster for the configuration changes to take effect.

This section contains the following topics:

3.3.5.1 Starting and Stopping Oracle WebLogic Server Clusters with a Startup Script

See "Starting Managed Servers with a Startup Script" section in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server to start the Managed Servers, one at a time, in the cluster.

3.3.5.2 Starting and Stopping an Oracle WebLogic Server Cluster Using WLST and Node Manager

See "Using Node Manager to Start Managed Servers in a WebLogic Domain or Cluster" section in Oracle Fusion Middleware Oracle WebLogic Scripting Tool.

3.3.5.3 Starting and Stopping an Oracle WebLogic Server Cluster Using Fusion Applications Control

To stop or restart a cluster using Fusion Applications Control:

  1. Modify the Oracle WebLogic Server configuration as required.

  2. From the navigation pane, expand the farm, WebLogic Domain, and then domain name.

  3. Select the Oracle WebLogic Server cluster.

  4. Expand the Oracle WebLogic Server cluster to show each target Managed Server.

  5. From the WebLogic Cluster menu, choose Control, then Shut Down or Start Up.

3.3.6 Starting and Stopping Specific Applications

You can start and stop applications using the WLST command line, the WebLogic Server Administration Console, or Fusion Applications Control.

Applications may not work correctly until all Managed Servers in all domains have been started.

This section contains the following topics:

3.3.6.1 Starting and Stopping Java EE Applications Using WLST

To start or stop applications with the WLST command line, use the following commands from the fusionapps Middleware directory:

startApplication(appName, [options])
stopApplication(appName, [options])

The application must be fully configured and available in the domain. The startApplication command returns a WLSTProgress object that you can access to check the status of the command. In the event of an error, the command returns a WLSTException. For more information about the WLSTProgress object, see "WLSTProgress Object" in the Oracle Fusion Middleware Oracle WebLogic Scripting Tool.

3.3.6.2 Starting and Stopping an Individual Application Instance for a Cluster Using Fusion Applications Control

To start or stop an application using Fusion Applications Control:

  1. From the navigation pane, expand the product family, then Fusion Applications, and then the cluster application.

  2. Select the application instance you want to stop.

  3. From the Fusion J2EE Application menu, choose Control, then Start Up or Shut Down.

3.3.6.3 Starting and Stopping all Application Instances for a Cluster Using Fusion Applications Control

To start or stop all the application instances in a cluster using Fusion Applications Control:

  1. From the navigation pane, expand the product family, then Fusion Applications, and then the cluster application.

  2. From the Fusion Cluster Application menu, choose Control, then Start Up or Shut Down.

3.4 Viewing and Changing Ports for Components

Oracle Database and Oracle Fusion Middleware components and services use ports. Most numbers are assigned during installation. As an administrator, it is important to know the numbers used by these services, and to ensure that the same number is not used by two services on your host.

For some ports, you can specify a number assignment during installation.

You can change the port numbers for some Oracle Fusion Middleware components from Oracle Fusion Applications, Oracle WebLogic Server Administration Console, or the command line.

Table 3-3 lists the port types and provides information on where to find documentation related to changing ports. The procedures referenced in the Oracle Fusion Middleware guides describe using Fusion Middleware Control. These procedure also apply to Fusion Applications Control.

Table 3-3 Changing Ports

Port Type Documentation for Changing Ports

Oracle Database

"Changing the Oracle Database Net Listener" section in the Oracle Fusion Middleware Administrator's Guide

Oracle Business Intelligence Suite

"Using Fusion Middleware Control to Scale System Components" section in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition

Oracle HTTP Server

"Manage Ports" section in the Oracle Fusion Middleware Administrator's Guide for Oracle HTTP Server

Oracle Enterprise Content Management Suite

"Modifying Server Configuration Parameters for Oracle UCM Content Server" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory for information about changing the for Oracle Universal Content Management Content Server

Oracle Internet Directory

"Configuring Server Properties" section or the "Setting System Configuration Attributes by Using ldapmodify" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory

Oracle Virtual Directory

"Configuring Oracle Virtual Directory to Listen on Privileged Ports" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Virtual Directory

Node Manager

"Overview of Node Manager Configuration" section in the Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server


3.5 Changing Passwords

Before you begin configuration, change the passwords for the various accounts to secure passwords. Table 3-4 describes the accounts and provides information on where to find related documentation for each account. The procedures referenced in the Oracle Fusion Middleware guides describe using Fusion Middleware Control. These procedure also apply to Fusion Applications Control.

Table 3-4 Changing Passwords

Password Account Description Documentation for Changing the Passwords

Oracle Fusion Middleware administration for the Oracle WebLogic Server domain

In an Oracle Fusion Applications installation. The super user is described in the next row of this table.

Section 4.8.5.2

Super User

The super user has the following privileges:

  • Administrative privileges for all Oracle WebLogic Server domains and all middleware.

  • Functional setup privileges for all Oracle Fusion applications.

  • Administrative privileges to Oracle Fusion applications. These do not include transactional privileges. You use this username and password to access the Fusion Applications Control and the Oracle WebLogic Server Administration Console.

You can change the credentials using Fusion Applications Control or Oracle Platform Security Services (OPSS) scripts.

This user is specified on the Identity and Policy Management page of the Provisioning Wizard during installation. See "Identity and Policy Management Configuration" section in the Oracle Fusion Applications Installation Guide for information about this page. Installation establishes the same username and password for all the domains.

Section 4.8.5.2 to change the administrative password

"Managing the Credential Store" section in the Oracle Fusion Middleware Application Security Guide

Oracle Metadata Repository schema

Oracle Metadata Services (MDS) repository contains metadata for the Oracle Fusion Applications and some Oracle Fusion Middleware component applications. The schema passwords are stored in the Oracle database.

"Changing Metadata Repository Schema Passwords" section in the Oracle Fusion Middleware Application Security Guide

Application App IDs

Oracle Fusion Applications must rely on a type of credential known as the App ID. Each application has its own App ID which is initially provisioned for the application.

Section 4.8.5.1

Oracle Fusion Applications Security Hardening Guide

Node Manager

The Node Manager account authenticates the connection between a client (for example, the Administration Server) and Node Manager.

In an Oracle Fusion Applications installation, this user is specified on the Installation Location page of the Provisioning Wizard. See the "Installation Location" section in the Oracle Fusion Applications Installation Guide for information about using this page.

"Specify Node Manager Username and Password" section in the Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server

BISystemUser

The BISystemUser account provides access to the Oracle Business Intelligence system components.

"Default Users and Passwords" section in the Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition


3.6 Managing the Oracle Database

To manage your Oracle database:

  1. Start the Oracle database instance, if not already started. See Section 3.3.2.

  2. Review database initialization parameters. Modify initialization parameters as needed. See Section 3.6.1.

  3. Review your database storage structures: tablespaces and data files, online redo log files, and control files. Create or modify storage structures as needed. See Section 3.6.2.

  4. Review memory allocation and adjust as needed. See Section 3.6.3.

  5. Review, unlock, and reset passwords for predefined database users as needed. Create new users, and assign privileges and roles to them as needed. See Section 3.6.4.

  6. Create or review the backup strategy for the database and back up the database. See Chapter 14.

3.6.1 Viewing and Modifying Initialization Parameters

Managing an Oracle instance includes configuring parameters that affect the basic operation of the Oracle instance. These parameters are called initialization parameters. The Oracle instance reads initialization parameters from a file at startup.

After being read from a file, initialization parameters are retained in memory, where the values for many of them can be changed dynamically. There are two types of parameter files. The type of file used to start the instance determines if dynamic initialization parameter changes persist across database shutdown and startup. The parameter file types are:

  • Server parameter file

    The server parameter file is a binary file that can be written to and read by the database. It must not be edited manually. It is stored on the host system on which Oracle Database is running. Changes are made when you use Database Control to modify one or more initialization parameters, or when Oracle Database itself makes changes for self-tuning purposes. Any changes to it persist across database shutdown and startup operations.

  • Text initialization parameter file

    A text initialization parameter file is a text file that can be read by the Oracle instance, but it is not written to by the instance. You can change a text initialization parameter file with a text editor, but changes do not take effect until you restart the Oracle instance. When you start the instance with this type of file, you can still change many initialization parameters dynamically with Database Control, but only for the current instance. Unless you also edit the text initialization parameter file and make the same change, the change is lost when you restart the database instance.

As the number of database users increases and the workload increases, you might have to alter some initialization parameters. You can make these changes using the Initialization Parameter page in Oracle Enterprise Manager Database Control, accessible from the Database Configuration section of the Server tab.

Table 3-5 lists specific initialization parameters that you should set and their recommended values.

Table 3-5 Initialization Parameters

Parameter Recommended Values

CONTROL_MANAGEMENT_PACK_ACCESS

Set this parameter to DIAGNOSTIC+TUNING (default) or DIAGNOSTIC to enable Automatic Database Diagnostic Monitor (ADDM).

STATISTICS_LEVEL

Set this parameter to TYPICAL (default) to enable the automatic performance tuning features of Oracle Database, including Automatic Workload Repository (AWR) and ADDM.


For information about viewing and modifying initialization parameters, see the "Viewing and Modifying Initialization Parameters" section in the Oracle Database 2 Day DBA.

3.6.2 Managing Database Storage Structures

Oracle Database is made up of physical and logical structures. Physical structures can be seen and operated on from the operating system, such as the physical files that store data on a disk.

Logical structures are created and recognized by Oracle Database and are not known to the operating system. The primary logical structure in a database, a tablespace, contains physical files. The applications developer or administrator may be aware of the logical structure, but may not be aware of the physical structure. The database administrator (DBA), on the other hand, must understand the relationship between the physical and logical structures of a database.

Oracle Database can automate much of the management of its structure. To view a database storage structure using Oracle Enterprise Manager Database Control, go to the Storage section of the Server tab, where you can access the following storage options:

  • Control files

  • Tablespaces

  • Temporary tablespace groups

  • Datafiles

  • Rollback segments

  • Redo log groups

  • Archive legs

  • Disk groups

  • Other storage structures

For more information about managing database storage structures, see the "Managing Database Storage Structures" chapter in the Oracle Database 2 Day DBA.

3.6.3 Managing Memory

Memory management involves maintaining optimal sizes for the Oracle instance memory structures as demands on the database change. The memory that must be managed are the System Global Area (SGA) memory and the instance Program Global Area (PGA) memory. The instance PGA memory is the collection of memory allocations for all individual PGAs.

Oracle Database can manage the SGA memory and instance PGA memory automatically. You designate only the total memory size to be used by the instance, and Oracle Database dynamically exchanges memory between the SGA and the instance PGA as needed to meet processing demands. This capability is referred to as automatic memory management. In this memory management mode, the database also dynamically tunes the sizes of the individual SGA components and the sizes of the individual PGAs.

To have more direct control over the sizes of the SGA and instance PGA, use the Memory Advisors page of Oracle Enterprise Manager Database Control to disable automatic memory management and enable automatic shared memory management. With automatic shared memory management, you set target and maximum sizes for the SGA. Oracle Database then tunes the total size of the SGA to your designated target, and dynamically tunes the sizes of all SGA components. In this memory management mode, you also implicitly enable automatic PGA memory management. With automatic PGA memory management, you set a target size for the instance PGA. The database then tunes the size of the instance PGA to your target, and dynamically tunes the sizes of individual PGAs.

If you want complete control of individual SGA component sizes, then use the Memory Advisors page of Oracle Enterprise Manager Database Control to disable both automatic memory management and automatic shared memory management. This is called manual shared memory management. In this mode, you set the sizes of several individual SGA components, thereby determining the overall SGA size. You then manually tune these individual SGA components on an ongoing basis. Manual shared memory management mode is intended for experienced DBAs only. Note that in this mode, automatic PGA memory management remains enabled.

To manage memory, use the Memory Advisor page in Database Control, accessible from the Database Configuration section of the Server tab.

For more information about memory management, see the "Managing Memory" section in the Oracle Database 2 Day DBA.

3.6.4 Administering User Accounts

For users to access your database, you must create user accounts and grant appropriate database access privileges to those accounts. A user account is identified by a user name and defines the attributes of the user, including the following:

  • Authentication method

  • Password for database authentication

  • Default tablespaces for permanent and temporary data storage

  • Tablespace quotas

  • Account status (locked or unlocked)

  • Password status (expired or not)

When you create a user account, you must not only assign a user name, a password, and default tablespaces for the account, but you must also do the following:

  • Grant the appropriate system privileges, object privileges, and roles to the account.

  • If the user will be creating database objects, then give the user account a space usage quota on each tablespace in which the objects will be created.

In addition, you may want to create user accounts that are used by applications only, such as Fusion Applications. Users do not log in with these accounts; instead, applications use these accounts to connect to the database, and users log in to the applications. This type of user account avoids giving application users the ability to log in to the database directly, where they could unintentionally cause damage.

To administer user accounts using Oracle Enterprise Manager Database Control, go to the Security section of the Server tab, where you can access users and roles.

For more information about administering user accounts, see the "Administering User Accounts and Security" chapter in the Oracle Database 2 Day DBA.

3.7 Patching

It is necessary to perform various maintenance actions on your applications, their middleware dependencies, and their database components. Maintenance actions include fixing issues that affect the way the applications perform, adding new functionality and features, updating to a higher maintenance level, or providing interoperability to new technology stacks. Patches may be required for maintenance of middleware artifacts, database artifacts, or both. Table 3-6 describes the types of patching and provides information on where to find related documentation.

Table 3-6 Patching

Type of Patching Description Documentation for Patching

Oracle Fusion Applications

The Oracle Fusion Applications Patching Framework provides the tools needed to sup updates to Oracle Fusion Applications software between major or patch set releases. These tools manage the processes for applying individual patches, patch sets, and release update packs.

Oracle Fusion Applications Patching Guide

Oracle Fusion Middleware

OPatch patches any Oracle Fusion Middleware component, except Oracle WebLogic Server. For Oracle WebLogic Server, use Smart Update.

Oracle Fusion Middleware Patching Guide for information about patching middleware artifacts

Oracle Smart Update Installing Patches and Maintenance Packs for information about patching Oracle WebLogic Server

Oracle Database

Oracle Universal Installer and OPatch manage the patching for Oracle database and third-party software.

Oracle Universal Installer and OPatch User's Guide for Windows and UNIX