Example: Reservation event functional type |
|
|
|
Service Definer allows you to define technical interfaces so that you can build an integration layer between different systems. A technical interface defines the characteristics of integrations between systems: the operations themselves, whether operations are read or write, data transport layers, data formats... Usually the data format of choice when working with technical interfaces is XML or JSON. In Service Definer you can use a structure as input/output of your service, and Service Framework will create the XML (or JSON) message for you at runtime. A travel agency wants to create a technical interface for message events that follow a participant in a reservation for a scheduled tour. The technical interface is a REST service. This REST service allows the operations of participant reservation, participant arrival, and participant departure. Each operation involves data in XML format. Participant reservation is the operation of registering a new participant in a reservation. It involves data such as the following.
Participant arrival is the operation of registering that a participant has arrived at a specific location to join a group (for example, when the tour starts). It involves data such as the following.
Participant departure is the operation of registering that a participant has left the group (for example, at the end of the tour). It involves data such as the following.
The following example will only show how to implement a functional type for a structure that has reusable attributes. First create a REST Service for each operation that will insert the above XML data in a PARTICIPANT_EVENT table. Use ParticipantRegistrationEvent, ParticipantArrivalEvent and ParticipantDepartureEvent as names for your generated structures. Since all XML messages have common attributes, the generated structures have also common fields. You can create a new structure ParticipantEvent that holds the common attributes. As a next step, you can create a functional type based on the new structure and use it in each participant event structure as a functional type. This way, if the ParticipantEvent changes, all types of participant events will change also.
See also |
|
