Transcript Towards Wireless Overlay Network Architectures

Commercial Subpanel
Kick-off Briefing
Randy Katz, Berkeley, Group Leader
(Duane Adams, CMU)
Troy Crites, Sparta
Carl Kessler, IBM
Rich O’Lear, Lockheed-Martin
Sean Rice, Boeing
George Spix, Microsoft
(Bob Sproul, Sun Microsystems)
Stephen Wolff, Cisco Systems
Capt. David Gaines, USAF
1
Evolution of Enterprise Computing
Early 1990s
Automated Enterprise
– Enterprise Applications
Emerging
Now-to-Five Years Out
Real-Time, Integrated
Enterprise
Dynamic, Adaptive
Enterprise
– Real-time analysis and
closed loop feedback
Beyond Five Years Out
Adaptable, Self-Organizing,
Collaborative Supply
Networks
– Automated capabilities via
collaborating agents
(cogents)
2
Emerging Middleware Industry
System Integrators
Packaged Applications
Valued-Added Resellers
Computer Technology
Oracle
RDMS
IBM
MQ
Series
Microsoft
MSMQ
Inprise
VisiBroker
Iona
Orbix
Computer Platforms
3
Emerging Middleware Industry
Application Management
Application Integration
Push
Workflow
Message Broker
Transaction Monitor
Object-Based
Message-Based Middleware
Reliable Multicast
Tivoli
Crossworld
Backweb
Vitria
Neon, Mercator
Tuxedo
COM/DCOM, Corba, EJB
IBM MQ
Cisco
4
Middleware Functionality
•
•
•
•
•
•
Transactions
Security
Management
Internet
Fault Management
Load Balancing
• Connectivity
• Multiple Clients
• Interface
Representation
• Messaging
• Publish/Subscribe
• Java Execution
5
Elements of Middleware
• Web applications infrastructure
– Infrastructure for enabling distributed web- and Internetrelated applications
• Multi-agent systems
– Infrastructure for enabling systems of cooperating
independent agents
• Distributed object/component systems
– Infrastructure for enabling interactions among distributed
objects and components (including three major approaches—
DCOM, CORBA, and Java)
• Message-oriented middleware (MOM)
– Infrastructure for message passing among distributed
computing elements
• Distributed database applications infrastructure
– Infrastructure for distributed database applications
6
Relevent Commercial
Techologies
• Web Technologies
– DHTML, XML, DOM,
HTTP-NG
• Agent Technology
– Multiagent Systems
• Collaborative Apps
– Notes
• Distributed App Building
Blocks
– RPC & Java RMI
• Message-Oriented
Middleware (MOM)
– IBM’s MQ series, Tibco’s
“information bus,” Lotus
Notes/Domino
• Distributed Object
/Component-based
Systems
– Microsoft’s COM, COM+,
DCOM; OMG’s CORBA; and
Java (Java Beans,
Enterprise Java Beans,
Javaspaces, Jini, etc.)
• Distributed DB
Technologies
– XACT servers,
ODBC & JDBC
Areas of
Concentration 7
Architectural Framework
UI/Navigation
Tools
HTML/Scripting
Authoring
Rapid
Applications
Development
Component
Creation
Team
Development
Basic
html
Dyn
html
Forms Native
Management
Business Process
Web
Svr
Trans- Msg
actions Que
Scripting
Integrated Storage
File
Sys
Distributed
OS
Environment
Data- Mail
Other
base Store Stores
Directory
Security
Networking
Base Services
8
Emerging Generic Middleware
Architecture
Client
Enterprise
Legacy
Web Server
N
User
e
Interface t
w
o
r
Forms
k
Business Logic
XACT/DBMS
Computer Storage
N
e
t
w
o
r
k
E
v
e
n
t
s
C
o
n
n
e
c
t
o
r
s
Packaged
Applications
(SAP, Baan,
PeopleSoft)
Old Apps &
Data Sets
9
Technology Provider
Companies Visited
• BEA Systems: Corbabased Applications
Middleware + Messagebased transaction agent
• Cisco Systems:
Networking Equipment
• Lotus: Collaboration
Framework
• Lucent: Networking
Equipment
• Microsoft: Enterprise
Software Strategy
• Novell Networks:
Distributed Directory
Services
• Oracle: Distributed
Database/Applications
Development Frameworks
• Sun Microsystems:
Distributed Object
Systems: EJB, Java, Jini
• Template Software:
Enterprise Application
Integration
• Tibco: Event-Driven
Processing
• Vitria: Application
Integration Engines
13
Other Relevant Companies
• Ascent Technology, Inc.
(www.ascent.com)
– Resource planning/RT res. Alloc.,
situation assessment, res. mhmt
problems, transportation &
logistics;
• Stratfor.com
(www.stratfor.com)
– Corporate intelligence services
• Intelligent Systems
Technology, Inc.
(www.intelsystech.com)
– Framework for enterprise
process support, decision
support, self-paced instruction.;
knowledge-based approaches
• Webmethods.com
(www.webmethods.com)
– XML/e-commerce
• www.businessobjects.com
– Enterprise query, reporting, and
analysis for the web
• Tivoli Systems
(www.tivoli.com)
– “Easier for organizations
worldwide to control all of their
IT resource”
– Enterprise applications: asset
management, change management,
database management, distributed
monitoring, enterprise console
14
Other Relevant Companies
• Neon (www.neon.com)
– Enterprise application
integration for tying together
packaged, legacy, client/server,
web-based apps across different
hardware platforms
• CrossWorlds Software
(www.crossworlds.com)
– Middleware apps that integrate
third party enterprise software
products for customer service,
sales force automation, HR,
financial management
• Backweb (www.backweb.com)
– Communicate business-critical,
time sensitive information
through extended enterprise of
customers, partners, employees
• Mercator (www.tsisoft.com)
– EAI software for enterprise
applications--synchronizes
business rules and document
semantics(XML-based) among
different applications; Process
flow control, Application
adapters, Data transformation,
Messaging and transport services
• Inprise (www.inprise.com)
– Manage development, integration,
deployment, and management of
enterprise applications
• Iona (www.iona.com)
– Orbix: software infrastructure
that integrates diverse
applications (legacy, client-server,
Web-based) across enterprise
15
Technology Consumer
Companies
• Boeing
– Use of OO technologies in commercial and military
systems design
– Strong commitment to open systems architecture for C3I
• Mitre
– Use of OO technologies in Air Force systems designs
– Lessons learned
16
Distributed Systems
•
•
•
•
•
•
•
•
Collaborative Applications
Multiagent Systems
Component-Based Distributed Systems
Message-Oriented Middleware
Enterprise Application Integration
Distributed Database Application Infrastructure
Network Directories
Network Services
17
Collaborative Applications:
E.g., Lotus Notes
• Document-oriented, replicated, semistructured “database”
– Asynchronous collaboration
– Enhanced activity “awareness”
• Personal Information Management, Calendaring
and Scheduling, People Locator, Expertise
Locator, Distance Learning (“Learning Space”)
• Notes R5: improved performance, better
database semantics (e.g., transaction logging)
• Built on top of “intelligent routing of mail”
– High/medium/low priority of messages
– Mail probes/server-to-server to determine QoS
18
E.g., Lotus SameTime Server
• “Co-worker” – Awareness Services
– Knowledge discovery + knowledge in action
– Planning templates
– Profiling: finding people with certain expertise;
Infer from how he/she uses information sources
• Applications:
–
–
–
–
–
–
–
–
Intercompany/agency communications
Connect with vendors
Presentations/project reviews
Knowledge networks/experts & communities
Project management
Internal training
Conference call support
Emerging strategy session
19
Multiagent Systems
• System of autonomous computations that
cooperate or compete through messageoriented communications
• Individual agents attach to other objects to
observe, react, control
• Intelligence, ability to adapt, learn, move
usually assumed
• Decomposition of distributed apps into many,
perhaps 1000's of, autonomous computations
20
Component-Based Systems
• Delivers object-to-object, component-tocomponent, and application-to-application
interoperability among distributed systems
– Objects: software constructs with state, behavior,
identity, and well-defined interfaces
– Opaque units of independent production, acquisition, and
deployment that interact to form a functioning system
• DCE, Java RMI, COM, DCOM, CORBA, ORB’s,
object transaction servers, Enterprise Java
Beans (EJB)
• E.g., BEA Systems (M3,WebLogic), Inprise
(Visibroker), IBM (SOM object broker), Iona
Technologies, Microsoft (DCOM), Sun (EJB)
21
Alternative Object
Architectures
• Java
–
–
–
–
Network-oriented programming language for mobile code
JavaBeans: Component Model for finding/composing Java applets
Java RMI: Client/server via remote method invocation
JINI: Network “Plug and Play,” Service Discovery Service
• COM/DCOM
– Microsoft proprietary, not platform independent (Win/Win NT only)
– Building blocks for all of the major desktop applications
• CORBA
– Common Object Request Broker Architecture
– Interface Definition Language (IDL) + APIs
– Internet InterORB Protocol (IIOP) for client-server computing in
CORBA framework
22
Message-Oriented Middleware
• Delivers interoperability between applications
and middleware based on message exchange
• Includes message queuing engines (including
push, multicast, event-driven processing, etc.)
and application integration engines
• Uses broadcast techniques; senders need no
knowledge of receivers, and the receivers
need no knowledge of senders
• E.g., BEA Systems (MessageQ, Advanced
Messaging System), IBM (MQ/MQ Integrator,
Lotus Notes/Domino, Microsoft (Message
Queue Server), Tibco (Information Bus)
23
Enterprise Application
Integration
•
•
•
•
•
Data in Consistent Form
Distributing data to multiple legacy systems
Follow basic “business rules”
Business process automation
Update and enhance the functionality of existing
systems
• Manage cross-application events and functionality
24
Event-Based Programming
Message structure
Events
•
•
•
•
•
•
•
• Unsolicited
broadcasting/notification
• Broadcasting
• Anonymous
publish/subscribe
• Sophisticated filters and
rules engines
• XACT semantics are
trickier
• Underlying technology is
evolving: reliable
multicast, smart agents
Transactional Messages
Perishable Messages
Selection Criteria
Timers
Push or pull
Peeking or browsing
Message formats based
on XML
25
Event-Enabled Enterprise
• Business Events: semantically rich
Business Process: “Hire an employee”
Business Goal: global control and visibility of
business processes
• Access Control Lists (ACL) for security
• Business Metrics: info revealed to the cockpit
– e.g., order status, orders by product, orders by customer,
quote to ship, quote to bill, quote to cash time
• Stovepipe applications today
• Event-oriented message and
connectivity/wrappers and connectors
• Real-time analyzer/protocols and transformation
26
Distributed DatabaseApplication Infrastructure
• Delivers transaction management and interoperability between applications and data sources
• Transaction servers (MTS and EJB), Object /
Object-Relational, and Java-oriented Database
Management Systems, Heterogeneous DB access
• E.g., BEA Systems (Tuxedo), IBM (DB/2, Java
and JDBC), Microsoft (Transaction Server, SQL
Server, OLE DB specification), Oracle (8i)
27
Network Evolution
• VPNs as a business solution, not just for security
• Kinds of Services: Connectivity, Security,
Scalability, Reliability
• Personalized Service Vision enabled by directory
services
• Network DNA: Distributed Network Architecture
– Directory-enabled network
– Policy-driven networking
– Application-aware networking
28
Novell “Full Service Directories”
Location
Dynamic Naming
Availability
Membership
Relationships
Roles
Contact Info
Credentials
Preferences
Reality
Community
• Distributed Name
Services
• Centralized
Indexed Search
• Loose Consistency
Replication
• Fine-grained
Discretionary
Access Control
• Extensible Schema
Identity
29
BEA End-to-End Architecture
Client Diversity
JAVA App Server
Business Logic:
Process, Workflow, Rules
IIOP
Java
Desktop
BEA
Apps
OTM
EJB
Corba
EJB
Apps
Microsoft
Desktop
(COM)
Web
HTML
Network Resources
Web
Server
Servlets
BEA
Weblogic
App
HTML
Server Pages
BEA Jolt
JDBC
BEA
Apps
TP
Apps
Monitor
Apps
Enterprise JAVA APIs
Management & Security
Legacy
Systems
Databases
30
Vitria’s Middleware
Architecture
•
•
•
•
•
•
Process Feedback
Process Analysis
Process Monitoring
Process Automation
Rules Processing
Data Transport
– Reliable Messaging
– Event Messaging
– Publish/subscribe
• Data Transform
– Enterprise Integration
• Data Extract
• Analyzer
• Automater
• Communicator
– Channels
– Names/QoS (reliable,
guaranteed, XACT,
prioritized)
– Secure Channels (ACL on
channels)
• Example Connectors
– SAP R/3
– Oracle
– Custom
31
TIBCO Middleware
Architecture
Presentation
(Event Console)
Integration
(Adapters, Content
Broker)
Connectivity
(Connectors,
Message Broker)
System
Monitoring
&
Management
(Hawk)
Messaging
(ObjectBus, ETX,
Rendezvous)
32
Java 2 Enterprise Edition
Transactions
JSPs Servlets
Containers
Messaging
Mail
Connectors
EJBs
Application Programming Model
Applets
JavaBeans
Tools
Java 2 SDK, Standard Edition
CORBA
RMI
Database
Naming/Directory
• Distributed Applications built from Beans
• JSP: Java Server Pages (mixed HTML and
Java code)
33
Windows “DNA” Vision
(Digital Nervous System)
FS
SQL
Server
Replication
FS
SQL
Server
Storage+
COM+
Xchg
MTS
Common:
Transactions
Scheduling
Queuing
Xchg
MTS
IIS
MSMQ
Methods &
Events
IIS
COM+
MSMQ
Windows
Client
Transparency
Storage+
Windows
Server
34
Oracle 8i Architecture
• Message brokering
• Enterprise application
integration
• Security
– LDAP secure directory
– SSL encryption
– Application specific security
policies
– Roles in security
• Java in the DB
• Queuing in the DB
• Message broker with
transformation
• Business process coordination:
new term for workflow
• Business process modeling
• Reliable Queue w/ pub/sub
• Rules-based
• Message-broker: scalable
transformation engines
• Async messaging critical for
application integration
• Typed/structured messages
• AQ: persistent queue in the
DB, available for business
analyses
• UML graphical editor for
workflow specification
• Message types defined by
industries
• Security
35
Lucent
• Committed to JAVA-enabled
telecommunications services
• Research issues in CORBA
–
–
–
–
–
ORB Reliability: replication, persistence, message logging
ORB Performance
Real Time ORBs
ORBs for telecomms
CORBA speculative evolution/improvement
36
Boeing--Lessons Learned
• Customer acceptance of standards not taken for
granted
• COTS
–
–
–
–
Integration/migration interoperability not always smooth
Scaleable to large systems?
Risk if too leading edge--long term supplier commitment?
Leverage widespread use of components to insure reliability
• Govt & commercial standards/products not always
in sync
• Componentization/isolation has large
processing/memory impact
• Cost to keep up with rapid technology evolution
37
Mitre--Lessons Learned
• Average Developer
–
–
–
–
Difficulty with CORBA and RMI
Can apply design patterns
Can use VBand JAVA IDE (imperfectly)
Continuous training very important
• TADIL-J/Position Object
– Archeological Digs: few tools to support the reverse
engineering problem
– IDL++ human readible helps a lot
– Reverse engineering
» Interactions between objects
» 1000s of classes
» Domain objects  simulation
38
Mitre--Lessons Learned
• Wrappers
– Multiple middleware environments are likely to persist/coexistance
– Duplication of functionality
» Unify slightly different implementation of X
» Objects are not a silver bullet for interoperability
• HCI + mission experts build client models,
domain experts build enterprise models
• Observations:
– Passing context across systems is difficult!
– Mapping tool/callback handler is a needed tool particularly
important for military systems; code is often invoked from
(too) many systems
39
Maturity of Technology
• Web Application Infrastructure
– Mature except for metadata (XML rapidly evolving)
• Multi-Agent Systems
– Still immature
• Message-Oriented Middleware
– Rapidly reaching maturity
• Distributed Database Apps Infrastructure
– Mature
• Distributed Object/Component Systems
– Distributed data today; distribution of programs available in
Java and COM;distribution of process with EJB and COM+
– CORBA functionality migrating to DCOM & Java
41
Meeting DoD Requirements
• Security
– Does security in commercial systems meet DoD
requirements?
• Metadata
– Description of distributed elements to support distributed
semantic processing generally emerging, based on evolving
metadata approaches and standards
– Development of schemas/ontologies (e.g., XML DTD’s)
• Interoperation
– Support for multiple approaches working together, rather
than commitment to single approach
42
Proposed Next Steps
• Develop detailed Air Force scenario(s) in
terms of “business processes”
• Work with industry experts to understand how
existing and near term (1-5 years) middleware
technologies can support these architectures
– Dr. Arvola Chan, Tibco
– Dr. Mark Linton, Vitria
• Develop detailed presentation materials based
on design
• Formulate R&D directions
43