Skip to content
Acra reporting library endpoint
Java HTML JavaScript Other
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
JAcraEAR
JAcraEJB
JAcraRestWAR
JAcraSoapWAR
JAcraSubmitWAR
JAcraUiWAR
.gitignore
COPYING
README.md
pom.xml
release.sh

README.md

JAcra: an Acra reporting library endpoint

JAcra is a powerful backend for Acra library providing various notification mechanisms as well as build-in analytics. JAcra is a pure Java EE 7 application designed to be run on a Wildfly Application Server. You can take a look at the UI here.

Notable features are:

  • JSON and FORM data formats support see
  • Built-in powerful SQL-like search engine
  • Application server security support
  • Actions audit support
  • Optional E-Mail notifications (either instant, hourly or daily)
  • Optional JMS notifications
  • Multicast support through submitter groups
  • JMX monitoring support.

Installation guideline

JAcra installation requires Java EE application servers configuration experience. Configuring ones for the first time may lead to a headache, dissociative disorder, sudden fit of anger and massive environmental destructions.

Installation requirements

Mandatory requirements are:

  • Java EE 7 Full Profile application server (Wildfly 8+ is officially supported, Glassfish 4+ is officially unsupported)
  • Pre-configured security realm/domain named 'jacra'
  • Pre-configured data source named 'java:/persistence/JAcraPersistence' with schema applied

Requirements for E-Mail notifications support:

  • An SMTP server (either self-hosted or a public one)
  • An E-Mail session object named 'java:/mail/jacra/session'
  • System property 'me.jtalk.jacra.notification.email.enabled' set to 'true'
  • A Session object name can be configured through the 'me.jtalk.jacra.email.session.address' property

Requirements for JMS notifications support:

  • A JMS queue named 'java:/jms/jacra/NotificationQueue'.
  • A JMS connection factory named 'java:/jms/jacra/NotificationFactory'
  • System property 'me.jtalk.jacra.notification.jms.enabled' set to 'true'
  • JMS objects names can be configured through both the 'me.jtalk.jacra.notification.jms.queue.address' and the 'me.jtalk.jacra.notification.jms.factory.address' properties.

Contribution guidelines

  • Pull requests are welcome
  • Tabs only, braces everywhere, EJB is fun!

Contacts

Feel free to contact us regarding project setup, usage, development workflow and contribution.

You can’t perform that action at this time.