The fourth step of the wizard requires the service developer to supply the domain model which the new data service will expose to the grid. Domain Models define the classes, their attributes, and relationships such that data services may be discovered by the types they expose, and CQL queries can be formulated without a priori knowledge of an arbitrary data service's contents.
The domain model panel contains a drop-down menu at the top which specifies the Domain Model Source. This wizard provides three potential sources for the domain model:
- Default XMI
This setting directs the wizard to convert the XMI model which it detects is used by the caCORE SDK system specified in step 2 as the domain model. The XMI will be converted to a domain model XML document.
This option allows the service developer to specify a pre-generated domain model XML document from the local file system. This might prove useful for developers who have previously generated a data service and wish to re-use the model, or have created a custom model.
This option lets the service developer select a project and packages from the cancer Data Standards Repository (caDSR) and generate a domain model extract from it for use in their data service.
- For this tutorial, select Default XMI as the Domain Model Source.
The wizard will attempt to populate as many of the fields on this page as possible, and the ones it cannot will be highlighted in red. Typically, only the Project Version and Exclude Packages fields will require your attention. Only the Project Name, Project Version, and Exclude Packages fields are editable on this page.
- For this tutorial, enter 4.1 in the Project Version field. Set the Exclude Packages value to
- Leave the other fields as they are.
Click Next: Schemas to convert the XMI file to a domain model and continue to the last step of the wizard.