Tài liệu Module 8: Integrating XML Web Services in a B2B Solution pdf

Module 8: Integrating
XML Web Services in a
B2B Solution
Contents
Overview

1

Lesson: Introduction to XML Web Services

2

Lesson: Applying XML Web Services to
Order Processing

10

Lesson: Providing XML Web Services to
Trading Partners

16

Review

22

Lab A: Integrating XML Web Services

24

Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the example companies, organizations, products,
domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious,
and no association with any real company, organization, product, domain name, e-mail address,
logo, person, place or event is intended or should be inferred. Complying with all applicable
copyright laws is the responsibility of the user. Without limiting the rights under copyright, no
part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
 2001 Microsoft Corporation. All rights reserved.
Microsoft, Windows, BackOffice, BizTalk, FrontPage, Hotmail, PowerPoint, Visual Basic,
Visual C++, Visual Studio, and Windows Media are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their
respective owners.


Module 8: Integrating XML Web Services in a B2B Solution

iii

Instructor Notes
Presentation:
45 minutes
Lab:
45 minutes

This module introduces students to Extensible Markup Language (XML) Web
services and how students can use them to process purchase orders from
business-to-business (B2B) trading partners. Students will learn how to choose
XML Web services and how to integrate them in their order processing
workflow. Students will also explore the requirements for hosting their own
XML Web services and providing them to trading partners.
After completing this module, students will be able to:
!

Describe how to use XML Web services in a B2B scenario.

!

Decide how to integrate XML Web services in order processing.

!

Decide whether and how to make their own XML Web services available to
trading partners.

Required materials

To teach this module, you need Microsoft® PowerPoint® file 2420A_08.ppt.

Preparation tasks

To prepare for this module:
!
!

Perform the instructor demonstration.

!

Review Course 2524A, Developing XML Web Services.

!

Classroom setup

Read all of the materials for this module.

Download and become familiar with the Simple Object Access Protocol
(SOAP) Toolkit, located at />
The information in this section provides setup instructions that are required to
prepare the instructor computer for the hands-on practice.

! To prepare for the demonstration
• Ensure that the instructor computer can connect to the Internet.


iv

Module 8: Integrating XML Web Services in a B2B Solution

How to Teach This Module
This section contains information that will help you teach this module.

Lesson: Introduction to XML Web Services

This module begins by explaining the challenges that businesses must
overcome to integrate business systems, and how students can use XML Web
services to overcome those challenges. This lesson is introductory material. For
more in-depth coverage of XML Web services, refer students to Course 2524A,
Developing XML Web Services.
The following information is specific to individual pages in this lesson.
Elements of an XML
Web Service Document

This page is intended only to familiarize students with XML Web services and
to provide a high-level overview of how XML Web services work. It is not
necessary to discuss in depth the mechanics of XML Web services, but ensure
that students understand how XML Web services work.

Demonstration: Using
an XML Web Service

This demonstration uses Microsoft’s profile in the Universal Description,
Discovery and Integration (UDDI) Business Registry. In this demonstration,
show students how an XML Web service returns information based on a query.
Encourage discussion about the XML Web service, and ask students how they
could use an XML Web service or create their own. Use this example as a
reference point throughout the module. Also point out that the Microsoft UDDI
Web site is an XML Web service.

Lesson: Applying XML Web Services to Order Processing
This lesson provides more detail about integrating XML Web services. For the
purpose of B2B trading partner integration, XML Web services are most
commonly used in order processing. However, students can integrate XML
Web services in almost any part of their business systems.

The following information is specific to individual pages in this lesson.
How BizTalk Server Can
Call XML Web Services

Check the Microsoft BizTalk™ Server 2000 Web site at
for white paper updates about the use of
XML Web services with BizTalk Server in order processing.

Considerations for
Integrating XML Web
Services with Commerce
Server

Although you can call an XML Web service from a Microsoft Commerce
Server 2000 pipeline, emphasize that students should do so only under very
specific conditions, which are mentioned on this page.

Lesson: Providing XML Web Services to Trading Partners
Students may want to create their own XML Web services and make them
available to their trading partners. This lesson discusses the design
considerations for doing so, along with a business justification for creating
XML Web Services and infrastructure requirements for making them available.


Module 8: Integrating XML Web Services in a B2B Solution

v

The following information is specific to individual pages in this lesson.
Considerations for

Hosting XML Web
Services
Summary: Integrating
XML Web Services

Unless time permits, avoid an in-depth discussion about high availability and
Web service architecture.
This summary page highlights the main design elements of the module. It is
intended to be a simple module review and a tool to help students prepare for
the final module and lab, where they analyze a new trading partner integration
scenario and create a B2B design plan.

Lab: Integrating XML Web Services
In this design lab, students examine how Adventure Works can integrate XML
Web services to streamline its order processing workflow. Students learn how
Adventure Works can automate aspects of its order processing and offer its own
XML Web services to trading partners.
Timing

The design lab is scheduled for 45 minutes. Divide students into pairs or small
teams, and ask them to spend 20 minutes reading and discussing the scenario.
Then, have each pair or team present its answers to the class.

Discussion

Although the lab scenario provides a clear path to certain design decisions, it
contains enough ambiguity to encourage student discussion and debate.
Students may disagree with the answers that are provided in the Delivery Guide
and the Student Materials compact disc. Disagreement is acceptable if students
can provide adequate business or technical justification. To increase student

involvement, ask a representative of each team to present the team’s answers to
the class and then defend the design.


vi

Module 8: Integrating XML Web Services in a B2B Solution

Customization Information
This section identifies the lab setup requirements for a module and the
configuration changes that occur on student computers during the labs. This
information is provided to assist you in replicating or customizing Microsoft
Official Curriculum (MOC) courseware.
This module contains a single paper-based design lab. There are no hands-on
labs in this module, and as a result, there are no lab setup requirements or
configuration changes that affect replication or customization.


Module 8: Integrating XML Web Services in a B2B Solution

1

Overview
!

Introduction to XML Web Services

!

Applying XML Web Services to Order Processing

!

Providing XML Web Services to Trading Partners
Supplier
Supplier

Business
Business
Logic
Logic

Other
Other
Business
Business
Systems
Systems
CRM
ERP
Inventory
Accounting
XML
Web
Service

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

Extensible Markup Language (XML) Web services enable different

applications to exchange information locally and over the Internet without
complex integration requirements. You can use XML Web services to integrate
your business systems with those of your trading partners; to apply XML Web
services to internal applications, such as order processing; and to provide valueadded services to trading partners who buy from you.
In a business-to-business (B2B) scenario, XML Web services can improve your
order processing workflow. You can integrate XML Web services that other
organizations develop, or you can develop your own XML Web services. To
enable your business partners to benefit from the XML Web services that you
develop, expose your XML Web services over the Internet.

Objectives

After completing this module, you will be able to:
!

Describe how to use XML Web services in a B2B scenario.

!

Decide how to integrate XML Web services in order processing.

!

Decide whether and how to make your own XML Web services available to
your trading partners.


2

Module 8: Integrating XML Web Services in a B2B Solution

Lesson: Introduction to XML Web Services
!

Challenges to Integrating Applications

!

What Are XML Web Services?

!

How XML Web Services Can Work in a B2B Solution

!

Elements of an XML Web Service Document

!

Reasons to Use XML Web Services in a B2B Solution

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

XML Web services enable trading partners to solve many of the challenges of
integrating applications and enable your business systems to take advantage of
services that other organizations provide.

Lesson objectives

After completing this lesson, you will be able to:
!

Explain the difficulties of integrating applications.

!

Describe XML Web services.

!

Describe how a typical XML Web service works in a B2B trading partner
integration solution.

!

Identify the elements of an XML Web service document.

!

Explain the benefits of using XML Web services in a B2B integration
solution.


Module 8: Integrating XML Web Services in a B2B Solution

3

Challenges to Integrating Applications

Supplier
Supplier

Internet

Order Processing Application
Order Processing Application
Subtotal: 500.00
Tax:

???

Total:

???

Tax Company

Common integration challenges
!

Programming languages and operating systems differ

!

The corporate firewalls prohibit RPC traffic

!

Locally installed COM components must be registered and

manually updated

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

For trading partners to integrate their business applications, the applications
must be able to communicate freely with each other, which can be difficult. In
the example shown in the slide, a supplier that uses an order processing
application receives a purchase order, but wants to obtain tax calculations over
the Internet from another application.

Platform incompatibility

Several major challenges exist when you exchange information externally. The
operating system or programming language of the order processing application
may be incompatible with the service that provides the data. For example, if the
order processing application uses Component Object Model (COM)
architecture, but the tax calculation application was developed on a different
platform, a third middleware application is necessary to enable the two
applications to communicate. Middleware applications are often expensive and
require significant programming knowledge to implement.

Firewalls prohibit RPC
traffic

Most corporate firewalls prohibit Remote Procedure Call (RPC) traffic because
of its inherent security risks. Even if both applications in the previous example
use COM architecture, for example, RPC traffic would still occur each time the
order processing client requests information from the tax application server.
The corporate firewall, however, would block the RPC calls.

Components must be
updated

Most locally stored components require continual monitoring for updates. To
eliminate the need for RPC traffic, the tax company in the previous example
can supply the necessary COM or COM+ components to suppliers, which
register and install the components in the order processing application.
However, when an update occurs, the supplier must obtain the updated files
from the tax company and then update the components manually.


4

Module 8: Integrating XML Web Services in a B2B Solution

What Are XML Web Services?
XML Web services:
!

Are XML-based units of application logic that provide
data and services to other applications

!

Enable applications to communicate over the Internet
regardless of operating system or programming
language
XML Web services
XML Web services

Internet

Supplier
Supplier
XML Web Service
Provider

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

XML Web services are XML-based units of application logic that provide data
and services to other applications. XML Web services enable applications to
communicate over the Internet regardless of operating system or programming
language.

Definition

An XML Web service is programmable application logic that applications can
access by using standard Internet protocols. XML Web services are defined by
public standards organizations, such as the World Wide Web Consortium
(W3C).
XML Web services combine the best aspects of component-based development
and the Internet. Developers can create XML Web services without knowing
how other applications will implement them. Applications call XML Web
services by using common Web protocols and data formats, such as Hypertext
Transfer Protocol (HTTP) and XML.

XML Web services
enable seamless

communication

XML Web services enable applications to make RPC-like calls over the Internet
and to share data. The calls can occur regardless of the operating system that
hosts the XML Web service or the programming language that was used to
create the XML Web service. By using XML Web services to share data,
different applications can be independent of each other, yet still work together
to perform a particular task.


Module 8: Integrating XML Web Services in a B2B Solution

5

How XML Web Services Can Work in a B2B Solution
Tax Company’s
Web Server
2
45.00 2

Order Processing Application
Order Processing Application
Subtotal: 500.00
Tax:

3
3

45.00

Shipping: 30.00
Total:

1
1

575.00

Internet
1
1
3
3

2
30.00 2
Shipping Company’s
Web Server

1. An application calls the XML Web services
2. The XML Web services perform the requested
calculations
3. The XML Web services send the calculated results to
the application
*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

Order processing is one of the most likely scenarios in which you integrate
XML Web services in a B2B integration solution.

Example of an XML Web
service

The preceding slide shows how XML Web services can function in an order
processing scenario. The order processing application receives a purchase order
(PO) for goods that totals $500. Before the supplier generates an invoice, the
order processing application adds any applicable tax and the appropriate
shipping charges.
To complete an XML Web service transaction in this example:
1. The application makes calls to XML Web services. The order processing
application invokes the tax and shipping XML Web services that your
organization integrated in its order processing application. The order
processing application prepares requests and transmits them by using HTTP
to the XML Web services that the tax and shipping companies provided.
2. The XML Web services execute. The XML Web service at each company
receives the request and makes the necessary calculations.
3. The XML Web services send the calculated results. Each XML Web service
prepares a response that includes the calculated data. It then encapsulates
the data with the necessary protocol and transmits the response back to the
order processing application by using HTTP. The order processing
application updates the purchase order with the information and then sends
the PO to the next step in the order processing workflow.


6

Module 8: Integrating XML Web Services in a B2B Solution

Elements of an XML Web Service Document
Request

POST /SalesTax.asmx
POST /SalesTax.asmx
HTTP/1.1 Host .…
HTTP/1.1 Host .…
<?xml version="1.0“ ?>
<?xml version="1.0“ ?>
<soap:Envelope …>
<soap:Envelope …>
<soap:Body>
<soap:Body>
<GetTax>
<GetTax>
Data request
Data request
<Sub>52.34</Sub>
<Sub>52.34</Sub>
to an XML
to an XML
<State>WA</State>
Web service
<State>WA</State>
Web service
</GetTax>
</GetTax>
</soap:Body>
</soap:Body>
</soap:Envelope>
</soap:Envelope>

Response

HTTP/1.1 200 OK.…
HTTP/1.1 200 OK.…
<?xml version="1.0“ ?>
<?xml version="1.0“ ?>
<soap:Envelope …>
<soap:Envelope …>
<soap:Body>
<soap:Body>
Data
Data
<GetTaxResponse>
<GetTaxResponse>
response
response
<Tax>4.34</Tax>
<Tax>4.34</Tax>
from an XML
from an XML
/GetTaxResponse>
/GetTaxResponse>
Web service
Web service
</soap:Body>
</soap:Body>
</soap:Envelope>
</soap:Envelope>

An XML Web service document contains:
! An HTTP header
! A SOAP wrapper

! An XML Web service request and response

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

An XML Web service call is a document that contains an HTTP header, a
Simple Object Access Protocol (SOAP) wrapper, and the XML data request and
response.

HTTP header

A typical XML Web service document contains standard HTTP headers that
send and receive information. The XML Web service uses HTTP to transmit
data between it and the requesting application. (In the example in the slide, the
HTTP header is abbreviated.) Although most XML Web services use HTTP,
they can use any transport protocol.

SOAP wrapper

SOAP is a lightweight protocol that is used to exchange XML messages. The
SOAP specification defines a set of rules for how you can use XML to
represent data. XML Web services use a SOAP wrapper to enclose the XML.
By wrapping all calls to and responses from XML Web services, SOAP enables
XML Web services to be independent of an operating system or programming
language. Other parts of the SOAP specification define an extensible message
format, conventions for representing RPCs that use the SOAP message format,
and bindings to the HTTP protocol.

XML Web service
request and response

The SOAP wrapper contains the request that the XML Web service client sends
to the XML Web service. The request describes the method, or operation, of the
XML Web service that the request invokes, and all arguments that the invoking
application passes to the XML Web service. The response instructs the
application that called the XML Web service to process the information that the
XML Web service returns.
Note For more information about HTTP and SOAP, see the World Wide Web
Consortium Web site at .


Module 8: Integrating XML Web Services in a B2B Solution

7

Reasons to Use XML Web Services in a B2B Solution
Benefits
Benefits

Business
Business

Technical
Technical

Ability to receive dynamic data upon request
Ability to receive dynamic data upon request
Access to data that is stored anywhere and on
Access to data that is stored anywhere and on
any platform

any platform
" Ability to easily create business logic
" Ability to easily create business logic
applications
applications
"
"
"
"

" Low integration and maintenance requirements
" Low integration and maintenance requirements
" Suitability for EAI
" Suitability for EAI
" Conformity with industry standards
" Conformity with industry standards

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

By using XML Web services, you can streamline business practices and add
value to your trading partners.

Business benefits

You can use XML Web services to enhance your current business processes
and to create new ones. XML Web services can offer the following benefits to
your business processes:
!

Dynamic data upon request. XML Web services can access dynamic, or
changing, data from other sources, including other organizations. For
example, an XML Web service can provide you with a tax rate based on a
price that you supply and can also gather the latest currency exchange rates.

!

Access to data anywhere, on any platform. Because XML Web services are
independent of operating systems and programming languages, and they are
designed to be distributed, the data that an XML Web service calls can
reside anywhere, on any platform. For example, an XML Web service can
retrieve the latest shipping costs from several freight lines, and then a
locally installed component that you provide can select the freight line that
offers the lowest cost, regardless of the platform that the freight line uses.

!

Integration of business applications. XML Web services are ideally suited
for using with internal business applications because you can integrate them
easily with dissimilar platforms and programming languages. For example,
you can create an XML Web service that calls information from your
Enterprise Resource Planning (ERP) system and sends it to your Microsoft®
Commerce Server 2000 and Microsoft SQL Server™ 2000 order
management system.


8

Module 8: Integrating XML Web Services in a B2B Solution

Technical benefits

The technical benefits of XML Web services are equally compelling:
!

Low integration requirements. Unlike COM and COM+ applications, XML
Web services do not require you to register and maintain dynamic link
library (DLL) files. And unlike RPCs, XML Web services use HTTP as the
transport protocol and do not require complex firewall configurations.

!

Suitability for EAI. Because XML Web services are independent of
programming languages and operating systems, they are well suited for use
with Enterprise Application Integration (EAI) systems. For example, an
organization may want to integrate a Java-based inventory control system
and a COM architecture-based ERP system in its Microsoft supplier
enablement solution. You can use XML Web services to provide data to the
ERP system, rather than use complicated and costly middleware software.

!

Compliance with industry standards. Microsoft .NET XML Web services
follow standards that are issued by major standards bodies, such as W3C.
XML Web services that developers create by using Microsoft
Visual Studio® version 6.0 with the SOAP Toolkit version 2.0, or by using
Microsoft Visual Studio .NET, are fully interoperable with any vendor,
platform, or programming language that follows the W3C standards.

Module 8: Integrating XML Web Services in a B2B Solution

9

Demonstration: Using an XML Web Service
Demonstration Steps
Demonstration Steps

1. Open the UDDI Web site at
1. Open the UDDI Web site at


2. Search for XML Web services offered by
2. Search for XML Web services offered by
Microsoft
Microsoft
3. Demonstrate the Best Bets service
3. Demonstrate the Best Bets service

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

In this demonstration, the instructor will show an example of a simple XML
Web service. Using the Universal Description, Discovery and Integration
(UDDI) Business Registry, you can gain access to an XML Web service that
Microsoft provides. This XML Web service offers you an easy way to find
information about a particular Microsoft product or technology on the
Microsoft Web site. In this case, you will see several hyperlinks on the
Microsoft Web site where you are most likely to locate information about
Microsoft BizTalk™ Server 2000.

Procedure

The following steps occur in the demonstration:
1. Open the Microsoft UDDI Web site at .
2. Click Advanced Search.
3. In the Search for box, type 08-146-6849
4. In the in box, select Business identifier, and then click the arrow button.
5. Click Microsoft Corporation.
6. Under Services, click Web services for smart searching.
7. Under Bindings, click the hyperlink next to the description Best Bets.
8. On the MSComSearchService Web Service page, click GetBestBets.
9. Under GetBestBets Web Method, in the Query box, type BizTalk Server
and then click Invoke.
10. Scroll down the XML document to view the information that the XML Web
service returned.


10

Module 8: Integrating XML Web Services in a B2B Solution

Lesson: Applying XML Web Services to Order Processing
!

Considerations for Selecting XML Web Services

!

How to Use UDDI to Locate XML Web Service

Information

!

How BizTalk Server Can Call XML Web Services

!

Considerations for Integrating XML Web Services with
Commerce Server

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

In a B2B integration scenario, the order processing workflow is the most likely
place for you to use an XML Web service because it can expedite your
processing, offer extra information, and provide other value-added services that
benefit your trading partners.
Before you use an XML Web service, carefully study the costs and benefits of
the service. You can use UDDI, a free online service, to discover XML Web
services that third parties offer. If you decide to use the service, you must
integrate the service with your order processing workflow. Both BizTalk Server
and Commerce Server can accommodate XML Web services in their order
processing workflows. Evaluate the capabilities of both applications to choose
the most appropriate one for your business and technical requirements.

Lesson objectives

After completing this lesson, you will be able to:
!

Balance the considerations for selecting an XML Web service.

!

Locate XML Web service information by using UDDI.

!

Choose between BizTalk Server and Commerce Server for integrating XML
Web services.


Module 8: Integrating XML Web Services in a B2B Solution

11

Considerations for Selecting XML Web Services
Considerations
Considerations

Business
Business

" Value proposition that the XML Web service
" Value proposition that the XML Web service
provides
provides
" How the XML Web service changes current
" How the XML Web service changes current

business and technical processes
business and technical processes
" Usage fees that the XML Web service provider
" Usage fees that the XML Web service provider
charges
charges

Technical
Technical

" The performance of the XML Web service
" The performance of the XML Web service
" The security requirements of data sent and received
" The security requirements of data sent and received
by the XML Web service
by the XML Web service
" The reliability of the XML Web service and your
" The reliability of the XML Web service and your
organization’s Internet connection
organization’s Internet connection

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

Before you decide on an XML Web service that suits your requirements,
consider several business and technical aspects of the service and its provider.

Business considerations

Business considerations include:

!

Value proposition. Examine the importance of the business problem that the
XML Web service solves and the value that it provides. Clear benefits can
include: Reduce costs that are associated with order processing, improve
services for trading partners, and gain an advantage over competitors.

!

How processes will change. How you implement XML Web services will
change your business and technical processes. The cost of change can be
considerable, especially if you replace a business process, COM component,
or application. Often, dependencies on an existing process are not apparent.
For example, your organization may rely on an individual who, unknown to
anyone else, manually corrects orders before she enters them in your
system. If you automate this process, any errors would be directly passed to
the XML Web service and result in misdirected orders.

!

Usage fees. The service provider can charge usage fees for the XML Web
service in one of several ways. For example, in a subscription service, users
pay periodic fees for the service, similar to a monthly charge for telephone
service. Or, users can pay a per-use fee each time they use an XML Web
service, similar to when you use a pay telephone to place a telephone call.
Many third parties have created payment models for XML Web services to
enable convenient billing.


12

Module 8: Integrating XML Web Services in a B2B Solution

Technical
considerations

Technical considerations include:
!

Performance. You must ensure that the performance requirements of your
order processing application are compatible with the performance that the
XML Web service provider offers. In particular, ensure that the
performance capacity of the provider’s platform and infrastructure is
adequate, and that you can accept the latency, or roundtrip time, between
your order processing application and the XML Web service.

!

Security. XML Web services have no inherent security. By default,
arguments that are passed to XML Web services and data that XML Web
services return are sent in plaintext. If you transmit customer data or other
sensitive data by using an XML Web service, you must make the necessary
security arrangements with the XML Web service provider. You can
encrypt the data that the XML Web service transmits by using SOAP
extensions. Or, you can secure the protocol that the XML Web service uses
to transport data—for example, by using Secure Sockets Layer (SSL) or
Transport Layer Security (TLS) over HTTP.

Note For more information about securing XML Web services by using SOAP
extensions, see Course 2524A, Developing XML Web Services.

Note For more information about securing XML Web services by using SSL,
see Q307267: How to Secure XML Web Services with SSL at
/>!

Reliability. Because you integrate an XML Web service in your own
business process, the reliability of the service can directly affect the service
that you provide to your trading partners. Ensure that the XML Web service
provider can guarantee an acceptable level of reliability. Also ensure that
your own organization’s Internet connection is reliable.


Module 8: Integrating XML Web Services in a B2B Solution

13

How to Use UDDI to Locate XML Web Service Information
Tasks
Tasks
Use a Web browser or programmatic tools to
Use a Web browser or programmatic tools to
search UDDI for XML Web services offered by
search UDDI for XML Web services offered by
other organizations
other organizations
For each XML Web service, research:
For each XML Web service, research:
" What the service provides
" What the service provides
" How to integrate the service
" How to integrate the service

UDDI

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

You can use UDDI to register your company and XML Web services in a
distributed database. Companies can then search over the Internet for your
services. Likewise, you can search UDDI to locate XML Web services that
other organizations offer.

Searching UDDI by
using a Web browser

You can locate XML Web service providers in UDDI by browsing the Web site
of a UDDI node, such as . You can locate an
organization’s profile in UDDI and browse the business services and XML
Web services that the organization offers. Or, you can search for keywords in
tModels. A tModel is a generic metadata structure in UDDI that organizations
can use to describe their XML Web services and B2B XML schemas.

Searching UDDI
programmatically

The UDDI Business Registry is programmatically exposed to make UDDI
easier to search. You can use either Visual Studio .NET or Visual Basic 6.0
with the UDDI software development kit (SDK) to search the UDDI registry for
XML Web services and integration information.
As more organizations use UDDI, business applications, such as ERP systems,
will likely include the capability to search UDDI for XML Web services as a
built-in feature.

Researching integration
information

After you locate an XML Web service, determine what it provides and how to
integrate it in your existing business systems or workflow. You can examine the
tModel for integration information, such as the Web Services Discovery
Language (WSDL). The WSDL describes the services that the XML Web
service offers and how the XML Web service client calls the service.
Note For more information about UDDI, see the UDDI Web site at
.


14

Module 8: Integrating XML Web Services in a B2B Solution

How BizTalk Server Can Call XML Web Services
BizTalk Orchestration Services can:
!

Process orders asynchronously

!

Process long-running transactions

!

Call XML Web services by invoking COM proxies

BizTalk Orchestration Services

XML Web service call
XML Web service call

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

BizTalk Server can orchestrate complex business workflows. Because BizTalk
Server can process orders asynchronously, it is a good choice for the integration
of XML Web services in order processing.

Asynchronous
processing

BizTalk Orchestration Services is a feature that can process purchase orders
asynchronously, or without regard to sequence. In asynchronous processing, the
failure of an XML Web service to respond to one PO processing event does not
disrupt other POs that follow.

Processing long-running
transactions

The response time of an XML Web service call can vary. BizTalk Orchestration
Services minimizes the use of server resources when it executes long-running
transactions by writing processing events to a SQL Server database while it
waits for the XML Web service to respond. This process is called dehydration.
BizTalk Orchestration Services automatically returns the transaction to memory
when the XML Web service responds, a process known as rehydration. BizTalk
Orchestration Services also provides advanced management for long-running

transactions, including nested transactions and transaction rollback.

Using COM components

BizTalk Orchestration Services calls XML Web services by invoking COM
components. Although BizTalk Server 2000 does not have built-in functionality
to invoke XML Web services, you can build COM components that act as
SOAP clients to invoke XML Web services. The SOAP Toolkit provides a
wizard to create the Web service proxy component.
Note For more information about using the Web Service Proxy Wizard, see the
link about the wizard under Additional Reading on the Web page on the
Student Materials compact disc.


Module 8: Integrating XML Web Services in a B2B Solution

15

Considerations for Integrating XML Web Services with Commerce
Server
!

Integrate XML Web services only if all three conditions
apply:
The order processing system
currently uses the Order
Processing pipeline in
Commerce Server
The XML Web service has a
low latency

The XML Web service is
highly reliable

Order
Order
Processing
Processing
pipeline
pipeline

XML Web
XML Web
service call
service call

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

Commerce Server Order Processing pipelines (OPP) are designed for
short-lived processes and high performance. Because the OPP processes orders
synchronously, or one at a time, order processing can slow or stop when
problems occur. For example, if an XML Web service problem disrupts the first
PO in a string of five POs, the remaining four POs are delayed until the first PO
proceeds, or you manually trigger them to continue.

Commerce Server and
order processing

Use Commerce Server 2000 only to integrate XML Web services under specific
circumstances. If you have not implemented the OPP in Commerce Server or

Microsoft Site Server version 3.0 Commerce Edition to process incoming
purchases, BizTalk Server is preferable for the integration of XML Web
services.

Conditions for use

Although you can use Commerce Server to integrate XML Web services, it is
recommended that you do so only if the following three conditions are met:
!

The order processing system uses the OPP in Commerce Server. If you
already use the OPP, you can integrate an XML Web service directly in a
pipeline component.

!

The XML Web service has a low latency. That is, the XML Web service
responds quickly. If the XML Web service has a high latency, it may
become a bottleneck in the OPP and prevent orders from being processed in
a timely manner.

!

The XML Web service is highly reliable. If the XML Web service does not
offer the level of reliability that your order processing system requires, it
may become a bottleneck in the OPP and cause order processing to slow or
stop.


16

Module 8: Integrating XML Web Services in a B2B Solution

Lesson: Providing XML Web Services to Trading Partners
!

Reasons to Provide XML Web Services

!

Considerations for Hosting XML Web Services

!

How You Make XML Web Services Available

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

If you identify business challenges that existing XML Web services cannot
solve, you may decide to create your own XML Web services. You may also
decide to provide those XML Web services to your trading partners so that they
can benefit from them.
Before creating your own XML Web services, identify your requirements and
design considerations for hosting XML Web services, and then examine how
the services can benefit your trading partners. Then, ensure that your partners
can gain access to your services.

Lesson objectives

After completing this lesson, you will be able to:
!

Describe reasons to provide XML Web services.

!

Explain the design considerations for hosting an XML Web service.

!

Describe how to make an XML Web service available for use by trading
partners.


Module 8: Integrating XML Web Services in a B2B Solution

17

Reasons to Provide XML Web Services
Benefits
Benefits
Customer Satisfaction
Customer Satisfaction

" Improve service to trading partners
" Improve service to trading partners
www.supplier.com

Tracking

Info

" Offer a new value-added business service
" Offer a new value-added business service

" Reduce customer service costs
" Reduce customer service costs

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

Providing your own XML Web services offers a way to distinguish your
organization from your competitors and provide better service to your trading
partners.

Business benefits

Three important reasons to provide your own XML Web services include:
!

!

Provide a new value-added business service. You may discover an
opportunity to provide a new service that benefits you or your trading
partners—for example, one that shows up-to-the-minute inventory levels.

!

Example of benefits

Improve or augment service to trading partners. You may find an
opportunity to improve a business system or replace a nonautomated
service. For example, you could process returned products by using an XML
Web service.

Reduce customer service costs. You may find a way to use an XML Web
service to automate certain labor-intensive tasks, such as providing reports
on current order status, which can reduce costs that are associated with
maintaining help resources.

Consider an organization where the sales representatives are frequently
interrupted by telephone calls from an important trading partner that wants to
know the status of orders that it submitted to a B2B marketplace. The
organization could develop an XML Web service so that any trading partner
can see the up-to-the-minute status of an order. Not only does the XML Web
service solve the immediate problem of disruption to the organization’s sales
representatives, it provides a new, valuable business service that other trading
partners can benefit from.


18

Module 8: Integrating XML Web Services in a B2B Solution

Considerations for Hosting XML Web Services
Internet
Secure the protocols
Secure the protocols

Add redundant Internet

Add redundant Internet
infrastructure for reliability
infrastructure for reliability

Trading
Trading
Partner
Partner

Supplier
Supplier

Routers

Scale out by
Scale out by
adding servers
adding servers

Servers hosting
XML Web services

Load balance your systems
Load balance your systems
for increased availability
for increased availability

Servers hosting
COM component
clusters

*****************************ILLEGAL FOR NON-TRAINER USE******************************
Introduction

Many of the issues that you consider before hosting an XML Web service are
the same as those you consider before using a third-party XML Web service.
Before you host your own XML Web service, consider the technical issues that
will affect your design.

Security

Because a value-added service will likely require the exchange of confidential
buyer and supplier information, you must ensure the security of the exchanged
information. Carefully consider what security precautions to take if your trading
partners submit confidential information, such as logon and password
information, or if you provide private data, such as order or payment details.
For example, you can secure the transport protocol by securing HTTP with SSL
or TLS. Or, you can encrypt the data that the XML Web service exchanges by
using SOAP extensions.

Reliability

Reliability refers to the likelihood that a service will fail. If your XML Web
service is unavailable for even a small amount of time, the frustration and
customer dissatisfaction that may occur can outweigh the benefits that you gain
from the majority of trading partners who use your XML Web service
successfully.
To improve reliability, you can use clustering to provide redundancy for
software and hardware failures. For example, you can use Microsoft
Application Center 2000 to cluster COM components, thereby increasing the

reliability of COM components that an XML Web service calls. You can also
increase hardware and software reliability, improve fault tolerance, and
strengthen Open Systems Interconnection (OSI) layer 3 and below Internet
infrastructure.
Note For more information about creating COM clusters in Application
Center 2000, see the Microsoft Application Center 2000 Resource Kit.


Module 8: Integrating XML Web Services in a B2B Solution

19

Scalability

Scalability refers to the enlarging of a segment of your infrastructure. It reflects
the ease with which you can add new hardware and software to accommodate
increased demand. If you anticipate increased demand from trading partners for
your XML Web services, consider scaling your XML Web service
infrastructure. For example, if you plan to host an XML Web service that
requires four CPUs per server, install Microsoft Windows® 2000 Advanced
Server, which permits up to eight CPUs per server, rather than installing
Windows 2000 Server, which is limited to four CPUs per server.

Availability

Availability refers to the ability of trading partners to always gain access to
your services, even during peak usage. Increased traffic and the processing
requirements of your XML Web services may also affect the availability of
your services. To ensure availability, consider using redundant or backup
connections in case your primary connection fails. Also ensure that your

network can accommodate increased traffic—for example, during busy or peak
seasons. You may want your XML Web service to make calls to a local COM
component. If so, use Application Center 2000 to perform component load
balancing.
Note For more information about building highly available Web solutions, see
Course 2088A, Designing a Highly Available Web Infrastructure.