Starting and Stopping OSM

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:

Change to the domain_home directory. This is the base directory for the WebLogic domain into which OSM was deployed.
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".

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>
```
Use Ctrl + c to halt the tail command and return to the command prompt.

Stopping OSM

To stop OSM:

Change to the domain_home/bin directory.
Run the following command:
```
./stopWebLogic.sh
```

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.

If you cannot perform a graceful shutdown of OSM, for example, if you need to use the kill command or if there is a power failure on the host machine running the OSM WebLogic server instance, you must manually delete the files in the /tmp/vfs_cache_user folder (where user is the Linux or UNIX user account that you use to run the OSM WebLogic server) before you can restart OSM.

Verifying that OSM Has Stopped

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

Look at the text in the nohup.out file located in the directory where OSM was started (usually domain_home). One of the last messages displayed when the server shuts down is:
```
<Order Management Webservice destroyed.>
```
Try connecting to the WebLogic console. If you cannot, WebLogic is probably not running.
Look at the process list for the user who started the server. If WebLogic is running, there will probably be at least one process with startWebLogic.sh in its description.
Look in the user's process list for a java process that was started out of the Java directory for WebLogic. Process descriptions vary from platform to platform, so look at the process list when you know OSM is running to see what the entries look like on your platform. You can later use this information to confirm that the WebLogic server has shut down completely.