rhoconnect 3.4.5 → 4.0.0.beta.10

data/doc/metadata.txt

@@ -23,7 +23,7 @@ Then add `rhodes_translator` to your extensions in your Rhodes application's `bu
 	:::yaml
   	extensions: ["rhodes_translator"]
 
-Now define some metadata and add this to a `metadata` method your [source adapter](/rhoconnect/source-adapters).  For example:
+Now define some metadata and add this to a `metadata` method your [source adapter model](/rhoconnect/source-adapters).  For example:
 
 	:::ruby
 	def metadata

data/doc/migration.txt

@@ -1,194 +1,160 @@
-Migrating RhoSync application to RhoConnect
+Migrating your application to RhoConnect 4.0
 ===
 
-The best way of migrating your Rhosync app to Rhoconnect is to re-generate the application skeleton
+The best way of migrating your old RhoConnect app to Rhoconnect 4.0+ is to re-generate the application skeleton
 using Rhoconnect, then integrate all of your implementation specifics into it.
-However, if you prefer to migrate your Rhosync app manually, perform the steps in this document:
+However, if you prefer to migrate your RhoConnect app manually, perform the steps in this document.
 
-## Install the Bundler
-Install the `bundler` gem:
+## Upgrading dependency manifest
 
-	:::term
-	$ [sudo] gem install bundler
-
-## Create the Gemfile
-Create a new `Gemfile` file in your application directory with the following content:
+Open the `Gemfile` of your application and find the `rhoconnect` line, it should look something like:
 
 	:::ruby
-	source 'http://rubygems.org'
+	gem 'rhoconnect', '3.3.6'
 
-	gem 'rhoconnect', '3.0.0'
+Change this to the latest release version, which you can find on [rubygems.org](http://rubygems.org/gems/rhoconnect), for example if it is 4.0.1:
 
-	# Helps with some of the limitations of green threads, not needed in ruby 1.9.x
-	gem 'SystemTimer', '~> 1.2.3', :platforms => :ruby_18
+	:::ruby
+	gem 'rhoconnect', '4.0.1'
 
-	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
+Run the following command from the root application directory:
 
-	gem 'sqlite3', ">= 1.3.3", :platforms => [:ruby, :mswin, :mingw]
+	:::term
+	$ bundle install
 
-	# For jruby trinidad JRuby web server is used
-	gem 'trinidad',  :platforms => :jruby
+Now update your application's RhoConnect dependency manifest:
 
-	group :development do
-	  # By default to run application thin web server is used
-	  gem 'thin', :platforms => [:ruby, :mswin, :mingw]
-	end
+	:::term
+	$ rhoconnect update
 
-	group :test do
-	  gem 'rack-test', '>= 0.5.3', :require => "rack/test"
-	  gem 'rspec', '~> 2.6.0'
-	  gem 'rcov', '>= 0.9.8'
-	end
-	
+## Migrating application files
 
-## Edit the Rakefile
+If you have an existing RhoConnect application using version < 4.0 and want to upgrade it to RhoConnect 4.0+, then
+you need to update the `Gemfile` file to properly use the latest RhoConnect runtime dependencies.
 
-Adjust the existing `Rakefile` by changing `rhosync` to `rhoconnect`.
+First, follow the instructions described in the [previous section](/rhoconnect/migration#upgrading-dependency-manifest).
 
-Change this:
-	
-	:::ruby
-	begin
-	  require 'vendor/rhosync/lib/rhosync/tasks'
-	  require 'vendor/rhosync/lib/rhosync'
-	rescue LoadError
-	  require 'rhosync/tasks'
-	  require 'rhosync'
-	end
-	
-to this:
+Next, make sure your `Gemfile` looks like the following example, replacing the version as necessary.
+The `rhoconnect update` command will generate a reference `Gemfile.new` which you can use to replace your `Gemfile`:
 
 	:::ruby
-	begin
-	  require 'vendor/rhoconnect/lib/rhoconnect/tasks'
-	  require 'vendor/rhoconnect/lib/rhoconnect'
-	rescue LoadError
-	  require 'rhoconnect/tasks'
-	  require 'rhoconnect'
-	end
-
-## Edit config.ru
-
-Adjust `config.ru` file by performing the following steps:
-
-1) Change the section shown below to replace `rhosync` with `rhoconnect`.
+	source 'http://rubygems.org'
 
-Change this:
+	gem 'rhoconnect', '<put correct version here>'
+	gemfile_path = File.join(File.dirname(__FILE__), ".rcgemfile")
 
-	:::ruby
 	begin
-	  require 'vendor/rhosync/lib/rhosync/tasks'
-	  require 'vendor/rhosync/lib/rhosync'
-	rescue LoadError
-	  require 'rhosync/tasks'
-	  require 'rhosync'
+		eval(IO.read(gemfile_path))
+	rescue Exception => e
+		puts "ERROR: Couldn't read RhoConnect .rcgemfile"
+		puts e.message
+		exit 1
 	end
 
-to this:
+	# DON'T FORGET to add your application specific gems after this line ...
+	# ...
 
-	:::ruby
-	begin
-	  require 'vendor/rhoconnect/lib/rhoconnect/tasks'
-	  require 'vendor/rhoconnect/lib/rhoconnect'
-	rescue LoadError
-	  require 'rhoconnect/tasks'
-	  require 'rhoconnect'
-	end
+You must update `config.ru`, `Rakefile`, 'application.rb' and your source adapter files to match RhoConnect 4.0+ gem requirements.
 
-2) Change all `Rhosync` references to `Rhoconnect`.
-
-For example, change this:
+Replace your existing `config.ru` with the listing below. Save your old `config.ru` since you will use values within it in the new `config.ru`. 
 
 	:::ruby
-	Rhosync::Server.disable :run
+	# config.ru file
 	
-to this:
+	#!/usr/bin/env ruby
+	require 'rhoconnect/application/init'
 
-	:::ruby
-	Rhoconnect::Server.disable :run
-	
-## Edit application.rb
+	# secret is generated along with the app
+	# NOTE:
+	# Substitute 'REPLACE_ME' string by the Rhoconnect::Server.set :secret value from your old config.ru	
+	Rhoconnect::Server.set     :secret, 'REPLACE_ME'
 
-Adjust `application.rb` file with the following steps:
+	# !!! Add your custom initializers and overrides here !!!
+	# For example, uncomment the following line to enable Stats
+	#Rhoconnect::Server.enable  :stats
+	# uncomment the following line to disable Resque Front-end console
+	#Rhoconnect.disable_resque_console = true
+	# uncomment the following line to disable Rhoconnect Front-end console
+	#Rhoconnect.disable_rc_console = true
 
-1) Change the name of the base class from:
+	# run RhoConnect Application
+	run Rhoconnect.app	
 
-	:::ruby
-	class Application < Rhosync::Base
-	
-to:
+And replace your existing `Rakefile` with the following:
 
 	:::ruby
-	class Application < Rhoconnect::Base
+	require 'rubygems'
+	require 'bundler/setup'
+	require 'rhoconnect/tasks'
+	require 'rhoconnect'
+	require 'resque/tasks'
 
-## Edit spec/spec_helper.rb
+	ROOT_PATH = File.expand_path(File.dirname(__FILE__))
 
-Edit your `spec/spec_helper.rb` file to contain the following:
+	task 'resque:setup' do
+	  # The number of redis connections you want a job to have
+	  Rhoconnect.connection_pool_size = 1
+	  require 'rhoconnect/application/init'
 
-	:::ruby
-	require 'rubygems'
+	  Resque.after_fork do
+	    Store.reconnect
+	  end
+	end
 
-	# Set environment to test
-	ENV['RHO_ENV'] = 'test'
-	ROOT_PATH = File.expand_path(File.join(File.dirname(__FILE__),'..'))
-	Bundler.require(:default, ENV['RHO_ENV'].to_sym)
+Move your existing `application.rb` file into `controllers/ruby/application_controller.rb` and update it with the following:
 
-	# Try to load vendor-ed rhoconnect, otherwise load the gem
-	begin
-	  require 'vendor/rhoconnect/lib/rhoconnect'
-	rescue LoadError
-	  require 'rhoconnect'
+	:::ruby
+	class ApplicationController < Rhoconnect::Controller::AppBase
+  		register Rhoconnect::EndPoint
+
+  		post "/login", :rc_handler => :authenticate,
+                 :deprecated_route => {:verb => :post, :url => ['/application/clientlogin', '/api/application/clientlogin']} do
+    		login = params[:login]
+    		password = params[:password]
+    		<INSERT YOUR AUTHENTICATION CODE HERE>
+  		end
+
+  		get "/rps_login", :rc_handler => :rps_authenticate, 
+        	            :login_required => true do
+    		login = params[:login]
+    		password = params[:password]
+    		<INSERT YOUR RPS AUTHENTICATION CODE HERE>
+  		end
+
+  		# <.... PLACE HERE ALL OF YOUR EXISTING APPLICATION CODE ...>
 	end
 
-	# Load our rhoconnect application
-	require './application'
-	include Rhoconnect
+NOTE: You must remove `initializer` method from the ApplicationController class. It is no longer supported. 
 
-	require 'rhoconnect/test_methods'
+NOTE: If you had `store_blob` method overriden in the `application.rb` file - you will need to move it into the corresponding model class. Global `store_blob` method is no longer supported.
+See below for details.
 
-	module RSpec
-	  module Core
-	    module SharedExampleGroup
-	    private
-	      def ensure_shared_example_group_name_not_taken(name)
-	      end
-	    end
-	  end
-	end
+Re-generate your sources by running 'rhoconnect source YOUR_SOURCE' command for all of your application sources. This will create source's controller files in the `controllers/ruby` directory
+and source's model files in the `models/ruby` directory. After that, move your existing files from the `sources` directory into the `models/ruby` directory, replacing the generated model files. 
+Then, modify every file to make sure that your SourceAdapter classes now derive from the `Rhoconnect::Model::Base` class - SourceAdapters now became Models:
 
-	shared_examples_for "SpecHelper" do
-	  include Rhoconnect::TestMethods
-  
-	  before(:each) do
-	    Store.db.flushdb
-	    Application.initializer(ROOT_PATH)
-	  end  
+	:::ruby
+	class Product < Rhoconnect::Model::Base
+		# .... rest of your code
 	end
 
-## Edit spec files
-all of your spec files should be modified from:
+If you had global `store_blob` method in the `application.rb` file - you need to move it into every model's class that supports blobs:
 
 	:::ruby
-	describe "<SampleSpec>" do
-  		it_should_behave_like "SpecHelper"
-		...
-	end
+	class Product < Rhoconnect::Model::Base
+		# ... your code here ....
+		def store_blob(object, field, blob)
+			<YOUR_STORE_BLOB_IMPLEMENTATION>
+		end
+	end 
 
-to:
+If you had source spec files in the `spec/sources` directory - you will need to move them into `spec/models/ruby` directory and adjust the top line of each spec file:
 	
 	:::ruby
-	describe "<SampleSpec>" do
-  		it_should_behave_like "SpecHelper" do
-			...
-		end
-	end
-	
-## Edit implementation files
-Modify all of your application implementation files by changing the `Rhosync` references
-to `Rhoconnect`.
+	require File.join(File.dirname(__FILE__),'..','..','spec_helper')
+
+
+Finally, run `bundle install` to install any missing dependencies in your RhoConnect directory:
+
+	:::term
+	$ bundle install

data/doc/preparing-production.txt

@@ -64,7 +64,7 @@ By default, the Rhoconnect application is started with Rack FiberPool's size equ
 
 
 ## 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:
+This file contains all source adapter options and settings, such as the redis server connection. Before deploying to production, make sure you have the appropriate production settings. A complete list of the settings is in the [RhoConnect Settings chapter](/rhoconnect/settings). Some sample settings for production are shown below. In this sample, the `poll_interval` setting was auto-generated for a source adapter named Product.
 
 	:::yaml
 	:sources: 

data/doc/push-backend-setup.txt

@@ -3,6 +3,8 @@ Setting Up Push on Backend Application
 
 A RhoConnect push to the client consists of executing a RhoConnect ping call. There are three ways to execute a ping call: you can use the RhoConnect REST API to remotely call the ping, perform the ping job directly in a blocking ruby call, or enqueue a resque job to ping asynchronously.
 
+The push message can trigger the following actions in the Rhodes client application: alert with a message, sync one or more sources, vibrate, display a badge, and play a sound file.
+
 ## Pushing Remotely with the RhoConnect REST API
 
 You can trigger a push remotely using the [RhoConnect API Ping method](/rhoconnect/rest-api). This is useful if you want to fully control the push process from a remote server, such as when you use a RhoConnect plugin to connect your backend application to the RhoConnect server application.

data/doc/push-client-setup-android.txt

@@ -0,0 +1,78 @@
+Setting Up RhoConnect Push-Based Synchronization with Google Cloud Messaging
+===
+
+This chapter contains the steps you need to set up your Android Rhodes client and RhoConnect server for push messaging. After you perform the steps in this chapter, you will finish by performing the [client setup that is needed for all platforms](/rhoconnect/push-client-setup).
+
+**NOTE: If you are setting up RhoConnect Push Service on an Android client, you do not perform the steps in this chapter. Perform the steps in [RhoConnect Push Service setup](/rhoconnect/push-client-setup-rps) instead.**
+
+## Setting up Android Google Cloud Messaging
+
+To set up your Android Rhodes client application and RhoConnect server application for RhoConnect Push, you need to set up Android Google Cloud Messaging (GCM).
+
+To do so, perform the following sections from the [GCM Getting Started](http://developer.android.com/google/gcm/gs.html) guide.
+
+1. Creating a Google API project. (This gets a Google API project number which you will set in your Android client application.)
+2. Enabling the GCM Service.
+3. Obtaining an API Key. (You will set this key in your RhoConnect application.)
+
+You can optionally stop in these Getting Started instructions once you complete the Obtaining an API Key section.
+
+You may read common [GCM docs](http://developer.android.com/guide/google/gcm/index.html) at the Google developer site.
+
+## Setting up RhoConnect Server Application for GCM Push
+
+To set up your RhoConnect application for Android Google Cloud Messaging (GCM), you must have first set up Android Google Cloud Messaging. Then you can find your GCM API key in your [Google apis dashboard](https://code.google.com/apis/console).
+
+Update `settings/settings.yml` to include your GCM API key:
+
+	:::yaml
+	:development:
+	  :redis: localhost:6379
+	  :syncserver: http://localhost:9292/application/
+	  :licensefile: settings/license.key
+	  :gcm_api_key: your_gcm_api_key_here
+
+## Enabling the Rhodes Android Client for Push
+
+Enable push in your Rhodes client application in build.yml.
+
+	:::yaml
+	capabilities:
+	  - push
+
+## Setting up the Rhodes Android (GCM) Client
+
+Here are some guidelines for developing and testing an Android application that uses the Android Google Cloud Messaging feature.
+
+* To develop and test your GCM applications, you need to run and debug the applications on an Android 2.2 system image that includes the necessary underlying Google services.
+* To develop and debug on an actual device, you need a device running an Android 2.2 system image that includes the Market application.
+* To develop and test on the Android Emulator, you need to download the Android 2.2 version of the Google APIs Add-On into your SDK using the Android SDK and AVD Manager. Specifically, you need to download the component named "Google APIs by Google Inc, Android API 8". Then, you need to set up an AVD that uses that system image.
+* Android GCM system uses an existing connection for Google services. This requires users to set up their Google account on their mobile devices (and on emulator!).
+
+### Setting up the Google API project ID in Your Client Application
+
+To set up your Rhodes client application for Android Google Cloud Messaging (GCM), you must have first set up Android Google Cloud Messaging, where you noted the Google API project number.
+
+Register the Google API project number for your client application. Modify your application's build.yml to specify the Google API project number used to send PUSH messages:
+
+	:::yaml
+	android:
+	  push:
+	    sender: <Google API project number>
+
+### Setting up Status Bar Notifications for PUSH Messages
+
+On the Android client, it is possible to set up status bar notifications for PUSH messages. In this case, push notification can be shown on the Android status bar after ruby callback. The user can activate application by touching this notification.
+There are two modes available for push notifications:
+ - <i>always</i> - push notification is shown always
+ - <i>background</i> - push notification is shown only if application is backgrounded (not started)
+If no push notification mode is specified in build.yml then no notifications are shown at all.
+
+	:::yaml
+	android:
+	  push:
+	    notifications: background
+
+## Finishing Client Setup
+
+Once you have completed the above steps for setting up push on Android client and RhoConnect server, you must still [perform the client setup that is needed for all platforms](/rhoconnect/push-client-setup).

data/doc/push-client-setup-bb.txt

@@ -0,0 +1,81 @@
+Setting Up RhoConnect Push-Based Synchronization with BlackBerry Enterprise Server
+===
+
+This chapter contains the steps you need to set up your BlackBerry Rhodes client and RhoConnect server for push messaging. After you perform the steps in this chapter, you will finish by performing the [client setup that is needed for all platforms](/rhoconnect/push-client-setup).
+
+## Setting up RhoConnect Server Application for Push to Blackberry Clients
+
+To set up your RhoConnect application for pushing to a BlackBerry client, you will need to update `settings/settings.yml` to include the following:
+
+	:::yaml
+	:development:
+	  :redis: localhost:6379
+	  :mdsserver: 192.168.1.110
+	  :mdsserverport: 8080
+	  :syncserver: http://localhost:9292/application/
+	  :licensefile: settings/license.key
+
+Replace `:mdsserver:` and `:mdsserverport:` with the hostname/IP and port of your machine (default port is 8080).
+
+## Enabling Rhodes Client for RhoConnect Server Push
+
+Enable push in your rhodes application in build.yml.
+
+	:::yaml
+	capabilities:
+	  - push
+
+## Setting up the Rhodes Blackberry Client for Push
+
+Notifications to BlackBerry are sent using PAP 2.0 message through a BES/MDS server.
+
+On the simulator, this is done via the MDS simulator tool (which you've probably already seen in the form of a console window every time you do 'rake run:bb'). On the device, this is done through the BES/MDS server that the phone is configured to use.
+
+These instructions assume you are familiar with BES/MDS concepts (for more information please see [here](http://na.blackberry.com/eng/services/business/server/full/)).
+
+In case of Blackberry, if the application is in the background, an alert operation will bring the application upfront; other operations will not.
+
+### Setup MDS Simulator
+
+<i>Make sure you close the BlackBerry simulator and MDS simulator before continuing for your changes to take effect!</i>
+
+To enable the push port in your MDS simulator, edit the following file:
+
+	C:\Program Files\Research In Motion\BlackBerry JDE <VERSION YOU ARE BUILDING>\MDS\config\rimpublic.property
+
+Uncomment the last line of the file, which should be 'push.application.reliable.ports=100':
+
+	push.application.reliable.ports=100
+
+### Setup BlackBerry Simulator
+
+To listen for incoming messages on BlackBerry, the Rhodes application will start when the device powers on, and will run a listener thread in the background. You will use the "push_port" option in the [rhoconfig.txt](configuration#run-time-configuration) to specify the listening port for incoming push messages. If "push_port" is not specified, default will be 100 as shown in the previous section.
+
+For testing push on the BlackBerry simulator, you should preform the following 'kickstart' process. When the simulator starts, open the web browser on the simulator and navigate to any web page (i.e. http://m.google.com/). Now your simulator is ready to receive push messages.
+
+### Setup BlackBerry Device
+
+To test push on a BlackBerry device, you will need to use a device that is configured with a BES server. Then, [build your Rhodes application for the device](build#build-for-blackberry).
+
+### BlackBerry 5.0 Push service
+
+Rhodes 2.2 and higher supports the [Blackberry Push Service](http://na.blackberry.com/eng/developers/javaappdev/pushapi.jsp).
+
+Define in [rhoconfig.txt](configuration#run-time-configuration) which push to use (if empty or missed, only MDS push is supported).
+
+	push_options = 'mds;push_service'
+
+The following parameters are from [PushApplicationDescriptor](http://www.blackberry.com/developers/docs/5.0.0api/net/rim/blackberry/api/push/PushApplicationDescriptor.html). Set them in [rhoconfig.txt](configuration#run-time-configuration):
+
+	push_service_url  = 'https://pushapi.eval.blackberry.com/'
+	push_service_port = 20558
+	push_service_appname = 'RhoTest'
+	push_service_type = 'BPAS'
+
+### Alert Audio File Setup for Blackberry
+
+In case of Blackberry Rhodes client, if the audio file is in the public folder, the file name will be `/apps/public/alerts/test-file.mp3`.
+
+## Finishing Client Setup
+
+Once you have completed the above steps for setting up push on Blackberry client and RhoConnect server, you must still [perform the client setup that is needed for all platforms](/rhoconnect/push-client-setup).

data/doc/push-client-setup-ios.txt

@@ -0,0 +1,70 @@
+Setting Up RhoConnect Push-Based Synchronization with Apple Push Notification Service
+===
+
+This chapter contains the steps you need to set up your iOS Rhodes client and RhoConnect server for push messaging. After you perform the steps in this chapter, you will finish by performing the [client setup that is needed for all platforms](/rhoconnect/push-client-setup).
+
+## Setting up RhoConnect Server Application for Push to iOS Clients
+
+To set up your RhoConnect application for pushing to an iOS client, you will need to update `settings/settings.yml` to include the following:
+
+	:::yaml
+	:development:
+	  :redis: localhost:6379
+	  :iphonecertfile: settings/apple_push_cert.pem
+	  :iphonepassphrase: #=> empty or put password for your certificate
+	  :iphoneserver: gateway.sandbox.push.apple.com
+	  :iphoneport: 2195
+	  :syncserver: http://localhost:9292/application/
+	  :licensefile: settings/license.key
+
+This is for running your application in development mode; for production, you will need all of the iphone settings, and you change the `:iphoneserver:` to:
+
+	:::yaml
+  	:iphoneserver: gateway.push.apple.com
+
+## Enabling Rhodes Client for RhoConnect Server Push
+
+Enable push in your rhodes application in build.yml.
+
+	:::yaml
+	capabilities:
+	  - push
+
+## Setting up the Rhodes iOS (APNS) Client for Push
+
+iOS PUSH support uses the Apple Push Notification Service (APNS) introduced in iOS SDK 3.0.  In order to use the service, you will need to obtain a push-enabled provisioning profile and a server-side push certificate used for encrypting RhoConnect->APNS traffic.
+
+In case of iOS, regardless of the operation, the user will be presented with the option to activate the application if it is not running.
+
+**NOTE: For testing push, you will need to build and deploy your application to a physical iPhone (or iPad) device. Apple does not support testing push on simulators.**
+
+### Setup Push Certificate
+The first step to setting up your environment is to create an APNS push certificate. To create the SSL certificate, follow the "Creating the SSL Certificate and Keys" section on the
+[developer site](https://developer.apple.com/iphone/library/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ProvisioningDevelopment/ProvisioningDevelopment.html#//apple_ref/doc/uid/TP40008194-CH104-SW4).
+
+Once you have the certificate, you will need to export it to a .pem format using [these instructions](https://developer.apple.com/iphone/library/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ProvisioningDevelopment/ProvisioningDevelopment.html#//apple_ref/doc/uid/TP40008194-CH104-SW6). Make sure to name the output file 'apple_push_cert.pem' file from these instructions, since this is what we configured in our RhoConnect application.
+
+Once you have this file, copy it to your RhoConnect application directory under the settings folder:
+
+	:::term
+	$ cd myrhoconnectapp
+	$ cp /path/to/apple_push_cert.pem settings/apple_push_cert.pem
+
+Now your RhoConnect application is ready to send APNS messages.
+
+### Setup Provisioning Profile
+Next, you can setup your Apple Push Provisioning Profile using Apple's [developer site instructions](https://developer.apple.com/iphone/library/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ProvisioningDevelopment/ProvisioningDevelopment.html#//apple_ref/doc/uid/TP40008194-CH104-SW5).  Once you have the profile installed in XCode and on your test device, you are ready to test push.
+
+### Setup iOS Device
+Setting up the device is the same process as [building any normal Rhodes application](build#building-a-rhodes-application-for-iphoneipad). When you start the application, make sure to also open the console window (cmd-shift-R). When the application starts, you should see some output in the console that shows the device token (towards the top):
+
+	2010-08-19 10:14:22.627 rhorunner[1486:307] Device token is <10fd92ab fa8ee481 55d9af6e 73290863 22b323fd 0d18fdbd 19e92d03 c0fef7c8>
+
+This confirms that your application is running with push enabled. Once you login to the RhoConnect application and sync, you will see the device registered on the RhoConnect console under the user id you used to login. Now you are ready to [test push from your RhoConnect application](/rhoconnect/push-server-setup#testing-push-in-the-rhoconnect-web-console).
+
+### Alert Audio File Setup for iOS
+In case of iOS, audio files for the push alert should be placed in the `/public/alerts` folder and build script will copy them into root of the application main bundle (iOS wouldn't play file from any other place).
+
+## Finishing Client Setup
+
+Once you have completed the above steps for setting up push on iOS client and RhoConnect server, you must still [perform the client setup that is needed for all platforms](/rhoconnect/push-client-setup).