EventJuggler

Prerequisites

• Java Development Kit 1.7
• Recent Git client
• Recent Maven 3
• JBoss EAP 6.1.0.Alpha

Building

mvn clean install

Deploying to JBoss AS

Deploy ear (includes client and server)

mvn -pl ear jboss-as:deploy

Deploy client and server

mvn -pl client,server jboss-as:deploy

Access web application

Open http://localhost:8080/eventjuggler-client

Import and export data

Export events

curl http://localhost:8080/eventjuggler-server/events > events.json

Import events

curl -H "Content-Type: application/json" -X POST -d @events.json http://localhost:8080/eventjuggler-server/events

Sample data

There's some sample data available in sample-data. This contains the events data in json format and associated images.

To use the sample data start the JBoss EAP with '-Dej.image.dir='. For example if you have cloned eventjuggler to '/home/user/dev/eventjuggler' start JBoss EAP with:

bin/standalone.sh -Dej.image.dir=$(echo ~/dev/eventjuggler/sample-data/images)

Then import the events data with:

cd ~/dev/eventjuggler/sample-data
curl -H "Content-Type: application/json" -X POST -d @events.json http://localhost:8080/eventjuggler-server/events

Functional Tests

The testsuite contains a set of integration tests. The tests can be execute with JBoss EAP in either managed or remote mode.

Before running tests make sure that any manually installed deployables are unistalled from JBoss EAP:

mvn -pl ear jboss-as:undeploy
mvn -pl client,server jboss-as:undeploy

To run the testsuite in managed mode, run:

mvn -Pit-managed -Djboss.home=<PATH TO JBOSS EAP> clean install

To run the testsuite in remote mode, first start JBoss EAP with the EventJuggler Services sub-systems enabled, and run:

mvn -Pit-remote clean install

For some tests to pass you need to have chromedriver executable on your path.

Configuring Facebook Login

Facebook login requires three properties to be configured in your AS7 standalone.xml file.

<server xmlns="urn:jboss:domain:1.3">

    <extensions>
        ...
    </extensions>

    <system-properties>
        <property name="eventjuggler-server.FB_CLIENT_ID" value="VALUE_OF_YOUR_FACEBOOK_APP_ID"/>
        <property name="eventjuggler-server.FB_CLIENT_SECRET" value="VALUE_OF_YOUR_FACEBOOK_APP_SECRET"/>
        <property name="eventjuggler-server.FB_RETURN_URL" value="http://localhost:8080/eventjuggler-server/facebook"/>
        ...
    </system-properties>
    ...
</server>

In order to get Facebook App ID, and App Secret, go to https://developers.facebook.com/apps, and use Create New Application button.

For App Name type some name i.e. EventJuggler, leave App Namespace empty, and leave Web Hosting unchecked.

Complete the wizard.

After your application is created select how your app integrates with Facebook in the bottom of the screen. Choose the first option - Website with Facebook Login.

Type in the Site URL: http://localhost:8080/eventjuggler-server/facebook

That's it.

You now have your application, and an App ID, App Secret, and you have secured your app to only communicate with localhost:8080 ...

Replace VALUE_OF_YOUR_FACEBOOK_APP_ID, and VALUE_OF_YOUR_FACEBOOK_APP_SECRET with actual values.

Configuring Twitter Login

Twitter login requires three properties to be configured in your AS7 standalone.xml file.

<server xmlns="urn:jboss:domain:1.3">
    <extensions>
        ...
    </extensions>

    <system-properties>
        <property name="eventjuggler-server.TWIT_CLIENT_ID" value="VALUE_OF_YOUR_TWITTER_CONSUMER_KEY"/>
        <property name="eventjuggler-server.TWIT_CLIENT_SECRET" value="VALUE_OF_YOUR_TWITTER_CONSUMER_SECRET"/>
        <property name="eventjuggler-server.TWIT_RETURN_URL" value="http://localhost:8080/eventjuggler-server/twitter"/>
        ...
    </system-properties>
    ...
</server>

In order to get Twitter Consumer Key, and Consumer Secret, go to https://dev.twitter.com/apps, and use Create New Application button.

For Name type some globally unique name i.e. EventJuglerDemo-007. Then type a short Description. For Website enter something that looks like a top level domain - i.e. http://www.eventjuggler.org. For Callback URL enter some fake URL i.e. http://www.eventjuggler.org/twitter. Leave the rest empty.

Submit the form. That's it.

You now have your application, and a Consumer Key, and Consumer Secret.

Replace VALUE_OF_YOUR_TWITTER_CONSUMER_KEY, and VALUE_OF_YOUR_TWITTER_CONSUMER_SECRET with actual values.