IBM
eBusiness – Past and Future
Anders Bonde, Senior IT Architect
© 2006 IBM Corporation
IBM
Anders Bonde
 1982
Master of Science (Math. & Physics)
 1982-85
Teacher (“Gymnasium”, University etc)
 1985-92
IBM Denmark
– Co-Author of IBM Redbook (1990)
• “Object-oriented design - A preliminary approach”.
 1992-2004
The Danish Object Company
– Involved in approx. 100 projects (1992-2004)
• My role: Mentor, teacher, architect, designer, project manager and programmer
 2004-2006 (July) Mærsk Data (now IBM)
– Manager IBM APMM eCommerce
• 50 people in DK & 20 people in India
– My people: Project mgrs, architects, developers, integrators and testers
 2006 (aug)-now IBM Global Business Solutions
– Business Manager / Senior IT Architect
• APM, Arla, Jyske Bank, Skat etc
© 2003 IBM Corporation
IBM
Agenda
 The Past: 4 eBusiness Case-stories
– Jyske Netbank Erhverv
– CRMDirect
– Maerskline.com
– Stockholm Congestion Tax System
 The Future: Patterns & Reference Architecture
– IBM Patterns for eBusiness
– IBM eBusiness Reference Architecture
– SOA – Service Oriented Architecture
© 2003 IBM Corporation
IBM
Warning: I talk ‘Technish’
 eBusiness/eCommerce is not ONLY about technology
– But it is ALSO about technology
• “As simple as possible, but not simpler” (*)
 And I will talk about technology
– But I also understand the (e)Business!
You are welcome to challenge me!
(*) Einstein about Physics
© 2003 IBM Corporation
IBM APMM Account
Requirements - it’s not easy :o)
You know this?
5
IBM APMM Account
The traditional IT development process
Business
This is
what
I want
IT
Disjoint, Slow
Requirement
Analysis
breakdown
requirements
• round
• hollow
• air inside
• elongated. Length> height
6
This is
what I’ll get
Design to
requirements
• round
• with a hole
• air inside
• width > height
IBM
The Past: “Real life” eBusiness Case-stories
Anders Bonde
© 2006 IBM Corporation
Jyske Netbank
Erhverv
The Danish Object Company A/S
Anagrammer
November 2001
Jyske Netbank Erhverv
 Officebank system for enterprise customers.


State-of-the-art
100% Java (signed applet runs in browsers, also “offline”)
 Main features



Payment-system (!!!) (incl. Euro support)
Integration with leading ERP systems
Advanced reporting facilities.
 “FIT” Client technology


“Look-and-feel” of client/server,
Maintained like a mainframe application.
The Danish Object Company A/S
Anagrammer
November 2001
Jyske Netbank Erhverv
 New customer: Danish Government
 Unique Selling Points:



Ease-of-use
Performance
Price!
 Handle all payments for next 5 years




30 million transactions per year!
1000 billion DKK (125 billion EUR) per year
2000 Public Departments
10000++ users
The Danish Object Company A/S
Anagrammer
November 2001
The Danish Object Company A/S
Anagrammer
November 2001
The Danish Object Company A/S
Anagrammer
November 2001
Jyske Netbank Erhverv Arkitektur
”http”
(CBT)
Internet Server (S/390)
JNE Appl.
JDBC
Java
object
C / CGI
Local Database (Access)
BackOffice
programmer
DB2
SQL
Database Server (S/390)
The Danish Object Company A/S
COBOL
Application Server (S/390)
Anagrammer
November 2001
The Danish Object Company A/S
Anagrammer
November 2001
What is CRMDirect
• Internet-based CRM concept
– Customer Relationship Management
• Everything ”In a box”
– CRM, Hosting, Security, Backup etc
– Optional: Partner data
• Integrated with intelligent data
– Market- & Credit information
• Købmandsstandens OplysningsBureau, DK
• CreditInform, Norway
– Or your data ...
CustomerWare 2002
The Danish Object Company A/S
Anagrammer
November 2001
CRM Vision
• ”As simple as possible, but not simpler”
– CRM functionality = Pragmatic
• ”Best-of-breed”
– Technology = No compromises!
• THE CRM solution for
The Mobile Organisation
CustomerWare 2002
Architecture II
WAP
https/
XML
Internet Server (WebSphere)
Client Appl.
Java
object
ERP
“ServLet’s”
IP
Server Appl.
EJB
DB2
Database Server
CustomerWare 2002
SQL
Application Server
IBM
Anders Bonde
© 2003 IBM Corporation
IBM
A Container is not just a container :o)
© 2003 IBM Corporation
IBM
© 2003 IBM Corporation
Stockholm Congestion Tax
System
Europe
May 2-5, 2006 Madrid, Spain
© Copyright IBM Corporation 2006
The Stockholm Project
A local government project to reduce congestion,
based on three initiatives.
2 – Test congestion taxation
1 – Improve public transport
Europe
May 2-5, 2006 Madrid, Spain
3 – Provide more parking
© Copyright IBM
Corporation 2006
Congestion Tax Objectives
 Reduce traffic by 10-15%
 Increase average speed
 Reduce pollution
 Improve environment
 Improve public
transportation
Europe
May 2-5, 2006 Madrid, Spain
© Copyright IBM
Corporation 2006
Congestion Tax Solution
Overview
 Variable tax scheme
 Continues flow
 Alternative ways of
identification
User channels: Internet,
Pressbyrån, 7-Eleven,
Call Centre
Technology:
Q-free Roadside
Transponder
Europe
May 2-5, 2006 Madrid, Spain
IBM Data Centre
IBM OCR
Payment
channels
© Copyright IBM
Corporation 2006
Challenges
 Negative public opinion
 Demanding SLA
 High visibility
 Integrity problems
 24 hours cycle
 Volume uncertainty





Passages
Images stored
Payments
Call center calls
OBU distribution
Europe
May 2-5, 2006 Madrid, Spain
© Copyright IBM
Corporation 2006
Stockholm Congestion Tax
Results
 Uninterrupted operation every day
 Traffic reduced by 25%
 Public transportation passengers increased by 40,000
per day
 Congestion during peak hours dramatically reduced
 No major re-routed traffic problems
 Average speed of buses increased
Europe
May 2-5, 2006 Madrid, Spain
© Copyright IBM
Corporation 2006
99,99% vehicle identification
Europe
May 2-5, 2006 Madrid, Spain
© Copyright IBM
Corporation 2006
IBM
The future: Patterns and Reference Architectures
Anders Bonde
© 2006 IBM Corporation
© 2006 IBM Corporation
© 2006 IBM Corporation
© 2006 IBM Corporation
© 2006 IBM Corporation
© 2006 IBM Corporation
© 2006 IBM Corporation
© 2006 IBM Corporation
© 2006 IBM Corporation
e-business Reference
Architecture V2.3
An Introduction
|
© Copyright IBM Corporation 2003 All Rights Reserved
Enterprise Architecture & Technology Center of Excellence
What is ESS e-business Reference Architecture?


The Enterprise Solution Structure has
reviewed and approved several reference
architectures. The e-business reference
architecture (ebRA) is its latest addition.
ebRA is a very prescriptive reference
architecture that addresses the e-business
solutions architecture space.
Business View
User /
Information
View
Functional
View
Integration
View
Data View

ebRA is based on the Architecture Blueprint
which identifies 9 views that any
architecture should satisfy.
Content Management View
Operational View

ebRA is designed to be adaptive such that it
meets current and future needs of a diverse
user population and adapts to changing
requirements
Security View
Systems Management View
© Copyright IBM Corporation 2003 All Rights Reserved
What is
Enterprise Architecture & Technology Center of Excellence
Across all
For any
Industries
eit?
business
solution
Financial Services Solutions
Wealth management
Online Brokerage
Claims Processing
……
Customer Self Service
Customer Loyalty
eCRM
Industrial Sector Solutions
Automotive solutions
Manufacturing solutions
Petrochemical solutions
……
Distribution Sector Solutions
Retail solutions
CPG solutions
Online Gaming
……
Telco and Media Solutions
Digital Asset Management
Online booking
E-Marketplaces
Supply Chain Management
E-Procurement
Provides a
strong and
reliable
foundation
Sell and Support
Solutions
Buy and Supply
Solutions
Industry
Solutions
Employee Self Service
Enterprise Portals
Knowledge Management
Enterprise
Solutions
First of a kind solutions
Technology Refresh
Web enabling legacy systems
Custom SI
Solutions
e-business
End-to-End
Architecture
……
Public Sector Solutions
E-government
Federal government solutions
State government solutions
……
© Copyright IBM Corporation 2003 All Rights Reserved
Enterprise Architecture & Technology Center of Excellence
Work Product Traceability Diagram
Business
Context Diagram
(part of Business
Environment WP)
System
Context
Diagram
Customer Wants &
Needs
Provides input to
Candidate Asset List
Define the
scope of
User Profiles
Help
define
Define the
scope of
Help
define
Use Case Model
Security & Privacy
Policy
Architectural
Decisions
Are mapped to
the Component
Interaction
Diagram
Standards
Architectural
Template
Architecture
Overview Diagram
Defines
relationships
between
Components
Viability
Assessment
Service Level
Characteristic Analysis
Reference Architecture
Current IT Environment
Help provide the
structure to
Components
Component
Model
Make changes
to
Make changes
to
Drive
Drive
Non-Functional
Requirements
Are the
primary inputs
for
Help define
Defines
Nodes
Help
Define
Operational
Model
Security & Privacy
Requirements
Drive
Help establish
SLAs for
nodes
Performance
Model
Help define
packages
Help
Define
Help define
packages
Security
Architecture
Principles
Drive
Deployment
Unit
Security
Architecture
Help define
packages
Help
Define
Change
Cases
Make changes
to
Make changes
to
Business Domain WP
Application Domain WP
Architecture Domain WP
Security Domain WP
Aa Engagement Specific WP
© Copyright IBM Corporation 2003 All Rights Reserved
Enterprise Architecture & Technology Center of Excellence
The Business Environment contains the Business Context Diagram which documents the identity
of the enterprise and its interactions with other entities in its environment
 The e-business
reference architecture
provides the ability:



For customers to
perform their own
transactions via the
Internet
For enterprise
employees to interact
via the enterprise’s
Intranet
To conduct business
amongst companies
via an extranet or the
public Internet
© Copyright IBM Corporation 2003 All Rights Reserved
Enterprise Architecture & Technology Center of Excellence
The System Context highlights important characteristics of the system events and
data the system receives and generates

ebRA identifies and describes
the following with their
connectivity considerations:







Pervasive Computing Device
Browser-based Internet Client
Browser-based Intranet Client
Legacy Systems and
Databases
Web Services Directories
External Entities
Also included is a table that
identifies the flows between the
system the items above. The
table identifies:




Entities involved with the flow
Definitions of inputs and
outputs
Volume Information
Access Times
Pervasive
Computing
Devices
External Entities
Customized
Requests for
XML documents
(Business
information made
delivered to
Partners,
over wireless
external systems
Vendors,
ASPs)
protocols
over HTTP or
HTTPS
XML documents
returned from
partner site/
application over
HTTP or HTTPS
Customized
presentation
delivered to client
over wireless
protocols
Browser-based
Internet Client
Request for informational
and business data made
over HTTP or HTTPS
HTML and XML
documents, audio, video,
and image files delivered
over HTTP or HTTPS
Request for
information
made over
HTTP or HTTPS
Browser-based
Intranet Client
e-business
Application
Request for information
about location and
binding details of
services over TCP/IP
Web Services
Directories
Information about location
and binding details of
services returned from
Directory over TCP/IP
Requested data
or transaction
results returned
over TCP/IP
Information
delivered to a full
function client
desktop over HTTP
or HTTPS
Request for data or
transactions over
TCP/IP
Legacy Systems
and Databases
© Copyright IBM Corporation 2003 All Rights Reserved
Enterprise Architecture & Technology Center of Excellence
The Use Case Model describes the functional characteristics of the system
01-020
U
s
e
C
a
s
e
N
u
m
b
e
r
:
S
u
b
j
e
c
t
A
r
e
a
:
B
u
s
i
n
e
s
s
E
v
e
n
t
:
N
a
m
e
:
S
c
e
n
a
r
i
o
N
u
m
b
e
r
O
v
e
r
v
i
e
w
:
U
s
e
C
a
s
e
N
u
m
b
e
r
P
r
e
c
o
n
d
i
t
i
o
n
s
:
T
e
r
m
i
n
a
t
i
o
n
O
u
t
c
o
m
e
D
e
s
c
r
i
p
t
i
o
n
:
S
c
e
n
a
r
i
o
N
o
t
e
s
A
s
s
o
c
i
a
t
i
o
n
s
:
S
c
e
n
a
r
i
o
D
e
s
c
r
i
b
p
t
i
o
n
T
r
a
c
e
a
b
l
e
T
o
:
U
s
a
b
i
l
i
t
y
I
n
d
e
x
:
T
e
r
m
i
n
a
t
i
o
n
O
u
t
c
o
m
e
:
I
n
p
u
t
s
:
D
e
c
i
s
i
o
n
T
a
b
l
e
O
u
t
p
u
t
s
:x
x
x
x
x
x
x
x
x
x
x
xT
T
F
N
o
t
e
s
: x
o
n
d
i
t
i
o
n
s
A
f
f
e
c
t
i
n
g
:
x
x
x
x
x
x
x
x
x
x
xF
F
F C
T
T
x
x
x
x
x
x
x
x
x
x
x
xF
x
x
x
x
x
x
x
x
x
x
x
x
D
e
c
i
s
i
o
n
T
a
b
l
e
x
x
x
x
x
x
x
x
x
x
x
xT
T
F
x
x
x
x
x
x
x
x
x
x
x
xF
F
F
T
T
x
x
x
x
x
x
x
x
x
x
x
xF
x
x
x
x
x
x
x
x
x
x
x
x



T
T
F
l
o
w
o
f
E
v
e
n
t
s
A
c
t
o
r
N
a
m
e
:
D
e
s
c
r
i
p
t
i
o
n
:
S
t
a
t
u
s
:
S
u
b
c
l
a
s
s
:
S
u
p
e
r
c
l
a
s
s
:
A
s
s
o
c
i
a
t
i
o
n
s
:
P
r
o
b
l
e
m
D
o
m
a
i
n
C
o
n
c
e
p
t
s
S
y
s
t
e
m
S
e
q
u
e
n
c
e
D
i
a
g
r
a
m
S
T
E
P
A
/
S
A
C
T
I
O
N D
A
T
AV
A
L
I
D
A
T
I
O
N
N
O
T
E
S
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x x
x
x
x
x
x
x
x
x
x
xx
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x x
x
x
x
x
x
x
x
x
x
xx
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x x
x
x
x
x
x
x
x
x
x
xx
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x x
x
x
x
x
x
x
x
x
x
xx
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x x
x
x
x
x
x
x
x
x
x
xx
x
x
x
x
x
x
x
x
x
Actors include the primary actors from the User
Profiles, including: User, Registered User and
Mobile User
Use Case Model
Use Cases include (some from mobile devices):










Register User
Unregistered User
Logon
Change Password
Register User
Enterprise Systems Inquiry
Browse Enterprise Systems
External Enterprise System Inquiry
Update Enterprise System
Create User Profile
Create Content
Request External Web Service
02-012
02-013
Browse Enterprise System
Browse Enterprise
System From
Mobile Device
01-010
01-011
Logon
Logon From
Mobile Device
01-012
01-013
Change Password
Change Password
From Mobile
Device
Mobile
Registered
User
03-010
RegisteredUser
Create User Profile
Administrator
02-010
02-011
Enterprise System
Inquiry
Enterprise System
Inquiry From Mobile
Device
02-014
05-011
External Enterprise
System Inquiry
Request
External Web
Services
02-015
Enterprise System Update
04-010
Enterprise Representative
Create Content
External Enterprise
System
© Copyright IBM Corporation 2003 All Rights Reserved
Enterprise Architecture & Technology Center of Excellence
The Architecture Overview Diagram represents governing ideas and candidate
building blocks
Users
 Overview Diagrams, Architecture Layers and
Services are described for:


e-business
Services
Registration Function
Enterprise View
IT System View
Services View

Delivery
Channels
Resources
Directory
Systems
Pervasive/
Wireless Devices
Authentication and
Authorization Function
Customer
Legacy
Applications
Enterprise Inquiry
Function
Internet
Browser
Database(s)
Enterprise Update
Function
Service
Representative
System
Monitoring
Enterprise Reporting
Function
Intranet Browser
Presentation Services
Resource Managers
Application Services
Clients
Enterprise Administration
Function
Directory & Security
Services
Device
Gateway
Load
Balancer
Reverse
Proxy
Server
Transcoder
Third Party
Systems or
Services
Public or
Private
Networks
User
Profiles
Content
Management
Internet
Pervasive
Device
Business Partner
Packaged
Solutions
Managed
Content
Browser
Web Server
Content
Delivery
Messaging & Collaboration
Function
Internal User
APPLICATION
TIER
PRESENTATION
TIER
Application
Logic
Static
Content
Web
Enhancing
Services
Web Server
Legacy
Applications
Application
Database
Services
Web Client
(Browser)
Pervasive
Computing and
Wireless Devices
Caching
Proxies
DIspatcher/
Load Balancing
Device Gateway
Firewall
Gateway
Services
Application
Data
Web Services
Directory
Enterpise Security Management
Enterprise System Managment
Security
Enterprise
Database(s)
ENTERPRISE
TIER
e-business system boundary
Presentation
Delivery
Services
Integration
Hub
External
Enterprise
System
Internet or
Extranet Browser
CRM
Web
Application
Services
Customer
Relationshup
management
Web Application
Services
Presentation Logic
Processing
Integration
Services
Data
Stores
Brokering
Application Logic
Processing
Process Mgmt
Session State Manager
Common &
Custom Svscs
Load Balancing
Coonection Pooling
Internal
Legacy
Applications
Packaged
Business
Applications
Adapters
 Enterpris
 Database
 External
Thread Pooling
Gateway Services
External
Partner
Services
Web Services
Directory
Enabling Services – JVM, XML Parsers etc.
Base System Services
Networking Services
Universal Layer
Systems Management Services
© Copyright IBM Corporation 2003 All Rights Reserved
Enterprise Architecture & Technology Center of Excellence
Non-Functional Requirements identify considerations affecting Quality of Service
and Constraints for the system








Availability
Backup & Recovery
Capacity Estimates & Planning
Configuration Management
Disaster Recovery
Extensibility / Flexibility
Failure Management
Performance








Reliability
Scalability
Security
Service Level Agreements
Standards
Systems Management
Environment
Quality of Service under load
© Copyright IBM Corporation 2003 All Rights Reserved
Enterprise Architecture & Technology Center of Excellence
The Security & Privacy Policies provide high level statements of the
management’s goals, objectives & beliefs in the security & privacy area.



This work product prescribes management’s direction to guide an organization in
meeting the security & privacy objectives. These are used in the creation of the
architecture as well as in the implementation of any specific solution or
application.
The following policies are described in great detail in this work product:

Internet Privacy Policy

Key Management Policy

Security Policy

PC and LAN Security Policy

Domain Name Service Policy

System Access Policy

Extranet Firewall Policy

Access Control Administration
Policy

Internet Firewall Policy

Content Policy

Remote Access Policy

Anti-virus Policy

Cryptography Policy
The scope of these policies are enterprise wide. In addition to the definition of
policies, this work product identifies the roles and responsibilities of individuals
and organizations responsible for the implementation of these directives.
© Copyright IBM Corporation 2003 All Rights Reserved
Enterprise Architecture & Technology Center of Excellence
Security & Privacy Requirements
 This document addresses risks related to protecting business information
wherever it resides and categorizes them into the following









Authentication / identification
Administration / Configuration
Assurance / Monitoring
Access Control
Security Policy Administration
Privacy / Confidentiality
Integrity
Accountability / Non-repudiation
Security Management
 The Security & Privacy Requirements captures the process & technology
needs specific to the business & IT strategies from a security and privacy
perspective.
© Copyright IBM Corporation 2003 All Rights Reserved
IBM
SOA – Service Oriented Architecture
Anders Bonde
© 2006 IBM Corporation
IBM Transport & Logistics
What is …..?
… a service?
… service orientation?
A repeatable
business task – e.g.,
print an invoice; create
new booking
A way of integrating your
business as linked
services
and the outcomes that
they bring
… service oriented
architecture (SOA)?
… a composite
application?
An IT architectural
style that supports
service orientation
A set of related &
integrated services that
support a business
process built on an SOA
IBM Transport & Logistics
Why use a Service Oriented Architecture?

Flexibility
Customer
 Wire and rewire your business to win in the market

Responsiveness
Division
 Change the way you run your business quickly
Shared
Service
 Continually measure and improve your business
operations for performance
Supplier

Optimization

AND Solution Building Efficiency
 Deploy business process
solutions at lowest cost
Outsourced
*Sources: CBDi
IBM Transport & Logistics
Layers of SOA
SERVICES
SERVICE
PROVIDER
COMPONENTS
QoS, SECURITY, MANAGEMENT AND MONITORING
(INFRASTRUCTURE SERVICES)
BUSINESS PROCESSES
- SHORT TERM
- NON-INTERRUPTABLE
- SYSTEM ROLES ONLY
- LOOSE COUPLING
INTEGRATION ARCHITECTURE
(ENTERPRISE SERVCIE BUS)
SERVICE
CONSUMER
Service Oriented Architecture is based on a 3-layer
model of “components”, “services” and “processes”
- LONG RUNNING
- INTERRUPTABLE
- INTERRACTIVE
- HUMAN AND SYSTEM ROLES
- ALTERNATIVE FLOWS FOR NON
STANDARD CONDITIONS
- COLLABORATIONS OF
FINER GRAINED SERVICES
- PERFORMANCE
FAVOURED ABOVE LOOSE
COUPLING
NEW / EXISTING APPLICATIONS AND RESOURCES
IBM Transport & Logistics
IBM SOA Reference Architecture
Comprehensive services in support of your SOA
Business Modeling
Business Monitoring
Business Dashboards
Interaction Services
Process Services
Ad hoc composition
Service Choreography
Information
Services
Master Data Management
User Integration
Device Integration
Business Rules
Staff
Information Integration
Data Management
Build
Interoperability
Mediation
ESB
Registry
Deployment
Asset
Mgmt.
IT Service
Management
Development
Services
Business Innovation & Optimization Services
Security
Policy
Partner Services
Business App Services
Access Services
Partner Management
Protocol
Document Handling
Component
Data
Service Enablement
Object Discovery
Event Capture
Edge
Infrastructure Services
Workload Management
Virtualization
High Availability
IT
Monitoring
IBM Transport & Logistics
Service Oriented Development
Business dashboard
Business Innovation & Optimization Services
Portal
Information
Services
Federated
IT Service
Management
Process Services
Query
ESB
Partner Services
Community
Manager
Business App
Services
App EJBs
Infrastructure Services
Access Services
Oracle
Adapter
SAP
Adapter
Apps &
Info Assets
Development
Services
Interaction Services
DB
Access
IT impact
on processes
IBM Transport & Logistics
Business Processes
 Coordinated chains of activities producing a business results
 Typically consist of:
Human activities (Human Workflow)
Business system activities (such as ERP, or CRM,…)
Combinations of human and system activities
 Define how the business runs at an operational level
 May be hidden or embedded:
In the organization and culture of a company
In the business systems of a company
 Are often poorly understood
IBM Transport & Logistics
Processes & Simulation
Show
understanding
and articulate
solutions using
basic mapping
Maintenance Repair And Overhaul Process - Model
Maintenance Repair And Overhaul Process - Simulation
Quantify value
using basic
analysis
As-Is Analysis
To-Be Analysis
Model Exported as a BPEL Process
Business
Analyst
BPEL
Process Choreography
Integration
Developer
Decision of
•Which Services are invoked
•What order Services are
invoked
Transformation of data output from
one Service and input to another
© 2006 IBM Corporation
BPEL …
 Business Process Execution Language
 A specification for Business Process description and execution
 Invented by a core set of companies led by IBM and Microsoft
 Now progressing towards standard through OASIS
 Current Technical Committee
BEA Systems Inc
Hewlett-Packard
IBM
Microsoft Corporation
NEC Corporation
Novell
Oracle
SAP
SeeBeyond Corporation
Sterling Commerce
Sun Microsystems
Tibco
webMethods Inc.
© 2006 IBM Corporation
Thai
Traditional Chinese
Gracias
Russian
Spanish
Thank
You
Tak
Danish
English
Merci
French
Obrigado
Brazilian Portuguese
Arabic
Grazie
Danke
Italian
German
Simplified Chinese
Japanese
© 2006 IBM Corporation