Skip Headers
Oracle® Fusion Applications Administrator's Guide
11g Release 6 Refresh 4 (11.1.6)

Part Number E14496-14
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
PDF · Mobi · ePub

4 Performing Routine Administrative Tasks

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

This chapter contains the following topics:

4.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:

4.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.

4.3 Viewing and Managing Targets Across Domains (Optional)

In Fusion Applications, certain business process flows or operational requirements can span domains and/or product families. (For example, a Customer Relationship Management (CRM) process can rely on the availability of certain Human Capital Management (HCM) components. Out-of-the-box tools (such as Fusion Applications Control) are limited to monitoring the domains within their product family In addition, administrators might want to monitor by target type across domains. For example, they might want o monitor all of the J2EE application targets across multiple WebLogic Server domains.The only way to accomplish this is via the Group functionality in Oracle Enterprise Manager Cloud Control. (Your system must have Cloud Control installed and configured.)

For general information on Groups, see "Managing Groups," in the Oracle Enterprise Manager Cloud Control Administrator's Guide.

The following example shows how to create a Dashboard to view Enterprise Scheduling Service (ESS) components which are spread across the Common, HCM, CRM, and Financial Domains in the system. Use the same principles to create a Dashboard that fits your parameters.

  1. Log in to Enterprise Manager Cloud Control and select Targets and Groups.

  2. Select Create and choose Group from the drop-down menu.

  3. On the resulting Create Group page, enter a Name and click Search for Members.

    A list of all available Targets is displayed in a Group home page.

  4. In the Search field at the top of the page, type ESSAPP to find all the Scheduler-related elements.

    Search Targets page
  5. Choose Select All, or selectively click the results you want to include, then click OK.

    You see your Group with the chosen Members listed.

  6. If it is correct, click OK. The list of all Groups is displayed.

  7. Select your newly created Group by Name. The Group Dashboard is displayed.

    Group Dashboard page

4.4 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:

4.4.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.

Table 4-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 4-1 Starting and Stopping

Component Description Documentation

Oracle Fusion Applications

Oracle Fusion applications

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

Section 4.4.9, "Starting and Stopping Specific Applications"

"Start applications and modules" and "Stop applications and modules" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help for the WebLogic Server Administration Console

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.

You can use the fastartstop utility to start the Administration Server in one or more domains.

Section 4.4.4.1, "Starting the Administration Servers and Managed Servers"

Section 4.4.4.2, "Stopping the Administration Servers and Managed Servers"

Managed Servers for the Oracle Fusion applications and Oracle Fusion Middleware components

A Managed Server can host Oracle Fusion applications, application components, Web services, and their associated resources. Managed Servers also host applications for the following Oracle Fusion Middleware components:

  • Oracle Business Intelligence

  • Oracle Data Integrator

  • Oracle Enterprise Scheduler

  • Oracle Secure Enterprise Search

  • Oracle SOA Suite

  • Oracle WebCenter Content

  • Oracle WebCenter Content: Imaging

  • Oracle WebCenter Portal's Discussion Server

  • Oracle WebCenter Portal: Spaces

You can use the fastartstop utility to start one or more Managed Servers in one or more domains. Alternatively, you can use Fusion Applications Control or WebLogic Server Administration.

Section 4.4.4.1, "Starting the Administration Servers and Managed Servers"

Section 4.4.4.2, "Stopping the Administration Servers and Managed Servers"

Node Manager

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

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

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

Section 4.4.3.1.3, "Task 3: Start Node Manager"

Oracle Business Intelligence Suite

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

You can use the fastartstop utility to start and stop the BI Presentation Server component.

"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

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

Section 7.7, "Starting and Stopping Oracle Enterprise Scheduler Service Components"

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 SOA Suite

You can use Fusion Applications Control to start and stop the SOA Infrastructure and the Managed Servers for Oracle SOA Suite.

"Stopping and Starting the Managed Server and SOA Infrastructure" section in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite

Oracle WebCenter Portal: Spaces

Always ensure Content Server is running when starting Oracle WebCenter Portal: Spaces. If Content Server is not running when Spaces is started up Spaces will consider the Document service as unavailable. After Content Server is started, a restart of Spaces is needed for it to recheck if the Document service is configured.

"Starting Content Server" section in the Oracle WebCenter Content System Administrator's Guide for Content Server

"Starting and Stopping the Spaces Application" section in the Oracle WebCenter Content System Administrator's Guide for Content Server

Oracle WebLogic Server domain for a product family

When applying a patch that only applies to one product family, 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.

Use the fastartstop utility for this task. You can alternatively use Fusion Applications Control.

Section 4.4.7, "Starting and Stopping a Product Family Oracle WebLogic Server Domain"

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.

Use the fastartstop utility for this task. You can alternatively use Fusion Applications Control and WebLogic Server Administration Console.

Section 4.4.8, "Starting and Stopping an Oracle WebLogic Server Cluster in a Product Family for a Configuration Change"

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


4.4.2 Understanding Starting and Stopping with the fastartstop Utility

The fastartstop script is installed with the Oracle Fusion Applications patching framework. 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 a 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 uses Node Manager to start and stop servers. fastartstop will fail if Node Manager is not already running.

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

This section contains the following topics:

4.4.2.1 fastartstop Syntax

If the Oracle Fusion Applications patching framework was installed, the fastartstop utility is available from the following directories:

(UNIX) FA_ORACLE_HOME/lcm/ad/bin
(Windows) FA_ORACLE_HOME\lcm\ad\bin

FA_ORACLE_HOME is the Oracle Fusion Applications Oracle home located at:

(UNIX) APPLICATIONS_BASE/fusionapps/applications
(Windows) APPLICATIONS_BASE\fusionapps\applications

The fastartstop utility supports the following syntax:

(UNIX) ./fastartstop.sh -Start|-Stop|-Bounce|-StartBIPS|-StopBIPS 
-all|-domains domain_name,domain_nameN,domain_nameN|-BIPServerComponents
-all|-domains "domain_name(server:all,server:managed_server_name|AdminServer),domain_name(server:all,server:managed_server_name|AdminServer)"|-BIPServerComponents
[-componentType OHS |-componentDomain component_domain_name][iasInstance=instance_id][iasComponent=component_id][-processType=component_type]
[-clusterType soa]
-username user_name
-appbase FA_ORACLE_HOME
[-loglevel log_level]
[-timeout timeout_period]
[--help]

(Windows) fastartstop.cmd -Start|-Stop|-Bounce|-StartBIPS|-StopBIPS 
-all|-domains domain_name,domain_nameN,domain_nameN|-BIPServerComponents
-all|-domains "domain_name(server:all,server:managed_server_name|AdminServer),domain_name(server:all,server:managed_server_name|AdminServer)"|-BIPServerComponents
[-componentType OHS |-componentDomain component_domain_name][iasInstance=instance_id][iasComponent=component_id][-processType=component_type]
[-clusterType soa]
-username user_name
-appbase FA_ORACLE_HOME
[-loglevel log_level]
[-timeout timeout_period]
[--help]

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

Table 4-2 Options for the fastartstop Script

Options Description

-Start|-Stop|-Bounce|-StartBIPS|-StopBIPS

Specify the operation to execute:

  • Use -Start to start Managed Servers.

  • Use -Stop to stop Managed Servers.

  • Use -Bounce to restart Managed Servers.

  • Use –StartBIPS to start Oracle Business Intelligence.

  • Use -StopBIPS to stop Oracle Business Intelligence.

-all|-domains|-BIPServerComponents

Specify what to start, stop, or restart:

  • Use -all for all components in all the domains. Components that are started include the Administration Server, Managed Servers, OPMN-based components Oracle Business Intelligence and Oracle HTTP Server.

  • Use -domains for Managed Servers and the Administration Server in specific domains. Delineate the domain names with a comma, (domain_name,domain_name); white space is not allowed in the domain name list. This option does not manage OPMN-based components Oracle Business Intelligence and Oracle HTTP Server.

  • Use -BIPServerComponents for Oracle Business Intelligence components. This option should be used only in conjunction with the –StartBIPS or -StopBIPS option.

  • Use suboption server to specify the Administration Server or Managed Servers for the domains you want to start, stop, or bounce. When the server suboption is used, enclose the -domains argument in quotes:

    -domains "domain_name(server:all,server:managed_server_name|AdminServer)"
    

This -domains option is mutually exclusive to the following options:

  • -startAdminServer

  • -clusterType

  • -adminServersOnly

You cannot include these options in the same fastartstop command as the -domains options.

If you use the server suboption for one domain, you must use it for all domains. Example 4-21 shows a mix, which would generate an error.

-componentType|-componentDomain

Specify the operation to execute:

  • Use -componentType to start Oracle HTTP Server. It is a customized form of -componentDomain option.

  • Use -componentDomain an alternative to starting or stopping Oracle HTTP Server managed through Oracle Process Manager and Notification (OPMN) component. You use the -iasInstance, -iasComponent, and -processType suboptions to completely specify a component. For general information about these attributes, see the Oracle Fusion Middleware Oracle Process Manager and Notification Server Administrator's Guide.

    - Use -iasInstance to specify the instance ID. Enter a value of CommonDomain_webtier for Oracle HTTP Server.

    - Use -iasComponent to specify the component ID for the component. The value is ohs for Oracle HTTP Server.

    - Use -processType to specify the component type. The valid value is OHS for Oracle HTTP Server.

-iasComponent is a child of -iasInstance. Therefore, you cannot issue a fastartstop command using -iasComponent without its hierarchical parent command. You can use -iasInstance independent of -iasComponent commands.

For example, -componentDomain CommonDomain -iasInstance CommonDomain_webtier will act upon all components under the CommonDomain_webtier instance ID. Similarly -componentDomain CommonDomain -iasInstance CommonDomain_webtier -iasComponent ohs1 will act upon all process types under ohs1 component ID. However, -componentDomain CommonDomain -iasComponent ohs1 will result in an error, as the hierarchy is not maintained. The component named ohs1 can be present under any instance, so the hierarchy needs to be maintained to ensure the correct Oracle HTTP Server.

-clusterType

Specify to start, stop, or restart Managed Servers within a cluster. This parameter is currently only supported for Oracle SOA Suite clusters (soa).

This option is mutually exclusive to the server suboption of the -domain option. You cannot include this option in the same fastartstop command as the server suboption.

This option is mutually exclusive to the following options:

  • -adminServersOnly

  • server suboption of the -domains option

You cannot include the -clusterType option in the same fastartstop command as these options.

-username

Specify an user with Oracle Fusion Middleware administration user privileges.

-appbase

Specify the complete directory path to the Oracle Fusion Applications Oracle home. This directory is located at:

(UNIX) APPLICATIONS_BASE/fusionapps/applications
(Windows) APPLICATIONS_BASE\fusionapps\applications

-adminServersOnly

Use to start, stop, or restart the Administration Servers only, leaving the Managed Servers untouched.

This option is mutually exclusive to the following options:

  • -startAdminServer

  • -clusterType

  • server suboption of the -domains option

You cannot include the -adminServersOnly option in the same fastartstop command as these options.

When used with Bounce, fastartstop performs a restart for Administration Servers. If some Administration Servers fail during the Bounce command, in next run, failed servers will be acted upon. The servers bounced successfully in the previous runs will be skipped in the next run.

-startAdminServer

Specify true to start the Administration Server; specify false to stop the Administration Server. The default is false.

This option is mutually exclusive to the following options:

  • -adminServersOnly

  • server suboption of the -domains option

You cannot include the -startAdminServer option in the same fastartstop command as these options.

--help

Specify to display the syntax.

-loglevel

Specify the log level for the fastartstop.log file:

  • INFO: Provides informational messages.

  • FINER: Provides detailed log messages.

  • WARNING: Provides messages for potentially problems.

INFO is the default.

-timeout

Specify the number of seconds to wait for the start, stop, or restart the domain or a server. When all the servers in the domain are started in parallel, the timeout is associated with the domain. When individual Administration Sever or Managed Sever are started instead of a domain, the timeout is associated with the server.

The default timeout is 40 minutes. In addition, this option has a minimum guard value of 12 minutes. If you provides a value less than 12 minutes, then guard value will be used instead.


The fastartstop utility prompts you for the password for the user with Oracle Fusion Middleware administrator privileges specified by the -username argument. If you pass this argument to the fastarstop utility on the standard input, the utility will not prompt.

See Section 6.8.5.2 for more information about changing this password.

The fastartstop utility generates fastartstop.log in the following subdirectories:

(UNIX) FA_ORACLE_HOME/lcm/ad/bin
(Windows) FA_ORACLE_HOME\lcm\ad\bin

FA_ORACLE_HOME is the Oracle Fusion Applications Oracle home located at:

(UNIX) APPLICATIONS_BASE/fusionapps/applications
(Windows) APPLICATIONS_BASE\fusionapps\applications

4.4.2.2 fastartstop Examples

The following examples provide syntax examples for common scenarios:

4.4.2.2.1 Starting Examples with fastartstop

Example 4-1 shows starting the Administration Server and all the Managed Servers in the SCMDomain domain.

Example 4-1 Syntax Sample to Start the Administration Server and All Managed Servers in a Single Domain

./fastartstop.sh -Start -domains "SCMDomain(server:all)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-2 shows starting the Administration Server and the soa_server1 Managed Server in the SCMDomain domain.

Example 4-2 Syntax to Start the Administration Server and Another Managed Server in a Single Domain

./fastartstop.sh -Bounce -domains "SCMDomain(server:AdminServer,server:soa_server1)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-3 shows starting Managed Servers soa_server1 and AdvancedPlanningServer_1 in the SCMDomain domain.

Example 4-3 Syntax to Start Multiple Managed Servers in a Single Domain

./fastartstop.sh -Start -domains "SCMDomain(server:soa_server,server:AdvancedPlanningServer_1)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-4 shows starting Managed Servers soa_server1 and AdvancedPlanningServer_1 in the SCMDomain domain and soa_server from the HCMDomain domain.

Example 4-4 Syntax to Start Multiple Managed Servers in Multiple Domains

./fastartstop.sh -Start -domains "SCMDomain(server:soa_server,server:AdvancedPlanningServer_1),HCMDomain(server:soa_server)"  -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-5 shows starting all the Managed Servers and the Administration Server in the HCMDomain domain.

Example 4-5 Syntax to Start the Managed Servers and Administration Server in the SOA Cluster of a Single Domain

./fastartstop.sh -Start -domains HCMDomain -username username 

appbase /scratch/aime1/appltop/fusionapps/applications 

-clusterType soa -startAdminServer true

Example 4-6 shows starting the CommonDomain domain. Starting a domain starts its Managed Servers and Administration Server. Starting a domain includes starting its Administration Server, followed by the Managed Servers. Once all the Managed Servers are up, the Administration Server is stopped. If you want the Administration Server to continue to run, use -startAdminServer true, as shown in Example 4-5. This command does not start OPMN-based components Oracle Business Intelligence and Oracle HTTP Server.

Example 4-6 Syntax to Start a Specific Domain

./fastartstop.sh -Start -domains CommonDomain -username FUSION_APPS_PROV_PATCH_APPID -appbase /slot/ems7770/oracle/apphome/fusionapps/applications 

Example 4-7 shows starting all the domains. Starting a domain includes starting its Administration Server, followed by the Managed Servers. Once all the Managed Servers are up, the Administration Server is stopped. If you want the Administration Servers to continue to run, use -startAdminServer true, as shown in Example 4-8. The -all option also starts OPMN-based components Oracle Business Intelligence and Oracle HTTP Server.

Example 4-7 Syntax to Start All Domains

./fastartstop.sh -Start -all -username FUSION_APPS_PROV_PATCH_APPID -appbase /slot/ems7770/oracle/apphome/fusionapps/applications 

Example 4-8 shows starting multiple domains. Starting domains starts all the Managed Servers and Administration Server for each product family domain.

Example 4-8 Syntax to Start Multiple Domains

./fastartstop.sh -Start -domains HCMDomain,BIDomain,ProjectsDomain -username FUSION_APPS_PROV_PATCH_APPID -appbase /scratch/aime/V1HCM/APPTOP/fusionapps/applications -startAdminServer true -clusterType soa
4.4.2.2.2 Stopping Examples with fastartstop

Example 4-9 shows stopping the Administration Server and all the Managed Servers in the SCMDomain domain.

Example 4-9 Syntax to Stop the Administration Server and All Managed Servers in a Single Domain

./fastartstop.sh -Stop -domains "SCMDomain(server:all)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-10 shows stopping Managed Servers soa_server1 and AdvancedPlanningServer_1 in the SCMDomain domain.

Example 4-10 Syntax to Stop Multiple Managed Servers in a Single Domain

./fastartstop.sh - Stop -domains "SCMDomain(server:soa_server,server:AdvancedPlanningServer_1)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-11 shows stopping Managed Servers soa_server1 and AdvancedPlanningServer_1 in the SCMDomain domain and soa_server in the HCMDomain domain.

Example 4-11 Syntax to Stop Multiple Managed Servers in Multiple Domains

./fastartstop.sh - Stop -domains "SCMDomain(server:soa_server,server:AdvancedPlanningServer_1),HCMDomain(server:soa_server)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-12 shows stopping the CommonDomain domain. Stopping a domain stops its Managed Servers and Administration Server.

Example 4-12 Syntax to Stop a Specific Domain

./fastartstop.sh -Stop -domains CommonDomain -username FUSION_APPS_PROV_PATCH_APPID -appbase /slot/ems7770/oracle/apphome/fusionapps/applications 

Example 4-13 shows stopping all the product family domains. Stopping all the domains stops the Managed Servers, Administration Server, and the OPMN-based components Oracle Business Intelligence and Oracle HTTP Server for each domain.

Example 4-13 Syntax to Stop All Domains

./fastartstop.sh -Stop -all -username FUSION_APPS_PROV_PATCH_APPID -appbase /slot/ems7770/oracle/apphome/fusionapps/applications 

Example 4-14 shows stopping multiple domains. Stopping domains stops all the Managed Servers and Administration Server for each product family domain.

Example 4-14 Syntax to Stop Multiple Domains

./fastartstop.sh -Stop -domains HCMDomain,BIDomain,ProjectsDomain -username FUSION_APPS_PROV_PATCH_APPID -appbase /scratch/aime/V1HCM/APPTOP/fusionapps/applications -startAdminServer true -clusterType soa
4.4.2.2.3 Bouncing Examples with fastartstop

Example 4-15 shows restarting the Administration Server and all the Managed Servers in the SCMDomain domain.

Example 4-15 Syntax to Bounce the Administration Server and All Managed Servers in a Single Domain

./fastartstop.sh -Bounce -domains "SCMDomain(server:all)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-16 shows restarting Managed Servers soa_server1 and AdvancedPlanningServer_1 in the SCMDomain domain.

Example 4-16 Syntax to Bounce Multiple Managed Servers in a Single Domain

./fastartstop.sh - Bounce -domains "SCMDomain(server:soa_server,server:AdvancedPlanningServer_1)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-17 shows restarting Managed Servers soa_server1 and AdvancedPlanningServer_1 in the SCMDomain domain and soa_server in the HCMDomain domain.

Example 4-17 Syntax to Bounce Multiple Managed Servers in Multiple Domains

./fastartstop.sh - Bounce -domains "SCMDomain(server:soa_server,server:AdvancedPlanningServer_1),HCMDomain(server:soa_server)"  -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

Example 4-18 shows restarting the CommonDomain domain. Restarting a domains restarts the Managed Servers and Administration Server in the domain.

Example 4-18 Syntax to Bounce a Specific Domain

./fastartstop.sh -Bounce -domains CommonDomain -username FUSION_APPS_PROV_PATCH_APPID -appbase /slot/ems7770/oracle/apphome/fusionapps/applications 
4.4.2.2.4 Using the AdminServersOnly Option with fastartstop

Example 4-19 Syntax to Restart all the Administration Servers

./fastartstop.sh -Bounce -all  -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -adminServersOnly
4.4.2.2.5 Using Combination Commands with fastartstop

If the server suboption is set to all and another Managed Server or Administration Server with the -domain option (Example 4-21), all will take precedence and the start, stop, or restart operation will occur on all servers.

Example 4-20 Syntax with Contradicting server Suboption Settings

./fastartstop.sh -Bounce -domains "SCMDomain(server:all,server:soa_server1)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER

If you use the server suboption for one domain, you must use it for all domains. In addition, you cannot use the server suboption with the -adminServersOnly option. Example 4-21 shows server:all for the SCMDomain domain, but not for the HCMDomain domain. It also shows the -adminServersOnly option in combination with the server suboption. This syntax would generate an error.

Example 4-21 Syntax with server Suboption Settings Not Consistently Used

./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all),HCMDomain" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -adminServersOnly

If the server suboption of the -domains option is used, the following options cannot be used:

  • -startAdminServer

  • -clusterType

  • -adminServersOnly

Example 4-22 shows incorrect combinations of these commands. If these examples are entered, you would see error messages.

Example 4-22 Sample Syntax with Contradicting server Suboption Settings

./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -clusterType SOA

./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -startAdminServer true

./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all)" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -adminServersOnly

./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all),HCMDomain" -username FAAdmin -appbase /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -adminServersOnly

4.4.3 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:

4.4.3.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:

4.4.3.1.1 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.

4.4.3.1.2 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
    
4.4.3.1.3 Task 3: Start Node Manager

Each host has its own copy of the Node Manager and all the Node Managers should be running before attempting to start any Administration Servers or Managed Servers.

Start Node Manager for each of the hosts for which you want to start the Administration Servers:

  1. Set the JAVA_OPTIONS environment variable:

    setenv JAVA_OPTIONS "${JAVA_OPTIONS} -Dserver.group=AdminServer"
    
  2. Set the WLST_PROPERTIES environment variable:

    setenv WLST_PROPERTIES "-Dweblogic.security.SSL.trustedCAKeyStore=APPLICATIONS_CONFIG/keystores/fusion_trust.jks"
    

    where APPLICATION_CONFIG is one of the following directories:

    (UNIX) APPLICATIONS_BASE/instance
    (Windows) APPLICATIONS_BASE\instance 
    
  3. Start Node Manager with the startNodeManagerWrapper utility from the following locations:

    (UNIX) APPLICATIONS_CONFIG/nodemanager/host_name/startNodeManagerWrapper.sh
    (Windows) APPLICATIONS_CONFIG\nodemanager\host_name\startNodeManagerWrapper.cmd 
    
  4. For all the hosts, verify that Node Manager is running. For example, on UNIX platforms, enter the following command:

    netstat –a|grep 5556
    

    The 5556 port should be in a listening state. If your environment uses a different port, then use the port number in the System Port Allocation page during the creation of a provisioning plan. See the "System Port Allocation" section in the Oracle Fusion Applications Installation Guide.

4.4.3.1.4 Task 4: Start the Key Oracle Fusion Middleware Components on the Provisioned Environment

To start the Administration Servers, Managed Servers, Oracle HTTP Server, and Oracle Business Intelligence on the provisioned environment:

  1. At an operating system command prompt, navigate to the location of the fastartstop script:

    (UNIX) FA_ORACLE_HOME/lcm/ad/bin
    (Windows) FA_ORACLE_HOME\lcm\ad\bin
    

    FA_ORACLE_HOME is the Oracle Fusion Applications Oracle home located at:

    (UNIX) APPLICATIONS_BASE/fusionapps/applications
    (Windows) APPLICATIONS_BASE\fusionapps\applications
    
  2. From the shared host location, run the fastartstop utility with the -all option for all the domains:

    fastartstop.sh/fastartstop.cmd -Start -all
    -username user_name
    -appbase APPLICATIONS_BASE
    [-loglevel log_level]
    [-timeout timeout_period]
    

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

4.4.3.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:

4.4.3.2.1 Task 1: Stop the Key Oracle Fusion Middleware Components on the Provisioned Environment

To start the Administration Servers, Managed Servers, Oracle HTTP Server, and Oracle Business Intelligence on the provisioned environment:

  1. At an operating system command prompt, navigate to the location of the fastartstop script:

    (UNIX) FA_ORACLE_HOME/lcm/ad/bin
    (Windows) FA_ORACLE_HOME\lcm\ad\bin
    

    FA_ORACLE_HOME is the Oracle Fusion Applications Oracle home located at:

    (UNIX) APPLICATIONS_BASE/fusionapps/applications
    (Windows) APPLICATIONS_BASE\fusionapps\applications
    
  2. From the shared host location, run the fastartstop utility with the -all option for all the domains:

    fastartstop.sh/fastartstop.cmd -Stop -all
    -username user_name
    -appbase APPLICATIONS_BASE
    [-loglevel log_level]
    [-timeout timeout_period]
    

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

4.4.3.2.2 Task 2: 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
    
4.4.3.2.3 Task 4: 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.

4.4.4 Starting and Stopping the Administration Servers and Managed Servers

This section contains the following topics:

4.4.4.1 Starting the Administration Servers and Managed 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 and Managed Servers from a shared location, see Section 4.2.

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

When you start an 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 the Administration Servers and Managed Servers:

  1. At an operating system command prompt, navigate to the location of the fastartstop script:

    (UNIX) FA_ORACLE_HOME/lcm/ad/bin
    (Windows) FA_ORACLE_HOME\lcm\ad\bin
    

    FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.

  2. From the shared host location, run the fastartstop utility to start the Administration Servers and the Managed Servers:

    • To start only Administration Servers, use the -adminServersOnly option. Use the -startAdminSever option to keep Admin Servers running after starting/stopping Managed Servers. Use the -all option to start the Administration Servers for all the domains or the -domains option to start the Administration Server for specific domains.

      fastartstop.sh/fastartstop.cmd -Start
      -all|-domains domain_name,domain_nameN,domain_nameN
      -username user_name
      -appbase APPLLICATIONS_BASE
      -adminServersOnly
      [-loglevel log_level]
      [-timeout timeout_period]
      
      fastartstop.sh/fastartstop.cmd -Start
      -all|-domains domain_name,domain_nameN,domain_nameN
      -username user_name
      -appbase APPLLICATIONS_BASE
      -startAdminServer true
      [-loglevel log_level]
      [-timeout timeout_period]
      
      fastartstop.sh/fastartstop.cmd -Start
      -all|-domains "domain_name(server:AdminServer),domain_name(server:AdminServer)"
      -username user_name
      -appbase APPLLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

      When the server suboption is used, enclose the -domains argument in quotes:

      -domains "domain_name(server:AdminServer),domain_name(server:AdminServer)"
      
    • To start only the Managed Servers, use the -domains option with the server suboption to specify the Managed Servers to start:

      fastartstop.sh/fastartstop.cmd -Start 
      -domains "domain_name(server:managed_server_name,server:managed_server_name),domain_name(server:managed_server_name,server:managed_server_name)"
      -username user_name
      -appbase APPLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

      When the server suboption is used, enclose the -domains argument in quotes:

      -domains "domain_name(server:managed_server_name,server:managed_server_name),domain_name(server:managed_server_name,server:managed_server_name)"
      
    • To start the Administration Servers and Managed Servers in one fastartstop command, use the -domains option to specify the domains and the -startAdminServer true, or use the -domains option with the server:all suboption:

      fastartstop.sh/fastartstop.cmd -Start 
      -domains domain_name,domain_nameN,domain_nameN
      -username user_name
      -appbase APPLICATIONS_BASE
      -startAdminServer true
      [-loglevel log_level]
      [-timeout timeout_period]
      
      fastartstop.sh/fastartstop.cmd -Start 
      -domains domain_name(server:all),domain_name(server:all)
      -username user_name
      -appbase APPLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

      When the server suboption is used, enclose the -domains argument in quotes:

      -domains "domain_name(server:all),domain_name(server:all)"
      

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

Note:

Do not use the following Oracle WebLogic Server scripts to start the Administration Servers:

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

Starting Managed Servers with Fusion Applications Control

If you are working on a specific domain in Fusion Applications Control, you can also start the Managed Servers for that domain.

To start the Managed Servers for a specific domain with Fusion Applications Control:

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

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

Starting Managed Servers with WebLogic Server Administration Console

If you prefer to use the WebLogic Server Administration Console instead of Fusion Applications Control, see "Start Managed Servers from the Administration Console" and "Start Managed Servers in a cluster" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

4.4.4.2 Stopping the Administration Servers and Managed 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.

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

To stop the Administration Servers and Managed Servers:

  1. At an operating system command prompt, navigate to the location of the fastartstop script:

    (UNIX) FA_ORACLE_HOME/lcm/ad/bin
    (Windows) FA_ORACLE_HOME\lcm\ad\bin
    

    FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.

  2. From the shared host location, run the fastartstop utility to stop the Administration Servers and the Managed Servers:

    • To stop only Administration Servers, use the -adminServersOnly option. Use the -startAdminSever option to keep Admin Servers up after starting/stopping managed servers. Use the -all option to stop the Administration Servers for all the domains or the -domains option to stop the Administration Servers for specific domains.

      fastartstop.sh/fastartstop.cmd -Stop
      -all|-domains domain_name,domain_nameN,domain_nameN
      -username user_name
      -appbase APPLLICATIONS_BASE
      -adminServersOnly
      [-loglevel log_level]
      [-timeout timeout_period]
      
      fastartstop.sh/fastartstop.cmd -Stop
      -all|-domains domain_name,domain_nameN,domain_nameN
      -username user_name
      -appbase APPLLICATIONS_BASE
      -startAdminServer false
      [-loglevel log_level]
      [-timeout timeout_period]
      
      fastartstop.sh/fastartstop.cmd -Stop
      -all|-domains "domain_name(server:AdminServer),domain_name(server:AdminServer)"
      -username user_name
      -appbase APPLLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

      When the server suboption is used, enclose the -domains argument in quotes:

      -domains "domain_name(server:AdminServer),domain_name(server:AdminServer)"
      
    • To stop only the Managed Servers, use the -domains option with the server suboption to specify the Managed Servers to stop:

      fastartstop.sh/fastartstop.cmd -Stop 
      -domains "domain_name(server:managed_server_name,server:managed_server_name),domain_name(server:managed_server_name,server:managed_server_name)"
      -username user_name
      -appbase APPLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

      When the server suboption is used, enclose the -domains argument in quotes:

      -domains "domain_name(server:managed_server_name,server:managed_server_name),domain_name(server:managed_server_name,server:managed_server_name)"
      
    • To stop the Administration Servers and Managed Servers in one fastartstop command, use the -domains option with the server:all suboption to stop the servers for specific domains.

      fastartstop.sh/fastartstop.cmd -Stop 
      -domains domain_name,domain_nameN,domain_nameN
      -username user_name
      -appbase APPLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      
      fastartstop.sh/fastartstop.cmd -Stop 
      -domains "domain_name(server:all),domain_name(server:all)"
      -username user_name
      -appbase APPLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

    When the server suboption is used, enclose the -domains argument in quotes:

    -domains "domain_name(server:all),domain_name(server:all)"
    

    For more information about the fastartstop syntax, see Section 4.4.2.1.

Note:

Do not use the following Oracle WebLogic Server scripts to stop the Administration Servers:

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

Stopping Managed Servers with Fusion Applications Control

If you are working on a specific domain in Fusion Applications Control, you can also stop the Managed Servers for that domain.

To stop the Managed Servers for a specific domain with Fusion Applications Control:

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

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

Stopping Managed Servers with WebLogic Server Administration Console

If you prefer to use the WebLogic Server Administration Console, see "Start Managed Servers from the Administration Console" and "Shutdown servers in a cluster" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

4.4.5 Starting and Stopping Oracle HTTP Server

This section contains the following topics:

4.4.5.1 Starting the Oracle HTTP Server

To start Oracle HTTP Server:

  • fastartstop

    1. At an operating system command prompt, navigate to the location of the fastartstop script:

      (UNIX) FA_ORACLE_HOME/lcm/ad/bin
      (Windows) FA_ORACLE_HOME\lcm\ad\bin
      

      FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.

    2. From the shared host location, run the fastartstop utility with -componentType option:

      fastartstop.sh/fastartstop.cmd -Start -componentType OHS
      -username user_name
      -appbase APPLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

      The -username option is not needed for starting Oracle HTTP Server.

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

  • opmnctl

    (UNIX) WT_CONFIG_HOME/bin/opmnctl startproc process-type=OHS
    (Windows) WT_CONFIG_HOME\bin\opmnctl startproc process-type=OHS
    
  • 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.

4.4.5.2 Stopping the Oracle HTTP Server

To stop Oracle HTTP Server:

  • fastartstop

    1. At an operating system command prompt, navigate to the location of the fastartstop script:

      (UNIX) FA_ORACLE_HOME/lcm/ad/bin
      (Windows) FA_ORACLE_HOME\lcm\ad\bin
      

      FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.

    2. From the shared host location, run the fastartstop utility with -componentType option:

      fastartstop.sh/fastartstop.cmd -Stop -componentType OHS
      -appbase APPLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

      The -username option is not needed for stopping Oracle HTTP Server.

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

  • opmnctl

    (UNIX) WT_CONFIG_HOME/bin/opmnctl stopproc process-type=OHS
    (Windows) WT_CONFIG_HOME\bin\opmnctl stopproc process-type=OHS
    
  • 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.

4.4.6 Starting and Stopping Oracle Business Intelligence

This section contains the following topics:

4.4.6.1 Starting Oracle Business Intelligence

To start Oracle Business Intelligence:

  • fastartstop

    1. At an operating system command prompt, navigate to the location of the fastartstop script:

      (UNIX) FA_ORACLE_HOME/lcm/ad/bin
      (Windows) FA_ORACLE_HOME\lcm\ad\bin
      

      FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.

    2. From the shared host location, run the fastartstop utility with -StartBIPS and -BIPServerComponents options:

      fastartstop.sh/fastartstop.cmd -StartBIPS -BIPServerComponents
      -username user_name
      -appbase APPLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

      These options start the BIDomain, including the Administration Server and all the Managed Servers, as well as the following Oracle Business Intelligence components:

      • JavaHost

      • Oracle BI Presentation Server

      • Oracle BI Scheduler

      • Oracle BI Server

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

  • Other tools

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

4.4.6.2 Stopping Oracle Business Intelligence

To stop Oracle Business Intelligence:

  • fastartstop

    1. At an operating system command prompt, navigate to the location of the fastartstop script:

      (UNIX) FA_ORACLE_HOME/lcm/ad/bin
      (Windows) FA_ORACLE_HOME\lcm\ad\bin
      

      FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.

    2. From the shared host location, run the fastartstop utility with -StopBIPS and -BIPServerComponents options:

      fastartstop.sh/fastartstop.cmd -StopBIPS -BIPServerComponents
      -username user_name
      -appbase APPLICATIONS_BASE
      [-loglevel log_level]
      [-timeout timeout_period]
      

      These options stop the BIDomain, as well as the following Oracle Business Intelligence components:

      • JavaHost

      • Oracle BI Presentation Server

      • Oracle BI Scheduler

      • Oracle BI Server

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

  • Other tools

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

4.4.7 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:

4.4.7.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

See Section 4.4.5.2.

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, use the fastartstop utility with the -domains option.

fastartstop.sh/fastartstop.cmd -Stop
-domains domain_name,domain_nameN,domain_nameN
-username user_name
-appbase APPLICATIONS_BASE
[-loglevel log_level]
[-timeout timeout_period]

For more information about the fastartstop syntax, see Section 4.4.2.1.

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.

4.4.7.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

See Section 4.4.5.1.

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, use the fastartstop utility with the -domains option.

fastartstop.sh/fastartstop.cmd -Start
-domains domain_name,domain_nameN,domain_nameN
-username user_name
-appbase APPLICATIONS_BASE
[-loglevel log_level]
[-timeout timeout_period]

For more information about the fastartstop syntax, see Section 4.4.2.1.

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.

4.4.8 Starting and Stopping an Oracle WebLogic Server Cluster in a Product Family 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. Starting and stopping a cluster stops all the Managed Servers within that cluster.

This section contains the following topics:

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

4.4.8.1 Starting and Stopping an Oracle WebLogic Server Cluster Using fastartstop

The fastartstop utility enables you to start or stop a cluster in a product family domain. Starting and stopping a cluster stops all the Managed Servers within the cluster.

To start the Oracle WebLogic Server cluster:

  1. At an operating system command prompt, navigate to the location of the fastartstop script:

    (UNIX) FA_ORACLE_HOME/lcm/ad/bin
    (Windows) FA_ORACLE_HOME\lcm\ad\bin
    

    FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.

  2. From the shared host location, run the fastartstop utility.

    From the shared host location, run the fastartstop utility with the -domains option with the server suboption to specify all the Managed Servers in the cluster to start:

    fastartstop.sh/fastartstop.cmd -Start 
    -domains "domain_name(server:managed_server_name,server:managed_server_name)"
    -username user_name
    -appbase APPLICATIONS_BASE
    [-loglevel log_level]
    [-timeout timeout_period]
    

    When the server suboption is used, enclose the -domains argument in quotes:

    -domains "domain_name(server:managed_server_name,server:managed_server_name)"
    

    For a SOA cluster, you can start all the Managed Servers in the cluster with the -domains option and the -clusterType option. The -clusterType option only supports SOA clusters.

    fastartstop.sh/fastartstop.cmd -Start 
    -domains domain_name,domain_nameN,domain_nameN
    -clusterType soa
    -username user_name
    -appbase APPLICATIONS_BASE
    [-loglevel log_level]
    [-timeout timeout_period]
    

    For more information about the fastartstop syntax, see Section 4.4.2.1.

4.4.8.2 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.

4.4.8.3 Starting and Stopping an Oracle WebLogic Server Cluster WebLogic Server Administration Console

If you prefer to use the WebLogic Server Administration Console, see "Start Managed Servers in a cluster" and "Shutdown servers in a cluster" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

4.4.9 Starting and Stopping Specific Applications

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

This section contains the following topics:

4.4.9.1 Starting and Stopping Java EE Applications Using WLST

To start or stop applications with the WebLogic Scripting Tool (WLST):

  1. At an operating system command prompt, navigate to the location of the WLST script:

    (UNIX) FA_MW_HOME/oracle_common/common/bin           
    (Windows) FA_MW_HOME\oracle_common\common\bin
    

    FA_MW_HOME is named fusionapps and located under the APPLICATIONS_BASE.

  2. Run the wlst script:

    (UNIX) wlst.sh        
    (Windows) wlst.cmd
    
  3. Connect to Oracle WebLogic Server with the following WLST command:

    connect([options])
    

    See the "connect" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

  4. Use the following WLST commands:

    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.

4.4.9.2 Starting and Stopping an Individual Application Instance for a Cluster Using Fusion Applications Control or Cloud Control

To start or stop an application using Fusion Applications Control or Cloud Control:

  1. Navigate to a product family home page:

    • From Fusion Applications Control, from the navigation pane, select the product family.

    • From Cloud Control:

      1. From the Targets menu, choose Fusion Applications.

        The Fusion Applications target home page displays.

      2. In the table on the Fusion Applications target home page, click the appropriate Product Family target.

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

  3. Select the application instance you want to stop.

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

If you prefer to use the WebLogic Server Administration Console, see "Start applications and modules" and "Stop applications and modules" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

4.4.9.3 Starting and Stopping All Application Instances for a Cluster Using Fusion Applications Control or Cloud Control

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

  1. Navigate to a product family home page:

    • From Fusion Applications Control, from the navigation pane, select the product family.

    • From Cloud Control:

      1. From the Targets menu, choose Fusion Applications.

        The Fusion Applications target home page displays.

      2. In the table on the Fusion Applications target home page, click the appropriate Product Family target.

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

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

4.5 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.

Table 4-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 4-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 Essbase

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

You may also need to modify the port range used by Essbase Applications. These are managed separately from the rest of the ports.

To modify the port range:

  1. At an operating system command prompt, navigate to the location of the opmn.xml file:

    (UNIX) APPLICATIONS_BASE/instance/BIInstance/config/OPMN/opmn 
    (Windows) APPLICATIONS_BASE\Instance\BIInstance\config\OPMN\opmn
    

    This is the port range used by Essbase Applications. These are allocated by the Essbase server as required. The Essbase server will use the ports, even if they are explicitly allocated elsewhere to another component. Therefore, it is important to not use the same port range as the rest of the Oracle Business Intelligence domain port range.

  2. Modify the port range:

    <port id="essbase-port-range" range="9500-9599"/>
    
  3. Ensure that the OPMN server re-reads its configuration after changing the contents of opmn.xml:

    (UNIX) APPLICATIONS_BASE/instance/BIInstance/bin/opmnctl reload
    (Windows) APPLICATIONS_BASE\instance\BIInstance\bin\opmnctl reload
    
  4. Restart the Essbase server:

    (UNIX) APPLICATIONS_BASE/instance/BIInstance/bin/opmnctl restartproc process-type=Essbase
    (Windows) APPLICATIONS_BASE\instance\BIInstance\bin\opmnctl restartproc process-type=Essbase
    

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 WebCenter Content 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


4.6 Changing Passwords

Before you begin configuration, change the passwords for the various accounts to secure passwords. Table 4-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 4-4 Changing Passwords

Password Account Description Documentation for Changing the Passwords

Oracle Fusion Middleware administration for the Oracle WebLogic Server domain

During the Oracle Fusion Applications installation, you must provide a password for the Oracle Fusion Middleware administration user. By default, this administrator takes the Super User value you specified on the Identity Management page when creating the provisioning plan. The super user is described in the next row of this table.

Section 6.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 6.8.5.2 to change the administrative password

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

Oracle Identity Management

The password-reset-tool utility enables you to modify the passwords for the FAAdmin, IDROUser, IDRWUser, PolicyRWUser, and oamadminuser users. For a configuration that does not use FAAdmin as the Oracle Fusion Middleware administrative user, use one of the methods described in Section 6.8.5.2.

Section 6.8.5.3

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

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 6.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


4.6.1 Changing Oracle Fusion Applications Passwords in the Oracle Database

As part of routine maintenance, it is security best-practice to reset the schema passwords in an environment according to a schedule. Use the Password Change Utility for this purpose.

The Password Change Utility changes the passwords for critical schemas in the Fusion Applications Database. It also updates schema passwords stored outside of the database to match the new schema passwords in the database. Database schema passwords are stored outside the database in the Credential Store, in WLS data sources, and in other configuration files/repositories used by Fusion Middleware.

The Password Change Utility changes the passwords for all critical schemas at once. It cannot change the password for only a subset of schemas. However, it allows you to specify the existing password for a schema, so you can change the password for only one schema by specifying the existing passwords for all other schemas in the tool's input file and specifying a new password for the schema you want to modify.

The Password Change Utility can be run interactively or non-interactively. The steps required for running interactively and non-interactively are different and are explained in the following sections. Running the Password Change Utility interactively is simple, but may require more user input. Running the Password Change Utility non-interactively is more complex, but may require less user input.

The Password Change Utility can be run in a special mode in which it only ensures that all critical schemas are registered in the credential store. This special mode is called CSF-only mode. The CSF-only mode is not documented in detail in this document, because it is mainly used to ensure that the credential store is up-to-date prior to running the RUP Installer to upgrade to a new Fusion Applications release level. Running the Password Change Utility interactively in CSF-only mode is documented in detail in the "Register Database Schema Information" section of the Upgrade Guide. Running the Password Change Utility non-interactively in CSF-only mode is possible, but is not currently documented.

For most configurations, you can run the Password Change Utility on any Fusion Applications Middle Tier host. However, specifically for the case where you have installed BI on a separate host, you must run the Password Change Utility on the BI host. The Password Change Utility will fail when updating BI artifacts, if BI is installed on a separate host and you run the tool on a middle tier host instead of the BI host.

At a high level, running the Password Change Utility consists of the following three steps:

Step 1: Create a template input file using the templateGen utility

Run the templateGen utility to create template input files appropriate for your current Fusion Applications Release version. The templateGen utility generates template input files for both normal mode and CSF-only mode, but only the normal-mode template file is used for changing database schema passwords.

Step 2: Create an input file using the iniGen utility

The Password Change Utility relies on an input configuration file that specifies the new database schema passwords and other important information about your Fusion Applications installation. This input file is generated by the iniGen utility using template files produced by the templateGen utility. The iniGen utility writes password values to the input configuration file in encrypted format. It writes other values in plain text.

As part of running the Password Change Utility non-interactively, a temporary plain text file is created and is encrypted immediately. The file is later decrypted and the contents are provided as input to iniGen. Oracle provides a tool named lcmcrypt to perform encryption and decryption on all platforms. You can use an alternative encryption tool if you prefer. If you use an alternative encryption tool (like gpg provided by Linux), you are responsible for using it properly. This document explains how to perform the required encryption/decryption using lcmcrypt.

Step 3: Change schema passwords using the Password Change Utility

Run the Password Change Utility to change the database schema passwords and update other artifacts/repositories to reflect the new schema passwords. The Password Change Utility prompts you for the password for decrypting the input file. To avoid this prompt, you can send the passcode as the standard input of the Password Change Utility.

The tasks for running the Password Change Utility are explained in the following sections:

4.6.1.1 Task 1: Stop the Oracle Fusion Applications Environment

To stop the environment before running the Password Change Utility:

  1. Stop all incoming user requests by stopping the Oracle HTTP server. See Section 4.4.5.2.

  2. Stop all the WebLogic Servers. See Section 4.4.4.2.

  3. Start up only Admin Servers. See Section 4.4.4.1.

4.6.1.2 Task 2: Create the Template Input Files

Run the templateGen utility to create template input files appropriate for your current Fusion Applications Release version. The templateGen utility generates template input files for both normal mode and CSF-only mode, but only the normal-mode template file is used for changing database schema passwords.

At an operating system command prompt: navigate to the location of the various password-change utility scripts:

  1. Navigate to the location of the various password-change utility scripts:

    (UNIX) APPLICATIONS_BASE/fusionapps/applications/lcm/util/bin
     
    (Windows) APPLICATIONS_BASE\fusionapps\applications\lcm\util\bin
    
  2. Run the templateGen utility:

    (UNIX) templateGen.sh -appbase APPLICATIONS_BASE
     
    (Windows) templateGen.cmd -appbase APPLICATIONS_BASE
    

    For the -appbase argument, specify the complete directory path to the Applications Base directory.

    The templateGen utility generates the following template files in the config directory using the existing pre-template files:

    • standard_pre_template.ini -> standard_template.ini

    • csf_pre_template.ini -> csf_template.ini

4.6.1.3 Task 3: Create the Input File

The Password Change Utility relies on an input configuration file that specifies the passwords. This input file is generated by the iniGen utility using template files produced by the templateGen utility. The iniGen utility writes password values to the input configuration file in encrypted format. It writes other values in plain text.

The iniGen utility has two optional command-line arguments: -templatefile and -outputfile. If the -templatefile argument is not specified, it defaults to standard_template.ini in the config directory. If the -outputfile argument is not specified, the output file will be input<TIMESTAMP>.ini in the config directory.

By default, the iniGen utility creates the Password Change Utility input file in the config directory:

(UNIX) APPLICATIONS_BASE/lcm/util/config

(Windows) APPLICATIONS_BASE\lcm\util\config

Steps to run the tool in Interactive Mode:

To run the Password Change Utility in interactive mode, run the iniGen utility and respond to the prompts.

At an operating system command prompt:

  1. Navigate to the location of the various password-change utility scripts:

    (UNIX) APPLICATIONS_BASE/fusionapps/applications/lcm/util/bin
    (Windows) APPLICATIONS_BASE\fusionapps\applications\lcm\util\bin
    
  2. Run the iniGen utility:

    (UNIX) iniGen.sh -appbase APPLICATIONS_BASE
    
    (Windows) iniGen.cmd -appbase APPLICATIONS_BASE
    
  3. Respond to the iniGen prompts to create the input configuration file.

The iniGen character-based user interface prompts for a master password for encrypting sensitive information in the input file. You must enter the master password twice. In general, you must enter password values twice and non-password values once.

iniGen has a feature that allows you to reset all schema passwords to the same value. If you select this option, the utility will only ask for the schema password twice, and skip all the other schema-related prompts. Otherwise, the iniGen utility prompts you for the password for each schema individually.

Steps to run the tool in Non-interactive Mode:

To run the Password Change Utility in non-interactive mode, perform the following steps:

  1. Copy the standard_template.ini from the config directory to a temporary file. For example, standard_plain.ini.

  2. Edit the temporary file as follows:

    • Provide actual value for the master_password property. This is the master password that will be used for encrypting sensitive information in the input file generated by iniGen. When you later run iniGen in non-interactive mode to create the schemaPasswordResetTool input file, it will reset the value of the master_password property to ignore_me.

    • Replace every occurrence of #text# or #password# with the correct value for your environment.

    Note:

    Do not make any other changes to the temporary file (standard_plain.ini). The iniGen tool cross references this file along with standard_template.ini in the config directory while generating the output file. Additional changes to the temporary file might lead to incorrect results.

  3. Create an encrypted version of the temporary file (standard_plain.ini) and delete the clear-text version of the file.

    1. Navigate to the location of the various password-change utility scripts:

      (UNIX) APPLICATIONS_BASE/fusionapps/applications/lcm/util/bin
       
      (Windows) APPLICATIONS_BASE\fusionapps\applications\lcm\util\bin
      
    2. Run the lcmcrypt utility:

      (UNIX)
      export  PATH=/usr/local/bin:$PATH
      echo <file_encryption_password> | ./lcmcrypt.sh -encrypt -inputfile <temp_dir>/standard_plain.ini
       
      (Windows)
      SET PASSCODE=<file_encryption_password>
      lcmcrypt.cmd -encrypt -inputfile <file that needs to be encrypted>
      SET PASSCODE=
      
      For example,
      SET PASSCODE=welcome
      lcmcrypt.cmd -encrypt -inputfile ..\config\standard_slcah286.ini
      SET PASSCODE=
      

      The lcmcrypt utility reads the file passed into it and encrypts the file contents using the password supplied. lcmcrypt generates an encrypted file with an additional .enc extension in the same directory as that of the original file. It deletes the original input file after creating the encrypted version. In the given example, an encrypted file is created (<temp_dir>/standard_plain.ini.enc) and the plain text file (<temp_dir>/standard_plain.ini) is deleted.

      The <file_encryption_password> for lcmcrypt is not related to the master password used by iniGen. <file_encryption_password> is used to encrypt/decrypt the plain-text file standard_plain.ini. The iniGen master password is used to encrypt/decrypt passwords stored in the Password Change Utility input file.

  4. Run the iniGen utility in non-interactive mode.

    1. Navigate to the location of the various password-change scripts:

      (UNIX) APPLICATIONS_BASE/fusionapps/applications/lcm/util/bin
       
      (Windows) APPLICATIONS_BASE\fusionapps\applications\lcm\util\bin
      
    2. Run the lcmcrypt utility and pipe its output to the iniGen utility:

      (UNIX) echo <file_encryption_password> | ./lcmcrypt.sh -decrypt -inputfile <temp_dir>/standard_plain.ini.enc | ./iniGen.sh -nonInteractive -appbase APPLICATIONS_BASE
       
      (Windows)
      SET PASSCODE=<file_encryption_password>
      lcmcrypt.cmd -decrypt -inputfile <file that needs to be decrypted> | .\iniGen.cmd -appbase APPLICATIONS_BASE -nonInteractive
      SET PASSCODE=
      
      For example,
      SET PASSCODE=welcome
      lcmcrypt.cmd -decrypt -inputfile ..\config\standard_slcah286.ini.enc | .\iniGen.cmd -appbase c:\APPLTOP -nonInteractive
      SET PASSCODE=
      

During decryption, lcmcrypt reads the encrypted input file and decrypts the file contents using the password supplied. The decrypted file is streamed to the standard output of lcmcrypt. lcmcrypt -decrypt does not generate a clear-text file.

In non-interactive mode, iniGen creates the Password Change Utility input file using the data it receives on standard input. The Password Change Utility input files generated by iniGen in non-interactive mode have exactly the same format as that of the files generated in interactive mode.

4.6.1.4 Task 4: Change the Database Schema Passwords

Run the schemaPasswordChangeTool to change the database schema passwords and update other artifacts/repositories to reflect the new schema passwords.

For most configurations, you can run the schemaPasswordChangeTool on any Fusion Applications Middle Tier host. However, specifically for the case where you have installed BI on a separate host, you must run the schemaPasswordChangeTool on the BI host. The schemaPasswordChangeTool will fail when updating BI artifacts if BI is installed on a separate host and you run the tool on a middle tier host instead of the BI host.

Steps to run the tool in Interactive Mode:

At an operating system command prompt:

  1. Navigate to the location of the various password-change utility scripts:

    (UNIX) APPLICATIONS_BASE/fusionapps/applications/lcm/util/bin
    
    (Windows) APPLICATIONS_BASE\fusionapps\applications\lcm\util\bin
    
  2. Run the schemaPasswordChangeTool:

    (UNIX) ./schemaPasswordChangeTool.sh -appbase APPLICATIONS_BASE -inputfile ../config/input1335820380736.ini
    
    (WINDOWS) schemaPasswordChangeTool.cmd -appbase APPLICATIONS_BASE -inputfile ..\config\input1335820380736.ini
    

    The schemaPasswordChangeTool prompts you for the master password for decrypting passwords in the input file.

Steps to run the tool in Non-interactive Mode:

Windows does not support running the schemaPasswordChangeTool in non-interactive mode.

At an operating system command prompt:

  1. Navigate to the location of the various password-change utility scripts:

    (UNIX) APPLICATIONS_BASE/fusionapps/applications/lcm/util/bin
    
  2. Run the schemaPasswordChangeTool:

    (UNIX) echo <master_password> | ./schemaPasswordChangeTool.sh -appbase APPLICATIONS_BASE -inputfile ../config/input1335820380736.ini
     
    

4.6.1.5 Task 5: Restart the Oracle Fusion Applications Environment

To restart the environment after running the Password Change Utility:

  1. Shut down the Administration Servers. See Section 4.4.4.2.

  2. Start all the Servers. See Section 4.4.4.1.

  3. Start Oracle HTTP Server, so users can resume sending requests. See Section 4.4.5.1.

4.6.1.6 Reference Information

The structure of the template files for both Standard Mode and CSF-only Mode are described in this section:

Structure of the template for STANDARD Mode:

#
# Sample input parameters file for the password change utility
#
# You must verify/edit ALL entries in this file to match your environment
# and your actual database schema passwords
# -------------------------------------------------------------
#
# 
[Password Change Utility]
#
# Utility Parameters
# -------------------------------------------------------------
#
# Master password
#
# This password is needed in Non-Interactive mode for decryption during the password change run
#
master_password=ASD
#
# This is the top level directory under which the password change tool lives
#
# It is normally something like /fusionapps/applications/lcm/util
#
HOME=/APPTOP/fusionapps/applications/lcm/util
[WALLET]
#
# Used for updating Fusion Runtime schema entry in the wallet
# -------------------------------------------------------------
#
# Top level directory where Fusion Apps is installed
#
appltop=/APPTOP/
#
# Wallet store password
#
# Set to standard admin password when Fusion Apps is installed
# May have been changed later
#
esswalletpassword=welcome1
#
# Service Name for connecting to the Fusion Apps Database
#
# Used to identify the correct wallet entry to update
#
servicename=ems9558
[WLS]
#
# Used for connecting to the WLS admin console and running WLST scripts
# -------------------------------------------------------------
#
# FA WLS Console admin user name
#
USER=faadmin
#
# FA WLS Console admin password
#
PASSWORD=fusionfa1
#
# IDM WLS Console admin user name
#
IDM_WLADMIN_USER=oim_admin
#
# IDM WLS Console admin password
#
IDM_WLADMIN_PASSWORD=Fusionapps1
#
# The [*Domain] sections list all Fusion Apps WLS domains that contain
# data sources to be updated.
#
# The list will not change in a given Fusion Apps release, but could
# change in future releases.
# -------------------------------------------------------------
#
[CommonDomain]
#
# The WLS admin URL for the Common Domain
#
fa.domain.url.t3=t3://slcac574.example.com:7001
[FinancialDomain]
#
# The WLS admin URL for the Financials Domain
#
fa.domain.url.t3=t3://slcac574.example.com:7401
[SCMDomain]
#
# The WLS admin URL for the SCM Domain
#
fa.domain.url.t3=t3://slcac574.example.com:7801
[HCMDomain]
#
# The WLS admin URL for the HCM Domain
#
fa.domain.url.t3=t3://slcac574.example.com:9401
[ICDomain]
#
# The WLS admin URL for the IC Domain
#
fa.domain.url.t3=#text#
[CRMDomain]
#
# The WLS admin URL for the CRM Domain
#
fa.domain.url.t3=t3://slcac574.example.com:9001
[PRCDomain]
#
# The WLS admin URL for the PRC Domain
#
fa.domain.url.t3=#text#
[PRJDomain]
#
# The WLS admin URL for the PRJ Domain
#
fa.domain.url.t3=t3://slcac574.example.com:8601
[BizDomain]
#
# The WLS admin URL for the BI Domain
#
fa.domain.url.t3=t3://slcac574.example.com:10201
[OIMDomain]
#
# The WLS admin URL for the OIM Domain
#
idm.domain.url.t3=t3://slc01qey.example.com:17001
[BIDomain]
#
# Used for updating the BI RPD file, reg.properties file and EPM Resgistry
# ---------------------------------------------------------------------------
#
# Directory for BI home
#
BI_HOME=/scratch/aime/work/APPTOP/fusionapps/bi
#
# Directory containing configuration files for your BI domain
#
BI_INSTANCE=/scratch/aime/work/APPTOP/instance/BIInstance
#
# Password for editing the BI RPD file
#
RPD_PASSWORD=welcome1
#
# Full pathname for the current active BI RPD file
#
# Should be $(BI_INSTANCE)/bifoundation/OracleBIServerComponent/
#           coreapplication_obis1/repository/OracleBIApps_BI.rpd
#
# Where  is updated every time the RPD file is updated.
#
RPD_INPUT_FILENAME=/scratch/aime/work/APPTOP/instance/BIInstance/bifoundation/OracleBIServerComponent/coreapplication_obis1/repository/OracleBIApps_BI0004.rpd
#
# The WLS admin URL for the BI Domain
#
# Should be the same value as in the [BizDomain] section above
#
fa.domain.url.t3=t3://slcac574.example.com:10201
#
[IDM.SCHEMAS]
#
# Passwords for schemas in the IDM database which
# are used by Fusion Apps and could have corresponding
# data sources.
#
# Used to update data sources to contain
# the new schema passwords.
#
# NOTE: Provide uppercase entries for schema usernames 
#       even if they are in lowercase in the datasources.
#       Never provide lowercase schema usernames.
# -------------------------------------------------------------
#
OIM_MDS=oim_mds
[FUSION_DB_INFO]
#
# Information about the Fusion Apps database
#
# Declare if DB is RAC or non-RAC, then fill in values for relevant
# properties.  Set of properties for RAC and non-RAC are different.
# Only need to fill in properties relevant to your DB configuration
# -------------------------------------------------------------
#
# Is your Fusion Apps database configured with RAC?
#
# Should be "true" for RAC databases, and "false" for non-RAC.
#
IS_RAC_DB=false
#
# Must provide values for the following properties if IS_RAC_DB is true
# No need to provide values for the following properties if IS_RAC_DB is false
#   DB_RAC_INSTANCEs, DB_RAC_SERVICE_NAME
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#
# List of RAC instances 
#
# Example for property: DB_RAC_INSTANCES
# 3;adc6161377.example.com;1616;ORCL1;adc6161378.example.com;1616;ORCL2
#
DB_RAC_INSTANCES=NA
#
# RAC service name
#
# Example for property: DB_RAC_SERVICE_NAME
# ORCL
#
DB_RAC_SERVICE_NAME=NA
#
# Must provide values for the following properties if IS_RAC_DB is false
# No need to provide values for the following properties if IS_RAC_DB is true
#   DB_HOST_NAME, DB_PORT, DB_SERVICE_NAME
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#
# Host on which your Fusion Apps database is running
#
DB_HOST_NAME=slc01qey.example.com
#
# Port for the database listener service
#
DB_PORT=1579
#
# Name of the database listener service
#
DB_SERVICE_NAME=ems9558
[IDM_DB_INFO]
#
# Information about the IDM database
#
# Provide IDM DB Credentials. Generally the SYS user or users with 
# SYSDBA privilege. This username/password will be used to connect
# as SYSDBA to execute password changes in the database.
#
DB_USER=sys as sysdba
#
DB_PASSWORD=welcome1
#
# Declare if DB is RAC or non-RAC, then fill in values for relevant
# properties.  Set of properties for RAC and non-RAC are different.
# Only need to fill in properties relevant to your DB configuration
# -------------------------------------------------------------
#
# Is your IDM database configured with RAC?
#
# Should be "true" for RAC databases, and "false" for non-RAC.
#
IS_RAC_DB=false
#
# Must provide values for the following properties if IS_RAC_DB is true
# No need to provide values for the following properties if IS_RAC_DB is false
#   DB_RAC_INSTANCEs, DB_RAC_SERVICE_NAME
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#
# List of RAC instances 
#
# Example for property: DB_RAC_INSTANCES
# 3;adc6161377.example.com;1616;ORCL1;adc6161378.example.com;1616;ORCL2
#
DB_RAC_INSTANCES=NA
#
# RAC service name
#
# Example for property: DB_RAC_SERVICE_NAME
# ORCL
#
DB_RAC_SERVICE_NAME=NA
#
# Must provide values for the following properties if IS_RAC_DB is false
# No need to provide values for the following properties if IS_RAC_DB is true
#   DB_HOST_NAME, DB_PORT, DB_SERVICE_NAME
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#
# Host on which your IDM database is running
#
DB_HOST_NAME=slc01qey.example.com
#
# Port for the database listener service
#
DB_PORT=1521
#
# Name of the database listener service
#
DB_SERVICE_NAME=oimdb.example.com
[oracle.patching]
FUSION_APPS_PATCH_FUSION_SCHEMA-KEY=FUSION
FUSION_APPS_PATCH_FUSION_DYNAMIC_SCHEMA-KEY=FUSION_DYNAMIC
FUSION_APPS_PATCH_FUSION_RUNTIME_SCHEMA-KEY=FUSION_RUNTIME
FUSION_APM-KEY=FUSION_APM
FUSION_APPS_AQ-KEY=FUSION_AQ
FUSION_APPS_BI-KEY=FUSION_BI
FUSION_APPS_DQ-KEY=FUSION_DQ
FUSION_APPS_ODI_STAGE-KEY=FUSION_ODI_STAGE
FUSION_ORA_ESS-KEY=FUSION_ORA_ESS
FUSION_APPS_CRM_MDS_SOA_SCHEMA-KEY=CRM_FUSION_MDS_SOA
FUSION_APPS_FIN_MDS_SOA_SCHEMA-KEY=FIN_FUSION_MDS_SOA
FUSION_APPS_HCM_MDS_SOA_SCHEMA-KEY=HCM_FUSION_MDS_SOA
FUSION_APPS_OIC_MDS_SOA_SCHEMA-KEY=OIC_FUSION_MDS_SOA
FUSION_APPS_PRC_MDS_SOA_SCHEMA-KEY=PRC_FUSION_MDS_SOA
FUSION_APPS_PRJ_MDS_SOA_SCHEMA-KEY=PRJ_FUSION_MDS_SOA
FUSION_APPS_SCM_MDS_SOA_SCHEMA-KEY=SCM_FUSION_MDS_SOA
FUSION_APPS_SETUP_MDS_SOA_SCHEMA-KEY=SETUP_FUSION_MDS_SOA
FUSION_APPS_MDS-KEY=FUSION_MDS
FUSION_APPS_MDS_ESS-KEY=FUSION_MDS_ESS
FUSION_APPS_MDS_SPACES-KEY=FUSION_MDS_SPACES
SEARCHSYS-KEY=SEARCHSYS
FUSION_APPS_UCM-KEY=FUSION_OCSERVER11G
FUSION_APPS_IPM-KEY=FUSION_IPM
FUSION_APPS_BIPLATFORM-KEY=FUSION_BIPLATFORM
FUSION_APPS_OTBI-KEY=FUSION_OTBI
FUSION_APPS_ORASDPLS-KEY=FUSION_ORASDPLS
FUSION_APPS_ORASDPXDMS-KEY=FUSION_ORASDPXDMS
FUSION_APPS_ORASDPSDS-KEY=FUSION_ORASDPSDS
FUSION_APPS_ORASDPM-KEY=FUSION_ORASDPM
FUSION_APPS_CRM_SOAINFRA-KEY=CRM_FUSION_SOAINFRA
FUSION_APPS_FIN_SOAINFRA-KEY=FIN_FUSION_SOAINFRA
FUSION_APPS_HCM_SOAINFRA-KEY=HCM_FUSION_SOAINFRA
FUSION_APPS_OIC_SOAINFRA-KEY=OIC_FUSION_SOAINFRA
FUSION_APPS_PRC_SOAINFRA-KEY=PRC_FUSION_SOAINFRA
FUSION_APPS_PRJ_SOAINFRA-KEY=PRJ_FUSION_SOAINFRA
FUSION_APPS_SCM_SOAINFRA-KEY=SCM_FUSION_SOAINFRA
FUSION_APPS_SETUP_SOAINFRA-KEY=SETUP_FUSION_SOAINFRA
FUSION_APPS_WEBCENTER-KEY=FUSION_WEBCENTER
FUSION_APPS_PORTLET-KEY=FUSION_PORTLET
FUSION_ACTIVITIES-KEY=FUSION_ACTIVITIES
FUSION_APPS_DISCUSSIONS-KEY=FUSION_DISCUSSIONS
FUSION_APPS_DISCUSSIONS_CRAWLER-KEY=FUSION_DISCUSSIONS_CRAWLER
FUSION_APPS_ODI_SCHEMA-KEY=FUSION_ODI
FUSION_APPS_DBA-KEY=SYS
[oracle.apps.security]
FUSION_APPS_PATCH_FUSION_RUNTIME_SCHEMA-KEY=FUSION_RUNTIME
SEARCHSYS-KEY=SEARCHSYS
[oracle.bi.enterprise]
FUSION_APPS_BIPLATFORM-KEY=FUSION_BIPLATFORM
[SCHEMAS]
FUSION=fusion
FUSION_DYNAMIC=fusion_dynamic
FUSION_RUNTIME=fusion_runtime
FUSION_APM=fusion_apm
FUSION_AQ=fusion_aq
FUSION_BI=fusion_bi
FUSION_DQ=fusion_dq
FUSION_ODI_STAGE=fusion_odi_stage
FUSION_ORA_ESS=fusion_ora_ess
CRM_FUSION_MDS_SOA=crm_fusion_mds_soa
FIN_FUSION_MDS_SOA=fin_fusion_mds_soa
HCM_FUSION_MDS_SOA=hcm_fusion_mds_soa
OIC_FUSION_MDS_SOA=oic_fusion_mds_soa
PRC_FUSION_MDS_SOA=prc_fusion_mds_soa
PRJ_FUSION_MDS_SOA=prj_fusion_mds_soa
SCM_FUSION_MDS_SOA=scm_fusion_mds_soa
SETUP_FUSION_MDS_SOA=setup_fusion_mds_soa
FUSION_MDS=fusion_mds
FUSION_MDS_ESS=fusion_mds_ess
FUSION_MDS_SPACES=fusion_mds_spaces
SEARCHSYS=searchsys
FUSION_OCSERVER11G=fusion_ocserver11g
FUSION_IPM=fusion_ipm
FUSION_BIPLATFORM=fusion_biplatform
FUSION_OTBI=fusion_otbi
FUSION_ORASDPLS=fusion_orasdpls
FUSION_ORASDPXDMS=fusion_orasdpxdms
FUSION_ORASDPSDS=fusion_orasdpsds
FUSION_ORASDPM=fusion_orasdpm
CRM_FUSION_SOAINFRA=crm_fusion_soainfra
FIN_FUSION_SOAINFRA=fin_fusion_soainfra
HCM_FUSION_SOAINFRA=hcm_fusion_soainfra
OIC_FUSION_SOAINFRA=oic_fusion_soainfra
PRC_FUSION_SOAINFRA=prc_fusion_soainfra
PRJ_FUSION_SOAINFRA=prj_fusion_soainfra
SCM_FUSION_SOAINFRA=scm_fusion_soainfra
SETUP_FUSION_SOAINFRA=setup_fusion_soainfra
FUSION_WEBCENTER=fusion_webcenter
FUSION_PORTLET=fusion_portlet
FUSION_ACTIVITIES=fusion_activities
FUSION_DISCUSSIONS=fusion_discussions
FUSION_DISCUSSIONS_CRAWLER=fusion_dicussions_crawler
FUSION_ODI=fusion_odi
SYS=manager
OIM_MDS=oim_mds
#
# End of Sample input parameters file for the password change utility
# -------------------------------------------------------------
#
[INTERNAL]
#
# The following two values are used internally by the tool and may be updated
# by the tool itself.  DO NOT CHANGE THEM!
#
tool.algorithm=PBEWithSHA1AndDESede
tool.transformation=PBEWithSHA1AndDESede/CBC/PKCS5Padding
ini.type=STANDARD

Structure of the template for CSF-only Mode:

#
# Sample input parameters file for the password change utility
#
# You must verify/edit ALL entries in this file to match your environment
# and your actual database schema passwords
# -------------------------------------------------------------
#
[Password Change Utility]
#
# Utility Parameters
# -------------------------------------------------------------
#
# Master password
#
# This password is needed in Non-Interactive mode for decryption during the password change run
#
master_password=ignore_me
#
#
# This is the top level directory under which the password change tool lives
#
# It is normally something like <prov_top>/fusionapps/applications/lcm/util
#
HOME=#text#
[WLS]
#
# Used for connecting to the WLS admin console and running WLST scripts
# -------------------------------------------------------------
#
# WLS Console admin user name
#
USER=#text#
#
# WLS Console admin password
#
PASSWORD=#password#
#
# The [*Domain] sections list all Fusion Apps WLS domains that contain
# data sources to be updated.
#
# The list will not change in a given Fusion Apps release, but could
# change in future releases.
# -------------------------------------------------------------
#
[CommonDomain]
#
# The WLS admin URL for the Common Domain
#
fa.domain.url.t3=#text#
[oracle.patching]
FUSION_APPS_PATCH_FUSION_SCHEMA-KEY=FUSION
FUSION_APPS_PATCH_FUSION_DYNAMIC_SCHEMA-KEY=FUSION_DYNAMIC
FUSION_APPS_PATCH_FUSION_RUNTIME_SCHEMA-KEY=FUSION_RUNTIME
FUSION_APM-KEY=FUSION_APM
FUSION_APPS_AQ-KEY=FUSION_AQ
FUSION_APPS_BI-KEY=FUSION_BI
FUSION_APPS_DQ-KEY=FUSION_DQ
FUSION_APPS_ODI_STAGE-KEY=FUSION_ODI_STAGE
FUSION_ORA_ESS-KEY=FUSION_ORA_ESS
FUSION_APPS_CRM_MDS_SOA_SCHEMA-KEY=CRM_FUSION_MDS_SOA
FUSION_APPS_FIN_MDS_SOA_SCHEMA-KEY=FIN_FUSION_MDS_SOA
FUSION_APPS_HCM_MDS_SOA_SCHEMA-KEY=HCM_FUSION_MDS_SOA
FUSION_APPS_OIC_MDS_SOA_SCHEMA-KEY=OIC_FUSION_MDS_SOA
FUSION_APPS_PRC_MDS_SOA_SCHEMA-KEY=PRC_FUSION_MDS_SOA
FUSION_APPS_PRJ_MDS_SOA_SCHEMA-KEY=PRJ_FUSION_MDS_SOA
FUSION_APPS_SCM_MDS_SOA_SCHEMA-KEY=SCM_FUSION_MDS_SOA
FUSION_APPS_SETUP_MDS_SOA_SCHEMA-KEY=SETUP_FUSION_MDS_SOA
FUSION_APPS_MDS-KEY=FUSION_MDS
FUSION_APPS_MDS_ESS-KEY=FUSION_MDS_ESS
FUSION_APPS_MDS_SPACES-KEY=FUSION_MDS_SPACES
SEARCHSYS-KEY=SEARCHSYS
FUSION_APPS_UCM-KEY=FUSION_OCSERVER11G
FUSION_APPS_IPM-KEY=FUSION_IPM
FUSION_APPS_BIPLATFORM-KEY=FUSION_BIPLATFORM
FUSION_APPS_OTBI-KEY=FUSION_OTBI
FUSION_APPS_ORASDPLS-KEY=FUSION_ORASDPLS
FUSION_APPS_ORASDPXDMS-KEY=FUSION_ORASDPXDMS
FUSION_APPS_ORASDPSDS-KEY=FUSION_ORASDPSDS
FUSION_APPS_ORASDPM-KEY=FUSION_ORASDPM
FUSION_APPS_CRM_SOAINFRA-KEY=CRM_FUSION_SOAINFRA
FUSION_APPS_FIN_SOAINFRA-KEY=FIN_FUSION_SOAINFRA
FUSION_APPS_HCM_SOAINFRA-KEY=HCM_FUSION_SOAINFRA
FUSION_APPS_OIC_SOAINFRA-KEY=OIC_FUSION_SOAINFRA
FUSION_APPS_PRC_SOAINFRA-KEY=PRC_FUSION_SOAINFRA
FUSION_APPS_PRJ_SOAINFRA-KEY=PRJ_FUSION_SOAINFRA
FUSION_APPS_SCM_SOAINFRA-KEY=SCM_FUSION_SOAINFRA
FUSION_APPS_SETUP_SOAINFRA-KEY=SETUP_FUSION_SOAINFRA
FUSION_APPS_WEBCENTER-KEY=FUSION_WEBCENTER
FUSION_APPS_PORTLET-KEY=FUSION_PORTLET
FUSION_ACTIVITIES-KEY=FUSION_ACTIVITIES
FUSION_APPS_DISCUSSIONS-KEY=FUSION_DISCUSSIONS
FUSION_APPS_DISCUSSIONS_CRAWLER-KEY=FUSION_DISCUSSIONS_CRAWLER
FUSION_APPS_ODI_SCHEMA-KEY=FUSION_ODI
FUSION_APPS_DBA-KEY=SYS
FUSION_APPS_BEEHIVE_BEE_CODE-KEY=BEE_CODE
FUSION_APPS_BEEHIVE_BEE_DATA-KEY=BEE_DATA
FUSION_APPS_BEEHIVE_BEE_MDS-KEY=BEE_MDS
[oracle.apps.security]
FUSION-DB-KEY=FUSION_RUNTIME
FUSION_APPS_ECSF_SES_ADMIN-KEY=SEARCHSYS
[oracle.bi.enterprise]
scheduler.schema=FUSION_BIPLATFORM
[SCHEMAS]
FUSION=#password#
FUSION_DYNAMIC=#password#
FUSION_RUNTIME=#password#
FUSION_APM=#password#
FUSION_AQ=#password#
FUSION_BI=#password#
FUSION_DQ=#password#
FUSION_ODI_STAGE=#password#
FUSION_ORA_ESS=#password#
CRM_FUSION_MDS_SOA=#password#
FIN_FUSION_MDS_SOA=#password#
HCM_FUSION_MDS_SOA=#password#
OIC_FUSION_MDS_SOA=#password#
PRC_FUSION_MDS_SOA=#password#
PRJ_FUSION_MDS_SOA=#password#
SCM_FUSION_MDS_SOA=#password#
SETUP_FUSION_MDS_SOA=#password#
FUSION_MDS=#password#
FUSION_MDS_ESS=#password#
FUSION_MDS_SPACES=#password#
SEARCHSYS=#password#
FUSION_OCSERVER11G=#password#
FUSION_IPM=#password#
FUSION_BIPLATFORM=#password#
FUSION_OTBI=#password#
FUSION_ORASDPLS=#password#
FUSION_ORASDPXDMS=#password#
FUSION_ORASDPSDS=#password#
FUSION_ORASDPM=#password#
CRM_FUSION_SOAINFRA=#password#
FIN_FUSION_SOAINFRA=#password#
HCM_FUSION_SOAINFRA=#password#
OIC_FUSION_SOAINFRA=#password#
PRC_FUSION_SOAINFRA=#password#
PRJ_FUSION_SOAINFRA=#password#
SCM_FUSION_SOAINFRA=#password#
SETUP_FUSION_SOAINFRA=#password#
FUSION_WEBCENTER=#password#
FUSION_PORTLET=#password#
FUSION_ACTIVITIES=#password#
FUSION_DISCUSSIONS=#password#
FUSION_DISCUSSIONS_CRAWLER=#password#
FUSION_ODI=#password#
SYS=#password#
BEE_CODE=#password#
BEE_DATA=#password#
BEE_MDS=#password#
#
# End of Sample input parameters file for the password change utility
# -------------------------------------------------------------
#
[INTERNAL]
#
# The following values are used internally by the tool and may be updated
# by the tool itself.  DO NOT CHANGE THEM!
#
tool.algorithm=PBEWithSHA1AndDESede
tool.transformation=PBEWithSHA1AndDESede/CBC/PKCS5Padding
ini.type=CSF

4.7 Managing the Oracle Database

To manage your Oracle database:

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

  2. Review database initialization parameters. Modify initialization parameters as needed. See Section 4.7.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 4.7.2.

  4. Review memory allocation and adjust as needed. See Section 4.7.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 4.7.4.

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

4.7.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 4-5 lists specific initialization parameters that you should set and their recommended values.

Table 4-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.

4.7.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.

4.7.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.

4.7.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.

4.8 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 4-6 describes the types of patching and provides information on where to find related documentation.

Table 4-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 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


4.9 Managing Oracle Fusion Applications-Specific Labels in the Oracle Metadata Repository

The Oracle Metadata Repository (MDS Repository) contains metadata for Oracle Fusion Middleware components. It can also contain metadata about the configuration of Oracle Fusion Middleware and metadata for your applications. For general instructions on managing the metadata for Oracle Fusion Middleware components in the Oracle Metadata Repository, see the "Managing the Metadata Repository" chapter in the Oracle Fusion Middleware Administrator's Guide.

As a part of MDS Repository management, you work with metadata labels. You select a version for the repository to select a particular version of each object from a metadata repository partition. Also, if you take actions that affect the MDS Repository, such as deploying, patching, or doing some customizations, you can potentially put the repository into a broken state. When this happens, you can rollback to a previous label. For example, when you roll back to a label, all objects within that repository move to that state. To manage labels, note the following prefixes for Oracle Fusion Applications in the MDS Repository:

For more information about managing labels, see the "Managing Metadata Labels in the MDS Repository" section in the Oracle Fusion Middleware Administrator's Guide.

4.10 Modifying Oracle Application Development Framework Connections in Oracle Fusion Applications

A connection configuration (connections.xml) contains information that a client application uses to identify the Oracle Application Development Framework (Oracle ADF) application module's deployment scenario. For more information about modifying the configuration of a single application, see the following sections in the Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework:

In an Oracle Fusion Applications environment, you may need to change the internal and external settings for several applications. For example, if there was an outage of the Oracle Fusion Customer Relationship Management (Oracle Fusion CRM) applications due to a lost Oracle HTTP Server host, then you would need update all the applications that depend on the Oracle Fusion CRM-provided web services. If all the applications in an Oracle WebLogic Server domain use the same connections.xml, which is the default behavior after provisioning, you can make this edit in one place using Fusion Applications Control.

To modify the connections for all the applications in an Oracle WebLogic Server domain using Fusion Applications Control:

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

  2. Click the domain.

    The Oracle WebLogic Server Domain home page displays.

  3. From the WebLogic Domain menu, choose ADF Domain Configuration.

    The ADF Common Properties page displays.

  4. In the Property Sets table, click the property set to modify, and in the Details for Property Set table, modify the property values.

    These property sets and properties reside in the adf-domain-config.xml file, and are used in the ELs in the connections.xml file.

  5. Click Save.

4.11 Modifying Oracle Data Integrator Configuration

Oracle Data Integrator (ODI) is installed with the following product families:

The Oracle Fusion applications use Oracle Application Development Framework and Oracle SOA Suite, which in turn use ODI for bulk data movement requirements. This section describes how to modify key aspects of ODI configuration without interrupting the service of the applications.

This section contains the following topics:

4.11.1 Editing the Oracle Data Integrator Topology for Database Endpoint Changes

ODI moves data between two databases. In some cases, a database endpoint changes or the JDBC password changes for security reasons. When these types of changes occur, you must modify the configuration of the database topology.

To modify the database topology:

  1. Log into Oracle Data Integrator Console.

    http://product_familyinternal.domain:port/odiconsole
    

    where product_familyinternal.domain. port is the host and domain of the Oracle HTTP Server or a Load Balancer.

  2. From the Browse pane, expand Topology and then Data Servers.

  3. Select the database server and click the Edit icon (Edit icon).

    The Edit Data Server page displays.

  4. Scroll to the JDBC Details section at the bottom of the page.

  5. Modify the JDBC fields for the endpoint:

    Field Description

    JDBC Driver

    The JDBC driver for the data source connection. The value in this field must conform to the database specifications.

    JDBC URL

    The JDBC URL for the data source connection in the format of jdbc:oracle:thin:@//DB_host_name.domain/sid.

    User

    The Oracle Database schema name (user name) to log into the database.

    JDBC Password

    The password for the user.


  6. Click Save.

4.11.2 Modifying ODI Agent Host and Port Configuration

The ODI agent connects to a master repository and connects to different technologies to move data. If the ODI agent host or port configuration has been modified in Oracle WebLogic Server, then you reflect those changes in ODI.

To modify the configuration of an agent:

  1. Log into Oracle Data Integrator Console.

    http://product_familyinternal.domain:port/odiconsole
    

    where product_familyinternal.domain. port is the host and domain of the Oracle HTTP Server or a Load Balancer.

  2. From the Browse pane, expand Topologies, Agents, and then Physical Agents.

  3. Select an agent click the Edit icon (Edit icon).

    The Edit Physical Agent page displays.

  4. In the Definition section, modify the Host Name and Port Number fields.

  5. Click Save.