đź”—Starting and Stopping Standalone CDAP

Use the cdap.sh script (or, if you are using Windows, use cdap.bat) to start and stop the Standalone CDAP (the location will vary depending on where the CDAP SDK is installed):

$ cd cdap-sdk-3.6.0
$ ./bin/cdap.sh start
. . .
$ ./bin/cdap.sh stop
> cd cdap-sdk-3.6.0
> .\bin\cdap.bat start
. . .
> .\bin\cdap.bat stop

Note: There is an issue with running Microsoft Windows and using the CDAP Standalone scripts when JAVA_HOME is defined as a path with spaces in it. A workaround is to use a definition of JAVA_HOME that does not include spaces, such as C:\PROGRA~1\Java\jdk1.7.0_79\bin or C:\ProgramData\Oracle\Java\javapath.

Note that starting CDAP is not necessary if you use either the Virtual Machine or the Docker image, as they both start the Standalone CDAP automatically on startup.

Once CDAP is started successfully, in a web browser you will be able to see the CDAP UI running at http://localhost:9999, where you can deploy example applications and interact with CDAP.

Note that in the case of the Docker container running inside a Virtual Machine (as on either Mac OS X or Microsoft Windows), you will need to substitute the Docker VM's IP address for localhost in the web browser address bar.