Maintaining the Core – Service Repository - Applied SOA Patterns on the Oracle Platform - page 347

resource, customer, and so on. Information about the transporting Object is one of the
mandatory parts of message identification, used for Object filtering, routing, and trans-
formation (the last one naturally shall be avoided). This information must be presented in
the MessageHeader together with ObjectContext for the realization of the Event
Identification and State Messaging pattern.
The properties of the object are OBJECT_ID , OBJECT_NAME , and UML_REF .
Service/Task
The most simple part of the taxonomy is defined in SOA terms. We register the executable
module that can be a part of the composition (fulfill the role of composition member) and/
or something we can dynamically execute (for instance, the rule function). Thus, a role
cannot be a property of a service as it's related to a service within the composition. Engine
and Model are the Service properties. Part of the design-time service definition is a regis-
tration of service event messages, provided to the runtime log. This information will be
used for runtime Audit and testing purposes.
Obviously, services can be a part of the bigger composition (SCA), which is also a ser-
vice, and can be registered in the repository for further reuse.
The properties of the Service/Task are SERVICE_ID , SERVICEMODEL_ID ,
ENGINE_ID , SERVICE_NAME , and SERVICE_DESCRIPTION .