| Oracle® Fusion Applications Administrator's Guide 11g Release 1 (11.1.3) Part Number E14496-04 |
|
|
View PDF |
| Oracle® Fusion Applications Administrator's Guide 11g Release 1 (11.1.3) Part Number E14496-04 |
|
|
View PDF |
This chapter describes the common, essential tasks for administering your Oracle Fusion Applications environment.
This chapter contains the following topics:
Running Administration Servers and Managed Servers from Shared and Local Disks
Managing Oracle Fusion Applications-Specific Labels in the Oracle Metadata Repository
Modifying Oracle Application Development Framework Connections in Oracle Fusion Applications
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:
Oracle Fusion Applications Common Implementation Guide for common setup and maintenance tasks for Oracle Fusion applications
Oracle Fusion Applications Post-Installation Guide for configuration tasks to perform after installation
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.
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:
Starting and Stopping Components in the Oracle Fusion Applications Environment
Starting and Stopping the Entire Oracle Fusion Applications Environment
Starting and Stopping the Oracle Fusion Applications Middle Tier Using the fastartstop Utility
Starting and Stopping a Product Family Oracle WebLogic Server Domain
Starting and Stopping an Oracle WebLogic Server Cluster for a Configuration Change
For many of the Oracle Fusion Middleware components, you can start and stop in different ways, depending on your requirements.
Table 3-1 describes the Oracle Fusion Applications, Oracle Fusion Middleware, and Oracle Database components you can start and stop, and provides information on where to find related documentation for each component.
The procedures referenced in the Oracle Fusion Middleware guides describe using Fusion Middleware Control. These procedure also apply to Fusion Applications Control.
Table 3-1 Starting and Stopping
| Component | Description | Documentation |
|---|---|---|
|
Oracle Fusion Applications |
||
|
Oracle Fusion applications |
You can start and stop applications using the WLST command line, Fusion Applications Control, Cloud Control, or WebLogic Server Administration Console. |
Section 3.3.6 for WLST and Fusion Applications Control "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 WLST command line to start an Administration Server or the |
|
|
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 |
|
Managed Server for an application |
Managed Servers host business applications, application components, Web services, and their associated resources. You can use Fusion Applications Control or WebLogic Server Administration Console to start the Managed Servers for a domain, or the |
Section 3.3.2.1, Task 4, "Start the Managed Servers" for Fusion Applications Control and the "Start Managed Servers from the Administration Console", "Start Managed Servers in a cluster" and "Shutdown servers in a cluster" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help for the WebLogic Server Administration Console |
|
Oracle Business Intelligence Suite |
You can use Fusion Applications Control or the |
"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. |
|
|
Oracle HTTP Server |
You can use Fusion Applications Control or the |
"Starting, Stopping, and Restarting Oracle HTTP Server" section in the Oracle Fusion Middleware Administrator's Guide for Oracle HTTP Server |
|
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 a product family, you can stop the Oracle WebLogic Server domain for the product family and restart it after you apply the patch without stopping the entire Oracle Fusion Applications environment. You can use Fusion Applications Control to start and stop an Oracle WebLogic Server domain. |
|
|
Oracle WebLogic Server cluster for a product family |
If you modify the Oracle WebLogic Server configuration, you must stop and restart the cluster for the configuration changes to take effect. You can start and stop Oracle WebLogic Server clusters with either Fusion Applications Control or Node Manager. |
Section 3.3.5.2 for Fusion Applications Control "Using Node Manager to Start Managed Servers in a WebLogic Domain or Cluster" section in Oracle Fusion Middleware Oracle WebLogic Scripting Tool for Node Manager |
|
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 |
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:
To perform a complete start of the Oracle Fusion Applications environment, you must start the Oracle WebLogic Server domain for the Oracle Fusion Setup product family before the domains for the other product families.
Applications may not work correctly until all the Managed Servers in all domains have been started.
The section contains the following topics for performing a complete start of the Oracle Fusion Applications environment:
The fastartstop utility provides an alternative way to starting the Administration Servers and Managed Servers for all the product families in one step. See Section 3.3.3.
To start the Oracle database instance using Oracle Database Control:
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.
In the Database Home page, click Startup.
The Startup/Shutdown Credentials page appears.
Enter credentials as follows:
Enter the host computer credentials of the user who installed Oracle Database, or of any user who is authorized to use SQL*Plus.
Enter the database credentials consisting of the user name SYS and the password that you assigned to SYS during the installation.
From the Connect As list, select SYSOPER.
Click OK.
A confirmation page appears.
Click Yes.
The Startup page appears, indicating that the database is being started up. When startup is complete, the Login page appears.
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.
To start the Oracle Identity Management system components:
Set the ORACLE_HOME environment variable to the Oracle home for the Oracle Identity Management components.
Start Oracle Process Manager and Notification Server (OPMN) and all system components:
opmnctl startall
You must start the Oracle WebLogic Server Administration Server for the CommonDomain domain in the Oracle Fusion Setup product family from a shared disk. The applications and other product families depend on topology information in the Administration Server in the Oracle Fusion Setup product family. For more information about running the Administration Server from a shared location, see Section 3.2.
Optionally, if you need to perform administration tasks for other product families, start the Administration Server for those product families.
When you start the Administration Server, you also start the applications that run on the Administration Server, including the WebLogic Server Administration Console and Fusion Applications Control.
To start an individual Administration Server:
Start the host-specific Node Manager for the domain for which you want to start the Administration Servers:
Set the JAVA_OPTIONS environment variable:
setenv JAVA_OPTIONS "${JAVA_OPTIONS} -Dserver.group=AdminServer"
Set the WLST_PROPERTIES environment variable:
setenv WLST_PROPERTIES "-Dweblogic.security.SSL.trustedCAKeyStore=WL_HOME/server/lib/fusion_trust.jks"
where WL_HOME is the Oracle WebLogic Server home directory under the fusionapps Middleware subdirectory.
Start Node Manager with the startNodeManagerWrapper utility from the Oracle WebLogic Server home directory under the fusionapps Middleware subdirectory:
(UNIX) WL_HOME/common/nodemanager/host_name/startNodeManagerWrapper.sh (Windows) WL_HOME\common\nodemanager\host_name\startNodeManagerWrapper.cmd
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 Administrator's Guide.
Note:
Do not start Node Manager with WLST or the following Oracle WebLogic Server scripts:
(UNIX) WL_HOME/server/bin/startNodeManager.sh (Windows) WL_HOME\server\bin\startNodeManager.cmd
Start the Administration Server:
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.
Run the wlst script:
(UNIX) wlst.sh (Windows) wlst.cmd
Connect to Oracle WebLogic Server with the following WLST command:
nmConnect('node_manager_user_name','node_manager_password',
'node_manager_host_name','node_manager_host_port', 'domain_name',
'path_to_domain_home_of_the_domain')
The following shows an example of a connection to the CommonDomain domain:
nmConnect('bootstrap_admin','welcome','weblogic1.company.com','5556',
'CommonDomain','/oracle/fusion/top/instance/domains/weblogic1.company.com/CommonDomain')
See the "nmConnect" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
Start the Administration Server:
nmStart('WLS_server_name')
For example a connection to the CommonDomain domain might be:
nmStart('AdminServer')
See the "nmStart" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
To start all the Administration Servers for all the product families:
Start the host-specific Node Managers for all of the product family domains:
Each host has its own copy of the Node Manager and all the Node Managers should be running before attempting to start any Administration or Managed Servers.
Set the JAVA_OPTIONS environment variable:
setenv JAVA_OPTIONS "${JAVA_OPTIONS} -Dserver.group=AdminServer"
Set the WLST_PROPERTIES environment variable:
setenv WLST_PROPERTIES "-Dweblogic.security.SSL.trustedCAKeyStore=WL_HOME/server/lib/fusion_trust.jks"
where WL_HOME is the Oracle WebLogic Server domain home directory under the fusionapps Middleware subdirectory.
Start Node Manager with the startNodeManagerWrapper utility from the Oracle WebLogic Server home directory under the fusionapps Middleware subdirectory:
(UNIX) WL_HOME/common/nodemanager/host_name/startNodeManagerWrapper.sh (Windows) WL_HOME\common\nodemanager\host_name\startNodeManagerWrapper.cmd
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 Administrator's Guide.
Note:
Do not start Node Manager with WLST or the following Oracle WebLogic Server scripts:
(UNIX) WL_HOME/server/bin/startNodeManager.sh (Windows) WL_HOME\server\bin\startNodeManager.cmd
Start the Administration Servers for all the product families:
If the Oracle Fusion Applications patching framework was installed, the fastartstop utility is available from the following directories:
(UNIX) FA_ORACLE_HOME/applications/lcm/ad/bin (Windows) FA_ORACLE_HOME\applications\lcm\ad\bin
FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.
From the shared host location, run fastartstop to start all the domains or specific domains:
(UNIX) fastartstop.sh -Start -all -username user_name -appbase APPLLICATIONS_BASE -adminServersOnly [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period] (Windows) fastartstop.cmd -Start -all -username user_name -appbase APPLLICATIONS_BASE -adminServersOnly [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period]
For more information about the syntax, see Table 3-2. For more information about starting the Administration Servers and Managed Servers for all the product families is the fastartstop utility. See Section 3.3.3.
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
Depending on the configuration established during provisioning, you can start Oracle WebLogic Server Managed Servers from either a shared or local disk. See Section 3.2.
To start the Managed Servers for a domain using Fusion Applications Control:
From the navigation pane, expand the farm, WebLogic Domain.
From the WebLogic Domain menu, choose Control, then Start Up.
If you prefer to use the WebLogic Server Administration Console, "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
To start all the Administration Servers and Managed Servers for all the product families in one step, use the fastartstop utility. See Section 3.3.3.
Note:
Do not use the following Oracle WebLogic Server scripts to start the Managed Servers:
(UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh (Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd
See "Starting and Stopping Oracle Business Intelligence" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
To start the Oracle HTTP Server using opmnctl:
(UNIX) WT_CONFIG_HOME/bin/opmnctl startproc process-type=OHS (Windows) WT_CONFIG_HOME\bin\opmnctl startproc process-type=OHS
To start Oracle HTTP Server using Fusion Applications Control:
From the navigation pane, expand the farm and then the Web Tier installation type.
Select the Oracle HTTP Server.
From the Oracle HTTP Server menu, choose Control, then Start Up.
You can follow these procedures when you need to completely shut down the Oracle Fusion Applications environment. For example, when preparing to perform a complete backup of your environment, or apply a patch.
The section contains the following topics for performing a complete stop of the Oracle Fusion Applications environment:
The fastartstop utility provides an alternative way to stopping the Administration Servers and Managed Servers for all the product families in one step. See Section 3.3.3.
To stop the Oracle HTTP Server using opmnctl:
(UNIX) WT_CONFIG_HOME/bin/opmnctl stopproc process-type=OHS (Windows) WT_CONFIG_HOME\bin\opmnctl stopproc process-type=OHS
To stop the Oracle HTTP Server using Fusion Applications Control:
From the navigation pane, expand the farm and then the Web Tier installation type.
Select the Oracle HTTP Server.
From the Oracle HTTP Server menu, choose Control, then Shut Down.
See "Starting and Stopping Oracle Business Intelligence" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
To stop the Oracle Identity Management system components:
Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components.
Start OPMN and all system components:
opmnctl stopall
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.
To stop an individual Administration Server:
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.
Run the wlst script:
(UNIX) wlst.sh (Windows) wlst.cmd
Connect to Oracle WebLogic Server with the following WLST command:
nmConnect('node_manager_user_name','node_manager_password',
'node_manager_host_name','node_manager_host_port', 'domain_name',
'path_to_domain_home_of_the_domain')
The following shows an example of a connection to the CommonDomain domain:
nmConnect('bootstrap_admin','welcome','weblogic1.company.com','5556',
'CommonDomain','/oracle/fusion/top/instance/domains/weblogic1.company.com/CommonDomain')
See the "nmConnect" section in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
Stop the Administration Server:
nmStop('WLS_server_name')
For example, to stop the Administration Server:
nmStop('AdminServer')
To stop all the Administration Servers for all the product families:
Stop the Administration Servers for all the product families:
If the Oracle Fusion Applications patching framework was installed, the fastartstop utility is available from the following directories:
(UNIX) FA_ORACLE_HOME/applications/lcm/ad/bin (Windows) FA_ORACLE_HOME\applications\lcm\ad\bin
FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.
From the shared host location, run fastartstop to start all the domains or specific domains:
(UNIX) fastartstop.sh -Stop -all -username user_name -appbase APPLLICATIONS_BASE -adminServersOnly [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period] (Windows) fastartstop.cmd -Stop -all -username user_name -appbase APPLLICATIONS_BASE -adminServersOnly [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period]
For more information about the syntax, see Table 3-2. For more information about stopping the Administration Servers and Managed Servers for all the product families is the fastartstop utility. See Section 3.3.3.
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
Depending on the configuration established during provisioning, you can stop Oracle WebLogic Server Managed Servers from either a shared or local disk. See Section 3.2.
To stop the Managed Servers for a domain using Fusion Applications Control:
From the navigation pane, expand the farm, and then WebLogic Domain.
From the WebLogic Domain menu, choose Control, then Shut Down.
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
To stop all the Administration Servers and Managed Servers for all the product families in one step, use the fastartstop utility. See Section 3.3.3.
Note:
Do not use the following Oracle WebLogic Server scripts to stop the Managed Servers:
(UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh (Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd
To stop the Oracle database instance using Oracle Database Control:
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.
In the Database Home page, click Shutdown.
The Startup/Shutdown Credentials page appears.
Enter credentials as follows:
Enter the host computer credentials of the user who installed Oracle Database, or of any user who is authorized to use SQL*Plus.
Enter the database credentials consisting of the user name SYS and the password that you assigned to SYS during the installation.
From the Connect As list, select SYSOPER.
(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.
Click OK.
A confirmation page appears.
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.
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.
Another alternative to starting and stopping the Oracle Fusion Applications Administration Servers and Managed Servers is the fastartstop utility.
The fastartstop script 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 requires Node Manager to run.
While the utility starts and stops the domains, it does not start and stop Oracle HTTP Server, Oracle Identity Management, and the Oracle Database. Therefore, you must start these components separately.
This section contains the following topics:
Starting an Oracle Fusion Applications Environment with the fastartstop Utility for the Middle Tier
Stopping an Oracle Fusion Applications Environment with the fastartstop Utility
If the Oracle Fusion Applications patching framework was installed, the fastartstop utility is available from the following directories:
(UNIX) FA_ORACLE_HOME/applications/lcm/ad/bin (Windows) FA_ORACLE_HOME\applications\lcm\ad\bin
FA_ORACLE_HOME is a directory named applications, located under the fusionapps Oracle Fusion Applications Middleware home.
(UNIX) fastartstop.sh -Start|-Stop|-Bounce|-StartBIPS|-StopBIPS -all|-domains domain_name, ...domain_nameN|-BIPServerComponents [-clusterType soa] -username user_name -appbase APPLICATIONS_BASE [-adminServersOnly] [-startAdminServer true|false] [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period] [-help] (Windows) fastartstop.cmd -Start|-Stop|-Bounce|-StartBIPS|-StopBIPS -all|-domains domain_name, ...domain_nameN|-BIPServerComponents [-clusterType soa] -username user_name -appbase APPLICATIONS_BASE [-adminServersOnly] [-startAdminServer true|false] [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period] [-help]
The following example shows starting Managed Servers in SOA cluster for the HCMDomain domain and the Administration Server of that domain.
fastartstop.sh -Start -domains HCMDomain -username username
appbase /scratch/aime1/appltop/fusionapps/applications
-clusterType soa -startAdminServer true
Table 3-2 describes the options for the fastartstop script.
Table 3-2 Options for the fastartstop Script
| Options | Description |
|---|---|
|
|
Specify the path for the Oracle Fusion Applications installation. |
|
|
Use to start, stop, or restart the Administration Servers only, leaving Managed Servers untouched. This option is mutually exclusive to the When used with |
|
|
Specify what to start, stop, or bounce:
|
|
|
Specify to start or stop Managed Servers within a cluster. This parameter is currently only supported for Oracle SOA Suite clusters ( |
|
|
Specify to display the syntax. |
|
|
Specify the log level for the
|
|
|
Specify whether to start, stop, or restart:
|
|
|
Specify the location of the (UNIX) FA_ORACLE_HOME/admin (Windows) FA_ORACLE_HOME\admin
|
|
|
Specify This option is mutually exclusive to the |
|
|
Specify the timeout in seconds for the utility to run. |
|
|
Specify the Oracle Fusion Middleware administration user. |
The utility prompts you for the Oracle Fusion Middleware administration user. See Section 4.8.5.2 for more information about changing this password.
The fastartstop utility generates fastartstop.log in the following subdirectories:
(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.
Example 3-1 shows the format of a typical entry in the SetupDetails.xml. It is populated with the CommonDomain domains details. The other domains are not represented, because they are automatically read from the API. The file contains Oracle WebLogic Server domain information, including the Administration Server, the Managed Servers, and Node Manager.
You can reduce the number of steps required to start the Oracle Fusion Applications environment with the fastartstop utility.
The section contains the following topics for starting the Oracle Fusion Applications environment with the fastartstop utility:
To start the Oracle database instance using Oracle Database Control:
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.
In the Database Home page, click Startup.
The Startup/Shutdown Credentials page appears.
Enter credentials as follows:
Enter the host computer credentials of the user who installed Oracle Database, or of any user who is authorized to use SQL*Plus.
Enter the database credentials consisting of the user name SYS and the password that you assigned to SYS during the installation.
From the Connect As list, select SYSOPER.
Click OK.
A confirmation page appears.
Click Yes.
The Startup page appears, indicating that the database is being started up. When startup is complete, the Login page appears.
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.
To start the Oracle Identity Management system components:
Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components.
Start OPMN and all system components:
opmnctl startall
Start Node Manager for each of the hosts for which you want to start the Administration Servers:
Set the JAVA_OPTIONS environment variable:
setenv JAVA_OPTIONS "${JAVA_OPTIONS} -Dserver.group=AdminServer"
Set the WLST_PROPERTIES environment variable:
setenv WLST_PROPERTIES "-Dweblogic.security.SSL.trustedCAKeyStore=WL_HOME/server/lib/fusion_trust.jks"
where WL_HOME is the Oracle WebLogic Server home directory under the fusionapps Middleware subdirectory.
Start Node Manager with the startNodeManagerWrapper utility from the Oracle WebLogic Server home directory under the fusionapps Middleware subdirectory:
(UNIX) WL_HOME/nodemanager/host_name/startNodeManagerWrapper.sh (Windows) WL_HOME\nodemanager\host_name\startNodeManagerWrapper.cmd
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 Administrator's Guide.
From the shared host location, run fastartstop to start all the domains or specific domains:
(UNIX) fastartstop.sh -Start -all|-domains domain_name, ...domain_nameN [-clusterType soa] -username user_name -appbase APPLLICATIONS_BASE [-startAdminServer true] [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period] (Windows) fastartstop.cmd -Start -all|-domains domain_name, ...domain_nameN [-clusterType soa] -username user_name -appbase APPLLICATIONS_BASE [-startAdminServer true] [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period]
For more information about the syntax, see Table 3-2.
To start the Oracle HTTP Server using opmnctl:
(UNIX) WT_CONFIG_HOME/bin/opmnctl startproc process-type=OHS (Windows) WT_CONFIG_HOME\bin\opmnctl startproc process-type=OHS
To start Oracle HTTP Server using Fusion Applications Control:
From the navigation pane, expand the farm and then the Web Tier installation type.
Select the Oracle HTTP Server.
From the Oracle HTTP Server menu, choose Control, then Start Up.
You can reduce the number of steps required to stop the Oracle Fusion Applications environment with the fastartstop utility.
The section contains the following topics for stopping the Oracle Fusion Applications environment with the fastartstop utility:
To stop the Oracle HTTP Server using opmnctl:
(UNIX) WT_CONFIG_HOME/bin/opmnctl stopproc process-type=OHS (Windows) WT_CONFIG_HOME\bin\opmnctl stopproc process-type=OHS
To stop the Oracle HTTP Server using Fusion Applications Control:
From the navigation pane, expand the farm and then the Web Tier installation type.
Select the Oracle HTTP Server.
From the Oracle HTTP Server menu, choose Control, then Shut Down.
The fastartstop utility requires the Node Manager be running.
To start Node Manager, use the startNodeManagerWrapper utility from the Oracle WebLogic Server home directory under the fusionapps Middleware subdirectory:
(UNIX) WL_HOME/nodemanager/host_name/startNodeManagerWrapper.sh (Windows) WL_HOME\nodemanager\host_name\startNodeManagerWrapper.cmd
From the shared host location, run fastartstop to stop all the domains or specific domains:
(UNIX) fastartstop.sh -Stop -all|-domains domain_name, ...domain_nameN [-clusterType soa] -username user_name -appbase APPLLICATIONS_BASE [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period] (Windows) fastartstop.cmd -Stop -all|-domains domain_name, ...domain_nameN [-clusterType soa] -username user_name -appbase APPLICATIONS_BASE [-setup setup_details.xml_file_location] [-loglevel log_level] [-timeout timeout_period]
For more information about the syntax, see Table 3-2.
To stop the Oracle Identity Management system components:
Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components.
Stop OPMN and all system components:
opmnctl stopall
To stop the Oracle database instance using Oracle Database Control:
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.
In the Database Home page, click Shutdown.
The Startup/Shutdown Credentials page appears.
Enter credentials as follows:
Enter the host computer credentials of the user who installed Oracle Database, or of any user who is authorized to use SQL*Plus.
Enter the database credentials consisting of the user name SYS and the password that you assigned to SYS during the installation.
From the Connect As list, select SYSOPER.
(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.
Click OK.
A confirmation page appears.
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.
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.
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:
Stopping an Oracle WebLogic Server Domain for a Product Family
Starting 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:
Oracle HTTP Server is typically installed on a computer separate from the product family. By stopping Oracle HTTP Server, you stop requests to the entire Oracle Fusion Applications environment. Stopping Oracle HTTP Server before the product family ensures a cleaner shutdown.
To stop the Oracle HTTP Server using opmnctl:
(UNIX) WT_CONFIG_HOME/bin/opmnctl stopproc process-type=OHS (Windows) WT_CONFIG_HOME\bin\opmnctl stopproc process-type=OHS
To stop Oracle HTTP Server using Fusion Applications Control:
From the navigation pane, expand the farm and then the Web Tier installation type.
Select an Oracle HTTP Server.
From the Oracle HTTP Server menu, choose Control, then Shut Down.
When you stop an Oracle WebLogic Server domain for a product family, you stop all the applications on the cluster of Managed Servers in the domain. For example, the Oracle Enterprise Scheduler ESSAPP application and the SOA Infrastructure soa-infra application stop running.
To stop a product family domain using Fusion Applications Control:
From the navigation pane, expand the farm, then WebLogic Domain.
Select the Oracle WebLogic Server domain.
From the WebLogic Domain menu, choose Control, then Shut Down.
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:
To start the Oracle HTTP Server using opmnctl:
(UNIX) WT_CONFIG_HOME/bin/opmnctl startproc process-type=OHS (Windows) WT_CONFIG_HOME\bin\opmnctl startproc process-type=OHS
To stop Oracle HTTP Server using Fusion Applications Control:
From the navigation pane, expand the farm and then the Web Tier installation type.
Select the Oracle HTTP Server.
From the Oracle HTTP Server menu, choose Control, then Start Up.
When you start an Oracle WebLogic Server domain for a product family, you start the cluster of Managed Servers in the domain and all the applications.
To start a product family domain using Fusion Applications Control:
From the navigation pane, expand the farm, then WebLogic Domain.
Select the Oracle WebLogic Server domain.
From the WebLogic Domain menu, choose Control, then Start Up.
If you modify the Oracle WebLogic Server configuration, you must stop and restart the cluster for the configuration changes to take effect.
This section contains the following topics:
Starting and Stopping an Oracle WebLogic Server Cluster Using WLST and Node Manager
Starting and Stopping an Oracle WebLogic Server Cluster Using Fusion Applications Control
See "Using Node Manager to Start Managed Servers in a WebLogic Domain or Cluster" section in Oracle Fusion Middleware Oracle WebLogic Scripting Tool.
To stop or restart a cluster using Fusion Applications Control:
Modify the Oracle WebLogic Server configuration as required.
From the navigation pane, expand the farm, WebLogic Domain, and then domain name.
Select the Oracle WebLogic Server cluster.
Expand the Oracle WebLogic Server cluster to show each target Managed Server.
From the WebLogic Cluster menu, choose Control, then Shut Down or Start Up.
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.
Applications may not work correctly until all Managed Servers in all domains have been started.
This section contains the following topics:
To start or stop applications with the WebLogic Scripting Tool (WLST):
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.
Run the wlst script:
(UNIX) wlst.sh (Windows) wlst.cmd
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.
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.
To start or stop an application using Fusion Applications Control or Cloud Control:
Navigate to a product family home page:
From Fusion Applications Control, from the navigation pane, select the product family.
From Cloud Control:
From the Targets menu, choose Fusion Applications.
The Fusion Applications target home page displays.
In the table on the Fusion Applications target home page, click the appropriate Product Family target.
From the navigation pane, expand the product family, then Fusion Applications, and then the cluster application.
Select the application instance you want to stop.
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.
To start or stop all the application instances in a cluster using Fusion Applications Control or Cloud Control
Navigate to a product family home page:
From Fusion Applications Control, from the navigation pane, select the product family.
From Cloud Control:
From the Targets menu, choose Fusion Applications.
The Fusion Applications target home page displays.
In the table on the Fusion Applications target home page, click the appropriate Product Family target.
From the navigation pane, expand the product family, then Fusion Applications, and then the cluster application.
From the Fusion Cluster Application menu, choose Control, then Start Up or Shut Down.
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 3-3 lists the port types and provides information on where to find documentation related to changing ports. The procedures referenced in the Oracle Fusion Middleware guides describe using Fusion Middleware Control. These procedure also apply to Fusion Applications Control.
Table 3-3 Changing Ports
| Port Type | Documentation for Changing Ports |
|---|---|
|
Oracle Database |
"Changing the Oracle Database Net Listener" section in the Oracle Fusion Middleware Administrator's Guide |
|
Oracle Business Intelligence Suite |
"Using Fusion Middleware Control to Scale System Components" section in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition |
|
Oracle 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:
|
|
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 |
Before you begin configuration, change the passwords for the various accounts to secure passwords. Table 3-4 describes the accounts and provides information on where to find related documentation for each account. The procedures referenced in the Oracle Fusion Middleware guides describe using Fusion Middleware Control. These procedure also apply to Fusion Applications Control.
Table 3-4 Changing Passwords
| Password Account | Description | Documentation for Changing the Passwords |
|---|---|---|
|
Oracle Fusion Middleware administration for the Oracle WebLogic Server domain |
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. |
|
|
Super User |
The super user has the following privileges:
You can change the credentials using Fusion Applications Control or Oracle Platform Security Services (OPSS) scripts. This user is specified on the Identity and Policy Management page of the Provisioning Wizard during installation. See "Identity and Policy Management Configuration" section in the Oracle Fusion Applications Installation Guide for information about this page. Installation establishes the same username and password for all the domains. |
Section 4.8.5.2 to change the administrative password "Managing the Credential Store" section in the Oracle Fusion Middleware Application Security Guide |
|
Oracle Metadata Repository schema |
Oracle Metadata Services (MDS) repository contains metadata for the Oracle Fusion Applications and some Oracle Fusion Middleware component applications. The schema passwords are stored in the Oracle database. |
"Changing Metadata Repository Schema Passwords" section in the Oracle Fusion Middleware Application Security Guide |
|
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. |
|
|
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 |
|
|
The |
"Default Users and Passwords" section in the Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition |
To manage your Oracle database:
Start the Oracle database instance, if not already started. See Section 3.3.2.
Review database initialization parameters. Modify initialization parameters as needed. See Section 3.6.1.
Review your database storage structures: tablespaces and data files, online redo log files, and control files. Create or modify storage structures as needed. See Section 3.6.2.
Review memory allocation and adjust as needed. See Section 3.6.3.
Review, unlock, and reset passwords for predefined database users as needed. Create new users, and assign privileges and roles to them as needed. See Section 3.6.4.
Create or review the backup strategy for the database and back up the database. See Chapter 15.
Managing an Oracle instance includes configuring parameters that affect the basic operation of the Oracle instance. These parameters are called initialization parameters. The Oracle instance reads initialization parameters from a file at startup.
After being read from a file, initialization parameters are retained in memory, where the values for many of them can be changed dynamically. There are two types of parameter files. The type of file used to start the instance determines if dynamic initialization parameter changes persist across database shutdown and startup. The parameter file types are:
Server parameter file
The server parameter file is a binary file that can be written to and read by the database. It must not be edited manually. It is stored on the host system on which Oracle Database is running. Changes are made when you use Database Control to modify one or more initialization parameters, or when Oracle Database itself makes changes for self-tuning purposes. Any changes to it persist across database shutdown and startup operations.
Text initialization parameter file
A text initialization parameter file is a text file that can be read by the Oracle instance, but it is not written to by the instance. You can change a text initialization parameter file with a text editor, but changes do not take effect until you restart the Oracle instance. When you start the instance with this type of file, you can still change many initialization parameters dynamically with Database Control, but only for the current instance. Unless you also edit the text initialization parameter file and make the same change, the change is lost when you restart the database instance.
As the number of database users increases and the workload increases, you might have to alter some initialization parameters. You can make these changes using the Initialization Parameter page in Oracle Enterprise Manager Database Control, accessible from the Database Configuration section of the Server tab.
Table 3-5 lists specific initialization parameters that you should set and their recommended values.
Table 3-5 Initialization Parameters
| Parameter | Recommended Values |
|---|---|
|
|
Set this parameter to |
|
|
Set this parameter to |
For information about viewing and modifying initialization parameters, see the "Viewing and Modifying Initialization Parameters" section in the Oracle Database 2 Day DBA.
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.
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.
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.
It is necessary to perform various maintenance actions on your applications, their middleware dependencies, and their database components. Maintenance actions include fixing issues that affect the way the applications perform, adding new functionality and features, updating to a higher maintenance level, or providing interoperability to new technology stacks. Patches may be required for maintenance of middleware artifacts, database artifacts, or both. Table 3-6 describes the types of patching and provides information on where to find related documentation.
Table 3-6 Patching
| Type of Patching | Description | Documentation for Patching |
|---|---|---|
|
Oracle Fusion Applications |
The Oracle Fusion Applications Patching Framework provides the tools needed to sup updates to Oracle Fusion Applications software between major or patch set releases. These tools manage the processes for applying individual patches, patch sets, and release update packs. |
|
|
Oracle Fusion 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 |
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 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:
postDeployLabel_ for labels created by MDS Repository at deployment time
Creation_ for labels created by Oracle Fusion Middleware Extensions for Applications (Applications Core) in the MDS Repository
PreMerge_ for labels created by Applications Core in the MDS Repository during sandbox creation.
composer_PostMerge_ for labels created by Applications Core in the MDS Repository during a sandbox publish operation
mds_ for labels created during a Flexfield changes applied during a patch
soa_ for labels created during SOA deployments
composer_ for labels created by Oracle Composer when using the Save and Label button. For more information about Save and Label button, see "Create Labels On Saving Application Customizations" in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter Portal.
For more information about managing labels, see the "Managing Metadata Labels in the MDS Repository" section in the Oracle Fusion Middleware Administrator's Guide.
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 (CRM) applications due to a lost Oracle HTTP Server host, then you would need update all the applications that depend on the 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:
From the navigation pane, expand the farm and then WebLogic Domain.
Click the domain.
The Oracle WebLogic Server Domain home page displays.
From the WebLogic Domain menu, choose ADF Domain Configuration.
The ADF Common Properties page displays.
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.
Click Save.
|
 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|