Starting and Stopping OData Server

Use the dbosrv16 utility to start, and dbostop to stop the embedded HTTP server and the OData Producer.

The SAP ASE installer creates all the folders and copies the files necessary to run OData. After you successfully install SAP ASE, start or stop the embedded HTTP server and the OData Producer by using:
Command Description
dbosrv16
The utility, located in $SYBASE/ODATA-16_0/bin64 (%SYBASE%\ODATA-16_0\bin64 for Windows), starts the embedded HTTP server and the OData Producer by invoking the configuration file you created to set up parameters and options. The syntax is:
dbosrv16 server.properties
This specifies name of the configuration file you used to set up the database connection.

dbosrv16 contains both the servlet implementation and the components necessary to launch its own HTTP server.

dbostop
The utility, located in $SYBASE/ODATA-16_0/bin64 (%SYBASE%\ODATA-16_0\bin64 for Windows), stops the embedded HTTP server and the OData Producer. The syntax is:
dbostop [-q] {-f properties-filename | -p port-number}
where:
  • -f properties-filename – uses the port number specified by the ShutdownListenerPort option to send a shutdown request. properties-filename is the file name with which you started the server. If you do not include -f, dbostop attempts to shut down the embedded HTTP server and the OData Producer on port 2449.
  • -p port-number – is the value of the ShutdownListenerPort option you specified in the OData Server configuration file that you used to start OData Server. Using -p specifies the port number to send the shutdown request to. The default value is 2449. This option is:
    • Not required if your server.properties configuration file already includes the shutdownlistener port.
    • Required if you do not specify the server.properties configuration file in the command.
    If you do not include -p, dbostop attempts to shut down the embedded HTTP server and the OData Producer on port 2449
  • -q – attempts to shut a server down quietly; no message appears.

Any time you change the database schema, stop OData Server with dbostop, then restart it with dbosrv16. This allows the changes to take effect and become visible to OData clients.