Software Services profile to SoaML profile mapping

This topic describes how Software Services profile elements map to SoaML profile elements when you migrate a UML model from the Software Services profile to SoaML.

The following table lists how the older Software Services profile maps to the newer SoaML profile.

Note: Elements that do not appear in the table have an exact one-to-one mapping between the profiles.

Software Services profile	SoaML profile
`Message Message::encoding`	`MessageType MessageType::encoding`
`MessageAttachment MessageAttachment::encoding`	`Attachment Attachment::encoding`
`Service Service::allowedBindings`	`Service // where the port type is an Interface Request // where the port type is a Class` Note: «Service» or «Request» can be typed by an interface or class, or stereotyped as a «ServiceInterface». The Request element has a value of isConjugate=true and switches the calculation of provided and required interfaces for the port and component.
`ServiceChannel ServiceChannel::binding`	`ServiceChannel`
`ServiceCollaboration ServiceCollaboration::strict ServiceCollaboration::binding`	`Collaboration Collaboration::isStrict` Note: This element can be either a ServiceContract element or ServicesArchitecture depending on what the service collaboration models.
`ServiceConsumer`	`Participant`
`ServiceGateway`	`ServiceChannel`
`ServiceModel`	`No longer needed`
`ServicePartition`	`Participant`
`ServiceProvider ServicePorvider::allowedBindings ServiceProvider::location`	`Participant`
`ServiceSpecification ServiceSpeicification::published ServiceSpeicification::source ServiceSpeicification::status`	`ServiceInterface //`
`SpecialStatus`
`PolicyStatment`

Feedback