Index_W

W

W3C (World Wide Web Consortium)

defining data types in DTDs, 85

maintaining standards for HTML and XML, 69

setting Web services standards, 598

standards for DOM node-based interface, 141

WSDL specifications, 608

XML specifications, 69

XPath specifications, 182

XSD data type changes, 100, 111

XSD scale and precision attribute changes, 107

XSL and XSLT specifications, 169

weather forecaster response schema, 522–523

weather Web service, 320–352

adding authentication to, 361–365

building listener as ASP page, 333–337

building responder, 337–345

building schema for requests and responses, 329–332

choosing technology for, 321–323

defining security model for, 323–324

deploying, 345–346

establishing site hosting, 346–350

identifying consumer with certificate, 324

interaction schema for, 331–332

interface design for, 325–332

overview, 320–321

parsing request for, 335

reviewing S3Weather component for implementing in, 325–328

testing, 350–352

validating data requested for, 335–337

See also certificate security; weather Web service consumer

weather Web service consumer, 520–535

building request for, 528–529

callWeatherWS method, 533–535

creating in Java, 520

designing, 520–525

developing application window for, 526–527

invoking Web service for, 528, 529–530

parsing response from, 530–532

testing, 535

See also weather Web service

weatherCheck request schema, 330

weatherCheck response schema, 330–331

Web applications

architecture of Web service vs., 50–51

defined, 2

logical architecture of, 46–47

n-tier architecture of, 3–4

Web services vs., 20–21

Web servers

services for maintaining state, 36

timeout properties for, 37

Web services, 1–23

architecture of Web application vs., 50–51

changing interface after deploying, 413

content-oriented, 204–213

converting static Web page to, 21–23

creating masked, 194–196

defined, 16

defining presentation service options, 203–204

determining exposure level of, 194–202

developing models for, 191–193

developing standards for, 597–598

development life cycle for, 14–18

direct vs. proxied, 260–262

embedded, 199–202

enterprise application integration and, 13–14

FTP transfer process part of, 22

HTTP form submission part of, 22–23

identifying service offerings around, 18

identifying solutions for, 16–17

implementing, 17

integration model for, 18–21

invoking for consumers, 528, 529–530

isolated, 196–199

listener and responder in, 37–40

maintaining presentation model after deployment, 200

model development for, 191–193

organizations setting standards for, 598

overview of XML Web applications, 1–3

parsing response from, 530–532

partnership scenarios for, 25–30

peer-to-peer communication with, 266–267

setting style for presentation, 213–215

sharing processes with business layers, 8–14

stating objectives for, 15–16

types of input interfaces for isolated, 198

vendor customization of, 44

Web applications vs., 20–21

See also emerging standards for Web services; modeling Web services; vendor strategies; and specific Web services

Web services calls. See calls

Web Services Definition Language (WSDL), 225, 605–608

Web Services Directory (Bowstreet), 618–619

Web Services Test Area (IBM), 622–623

Web Services Toolkit (IBM), 622

Web services workflows. See workflows

Web Site Content Directory screen (Virtual Directory Creation wizard), 348–349

Web sites

AAA Conferences sample, 551–555, 558–560, 565–572

adding authentication to Web service on, 361–365

archive for code listings and Web services, 457, 519

Ariba, 616

BEA, 617

Bowstreet, 620

for Certificate Server, 353

converting Web pages to Web services, 21–23

Find-A-Home Realtor sample, 536–537

Hewlett-Packard, 621

IBM, 623

Microsoft, 625, 626

Sun, 628

WebDAV (Web-based Distributed Authoring and Versioning), 523

WebLogic (BEA), 616–617

webMethods, 614

WebSphere Application Server

administrative console of, 312

configuring application server, 311–317

creating applications in, 312–313

creating Java servlet in, 314–315

designating servlet Web path in, 316–317

IBM's strategy with, 622

installing Test Environment, 293

naming and specifying Java servlet in, 315–316

WebTop (Sun), 628

well-formed documents, 79–80

well-formed XML

valid XML vs., 72

validating, 470–471

when element (XSLT), 171, 176

Windows 2000. See Microsoft Windows 2000

workflows

for appointment, 229–233, 237–242

building test client for hotel reservation system, 462–465

consuming Web service, 550

creating efficient responses for, 237–241

defined, 281

designing with process flow diagram, 228

determining requirements of hotel reservation system, 367–370

for embedded and isolated Web services, 399–400

identifying process flow in interface model, 373–378

integrating consumer processes in presentation layer, 558–560

interface logic for requests and responses, 480–485

for isolated or embedded service processes, 374

for listener, 443–447

managing state in, 233–237

modified process flow for embedded service consumers, 375

process flow for isolated service without confirmation interaction, 442

processRequest validation logic for hotel reservation, 470–471

recognizing processes in complex consumer applications, 556–558

for responder, 448–450, 451

service variables for embedded and isolated Web services, 400

session data model, 452–453

storyboard design and, 373

validating service variables, 472–474

validating XML against Web service schemas, 471–472

See also hotel reservation system consumer; hotel reservation system workflow

World Wide Web (WWW), 2

World Wide Web Consortium. See W3C

WSDL (Web Services Definition Language), 225, 605–608

wsFetchAvailability function (HRSWS)

logic of, 480–485

process flow for, 395

wsFetchHotelContent function in, 493–495

WWW (World Wide Web), 2




Architecting Web Services
Architecting Web Services
ISBN: 1893115585
EAN: 2147483647
Year: 2001
Pages: 77

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net