18CSC343T

Web Services Development for

Games

UNIT 1
 Web Service
• A Web service, in very broad terms, is a method of communication
between two applications or electronic devices over the World Wide
Web (WWW)
• Web services are of two kinds: Simple Object Access Protocol (SOAP)
and Representational State Transfer (REST).
• The Web Server architecture includes a set of application services for
various application-specific functions.
• These application services include the following: Security and access
control. Session management service. File system service.
Types of web architecture

1.Monolithic architecture:
This architecture uses one code base in the application to structure a single
component providing high performance. ...
2.Microservices Architecture
3.Serverless Architecture:
 Web Service Architecture
• Web Service Architecture –
• Web service architecture refers to the structure and design principles
that govern the implementation of web services using protocols like
WSDL, SOAP, and UDDI to facilitate application integration on the
internet
Web service interacts among three roles
service provider, service requester, and service registry.
The interaction involves the three operations:
publish, find, and bind. These operations and roles act upon the web services
artifacts.

These service requestor uses a find operation to retrieve the service description
locally or from the service registry. It uses the service description to bind with the
service provider and invoke with the web service implementation.

.
Roles in a Web Service Architecture

There are three roles in web service architecture:

Service Provider
Service Requestor
Service Registry

Service Provider
From an architectural perspective, it is the platform that hosts the services.

Service Requestor
Service requestor is the application that is looking for and invoking or initiating an interaction

.
with a service. The browser plays the requester role, driven by a consumer or a program
without a user interface.

Service Registry
Service requestors find service and obtain binding information for services during development.
Operations in a Web Service Architecture

Publication of service descriptions (Publish)

Finding of services descriptions (Find)
Invoking of service based on service descriptions (Bind)

Publish: In the publish operation, a service description must be published so that a

service requester can find the service.

Find: In the find operation, the service requestor retrieves the service description
directly. It can be involved in two different lifecycle phases for the service requestor:
At design, time to retrieve the service's interface description for program development.
.
And, at the runtime to retrieve the service's binding and location description for
invocation.

Bind: In the bind operation, the service requestor invokes or initiates an interaction
with the service at runtime using the binding details in the service description to locate,
contact, and invoke the service.
Web Service Implementation Lifecycle

Requirements Phase

Analysis Phase

Design Phase

Coding Phase

Test Phase

Deployment Phase
.
Features/Characteristics Of Web Service
(a) XML Based: The information representation and record transportation
layers of a web service employ XML. There is no need for networking, operating
system, or platform binding when using XML. At the middle level, web offering-
based applications are highly interoperable.
(b) Loosely Coupled: A customer of an internet service provider isn’t
necessarily directly linked to that service provider
(c) Capability to be Synchronous or Asynchronous: Synchronicity refers to
the client’s connection to the function’s execution.
Asynchronous clients get their results later, but synchronous clients get their
effect immediately when the service is completed.
.
(e) Supports Remote Procedural Call: Consumers can use an XML-based
protocol to call procedures, functions, and methods on remote objects utilizing
web services. A web function can support RPC by offering its own services, n.
(f) Supports Document Exchanges: One of XML’s most appealing features is
its simple approach to communicating with data and complex entities. These
records can be as simple as talking to a current address or as complex as
Building blocks of web
A typical Web services architecture-based solution relies on de facto Web-
services standards such as XML, SOAP, WSDL, and UDDI, and on industry-
standard protocols such as HTTP and SMTP. These standards-based
technologies form the foundation for building a Web services architecture and
enabling Web services.

services?

.
Building blocks of web
XML
A general-purpose specification for creating custom markup languages. XML is
used to communicate between web services across standard protocols like
HTTP, TCP/IP, SMTP, or FTP.
SOAP
Simple Object Access Protocol is a lightweight protocol that uses XML to
exchange information between distributed applications. SOAP uses a standard
services?

packaging structure to transport XML documents over standard internet

technologies. SOAP also uses WSDL documents to describe how SOAP
requests and responses should appear.
WSDL
.
Web Services Description Language is an XML-based language that describes
web services. WSDL documents capture service descriptions that determine the
operations a web service provides.
Building blocks of web
UDDI
Universal Description, Discovery, and Integration is a standard that plays a key
role in web services.
REST
Representational State Transfer is a design technique for networked
applications that focuses on simplicity, scalability, and statelessness. RESTful
systems use conventional HTTP techniques like GET and POST.
WSIL
Web Services Inspection Language is a standard that plays a key role in web
services.
WS-I
.
Web Services Interoperability is a standard that plays a key role in web
services.
Web services can support more than one protocol, and the protocols supported
are published in the WSDL file
web services communication
Web services communication is the exchange of information between electronic
devices over a network. Web services are software functions that are always
available over the web.
FTP, HTTP is a file sharing protocol that runs over TCP/IP. But HTTP primarily
works over web browsers and is commonly recognizable for most users

.
Basic steps for implementing web services are
Create an application: Create a new application
Specify the proxy server address: Specify the address of the application
proxy server
Create a web service reference: Create a web service reference by supplying
the location of a WSDL document or by creating it manually

Test the web service: Test the web service

Here are some other things to consider when implementing web services:

Use SOAP
.
SOAP is a standard that allows web services to be accessed using internet
technologies. SOAP specifies a package of XML documents that can be
transported using internet protocols like HTTP(S) and SMTP.
Basic steps for implementing web services are
Creating Web Service References.

Creating a New Application.

Specifying an Application Proxy Server Address.

Searching a UDDI Registry for a Business Name.

Searching a UDDI Registry for a Service Name

.
Basic steps for implementing web services are
Use a services oriented architecture (SOA)
SOA allows for the flexible and standardized sharing or connecting of data and
resources.

Secure the web service

Use authentication mechanisms like API keys, JSON Web Tokens (JWT), or
OAuth to authenticate clients and protect sensitive data.

Use network protocols

Web services use protocols like HyperText Transfer Protocol (HTTP) and Java
.
Message Service (JMS) to receive requests and send responses. The WSDL
file publishes the protocols that a web service supports.
Basic steps for implementing web services are
Use a services oriented architecture (SOA)
SOA allows for the flexible and standardized sharing or connecting of data and
resources.

Secure the web service

Use authentication mechanisms like API keys, JSON Web Tokens (JWT), or
OAuth to authenticate clients and protect sensitive data.

Use network protocols

Web services use protocols like HyperText Transfer Protocol (HTTP) and Java
.
Message Service (JMS) to receive requests and send responses. The WSDL
file publishes the protocols that a web service supports.
WSDL introduction
 The full form of WSDL is web services description language which acts as an
XML-based language used to describe the operations and functionalities
of web service.
 web services are the type of software components that allow applications to
communicate with each other over any network typically using standard
protocols like HTTP.
 It is divided into separate individual sections which actually specify physical
details and logical design interface of a web service.
WSDL and its Documents
A WSDL document gives or defines the details of any web services. As I
.
mentioned below are the elements associated with it.
<types> - This particular element in web service is used to define the datatypes
used in web services which acts as an XML schema implementation.
<messages> - For each operation it outlines and defines the data elements in a
web service associated with it.
<binding> - We get to know what type of port is used and what data format can
WSDL
WSDL and its Documents
A WSDL document gives or defines the details of any web services. As I
mentioned below are the elements associated with it.
<types> - This particular element in web service is used to define the datatypes
used in web services which acts as an XML schema implementation.
<messages> - For each operation it outlines and defines the data elements in a
web service associated with it.
<binding> - We get to know what type of port is used and what data format can
be analyzed using this element.
<portType> - It describes all the operations used in a web service.
.
WSDL
Advantages of WSDL
Interoperability - It is a language-neutral and platform-independent. it allows
the integration of diverse systems. It means that web services using WSDL can
be consumed by applications developed in various programming domains and
platforms.
Documentation - This provides a clear and structured description of service
operations, their I/O parameters, and the protocols used. Documentation is
helpful for developer and clients when they access the web server.
Discovery - It also facilitates service discovery. Clients find easy-to-understand
web services by inspecting WSDL documents, which can be made public.
.
Tool - It is supported by a wide range of development tools which makes it
easier for developers to create, analyze, and publish web services. The tools
often generate code for working with WSDL documents.
Standardization - It helps to ensure consistency in describing web services, it
also simplifies creating and consuming web services.
WSDL
Disadvantages of WSDL
 WSDL documents are somewhat complex, especially for large web
services. The XML-based nature of WSDL maintains documents that may be
error-prone.
 WSDL consists of complex tooling and beginners may find it challenging to
create or modify WSDL documents.
 It has some alternative standards such as RESTful services, but some
developers prefer human-readable alternatives to WSDL.
 Version challenges by maintaining backward compatibility can be a
challenge, particularly when evolving a service over time.
.
 It creates additional overhead which can impact performance, especially in
bandwidth-constrained environments.
Non functional service description

.
Non functional service description?
Hosting environment: The security policy, quality of service levels, and privacy
policy

Message extensions: Parameters related to a required security protocol

Message syntax: How the service impacts the syntax of the message

Performance: How fast the service should perform

Scalability: How well the service can scale to meet demand

.
Usability: How easy the service is to use
Differences between WSDL 2.0 and WSDL 1.1

.
WSDL Document
 A WSDL document has a definitions element that contains the other five
elements, types, message, portType, binding and service.
 The following sections describe the features of the generated client code.
WSDL supports the XML Schemas specification (XSD) as its type system.

.
WSDL Document

.
WSDL Binding
 A WSDL binding describes how the service is bound to a messaging protocol,
particularly the SOAP messaging protocol. A WSDL SOAP binding can be
either a Remote Procedure Call (RPC) style binding or a document style
binding.

<binding name = "Hello_Binding" type =

"tns:Hello_PortType">

.
WSDL Binding
soap:binding: This element denotes that SOAP will be used to make the
binding available. The SOAP message format’s overall style is indicated via the
style attribute. An RPC format is specified by a style value of rpc.

soap:operation: This element denotes the connection between a certain

operation and a particular SOAP implementation. The SOAPAction HTTP
header should be used to identify the service, according to the soapAction
attribute.

soap:body: You can define the specifics of the input and output messages
.
using this element. In the case of HelloWorld, the body element defines the
namespace URN connected to the requested service as well as the SOAP
encoding type.
 WSDL Binding

binding name = "Greeting_Binding" type = "tns:Greeting_PortType">

<

<soap:binding style = "rpc" transport = "..."/>

<operation name = "Greeting">
<soap:operation soapAction = "Greeting"/>

<input>
<soap:body encodingStyle = "..." namespace =

</input>
<output>
.
"urn:examples:Greeting" use = "encoded"/>

<soap:body
encodingStyle = "..."
namespace = "urn:examples:Greeting" use = "encoded"/>
</output>
</operation>
</binding>
WSDL Tools
WSDL tools are used to create, edit, and test Web Services Description
Language (WSDL) files. WSDL tools can also help you generate documentation
for your WSDL files.

WSDL editor
A tool that allows you to browse, edit, and validate WSDL files. WSDL editors
can provide a graphical view of WSDL files, as well as a view that shows the
WSDL content as an XML file.

WSDL documentation tool

.
A tool that generates documentation for WSDL files, including annotations and
cross-references.
WSDL limitations
Operation type: All operations must be either RPC-encoded or doc/literal
Input and output: WSDL requires both input and output, so one-way
messaging is not supported

Overloaded operations: WSDL does not allow overloaded operations

Output mapping: WSDL does not support output mapping, which is the header
in a response
MIME and HTTP operations: WSDL only considers SOAP operations and
ignores MIME and HTTP operations

.
Mixed type messages: WSDL does not support mixed type messages
<wsdl:include> and <wsdl:types> elements: A WSDL file cannot have both a
<wsdl:include> and a <wsdl:types> element
SOAP-encoded structures and arrays: WSDL does not support SOAP-
encoded structures and SOAP-encoded arrays
UNIT-2
XML DOCUMENT STRUCTURE

.
XML DOCUMENT STRUCTURE

.
XML DOCUMENT STRUCTURE EXAMPLE
1.<?xml version="1.0"?>
2.<college>
3. <student>
4. <firstname>Tamanna</
firstname>
5. <lastname>Bhatia</lastname>
6. <contact>09990449935</
contact>
7. <email>tammanabhatia@abc.co
m</email>
8.
9.
10.
<address>
.
<city>Ghaziabad</city>
<state>Uttar Pradesh</
state>
11. <pin>201007</pin>
12. </address>
XML DOCUMENT STRUCTURE EXAMPLE
The image above represents books in this XML:
<?xml version="1.0" encoding="UTF-8"?>
<bookstore>
<book category="cooking">
<title lang="en">Everyday Italian</title>
<author>Giada De Laurentiis</author>
<year>2005</year>
<price>30.00</price>
</book>
<book category="children">
<title lang="en">Harry Potter</title>
<author>J K. Rowling</author>
<year>2005</year>
<price>29.99</price>
</book>
<book category="web">
.
<title lang="en">Learning XML</title>
<author>Erik T. Ray</author>
<year>2003</year>
<price>39.95</price>
</book>
XML Namespaces
Name Conflicts
In XML, element names are defined by the developer. This often results in a
conflict when trying to mix XML documents from different XML applications.
This XML carries HTML table information:
<table>
<tr>
<td>Apples</td>
<td>Bananas</td>
</tr>
</table>

<table>
<name>African Coffee Table</name>
.
This XML carries information about a table (a piece of furniture):

<width>80</width>
<length>120</length>
</table>
XML Namespaces
Solving the Name Conflict Using a Prefix
Name conflicts in XML can easily be avoided using a name prefix.
This XML carries information about an HTML table, and a piece of furniture:
<h:table>
<h:tr>
<h:td>Apples</h:td>
<h:td>Bananas</h:td>
</h:tr>
</h:table>

<f:table>
.
<f:name>African Coffee Table</f:name>
<f:width>80</f:width>
<f:length>120</f:length>
</f:table>
 XML Namespaces
XML Namespaces - The xmlns Attribute
When using prefixes in XML, a namespace for the prefix must be defined.
The namespace declaration has the following syntax. xmlns:prefix="URI".
<root>
<h:table xmlns:h="http://www.w3.org/TR/html4/">
<h:tr>
<h:td>Apples</h:td>
<h:td>Bananas</h:td>
</h:tr>
</h:table>

.
<f:table xmlns:f="https://www.w3schools.com/furniture">
<f:name>African Coffee Table</f:name>
<f:width>80</f:width>
<f:length>120</f:length>
</f:table>
</root>
 XML XML Schema
The XML Schema language is also referred to as XML Schema Definition (XSD).
XSD Example
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="note">
<xs:complexType>
<xs:sequence>
<xs:element name="to" type="xs:string"/>
<xs:element name="from" type="xs:string"/>
<xs:element name="heading" type="xs:string"/>

</xs:sequence>
</xs:complexType>
.
<xs:element name="body" type="xs:string"/>

</xs:element>
</xs:schema>
 XML Documentation and Navigation
All nodes have exactly one parent node. The following code navigates to the
parent node of <book>

Example

function myFunction(xml) {
var xmlDoc = xml.responseXML;
var x = xmlDoc.getElementsByTagName("book")[0];
document.getElementById("demo").innerHTML = x.parentNode.nodeName;
}
.
 SOAP
 Simple Object Access Protocol (SOAP) is a protocol for exchanging information
between applications over the internet.
 It's an XML-based protocol that's often used to implement web services.
 SOAP messages are sent from a sender to a receiver
 SOAP messages are made up of an envelope, header, and body.
•The envelope is the root element of the message and identifies it as
 a SOAP message.
•The header is optional and contains application-specific
information.
•The body contains the message being transported, including the
data and operation being invoked.
.
•SOAP messages can be combined to perform request/response
patterns.
 SOAP
Envelope: This specifies that the XML message is a SOAP message. A SOAP
message is an XML document containing a header and a body, both
encapsulated within the envelope. Any fault is included within the body of the
message.

Header: This part is optional. When present, it can provide crucial information
about the applications.

Body: This contains the actual message being transmitted. Faults are contained
within the body tags.
.
Fault: This optional section contains the status of the application and any errors.
It should not appear more than once in a SOAP message.
SOAP
Content-Type: application/soap+xml
<env:Envelope
xmlns:env="http://www.w3.org/2003/05/soap
-envelope">
<env:Header> <m:GetLastTradePrice
xmlns:m="Some-URI" />
</env:Header>
<env:Body>
.
<symbol xmlns:p="Some-URI" >DIS</symbol>
</env:Body>
</env:Envelope>
 SOAP
Works
SOAP messages are encoded in XML, which makes them portable and
system-independent.

SOAP messages are transmitted using HTTP, HTTPS, or other protocols.

SOAP messages are used to perform request/response patterns.

SOAP uses the same error and status codes as HTTP so that HTTP responses
can be directly interpreted by a SOAP module. Wire protocols

.
HTTP: The most common protocol used to transmit SOAP
messages. HTTP is an application layer protocol that is part of the
existing internet infrastructure.
HTTPS: Another protocol that can be used to transmit SOAP
 SOAP
SOAP Message Structure
The following block depicts the general structure
of a SOAP message −
<?xml version = "1.0"?> <SOAP-ENV:Envelope
xmlns:SOAP-ENV =
"http://www.w3.org/2001/12/soap-envelope"
SOAP-ENV:encodingStyle =
"http://www.w3.org/2001/12/soap-encoding">
<SOAP-ENV:Header> ... ... </SOAP-
.
ENV:Header> <SOAP-ENV:Body> ... ... <SOAP-
ENV:Fault> ... ... </SOAP-ENV:Fault> ...
</SOAP-ENV:Body> </SOAP_ENV:Envelope>
 SOA Enterprise service bus

•Communication: ESBs provide a platform for applications to

communicate with each other. This includes routing, message
transformation, and authentication.
•Integration: ESBs connect different applications and systems,
allowing them to exchange data and collaborate.
•Standardization: ESBs can enforce consistent data and
messaging formats across applications.
•Scalability: ESBs are designed to handle large volumes of data
and transactions. .
•Security: ESBs can provide security features like authentication
and authorization.
SOA Development life cycle
Steps in the SOA development lifecycle

Service-oriented analysis: Identify and model the organization's

business processes, domain, and services

Service-oriented design: Prepare and design the working plan, service

layers, and required interfaces

Service development: Develop the identified services

Specification review: Review the specifications and make changes if
needed
.
Approve specification: Approve the specifications
SOA Development life cycle
Steps in the SOA development lifecycle

Service-oriented analysis: Identify and model the organization's

business processes, domain, and services

Service-oriented design: Prepare and design the working plan, service

layers, and required interfaces

Service development: Develop the identified services

Specification review: Review the specifications and make changes if
needed
.
Approve specification: Approve the specifications
.
 SOAP Error Handling
SOAP error handling uses a Fault Envelope to send back error
information to a client when a SOAP message is processed
incorrectly.
The Fault Envelope contains a SOAP Fault, which is a standardized
way to return exception information for Web Services.
How SOAP error handling works
When a server processes a SOAP message and encounters an
error, it constructs a SOAP Fault.
The SOAP Fault is sent back to the client.
The Fault message contains standardized elements, including

.
<Message>, <Code>, <ErrorCode>, and <ErrorMessage>.
The <ErrorCode> element contains an error code, and the
<ErrorMessage> element contains a string describing the error.
UNIT-3
.
 SOAP Registering and discovering Service
 Service registration and discovery is the process of registering a
service's location in a central registry and then using that
information to find other services.
 This process enables services to communicate with each other
without hardcoded addresses.
 Service registry: A centralized database that stores information
about services and their locations
 Service discovery: The process of finding services using the
service registry
 Service registration: The process of registering a service's

.
location in the service registry
 SOAP Role of Service Registering
 Store information: Service registries store information about
services, such as schemas, artifacts, and API specifications
 Find services: Developers can use service registries to find
services that they can reuse in their applications.
 Validate schemas: Service registries can validate schemas and
detect errors in data.
 Enforce rules: Service registries can enforce rules for service
communication.
 Enable service composition: Service registries can help
developers locate services for reuse and enable service
composition.
.
 Enable dynamic interaction: Service registries can store
service descriptions that runtimes use to enable dynamic
interaction between services.
 SOAP Service Discovery
 Service discovery is the process of automatically finding and
connecting devices and services on a network. It's used to
reduce the amount of manual configuration required by
administrators and users.
 Service catalog
A service catalog stores a record of all services in a network. It acts
as a single source of truth that allows services to communicate and
query each other.
 Service registry
 Service location

.
 UDDI
 Universal Description, Discovery, and Integration (UDDI) is a
service that helps users find web services and web service
providers. It uses XML to describe and discover web services in
an internet topology.
How UDDI works
•Publish information
Businesses register with a UDDI registry and publish information about their we
•Search for services
Users can search for services by keyword, category, or business name
•Evaluate service details
Users can review technical information and other details to determine if the ser
•Integrate the service
.
Users can use binding templates to integrate the service into their application o
 UDDI ARCHITECTURE
 Service discovery is the process of automatically finding and
connecting devices and services on a network. It's used to
reduce the amount of manual configuration required by
administrators and users.
 Service catalog
A service catalog stores a record of all services in a network. It acts
as a single source of truth that allows services to communicate and
query each other.
 Service registry
 Service location

.
UDDI ARCHITECTURE

.
 UDDI ELEMENTS
UDDI Specification: It consists of UDDI Operators, UDDI
Programmer's API (API defines sets function that uddi registry
support e.g. publishing data) and UDDI Data Structures (such as
XML structures). Now a days UDDI Version 3.0.2 is mostly used it
describes the Web services and UDDI registry.
UDDI Schema: Schema is an abstract representation of an object's
characteristics and relationship that can describe another
objects. This means that uddi schema defines resources and
characterstics and relationship of another resources.
UDDI Regitery: UDDI Business Registry also called as UBR. UBR

.
consist of multiple business registry that synchronize uddi data
through replication. UDDI Registry is one by which web services list
themselves on the internet.
UDDI DATA MODEL
 Universal Description, Discovery, and Integration
(UDDI) specification defines a way to publish and
discover information about Web services.
 UDDI has two functions: It is a SOAP-based protocol
that defines how clients communicate with UDDI
registries. It is a particular set of global replicated
registries.

.
UDDI DATA MODEL
.

.
UDDI DATA MODEL
.
UDDI includes an XML Schema that describes the following data
structures −
• businessEntity
• businessService
• bindingTemplate
• tModel
• publisherAssertion
businessEntity Data Structure
The business entity structure represents the provider of web
.
services. Within the UDDI registry, this structure contains
information about the company itself, including contact
information, industry categories, business identifiers, and a list of
services provided.
UDDI DATA MODEL
.

.
UDDI DATA MODEL
.

.
 UDDI UDDI - Interfaces
The
. Publisher Interface
get_authToken − Retrieves an authorization token. All of the Publisher
interface operations require that a valid authorization token be
submitted with the request.
• discard_authToken − Tells the UDDI registry to no longer accept a
given authorization token. This step is equivalent to logging out of the
system.
• save_business − Creates or updates a business entity's information
contained in the UDDI registry.
• save_service − Creates or updates information about the web
services that a business entity provides.
• save_binding − Creates or updates the technical information about a
web service's implementation.
save_tModel − Creates or updates the registration of abstract concepts managed
by the UDDI registry.
delete_business − Removes the given business entities from the UDDI registry
 UDDI UDDI - Interfaces
The
. Publisher Interface
delete_service − Removes the given web services from the UDDI registry
completely.
delete_binding − Removes the given web services technical details from the UDDI
registry.
delete_tModel − Removes the specified tModels from the UDDI registry.
get_registeredInfo − Returns a summary of everything the UDDI registry is
currently keeping track of for the user, including all businesses, all services, and all
tModels.
set_publisherAssertions − Manages all of the tracked relationship assertions
associated with an individual publisher account.
add_publisherAssertions − Causes one or more publisherAssertions to be added
to an individual publisher's assertion collection.
delete_publisherAssertions − Causes one or more publisherAssertion elements
to be removed from a publisher's assertion collection.
 UDDI UDDI - Interfaces
T
. he Publisher
Interface
get_assertionStatusReport − Provides administrative support for determining the
status of current and outstanding publisher assertions that involve any of the
business registrations managed by the individual publisher account.
get_publisherAssertions − Obtains the full set of publisher assertions that is
associated with an individual publisher account.
UDDI UDDI - Interfaces
. he Inquiry Interface
T

find_binding − Returns a list of web services that match a particular set of criteria
based on the technical binding information.
find_business − Returns a list of business entities that match a particular set of
criteria.
find_ltservice − Returns a list of web services that match a particular set of
criteria.
find_tModel − Returns a list of tModels that match a particular set of criteria.
get_bindingDetail − Returns the complete registration information for a particular
web service binding template.
UDDI UDDI - Interfaces
. he Inquiry Interface
T

get_businessDetail − Returns the registration information for a business entity,

including all services that entity provides.
get_businessDetailExt − Returns the complete registration information for a
business entity.
get_serviceDetail − Returns the complete registration information for a web
service.
get_tModelDetail − Returns the complete registration information for a tModel.
find_relatedBusinesses − Discovers businesses that have been related via the
uddi-org:relationships model.