uCosminexus Service Platform, Overview
You can invoke a service component by using a message different from the message format of the service component side, or receive a message different from the message format of the service component side as a response. To do this, you need to define standard message format in the development environment. In the development environment, you also need to define a data transformation definition that defines the transformation rule for standard message format and service component message format. You can invoke a service component by transforming messages in standard message format to messages in service component message format. The following figure shows the relationship between standard message format and a data transformation definition.
Figure 2-6 Relationship between standard message format and a data transformation definition
Even for multiple adapters, you can define the same standard message format A and individual data transformation definition for each service adapter for Service1, Service2, and Service3 (see the figure below). Thus, when sending a request from the service requester, you can use the same request message by simply changing the service name (such as Service1).
Figure 2-7 Process flow when the same standard message format is defined in multiple service adapters
For details about standard message format and service component message format, see Chapter 4. Creating a Message Format in the Service Platform Basic Development Guide. For details about data transformation definitions, see 6.3. Defining data transformation in the Service Platform Basic Development Guide.
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.