Setting up multiple cases
You use the case selection feature when you need to migrate data from multiple classes in the source into multiple instances in a single target class. The case selection feature lets you create a set of expressions that apply on a case-by-case basis to the same target class.
For example, suppose in the target database that you have the class Adapter, which holds data from the following classes in the source: Sound Adapter and Video Adapter. In the target, you can create two cases for the class Adapter, one for the sound adapter and one for the video adapter. This method migrates multiple instances of adapters, some of which are video adapters and some are sound adapters:
- An adapter in the source meets the criteria specified for case 0 (in Integration Composer, the first case is always case 0). In this example, the first case is Sound Adapter. Integration Composer creates an instance in the target based on the expression defined for the sound adapter in case 0.
- An adapter in the source meets the criteria specified for case 1, which in this example is Video Adapter.Integration Composer creates an instance in the target based on the expression defined for the video adapter in case 1.
If you need multiple cases in the child class but not in the parent class, then create only one case (case 0) for the parent class. All instances created for the child class are based on the parent class.
However, if you need multiple cases in the child class and parent class, the same number of cases must exist in the child and parent classes. That is, for every case of a child class, the corresponding number of cases is required in its parent class. For example, if you create three cases (0, 1, and 2) for a child class, then create three cases for the parent class.
The maximum number of cases that you can create for a class is 100 (cases 0 - 99).