JavaBased MW Standards and AI

1
Java-Based MWStandards and AI

• IBM and Sun have decided to champion Java-based
  standards for creating portal APIs (known as
  "portlets") - Oracle, SAP, BEA, Epicentric, HP,
  Vignette, and Plumtree are part of the Java
  Portal API initiative, which is known as Java
  Specification Request (JSR) 168
• Java Message Service (JMS) - The Java Message
  Service (JMS) API is a messaging standard that
  allows application components based on the Java 2
  Platform, Enterprise Edition (J2EE) to create,
  send, receive, and read messages. It enables
  distributed communication that is loosely
  coupled, reliable, and asynchronous
  http//java.sun.com/products/jms
• Java Data Base Connectivity (JDBC) - an API that
  provides cross-DBMS connectivity to a wide range
  of SQL databases and access to other tabular data
  sources, such as spreadsheets or flat files. With
  a JDBC technology-enabled driver, you can connect
  all corporate data even in a heterogeneous
  environment. http//java.sun.com/products/jdbc

2
(continued )

• JCA - The J2EE Connector architecture provides a
  Java technology solution to the problem of
  connectivity between the many application servers
  and today's enterprise information systems (EIS)
  http//java.sun.com/j2ee/connector
• Java Middleware - The term encompasses
  application servers like BEA WebLogic, messaging
  products like Active Software's ActiveWorks and
  Push Technologies's SpiritWAVE, and hybrid
  products that build on a DBMS legacy and add
  server-based Java object execution features
  http//www.javaworld.com/jw-03-1999/jw-03-middlewa
  re.html

3
Java MW Categories

• Database Oriented JDBC for ODBC
  http//java.sun.com/docs/books/tutorial/jdbc/basic
  s
• Interprocess applications invoke methods of
  remote Java objects, possibly on different hosts.
  RMI uses object serialization to marshal and
  unmarshal parameters and does not truncate types,
  supporting true object-oriented polymorphism
  http//java.sun.com/products/jdk/rmi
• Message-oriented, JMS for dispatching and
  receiving messages with other Java enables
  applications or applets that exist anywhere in
  the network, http//java.sun.com/products/jms/tuto
  rial/index.html

4
(Java Middleware Categories continued )

• JMS Messaging Model - JMS messages are composed
  of the following parts Header (Header fields
  contain values used by both clients and providers
  to identify and route messages), Properties
  (Properties provide an efficient mechanism for
  supporting application-defined message filtering)
  and Body (The JMS API defines several types of
  message body, which cover the majority of
  messaging styles currently in use)
  http//java.sun.com/j2ee/sdk_1.3/techdocs/api/java
  x/jms/Message.html

5
JMS Messaging Modes

• JMS point-to-point defines how a client works
  with queues how it finds them, sends messages to
  them and/or receive messages from them. Works
  best when applications need to communicate with
  one another, without delaying the target or
  source from processing tasks. JMS queue involves
  Java classes called QueueObject(provider-specific
  queue name), TemporaryQueue, QueueConnection,
  QueueReceiver, QueueSender, and QueueSession
• Pub/Sub defines how clients publish messages and
  subscribe to them from a well defined node,
  called topics

6
JMS Application Development

• A JMS application can be created and deployed as
  a single unit, or by adding JMS clients to
  existing JMS enabled applications or applets.
• Load balancing, fault tolerance, and error
  notifications provisions have to be developed
• JMS client application uses Java Naming and
  Directory Information (JNDI) to find a
  ConnectFactory object, and one or more
  destination objects http//web2.java.sun.com/j2ee/
  1.4/docs/tutorial/doc/JMS4.html

7
JMS Connectivity

• JCA provides AI technology with a standard method
  for integrating EIS with J2EE components, using a
  common API and a set of services

8
XML and Java

• J2EE provides support for XML through the Java
  API for XML Processing (JAXP) which provides the
  ability to verify, create, access, and manipulate
  XML documents from Java applications
• JAXP supports Document Object Model (DOM) as well
  as Simple API for XML (SAX), also included is
  ability to use XSLT framework for Transformation
  API (TrAX)
• Java API for XML (JAXM) enables developers to
  send and receive XML messages based on SOAP,
  http//java.sun.com/xml/tutorial_intro.html
• Java API for XML Registries (JAXR) provides a
  uniform and standard Java API for interacting
  with XML registries such as UDDI and ebXML
  Registry/Depository
• Java API for XML-based RPC (JAX-RPC) enables
  XML-based RPC functionality for web services
  interoperability

9
Java Transactional API (JTA)

• EJB is a rudimentary transactional middleware
  environment with Java components called beans
  I.e. Session Beans (transient) and Entity Beans
  (persistent), http//java.sun.com/products/jta
• XA distributed transaction management classes are
  used and controlled directly by a transaction
  manager

10
Windows XP Middleware

• Windows XP provides native middleware support
  with COM ORB, an MTS-based component transaction
  layer, and an MSMQ-based messaging layer, as an
  extension to its operating system Microsoft COM
  (Component Object Model) technology in the
  Microsoft Windows-family of Operating Systems
  enables software components to communicate. COM
  is used by developers to create re-usable
  software components, link components together to
  build applications, and take advantage of Windows
  services. The family of COM technologies includes
  COM, Distributed COM (DCOM) and ActiveX
  Controls.
• Microsoft provides COM interfaces for many
  Windows application services such as Microsoft
  Message Queuing (MSMQ) Microsoft Active Directory
  (AD) and Windows Management and Instrumentation
  (WMI).
• Microsoft recommends that developers use the .NET
  Framework rather than COM for new development,
  http//www.microsoft.com/com/default.mspx