Service data objects
Service data objects complement Service Component Architecture. Service Component Architecture defines the services as components and the connectivity between them. Service data objects define the data flowing between components.
Each component passes information as input and output. When a service is invoked, data objects
are passed as an XML document with document-literal encoding when a WSDL port type is used, or as a
Java™ object when a Java
interface is used. Data objects are the preferred form for data and metadata in Service Component
Architecture services. Similar to components, service data objects separate the data object from its
implementation. For example, a component interacts with purchase orders while the purchase order
itself might use Java Database Connectivity (JDBC) or Enterprise JavaBeans (EJB) to perform the
updates to the data. Service data objects let the integration developer focus on working with
business artifacts. In fact, service data objects are transparent to the integration developer. They
are defined bya Java Specification Request (JSR) for service data objects. For more information see
the service data
objects topic.
Tip: By
default, the preserve-milliseconds-for-ais property is set to
true so that the requests that are sent to advanced integration services (AIS) and
the responses that are received from them keep the milliseconds in
datetime values.
If your service does not need to display milliseconds (for example, for compatibility with
applications or services that do not return milliseconds), set the
preserve-milliseconds-for-ais property to false in your
100Custom.xml configuration file and restart the server.In the following diagram, service data objects are passed from an external service to an export, from an export to a component, from a component to a component, from a component to an import, and from an import to a service. Imports and exports are discussed in a subsequent imports and exports section.
