If the JDBCODA needs additional information, Business Object Designer displays the BO Properties window, which prompts you for the information.
In the BO Properties window, enter or change the following information:
The default is Yes.
Figure 10. Associating Stored Procedures with Stored
Procedure Attributes
The stored procedure attributes to be added to the business object can be associated with one of the stored procedures in the database in that schema. You can choose a stored procedure from a drop down list of all stored procedures in the database in that schema, against each stored procedure attribute. This information will generate the necessary ASI information for that attribute.
The ASI (application-specific information) for the object level will look like TN=tableName
And for the attribute level, the ASI will look like CN=ColumnName
If a business object is being generated from a stored procedure, and if JDBC Adapter stored procedure attributes, such as SPForCreate, are associated with it, then the ODA provides a list of all stored procedure names in that schema against the stored procedure attributes and enables you to associate the required stored procedure with the business object. This will generate the ASI for the JDBC Adapter stored procedure attribute as follows:
SPN=stored procedure Name; IN=a1:a2; OUT=b1:b2; IO=c1:c2
Where IN means the parameter of the stored procedure is INPUT type, OUT means the parameter is OUTPUT type, and IO means it is INPUT/OUTPUT type. The ODA will not set RS to true or false on the ASI, so you need to set it manually.
The verbs added to the business object are the standard verbs, essentially Retrieve, RetrieveByContent, Create, Update and Delete.
If the return parameter of the stored procedure is of ResultSet Type, the ODA will analyst the result set and create a business object, making the columns of the result set attributes of the business object. The ASI for the stored procedure columns will be set as CN=StoredProcedureColumnName. The ODA sets the key attributes based on the JDBC metadata information returned by the driver. If none is returned, the ODA does not mark any attributes by default as keys. All other attributes, such as length and type, are set as for the attributes generated from tables.