SUMMARY
To
develop a software product, Enterprise Business Server, based on the EPC-IS
Specification Document by EPCglobal standards body. Its function is to accept
tag data from the Analyzer), convert them into high-level business events based
on user defined rules, store the data for historical monitoring, and provide
means to integrate the data to back-end systems.
TECHNOLOGIES
1. Eclipse
3.2 IDE for development, debugging.
2. JBoss-4.0.4.GA
as the web server.
3. SVN
version control for versioning and code delivery.
4. Junit
for unit, integration and system testing.
5. Programming
Language: Java (jdk 1.5)
6. Tapestry
as Web application framework.
7. Transport
Protocols: TCP, RMI, JMS, HTTP, File system, Web Services/SOAP
8. XML
Files are used for persisting the Events and Rules created by user.
9. EJB
Session Beans for implementing Event Transformation Engine.
10. Hibernate
is used as the object/relational persistence.
11. MySQL
is used as the database at the time of development.
PROJECTS IMPLEMENTATION DETAILS
Develop
the product as a J2EE application consisting of web module and EJB module that
runs in a J2EE complaint Application Server. The Enterprise Business Server
consists of the following components as shown in Figure 1.
Figure 1
Event
Transformation Engine
The
Event Transformation Engine converts tag events received from Analyzer into
high-level business events that a user can understand, based on User defined
rules. A rule includes two informations, on what conditions need to trigger a
rule and information on how to create a high-level business event.
Repository
The
repository is a database driven storage mechanism for business events. The
output of the Event Transformation Engine is fed to the repository for
historical monitoring .The repository stores dynamic data in the form of
business events, and static data is stored in the form of master data. We made
use of Hibernate technology for the database persistence mechanism.
Console
Console
provides the user interface that helps the users to specify business rules and
to interact with the system. Rules and transformations are created by the
console and are stored in the form of XML data. Console also helps the user to
create static master data and store it into the database. This master data is
provided as the inputs while creating the rules and transformations.
Develop
an Event Transformation Engine that receives ECReports from Analyzer and
converts them to Business Events. An RMI listener is registered as a subscriber
to an ECSpec defined in the Analyzer. Whenever a report is generated by the
Analyzer engine, it publishes the report to the RMI Notification listener. For
each report received from the Analyzer, it creates an event of type Analyzer
Event and transforms it to a business event based on the user defined rule. For
example, a rule can specify that if the tag events are from the packaging area,
and then create an Aggregation Event with all the pallet tags and case tag that
were read. It publishes the generated events to the interested publishers. This
system supports TCP, HTTP, File, and JMS for the publishers. Transformation
Engine is implemented using EJB Session Beans.
Web Application
The main purpose of the Web Application is to create Rules
for generating Business Events. Figure 2 shows the page to create a scenario
(Rule).User can select an event for a rule. When the Event Transformation
Engine is triggered from this selected event, it creates a business event based
on this rule and publishes to the Subscriber. Web Application is developed
using Tapestry
Figure 2
If the
user wants to create a new source event, use the Mange button and it shows the
page shown in Figure 3.
Figure 3
Figure 4
As
shown in Figure 4, User can create custom Event based on any of the base type
events shown in dropdown box.
Figure 5
Figure
5 shows a Scenario (Rule) created in the system. Whenever the system receives a
report from the Analyzer that matches the given constraints, it creates a
Shipping Event using the informations present in the Analyzer report and
publishes it to the JMS Publisher.