- •Project consultation pointing to relevant chapters
- •Annotation
- •Аннотация
- •Түйіндеме
- •1.5Final Goals
- •2Application architecture
- •2.1Enterprise JavaBeans (ejb)
- •2.2Bpm Process Engine
- •2.2.1Introduction
- •2.2.2What is bpmn?
- •2.2.3Bpmn 2.0 constructs Custom extensions
- •2.2.4Engine api
- •2.2.5Business archives
- •2.2.6Versioning of process definitions
- •2.2.7Generating a process diagram
- •2.3Integrating bpm into project
- •2.4Web Services
- •2.5Application Design
- •3Database Architecture
- •3.1Dbms
- •3.2Schemas Design
- •3.3Data Model Overview Table «Catalog» - Catalog of subjects which would be available in a faculty on certain term with some number of credits
- •Table «Class» - a set of lessons which will be tough by some instructor
- •Table «Class_Enroll» - Enroll for a class
- •Table «Class_Grades» - Grades of student for some class
- •Table «Student_Schedule» - Student Schedule of classes
- •Table «Subject» - Some area of study in education
- •Table «Term» - Special Period of time, which has name, start date and end date
- •3.4Activiti Database tables
- •Benefits
- •4Network and Servers
- •4.1Design
- •Benefits
- •5Bpmn usage in Middleware
- •6Conclusion
- •7References
2.4Web Services
What are Web Services?
Web services are application components
Web services communicate using open protocols
Web services are self-contained and self-describing
Web services can be discovered using UDDI
Web services can be used by other applications
XML is the basis for Web services
The basic Web services platform is XML + HTTP.
XML provides a language which can be used between different platforms and programming languages and still express complex messages and functions.
The HTTP protocol is the most used Internet protocol. In the Figure 2.30 shows SOA structure which web services platform elements are:
SOAP (Simple Object Access Protocol)
UDDI (Universal Description, Discovery and Integration)
WSDL (Web Services Description Language)
Figure 2.30 – SOA structure
Web Services take Web-applications to the Next Level
By using Web services, your application can publish its function or message to the rest of the world.
Web services use XML to code and to decode data, and SOAP to transport it (using open protocols).
With Web services, your accounting department's Win 2k server's billing system can connect with your IT supplier's UNIX server.
Web Services have Two Types of Uses
Reusable application-components.
There are things applications need very often. So why make these over and over again?
Web services can offer application-components like: currency conversion, weather reports, or even language translation as services.
Connect existing software.
Web services can help to solve the interoperability problem by giving different applications a way to link their data.
With Web services you can exchange data between different applications and different platforms.
What is SOAP?
SOAP is an XML-based protocol to let applications exchange information over HTTP.
Or more simple: SOAP is a protocol for accessing a Web Service.
SOAP stands for Simple Object Access Protocol
SOAP is a communication protocol
SOAP is a format for sending messages
SOAP is designed to communicate via Internet
SOAP is platform independent
SOAP is language independent
SOAP is based on XML
SOAP is simple and extensible
SOAP allows you to get around firewalls
SOAP is a W3C standard
What is WSDL?
WSDL is an XML-based language for locating and describing Web services.
WSDL stands for Web Services Description Language
WSDL is based on XML
WSDL is used to describe Web services
WSDL is used to locate Web services
WSDL is a W3C standard
What is UDDI?
UDDI is a directory service where companies can register and search for Web services.
UDDI stands for Universal Description, Discovery and Integration
UDDI is a directory for storing information about web services
UDDI is a directory of web service interfaces described by WSDL
UDDI communicates via SOAP
UDDI is built into the Microsoft .NET platform
2.5Application Design
Application is a middle ware which is written using Java EE 5 standards and EJB 3.0 technology. Includes JPA(Java Persistence API). Has Modules:
Security Module
BPM Engine Module
Provides WS(Web Services), RS(Restful Services) and EJB Local Interfaces.
May have such resources as Database and JMS(Java Messaging Service).
Connects to resources using JCA(Java Connector Adapters).
Figure 2.32 shows component diagram of how components are wired together to form larger components. They are used to illustrate the structure of arbitrarily complex systems.
Benefits of design are:
In distributed pattern
In standardized pattern to technologies
Has scalable services
Has independent security module
Has independent BPM engine module
In stability and reliability
Figure 2.31- Application Design
Figure 2.32 – Component Diagram
