The following topics are discussed:
For more information about the Oracle Fusion Applications environment topology, directory structures, and runtime processes, see Understand What the Oracle Fusion Applications Environment Looks Like in Oracle Fusion Applications Installation Guide.
End users access Oracle Fusion Applications through a set of URLs defined during the provisioning process (the provisioning wizard calls them external URLs). Depending on whether the topology includes a load balancer or reverse proxy, Oracle Fusion Applications URL endpoints may be at the load balancer or reverse proxy, or directly at the Oracle HTTP Server.
The main end user entry point to Oracle Fusion Applications is generally a URL similar to the following:
https://fusionapps-common.mycompany.com/homePage
Each product family may have its own host name or port, depending on the web tier and load balancer configuration in the provisioning wizard.
Administrators can access the administration consoles through a set of internal or administrative URLs defined in the provisioning wizard. Administrators can use Oracle Enterprise Manager Fusion Applications Control and Oracle Enterprise Manager Cloud Control Console to manage the Oracle Fusion Applications environment.
As with all URLs in Oracle Fusion Applications, access is subject to authentication through Oracle Access Manager.
Starting and stopping the Oracle Fusion Applications environment and its components, 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 is needed to start and stop an individual component or the entire environment, there are several supported scenarios for performing these operations correctly.
It is recommended to start and stop using the fastartstop
utility, particularly when starting or stopping an entire Oracle Fusion Applications environment. Since some components in the environment are dependent on one another, it is crucial to start and stop Oracle Fusion Applications sequentially, in the following order:
Oracle Database
Oracle Identity Management Suite
Node Manager
Oracle Fusion Applications components on the provisioned environment
Important: Due to the dependencies built into the Oracle Fusion Applications environment, it is generally recommended to use the fastartstop
utility instead of Cloud Control to start and stop. While it is possible to start and stop servers and clusters using Cloud Control interface buttons, it is safest to limit using such buttons to starting/stopping a single managed server, such as a SOA server, if desired.
To perform a complete start of the Oracle Fusion Applications environment, start the Oracle WebLogic Server domain for the Oracle Fusion Setup product family before starting the domains for other product families.
Applications may not work correctly until all the Managed Servers in all domains have been started.
The following sections describe steps for performing a complete start of the Oracle Fusion Applications environment.
Before you can start the Oracle Database, Fusion Applications Database must be discovered in EM to be able to start it in EM.
To start the Oracle database instance using Oracle Enterprise Manager Cloud Control Console:
In the Cloud Control Console, go to Targets and then, Databases.
Select a database instance.
The summary page for that instance appears.
Go to Oracle Database, select Control, and then select, Startup/Shutdown.
The credentials page appears.
Enter the appropriate credentials:
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 assigned to SYS
during the installation.
From the Connect As list, select SYSDBA.
Click OK.
A confirmation page appears.
Click Yes.
A message indicating that the database is being started displays. When startup is complete, the instance's summary page appears.
For information about shutting down and starting up the Oracle database instance, see section Shutting Down and Starting Up the Oracle Instance in the Oracle Database 2 Day DBA.
Provisioning created the startall.sh
script which is used to start all of the Oracle Identity Management components on a particular server.
Before invoking the following script, set JAVA_HOME
to JDK_HOME
.
JDK_HOME
can be found at:
LDAPHOST - $IDMTOP/products/dir/jdk
IDMHOST - $IDMTOP/products/app/jdk
WEBHOST - $IDMTOP/products/ohs/jdk
From UNIX, invoke the startall.sh
script. If starting the services on a single host is required, execute the command on that host.
Enter the Oracle WebLogic Server and Node Manager administrator passwords when prompted.
startall.sh This script will prompt for passwords for nodemanager admin and weblogic admin. To avoid the prompt, passwords can also be passed command line: ./startall.sh <nm password> <weblogic password>
LDAPHOST1
LDAPHOST2
IDMHOST1
IDMHOST2
WEBHOST1
WEBHOST2
The script starts the servers in the following order:
LDAPHOST1: oid1
LDAPHOST2: oid2
IDMHOST1: nodemanager1, adminserver, wls_ods1, wls_oam1
IDMHOST2: nodemanager2, wls_ods2, wls_oam2
WEBHOST1: ohs1
WEBHOST2: ohs2
Each host has its own copy of Node Manager and all 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 the Administration Servers will be started:
For more information, see the Node Manager Commands topic in the WLS Command and Variable Reference section in the WLST Command Reference for WebLogic Server.
The steps below will start the Administration Servers, Managed Servers, Oracle HTTP Server, and Oracle Business Intelligence on the provisioned environment using the fastartstop
utility.
For more fastartstop options, see Special Uses of the fastartstop Utility and Understand the fastartstop Utility and its Syntax.
Follow these procedures when the Oracle Fusion Applications environment needs to be completely shut down. For example, when preparing to perform a complete backup of the environment, or apply a patch.
To stop the Administration Servers, Managed Servers, Oracle HTTP Server, and Oracle Business Intelligence on the provisioned environment using the fastartstop
utility:
Before invoking this script, set JAVA_HOME
to JAVA_HOME
.
Run the stopall
script to stop all Oracle Identity Management servers.
UNIX:
stopall.sh
During execution it will be necessary to enter the Oracle WebLogic Server and Node Manager administrator passwords.
To stop the Oracle database instance using Oracle Enterprise Manager Cloud Control Console:
In the Cloud Control Console, click Targets, and then select Databases.
Select a database instance.
The summary page for that instance appears.
Go to Oracle Database then, Control , and then Startup/Shutdown.
The credentials page appears.
Enter the appropriate credentials:
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 SYSDBA.
Click OK.
A confirmation page appears.
Click Yes.
A message indicating that the database is being stopped displays. When the process is complete, the instance's summary page appears.
The fastartstop
utility is also used to start or stop the following:
Administration Servers and Managed Servers
Oracle HTTP Server
Oracle Business Intelligence
Product family domains
Oracle WebLogic Server clusters in a product family
Oracle WebLogic Server clusters in a product family for a configuration change
When an Administration Server is started, the applications that run on the Administration Server, including the WebLogic Server Administration Console and Fusion Applications Control, are also started.
To start the Administration Servers and Managed Servers:
Do not use the following Oracle WebLogic Server scripts to start the Administration Servers:
(UNIX) DOMAIN_HOME/bin/startWebLogic.sh
When the Administration Server is stopped, the applications that run on the Administration Server, including the WebLogic Server Administration Console and Fusion Applications Control, are also stopped.
To stop the Administration Servers and Managed Servers:
Do not use the following Oracle WebLogic Server scripts to stop the Administration Servers:
UNIX:
DOMAIN_HOME/bin/stopWebLogic.sh
To start Oracle HTTP Server:
fastartstop
OPMN of the OHS instance must be running for fastartstop
to start the OHS component.
At an operating system command prompt, navigate to the location of the fastartstop
script:
UNIX:
FA_ORACLE_HOME/lcm/ad/bin
FA_ORACLE_HOME
is a directory named applications
and located under the fusionapps
directory of Oracle Fusion Applications Middleware home.
From the shared host location, run the fastartstop
utility with -componentType
option:
fastartstop.sh/fastartstop.cmd -Start -componentType OHS -fa_oracle_home /APPTOP/fusionapps/applications/ -fa_oracle_home FA_ORACLE_HOME [-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 2-1.
opmnctl
UNIX:
WT_CONFIG_HOME/bin/opmnctl startproc process-type=OHS
Fusion Applications Control:
From the navigation pane, expand the farm and the Web Tier installation type.
Select the Oracle HTTP Server.
From the Oracle HTTP Server menu, choose Control, and then Start Up.
To stop Oracle HTTP Server:
fastartstop
At an operating system command prompt, navigate to the location of the fastartstop
script:
UNIX:
FA_ORACLE_HOME/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 the fastartstop
utility with -componentType
option:
fastartstop.sh/fastartstop.cmd -Stop -componentType OHS -fa_oracle_home FA_ORACLE_HOME [-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 2-1.
opmnctl
UNIX:
WT_CONFIG_HOME/bin/opmnctl stopproc process-type=OHS
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, and then Shut Down.
To start Oracle Business Intelligence:
fastartstop
At an operating system command prompt, navigate to the location of the fastartstop
script:
UNIX:
FA_ORACLE_HOME/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 the fastartstop
utility with the -componentType BI
option:
fastartstop.sh/fastartstop.cmd -componentType BI -fa_oracle_home FA_ORACLE_HOME [-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 2-1.
Other tools
See Starting and Stopping Oracle Business Intelligence in the System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
To stop Oracle Business Intelligence:
fastartstop
At an operating system command prompt, navigate to the location of the fastartstop
script:
UNIX:
FA_ORACLE_HOME/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 the fastartstop
utility with the -componentType BI
option:
fastartstop.sh/fastartstop.cmd -componentType BI -fa_oracle_home FA_ORACLE_HOME [-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 2-1.
Other tools
See Starting and Stopping Oracle Business Intelligence in the System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
When applying a patch that only applies to a product family, first stop the Oracle WebLogic Server domain for the product family. Restart the domain after applying the patch.
When an Oracle WebLogic Server domain is stopped for a product family , all the applications on the cluster of Managed Servers in the domain are stopped. 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 -fa_oracle_home FA_ORACLE_HOME [-loglevel log_level] [-timeout timeout_period]
For more information about the fastartstop
syntax, see Table 2-1.
To stop a product family domain using Fusion Applications Control:
An Oracle WebLogic Server domain must be started for a product family after applying a patch. The environment may require a restart of a domain for reasons other than a patch.
When an Oracle WebLogic Server domain is started for a product family, the cluster of Managed Servers in the domain and all the applications are started.
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 -fa_oracle_home FA_ORACLE_HOME [-loglevel log_level] [-timeout timeout_period]
For more information about the fastartstop
syntax, see Table 2-1.
To start a product family domain using Fusion Applications Control:
If the Oracle WebLogic Server configuration is modified, it is necessary to 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.
The fastartstop
script is installed with the Oracle Fusion Applications patching framework. After provisioning, 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. Use this utility to start all the domains or a selected 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 Suite and the Oracle Database. Therefore, these components must be started separately.
If the Oracle Fusion Applications patching framework is installed, the fastartstop
utility is available from the following directories:
UNIX:
FA_ORACLE_HOME/lcm/ad/bin
FA_ORACLE_HOME
is the Oracle Fusion Applications home located at:
UNIX:
APPLICATIONS_BASE/fusionapps/applications
The fastartstop
utility supports the following syntax:
UNIX:
fastartstop -Start|-Stop|-Bounce|-StartBIPS|-StopBIPS -all |-domains domain_name,domain_nameN,domain_nameN |-domains "domain_name(server:all,server:managed_server_ name|AdminServer)","domain_name(server:all,server:managed_server_name |AdminServer)" |-componentType <OHS or BI or GOP or OSN> |-componentDomain <component's domain name>|-iasInstance instance_id|-iasComponent component_id|-processType component_type |BIPServerComponents <valid with StartBIPS and StopBIPS options> <deprecated, use -componentType instead> -username <username> -fa_oracle_home <FA OracleHome> [-clusters Cluster_Name1,Cluster_Name2,Cluster_NameN] [-adminServersOnly|-startAdminServer <true or false>, default is false] [-includeServers <ENABLED or DISABLED or ALL>, default is ALL] [-loglevel <log level>] [-timeout <timeout period for server in seconds>] [-mode <mode value>] [-runId <an identifier to uniquely identify the run>] [-version] [--help]
Sample command is as follows:
fastartstop.sh -Start -all -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -clusters ESSCluster,UCMCluster
The following table describes the options for the fastartstop
script.
Table 2-1 Options for the fastartstop Script
Options | Description |
---|---|
|
Specify the operation to execute:
|
|
Specify what to start, stop, or restart:
|
|
Specify the WebLogic cluster name. The
|
|
Specify a user with Oracle Fusion Middleware administration user privileges. |
|
Specify the complete directory path to the Oracle Fusion Applications Oracle home. This directory is located at:
(UNIX) APPLICATIONS_BASE/fusionapps/applications
|
|
Use to start, stop, or restart the Administration Servers only, leaving the Managed Servers untouched. This option is mutually exclusive to the following options:
Do not include the When used with |
|
Specify This option is mutually exclusive to the following options:
Do not include the |
|
Specify to display the syntax. |
|
Specify the log level for the
|
|
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 Severs or Managed Severs 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 the user provides a value less than 12 minutes, then guard value will be used instead. |
|
Specify the mode value with which the (UNIX) <FA INSTANCE>/lcm/admin/FAStartStop The mode values supported by default are:
By default, the following files will be available at the directory specified above:
|
The fastartstop
utility requests a password for the user with Oracle Fusion Middleware administrator privileges specified by the -username
argument. If this argument is passed to the fastarstop
utility on the standard input, the utility will not prompt.
The fastartstop
utility generates fastartstop.log
in the following subdirectories:
(UNIX) APPLTOP/instance/lcm/logs/11.1.7.0.0/RUP/StartStop
FA_ORACLE_HOME
is the Oracle Fusion Applications home located at:
(UNIX) APPLICATIONS_BASE/fusionapps/applications
The following example shows starting the Administration Server and all the Managed Servers in the SCMDomain
domain.
Example 2-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 -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows starting the Administration Server and the soa_server1
Managed Server in the SCMDomain
domain.
Example 2-2 Syntax to Start the Administration Server and Another Managed Server in a Single Domain
./fastartstop.sh -Start -domains "SCMDomain(server:AdminServer,server:soa_server1)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows starting Managed Servers soa_server1
and AdvancedPlanningServer_1
in the SCMDomain
domain.
Example 2-3 Syntax to Start Multiple Managed Servers in a Single Domain
./fastartstop.sh -Start -domains "SCMDomain(server:soa_server1,server:AdvancedPlanningServer_1)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows starting Managed Servers soa_server1
and AdvancedPlanningServer_1
in the SCMDomain
domain and soa_server
from the HCMDomain
domain.
Example 2-4 Syntax to Start Multiple Managed Servers in Multiple Domains
./fastartstop.sh -Start -domains "SCMDomain(server:soa_server1,server:AdvancedPlanningServer_1),HCMDomain(server:soa_server)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows starting all the Managed Servers and the Administration Server in the HCMDomain
domain.
Example 2-5 Syntax to Start the Managed Servers and Administration Server in the SOA Cluster of a Single Domain
fastartstop.sh -Start -all -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -clusters ESSCluster,UCMCluster
The following example shows starting the CommonDomain
domain. Starting a domain includes starting its Administration Server followed by the Managed Servers. When 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 the previous example. This command does not start OPMN-based components Oracle Business Intelligence and Oracle HTTP Server.
Example 2-6 Syntax to Start a Specific Domain
./fastartstop.sh -Start -domains CommonDomain -username FUSION_APPS_PROV_PATCH_APPID -fa_oracle_home /slot/ems7770/oracle/apphome/fusionapps/applications
The following example shows starting all the domains. Starting a domain includes starting its Administration Server followed by the Managed Servers. When 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 the next example. The -all
option also starts OPMN-based components Oracle Business Intelligence and Oracle HTTP Server.
Example 2-7 Syntax to Start All Domains
./fastartstop.sh -Start -all -username FUSION_APPS_PROV_PATCH_APPID -fa_oracle_home /slot/ems7770/oracle/apphome/fusionapps/applications
The following example shows starting multiple domains. Starting domains starts all the Managed Servers and Administration Server for each product family domain.
Example 2-8 Syntax to Start Multiple Domains
./fastartstop.sh -Start -domains HCMDomain,BIDomain,ProjectsDomain -username FUSION_APPS_PROV_PATCH_APPID -fa_oracle_home /scratch/aime/V1HCM/APPTOP/fusionapps/applications -startAdminServer true -clusters soa
The following example shows stopping the Administration Server and all the Managed Servers in the SCMDomain
domain.
Example 2-9 Syntax to Stop the Administration Server and All Managed Servers in a Single Domain
./fastartstop.sh -Stop -domains "SCMDomain(server:all)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows stopping Managed Servers soa_server1
and AdvancedPlanningServer_1
in the SCMDomain
domain.
Example 2-10 Syntax to Stop Multiple Managed Servers in a Single Domain
./fastartstop.sh - Stop -domains "SCMDomain(server:soa_server1,server:AdvancedPlanningServer_1)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows stopping Managed Servers soa_server1
and AdvancedPlanningServer_1
in the SCMDomain
domain and soa_server
in the HCMDomain
domain.
Example 2-11 Syntax to Stop Multiple Managed Servers in Multiple Domains
./fastartstop.sh - Stop -domains "SCMDomain(server:soa_server1,server:AdvancedPlanningServer_1),HCMDomain(server:soa_server)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows stopping the CommonDomain
domain. Stopping a domain stops its Managed Servers and Administration Server.
Example 2-12 Syntax to Stop a Specific Domain
./fastartstop.sh -Stop -domains CommonDomain -username FUSION_APPS_PROV_PATCH_APPID -fa_oracle_home /slot/ems7770/oracle/apphome/fusionapps/applications
The following example 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 2-13 Syntax to Stop All Domains
./fastartstop.sh -Stop -all -username FUSION_APPS_PROV_PATCH_APPID -fa_oracle_home /slot/ems7770/oracle/apphome/fusionapps/applications
The following example shows stopping multiple domains. Stopping domains stops all the Managed Servers and Administration Server for each product family domain.
Example 2-14 Syntax to Stop Multiple Domains
./fastartstop.sh -Stop -domains HCMDomain,BIDomain,ProjectsDomain -username FUSION_APPS_PROV_PATCH_APPID -fa_oracle_home /scratch/aime/V1HCM/APPTOP/fusionapps/applications -startAdminServer true -clusters soa
The following examples show restarting the Administration Server and all the Managed Servers in the SCMDomain
domain.
Example 2-15 Syntax to Bounce the Administration Server and All Managed Servers in a Single Domain
./fastartstop.sh -Bounce -domains "SCMDomain(server:all)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows restarting Managed Servers soa_server1
and AdvancedPlanningServer_1
in the SCMDomain
domain.
Example 2-16 Syntax to Bounce Multiple Managed Servers in a Single Domain
./fastartstop.sh - Bounce -domains "SCMDomain(server:soa_server1,server:AdvancedPlanningServer_1)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows restarting Managed Servers soa_server1
and AdvancedPlanningServer_1
in the SCMDomain
domain and soa_server
in the HCMDomain
domain.
Example 2-17 Syntax to Bounce Multiple Managed Servers in Multiple Domains
./fastartstop.sh - Bounce -domains "SCMDomain(server:soa_server1,server:AdvancedPlanningServer_1),HCMDomain(server:soa_server)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER
The following example shows restarting the CommonDomain
domain. Restarting a domain restarts the Managed Servers and Administration Server in the domain.
Example 2-18 Syntax to Bounce a Specific Domain
./fastartstop.sh -Bounce -domains CommonDomain -username FUSION_APPS_PROV_PATCH_APPID -fa_oracle_home /slot/ems7770/oracle/apphome/fusionapps/applications
The following are additional examples of fastartstop
syntax.
Using the adminServersOnly option:
Example 2-19 Syntax to Restart all the Administration Servers
./fastartstop.sh -Bounce -all -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -adminServersOnly
Using combination commands:
If the server
suboption is set to all and another Managed Server or Administration Server with the -domain
option, all
will take precedence and the start, stop, or restart operation will occur on all servers.
Example 2-20 Syntax with Contradicting server Suboption Settings
./fastartstop.sh -Bounce -domains "SCMDomain(server:all,server:soa_server1)" -username FAAdmin -fa_oracle_home /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. The following example 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 2-21 Syntax with server Suboption Settings Not Consistently Used
./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all),HCMDomain" -username FAAdmin -fa_oracle_home /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
-clusters
-adminServersOnly
The following example shows incorrect combinations of these commands. If these examples are entered, you would see error messages.
Example 2-22 Sample Syntax with Contradicting server Suboption Settings
./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -clusters SOA ./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -startAdminServer true ./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all)" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -adminServersOnly ./fastartstop.sh -Start|Stop|Bounce -domains "SCMDomain(server:all),HCMDomain" -username FAAdmin -fa_oracle_home /scratch/aime/work/APPTOP/fusionapps/applications -loglevel FINER -adminServersOnly