|
1
|
|
|
2
|
|
|
3
|
- Summary of Previous Session
|
|
4
|
- Application Servers for Enhanced HTML (traditional)
- a.k.a., Page-Based Application Servers
- Mostly Used to Support Standalone Web Applications
- New Generation Page-Based Script-Oriented App. Servers
- First Generation Extensions (e.g., Microsoft IIS with COM+/ASP)
- Servlet/JSP Environments
- XSP Environment
- Can now be used as front-end to enterprise applications
- Hybrid development environments
- Distributed Object Computing Platforms
- Provide an infrastructure for distributed communications enabling
- Still need to merge traditional web-oriented computing with object
computing
- Object Management Architectures
- DOC Platform + APIs to reusable services and facilities
- OMAs + Component Models -> J2EE, CCM, DNA
- MDAs with Web Services- and Channels/B2Bi-Enabling services
|
|
5
|
|
|
6
|
- .Net CLR Interoperability Support
|
|
7
|
- Calling a COM Component from .Net
|
|
8
|
|
|
9
|
- Calling a .Net Component from COM
|
|
10
|
|
|
11
|
|
|
12
|
- Calling Native Win32 DLLs
|
|
13
|
- Web-Tier Horizontal Migration
|
|
14
|
- Web-Tier Horizontal Migration
- (continued)
|
|
15
|
- Middle-Tier Horizontal Migration
|
|
16
|
- Middle-Tier Horizontal Migration
- (continued)
|
|
17
|
- Standard vs. Custom Managed Wrappers
|
|
18
|
- .Net PetShop Logical Architecture
|
|
19
|
- .Net PetShop Physical Deployment Diagram
|
|
20
|
- .Net PetShop 3.0 Application Architecture
|
|
21
|
|
|
22
|
- See http://www.topxml.com/java/articles/javaxml/3.asp
- Java Soap library
- KVM kSOAP (http://ksoap.enhydra.org/)
- Environment Needed to Run XML-Based Java Applications
- Java KVM for J2ME
- Java Kilobyte Virtual Machine (KVM) designed to operate with as little
as 160 to 512 KB of memory
- NanoXML
- Lightweight DOM-style XML parser and document generator
- Palm OS Emulator (POSE)
- Software that emulates the hardware of different Palm devices (Palm
III, Vx, VII, etc.)
- Can be used as a unit testing platform
- Also See http://webdev.apl.jhu.edu/~rbe/kvm/
|
|
23
|
- Beaming contact information from a custom Palm database
|
|
24
|
|
|
25
|
- XML and JavaBeans integration
- JavaBeans and EJB state persistence using XML
- XML serialization for Java (e.g., Koala, etc.)
- XML Application Services as JavaBeans/EJBs
- e.g., Parsing, rendering, querying, messaging beans
|
|
26
|
- Towards XML Model Based Computing
|
|
27
|
- EJB Component/Programming Model
|
|
28
|
- Entity Beans in EJB Application Servers
|
|
29
|
- Session Beans
- in EJB Application Servers
|
|
30
|
|
|
31
|
- Anatomy of a CMP Bean
- (continued)
|
|
32
|
- EJB Generation
- (e.g., IBM EJBMaker, BEA WebGain Studio)
|
|
33
|
- Container Managed Persistence Architecture
|
|
34
|
- Bean Managed Persistence Architecture
|
|
35
|
- EJB Development Approach 1
|
|
36
|
- EJB Development Approach #2:
- Handcode the Bean and Descriptor
|
|
37
|
- EJB Development Approach #3:
- Graphical Bean and Descriptor Generator
|
|
38
|
- Four Patterns for Managing Persistence
|
|
39
|
- Container-Managed Entity Beans + Session Beans
|
|
40
|
- Beans-Managed Entity Beans + Session Beans
|
|
41
|
|
|
42
|
|
|
43
|
- Performance Characteristics
|
|
44
|
- Performance Characteristics
- (continued)
|
|
45
|
- SQL Statements v.s. Finder Methods
|
|
46
|
|
|
47
|
|
|
48
|
- Both separate data from rendition/presentation info
- Similar languages
- DBMSs: Forms and Reporting, DDL, DQL, DCL
- XML: XSL, XQL, and processing instructions
- No DML in XML
- XML is paired with a scripting or programming language
- Validation capabilities
- DBMSs: datatyping, relationship constraints
- XML: data type validity and semantic consistency checks
- XML can handle data too complex for some databases
- XML interchangeable form of data vs. multidatabases
|
|
49
|
- Serializing Java objects into XML using reflection
- Sims Computing lightweight XML messaging framework (based on JMS)
- xmlBlaster Message Oriented Middleware project
- MOM platform that uses XML for the message meta-data and quality of
service information
- Messages can be filtered using XPath expressions which match against
the XML header document
- Developing MOM applications using the SAX/DOM APIs
|
|
50
|
|
|
51
|
|
|
52
|
|
|
53
|
|
|
54
|
- B2Bi is based on the transformation and routing of XML documents
- B2Bi patterns:
- Direct Application Integration
- Data Exchange
- Closed Process Integration
- Open Process Integration
- Existing Frameworks:
- WebMethods B2Bi EAI framework
- MQSI (MQSeries Integrator)
- See STP/T+1 in Sub-Topic 2/3 Presentations
|
|
55
|
|
|
56
|
- Ability to interact directly with application APIs
- Integration brokers with built-in support for adapters, transformations,
and asynchronous content0based routing
- Same Integration Broker on both ends
- Secure transport, component authentification, and user authorizations
- Federated security control
|
|
57
|
|
|
58
|
- Translation of data native to an application into a common document
format, and transmission via a gateway
- No constraints on the presence of Integration Brokers
- B2B transactions enabled via a common data exchange format
|
|
59
|
|
|
60
|
- Principal participant responsible for managing processes
- Other participants are secondary, and do not have visibility into the
entire process
- Requires the introduction of business process integration (BPI) services
- B2Bi product offerings are beginning to incorporate BPI as an essential
component
- In this case, B2Bi enables the integration of logical business process
elements expressed as activities rather than data
|
|
61
|
|
|
62
|
- Introduces the notion of shared processes rather than operating from a
centralized master process manager model
- Each participant is actively managing business processes within its
domain
- The BPI layer must support fine-grained control of managed processes
|
|
63
|
- XML complements EAI technology
- Powerful meta language
- Simplicity
- Separation of content and presentation format
- Common open standard
- EAI Frameworks must address the limitations of XML
- Limited Semantics Interpretation
- Lack of data transformation facilities
- Inefficiencies of text-based documents
- Absence of component-based routing
|
|
64
|
|
|
65
|
|
|
66
|
|
|
67
|
|
|
68
|
|
|
69
|
|
|
70
|
|
|
71
|
|
|
72
|
- XML-RPC
- SOAP, DIME, and ROPE
- UDDI, and DISCO
- WSDL
|
Notes