Index 1

2

3

4

5

6

7

8

9

1

1

2

3

4

5

6

7

8

9

2

1

2

3

4

5

6

7

8

9

3

3

3

3

3

307

AAbstract interface, Web services, 60Accenture

history, UDDI, 92WS-Interoperability, 86

ACORD, 67XML standards for insurance

industry, 144Adapters, 9–11, 214–215

frameworks, 11JCA adapters, 205

Adjoin SOMMA, 210Administration tools, project evalu-

ation guidelines, 235–236alphaWorks, BPWS4J, 129Amazon, Web APIs, 40–41Apache Software Foundation,

SOAP history, 85Axis, 88, Licensing and support issues, 225Evaluating your requirements,

227-229 APIs (application programming

interfaces), 8–9Application adapters, 9–11, 214–215

frameworks, 11JCA adapters, 205

Application integrationAPIs, 8–9application-level, 7–9B2B, 5business intelligence systems, 4CRM, 4data-level, 7–8DCM, 4ERP, 2, 4external integration, 7FFA, 4heterogeneous integration,

158–159implementation difficulties, 6–7

KM systems, 4PLM, 4point-to-point integration,

162–163portals, 4SCM, 4SFA, 4tactical and strategic advantages, 3Web services as solution, 6

Application-level application inte-gration, 7–9

Application programming interfaces(APIs), 8–9

Application servers, 31Ariba, history of UDDI, 92ASP-style business model, 173–174Asymmetric encryption, 106Asynchronous communication, 14Atomic transactions, 123AT&T, 165Attunity, application adapter frame-

works, 11Authentication and authorization,

110–112, 114–115SOAP messaging, 74–76

Aventail, BPM standards, 128

BB2B (business-to-business)

application integration, 5, 20–21ebXML, 78electronic procurement, 170–171Web service technologies, 77

BEA SystemsBPEL4WS, 91–92, 129, 218BPM standards, 128orchestration and choreography,

126reliable message delivery, 130SOAP extension specifications, 134WebLogic Server, 88, 201, 222

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 307

BEA Systems (cont.)WS-Coordination and -Transaction

specifications, 124–126WS-Interoperability, 86WS-ReliableMessaging, 131WSCI, 91, 127

Binary data formats, 13Bind Systems, ebXML, 80Binding, SOA operation, 58, 6067Black Pearl, BPM standards, 128Blaze Software, BPM standards, 128BMC Patrol, 118, 206

BPM standards, 128Borland

SOAP integration into program-ming languages, 98

.NET language support, 185Web services development tools, 193Bowstreet, BPM standards, 128BPEL4WS (Business Process Exe-

cution Language for WebServices), 91–92, 129, 218

BPM (business process manage-ment) standards, 128, 215,217–218

BPMI (Business Process Manage-ment Initiative), orchestrationand choreography, 126, 128

BPML (Business Process ModelingLanguage), 128

BPSS (Business Process Specifica-tion Schema), 126–127, 130

Browser interfaces, 10BTP (Business Transaction Proto-

col), 123–126Business models

Amazon, 40–41Google, 38–39Kinko’s, 39–40

Business Process ExecutionLanguage for Web Services.See BPEL4WS

Business process management(BPM) standards, 128

Business Process Management Ini-tiative (BPMI), 126, 128

Business Process Modeling Lan-guage (BPML), 128

Business Process SpecificationSchema (BPSS), 126–127, 130

Business-to-business. See B2BBusiness Transaction Protocol

(BTP), 123–126Bytecode (Java), 184

CCA Unicenter, 118, 206Canonical form, XML documents,

109Cap Gemini Ernst & Young, BPM

standards, 128Cape Clear, 162–163Cell Directory Service, DCE, 64Certificate authorities, 75Choreography

BPEL4WS, 92standardization efforts, 126–130vendors, 217WSCI, 91

CICS (Customer InformationControl System) applications,44

CIL (Common IntermediateLanguage), 183–185

CIM (Common InformationModel), 119–120

Circle of trust, 113–114CLI (Common Language Infra-

structure) specification, 186Client/server-based communica-

tion, 14–16, 31client development tools,

198–199client SOA roles, 58

ClinicStation, 169–170CLR (Common Language Run-

time), 183–184Cobalt Group, ebXML, 80Cohesive transactions, 123Collaboration Protocol Profile and

Agreement (CPPA) specifica-tion, 79

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

308

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 308

Collaborative Planning, Forecastingand Replenishment (CPFR)standards, 147

Collaxa, BPEL4WS, 129, 218Collections, programming language

structures, 228Coloplast, 164ComCARE (Communications for

Coordinated Assistance andResponse to Emergencies),145–146

Command line tools, 191, 193CommerceOne

BPM standards, 128ebXML, 80history, UDDI, 92

Common Information Model(CIM), 119–120

Common Intermediate Language(CIL), 183–185

Common Language Infrastructure(CLI) specification, 186

Common Language Runtime(CLR), 183–184

Common Object Request BrokerArchitecture. See CORBA

Communication middlewarebasics, 12–13challenges, 16–20message-oriented, 14RPC-style, 14–16

Compaq, history of UDDI, 92Component Object Model (COM),

221Computer Sciences Corporation,

BPM standards, 128Con-Way Transportation Services,

159–160Containers

EJB containers, 203–205runtime, 200–202

Context, Web services, 124CORBA (Common Object Request

Broker Architecture), 15–17CORBA Naming Service, 64versus SOAP, 76

tightly coupled connections,19, 29

versus UDDI, 69versus WSDL, 63versus XML, 55, 57

Costs, ownership of middleware,18–20

Country Codes standard, 66CPFR (Collaborative Planning,

Forecasting and Replenish-ment) standards, 147

CPPA (Collaboration ProtocolProfile and Agreement) speci-fication, 79

CRM (customer relationship man-agement), 4

Customer Information ControlSystem (CICS), 44

Cyclone Commerce, BPM stan-dards, 128

DD-U-N-S numbers, UDDI, 66Data confidentiality, 107Data integrity, 107Data-level application integration,

7–8Database servers, 31Databases, UDDI registries, 238–239DataChannel, BPM standards, 128Datatypes, XML, 53DCE (Distributed Computing Envi-

ronment) RPC, 15–16Cell Directory Service, 64versus SOAP, 76versus WSDL, 63

DCM (demand chain management)application integration, 4

DCOM (Distributed ComponentObject Model) RPC, 15, 17

NT Registry, 64tightly coupled connections, 19,

29versus WSDL, 63versus XML, 55, 57

DealerSphere, ebXML, 80

1

2

3

4

5

6

7

8

9

1

1

2

3

4

5

6

7

8

9

2

1

2

3

4

5

6

7

8

9

3

3

3

3

3

309

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 309

DECnet, 50versus SOAP, 76

Demand chain management(DCM), 4

Deployment tools, 191, 193–194descriptors, 197–198project evaluation guidelines,

235–236Descriptors, deployment, 197–198Deutsche Telekom, T-Mobile Inter-

national, 41Development tools, 191, 193–194

clients, 198–199project evaluation guidelines,

234–235services, 194–198

DevelopMentor, SOAP project, 78,84

Diagnostic tools, 214, 216Digital certificates, 75Digital Signature Services (DSS),

110, 117Digital signatures, 106, 108–109

managing, 110, 213SOAP messaging, 74

Distributed Component ObjectModel. See DCOM

Distributed Computing Environ-ment. See DCE

DMTF (Distributed ManagementTask Force), 119

DNS (Domain Name System), 48Document-style SOAP messaging,

72Documentum, ebXML, 80Domain Name System. See DNSDotGNU project, 186DSS (Digital Signature Services),

110, 117Dynamic binding, 62, 147–150Dynamic discovery, 140–143Dynamic proxies, 62

EE-Gov Task Force, 165–169E-Travel, 166–167

EAI (enterprise application integra-tion), 11, 20

potential replacement by Webservices, 176

ebMS (ebXML Message Service), 79JAXM, 100

ebXML (Electronic Business usingExtensible Markup Language),78–80

CPPA specification, 79JAXR, 102orchestration and choreography,

126–127, 130Registry and Repository, 79

ECMACLI, 186technology ownership,

187–189EDI (Electronic Data Interchange),

170–171EDS

BPM standards, 128ebXML, 80

Einstein, 160–161EJBs (Enterprise JavaBeans),

202–205Electronic Business using Extensi-

ble Markup Language. SeeEbXML

Electronic Data Interchange (EDI),170–171

Encoding, 61Encryption, 106–108Endpoints, 61Enterprise application integration.

See EAIEnterprise JavaBeans (EJBs),

202–205Enterprise resource planning.

See ERPEntricom, BPM standards, 128Equifax, history of UDDI, 92ERP (enterprise resource

planning)application integration, 4Hershey Foods Corporation, 2

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

310

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 310

eSOAP platform, 199EXOR platform, 199Extensible Business Reporting

Language (XBRL) Inter-national, 146

Extensible Markup Language. SeeXML

Extensible Rights Markup Lan-guage. See XrML

Extensible Stylesheet LanguageTransformations. See XSLT

FFederated identity, 113FedEx, software-as-service business

model, 138Fell, Simon, 85FFA (field force automation), 4Field force automation. See FFAFile servers, 31File Transfer Protocol (FTP), 49Find SOA operation, 58Firewalls

definition, 21, 22Web services, 50

FirstGov portal, 169Forrester Research, 153Frameworks, 11Free Software Foundation, 186FTP (File Transfer Protocol), 49Fujitsu

history, UDDI, 92reliable message delivery, 130WS-Interoperability, 86

GGartner, 152GE Global eXchange Services, 11Global Web Services Architecture

(GXA), 134GNU Project, 186Google Web APIs, 38–39Graphical user interfaces, 10GUIs (graphical user interfaces), 10GXA (Global Web Services Archi-

tecture), 134

HHash tables, 228Hershey Foods Corporation, appli-

cation integration, 2–3Heterogeneous integration,

158–159Hewlett-Packard

history, UDDI, 92HP OpenView, 118, 206OMI, 121

Hitachi, reliable message delivery,130

HR-XML Consortium, 146HTML (Hypertext Markup Lan-

guage), 34vocabulary, 52

HTTP (Hypertext Transfer Protocol),49, 50

authentication, 110–111HTTPS (Hypertext Transfer Protocol

Secure), 73–74Hypertext Markup Language.

See HTMLHypertext Transfer Protocol. See

HTTPHypertext Transfer Protocol Secure.

See HTTPS

Ii2 Technologies, history of UDDI, 92IBM

BPEL4WS, 91–92, 129, 218BPM standards, 128ebXML, 80history, SOAP, 84history, UDDI, 92history, WSDL, 88–89orchestration and choreography,

126reliable message delivery, 130Tivoli, 118, 206UDDI4J, 102Web Services Developer Kit

(WSDK) 191-192WebSphere, 159-161WebSphereMQ, 14, 71, 212

1

2

3

4

5

6

7

8

9

1

1

2

3

4

5

6

7

8

9

2

1

2

3

4

5

6

7

8

9

3

3

3

3

3

311

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 311

IBM (cont.)WS-Coordination and -Transaction

specifications, 124–126WS-Interoperability, 86WS-ReliableMessaging, 131WS-Security specification, 115WSFL, 129

IDEs (integrated developmentenvironments), 214, 216

IDLs (interface definition lan-guages), 63

IdooXoap (Systinet), 85IETF (Internet Engineering Task

Force)encryption standards, 106Web services technologies, 90

IIS (Internet Information Services),183

Implementation of types, Webservices, 60–61

Information technology (IT), 2, 4Infrastructure-level Web services,

210–211reliable network providers,

211–212trust services, 213–214

UDDI registries, 212–213Intalio

BPM standards, 128BPML-based products, 128WSCI, 91, 127

Integrated development environ-ments (IDEs), 214, 216

Integrated Shipbuilding Environ-ment Consortium (ISEC),171–172, 173

Integration hooks, 9–11Intel

history, UDDI, 92WS-Interoperability, 86

Interactive applications, portlets,132–133

Interface definition language. SeeIDLs

International Standards Organiza-tion (ISO)

ISO 3166 Country Codes stan-dard, 66

technology ownership, 188Internet, 49

application integration, 20–22versus traditional middleware, 21

Internet Engineering Task Force.See IETF

Internet Information Services (IIS),183

Internetwork Packet Exchange(IPX) versus SOAP, 76

Interoperability, projects evaluationguidelines, 227–229

IONA application adapter frameworks,

11XMLBus, 165

IPX (Internetwork PacketExchange) versus SOAP, 76

ISDA (International Swaps andDerivatives Association), 145

ISEC (Integrated ShipbuildingEnvironment Consortium),171–172, 173

ISO (International StandardsOrganization)

ISO 3166 Country Codes stan-dard, 66

technology ownership, 188IT (information technology), 2, 4iWay Software, application adapter

frameworks, 11

JJacada Integrator, 164Java

API for WSDL (JWSDL), 101APIs for XML-based RPC

(JAX-RPC), 99API for XML Messaging (JAXM),

99–100API for XML Registries (JAXR),

102EJBs, 202–205JAX-RPC, 99, 209

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

312

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 312

JCA, 205JCP, 98–99JCP, technology ownership,

188–189J2EE application server,

202–205J2EE application server, versus

servlet engines, 205–206JMS, interfaces to MOM prod-

ucts, 14JNDI, 64JRE, 184JSPs, 203JVM, 184JWSDL, 101versus .NET framework, 182,

184–190platform selection for projects,

222–224Remote Method Invocation (See

RMI)Java Community Process. See Java,

JCPJava Message Service. See Java,

JMSJava Naming and Directory Inter-

face. See Java, JNDIJava Runtime Environment. See

Java, JREJava Virtual Machine. See Java,

JVMJavaServer Pages. See Java, JSPsJ2EE Connector Architecture. See

Java, JCAJPMorgan, 158–159Jupiter Research, 152

KKerberos tickets, 75, 111

WS-Security bindings, 116Key management, 106, 109–110Killdara, ebXML, 80Kinko’s “File, Print . . . Kinko’s”

Web service, 39–40kSOAP platform, 199Kulchenko, Paul, 85

LLiberty Alliance Project, 113–114Lifecycle of applications, 201Linked lists, 228Linux platform

deploying .NET applications, 186RPC-style middleware, 15, 17

Literal encoding, 72Loosely coupled connections,

19–20, 29document-style SOAP messaging,

72versus XML, 57

Lotus, SOAP history, 84

MMacromedia, XML protocols, 77Merrill Lynch, CICS environment,

44Message-oriented middleware.

See MOMMessage switching systems, 214–215META Group, 153Meta-markup languages, XML, 53Microsoft

BPEL4WS, 91–92, 129, 218DCOM RPC, 15, 17history, SOAP, 78, 84history, UDDI, 92history, WSDL, 88–89Intermediate Language (See

CIL)Microsoft MQ, 14, 17.NET framework, 85, 88, 98,

182–183.NET framework, versus Java,

182, 184–190orchestration and choreography,

126reliable message delivery, 130SOAP Toolkit, 85, 98WS-Coordination and -Transac-

tion specifications, 124–126WS-Interoperability, 86WS-ReliableMessaging, 131WS-Security specification, 115

1

2

3

4

5

6

7

8

9

1

1

2

3

4

5

6

7

8

9

2

1

2

3

4

5

6

7

8

9

3

3

3

3

3

313

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 313

Microsoft (cont.)XKMS, 110XLANG, 129

Middleware. See also traditionalmiddleware

challenges, 16–20communication middleware,

12–13communication middleware,

styles, 13––16network APIs, 11–13SOA, 30versus SOAP, 175–176Web service management exten-

sions, 207–209MOM (message-oriented middle-

ware), 14, 57challenges, 16difficulty to use, 17loosely coupled connections,

19–20RNPs, 212

Momentum, BPEL4WS, 129, 218Monitoring frameworks, 209–210Mono project, 186Multichannel user interfaces, 214,

216

NNAICS (North American Industry

Classification System), 66NASSL (Network Accessible Service

Specification Language), 89National Industrial Infrastructure

Protocols Consortium (NIIIP),171–172, 173

National Institute of Standards andTechnologies. See NIST

NDR (Native Data Representation),CORBA, 55

NEC, reliable message delivery, 130.NET framework (Microsoft), 85,

88, 98, 182–183versus Java, 182, 184–190

Network Accessible Service Specifi-cation Language (NASSL), 89

Network APIsmiddleware, basics, 11–13middleware, challenges, 16–20middleware, styles of communi-

cation, 13–16protocols, 13

NIIIP (National Industrial Infra-structure Protocols Consor-tium), 171–172, 173

NIST (National Institute of Stan-dards and Technologies), 106,107

North American Industry Classifica-tion System (NAICS), 66

NT Registry, DCOM, 64

OOASIS (Organization for Advance-

ment of Structured Informa-tion Standards)

BTP, 123–126DSS, 110ebXML, 78, 79history, SOAP, 88history, WSDL, 90SAML, 75, 111–112SNMP, 119SOAP history, 88SSTC, 111–112UDDI, 91UDDI, OASIS Standard, 93Web services security standards,

106WS-RM, 131WSDM, 122WSIA, 132WSRP, 132–133WSS, 115XCBF, 111XML security exchange, 75

OMA, 67OMG (Object Management Group)

CORBA, 15UML, 120

OMI (Open Management Inter-face), 121–122

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

314

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 314

ONC (Open Network Computing)RPCs, 15, 17versus WSDL, 63versus XML, 55

Ontology.Org, BPM standards, 128Open Application Group, ebXML,

80Open Management Interface

(OMI), 121–122Open Network Computing. See ONCOpenTravel Alliance (OTA), 67, 145

ebXML, 80Optimization tools, 214, 216Oracle

history, UDDI, 92reliable message delivery, 130WS-Interoperability, 86

Orchestrationstandardization efforts, 126–130vendors, 217

Organization for Advancement ofStructured Information Stan-dards. See OASIS

P – QPatricia Seybold Group, 153Peer-based style communication, 14PeopleSoft, ebXML, 80PKI (public key infrastructure),

109–110managing, 213

PLM (product lifecycle manage-ment), 4

PocketSoap (Simon Fell), 85Point-to-point integration, 162–163Portals, 214, 216

managing portal initiatives,167–169

portal presentation logic (Seeportlets)

Portlets (portal presentation logic),55

interactive applications, 132–133Ports, 61portTypes (WSDL), 60

versus service types, 65

Premier Farnell, 170–171Principal security identifiers, 233Print servers, 31Product lifecycle management. See

PLMProjects, evaluation guidelines

administration tools, 235–236characterizing projects, 219–221deployment tools, 235–236development tools, 234–235requirements, extensibility fea-

tures, 229–231requirements, interoperability,

227–229requirements, performance,

226–227requirements, scalability,

226–227requirements, security, 231–234requirements, standards support,

227–229selecting Java platform,

222–224selecting languages and operating

systems, 221–222UDDI registries, 236–243

Proxies, 61interceptors, 229–230

Public key (asymmetric) encryp-tion, 106

Public key infrastructure (PKI),109–110

RRDBMS (relational database man-

agement systems), 238Reference architecture, 90–91Register SOA operation, 58Registries. See UDDIRegistry and Repository, ebXML, 79Relational database management

systems (RDBMS), 238Reliable message delivery,

130–131Reliable network providers (RNPs),

181, 211–212

1

2

3

4

5

6

7

8

9

1

1

2

3

4

5

6

7

8

9

2

1

2

3

4

5

6

7

8

9

3

3

3

3

3

315

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 315

Remote Method Invocation. SeeRMI

Rendezvous (TIBCO), 14Return on investment (ROI), 5–6RMI (Remote Method Invocation),

15, 17registry, 64tightly coupled connections, 19,

29versus WSDL, 63versus XML, 55, 57

RNPs (reliable network providers),181, 211–212

ROI (return on investment), 5–6RosettaNet

ebXML, 80Web service technologies, 77XML-based standards, 67

RPC-style (remote procedure call)middleware, 14–16

challenges, 16–20SOA, 30SOAP, 72versus Web services, 29, 57

Runtime architecture, 191,199–202

SS1 Corporation, BPM standards,

128SAAJ (SOAP with Attachments API

for Java), 100Sales force automation. See SFASalesforce.com, 162–163SAML (Security Assertions Markup

Language), 75, 111–112, 117single sign-on services, 112–114WSS bindings, 116

SAPBPM standards, 128history, UDDI, 92WS-Interoperability, 86WSCI, 91, 127

Scalability, project evaluationguidelines, 226–227

SCL (SOAP Contract Language), 89

SCM (supply chain management), 4Screen scraping, 10Secure Sockets Layer/Transport

Layer Security. See SSL/TLSSecurity

authentication and authorization,110–112, 114–115

data confidentiality and integrity,107

digital signatures, 106, 108–109digital signatures, managing,

110encryption, 106–108expressing and exchanging infor-

mation in XML, 111–112key management, 106, 109–110middleware, 208project evaluation guidelines,

231–234security tokens, 111single sign-on services, 75,

112–114, 117SOAP, 73–76standardization efforts, 105–106XML security, 115–117

Security Assertions Markup Lan-guage. See SAML

Security Services Technical Com-mittee (SSTC), 111–112

SeeBeyond, BPML-based products,128

Semantic Web project, 143Service brokers, 58Service consumers, 58

standard international tax-onomies, 66

Service contractsIDL, 63SOA roles, 58

Service grids, 210–211Service Integrity SIFT, 210Service-Oriented Architecture.

See SOAService providers

SOA roles, 58UDDI, 65, 67

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

316

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 316

Service typesUBR, 94UDDI, 65UDDI, tModel, 66–68

Services, definition, 30Servlets/servlet engines versus J2EE

application server, 205–206SFA (sales force automation), 4Short Message Service. See SMSSiebel Call Center, 164SIIA (Software Information Indus-

try Association), 151Simple Mail Transfer Protocol. See

SMTPSimple Network Management Pro-

tocol (SNMP), 119Simple Object Access Protocol. See

SOAPSingle key (symmetric) encryption,

106Single sign-on services, 75,

112–114, 117SMS (Short Message Service), 42SMTP (Simple Mail Transfer Proto-

col), 49, 50SNA (System Network Architec-

ture), 50versus SOAP, 76

SNMP (Simple Network Manage-ment Protocol), 119

SOA (Service-Oriented Architec-ture), 30

core technology of Web services,47–48, 57–59

technologies implementing SOApatterns, 59

versus UDDI, 69–70SOAP Contract Language (SCL), 89

extensions, specifications, 134SOAP messages

body, 71, 117document-style, 72encoding, 73envelopes, 70header processors, 76, 117headers, 71, 117

processors, 200–201receivers, 72RPC-style, 72runtime containers, 200–202senders, 72

SOAP (Simple Object Access Proto-col), 27, 59

development challenges, 85–86engines, 181extensions, 73history, 84–85implementations, 83, 181versus middleware technologies,

175–176versus other communication sys-

tems, 76–77programming standards, 97–98,

103programming standards, Java,

99–100security, 73–76servers, 181versus SOA systems, 77stacks, 181standards, 190–191W3C and OASIS, 88WS-Interoperability, 86–88

SOAP Toolkit (Microsoft), 85, 98SOAP with Attachments API for

Java (SAAJ), 100SOAPbuilders, 86SOAP::Lite (Paul Kulchenko), 85Software AG, application adapter

frameworks, 11Software-as-service business model,

27, 172–174, 211, 247versus Web services, 37–38Web services potential, 137–140

Software Information IndustryAssociation (SIIA), 151

Sonic Softwarereliable message delivery, 130SonicMQ, 14

SSL/TLS (Secure SocketsLayer/Transport Layer Secu-rity), 73

1

2

3

4

5

6

7

8

9

1

1

2

3

4

5

6

7

8

9

2

1

2

3

4

5

6

7

8

9

3

3

3

3

3

317

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 317

SSTC (Security Services TechnicalCommittee), 111–112

Standards for Technology in Auto-motive Retail (STAR), 145

Sterling Commerce, ebXML, 80Style sheets, XSLT, 54–55Sun Microsystems

BPM standards, 128ebXML, 80history, UDDI, 92orchestration and choreography,

126reliable message delivery, 130technology ownership, 188–189WSCI, 91, 127

Supply chain management. SeeSCM

Sybase, SOAP integration into pro-gramming languages, 98

Symmetric encryption, 106Synchronous communication,

14–16System Network Architecture.

See SNASystinet

adoption of Web services, 151IdooXoap, 85WASP, 88, 158–159

TT-Mobile International, T-Mobile

Online, 41–43Taxonomies, UDDI, 65, 242TCP/IP (Transmission Control Pro-

tocol/Internet Protocol), 48, 50TechRepublic surveys, 152Testing tools, 214, 216Thomas Register supplier identifier,

66TIBCO Software

application adapter frameworks,11

reliable message delivery, 130Rendevous, 14Web Services SDK, 88WS-ReliableMessaging, 131

Tightly coupled connections, 19, 29SOAP RPC convention, 72versus XML, 57

TIRKS (Trunks Inventory RecordKeeping System), 165

Tivoli (IBM), 118, 206tModels, UDDI, 66–68Tokens, security, 75Trading partner networks, 171–172,

173Traditional middleware. See also

middlewarechallenges, 16–20inability to work across Internet,

21versus Internet, 21styles, 13–16versus WSDL, 64versus XML, 57

Transactions, 122–126Transmission Control

Protocol/Internet Protocol. SeeTCP/IP

Trunks Inventory Record KeepingSystem (TIRKS), 165

Trust services, 109–110, 213–214Types, Web services, 60

UUBR (UDDI Business Registry),

93–95, 239–240dynamic discovery of business

partners, 140, 142nodes, 93–94

UCC (Uniform Code Council)business XML standards,

146–147Core Order business message,

147–148RosettaNet, 77

UDDI Business Registry. See UBRUDDI (Universal Description, Dis-

covery & Integration), 59,65–69

dynamic binding, 149–150history, 92–93

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

318

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 318

versus other description lan-guages, 69–70

programming standards, 97, 103programming standards, Java,

101–102project evaluation guidelines,

236–243registries, 35, 212–213registries, for ISEC, 172, 173registries, private, 95–97registries, wizards, 192, 198UDDI Business Registry, 93–95UDDI Operators Council, 93–95

UDDI4J (UDDI Java client APIs),101–102

UML (Unified Modeling Language),120

UN/CEFACT (United Nations Cen-tre for Trade Facilitation andElectronic Business), 78, 79

Unified Modeling Language (UML),120

Uniform Code Council. See UCCUniform Resource Identifiers. See

URIsUniform Resource Locators. See

URLsUniform Resource Names. See URNsUnited Nations Centre for Trade

Facilitation and ElectronicBusiness (UN/CEFACT), 78, 79

United Nations Standard Productsand Services Codes (UNSPSC),66

United Parcel Service, UPS OnLineTools, 41

Universal Description, Discovery &Integration. See UDDI

Universal Product Code (UPC),146–147

University of Texas M.D. AndersonCancer Center, 169–170

UNIX platformdeploying .NET applications,

186RPC-style middleware, 15, 17

UNSPSC (United Nations StandardProducts and Services Codes),66

UPC (Universal Product Code),146–147

URIs (Uniform Resource Identi-fiers), 48–49

URLs (Uniform Resource Locators),48–49

URNs (Uniform Resource Names),48

U.S. Navy, private UDDI registries,95–96

Userland, SOAP project, 78, 84

VVeriSign

history, UDDI, 92WS-Security specification,

115XKMS, 110

Versata, BPM standards and prod-ucts, 128

VerticalNet, BPM standards, 128Verve, BPM standards, 128VES (VIrtual Execution System),

184VICS (Voluntary Interindustry

Commerce Standards) Asso-ciation, 147

Virtual Execution System (VES),184

Vitria, BPEL4WS, 218VoiceXML, 54–55

WWachovia, 160–161Wal-mart, effective use of informa-

tion technology, 138WAP (Wireless Application Proto-

col), 54–55WASP (Web Applications and

Services Platform), 88,158–159

WBEM (Web-Based EnterpriseManagement), 120

1

2

3

4

5

6

7

8

9

1

1

2

3

4

5

6

7

8

9

2

1

2

3

4

5

6

7

8

9

3

3

3

3

3

319

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 319

W3C (World Wide Web Consor-tium)

Semantic Web project, 143SOAP history, W3C Note, 84SOAP history, W3C Recommen-

dation, 88Web architecture development

and standards, 30Web services security standards,

106WSDL history, W3C Note, 89WSDL history, W3C Working

Draft, 90XKMS, 110XML Encryption, 108XML Schema, 53–54

Web. See World Wide WebWeb Applications and Services Plat-

form (WASP), 88, 158–159Web-Based Enterprise Management

(WBEM), 120Web servers, 31, 33Web services

adoption, 151–153application integration, 6, 22–23application integration, advan-

tages, 23–25application templates, 36–37basics, 27–32benefits, 153–155building, 32–33business models, 33-44characteristics, 35combining advantages of MOM

and RPC-style middleware, 20core technologies, 47domain-specific industry stan-

dards, 143–147dynamic binding, 147–150dynamic discovery of business

partners, 140–143employees sharing information,

169–170firewalls, 50inappropriate uses, 174–176infrastructure, 36–37

internal integration, 163–165managing portal initiatives,

167–169multichannel client formats,

160–161pervasiveness, 17–18potential uses, hype, 135–136programming standards, basics,

97–99programming standards, Java,

99–102reasons for using, 28–29reducing duplicative applications,

165–167scope, 35–37service grids, 210–211software-as-service, 137–140,

172–174versus software-as-service busi-

ness model, 37–44standardization efforts, 133–134standardization efforts, manage-

ment, 117–122superpowered PDAs, 136–137technologies, 36trading partner networks,

171–172, 173versus traditional middleware, 28unknown client environments,

159–160XML, 21–22

Web services, evaluation guidelinesadministration tools, 235–236characterizing projects, 219–221deployment tools, 235–236development tools, 234–235project requirements, extensibil-

ity features, 229–231project requirements, interoper-

ability, 227–229project requirements, perfor-

mance, 226–227project requirements, scalability,

226–227project requirements, security,

231–234

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

320

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 320

project requirements, standardssupport, 227–229

selecting Java platform, 222–224selecting languages and operating

systems, 221–222UDDI registries, 236–243

Web services, infrastructure-level,210–211

reliable network providers,211–212

trust services, 213–214UDDI registries, 212–213

Web services, management exten-sions

basics, 206–207middleware, 207–209monitoring frameworks,

209–210Web services, platforms

basics, 181–182deployment tools, 191, 193–194deployment tools, descriptors,

197–198development, clients, 198–199development, services, 194–198development, tools, 191,

193–194features, 190–192J2EE application server,

202–205J2EE application server, versus

servlet engines, 205–206.NET framework, 182–183.NET versus Java, 182, 184–190runtime architecture, 191,

199–202Web Services Architecture Working

Group, 90, 133Web Services Choreography Inter-

face. See WSCIWeb Services Coordination Group,

90Web Services Description Language.

See WSDLWeb Services Description Working

Group, 90

Web Services Distributed Manage-ment (WSDM), 122

Web Services Flow Language(WSFL), 129

Web Services for Remote Portals(WSRP), 132–133

Web Services Interactive Applica-tions (WSIA), 132

Web Services InteroperabilityOrganization. See WS-I

Web Services Reliable Messaging(WS-RM), 131

Web Services SDK (TIBCO Soft-ware), 88

Web Services Security TechnicalCommittee, 91

Web Services Security (WSS),115–116

Web sitesevolution, 33versus Web services, 34

WebForms, 183WebLogic Server (BEA), 88webMethods

application adapter frame-works, 11

BPEL4WS, 218OMI, 121XKMS, 110XML protocols, 77

WebSphereMQ (IBM), 14WebV2, BPEL4WS, 218White space, XML documents,

108–109WhiteMesa Server, 88Winer, Dave, 84WinForms, 183Wingfoot, 199Wireless Application Protocol.

See WAPWireless Markup Language. See

WMLWML (Wireless Markup Language),

54–55World Wide Web

DNS, 48

1

2

3

4

5

6

7

8

9

1

1

2

3

4

5

6

7

8

9

2

1

2

3

4

5

6

7

8

9

3

3

3

3

3

321

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 321

World Wide Web (cont.)evolution, 33–35FTP, 49HTTP, 49versus other networks, 50SMTP, 49TCP/IP, 48URI schemes, 49URIs, 48URLs, 48–49Web application protocols, 49Web services, 17Web services, core technology, 47

World Wide Web Consortium. SeeW3C

Wrapping services, 195–196, 201WS-Addressing, 131WS-Coordination specification,

124–126WS-I (Web Services Interoperability

Organization), 86–88WS-ReliableMessaging, 131WS-Reliability, 131WS-RM (Web Services Reliable

Messaging), 131WS-Security specification, 115WS-Transaction specification,

124–126WSCI (Web Services Choreography

Interface), 91, 127WSDL (Web Services Description

Language), 59–63building new services, 194–195challenges, version 1.1, 89–92versus EAI, 176history, 88–89JWSDL, 101versus other description lan-

guages, 63–65programming standards, 97, 103programming standards, Java,

101SOAP messages, 71, 75standards, 190–192

WSDM (Web Services DistributedManagement), 122

WSFL (Web Services Flow Lan-guage), 129

WSIA (Web Services InteractiveApplications), 132

WSRP (Web Services for RemotePortals), 132–133

dynamic discovery of businesspartners, 143

WSS (Web Services Security),115–116

X – ZX.509 certificates, 111

WS-Security bindings, 116XACML (XML Access Control

Markup Language), 115XBRL (Extensible Business Report-

ing Language) International,146

XCBF (XML Common BiometricFormat), 111

WS-Security bindings, 116Ximian, Mono project, 186XKMS (XML Key Management

Specification), 110, 116–117XLANG (Microsoft), 129XML Access Control Markup Lan-

guage (XACML), 115XML Common Biometric Format

(XCBF), 111XML documents, 51–52

canonical form, 109transforming with XSLT, 54–55white space, 108–109

XML elements, 51datatypes, 53

XML Encryption, 108XML (Extensible Markup Lan-

guage), 51definition, 21–22HTML vocabulary, 52meta-markup languages, 53OASIS, 75versus other data representations,

55–57SAML, 75

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

5

6

7

8

9

0

1

2

3

4

322

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 322

SOAP, 70–73tags, 51tokens, 111tools, 214–215Web service core technology, 47,

50–53XML Fund, BPM standards, 128XML Global, ebXML, 80XML Key Management Specifica-

tion (XKMS), 110XML Protocol Working Group, pro-

posals to W3C, 88, 90XML-RPC protocol, 78, 84

XML Schema, 53–54, 56element’s datatypes, 53RPC messages, 73

XML Signature Recommendations,109

XrML (Extensible Rights MarkupLanguage), 115

WS-Security bindings, 116XSLT (Extensible Stylesheet Lan-

guage Transformations), 54–55

versus XML, 56Yahoo, 174

1

2

3

4

5

6

7

8

9

1

1

2

3

4

5

6

7

8

9

2

1

2

3

4

5

6

7

8

9

3

3

3

3

3

323

Index

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 323

If you are interested in writing a book or reviewing manuscripts prior to publication, please write to us at:

Editorial Department Addison-Wesley Professional75 Arlington Street, Suite 300Boston, MA 02116 USAEmail: AWPro@aw.com

Visit us on the Web: http://www.awprofessional.com

You may be eligible to receive:

• Advance notice of forthcoming editions of the book

• Related book recommendations

• Chapter excerpts and supplements of forthcoming titles

• Information about special contests and promotions

throughout the year

• Notices and reminders about author appearances,

tradeshows, and online chats with special guests

at www.awprofessional.com/register

29731 13 pp. 307-324 r1jm.ps 5/16/03 9:58 AM Page 324