Specifying business object information

After you create a business object, you can specify the business object-level ASI and the attribute-level ASI.

This section describes how to specify this information using the ODA with Business Object Designer. For a detailed description of these categories of information and what they mean for business object structure in the iSeries connector, seeUnderstanding business objects for the connector.

Specifying the attribute-level ASI

Business Object Designer displays the attributes for the business object. For details about the attribute-level ASI in the iSeries connector, see Specifying business object attribute level application text.

The attributes are listed on the Attributes tab in the order in which they appear in the business object structure, as defined by the numeric value in the Pos column.

Figure 19. Setting the Attribute ASI
Setting the Attribute ASI

For each attribute, the window provides the name of the attribute, its type, and the ASI information. On this window, you need to specify a key (required by Business Object Designer to validate and save a business object) for each business object for which the ODA has not already specified a key.

In the business objects, passwords are not set as default value and not traced due to security reasons. The Business object generated for a sequential data queue has one attribute corresponding to its data length. For keyed data queues, there are 2 attributes of which the first one corresponds to the key while the other has the remaining length i.e. Data Length - Key Length. For a business object with an attribute with ASI DataLength = X and DecimalPositions=Y and when a BO is sent with the value of that attribute with greater than X digits (with the number of digits in Decimal Positions are greater than Y) the Connector will truncate this value to a length of decimal part to Y and maintain the Data Length to X and process the Business object successfully. If the integer part exceeds the length X-Y then Connector should throw an error. For example, if the ASI for an attribute is PackedDecimal=True;Datalength=10;DecimalPositions=2, then the values 112345678, 12345678.1, and 12345678.12 are accepted, but the extraneous decimal digits after the maximum limit of 2 in 12345678.123 will be truncated, and the value is taken as 12345678.12. A trace message is given for it as "Truncated String Value:<12345678.12> for DecimalPositions=2". The value 123456789.12 will log an error :" Length is not valid."

You can also use this window to set child object keys as needed and specify the following information:

Specifying the business object-level ASI

After specifying the attribute-level ASI, you can view and modify the business object-level ASI. For details about business object-level ASI, see Specifying business object attribute level application text.

The business object-level ASI is listed on the General tab. The ASI value that appears in the field Business Object Level Application-specific information contains the name of the proxy class that represents this business object. The connector uses this information to map a proxy class to a business object, and, in the case of a server-side business object (when the connector also runs as a server), the connector uses this information to map an implementation class to a business object.

This screen also lists all the verbs that are supported by the business object and provides the ASI for each verb. On this screen you can modify the ASI of the business object and its supporting verbs.

Figure 20. Setting the business object-level ASI
Setting the business object-level ASI

Copyright IBM Corporation 2003, 2005. All Rights Reserved.