+Java servlet container that accepts .war (e.g. tomcat, resin, jetta, ...)
+* Create basic d-flat repository using base/storage/mrt.local.properties
+Edit - these ant properties that define the
+new Storage Microservice
+-storage.node=[absolute file path to storage node that will be constructed by script]
+-can.node=[absolute file path to CAN node that will be constructed by script]
+The actual storage of the pairtree/dflat architecture will occur under ths directory.
+-can.info.identifier=[any number - used in restful interface]
+The Storage Service restful calls use this number which must be unique to the
+-store.info.baseURI=[Absolute URL that will be used for the Storage Service]
+This is the URL for your Storage Service calls.
+if present then delete storage service every time clean/build is done in maven
+if present then delete CAN every time clean/build is done in maven
+NOTE: If you are using Windows for your Storage Service, then the file paths that you
+set in the properties need to be specified in a unix style format with forward slashes:
+C:/Documents and Settings/dloy/...
+cd to downloaded version of mrt-storeCloud
+This should build a working storage service
+* Building a working servlet
+After running the previous step a storage.war file will now exist that can be used
+on the Storage Service defined by the previous step.
+The .war is base/store-war/war/storage.war
+Place this .war in a java container (tomcat/webapps, resin/webapps, jetta, ...) and start the container.
+The restful interface should now be available at[store.info.baseURI]
+Example: http:storge.myhost.org:8080/storage/state - Storage Service state
+Example: http:storge.myhost.org:8080/storage/state/10 - CAN state
+- Storage service URLs are sensitive to slashes (/) so URL encoding is required for any
+URL element containing a slash: