rhoconnect 3.0.0.beta1 → 3.0.0.beta3

data/CHANGELOG

@@ -1,4 +1,12 @@
-## 3.0.0 (not released)
+## 3.0.0.beta3 (not released)
+
+
+## 3.0.0.beta2 (2011-09-14)
+* #17830175 - moved SystemTimer in application's Gemfile so rhoconnect gem isn't specific
+* #13303895 - Generating a new source with 'rhosync source <name>' deletes sections in settings.yml
+* #10313437 - support source settings per environment
+
+## 3.0.0.beta1 (2011-09-01)
 * #1018 user delete now iterates through user sources and deletes data in redis
 * #11102931 ping api accepts vibrate string and int
 * #7197617 test spec helpers support pass through
@@ -10,7 +18,7 @@
 * #12105115 - removed unnecessary log4r dependency
 * added bundler to manage gem's dependencies, migrated from rspec1 to rspec2  
 * #5687948 - fixed issue "iPhone push specs failed" 
-* use redis 2.2.12 by default	
+* use redis 2.2.13 by default	
 * added SystemTimer gem dependency (used only on posix systems)					
 * #13616807 - Rake task spec:all fails for enterprise ruby (ree)
 * #13776713 - Rake -v 0.9.0 breaks rhosync rake tasks
@@ -35,6 +43,12 @@
 * #14286249 - jruby WAR file deployed , some of the links are broken in console window, should use the relative paths
 * #14285867 - jruby rhosync:start should have run with dtach
 * #17526603 - implement clientreset support for specified sources
+* #16628143 - implement 'ping' for multiple users at once in REST API
+* #18003071 - enhancing console to support multi-user ping
+* #10313437 - source settings per environment (also applied to dynamic adapters)
+* #18356697 - store lock is never released (bug fix)
+* #18672811 - edge case produces race condition which leads to corruption of Store data
+* #18508155 - on failed syncs allow the user to retry it up to pre-defined number of times
 
 ## 2.1.10 (2011-08-17)
 * #16001227 - raise exceptions on c2dm errors

data/Gemfile

@@ -4,15 +4,24 @@ source "http://rubygems.org"
 gemspec
 
 platforms :jruby do
-  gem 'trinidad'
+  gem 'jdbc-sqlite3', ">= 3.7.2"
+  gem 'dbi', ">= 0.4.5"
+  gem 'dbd-jdbc', ">= 0.1.4"
+  gem 'jruby-openssl', ">= 0.7.4"
   gem 'warbler'
 end
 
+gem 'sqlite3', ">= 1.3.3", :platforms => [:ruby, :mswin, :mingw]
+
 group :development do
-  gem 'rspec', '~> 2.6.0'
-  gem 'rcov', '>= 0.9.8'
+  gem 'fpm', '>= 0.3.8'
   gem 'ffaker', '~> 1.8.0'
-  gem 'rack-test', '>= 0.5.3', :require => 'rack/test'
   gem 'thor', '>= 0.13.6'
   gem 'webmock', '~> 1.6.4'
-end
+end
+
+group :test do
+  gem 'rspec', '~> 2.6.0'
+  gem 'rcov', '>= 0.9.8'
+  gem 'rack-test', '>= 0.5.3', :require => 'rack/test'
+end

data/Gemfile.lock

@@ -1,8 +1,7 @@
 PATH
   remote: .
   specs:
-    rhoconnect (3.0.0.beta1)
-      SystemTimer (~> 1.2.3)
+    rhoconnect (3.0.0.beta3)
       bundler (~> 1.0)
       json (~> 1.5.0)
       rake (= 0.9.2)
@@ -11,36 +10,32 @@ PATH
       rest-client (~> 1.6.1)
       rubyzip (~> 0.9.4)
       sinatra (~> 1.2)
-      sqlite3 (>= 1.3.3)
       templater (~> 1.0.0)
       uuidtools (>= 2.1.1)
 
 GEM
   remote: http://rubygems.org/
   specs:
-    SystemTimer (1.2.3)
     addressable (2.2.6)
-    crack (0.1.8)
+    crack (0.3.1)
     diff-lcs (1.1.3)
     extlib (0.9.15)
-    ffaker (1.8.0)
+    ffaker (1.8.1)
+    fpm (0.3.9)
+      json
     highline (1.6.2)
-    jruby-jars (1.6.4)
-    jruby-rack (1.0.10)
     json (1.5.4)
-    json (1.5.4-java)
     mime-types (1.16)
-    rack (1.3.2)
+    rack (1.3.3)
     rack-test (0.6.1)
       rack (>= 1.0)
     rake (0.9.2)
     rcov (0.9.10)
-    rcov (0.9.10-java)
     redis (2.2.2)
     redis-namespace (1.0.3)
       redis (< 3.0.0)
     resque (1.17.1)
-      json (>= 1.4.6, < 1.6)
+      json (< 1.6, >= 1.4.6)
       redis-namespace (~> 1.0.2)
       sinatra (>= 0.9.2)
       vegas (~> 0.1.2)
@@ -65,33 +60,28 @@ GEM
       highline (>= 1.4.0)
     thor (0.14.6)
     tilt (1.3.3)
-    trinidad (1.2.3)
-      jruby-rack (>= 1.0.9)
-      trinidad_jars (>= 1.0.1)
-    trinidad_jars (1.0.1)
     uuidtools (2.1.2)
     vegas (0.1.8)
       rack (>= 1.0.0)
-    warbler (1.3.2)
-      jruby-jars (>= 1.4.0)
-      jruby-rack (>= 1.0.0)
-      rake (>= 0.8.7)
-      rubyzip (>= 0.9.4)
     webmock (1.6.4)
       addressable (> 2.2.5, ~> 2.2)
       crack (>= 0.1.7)
 
 PLATFORMS
-  java
   ruby
 
 DEPENDENCIES
+  dbd-jdbc (>= 0.1.4)
+  dbi (>= 0.4.5)
   ffaker (~> 1.8.0)
+  fpm (>= 0.3.8)
+  jdbc-sqlite3 (>= 3.7.2)
+  jruby-openssl (>= 0.7.4)
   rack-test (>= 0.5.3)
   rcov (>= 0.9.8)
   rhoconnect!
   rspec (~> 2.6.0)
+  sqlite3 (>= 1.3.3)
   thor (>= 0.13.6)
-  trinidad
   warbler
   webmock (~> 1.6.4)

data/Rakefile

@@ -80,3 +80,89 @@ def ask(msg)
 end
 
 Bundler::GemHelper.install_tasks
+
+require 'rhoconnect/version'
+
+desc "Build archive rhoconnect-#{Rhoconnect::VERSION}.tar.gz into the pkg directory"
+task :archive do
+  `mkdir -p pkg`
+  `git archive --format=tar --prefix=rhoconnect-#{Rhoconnect::VERSION}/ HEAD | gzip > pkg/rhoconnect-#{Rhoconnect::VERSION}.tar.gz`
+end
+
+# Debian and RPM package building tasks
+
+version      = Rhoconnect::VERSION
+
+def create_post_install(version)
+  post_install = "#!/bin/sh
+VERSION=#{version}
+
+cd /tmp/installdir/rhoconnect-$VERSION
+./install.sh -v $VERSION
+
+echo \"Delete tmp files ...\"
+rm -rf /tmp/installdir
+end #create_Post_install"
+
+  post_install
+end #create_post_install
+
+def build_pkg(dist, arch, deps)
+  curr_dir            = `pwd`.strip
+  workspace           = "#{curr_dir}/pkg/workspace" 
+  version             = Rhoconnect::VERSION
+  description         = '"Rhoconnect production environment"'
+  post_install        = "#{workspace}/unix-like/post-install.sh"
+  prefix              = "/tmp/installdir/rhoconnect-#{version}"
+  gem_name            = "rhoconnect-#{version}.gem"
+  post_install        = create_post_install version
+  post_install_script = "#{workspace}/unix-like/post-install.sh" 
+
+  Dir.mkdir("#{workspace}")
+  Dir.mkdir("#{workspace}/unix-like")
+  Dir.mkdir("#{workspace}/utils")
+
+  # Turn post_install string into a bash script file and place it in the workspace.
+  post_install_file = File.new("#{post_install_script}", "w")
+  post_install_file.write(post_install)
+  post_install_file.close
+   
+  # Copy all necessary Files into the workspace
+  system("cp ./install.sh #{workspace}")
+  system("cp -r ./installer/unix-like/* #{workspace}/unix-like")
+  system("cp -r ./installer/utils/* #{workspace}/utils")
+  system("cp ./pkg/#{gem_name} #{workspace}")
+
+  # cd into the pkg dir so that fpm will create the package into the pkg dir.
+  Dir.chdir("./pkg")
+
+  # Construct fpm command
+  fpm_cmd = "fpm -s dir -t #{dist} -n rhoconnect -v #{version} -a #{arch} " + 
+            "-C #{workspace} --post-install #{post_install_script} --prefix #{prefix} " +
+            "--description #{description}"
+
+  # Add the list of dependencies to the fpm call
+  deps.each do |dep|
+    fpm_cmd << " -d #{dep}"
+  end #do
+
+  # Create the package
+  system(fpm_cmd)
+
+  # Leave no trace...
+  system("rm -rf #{workspace}")
+end #build_pkg
+
+task "build:deb" => :build do
+  deps = ['build-essential', 'zlib1g-dev','libssl-dev', 'libreadline5-dev', 
+          'libcurl4-openssl-dev', 'libsqlite3-0']
+
+  build_pkg "deb", "all", deps
+end #build:deb
+
+task "build:rpm" => :build do
+  deps = ['gcc-c++', 'zlib-devel', 'openssl-devel', 'readline-devel', 'curl-devel',
+          'pcre-devel']
+
+  build_pkg "rpm", "noarch", deps
+end #build:rpm

data/bench/bench_runner.rb

@@ -17,10 +17,11 @@ begin
   puts `bundle update`
   puts
   
-  puts "Installing rhoconnect ..."
-  puts `rake install`  
-  puts
-  
+  # Skip the following lines because becnchapp Gemfile uses path to rhoconnect code 
+  # puts "Installing rhoconnect ..."
+  # puts `rake install`
+  # puts
+
   Dir.chdir "bench/benchapp"  #puts Dir.pwd
   puts "Checking bench application dependencies ..."
   puts `bundle update`

data/bench/benchapp/Gemfile

@@ -1,17 +1,26 @@
 source 'http://rubygems.org'
 
-gem 'rhoconnect', '3.0.0'
+gem 'rhoconnect', :path => '../../'
 
-gem 'warbler', "~> 1.3.0", :platforms => :jruby
+# Helps with some of the limitations of green threads, not needed in ruby 1.9.x
+gem 'SystemTimer', '~> 1.2.3', :platforms => :ruby_18
+
+platforms :jruby do
+  gem 'jdbc-sqlite3', ">= 3.7.2"
+  gem 'dbi', ">= 0.4.5"
+  gem 'dbd-jdbc', ">= 0.1.4"
+  gem 'jruby-openssl', ">= 0.7.4"
+  gem 'warbler'
+end
+
+gem 'sqlite3', ">= 1.3.3", :platforms => [:ruby, :mswin, :mingw]
+
+# For jruby trinidad JRuby web server is used
+gem 'trinidad',  :platforms => :jruby
 
 group :development do
   # By default to run application thin web server is used
-  gem 'thin', :platforms => :ruby
-
-  # For jruby trinidad JRuby web server is used
-  gem 'trinidad',  :platforms => :jruby
-  # Alternative for jruby
-  # gem 'jetty-rackup',  :platforms => :jruby
+  gem 'thin', :platforms => [:ruby, :mswin, :mingw]
 end
 
 group :test do

data/bench/blobapp/Gemfile

@@ -1,27 +1,26 @@
 source 'http://rubygems.org'
 
-gem 'rhoconnect', '>= 3.0.0'
+gem 'rhoconnect', :path => '../../'
+
+# Helps with some of the limitations of green threads, not needed in ruby 1.9.x
+gem 'SystemTimer', '~> 1.2.3', :platforms => :ruby_18
 
 platforms :jruby do
-  gem 'jdbc-sqlite3', :require => false
-  gem 'dbi'
-  gem 'dbd-jdbc', :require => 'dbd/Jdbc'
-  gem 'jruby-openssl'
+  gem 'jdbc-sqlite3', ">= 3.7.2"
+  gem 'dbi', ">= 0.4.5"
+  gem 'dbd-jdbc', ">= 0.1.4"
+  gem 'jruby-openssl', ">= 0.7.4"
   gem 'warbler'
 end
 
-platforms :ruby do
-  gem 'sqlite3'
-end
+gem 'sqlite3', ">= 1.3.3", :platforms => [:ruby, :mswin, :mingw]
+
+# For jruby trinidad JRuby web server is used
+gem 'trinidad',  :platforms => :jruby
 
 group :development do
   # By default to run application thin web server is used
-  gem 'thin', '1.2.11', :platforms => :ruby
-
-  # For jruby trinidad JRuby web server is used
-  gem 'trinidad',  :platforms => :jruby
-  # Alternative for jruby
-  # gem 'jetty-rackup',  :platforms => :jruby
+  gem 'thin', :platforms => [:ruby, :mswin, :mingw]
 end
 
 group :test do

data/doc/adapters-crm.txt

@@ -0,0 +1,226 @@
+CRM adapters
+===
+
+With rhoconnect-adapters, you can utilize the pre-built set of [RhoConnect](http://rhomobile.com/products/rhoconnect/) applications 
+for popular CRM backends (SalesForce, Oracle CRM On Demand, Sugar CRM, etc.). Also, this library includes support for writing your own [RhoConnect](http://rhomobile.com/products/rhoconnect/)
+CRM applications to extend or customize the default functionality.
+
+### Generating Standard CRM Application
+
+To create a standard out-of-the-box rhoconnect CRM application use the following command:
+
+	$ rhoconnect-adapters crmapp <app_name> <CRM-backend>
+
+Here, the \<CRM\-backend\> parameter specifies the CRM backend that your application will use.
+Currently, the following CRM backends are supported:
+
+   - OracleOnDemand (for [Oracle CRM On Demand](http://crmondemand.oracle.com))
+   - MsDynamics (for [Microsoft Dynamics CRM](http://www.microsoft.com/en-us/dynamics/default.aspx))
+   - Salesforce (for [Salesforce CRM](http://www.salesforce.com/))
+   - Sugar (for [Sugar CRM](http://www.sugarcrm.com/crm/))
+
+The generated Rhoconnect CRM application structure will include typical [RhoConnect](http://rhomobile.com/products/rhoconnect/)
+files (for example, application.rb and settings.yml). It will also create a special vendor directory `vendor/\<CRM\-backend\>`
+containing all support files specific for the corresponding CRM backend.
+
+By default, the Rhoconnect CRM application will be generated with four standard source adapters corresponding
+to the following CRM objects:
+	
+	- Account
+	- Contact
+	- Lead
+	- Opportunity
+
+
+### Generating CRM Application without pre-built source adapters
+
+In some cases, it is necessary to generate an application without any standard sources.
+For this purpose, use the `--bare` option to generate just the application's skeleton.
+
+	rhoconnect-adapters crmapp <app_name> <CRM-backend> --bare
+	
+	
+### Generating CRM source adapters for the Rhoconnect CRM application
+
+Once you create your Rhoconnect CRM application, you can generate the desired source adapters
+based on the CRM objects by typing the following command in your application's directory:
+
+	rhoconnect-adapters crmsource <CRM-object-name> <CRM-backend>
+	
+Here, \<CRM\-object\-name\> must exactly correspond to the name of the CRM object you're trying to
+build the source adapter for.
+
+## Preparing the Rhoconnect CRM Application
+
+### OracleOnDemand settings
+All OracleOnDemand-specific settings are located in the `vendor/oracle_on_demand/settings` directory.
+In the file `settings.yml` you'll find the entries that you must customize before running the app.
+These are:
+
+- **:oraclecrm_service_url:** <oracle_web_services_integration_url> - substitute the default URL with your OracleOnDemand account URL.
+
+For every source adapter based on CRM object there is a corresponding *'vendor/oracle_on_demand/settings/\<CRM\-object\-name\>.yml'*
+file containing the descriptions for the OracleOnDemand CRM object.
+Every CRM object file has the following entries:
+
+	Query_Fields: hash of the objects's fields 
+			(each field's element has the value 
+			 in a form of the hash with the field's options , 
+			containing the following data):
+      	Label => <val> - display name of the field
+      	Type => <val> - type of the field data 
+			(textinput, textarea, Picklist, id, etc.)
+			
+	NonQuery_MappingWS_Fields: object's fields that can not be used
+	 		in OracleCRM Queries 
+			(however, Oracle returns them in GetMapping API)
+
+	StaticPickList: Normally, all picklist fields are queried 
+			for the allowed values using GetPicklistValues API
+            However, for certain fields OracleCRM API 
+			returns the error 'not a valid picklist'
+            This entry is a workaround for this error - 
+			fields's picklist values are statically hard-coded here.
+
+	ObjectFields: this one specifies a hash of fields 
+			that are actually references to other objects. 
+         	For example, AccountName field for Contact object 
+			is really a reference to the corresponding Account object.'
+	
+	TitleFields: this setting specifies an array of fields
+				used in constructing the object's title in the 'Show' page
+				using the Metadata method. Typically, you will want to put 
+				`name` fields in here.
+
+For the default generated CRM object adapters, this file is pre-filled with information. However, you can customize it by including or excluding
+options. For custom adapters, you need to fill this file with relevant information. List of object's fields, for example, can be obtained
+from the Oracle CRM On Demand documentation and then later used to fill the Query_Fields setting. Alternatively, user can customize the adapter and obtain 
+the list of fields using the GetMapping API.
+ 
+
+### MsDynamics settings
+All MsDynamics-specific settings are located in the **'vendor/ms_dynamics/settings'** directory.
+In the file *'settings.yml'* you'll find the entries that are necessary to customize before running the app.
+These are:
+
+- **:msdynamics_ticket_url:** <msdynamics_web_services_integration_url> - substitute the default URL with your MsDynamics account URL.
+
+For every source adapter based on CRM object there is a corresponding *'vendor/msdynamics/settings/\<CRM\-object\-name\>.yml'*
+file containing the descriptions for the Sugar CRM object.
+Every CRM object file has the following entries:
+
+	Query_Fields: hash of the objects's fields 
+			(each field's element has the value 
+			 in a form of the hash with the field's options , 
+			containing the following data):
+      	Label => <val> - display name of the field
+      	Type => <val> - type of the field data 
+			(textinput, textarea, Picklist, id, etc.)
+	
+	AttributeTypePicklists: this is a hash of picklist arrays
+			for artificially constructed fields
+	    	that are really represent some other field's type
+			for example, `customerid` field can be either
+			`account` or `contact`. In this case
+			field `customertype_attrtype` will represent `customerid` field's type
+			and will take values from the `AttributeTypePicklists`
+			array for the field `customerid_attrtype`
+
+	ObjectFields: this one specifies a hash of fields 
+			that are actually references to other objects. 
+         	For example, `account_name` field for Contact object 
+			is really a reference to the corresponding Account object.
+	
+	TitleFields: this setting specifies an array of fields
+				used in constructing the object's title in the 'Show' page
+				using the Metadata method. Typically, you will want to put 
+				`name` fields in here.
+
+For the default generated CRM object adapters, this file is pre-filled with information. However, you can customize it by including or excluding
+options. For custom adapters, you need to fill this file with relevant information. List of object's fields, for example, can be obtained
+from the MsDynamics documentation and then later used to fill the Query_Fields setting. Alternatively, user can customize the adapter and obtain 
+the desired list of object's fields using the MsDynamics SOAP API.
+
+### Sugar settings
+All Sugar-specific settings are located in the **'vendor/sugar/settings'** directory.
+In the file *'settings.yml'* you'll find the entries that are necessary to customize before running the app.
+These are:
+
+- **:sugarcrm_uri:** <oracle_web_services_integration_url> - substitute the default URL with your OracleOnDemand account URL.
+- **:debug_enabled:** <true/false> - enable debug output of the backend HTTP transactions.
+
+For every source adapter based on CRM object there is a corresponding *'vendor/sugar/settings/\<CRM\-object\-name\>.yml'*
+file containing the descriptions for the Sugar CRM object.
+Every CRM object file has the following entries:
+
+	Query_Fields: hash of the objects's fields 
+			(each field's element has the value 
+			 in a form of the hash with the field's options , 
+			containing the following data):
+      	Label => <val> - display name of the field
+      	Type => <val> - type of the field data 
+			(textinput, textarea, Picklist, id, etc.)
+
+	ObjectFields: this one specifies a hash of fields 
+			that are actually references to other objects. 
+         	For example, `account_name` field for Contact object 
+			is really a reference to the corresponding Account object.
+	
+	TitleFields: this setting specifies an array of fields
+				used in constructing the object's title in the 'Show' page
+				using the Metadata method. Typically, you will want to put 
+				`name` fields in here.
+
+For the default generated CRM object adapters, this file is pre-filled with information. However, you can customize it by including or excluding
+options. For custom adapters, you need to fill this file with relevant information. List of object's fields, for example, can be obtained
+from the SugarCRM documentation and then later used to fill the Query_Fields setting. Alternatively, user can customize the adapter and obtain 
+the desired list of object's fields using the SugarCRM REST API.
+
+### Salesforce settings
+All Salesforce-specific settings are located in the `vendor/salesforce/settings` directory.
+In the file `settings.yml` you'll find the entries that you must customize before running the app.
+These are:
+
+- **:salesforce_login_url:** <salesforce_soap_login_url> - Currently, this parameter is pre-defined to 
+`https://login.salesforce.com/services/Soap/c/22.0` for simple SOAP web service authentication. 
+Rhoconnect-adapters is not using `OAuth2` scheme at this point.
+
+For every source adapter based on CRM object there is a corresponding *'vendor/salesforce/settings/\<CRM\-object\-name\>.yml'*
+file containing the descriptions for the OracleOnDemand CRM object.
+Every CRM object file has the following entries:
+
+	Query_Fields: hash of the objects's fields 
+			(each field's element has the value 
+			 in a form of the hash with the field's options , 
+			containing the following data):
+      	Label => <val> - display name of the field
+      	Type => <val> - type of the field data 
+			(textinput, textarea, Picklist, datetime, id, etc.)
+			
+	ObjectFields: this one specifies a hash of fields 
+			that are actually references to other objects. 
+         	For example, AccountId field for Contact object 
+			is really a reference to the corresponding Account object.'
+	
+	TitleFields: this setting specifies an array of fields
+				used in constructing the object's title in the 'Show' page
+				using the Metadata method. Typically, you will want to put 
+				`name` fields in here.
+
+For the default generated CRM object adapters, this file is pre-filled with sample information. However, you can customize it by including or excluding
+different fields. For custom adapters, you need to fill this file with relevant information. List of object's fields, for example, can be obtained
+from the Salesforce documentation and then later used to fill the Query_Fields setting. Alternatively, user can customize the adapter and obtain 
+the list of fields using the `/sobjects/<CRM-object-name>/describe/` API.
+
+
+## Running the CRM Application
+Once your Rhoconnect application is customized and ready to run, you can start it like any other Rhoconnect app.
+Type the following command in the CRM application's root directory:
+
+	rake rhoconnect:start
+	
+
+## Meta
+Created and maintained by Rhomobile Inc.
+
+Released under the [MIT License](http://www.opensource.org/licenses/mit-license.php).

data/doc/adapters-intro.txt

@@ -0,0 +1,18 @@
+RhoConnect Adapters Introduction
+===
+
+rhoconnect-adapters is a ruby library containing a collection of the out-of-box [RhoConnect](http://rhomobile.com/products/rhoconnect) applications 
+for various needs.  
+
+## Setup
+Install the 'rhoconnect-adapters' gem by using the following command:
+
+	$ [sudo] gem install rhoconnect-adapters
+
+
+## Usage
+The 'rhoconnect-adapters' command creates pre-built [RhoConnect](http://rhomobile.com/products/rhoconnect/) applications.
+Visit the [RhoConnect](http://rhomobile.com/products/rhoconnect/) website for more information.
+
+
+<img src='https://s3.amazonaws.com/rhodocs/rhoconnect/rhoconnect-adapters-intro.png' alt='image' height='471' width='800' />

data/doc/client.txt

@@ -75,7 +75,14 @@ Rhoconnect Client is a library to add sync data capability to your applications.
 	@property(assign) NSString* name;
 
 	//possible values: RST_INCREMENTAL, RST_BULK_ONLY
-	@property int       sync_type;
+	@property(assign) int       sync_type;
+
+	//possible values: RMT_PROPERTY_BAG (default), RMT_PROPERTY_FIXEDSCHEMA
+	@property(assign) int       model_type;
+
+	//associations dictionary: the key is attribute name, the value is associated model name
+	//while using associations use object_id attribute as object reference
+	@property(assign) NSDictionary* associations;
 
 	// model constructor
 	- (id) init;
@@ -153,13 +160,33 @@ See [rhoconnect-client\Samples\ObjectiveC\store](http://github.com/rhomobile/rho
 	RhomModel* product = [[RhomModel alloc] init];
 	product.name = @"Product";
 
+	RhomModel* order = [[RhomModel alloc] init];
+	order.name = @"Order";
+    order.associations = [NSDictionary dictionaryWithObjectsAndKeys: @"Customer", @"customer", @"Product", @"product", nil];
+
 	RhoConnectClient* sclient = [[RhoConnectClient alloc] init];
-	NSArray* models = [NSArray arrayWithObjects:customer, product, nil];	
+	NSArray* models = [NSArray arrayWithObjects:customer, product, order, nil];
 
 	[sclient addModels:models];
 
 	sclient.sync_server = @"http://rhodes-store-server.heroku.com/application";
 
+#### Initialization of Schema model
+
+	RhomModel* product = [[RhomModel alloc] init];
+	product.name = @"Product_s";
+    product.model_type = RMT_PROPERTY_FIXEDSCHEMA;
+
+To create schema model tables edit database schema file: 
+
+* Copy file <rhoconnect-client>/shared/db/res/db/syncdb.schema to your project folder
+
+* Edit file syncdb.schema : add create table statment for each schema model. Note that mandatory object column should be in each table:
+
+    "object" varchar(255) PRIMARY KEY
+    
+* Open 'Copy bundle resources' build phase in project target and point it to local project db folder
+
 #### Login
 
 	:::cplusplus