Skip Headers
Oracle® Communications Order and Service Management System Administrator's Guide
Release 7.2.2

E35414-02
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Starting and Stopping OSM

This chapter describes how to start and stop the Oracle Communications Order and Service Management (OSM) product.

About Starting and Stopping OSM

Because OSM resides on Oracle WebLogic servers, starting or stopping the appropriate WebLogic server also starts or stops OSM.

Note:

If your OSM environment is in a WebLogic Server cluster, consult the Oracle WebLogic Server documentation for information about how to start and stop the necessary servers. If all of the servers in the cluster start properly, it means that OSM has started properly.

Starting the OSM Server

To start the OSM Server:

  1. Change to the domain_home directory. This is the base directory for the WebLogic domain into which OSM was deployed.

  2. Run the following command:

    nohup ./startWebLogic.sh &
    

    This starts the WebLogic server in the background and so that it will not stop if you close the terminal window.

Verifying that OSM Has Started

To verify that the OSM application has finished starting, you can use either the following method or the method described in "Using the WebLogic Console to Determine the Status of the OSM Application".

  1. From the directory where you started OSM, run the following command:

    tail -f nohup.out
    

    Wait until the following text is displayed. It indicates that server startup is complete.

    <Server started in RUNNING mode>
    
  2. Use Ctrl + c to halt the tail command and return to the command prompt.

Stopping OSM

To stop OSM:

  1. Change to the domain_home/bin directory.

  2. Run the following command:

    ./stopWebLogic.sh
    

Note:

The procedure above stops OSM by stopping the Administration server for the WebLogic Server. If the WebLogic Server does not shut down completely, you will not be able to start it again due to a port conflict. If the procedure above has completed, but some WebLogic Server processes are still running for the domain, you can use the kill command to stop them. See "Verifying that OSM Has Stopped" for information about verifying whether OSM and WebLogic have stopped completely.

Verifying that OSM Has Stopped

To verify that OSM has stopped, do any of the following: