4. Startup & Shutdown Procedures

Start Sequence

• FADB Start the Fusion Applications transaction database.

• FAIDM Start the Oracle Identity Management environment.

• FUSION Start Node Manager.

• FUSION Start the Administration Servers in all the domains.

• FUSION Start the Managed Servers.

• FUSION Start the Oracle Business Intelligence components.

• FUSION Start the Oracle HTTP Server

Stop Sequence

• FUSION Stop the Managed Servers.

• FUSION Stop the Oracle HTTP Server.

• FUSION Stop the Oracle Business Intelligence components.

• FUSION Stop the Administration Servers.

• FUSION Stop the Managed Servers.

• FAIDM Stop the Oracle Identity Management Environment.

• FADB Stop the Oracle Database.

IDM

• After provisioning, a set of standard control scripts is created and it can be used to start/stop the envrionment in one action.

xxxxxxxxxx
su - oracle
cd /oracle/idm/config/scripts
./startall.sh Welcome1 Welcome1
or
./stopall.sh Welcome1 Welcome1

• The 1st argument is the Node Manager password, and 2nd argument is the Weblogic admin password.

FUSION

• For the Fusion App Server environment, all the actions can be scripted, but I personally prefered to start/stop the managed servers manually. one domain at a time. If all managed servers are started at the same time, the CPU resource is bounded and it could cause some actions become time-out and not response properly.

Startup

xxxxxxxxxx
su - oracle
cd /oracle/fusion/instance/nodemanager/`hostname`
rm *.lck
nohup ./startNodeManagerWrapper.sh > /dev/null &

cd /oracle/fusion/instance/domains/`hostname`/CommonDomain/bin
nohup ./startWebLogic.sh < /dev/null &> /dev/null &

cd /oracle/fusion/instance/domains/`hostname`/FinancialDomain/bin
nohup ./startWebLogic.sh < /dev/null &> /dev/null &

cd /oracle/fusion/instance/domains/`hostname`/CRMDomain/bin
nohup ./startWebLogic.sh < /dev/null &> /dev/null &

cd /oracle/fusion/instance/domains/`hostname`/HCMDomain/bin
nohup ./startWebLogic.sh < /dev/null &> /dev/null &

cd /oracle/fusion/instance/domains/`hostname`/BIDomain/bin
nohup ./startWebLogic.sh < /dev/null &> /dev/null &

cd /oracle/fusion/instance/BIInstance/bin
./opmnctl startall

cd /oracle/fusion/instance/CommonDomain_webtier/bin
./opmnctl startall

• After all Weblogic admin servers and Enterprise Managers are up, you need to log on to each Weblogic server domain, and manually start all Managed Servers in one pass.

Stutdown

• First, manually stop all Managed Servers in each domain. Then you can shutdown the Weblogic admin server, Enterprise Manager, and then the Node Manager.

xxxxxxxxxx
cd /oracle/fusion/instance/CommonDomain_webtier/bin
./opmnctl stopall

cd /oracle/fusion/instance/BIInstance/bin
./opmnctl stopall

cd /oracle/fusion/instance/domains/`hostname`/BIDomain/bin
./stopWebLogic.sh

cd /oracle/fusion/instance/domains/`hostname`/CRMDomain/bin
./stopWebLogic.sh

cd /oracle/fusion/instance/domains/`hostname`/HCMDomain/bin
./stopWebLogic.sh

cd /oracle/fusion/instance/domains/`hostname`/FinancialDomain/bin
./stopWebLogic.sh

cd /oracle/fusion/instance/domains/`hostname`/CommonDomain/bin
./stopWebLogic.sh

kill -9 `ps -ef | grep [N]odeManager | awk '{print $2}'`

| Table of Content | Next |

| Home | Repositories | Blog |

© 2026 by Christopher Ho. All Rights Reserved