rhoconnect 3.0.6 → 3.1.0.beta1

data/doc/net-plugin.txt

@@ -3,7 +3,7 @@ rhoconnect.NET
 
 A .NET 4 framework library for the [Rhoconnect](http://rhomobile.com/products/rhoconnect) App Integration Server.
 
-Using rhoconnect.NET, your [ASP.NET MVC3](http://www.asp.net/mvc/mvc3) application's data will transparently synchronize with a mobile application built on the [Rhodes framework](http://rhomobile.com/products/rhodes), or any of the available [Rhoconnect clients](http://rhomobile.com/products/rhoconnect/).
+Using rhoconnect.NET, your [ASP.NET MVC](http://www.asp.net/mvc/mvc4) application's data will transparently synchronize with a mobile application built on the [Rhodes framework](http://rhomobile.com/products/rhodes), or any of the available [Rhoconnect clients](http://rhomobile.com/products/rhoconnect/).
 
 ## Getting started
 
@@ -14,17 +14,20 @@ Copy the [`rhoconnect.NET`](https://github.com/rhomobile/rhoconnect.NET) github
 By default, the `rhoconnect.NET` repository contains the pre-built `RhoconnectNET.dll` library in the `bin/Release` subdirectory.
 However, you can build your own library using the provided Microsoft Visual Studio .NET solution file and the source code files. 
 
-In order to use `Rhoconnect.NET` functionality in your `ASP.NET MVC 3` application, first you need to include the `Rhoconnect.NET` library 
+You can download and use the sample [`ASP.NET MVC4`](https://github.com/rhomobile/RhoconnectNET_MVC4_App) application to repeat the steps described below.
+
+In order to use `Rhoconnect.NET` functionality in your `ASP.NET MVC` application, first you need to include the `Rhoconnect.NET` library 
 as a dependency to your application. Click `Project => Add Reference` menu item in the Visual Studio and navigate to the `RhoconnectNET.dll` library.
 After this step is completed, you can add references to the `Rhoconnect.NET` namespace into the application's and Controller's files:
 
 	using RhoconnectNET;
 	using RhoconnectNET.Controllers;
+	
 
 
 ## Registering Rhoconnect.NET routes for your application
 
-To establish the communication channel between ASP.NET MVC 3 application and Rhoconnect server, 
+To establish the communication channel between ASP.NET MVC application and Rhoconnect server, 
 you need to implement the following `init_rhoconnect` and `rhoconnect_authenticate` methods in the `Global.asax.cs` file 
 and call them from the `Application_Start` method:
 
@@ -40,8 +43,8 @@ and call them from the `Application_Start` method:
 	
 	// implement init_rhoconnect() method to establish
 	// communication link between `Rhoconnect` server
-	// and ASP.NET MVC 3 application
-	const bool init_rhoconnect()
+	// and ASP.NET MVC application
+	private void init_rhoconnect()
 	{
 		// this call allows parsing JSON structures into Objects
 		ValueProviderFactories.Factories.Add(new JsonValueProviderFactory());
@@ -55,14 +58,14 @@ and call them from the `Application_Start` method:
 											  rhoconnect_authenticate);
 	}
 	
-	const bool rhoconnect_authenticate(String username, String password, Hashtable params)
+	private bool rhoconnect_authenticate(String username, String password, Hashtable auth_attrs)
 	{
 		// perform your authentication here
 		return true;
 	}
 	
 `RhoconnectNET.Client.set_app_point` method is a main point
-in establishing the communication link between `Rhoconnect` server and the ASP.NET MVC 3 application
+in establishing the communication link between `Rhoconnect` server and the ASP.NET MVC application
 and it has the following parameters:
 
 <table border="1">
@@ -104,7 +107,7 @@ invokes to perform CRUD operations on the data for the dataset you want to synch
 Each of the routes is mapped to a corresponding `rhoconnect_<operation>` method in the **IRhoconnectCRUD** interface
 which you must implement in the dataset's Controller class.
 
-		public class MyDataController : Controller, IRhoconnectCRUD
+		public class ContactController : Controller, IRhoconnectCRUD
 		{
 			... implementation of Controller routes
 	
@@ -120,14 +123,14 @@ which you must implement in the dataset's Controller class.
 The route `/rhoconnect/query` is mapped to the `rhoconnect_query_objects` method of the **IRhoconnectCRUD**
 interface that you must implement in the corresponding dataset's Controller class. It must
 return a collection of source objects in the form of a JsonResult:
-
-		JsonResult rhoconnect_query_objects(String partition)
+		
+		public JsonResult rhoconnect_query_objects(String partition)
 		{
-			return Json(db.Products.ToDictionary("id"));
+			return Json(db.Contacts.ToDictionary(c => c.ID.ToString()));
 		}
 	
-In the above example, the Products object set is converted to `Dictionary<String, Object>`
-where the dictionary's key must correspond to an unique object's `id` field.
+In the above example, the Contacts Db set is converted to `Dictionary<String, Object>`
+where the dictionary's key must correspond to an unique object's `ID` field.
 After dictionary is created , it is converted to JsonResult and sent to the Rhoconnect server.
 
 ## Create new objects
@@ -137,10 +140,10 @@ return a newly created object's id in case of success:
 
 		public ActionResult rhoconnect_create(String objJson, String partition)
         {
-            Product new_product = (Product)RhoconnectNET.Helpers.deserialize_json(objJson, typeof(Product));
-            db.Products.AddObject(new_product);
+            Contact new_contact = (Contact)RhoconnectNET.Helpers.deserialize_json(objJson, typeof(Contact));
+            db.Contacts.Add(new_contact);
             db.SaveChanges();
-            return RhoconnectNET.Helpers.serialize_result(new_product.id);
+            return RhoconnectNET.Helpers.serialize_result(new_contact.ID);
         }
 	
 ## Update existing objects
@@ -150,13 +153,13 @@ return an updated object's id in case of success:
 
 		public ActionResult rhoconnect_update(Dictionary<string, object> changes, String partition)
         {
-            String obj_id = changes["id"]);
-            Product product_to_update = db.Products.First(p => p.id == obj_id); 
-		    // this method will update only the modified fields
-            RhoconnectNET.Helpers.merge_changes(product_to_update, changes);
-            db.ObjectStateManager.ChangeObjectState(product_to_update, EntityState.Modified);
+            int obj_id = Convert.ToInt32(changes["id"]);
+            Contact contact_to_update = db.Contacts.First(c => c.ID == obj_id); 
+            // this method will update only the modified fields
+            RhoconnectNET.Helpers.merge_changes(contact_to_update, changes);
+            db.Entry(contact_to_update).State = EntityState.Modified;
             db.SaveChanges();
-            return RhoconnectNET.Helpers.serialize_result(obj_id); 
+            return RhoconnectNET.Helpers.serialize_result(contact_to_update.ID); 
         }
 
 ## Delete objects from the dataset
@@ -166,21 +169,21 @@ return a deleted object's id in case of success:
 
         public ActionResult rhoconnect_delete(Object objId, String partition)
         {
-            String key = objId.ToString();
+            int key = Convert.ToInt32(objId);
 
-            Product product_to_delete = db.Products.Single(p => p.id == key);
-            db.Products.DeleteObject(product_to_delete);
+            Contact contact = db.Contacts.Find(key);
+            db.Contacts.Remove(contact);
             db.SaveChanges();
-            return RhoconnectNET.Helpers.serialize_result(objId);
+            return RhoconnectNET.Helpers.serialize_result(key);
         }
 
 ## Partitioning Datasets
 Each of the above methods have a partition key supplied with the CRUD request.	This partition key is used by `Rhoconnect` to uniquely identify the model dataset when it is stored in a rhoconnect instance.  It is typically an attribute on the model or related model.  `Rhoconnect` supports two types of partitions:
 
-* :app - No unique key will be used, a shared dataset is synchronized for all users.
-* lambda { some lambda } - Execute a lambda which returns the unique key string.
+* app - No unique key will be used, a shared dataset is synchronized for all users.
+* String partition key - unique key string identifying the partition (typically, user name).
 
-For example, the `Product` model above might have a relationship to the User model.  This provides us a simple way to organize the `Product` dataset for rhoconnect by reusing this relationship.  
+For example, the `Contact` model above might have a relationship to the User model.  This provides us a simple way to organize the `Contact` dataset for rhoconnect by reusing this relationship.  
 In this case, your implementation might filter out data on a per user basis.
 	
 For more information about Rhoconnect partitions, please refer to the [Rhoconnect docs](http://docs.rhomobile.com/rhoconnect/source-adapters#data-partitioning).
@@ -191,81 +194,111 @@ However, to complete the implementation, it is necessary to implement a reverse
 Typically, your MVC Controller class reacts to the actions by implementing the CRUD POST routes, for example:
 
 		[HttpPost]
-		public ActionResult Create(Product new_product)
+		public ActionResult Create(Contact new_contact)
 		{
 		     if (ModelState.IsValid)
 		     {
-                db.Product.AddObject(new_product);
+                db.Contacts.Add(new_contact);
                 db.SaveChanges();
                 return RedirectToAction("Index");  
               }
 
-            return View(new_product);
+            return View(new_contact);
         }
 
 Here, you need to insert a call which will notify the Rhoconnect instance that a new object has been created.
 For this reason, `RhoconnectNET` library provides three callback routines for CUD notifications.
 The above example will look like this after inserting the corresponding callback routine:
 
+		// This method is used to access current partition
+		// in Rhoconnect notification callbacks
+        private String partition()
+        {
+            return "testuser";
+        }
+		
 		[HttpPost]
-	    public ActionResult Create(Product product)
-	    {
-		     if (ModelState.IsValid)
-		     {
-                db.Product.AddObject(product);
+        public ActionResult Create(Contact contact)
+        {
+            if (ModelState.IsValid)
+            {
+                db.Contacts.Add(contact);
                 db.SaveChanges();
 
-				// insert these lines to provide
-				// notifications to Rhoconnect server
-				Hashtable reqHash = new Hashtable();
-                reqHash.Add(new_product.id.ToString(), new_products);
-                RhoconnectNET.Client.notify_on_create("Product", "partition_string", reqHash);
+                // insert these lines to provide
+                // notifications to Rhoconnect server
+                RhoconnectNET.Client.notify_on_create(partition(), contact);
 
                 return RedirectToAction("Index");  
-              }
+            }
 
-              return View(new_product);
+            return View(contact);
         }
 
 In the example above, user need to call `RhoconnectNET.Client.notify_on_create` method 
 with the following parameters:
 
-- String rhoconnect_source_name : dataset's name
-- String rhoconnect_partition : partition to which the object belongs (see above section "Partitioning datasets")
-- Hashtable<String, Object> object_hash : Hashtable with object's id as a key and the object itself as a value
+<table border="1">
+	<tr>
+		<td>String</td>
+		<td><code>partition</code></td>
+		<td>partition to which the object belongs (see above section "Partitioning datasets")
+		In the above example, the partition string is returned from the partition() method</td>
+	</tr>
+	<tr>
+		<td>Object</td>
+		<td><code>new_object</code></td>
+		<td>newly inserted object, which will be passed to Rhoconnect in a Json form</td>
+	</tr>
+</table>
+
+NOTE: The above notification callback has several overloads. In its simplest form, 
+`notify_on_create` callback will obtain information about the source name from the `Contact` object
+class name (since it is equal) and will get the `id` field from the object itself. If your model
+stores `id` field under the custom name, then, you can use the following override to pass its name into
+the callback, where its value will be accessed through the Reflection mechanism:
+
+		// insert these lines to provide
+        // notifications to Rhoconnect server
+        RhoconnectNET.Client.notify_on_create(partition(), "MyContactCustomID", contact);
+
+In addition to that, if your model's class is not equal to the Rhoconnect's Source Adapter name, you can
+use the following override to pass it along:
+
+		// insert these lines to provide
+        // notifications to Rhoconnect server
+        RhoconnectNET.Client.notify_on_create("MyCustomContactSourceName", partition(), "MyContactCustomID", contact);
+		
 
 In the same fashion , your dataset's Controller need to implement `Edit` and `Delete` callback notifications:
 
 		[HttpPost]
-        public ActionResult Edit(Product product)
+        public ActionResult Edit(Contact contact)
         {
             if (ModelState.IsValid)
             {
-                db.Products.Attach(product);
-                db.ObjectStateManager.ChangeObjectState(product, EntityState.Modified);
+                db.Entry(contact).State = EntityState.Modified;
                 db.SaveChanges();
-				
-				// insert this callback to notify Rhoconnect
-				// about the update operation
-                Hashtable reqHash = new Hashtable();
-                reqHash.Add(product.id.ToString(), product);
-                RhoconnectNET.Client.notify_on_update("Product", "partition_string", reqHash);
+
+                // insert this callback to notify Rhoconnect
+                // about the update operation
+                RhoconnectNET.Client.notify_on_update(partition(), contact);
 
                 return RedirectToAction("Index");
             }
-            return View(product);
+            return View(contact);
         }
-
+		
         [HttpPost, ActionName("Delete")]
-        public ActionResult DeleteConfirmed(String id)
+        public ActionResult DeleteConfirmed(int id)
         {            
-            Product product = db.Products.Single(p => p.id == id);
-            db.Products.DeleteObject(product);
+            Contact contact = db.Contacts.Find(id);
+            db.Contacts.Remove(contact);
             db.SaveChanges();
 
-			// insert this callback to notify Rhoconnect
-			// about the delete operation
-            RhoconnectNET.Client.notify_on_delete("Product", rhoconnect_partition(), id);
+            // insert this callback to notify Rhoconnect
+            // about the delete operation
+            RhoconnectNET.Client.notify_on_delete("Contact", partition(), id);
 
             return RedirectToAction("Index");
         }

data/doc/plugin-intro.txt

@@ -1,6 +1,8 @@
 RhoConnect Plugins Introduction
 ===
 
-Rhoconnect Plugins allow you to connect your backend apps seamlessly with rhoconnect.  
+Rhoconnect Plugins allow you to connect your backend apps seamlessly with rhoconnect. You can write the source (query, create, update and delete operations) into a backend application, and write a RhoConnect plugin in the language that matchs your backend application, such as Java or .NET.
 
-<img src='https://s3.amazonaws.com/rhodocs/rhoconnect-service/intro-plugin.png' alt='image' height='467' width='800' />
+<img src='https://s3.amazonaws.com/rhodocs/rhoconnect-service/intro-plugin.png' alt='image' height='467' width='800' />
+
+**NOTE:** Another way to connect particular backend applications (such as for Salesforce or Oracle) is to generate a [RhoConnect source adapter](/rhoconnect/source-adapters) which contains the query, create, update and delete operations.

data/doc/preparing-production.txt

@@ -0,0 +1,63 @@
+# Preparing App for Production
+By default your RhoConnect application generates a few files that you should be familiar with and understand the settings.
+
+## config.ru
+This rackup file contains runtime configuration for the RhoConnect sinatra application:
+	
+	:::ruby
+	Rhoconnect::Server.disable :run
+	Rhoconnect::Server.disable :clean_trace
+	Rhoconnect::Server.enable  :raise_errors
+	Rhoconnect::Server.set     :secret,      '<changeme>'
+	Rhoconnect::Server.set     :root,        ROOT_PATH
+	Rhoconnect::Server.use     Rack::Static, :urls => ["/data"], :root => Rhoconnect::Server.root
+	
+The important setting here `:secret` you will want to change.  `:secret` should be set to a long random string, it ___should not___ be set to a dictionary word or short string (30 characters or more is sufficient).  This is used for the session storage using a digest algorithm as described [here](http://guides.rubyonrails.org/security.html#session-storage).
+
+If you don't change the `:secret` setting, RhoConnect automatically warns you each time the application starts:
+
+ 	[11:34:56 AM 2011-01-12] ************************************************************
+
+	[11:34:56 AM 2011-01-12] WARNING: Change the session secret in config.ru from <changeme> to something secure.
+	[11:34:56 AM 2011-01-12]   i.e. running `rake rhoconnect:secret` in your app will generate a secret you could use.
+
+	[11:34:56 AM 2011-01-12] ************************************************************
+	
+
+As this warning states, a good way to generate a cryptographically secure secret is by running `rake rhoconnect:secret` in your RhoConnect  application.
+
+	:::term
+	$ cd storemanager-server
+	$ rake rhoconnect:secret
+	040a2355475e9d0fb591ef78d5b9ca61a34cbcfd3f11942b18bc1d91f1ca66c27b2e0386333843a7efa29f40fff03624cd908d0883364ffbfa3208ab23fa2664
+	
+Then plug this secret into your `config.ru`:
+
+	:::ruby
+	Rhoconnect::Server.set     :secret, '040a2355475e9d0fb591ef78d5b9ca61a34cbcfd3f11942b18bc1d91f1ca66c27b2e0386333843a7efa29f40fff03624cd908d0883364ffbfa3208ab23fa2664'
+
+To run RhoConnect in production mode, use `RACK_ENV` environment variable set to "production".  This ensures RhoConnect will use the `:production` section of the settings.  For example:
+
+	:::term
+	$ thin start -e production -p 9292
+
+Will start thin in with `RACK_ENV` set to "production".  
+
+NOTE: If you deploy using passenger or on RhoHub, this variable is automatically set to production.
+
+## settings/settings.yml
+This file contains all source adapter options and settings like the redis server connection.  Before deploying to production, make sure you have the appropriate production settings:
+
+	:::yaml
+	:sources: 
+	  Product: 
+	    :poll_interval: 300
+
+	:production: 
+	  :redis: myredishost:6379
+	  :licensefile: settings/license.key
+	  :syncserver: http://localhost:9292/application/
+
+## settings/license.key
+This contains your RhoConnect license key text.  By default, a RhoConnect application comes with a 10 device license.  Please see the [licensing page](/rhoconnect/licensing) for more details.
+

data/doc/rhoconnect-redis-stack.txt

@@ -0,0 +1,252 @@
+# Creating a RhoConnect Stack in Amazon Web Services
+
+This tutorial will guide you through setting up a Redis stack and a RhoConnect application stack in the Amazon Web Service (AWS) cloud.
+
+The RhoConnect application stack is scalable; it uses load balancing to automatically distribute and balance the incoming application traffic among all the instances you are running. You will set the maximum number of instances that the load balancer can create for your RhoConnect application.
+
+## Logging onto the Amazon Web Service
+
+Go to the [Amazon Web Service (AWS) Console](http://aws.amazon.com/console/) and click on the Sign in to the AWS Console button. You can sign into an existing AWS account, or create a new one.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/AWS-login-button.png" alt="AWS login button" />
+
+Or you can open the URL for your account directly if you have the account number: 
+
+	:::term
+	https://<your_account_number>.signin.aws.amazon.com/console
+
+Enter your User Name and Password for your AWS account, then click the Sign in button.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/aws-sign-in-account-number.png" alt="AWS login page" />
+
+## Creating a Custom RhoConnect Image
+
+In the AWS Management Console, change the Region to US West (N. California).
+
+**NOTE:** The stacks created in this document only work in the N. California region.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/cloudformation-tab-ncalif-crop.png" alt="Cloud Formation page N California region" />
+
+We provide a public preconfigured image that contains a blank RhoConnect app:
+
+ * `ami-65e4bb20` (Us West N. California)
+
+### Launching an Instance
+
+To create your own RhoConnect Image, launch an EC2 Image:
+
+Click the EC2 tab, click EC2 Dashboard, then click the Launch Instance button.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/ec2-launch-instance.png" alt="Launch Instance button" />
+
+Click the Launch Classic Wizard radio button. Click Continue.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/create-new-instance-launch-classic-wizard.png" alt="create new instance classic wizard" />
+
+### Requesting the Instance
+
+In the Choose an AMI section click the Community AMIs tab.
+Then paste in the AMI `ami-65e4bb20`. When the preconfigured RhoConnect AMI appears, click Select.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/request-instances-wizard-community-AMIs.png" alt="request instances - choose AMI" />
+
+In the Instance Details section, select the Instance Type (such as Large).
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/request-instances-instance-details.png" alt="request instances - instance details" />
+
+In the Instance Details section, Advanced Instance Options screen, change nothing. Click Continue.
+
+In the Instance Details section, Add Tags screen, enter a name for your custom RhoConnect EC2 instance in the Value Column of the Name key, then click Continue.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/request-instances-instance-details-add-tags.png" alt="request instances - add tags" />
+
+In the Create Key Pair section, select your existing key pair or create a new keypair.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/request-instances-key-pair.png" alt="request instances - key pair" />
+
+### Requesting the Instance - Configuring the Firewall
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/request-instances-configure-firewall.png" alt="request instances - configure firewall" />
+
+In the Configure Firewall section, click the Create New Security Group radio button.
+
+CLick the Add Rule button to add each port.
+
+ * Add port 22 for SSH.
+ * Add port 80 for HTTP.
+ * Add port 6379 for redis.
+
+**NOTE:** You may use a preexisting security group if it has ports 22, 80, and 6379 open.
+
+Enter a firewall name and a group description, then click Continue.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/request-instances-review.png" alt="request instances - review" />
+
+Make sure all the instance information is correct as shown on the Review page and then click Launch. 
+
+In the window titled "Launch Instance Wizard", click Close and wait for your instance to be Running.
+
+### Customizing the Instance
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/instances-instances.png" alt="instances - instances" />
+
+In the EC2 tab, Click on Instances.
+
+For Viewing, select Running Instances. Select your newly created RhoConnect instance and scroll down to see Private DNS in the lower section of the My Instances screen. 
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/running-instances-public-dns.png" alt="running instances - public dns" />
+
+You will need:
+
+ * your keypair (the .pem file AWS gives you when the keypair is created)
+ * the public DNS name of the Instance, which you will see as the public DNS name in the running instance. For Example: `ec2-184-72-16-39.us-west-1.compute.amazonaws.com`.
+ * the username: `ec2-user`
+
+From the command line, use ssh to login to the running instance, using the keypair, DNS name, and user name. For example:
+
+	:::term
+	$ ssh -i ~/.ssh/devkey.pem ec2-user@ec2-50-18-229-26.us-west-1.compute.amazonaws.com
+
+Replace the blank 'rhoapp' application in the /opt/nginx/html folder with your app, and set its owner as 'nginx' user.
+
+	:::term
+	$ cd /opt/nginx/html
+	# ... copy your application here under name 'rhoapp'
+	$ sudo chown -R nginx:nginx rhoapp
+
+You can test the application.
+
+	:::term
+	$ sudo /etc/init.d/redis start
+	$ sudo /etc/init.d/nginx start
+
+If everything is configured properly, then you can login to the RhoConnect web console in your browser by using the instance's public DNS name as the URL in your browser. When you are done, you can stop the application.
+
+	:::term
+	$ sudo /etc/init.d/nginx stop
+	$ sudo /etc/init.d/redis stop
+
+## Create the Image
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/running-instances-public-dns.png" alt="Create Image popup" />
+
+In the EC2 tab, right-click the RhoConnect instance and select Create Image (EBS AMI).
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/create-image.png" alt="Create Image" />
+
+In the Create Image window, enter the image name and description for your custom image. Then click Create This Image.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/create-image-request.png" alt="Create Image request" />
+
+In the Create Image window showing that the request is received, click on "View pending image: ami-XXXXXXXX to go to your Amazon Machine Image.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/ami-image.png" alt="amazon machine image" />
+
+Copy the AMI number; you will use it when you create the scaleable RhoConnect stack.
+
+## Creating the Scalable RhoConnect Stack
+
+Click the Cloud Formation tab.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/cloudformation-tab.png" alt="Cloud Formation page" />
+
+Ensure that the Region selected is US West (N. California) and Click the Create New Stack button.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/cloudformation-tab-new-stack-button.png" alt="Cloud Formation page new stack button" />
+
+### Create Stack - Select Template
+
+In the Select Template section, you must select the template file for your redis stack. This is the template to run the AMI image with the Redis server. 
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/create-stack-select-template.png" alt="Create Stack Select Template window" />
+
+First, enter the name that you want for your stack into the Stack Name field.
+
+Now get the template by either providing the URL for the template file, or by uploading the template file.
+
+#### Providing the URL for the Template File
+
+Click the Provide a Template URL radio button.
+
+Copy the following URL and paste it into the text field below the Provide a Template URL radio button.
+
+`https://s3-us-west-1.amazonaws.com/rhoconnect-ca-deploy/rhoconnect_template.txt`
+
+#### Uploading the Template File
+
+Click the Upload a Template File radio button.
+
+In another browser window, go to [https://s3-us-west-1.amazonaws.com/rhoconnect-ca-deploy/rhoconnect_template.txt](https://s3-us-west-1.amazonaws.com/rhoconnect-ca-deploy/rhoconnect_template.txt).
+
+Save that text file to your computer.
+
+Click the Choose File button, and navigate to and select your template file.
+
+Click Continue.
+
+### Create Stack - Specify Parameters
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/create-stack-specify-parameters.png" alt="Create Stack Specify Parameters window" />
+
+In the Create Stack: Specify Parameters window:
+
+ * Enter the AMI image number that you saved earlier.
+ * Enter the maximum number of RhoConnect application servers that you want to run in your stack. Default = 2.
+ * Enter the name for your existing EC2 KeyPair to enable SSH access to the stack instances.
+
+Click Continue.
+
+### Create Stack - Review
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/create-stack-review.png" alt="Create Stack Review window" />
+
+Click Continue to see a window entitled \"Create Stack\" showing that the stack is being created.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/create-stack-being-created.png" alt="Create Stack being created window" />
+
+Click Close.
+
+## Checking the Status
+
+In the AWS Management Console, Cloud Formation tab, click the checkbox for your stack. To see the progress of the creation of your stack, click the Refresh button; the status should become CREATE_COMPLETE soon.
+
+To see the progress of the components in your stack, you can click the Events tab. You can click the refresh button to see the progress.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/aws-management-create-complete.png" alt="AWS Management CREATE_COMPLETE window" />
+
+## Using the RhoConnect Application URL
+
+In the AWS Management Console, Cloud Formation tab, click the Outputs tab. You will see a list of the Stack Outputs. 
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/aws-management-outputs.png" alt="AWS Management Stack Outputs window" />
+
+At the top of the output list is the URL of the RhoConnect application. You can click on it to see the RhoConnect Console for the running RhoConnect server.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/rhoconnect-console.png" alt="RhoConnect Console" />
+
+To use this scaleable RhoConnect server in your Rhodes application, copy the URL for the RhoConnect application into the rhoconfig.txt file in your Rhodes application as the syncserver variable. For example:
+
+	:::term
+	syncserver = http://rhoconnec-RhoLoadB-OX64XR1IKNT2-1364705573.us-west-1.elb.amazonaws.com
+
+## Deleting the Stack
+
+You are charged for the stack that you have created, by the hour. When you no longer want to use the stack, you can delete it by right-clicking on the stack name in the AWS Management Console, Cloud Formation tab, and clicking Delete Stack.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-redis-aws/delete-stack.png" alt="Delete Stack" />
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

data/doc/source-adapters.txt

@@ -1,7 +1,9 @@
 RhoConnect Source Adapters
 ===
 
-Connecting to a backend service with RhoConnect requires that you write a small amount of Ruby code for the query, create, update and delete operations of your particular enterprise backend. The collection of the Ruby code for these operations we refer to as a "source" or "source adapter".
+Connecting to a backend service with RhoConnect requires that you write a small amount of code for the query, create, update and delete operations of your particular enterprise backend. A RhoConnect source adapter is a collection of the Ruby code for these operations.
+
+**NOTE:** You can also write this source code (the query, create, update and delete operations) into a backend application, and [write a RhoConnect plugin](plugin-intro) in the language that matchs your backend application, such as Java or .NET.
 
 ## Generate Source Adapter