Building UnifiedPush Server from sources
by A577127
Hello,
I need to try some stuff with the UnifiedPush server (eg redirecting HTTP
POST requests to my own test server instead of GCM's server). However I'm
not really familiar with JBoss.
I've downloaded the sources from git here
<https://github.com/aerogear/aerogear-unifiedpush-server> and I need to do
a few things but didn't find out how to :
- Import the project to Eclipse (classic Eclipse Import doesn't show
anything)
- Build a .war deployable file (I looked for an Ant target on Github but
didn't find any)
- Edit web interface (I saw that .js file was minified ; can I get a
non-minified somewhere ?)
I know my questions are quite evasive, if I ask for too much don't hesitate
to just give me links to tutorials, I will take time to read them and try to
solve these problems myself.
Thanks,
--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Building-UnifiedPush-Server-fro...
Sent from the aerogear-dev mailing list archive at Nabble.com.
9 years, 11 months
Proxy settings questions
by A577127
Hello,
I'm intending to implement the proxy settings for the UPS. However it's not
really clear to me how different type of proxies work and what are the
different possible configurations.
I looked at these mockups :
https://issues.jboss.org/secure/attachment/12380178/proxy-config.png
And from what I saw, it looks like you only have one global proxy to set.
Should it be possible to configure several proxies (like a HTTP proxy for
GCM/SimplePush and a SOCKS proxy for APNS) ?
At the company I work for, they only have an HTTP proxy. Sending push
notifications to the APNS is still possible thanks to a socket tunnel (which
is already implemented in java-apns library by the way). But I guess some
companies have also a SOCKS proxy.
Moreover, since push notification only use HTTP(S) requests and TLS socket,
how could a FTP proxy be used ?
If you could clarify these points, that would help me a lot.
Thanks,
--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Proxy-settings-questions-tp7577...
Sent from the aerogear-dev mailing list archive at Nabble.com.
9 years, 12 months
SIMPLE Analytics / Metrics for the UnifiedPush Server
by Matthias Wessendorf
Hello,
second try - as the first thread was hijacked around other discussions.
For a first round of collecting some more data around the usage of the push
server (aka analytics/metrics), I'd propose we keep it very simple!
Overall, I see one major area of interest:
*metrics around push messages being sent:
- time of sending (using timezone of the server?)
- group of receivers (e.g. everyone or the provided cirterias(e.g. alias,
categories,...))
- payload (the entire payload, including custom keys - not only alert,
sound, badge etc)
- info on: "could we deliver to the 3rd party networks?"
This is a nice feature, and would enrich the UPS. The server will have a
RESTful endpoint, and an UI for displaying the data. The view would be
bascially a history for all the push sent (per "Push Application"
construct).
However, I can see also some interest around device specific metrics:
Today we obivously store all the registered devices, but we also remove
them from the database table if needed (to not send messages to phones that
would no longer receive them anyways).
Something that would be interesting as well, might be the following data:
- how often was an app has reached the push server (note: every time the
app starts, the metadata of the server is being updated (see [2])
- number of device-tokens / registrationIDs that have been removed, when
receiving errors from Apple/Google (see [3] or [4])
- number of devices, that were activly removed using our APIs (supported
only on Android/SimplePush due to Apple policy, see [5])
While the initial focus should be around the message related metrics,
capturing some device data is nice too.
Any thoughts ?
-Matthias
PS: Oh, for the longer run(...), I'd also like to see metrics like "was
mobile app opened due to a push notification". BUT that also requires some
more work/reseach on the client Push SDKs. But seriously, this is not a
priority for the next few months!
[1] https://issues.jboss.org/browse/AGPUSH-116
[2]
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs...
[3]
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/...
[4]
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/...
[5]
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs...
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
9 years, 12 months
Allow Push Without Master-Secret?
by Florian Schrofner
Hey there guys!
We are currently working on our semester project which allows you to sync
notifications across different devices. The notifications themselves are
stored on a separate webserver, but we are using the aerogear unified
pushserver to start a sync.
All the devices which should receive the push (and start the sync) are using
the same alias, the push will be triggered by one of these devices
On Android it should work fine, since we are able to use the Java Client and
the secret without a problem (at least i think the secret would not be
visible to anyone on Android).
But we are also planning to implement a Chrome Addon and we don't really
like the idea to make the master-secret visible to everyone.
We know that the unified push server is not intended to be used as
client-to-client push server atm, but since the pushes don't contain any
important data it would be a sufficient solution to just disable the need
for a master-secret if an alias is given (this would at least prevent
broadcasts from being sent by third persons).
So we wanted to ask you guys which lines of code we should modify inorder to
allow pushes without master-secret, if an alias is given?
It should only be an additional "if", I guess.. or does it get more
complicated?
We are currently hosting our unified pushserver on OpenShift (would be nice
if you could also roughly tell us how to push the changes onto the server..
do we need to recompile everything?)
Cheers,
Florian
--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Allow-Push-Without...
Sent from the aerogear-dev mailing list archive at Nabble.com.
9 years, 12 months
Re: [aerogear-dev] Problems sending notifications Cordova
by Florian Schrofner
At least the interface for aerogear was reachable while i was testing the pushes.. is it independant from the "real" server?
Unfortunately none of the pushes were sent/received, so it's not only the first one.
The app on Android was running and the registration was successful.
9 years, 12 months
Problems sending notifications Cordova
by Miguel Lemos
Hi,
After a couple of weeks without testing the service, I tried to send a push
notification, but the device didn't receive nothing. I didn't change
nothing...
And:
- I get a "job submitted" answer;
- The device is still registered and is with the "enabled status" at the
Aerogear Push Server;
- The device itself throws no error;
- No problem with the OpenShift DB, as happened before.
Has any thing changed? What could it be?
Thanks
Miguel
9 years, 12 months
Re: [aerogear-dev] Problems sending notifications Cordova
by Florian Schrofner
Got the same problem here using the library for Android!
The server seems to accept the request, but nothing happens.. maybe a problem with GCM?
On 23 Apr 2014 10:19, Miguel Lemos <miguel21op(a)gmail.com> wrote:
Hi,
After a couple of weeks without testing the service, I tried to send a push
notification, but the device didn't receive nothing. I didn't change
nothing...
And:
- I get a "job submitted" answer;
- The device is still registered and is with the "enabled status" at the
Aerogear Push Server;
- The device itself throws no error;
- No problem with the OpenShift DB, as happened before.
Has any thing changed? What could it be?
Thanks
Miguel
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
9 years, 12 months
