The steps outlined in this section include sample screens of an Object Discovery Agent that converts Roman-army soldiers (in XML format) to business object definitions.
Business Object Designer Express invokes Business Object Wizard, which displays the first dialog box in the wizard, Select Agent, shown in Figure 35.
Business Object Wizard identifies each running ODA by the name specified for the AGENTNAME variable of its startup script or batch file. This sample ODA is named Roman.
The first time you use a particular ODA, you specify values for each of its configuration properties. After doing so, you can save the property values in a named profile by clicking the Save button. The next time you use the same ODA, you can select the saved profile from the Select profile box. For more information, see "Entering values and saving a profile".
Important |
---|
If the ODA is unable to proceed when you click Next, verify that the ODA message file you have specified for the MessageFile configuration property exists in the ProgramDir\ODA\messages directory. For more information, see Specifying the ODA message file. |
Figure 38. Initial Select Source dialog box
The nodes of the source-node hierarchy can be table names, business object names, schema, or functions, depending on the ODA's data source. The ODA illustrated in these steps generates nodes from objects within an XML file called RomanArmy.xml. Figure 38 shows the single top-level source node for the Roman general specified for the Army general configuration property (see Figure 37).
Figure 39. Select Source dialog box with source nodes expanded and selected
To expand a source node to display its children, do either of the following:
Figure 40. Context menu for a node
To expand the selected node, click Retrieve all items. Business Object Wizard displays the next level of source nodes: the child nodes for the expanded parent node. To open lower levels, repeat this process.
Figure 41. Confirming the objects for which to generate business object definitions
If your selection is not correct, click Back to return to the previous dialog box and make the necessary changes.
Figure 42. Generating the definitions
If the ODA needs additional information, Business Object Wizard prompts you for this information by displaying the BO Properties dialog box. However, this sample ODA does not require additional information. Therefore, this dialog box does not open. For more information about the BO Properties dialog box, see "Providing additional information"..
Important |
---|
If the ODA generates a business object definition from a data-source object that does not identify a key element, this business object definition will not have a key attribute. Every business object must have at least one key. If the ODA might have generated business object definitions that do not include keys, you might want to choose the "Open the new BOs in separate windows" option instead of saving the business object definitions. Within Business Object Designer Express, you can verify that each business object definition has a key attribute, adding one if none exists. Business Object Designer Express does not allow you to save any business object definition that does not include a key. |
Figure 43. Saving the business object definition
Click Finish to save the business object definitions or Cancel to exit without saving these definitions. In either case, Business Object Wizard disconnects from the ODA. This dialog box also provides the option to have Business Object Wizard shut down the ODA after it disconnects. If you no longer need to use the ODA, click this option.
After you click Finish, if you have told Business Object Wizard to save the business object definitions to a file, Business Object Wizard provides a browse window that allows you to specify the name of this file, where to save it, and what format to use (text file or InterChange Server Express-specific format).
You have now successfully created business object definitions using an Object Discovery Agent.