ServiceOriented AI

1
Service-Oriented AI

• Increasingly desired and being advanced in view
  of web services
• May be more invasive and costly
• Integration of IOAI BPIOAI
• Existing mechanisms of frameworks, transactions,
  and distributed objects.
• Web services models from Microsoft (.NET)

2
(continued .)

• IBM Websphere
• http//www-06.ibm.com/software/websphere/
• BEA Service Infrastructure http//www.bea.com/fram
  ework.jsp?CNThomepage_main.jspFP/content
• HP SOA Manager (HP OpenView Life Cycle Management
  for Web Services). http//devresource.hp.com/drc/r
  esources/lcm4ws_overview/index.jsp
• SUN SOA SODA http//www.sun.com/software/whitepape
  rs/webservices/soa_ready.pdf
• Leveraging the Internet for Integration

3
Application Services

• Classically viewed as subroutines or methods
• Invoking services remotely
• Sharing common services
• Web-based services can benefit from common
  standards
• Changes required in systems built prior to
  emergence of web services/SOAI.
• Integration strategies and approaches pp. 82-83
  http//www.sun.com/software/whitepapers/webservice
  s/soa_ready.pdf

4
Web Services

• A collection of protocols and standards used for
  exchanging data between applications via the
  Internet accessible interfaces, in a manner
  similar to inter-process communication on a
  single computer
• Example, page 84
• Applications may conceivably be simply composed
  by interfacing to the Internet-connected
  services, in small (incremental) low risk steps
• Publishing and marketing services

5
Web Services Description Language (WSDL
Whuz-Duhl)

• WSDL is an XML format published for describing
  web services on the lines of previously used IDL
  in COM/CORBA for client-server interactions
• WSDL works with network end-points (ports)
  abstractions
• Information flows in the form of messages between
  applications, bound by concrete protocols for
  each port.

6
Rationalizing SOAI

• IO may serve adequately many inter and intra
  enterprise applications
• Desirable if redundant services exist across
  enterprise applications, and a service once
  created is made available across many
  applications
• May be necessary if information and services are
  tightly coupled.

7
Considering SOAI Solutions

• Event Driven event driven movement of
  information

8
(Continued )

• Composite applications services from many
  applications aggregating into a single
  application, composing components from existing
  components (appears most promising)

9
(Continued )

• Autonomous-Distributed tightly coupled as if a
  single application

10
Missing Pieces

• Leveraging user interfaces Web services User
  Interface Initiative (WSUI)
• Security (Security Assertion Markup Language
  SAML) http//www.oasis-open.org/specs/index.php
• XML Key Management Specifications (XKMS), based
  on Public Key Infrastructure (PKI)
• http//www.oasis-open.org/cover/xkms.html
• http//www.galeit.com/pki.htm