How to compile ODK Manage project in Eclipse?

Development
#1

What are the dependencies?

Please help...

#2

See this wiki: http://code.google.com/p/opendatakit/wiki/ODKManage

··· On Tue, Oct 11, 2011 at 4:37 AM, Himanshu Bansal wrote:

What are the dependencies?

Please help...

--
Mitch Sundt
Software Engineer

University of Washington
mitchellsundt@gmail.com

#3

Thanks Mitch :slight_smile:

I have deployed it successfully. But we want to scale our project up in the
future, so would need a better environment than appspot.com

Can we deploy this code locally on Tomcat, and then get it on our own
domain, or is it hard-wired for Google App Engine only?

If not, then please suggest some ways, so that we can build on top of
Manage.

#4

There would be a fair bit of work required to port it to MySQL or
PostgreSQL, as you would have to (1) replace all the datastore interactions
with database calls and (2) the authentication would need to be changed.

The absolute simplest port would be to code your own JDBC interactions for
the database and use the container-managed security of Tomcat for
authentication.

While you could leverage the database layers of Aggregate 1.0 to make
everything cross-platform, it hasn't yet been tried and there are probably a
lot of cross-dependencies that have crept in that would need to be
disentangled, so I would avoid that.

Mitch

··· On Tue, Oct 11, 2011 at 10:35 PM, wrote:

Thanks Mitch :slight_smile:

I have deployed it successfully. But we want to scale our project up in the
future, so would need a better environment than appspot.com

Can we deploy this code locally on Tomcat, and then get it on our own
domain, or is it hard-wired for Google App Engine only?

If not, then please suggest some ways, so that we can build on top of
Manage.

--
Mitch Sundt
Software Engineer

University of Washington
mitchellsundt@gmail.com

#5

How to add fields to the Manage server table?

Do tell in terms of which package/file to edit, also from which
package/file the database is getting updated?

#6

i think that goes beyond what we can help with. i'm glad to recommend some
developers for hire if you need this level of assistance.

··· On Wed, Oct 12, 2011 at 23:17, wrote:

How to add fields to the Manage server table?

Do tell in terms of which package/file to edit, also from which
package/file the database is getting updated?

#7

Hmmm...ok let me tell where I am at, so that you can see things in
perspective.

I am integrating Manage-mobile and ODK Collect, into one, and adding push
notifications and other cool features.

To enable push, I have written all client-side code, but need to persist
device registration ID on server side, so that can push notifications to
devices. Manage server comes here, where I can add one more field for this
reg_id, corresponding to each device.

Then, we will have integrated Manage+Collect without overhead polling and
manual sync controls (though there will be a manual override).

Now, can I get some help?

For Manage-server, have you used JDBC layer on database ?

#8

Hi,

Can you describe what you mean by "reg_id"? Note that ODK Manage already
allows you to enter a "user ID" in the client-side app which is used to
identify the phone on the Manage server. You could enter the "reg id" there.

ODK Manage is currently backed by the appengine datastore using JDO (
http://www.oracle.com/technetwork/java/index-jsp-135919.html). If you wanted
to port this off of appengine, the easiest way would be to continue using
JDO and back it with a different database. You could also completely port
src/odk/manage/server/model off of JDO with a moderate amount of effort..

··· On Thu, Oct 13, 2011 at 2:33 AM, wrote:

Hmmm...ok let me tell where I am at, so that you can see things in
perspective.

I am integrating Manage-mobile and ODK Collect, into one, and adding push
notifications and other cool features.

To enable push, I have written all client-side code, but need to persist
device registration ID on server side, so that can push notifications to
devices. Manage server comes here, where I can add one more field for this
reg_id, corresponding to each device.

Then, we will have integrated Manage+Collect without overhead polling and
manual sync controls (though there will be a manual override).

Now, can I get some help?

For Manage-server, have you used JDBC layer on database ?

#9

Reg id is a string given to each c2dm registered device. Currently manage
has no field for that, though it can fit in any existing field.
There is one more alternative, please tell if it's worth it or not.
We can deploy n distribute app engine instances to our clients, each running
manage server.
Also, i am integrating manage client with odk, how is that?

··· On Oct 13, 2011 8:28 PM, "Adam Lerer" wrote:

Hi,

Can you describe what you mean by "reg_id"? Note that ODK Manage already
allows you to enter a "user ID" in the client-side app which is used to
identify the phone on the Manage server. You could enter the "reg id" there.

ODK Manage is currently backed by the appengine datastore using JDO (
http://www.oracle.com/technetwork/java/index-jsp-135919.html). If you
wanted to port this off of appengine, the easiest way would be to continue
using JDO and back it with a different database. You could also completely
port src/odk/manage/server/model off of JDO with a moderate amount of
effort..

On Thu, Oct 13, 2011 at 2:33 AM, him.albert.sal@gmail.com wrote:

Hmmm...ok let me tell where I am at, so that you can see things in
perspective.

I am integrating Manage-mobile and ODK Collect, into one, and adding push
notifications and other cool features.

To enable push, I have written all client-side code, but need to persist
device registration ID on server side, so that can push notifications to
devices. Manage server comes here, where I can add one more field for this
reg_id, corresponding to each device.

Then, we will have integrated Manage+Collect without overhead polling and
manual sync controls (though there will be a manual override).

Now, can I get some help?

For Manage-server, have you used JDBC layer on database ?

#10

  1. What is c2dm? I'm trying to understand if reg_id is a field that you look
    up from the phone OS (like phone#, IMEI, etc.) or if it's a field that you
    want to enter into the client (like username).

  2. It is fine if you want to distribute app engine instances (servers) to
    your organizations (I don't want to use the word 'client' because that's
    what we call the phone app). You can set the server location on each ODK
    Manage phone client .

  3. I think you mean that you are integrating ODK Manage client with ODK
    Collect. I don't see anything wrong with that if it benefits your use case.
    Yaw/Mitch, do you have any opinion?

··· On Thu, Oct 13, 2011 at 11:31 AM, Himanshu Bansal wrote:

Reg id is a string given to each c2dm registered device. Currently manage
has no field for that, though it can fit in any existing field.
There is one more alternative, please tell if it's worth it or not.
We can deploy n distribute app engine instances to our clients, each
running manage server.
Also, i am integrating manage client with odk, how is that?
On Oct 13, 2011 8:28 PM, "Adam Lerer" adam.lerer@gmail.com wrote:

Hi,

Can you describe what you mean by "reg_id"? Note that ODK Manage already
allows you to enter a "user ID" in the client-side app which is used to
identify the phone on the Manage server. You could enter the "reg id" there.

ODK Manage is currently backed by the appengine datastore using JDO (
http://www.oracle.com/technetwork/java/index-jsp-135919.html). If you
wanted to port this off of appengine, the easiest way would be to continue
using JDO and back it with a different database. You could also completely
port src/odk/manage/server/model off of JDO with a moderate amount of
effort..

On Thu, Oct 13, 2011 at 2:33 AM, him.albert.sal@gmail.com wrote:

Hmmm...ok let me tell where I am at, so that you can see things in
perspective.

I am integrating Manage-mobile and ODK Collect, into one, and adding push
notifications and other cool features.

To enable push, I have written all client-side code, but need to persist
device registration ID on server side, so that can push notifications to
devices. Manage server comes here, where I can add one more field for this
reg_id, corresponding to each device.

Then, we will have integrated Manage+Collect without overhead polling and
manual sync controls (though there will be a manual override).

Now, can I get some help?

For Manage-server, have you used JDBC layer on database ?

#11

C2dm is cloud to device messaging, a system to enable push notifications on
android. Reg id is alloted by google's c2dm servers to every device, which
we have to persist, so that server can identify devices later, when there is
update on server and notify registered users. I will post complete doc
tomorow on this.
I am asking opinion in general, connecting manage client and odk collect for
the odk project. We can also enable push notifications to automaticlly
download tasks, no need to poll.

··· On Oct 13, 2011 9:22 PM, "Adam Lerer" wrote:

  1. What is c2dm? I'm trying to understand if reg_id is a field that you
    look up from the phone OS (like phone#, IMEI, etc.) or if it's a field that
    you want to enter into the client (like username).

  2. It is fine if you want to distribute app engine instances (servers) to
    your organizations (I don't want to use the word 'client' because that's
    what we call the phone app). You can set the server location on each ODK
    Manage phone client .

  3. I think you mean that you are integrating ODK Manage client with ODK
    Collect. I don't see anything wrong with that if it benefits your use case.
    Yaw/Mitch, do you have any opinion?

On Thu, Oct 13, 2011 at 11:31 AM, Himanshu Bansal < him.albert.sal@gmail.com> wrote:

Reg id is a string given to each c2dm registered device. Currently manage
has no field for that, though it can fit in any existing field.
There is one more alternative, please tell if it's worth it or not.
We can deploy n distribute app engine instances to our clients, each
running manage server.
Also, i am integrating manage client with odk, how is that?
On Oct 13, 2011 8:28 PM, "Adam Lerer" adam.lerer@gmail.com wrote:

Hi,

Can you describe what you mean by "reg_id"? Note that ODK Manage already
allows you to enter a "user ID" in the client-side app which is used to
identify the phone on the Manage server. You could enter the "reg id" there.

ODK Manage is currently backed by the appengine datastore using JDO (
http://www.oracle.com/technetwork/java/index-jsp-135919.html). If you
wanted to port this off of appengine, the easiest way would be to continue
using JDO and back it with a different database. You could also completely
port src/odk/manage/server/model off of JDO with a moderate amount of
effort..

On Thu, Oct 13, 2011 at 2:33 AM, him.albert.sal@gmail.com wrote:

Hmmm...ok let me tell where I am at, so that you can see things in
perspective.

I am integrating Manage-mobile and ODK Collect, into one, and adding
push notifications and other cool features.

To enable push, I have written all client-side code, but need to persist
device registration ID on server side, so that can push notifications to
devices. Manage server comes here, where I can add one more field for this
reg_id, corresponding to each device.

Then, we will have integrated Manage+Collect without overhead polling
and manual sync controls (though there will be a manual override).

Now, can I get some help?

For Manage-server, have you used JDBC layer on database ?

#12

Definitely follow Adam's suggestion of staying with JDO and changing the
underlying database layer (Adam is the author of ODK Manage).

Unfortunately, guiding you through this level of change is beyond what we
can do.

Mitch

··· On Thu, Oct 13, 2011 at 9:57 AM, Himanshu Bansal wrote:

C2dm is cloud to device messaging, a system to enable push notifications on
android. Reg id is alloted by google's c2dm servers to every device, which
we have to persist, so that server can identify devices later, when there is
update on server and notify registered users. I will post complete doc
tomorow on this.
I am asking opinion in general, connecting manage client and odk collect
for the odk project. We can also enable push notifications to automaticlly
download tasks, no need to poll.
On Oct 13, 2011 9:22 PM, "Adam Lerer" adam.lerer@gmail.com wrote:

  1. What is c2dm? I'm trying to understand if reg_id is a field that you
    look up from the phone OS (like phone#, IMEI, etc.) or if it's a field that
    you want to enter into the client (like username).

  2. It is fine if you want to distribute app engine instances (servers) to
    your organizations (I don't want to use the word 'client' because that's
    what we call the phone app). You can set the server location on each ODK
    Manage phone client .

  3. I think you mean that you are integrating ODK Manage client with ODK
    Collect. I don't see anything wrong with that if it benefits your use case.
    Yaw/Mitch, do you have any opinion?

On Thu, Oct 13, 2011 at 11:31 AM, Himanshu Bansal < him.albert.sal@gmail.com> wrote:

Reg id is a string given to each c2dm registered device. Currently manage
has no field for that, though it can fit in any existing field.
There is one more alternative, please tell if it's worth it or not.
We can deploy n distribute app engine instances to our clients, each
running manage server.
Also, i am integrating manage client with odk, how is that?
On Oct 13, 2011 8:28 PM, "Adam Lerer" adam.lerer@gmail.com wrote:

Hi,

Can you describe what you mean by "reg_id"? Note that ODK Manage already
allows you to enter a "user ID" in the client-side app which is used to
identify the phone on the Manage server. You could enter the "reg id" there.

ODK Manage is currently backed by the appengine datastore using JDO (
http://www.oracle.com/technetwork/java/index-jsp-135919.html). If you
wanted to port this off of appengine, the easiest way would be to continue
using JDO and back it with a different database. You could also completely
port src/odk/manage/server/model off of JDO with a moderate amount of
effort..

On Thu, Oct 13, 2011 at 2:33 AM, him.albert.sal@gmail.com wrote:

Hmmm...ok let me tell where I am at, so that you can see things in
perspective.

I am integrating Manage-mobile and ODK Collect, into one, and adding
push notifications and other cool features.

To enable push, I have written all client-side code, but need to
persist device registration ID on server side, so that can push
notifications to devices. Manage server comes here, where I can add one more
field for this reg_id, corresponding to each device.

Then, we will have integrated Manage+Collect without overhead polling
and manual sync controls (though there will be a manual override).

Now, can I get some help?

For Manage-server, have you used JDBC layer on database ?

--
Mitch Sundt
Software Engineer

University of Washington
mitchellsundt@gmail.com