Included CLI and UI sections into README (#9)

* Updated urls to internal in the README. Added section about Cadence UI

* Added CLI to README

* Updated README to not include internal links

* PR review feedback

Author: mfateev

README.md

@@ -1,8 +1,8 @@
 # Java Cadence Samples
 These samples demonstrate various capabilities of Java Cadence client and server. You can learn more about Cadence at:
-* Cadence: https://github.com/uber/cadence
-* Java Cadence Client: https://github.com/uber-java/cadence-client
-* Go Cadence Client: https://github.com/uber-go/cadence-client
+* [Cadence Service](https://github.com/uber/cadence)
+* [Cadence Java Client](https://github.com/uber-java/cadence-client)
+* [Go Cadence Client](https://github.com/uber-go/cadence-client)
 
 ## Overview of the Samples
 
@@ -63,10 +63,44 @@ If this does not work, see the instructions for running Cadence Server at https:
 
 ## Register the Domain
 
-To register the domain, run the follownig command once before running any samples:
+To register the *sample* domain, run the following command once before running any samples:
 
     ./gradlew -q execute -PmainClass=com.uber.cadence.samples.common.RegisterDomain
 
+## See Cadence UI
+
+The Cadence Server running in a docker container includes a Web UI.
+
+Connect to [http://localhost:8088](http://localhost:8088).
+
+Enter the *sample* domain. You'll see a "No Results" page. After running any sample, change the 
+filter in the
+top right corner from "Open" to "Closed" to see the list of the completed workflows.
+
+Click on a *RUN ID* of a workflow to see more details about it. Try different view formats to get a different level
+of details about the execution history.
+
+## Install Cadence CLI
+
+Check out [Cadence Service](https://github.com/uber/cadence) and run **make bins**.
+CLI executable named **cadence** will be in the root directory.
+
+To not pass the domain on every command set the following environment variable:
+
+    export CADENCE_CLI_DOMAIN=sample
+
+After the CADENCE_CLI_DOMAIN is set, to list closed workflow executions run:
+
+    cadence workflow list
+
+To see a history of a particular workflow execution run:
+
+    cadence workflow showid <WorkflowID>
+
+To see a stack trace of a currently running workflow execution run:
+
+    ./cadence workflow stack -w <WorkflowID>
+
 ## Run the samples
 
 Each sample has specific requirements for running it. The following sections contain information about