Integration Schemas
86
Integration Guide
Service Level Schemas
Service level schemas apply to enterprise services, object structure services, and
standard services. The same schema describes enterprise services and object
structure services. A different schema describes standard services.
Enterprise services, object structure services, and standard services use objects
and object structures as input and output for the operations they support.
Multiple services can perform the same operation using the same input and
output. For example, two AddMXPERSON services can have different processing
rules but the same input (the MXPERSON object structure). The input and output
schema types for enterprise services and object structure services are generally
reusable.
The system defines the input and output for publish channels and invocation
channels. This information is available to anyone who must implement these
channels to invoke external services or to map to other output formats.
Schema Name
The naming convention for object structure schemas and enterprise services
schemas is application service name + Service, for example, PERSONService.xsd.
The naming convention for service level schemas is object structure + Service, for
example, MXPERSONService.xsd.
Schema Generation
Predefined service schema files are not provided. When you deploy a service, a
service schema file is generated for the associated object structure, if one does not
exist already.
The following conditions initiate a system file generation:
T You generate the service-level schema by using the Select Action menu in the
Web Services Library application
T A Web service is deployed
The generated schema files are under the root/schema/common/service directory.
All service level schemas include the metadata schema file and the applicable
object structure and object schema files.
Service Level Schema Elements
One schema file is generated per object structure with multiple data types within
each file. Each data type corresponds to each input and output operation that can
be deployed or processed as a service. Different services reuse the data types in
these schemas. No one service uses all the data types in a single schema.
The service level schemas contain the following types, which use MXPERSON as
an example.
T CreateMXPERSON
T CreateMXPERSONResponse
T DeleteMXPERSON
To Next Page
Loading...