Kwwika-Superfeedr Demo

Demos‎ > ‎

Kwwika-Superfeedr Demo

This page is a work in progress. Please get in touch if you have any questions and we'll update the page with any necessary information.
Contents
1 Where can I see the demo
2 How to get your own dedicated demo
3 How do I set up the demo to run myself
3.1 Run the application locally
3.1.1 Web Application
3.1.2 Kwwika Update Console
3.2 Run the application remotely
3.2.1 Web Application
3.2.2 Kwwika Update Console

Where can I see the demo

You will find the demo here: http://superfeedr.kwwika.com

How to get your own dedicated demo

We'll then get back to you to let you know that your demo account has been set up and you'll be able to login to the Kwwika-Superfeedr demo using your Superfeedr credentials*.

* We will only store your username permanently and will only store your password during your demo session.

How do I set up the demo to run myself

If you plan to extend or use the Kwwika-Superfeedr demo application it's important to know that you can't create subscriptions within Superfeedr if you run directly from Visual Studio. In order to create subscriptions with Superfeedr you need to host the demo application on a publicly accessible web server in order for Superfeedr to be able to call back to your web server to verify subscriptions.

Whether running the application locally or remotely you should still sign up for Superfeedr and register for Kwwika Beta Access.

Run the application locally

Web Application

Register with Superfeedr as a Subscriber
Register with Kwwika and let us know that you are going to use the source code and run the demo yourself.
Download the code from GitHub (Kwwika-Superfeedr-Demo branch).
Ensure you have ASP.NET MVC installed. If not you install is using the Microsoft Web Platform installer (under What's New). You can get the installer here.
Ensure you have the .NET 4.0 framework installed - you should get it with ASP.NET MVC. If not you can get it here.
Create a SQL Server database instance and run the provided SQL files to create the necessary tables.

Ensure Server authentication allows SQL Server and Windows Authentication mode
Create a new database (maybe call it "Demo")
Create a new Login using SQL Server Authentication with the default database being "Demos"
Add the user to the Demos database - /Security/Users
Give the new user permissions on the Demo database of Connect, Insert, Update, Delete and Select
Run the sql\hubsubscriber_Users.sql script against the new database
Run the sql\hubsubscriber_Subscriptions.sql against the new database
Edit the Hubsubscriber\Web.config file by updating the database connectionstring to use the new Database (Demos) User/Login details to give the HubSubscriber application access to the database

Update Web.config <appSettings> to use your Superfeedr username and password.
Add your Superfeedr user to the hubsubscriber_Users database table
Open the the HubSubscriber.sln (solution file) in Visual Studio 2010. If you don't have Visual Studio you can get a trial from Microsoft.
Run the application within Visual Studio and you should be presented with the start page.

Kwwika Update Console

For more information on the Kwwika Update Console see the Kwwika Update Service Console page.

Run the application remotely

Web Application

The simplest way to deploy the application to your web server is to use the Visual Studio Publish functionality.

Open the the HubSubscriber.sln (solution file) in Visual Studio 2010. If you don't have Visual Studio you can get a trial from Microsoft.
Right-click on the HubSubscriber project and select Publish...
Your web server will also need to have a version of SQL Server installed and the database installed.
The Web.config details will need to be updated to match the credentials required on your remove server.

Kwwika Update Console

You'll also need to run the Kwwika Update Console on the remove web server. For more information on the Kwwika Update Console see the Kwwika Update Service Console page.

	Search this site