This step will be used to gather additional information needed to generate BO from selected MetaSolv classes. After the information has been gathered, an IBM WBI business object is generated. This is a two step process. The first step selected the common properties like BO prefix and supported verbs for the selected MetaSolv classes and if the ODA should allow the user to generate verb level AppSpecificInfo. Second step is to get the verb level Application Specific Information for each generated BO.
Figure 7. Step 5 - Select verbs
Prefix is used to set the prefix for the Business Objects to be generated. In this example it is MetaSolv_
Verbs is a drop down check list of verbs that will be applied to all the selected objects.
GenerateVerbAppInfo Set this value to true if you would like to specify verb level AppSpecificInfo during generation.
For details about business object verbs for the MetaSolv connector, see Creating or modifying business objects
For each class selected in Step 1: Common BO properties screen, a separate window appears where you specify the method sequence that must be executed for the verb. This window is displayed only if the property GenreateVerbApp is set to true in the previous step
Figure 8 illustrates this screen for the selected verbs of the PSRCustomerAccount business object created in Figure 5 and Figure 6.
The format for verb level App Specific Info is MO_MetaSolv_<verb name>_<BOName> where <verb name> is the name of the selected verb, Create, Retrieve etc.
<BOName> is the name of a business object like MetaSolv_PSRCustomerAccount.
The format of the attribute level App Specific Info is
<MetaSolv Data Type>:<Class Name> where
<MetaSolv Data Type> is an integer corresponding to MetaSolv
data type in the following table.
MetaSolv Application Data type | ASI Integer valule |
---|---|
Int, long | 0 |
float | 1 |
char | 2 |
string | 3 |
DateStruct | 4 |
Enumeration | 5 |
Object | 6 |
Union | 7 |
Sequence | 8 |
boolean | 9 |
<Class Name> is the name of the class including the full package name. This is required only if the attribute is a complex attribute. If the attribute maps to a class like PSRBillingAccountUnion the ASI would be:
7:MetaSolv.CORBA.WDIPSR.PSRBillingAccountUnion
The BO ASI will not be set by the ODA. It must be manually set by the users. Please refer to the MetaSolv adapter guide for information on format of BO ASI.
The Business Object Wizard - Step 6 of 6 - Save business objects screen appears.
Figure 9. Step 6 - Save business objects screen
You must open the business object in a separate window within Business Object Designer, and, after specifying a key for the top-level business object, you can save the generated business object definitions to a file.
To open the business objects in separate windows:
To save the business objects to a file (only after you a have specified a key for the parent-level business object, as illustrated in Figure 9):
Business Object Designer saves the files to the specified location.
If you have finished working with the ODA, you can shut it down by checking Shutdown ODA MetaSolv ODA before clicking Finish.