Service provider

The service provider is the code that implements the service. The service provider includes the interface specification (also called the service contract) and the related WSDL file.

The service provider also includes everything necessary to produce the WSDL file:

Rational® Rhapsody® uses the stereotype <<servicePackage>> to indicate a UML/SysML package that contains the model elements necessary for creating the WSDL file that includes the package with the service provider and the service contract. The stereotypes <<serviceProvider>> and <<serviceContract>>, respectively, indicate these classes. To define the data types, the WSDL files also include XML schemas and XSDs.

This Block Definition diagram example shows a typical collaboration in which the stereotypes indicate the service contract, service consumer, and service provider.

Collaborations in a top level or System of Systems model allow the systems engineers to confirm the data types, interfaces, and basic block behavior before generating the WSDL file. Executing the model ensures that both sides of the interface interpret messages the same way. This avoids consistency errors that, otherwise, might not be discovered until late in the integration phase.

The systems engineers and designers might model data types using the SysML units and value types, as shown the Block Definition diagram example (from Rational Rhapsody System samples "NetCentricWeatherService" project):

The Generate WSDL Specification tool uses these data types to create the schema information within the WSDL file.


Feedback