P5EE - Applications

The applications described here are sample application ideas which might be written for demonstration of a P5EE implementation. They are intended to be:

genuinely useful (so that people start installing it and using it),
simple (so that we don't expend too much energy on a demo), and
architecturally demanding (so that we exercise and demonstrate nearly the full feature set of P5EE)

General Purpose Reporting and Data Maintenance

Concept: Install it and your database instantly/automagically becomes accessible (visible and editable) to anyone with a browser (with proper security of course). Complex reporting capabilities can be enabled with a little configuration.

P5EE Network Management System (NMS)

Concept: The NMS would be useful to monitor and administer a network.

SNMP Daemon (daemon) - Can be installed on any machine with Perl (Win, Mac, Un*x), gather data, and send alarms as per the SNMP
Network Data Collector (HTTP, SNMP, ping) (daemon) - Collects data by querying SNMP daemons, making periodic HTTP requests to web servers, and ping-ing boxes which have no other way to report their status. This daemon should interface to every existing, known daemon that reports on system status
Monitoring User Interface (Real-time event display) - Monitor alerts throughout the network (web client, but cmdline/curses/Gtk/Wxperl clients are also possible)
General reporting system (Reporting, ROLAP, and EIS) - Report on historical data stored by the data collector (web client, but cmdline/curses/Gtk/Wxperl clients are also possible)
NMS Daemon (daemon) - Daemon running as the administrative user (root) which responds to and executes remote administration requests (i.e. from the Unified Management Console). It may also implement additional data collection techniques not possible through any of the other daemons (applications installed, etc.).
Unified Management Console (OLTP) - Allows an administrator to perform management activities on any machine on which an NMS daemon is running. (web client, but cmdline/curses/Gtk/Wxperl clients are also possible)
- Create/Administer User Accounts
- Install software

This application would be a good one to start with because it stresses many systems, disparate data sources, etc. This is a typical enterprise problem. It also would have to have bullet-proof security.

The following may be relevant reference.

Sun, Java, and web systems mgmt

Mail Center

Concept: Combines web-mail (i.e. Hotmail) application and mailing list / discussion group application.

Java Pet Store Clone

Concept: A pet store application that implements all of the stuff in the J2EE Pet Store Sample Application, but does it (of course) in Perl.

Private Key Infrastructure (PKI) System

Concept: A company can issue and manage its own digital certificates.

Product and Service Customer Interface (PSCI)

Concept: The PSCI allows a firm's customers to request and pay for products and services. They can access a product/service catalog (shopping cart metaphor) and order items. Charges may be added to a customer's account by the firm such as when it provides a requested service. Customers can also check their accounts (detailed, itemized, electronic bill) and settle them (credit card processing). If there are questions on the bill, the customer can post them and the firm can post responses.

The following modules are identified.

Customer account review and settlement (OLTP)
Customer account threaded-discussion area (OLTP)
Customer-Service account management (OLTP)
Bidirectional interface to the firm's accounting system and/or practice-management system (batch/polled)
Interface to credit card processing (OLTP)
General reporting system and Executive Information System (Reporting, ROLAP, and EIS)
Service delivery data capture (OLTP)
Account management review (OLTP)

The fact that this application handles money and financial transactions should stress the security requirement pretty well.