Create boot.properties:
Create a
"boot.properties" file for each of the servers, so we don't need to
manually enter credentials on startup/shutdown. This only has to be done once.
# AdminServer
echo "username=weblogic" >
$DOMAIN_HOME/servers/AdminServer/security/boot.properties
echo "password=Admin123" >> $DOMAIN_HOME/servers/AdminServer/security/boot.properties
# bi_server1
cp
$DOMAIN_HOME/servers/AdminServer/security/boot.properties
$DOMAIN_HOME/servers/bi_server1/security/boot.properties
Linux Command Terminal |
$ nohup $DOMAIN_HOME/bin/startWebLogic.sh & |
After issueing the
start command we tail the log until we see the message below, indicating that
the server has started successfully.
<WebLogicServer> <BEA-000360> <Server started in RUNNING
mode>
Step 2 of 4: Start NodeManager
There should be a
single Node Manager for the machine. Start it up with the
command below.
Linux Command Line |
$ nohup $MW_HOME/wlserver_10.3/server/bin/startNodeManager.sh
> NOD.out & |
After issuing the
start command we tail the log until we see the message below, indicating that
the server has started successfully.
<Info> <Secure socket listener started on port ####>
Step 3 of 4: Start ManagedWeblogicServer
By default there
should be one managed server, bi_server1 that we will start up. At this
point you should start any other Managed Servers in this Weblogic
domain.
Linux Command Line |
$ nohup $DOMAIN_HOME/bin/startManagedWebLogic.sh bi_server1 & |
After issueing the
start command we tail the log until we see the message below, indicating that
the server has started successfully.
Server started in RUNNING mode
Step 4 of 4: Startup OPMN Components
Oracle Process Manager
should be used to shutdown all system components.
Linux Command Line |
$ nohup $MW_HOME/instances/instance1/bin/opmnctl startall |
Stopping OBIEE 11g services:
It
is exactly in the opposite process of the starting the services. Follow below
steps:
Step 1 of 4: Stop all the OPMN Components
Oracle Process Manager
should be used to shutdown all system components.
Linux Command Line |
$ $MW_HOME/instances/instance1/bin/opmnctl stopall |
Step 2 of 4: Shutdown Managed Server
By default there
should be one managed server, bi_server1 that we will shut down. At the
point you should shut down any other Managed Servers in this WebLogic domain.
Linux Command Line |
$DOMAIN_HOME/bin/stopManagedWebLogic.sh bi_server1 |
Verify that the
Managed Server has shut down completely with the following commands
$ ps -ef | grep
bi_server1.
Step 3 of 4: Shutdown Node Manager
There should be a
single Node Manager for the machine. Shut it down with the command below.
Linux Command Line |
$ $MW_HOME/wlserver_10.3/server/bin/stopNodeManager.sh # Find the process of nodemanager with the below command and kill it $ ps -ef | grep Node | grep nodemanager | grep -v grep | cut
-c10-15 |
Step 4 of 4: Shutdown Admin Server
There should be a
single Node Manager for the machine. Shut it down with the command below.
Linux Command Line |
$ $DOMAIN_HOME/bin/stopWebLogic.sh |
Verify that the Managed Server has shutdown completely with ps -ef | grep AdminServer.
Cheers!
Bose
No comments:
Post a Comment