Service level schemas

Service level schemas apply to object structure services, enterprise services, and standard services. One schema describes enterprise services and object structure services. A different schema describes standard services.

Object structure services, enterprise 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.

Predefined input and output for publish channels and invocation channels are used to invoke external services or to map to other output formats.

File names and location

The naming convention for object structure schemas and enterprise services schemas is application service name + Service, for example, PERSONService.xsd where PERSON is the application service name.

The naming convention for service level schemas is object structure + Service, for example, MXPERSONService.xsd.

The schema files are located in the <root>/schema/common/service directory.

Schema generation

Predefined service-level schema files are not provided. When you deploy a web service, a service-level schema file is generated for the associated object structure, if one does not exist. You can also generate a service-level schema by using an action in the Web Services Library application

All service level schemas include the metadata schema file and the applicable object structure and object schema files.

Schema content

One schema file is generated for each 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.

Service-level schemas contain the following types, using the MXPERSON example:

  • CreateMXPERSON
  • CreateMXPERSONResponse
  • DeleteMXPERSON
  • InvokeMXPERSON
  • InvokeMXPERSONResponse
  • PublishMXPERSON
  • QueryMXPERSON
  • QueryMXPERSONResponse
  • SyncMXPERSON
  • UpdateMXPERSON