Overall Position
Primeton EOS functions as a middleware in the overall scheme of web-based application. It sits above application server and below applications. Since application server is commonly regarded as middleware, Primeton EOS is a “middleware above middleware”.
From technical perspective, Primeton EOS attempts to achieve following goals:
1. Provide two high levels of code abstraction above programming languages, namely, composite level and workflow level. Thus allow deeper end user participation, and permit majority of developers to consistently work on a higher level of abstraction with coarse-grained components.
2. Shield away the technical details of JEE and various implementation schemes.
3. Support latest SOA-enabling standards.
The Development Environment: EOS Studio
EOS Studio hosts a suite of development tools that supports software development at three different abstraction levels:
| Atomic |
Supports basic Java coding, web page writing. EOS provides productivity tools EOS RichWeb for JSP building, EOS Report for report development. From the perspective of Primeton EOS, this level produces atomic components. |
| Composite |
Here larger components are composed with smaller components. No Java, no html, or other languages, only the Primeton EOS graphical composition. This is not a better way of generating or looking at Java code. EOS does not convert composition into Java code; EOS Server interprets composite descriptions and carries out execution at runtime. This process can be iterated indefinitely to builder ever larger and more complex components. |
| BPM |
EOS developers can build applications on workflow level. This process can also be iterated indefinitely. Work items in turn can be made of EOS composites. Workflow engine which resides in EOS Server interprets workflow programs and carries out software execution. |
Primeton EOS is developed with Eclipse. Users of other products based on Eclipse should find Primeton EOS easy to learn and convenient to use.
Runtime Environment: EOS Server
Applications developed with EOS Studio require EOS Server to run. EOS Server offers following services to applications:
Provides the operating environment for components to manipulate data and carry out business functions according to pre-specified rules.
Hosts commonly used supporting and business components.
Serves as a bridge between EOS components and low level (application server) API.
Provides necessary infrastructure for EOS Governor to carry out its control and management functions.
Provides architectural support for SOA.
EOS Server can be viewed as consisting following layers:
Connection Layer
Handles connections to and from different client types and service protocols.
Service Layer
Provides standard services, service orchestration and manages security, policies and transaction.
Implementation Layer
Implements services using all appropriate technologies, such as Java, graphical workflow representation, web Service, EJB, BPEL, etc.
Data Layer
Provides unified, technology-neutral data service, including data access, data conversion, data integration, etc..
Component Governance
Provides governance functions such as service management, system management, policy definition, access approval, and data analysis.
|
