396 WebSphere Business Integration Adapters
11.Highlight the row for ObjectEventId by clicking the far left number.
12.Right-click and select Insert Above (Figure 22-18 on page 394).
13.In the Type column select the RM_Apartment type.
14.Name this Attribute, RM_Apartment.
15.Set the Cardinality to 1, meaning only one occurrence of this child object is
allowed. Each tenant has only one apartment record.
16.Repeat this for the RM_Maintenance, setting the Cardinality to N, meaning for
an apartment, there can be multiple maintenance records.
17.Set the Foreign Key flag on for the ApartmentId attribute.
18.Update the application-specific information to indicate that this attribute is part
of a foreign key, with the foreign key attribute being RM_Apartment.Id.
19.Change the application-specific information about the EMail attribute from
EMail to Email (with a lowercase letter “m”). All the application-specific
information is case-sensitive.
20.Save this business object.
If you now expand the child objects within the parent object, you see the correct
hierarchical structure of the tenant object with all of the keys and foreign keys set
correctly.
Double-check that all business objects have been saved to the project (ICL) and
to the repository files.
The business objects are now ready for use.

Get WebSphere Business Integration Adapters: An Adapter Development and WebSphere Business Integration Solution now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.